fix(behavior_path_planner): remove unnecessary publisher and subscriber

Description

Remove unnecessary publisher and subscriber.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Please remove it in launch.xml or remove this unused launch file.
https://github.com/autowarefoundation/autoware.universe/blob/main/launch/tier4_planning_launch/launch/scenario_planning/lane_driving/behavior_planning/behavior_planning.launch.xml#L6-L9

@kosuke55 Sorry, I missed it.
I fixed.


fix: Collapsible Navigation Example

🐛 Bug Report
On a website, i'm using a "FluentNavMenu" with Collapsible = true. But it's stopped working at version 4.10.0 and up.
when collapsed, it no longer open a popup of childs items when clicked.
💻 Repro or Code Sample
Your demo
Go to Collapsible Navigation Example, collapse, and click on item 3 => Exception and only showing 3.1 & 3.3
In my case, i'm displaying a FluentCard instead of a FluentNavLink in one of the FluentNavGroup and it doesn't show the popup at all on click :(
It also doesn't display any of the "normals" links.
🤔 Expected Behavior

😯 Current Behavior

I have to expand it, click on "Compte" to see my "login box"
like that :

💁 Possible Solution
Revert breaking changes introduced in 4.10
🌍 Your Environment
Win 10
Edge
.net 8 latest
`

<PackageReference Include="Blazor-ApexCharts" Version="3.4.0" />
<PackageReference Include="Blazored.LocalStorage" Version="4.5.0" />
<PackageReference Include="System.Formats.Asn1" Version="8.0.1" />

<PackageReference Include="System.IdentityModel.Tokens.Jwt" Version="8.1.1" />
<PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="8.0.8" />

<PackageReference Include="Microsoft.FluentUI.AspNetCore.Components" Version="4.10.0" />
<PackageReference Include="Microsoft.FluentUI.AspNetCore.Components.DataGrid.EntityFrameworkAdapter" Version="4.10.0" />
<PackageReference Include="Microsoft.FluentUI.AspNetCore.Components.Icons" Version="4.10.0" />

`
Thanks !

Have you added the new FluentMenuProvider to other providers? Now all "menus" use this provider.
https://www.fluentui-blazor.net/CodeSetup#add-component-providers

No, this

Have you added the new FluentMenuProvider to other providers? Now all "menus" use this provider. https://www.fluentui-blazor.net/CodeSetup#add-component-providers

This is a different issue. I'm able to replicate in the demo site. Currently investigating

Have you added the new FluentMenuProvider to other providers? Now all "menus" use this provider. https://www.fluentui-blazor.net/CodeSetup#add-component-providers

This is a different issue. I'm able to replicate in the demo site. Currently investigating

Will be fixed with next release. To solve this we actually need to not use the MenuService:


use ordered_float::OrderedFloat & impl From<&ObjHashable> for Obj

This can solve #3 . (please bump version if this is merged

Sure, LGTM. Sorry for not noticing for 8 months. Add a version bump (probably major just in case, since the behavior of hash does change) and apply the simplification I commented, unless you have any objections, and I'll merge this and publish to crates.io.

@sollyucko  Hi, where is the simplification you commented? Do I miss something? Or maybe your comments are still pending status?

My review comment is marked Pending. I suggested changing x.inner().iter().cloned().collect() to x.inner().clone().

My review comment is marked Pending. I suggested changing x.inner().iter().cloned().collect() to x.inner().clone().

Thanks, it's done.

LGTM. I'll merge now and publish to crates.io tonight. Thanks for contributing, and sorry for the huge delay!

I've published it to crates.io now! https://crates.io/crates/py-marshal/0.4.0
BTW, does this fix issues #3 and #4?

Yes, this fixes them.


WhiteList Cryptocurrency News Website, ZyCrypto.Com

hello, please whitelist our Cryptocurrency News Website , ZyCrypto.Com , we are a Cryptocurrency Media platform and we do not require any login details from our visitors to Read Our News Stories, i await your next positive reply.

Thanks a lot, it has been fixed.


Regenerate ID when copy-pasting checkboxes

Currently, selecting a checkbox and copying it into a new cell copies the content as-is.
It would be a very helpful addition to trigger the generation of a new id when an existing checkbox is pasted into the same document.
Alternatively a function to regenerate the id's on all checkboxes in the current document would work as well.
My use-case is tracking campaign preparation for a rpg:

Entering that many checkboxes manually is not fun, so i'm looking for easier ways.

Although it's not a solution, a workaround I've found is to use keyboard macros to quickly input the textbox notation.
Perhaps using a complex macro you could fully automate the creation of your checkboxes, at least until a solution is built into the plugin.

A command to regenerate checkbox ID's has been added to 3.0.0, alongside some improvements to the automatic conversion


The code of "Training-Free Confidence Scoring Mechanism"

Thanks for sharing your work. Are there some codes for "Training-Free Confidence Scoring Mechanism"? I clone the repository and only find eval/run_llava.py for runing a demo. And are there the evaluation code for coco?

Hi @CongHan0808 ,
Thank you for your interest in our work. In the init version of this repo, we only provide the demo code. We'll release the training and batch inference code later. Before the release, you can follow the instruction to modify the demo code:

Set the return_dict_in_generate=True and output_scores=True in the model.generate function.
Get the output sequence and corresponding score of each output token.
Calculate the bbox score and category score of each instance according to the paper (our implementation is the same as the paper description).

Later, we'll release the whole codes including the batch inference of REC/REG/Detection/Counting/Phrase Grounding.


Users can access the UI / API from remote IP address

The default configuration for the coffee demo is to run only accepting connections from localhost.  We need to document and test the configuration to allow someone to connect on the local network.

@Damfortx8 please make sure to document this configuration.

is in the readme

Link is wrong?  Goes to original project, not this project.

the link is the one (https://github.com/substrate-developer-hub/substrate-node-template) that's the base project where they explain all you need save the chain state, use the node in external mode, etc, i'm gonna add all of that to the readme making a reference


delay option

Hello, the delay (--delay) is a cool new feature, but it doesn't work properly with the extra extension (-x) param.
For example when I use '--delay 1000ms -x txt,php -t 1', my expectation is 1 request per 1 second.
But now, using v.3.1.0, I see 3 requests per second (word1, word1.txt and word1.php) and then a one-second delay before the next word2 from my wordlist.
My expectation is: word1 -- 1s delay -- word1.txt -- 1s delay-- word1.php -- 1s delay -- word2 -- 1s delay -- word2.txt -- ...
In case there is no option 'extension only', it is difficult to use this tool for enumerating when some protection like fail2ban exists.

this should be no problem anymore with the latest version


improve memory efficiency of sentmap

At the moment, sentmap is a list of frame-level objects. Each frame-level object in sentmap contains PN, sent_at, ack_epoch, etc. Size of quicly_sent_t is 48 bytes.
This PR splits packet-level information and frame level information. Sentmap is a list of packet_header followed by any number of frame-level objects. Size of quicly_sent_t becomes 32 bytes. In addition, byte-in-flight counter is integrated into sentmap, thereby reducing the need for a separate sentmap entry (i.e. quicly_sent_t::data.cc).
The change typically reduces the memory footprint of sentmap; footprint decreases from 96 bytes to 64 bytes when one retransmittable frame is sent in a packet. The difference gets bigger if multiple frames are included in one packet.
The only case that increases memory footprint is when sending an ACK only packet without an ACK gap; the size changes from 48 bytes to 64 bytes. However, that would be the case where we'd be using least memory (just receiving things!), and hopefully that would be a non-issue.
The API has been changed. Writing to sendmap is now surrounded by "prepare" and "commit" calls (for writing packet-level information). Iteration is now per-packet rather than per-frame. Doc-comment of struct st_quicly_sentmap_t in sentmap.h explains the new API.

@janaiyengar IIRC we've discussed making this change, I would appreciate it if you could review. Or if it helps, we can merge and then review the changes as time goes.
In general, I think this is a nice change becomes quicly.c becomes smaller and so does the memory footprint.

Let's merge, then discuss. Having less number of branches helps.

W00t!! Apologies for not responding sooner -- I dropped off during the break.


Publish as maven artifact

Your server provides great configuration posibilities that allows to integrate it to custom environment, such as provide custom class loader for code completion, lsp proxy etc. but unfortunately it is not published to the Central Repository what make it difficult to include to build.

At this time, we have no plans to publish a release of this project to Maven Central or anywhere else.

@joshtynjala Hey, would you be open to tagging versions in the git repo? This would allow it to be added to https://github.com/mason-org/mason-registry. Any tag would do really, perhaps the current date? (I took a quick peek and it doesn't seem like the language server implementation is versioned).


Python 3 support - NameError: name 'basestring' is not defined

I get the following error
    if not isinstance(value, basestring) and not isinstance(value,
NameError: name 'basestring' is not defined```

when I try to PUT a key:

def put(self, key, value, cache=None, options={}):
...
if not isinstance(value, basestring) and not isinstance(value,
(int, long)):
value = json.dumps(value)
   ...

Should `basestring` [be replaced with] (http://stackoverflow.com/a/1979107) `str`?

Hi @CambridgeMBN ,
You have old version of iron_cache client lib. Please install it by cloning from here or with pip install iron_cashe. The issue was resolved here: https://github.com/iron-io/iron_cache_python/pull/6
Thanks!

I pulled the package straight from pip, so you might want to update that too. Thanks for letting me know.


Error: undefined method `debug' for nil:NilClass

Describe the bug
A clear and concise description of what the bug is.
I attempted to add debug statements in the following file /lib/bosh/blobstore_client/base.rb
but getting errors that the existing logger is Nil.
To Reproduce
Steps to reproduce the behavior (example):

Deploy a bosh director on vsphere with Opsman 2.9.0-build.106
Modify this ruby file with the following

      def validate!(agent_blobstore_options, stemcell_api_version)
        return if can_sign_urls?(stemcell_api_version)

        has_all_required_creds = (required_credential_properties_list - agent_blobstore_options.keys).empty?

        return if has_all_required_creds

        logger.debug("test to see if logger can be invoked")
        raise(
          Director::BadConfig,
          "Inconsistent blobstore configuration: #{required_credential_properties_list.inspect} are required",
        )
      end

Expected behavior
Expected to see printout of "test to see if logger can be invoked" in the director logs
Logs
Logs
Versions (please complete the following information):

Infrastructure: vsphere
BOSH version 270.11.1
BOSH CLI version 6.2.1-a28042ac

releases:
- id: 61ae1a8c-6ed3-49b0-794b-3ad633d06d59
  name: bosh
  version: 270.11.1
- id: b95e4342-3d64-438f-6c0b-f8a40ce780ce
  name: bosh-vsphere-cpi
  version: 53.0.9
- id: 055414d6-3752-4071-710e-3ccd21efe988
  name: uaa
  version: 74.5.11
- id: dc7bff46-ec29-4766-6b20-15b12b27fd4f
  name: credhub
  version: 2.5.11
- id: ed045fac-a954-4fab-41e9-27f35b87d08c
  name: bosh-system-metrics-server
  version: 0.0.24
- id: cf3ac665-e7bf-4eae-69b5-c18d6d2d7de4
  name: os-conf
  version: 21.0.0
- id: f7ef73f8-c3fb-4e86-5ab8-3f6d90916be4
  name: backup-and-restore-sdk
  version: 1.17.2
- id: 7c9acfd0-77fe-464f-72ab-a510d02f32c2
  name: bpm
  version: 1.1.7
stemcells:
- alias: default
  os: ubuntu-xenial
  version: "621.55"
- alias: windows
  os: windows2019
  version: "2019.15"

I think this has to do with ruby inheritance: the actual blobstore object being used isn't base.rb and so validate! isn't a first-class method on the 'real' client.  Take a look at how create and create_object are working in the other clients. You could try @logger here? This isn't a bug with bosh, it's how ruby works. Closing this issue.


Remove experimental batching/unbatching API

https://github.com/facebookresearch/torcharrow/blob/64014481d942229ca5d9222fe4532a29b2628da3/torcharrow/icolumn.py#L1727-L1744
This is an experimental prototype API. However since customized batching in deep learning can be quite adhoc (e.g. https://github.com/pytorch/data/blob/cbd19f01fe92b7039583ea9fff29df2c6a898a9c/torchdata/datapipes/iter/transform/bucketbatcher.py#L28-L34), it's beyond DataFrame API's scope to handle it and should be handled by DataLoader instead.

Ehhhh I'm not so sure. The standard batching case really is this simple. I would consider this a convenience for when the user wants to quickly form some batches to start iterating to test a model or something - they won't be using the dataloader then.

Ya that sounds fine to me. I'm not super opinionated either way, just advocating the "syntactic sugar is nice" side to balance to "pruning the API" side 😀.

Add docstring with EXPERIMENTAL API for now:
https://github.com/facebookresearch/torcharrow/blob/380e1cbaf334b49d52242596c79627d456ef3b0d/torcharrow/icolumn.py#L1416-L1437


E2E Testing with Detox

Fixes #326
Creator

[ ] Build relevant tests if any apply
[ ] Ensure there are no new warnings
[ ] Upload an animated GIF showcasing the solution (if it applies)
[ ] Set a relevant reviewer

Reviewer

[ ] Run test and make sure all tests pass
[ ] Review function and form on iOS
[ ] Review function and form on Android
[ ] Review function and form on Web
[ ] Review new test logic

I still need to setup Android testing (which I don't think will be too difficult) and plugin these Detox e2e tests into our Jest testing workflow, in hopes to create a simple yarn test "do it all" command.
To run this locally, you'll need to yarn start and in a separate terminal tab run yarn test:e2e.

There are issues in trying to implement Detox into our current setup.

Inject this into Android is a pain and would need extensive time to configure.
On iOS, we branch out to a inapp-view to complete our giving flow. This 100% blocks our E2E test because Detox is not able to manipulate any view other then within the app of testing.

There is a path we could take to bring the entire give flow into native, but that would take some paper on iOS side and some dev work. This should be a high priority after launch. cc: @FrankGrand


Change RFC3339_RE to accept offset like +08:00,+0800 or +08/+8

Summary
Make Mojo::Date->parse accept date time format from PostgreSQL, which is like 2017-12-15 06:37:19.393027+00. Now the offset part of the date time accept +08, +8, +0800, +800 and +08:00.
Motivation
Although RFC3339 is commonly used on the internet, we could found other ISO 8601 date time format widely used in other areas, e.g. PostgreSQL. So, the small changes would make Mojo::Date more useful in web application development.

+1

I think this change makes sense, but you need to provide unit tests for the PR to be accepted.

What would be the documentation situation for this change. How do we explain the partial ISO 8601 support (outside of RFC 3339) to our users?

Afraid i have to give this a 👎, since the documentation does not convince me. Specifically i'm not convinced that partial ISO 8601 support adds enough value to make up for the possible confusion it may cause.

So, a complete ISO 8601 support would be better or completely ISO 8601 is not considered?

What would we want full ISO 8601 support for?

Adding RFC 3339 support was an easy decision, since it is used in many web services. What would we use ISO 8601 for?

It would save me from having to fall back on Time::Piece in Mojo::XMLRPC https://github.com/jberger/Mojo-XMLRPC/blob/abf27ee6bd7f2cb842fb3cde22e7c7347a232d66/lib/Mojo/XMLRPC.pm#L179-L185

If we decide that ISO 8601 is a reasonable addition to Mojo::Date, the implementation will need a formal spec review, to make sure it is compliant and covers the whole spec.

And if RFC 3339 is a profile of ISO 8601, why is there still separate RFC 3339 code?

I would like to see:

support for ISO 8601!
full spec compliance
better test messages than "right epoch value": say which feature is being tested on each one
why not incorporate the 3339 stuff into this, if @kraih is right
documentation that is up to usual Mojo standards

I should clarify, I think supporting ISO 8601 would be a nice thing. I have not reviewed the proposed patch having been too busy with the advent calendar.

My initial thought for adding ISO 8601 support is just to make Mojo::Date to support date time format of TIMESTAMP in PostgreSQL. So, I could probably use Mojo:Date to replace DateTime. Well, I would also want to add some more features like date time comparison,  addition, subtraction etc.  Although, I am not sure whether Mojo::Date is designed for having these features.

Mojo::Date was not designed for having those features, it's primarily meant for dealing with HTTP header fields. And i don't think PostgreSQL is a good reason to add ISO 8601 support, since it has such good tools already for dealing with timestamps, like extract(epoch from foo) as foo.

Understand now. So maybe I extend the class for my own usage. :D.

Anyway, after learned what extract(epoch from foo) as foo is, I don't
really think that's a good practice for me. It looks I will always have
to do that trick when I retrieve timestamp from the database. :-)
On Mon, Dec 25, 2017 at 9:30 PM, Sebastian Riedel<EMAIL_ADDRESS>wrote:

Mojo::Date was not designed for having those features, it's primarily
meant for dealing with HTTP header fields. And i don't think PostgreSQL is
a good reason to add ISO 8601 support, since it has such good tools already
for dealing with timestamps, like extract(epoch from foo) as foo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kraih/mojo/pull/1167#issuecomment-353869772, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHeLbdKW2q1vY4Yl5_D1F7L2PzgpH9qMks5tD6NzgaJpZM4RDFEy
.

--
Steve Guo

I'm not sure how to move forward with this pull request. At the moment it seems out of scope for Mojolicious to have full ISO 8601 support. Are there any real world web development use cases? Any APIs or protocols using the format?

I'd be happy if Mojo::Date could be used to parse Atom/RSS dates, and ISO 8601 support seems like a step in that direction.

@dotandimet Don't those use RFC 3339 and RFC 822? Both are already supported by Mojo::Date.

More people have brought up the argument that ISO 8601 support would be good for working with PostgreSQL. And i'm afraid that argument did not convince me, in fact it did the opposite. I now believe that it would just encourage bad practices, like avoiding the use of more efficient native PostgreSQL features such as extract(epoch from foo) as foo.
We've tried very hard to find other use cases on IRC, but none could be found, so i'll have to vote 👎 on this proposal for now.

Oh, I see that RFC3339 (what the Atom spec uses) is a subset of ISO 8601.
Of course, what Atom/RSS feeds in the wild use is a different thing (DateTime::Format::RSS just throws parsers at the string until something sticks).
Off-topic, I now want Mojo::Date to support timezones (perhaps by using Time::Zone, if installed?)

@dotandimet Please stay on topic, we are voting only on this patch.

As I commented before, XMLRPC spec designates ISO8601also. That said I think that the response to this proposal seems to suggest there's some public interest in supporting more formats but not strong in use cases. Therefore I wonder if we should encourage roles for adding more formats.
Given that perspective I give this proposal a weak :-1:

I would like to see more powerful date support in Mojo::Date, but I think a role is the way to go. 👎 to adding this to core, but would love to see it on CPAN.

Ok, i think we can conclude that this proposal did not reach the required votes. The primary reason being lack of real world use cases. Therefore this vote only means that we won't merge the patch at this point in time, but will not rule out a new vote in the future. It seems likely that full ISO 8601 support could become relevant again with new developments, the web is a moving target after all. Until then it would be great to see this feature turned into a role (Mojo::Date::Role::ISO8601?). Thank you @guo-steve for this proposal.


Tx::is_signed_by can't check for staking key signatures

There are cases where we require transactions to be signed by staking keys instead of, or aside from, spending keys. But Tx::is_signed_by() right now only allows checking for signatures matching PubKeyHashes.
If we try checking for a staking key signature like for example:
spending myValidator

struct Datum {
    acct: StakeKeyHash
}

func main(datum: Datum, _, ctx: ScriptContext) -> Bool {
    ctx.tx.is_signed_by(datum.acct).trace("signed by holder: ")
}

...an error like the following is thrown:
...node_modules/@hyperionbt/helios/helios.js:1587
                return new UserError(msg, src, startPos, endPos);
         ^
UserError: TypeError on line 25: expected 'PubKeyHash' for arg 1, got 'StakeKeyHash'
    at Function.new (...node_modules/@hyperionbt/helios/helios.js:1587:10)
    at Function.typeError (...node_modules/@hyperionbt/helios/helios.js:1633:30)
    at Site.typeError (...node_modules/@hyperionbt/helios/helios.js:1508:20)
    at FuncType.checkCall (...node_modules/@hyperionbt/helios/helios.js:18592:10)
    at FuncEntity.call (...node_modules/@hyperionbt/helios/helios.js:19590:28)
    at CallExpr.evalInternal (...node_modules/@hyperionbt/helios/helios.js:32561:24)
    at CallExpr.eval (...node_modules/@hyperionbt/helios/helios.js:29831:23)
    at MemberExpr.evalInternal (...node_modules/@hyperionbt/helios/helios.js:32839:33)
    at MemberExpr.eval (...node_modules/@hyperionbt/helios/helios.js:29831:23)
    at CallExpr.evalInternal (...node_modules/@hyperionbt/helios/helios.js:32492:30)

Tx::signatories and Tx.addSigner in the api should probably be updated also..
https://www.hyperion-bt.org/helios-book/lang/builtins/tx.html#signatories
https://www.hyperion-bt.org/helios-book/api/reference/classes/Tx.html#addsigner

I just saw this now, and responded in discord.   Here are my comments below.
I think the trick is to add the staking key hash as a signer to the tx in the offchain code, and then onchain you can check the staking key as if it were a public key hash. Both staking key and public key are just opaque types around a bytestring hash. So from a cryptographic perspective, it is simply a matter of confirming that the hash matches the signature.

And in your example, instead of using StakeKeyHash in the datum, use a bytestring to pass the hash, and then create a PubKeyHash in the onchain code.
struct Datum {
acct: ByteArray
}
const stakingHash: PubKeyHash = PubKeyHash::new(acct);

instead of using StakeKeyHash in the datum, use a bytestring to pass the hash, and then create a PubKeyHash in the onchain code.

Thanks for this! Definitely a work-around for now.
Still, it'd be better if we can just do tx.is_signed_by(stakeKeyHash) in future versions.

I've been giving this some thought, and maybe the best option is to simply get rid of StakeKeyHash and represent it with a PubKeyHash instead?

reposting here my comment on discord:
I can't say I know much about the low-level stuff, but if StakeKeyHash has the same structure as PubKeyHash, then it makes sense to just use PubKeyHash and get rid of StakeKeyHash entirely.
Then perhaps it's just the  docs that will need updating to make it clear, especially to newcomers, that these two types are treated the same by Helios.

v0.15.11 removes all occurences of StakeKeyHash in favor of PubKeyHash


Use class attribute to check active

In oven, the active checking don't use value property and always return false.

Thank you! 🙂


Allow a cancelled RPC to interrupt metadata syncing

Is your feature request related to a problem? Please describe.
If a user triggers a sync (i.e. via a listStatus) on a large directory and the sync takes an extended period of time, then the user might be inclined to ctrl-C to cancel the RPC and issue it again.
The problem with this now is that the metadata sync will continue to run on the master until completion. Only after completion will the handler eventually run into an error when returning the RPC response.
Imagine syncing a large directory that creates > 1M files. This will consume a large swath of CPU for some period of time. Depending on the hardware configuration, this can be a long time. If the user cancels the RPC, then it should interrupt the metadata sync which should allow more operations
Describe the solution you'd like
The solution itself is straightforward. Each RPC is associated with an OperationContext<T> - the context has a method isCancelled which will return whether the RPC issued by the user has been cancelled for one or more reasons (user, network, etc..). It uses the underlying gRPC StreamObserver#isCancelled method.
Within a metadata sync we should be able to provide an OperationContext and periodically check the isCancelled on the operation to see if we should continue syncing.
Describe alternatives you've considered
None at the moment. The proposed solutions seems like a simple and straightforward implementation with few, if any, downsides. The only argument I could see against this is that someone wants a "fire-and-forget" implementation for syncing where they can issue an ls, cancel the command, and continue using their terminal while the sync runs. In that case, the user would just never know when the sync is finished - but they would at least know that it was started.
Urgency
Prevent over-utilization on the master that doesn't benefit any client operation.
Additional context
N/A

One other issue I'd like to bring up is that in the event of a cancelled RPC, then we can leave a half-synced directory. In the implementation we probably want to think about what we should do in such an event.
If the sync interval is set to, let's say, 1h. Then someone comes along that does an ls which triggers the sync and cancels it, then even if only half or 10% of the directory was synced, another sync won't be attempted for another hour.
We should probably remove at least the root path from the UFS sync path cache in this situation so an RPC following a cancel can still trigger a sync without having to wait for the metadata interval. @ggezer What do you think?

If we do reset the sync status for the cancelled sync session, then the root need not be an exception and it's more consistent to reset for all base paths.
Overall, I believe we shouldn't need to reset. The sync logic should be confident when marking a path as synced by making sure all its child has been synced and marked successfully. Then no reset would be necessary. However, I can see some challenges associated with this solution and am fine with resetting for now.


Does famfs provide POSIX-like interfaces for operating files under the famfs file system, such as open, close, write, read, lseek, and other functions?

Does famfs provide POSIX-like interfaces for operating files under the famfs file system, such as open, close, write, read, lseek, and other functions?

Yes, with some limitations:
The most interesting use case for famfs is mmap(). If you memory map a famfs file, you are directly accessing the memory. Unlike conventional mmap, famfs does not demand-page data from a backing device (e.g. SSD) into the page cache. If you access an address from a memory mapped famfs file, the memory is accessed directly; cache lines are loaded into the processor cache directly from the memory.
Back to the question, If a file already exists, you can use any of the posix calls, with the following limitations:

Writing works up to, but not past EOF, because famfs does not allocate-on-write
Truncate is not allowed - but famfs can't currently prevent it, so a file whose size has been modified will be marked invalid (and stop working). Recovery from this is umount/remount.

Creating a file is special, because famfs never does allocate-on-write. So you need to use the famfs CLI or API:

famfs create -s <size> <path>
famfs cp <srcfile> <destfile>    #srcfile can be anywhere; destfile is in a mounted famfs file system
You can also create files via the famfs library that is called by the cli

One way to think about it is that creating a famfs file is analogous to allocating memory that can be referenced via the file.
Also, if you are using a shared-memory dax device, only the system that created the filesystem can create files. This is because both memory allocation and metadata log append must be serialized.
Many of the current limitations can be relaxed or eliminated if use cases justify adding complexity to famfs.
Hope this helps. Let me know if you have more questions.
John


Give CA's friendly names

Currently when you import a CA the Friendly Name column in MMC.exe says <None>

DoD does not put friendly name on their certs


Error saving model with advanced activation layers

Hi,
I'm trying to implement an easy method for cloning a model for cross validation; what I've found is that model_from_json(model.to_json()) is the easiest way. However, this doesn't work with advanced activation layers.
# ... all required imports, etc.
# I wrote the function build to create and compile a Keras model
net = build(layers=[
     Dense(2500, input_dim = 6380),
     BatchNormalization(),
     PReLU(),
     Dropout(0.2),

     Dense(500),
     BatchNormalization(),
     Activation('sigmoid'),
     Dropout(0.2),

     Dense(100),
     BatchNormalization(),
     Activation(ParametricSoftplus()),
     Dropout(0.2),

     Dense(2),
     Activation('softmax')
], optimizer='nadam', loss='use')

json = net.to_json()
# throws AttributeError: 'ParametricSoftplus' object has no attribute '__name__'
model_from_json(json)

Please make sure that the boxes below are checked before you submit your issue. Thank you!

[x] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[x] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[x] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

Please provide your original code, this code cannot be ran, since there is some undeclared and unused variables such as model and net

So sorry about the trouble. I recently realized that the error was when I wrote Activation(ParametricSoftplus()); when I changed it to just ParametricSoftplus(), I could save the model.
Strangely enough, my neural net was still running just fine with Activation(ParametricSoftplus()) as a layer.


Fix for 2017.2

Potentially fixes #58 by adding  metallicRough to glTFStandardinput.
Disclaimer: I have no idea why this works but it did with 2017.2 :).
I haven't tested this in 5.6 and not sure if an ifdef needs to be added?

@stevenvergenz I think this should do it. would be great if you confirm too? Documentation seems hard to find on the exact pattern

I still get the shader error with those guards. But you're right, there's no documentation for what the shader macro is for the new versioning scheme. So I guess revert that commit, it does more harm than good. Sorry for the goose chase.


Better detect when to show annotation buttons

Parse html content on demand and strip the tags before checking the length. Display corresponding buttons only for appropriate content length.

@4vanger, refactored according to your suggestions.

Addressed comments. Also found and fix accidental mistake from the previous PR 🤦


Add a license

Amazing resource! I think it's awesome that you decided to open-source this.
One request: please explicitly add license. Note that making the GitHub repo public doesn't automatically make it open source:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository

Errr whoops, I forgot to copy the license over. Will do first thing tomorrow (should be Creative Commons).

Added the license. I ported the project over from Gatsby to Vuepress and forgot to copy the license over. Thank you!

Shoot me an ETH address and I'll send you an NFT for pointing this out :-)


cmocka: 1.1.5 -> 1.1.6

Version 1.1.6 has been released to fix several issues and a few small new features.

https://gitlab.com/cmocka/cmocka/-/blob/cmocka-1.1.6/ChangeLog
We might conditionalize the patch e.g. for musl only, but I don't think it could cause trouble elsewhere.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I wonder if this would fix the aarch64-linux failure: https://hydra.nixos.org/build/209830359#tabs-buildsteps
@ofBorg build cmocka

Sadly, it's a big rebuild on linux (around 16k for x86_64).  Maybe we'd better upgrade just on darwin for now?  In that case the patching wouldn't be needed either.  And then later rebuild to this PR's state for staging branch.


bug(clean): pipenv clean delete Python Markdown extensions

1. Summary
pipenv clean delete my Python Markdown extensions, that I install from GitHub.
2. Environment

Windows 10 Enterprise LTSB 64-bit EN,
Python 3.6.4,
Pipenv 10.1.2,
Pelican 3.7.1,
Python Markdown 2.6.11,
my repository on GitHub.

3. Files
I add my Python Markdown extensions to pelicanconf.py (see MARKDOWN subsection on official Pelican site), example:
MARKDOWN = {
    'extension_configs': {
        'downheader': {},
    },
    'output_format': 'html5',
}

4. Stepse to reproduce
I try build my site:
D:\Kristinita>pipenv run pelican -s publishconf.py
ERROR: Could not process Gingerinas\Korvers.md
  | ModuleNotFoundError: No module named 'mdx_downheader'
ERROR: Could not process Gingerinas\Testus.md
  | ModuleNotFoundError: No module named 'mdx_downheader'
# Another articles …
ERROR: Could not process Sublime-Text\Sublime-Text-Power-User-notes.md
  | ModuleNotFoundError: No module named 'mdx_downheader'
ERROR: Could not process Sublime-Text\ValeriyaSpeller.md
  | ModuleNotFoundError: No module named 'mdx_downheader'
Done: Processed 0 articles, 0 drafts, 0 pages and 0 hidden pages in 2.03 seconds.

I get errors. I need to install mdx_downheader extension.
D:\Kristinita>pipenv install git+https://github.com/cprieto/mdx_downheader.git#egg=mdx_downheader --dev
Installing git+https://github.com/cprieto/mdx_downheader.git#egg=mdx_downheader…
Warning: You installed a VCS dependency in non–editable mode. This will work fine, but sub-dependencies will not be resolved by $ pipenv lock.
  To enable this sub–dependency functionality, specify that this dependency is editable.
Collecting mdx_downheader from git+https://github.com/cprieto/mdx_downheader.git#egg=mdx_downheader
  Cloning https://github.com/cprieto/mdx_downheader.git to c:\users\sashac~1\appdata\local\temp\pip-build-tgmzt091\mdx-downheader
Requirement already satisfied: Markdown in d:\kristinita\.venv\lib\site-packages (from markdown-downheader)
Installing collected packages: markdown-downheader
  Running setup.py install for markdown-downheader: started
    Running setup.py install for markdown-downheader: finished with status 'done'
Successfully installed markdown-downheader-1.0.1

Adding git+https://github.com/cprieto/mdx_downheader.git#egg=mdx_downheader to Pipfile's [dev-packages]…
Pipfile.lock (46f8f0) out of date, updating to (2e4879)…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Updated Pipfile.lock (2e4879)!
Installing dependencies from Pipfile.lock (2e4879)…
  ================================ 37/37 - 00:00:23
To activate this project's virtualenv, run the following:
 $ pipenv shell

Now I can successful build my Pelican site:
D:\Kristinita>pipenv run pelican -s publishconf.py
Done: Processed 26 articles, 0 drafts, 0 pages and 0 hidden pages in 6.94 seconds.

But pipenv clean delete mdx_downheader:
D:\Kristinita>pipenv clean --verbose
Ignoring 'six'.
Ignoring 'packaging'.
Unintalling 'markdown-downheader'…
Unintalling 'mdx-customspanclass'…

I can't build my site again.
D:\Kristinita>pipenv run pelican -s publishconf.py
ERROR: Could not process Gingerinas\Korvers.md
  | ModuleNotFoundError: No module named 'mdx_downheader'
ERROR: Could not process Gingerinas\Testus.md
  | ModuleNotFoundError: No module named 'mdx_downheader'
# Another articles …
ERROR: Could not process Sublime-Text\Sublime-Text-Power-User-notes.md
  | ModuleNotFoundError: No module named 'mdx_downheader'
ERROR: Could not process Sublime-Text\ValeriyaSpeller.md
  | ModuleNotFoundError: No module named 'mdx_downheader'
Done: Processed 0 articles, 0 drafts, 0 pages and 0 hidden pages in 2.92 seconds.

Thanks.

Don't run clean.

@kennethreitz , I run pipenv clean, that clean really unneeded packages.
Thanks.

oh i see what's happening here — you need to provide your git installs as editable in order for us to know about their dependencies.

@kennethreitz, thanks, it works for me!
If I install Python GitHub packages in format:
pipenv install -e git+https://github.com/user/package_name.git#egg=package_name --dev

pipenv clean doesn't clean these packages:
D:\Kristinita>pipenv clean --verbose
Ignoring 'markdown_downheader'.
Ignoring 'markdown_newtab'.
Ignoring 'mdx_cite'.
Ignoring 'mdx_customspanclass'.
Ignoring 'six'.
Ignoring 'packaging'.

Type: Addition ➕
1. Summary
If you installed VCS dependency, package_name should be whatever Pipenv wants (I can’t say that I fully understood the algorithm). Otherwise, pipenv clean delete it.
2. MCVE
For example, I want to download https://github.com/exaroth/mdx_custom_span_class extension. I tried:
D:\SashaDebugging\KiraPipenv>pipenv install -e git+https://github.com/exaroth/mdx_custom_span_class.git#egg=mdx-custom-span-class
Installing -e git+https://github.com/exaroth/mdx_custom_span_class.git@master#egg=mdx-custom-span-class…
Adding mdx-custom-span-class to Pipfile's [dev-packages]…
Installation Succeeded
Pipfile.lock (634863) out of date, updating to (bd9137)…
Locking [dev-packages] dependencies…
           Building requirements…
Resolving dependencies…
Success!
Locking [packages] dependencies…
Updated Pipfile.lock (bd9137)!
Installing dependencies from Pipfile.lock (bd9137)…
  ================================ 1/1 - 00:00:02
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.

But package_name mdx-custom-span-class is not a good idea. pipenv-clean will delete the extension:
D:\SashaDebugging\KiraPipenv>pipenv clean --verbose --dry-run
Ignoring pip.
Ignoring setuptools.
Ignoring wheel.
mdx-customspanclass

I deleted mdx-custom-span-class:
D:\SashaDebugging\KiraPipenv>pipenv uninstall mdx-custom-span-class
Uninstalling mdx-custom-span-class…
Removing mdx-custom-span-class from Pipfile…
Locking [dev-packages] dependencies…
 Locking…Building requirements…
Resolving dependencies…
Success!
Locking [packages] dependencies…
Updated Pipfile.lock (53199a)!

And installed the extension again under the name mdx-customspanclass that appeared when I ran the command pipenv clean --verbose --dry-run:
D:\SashaDebugging\KiraPipenv>pipenv install -e git+https://github.com/exaroth/mdx_custom_span_class.git#egg=mdx-customspanclass
Installing -e git+https://github.com/exaroth/mdx_custom_span_class.git#egg=mdx-customspanclass…

Adding mdx-customspanclass to Pipfile's [dev-packages]…
Installation Succeeded
Pipfile.lock (53199a) out of date, updating to (b9a889)…
Locking [dev-packages] dependencies…
           Building requirements…
Resolving dependencies…
Success!
Locking [packages] dependencies…
Updated Pipfile.lock (b9a889)!
Installing dependencies from Pipfile.lock (b9a889)…
  ================================ 0/0 - 00:00:00
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.

Now I can use this extension and pipenv clean won’t delete it:
D:\SashaDebugging\KiraPipenv>pipenv clean --verbose --dry-run
Ignoring pip.
Ignoring setuptools.
Ignoring wheel.

3. Environment

Windows 10.0.18363 Pro N for Workstations 64-bit EN
pipenv, version 2020.8.13

Thanks.


Support Windows

I don't know how feasible this is, but I'm seeing some crashes when running tests for my project on Windows (SR-13819) but I'm not seeing anything useful in the console printed when the crashes occur.
I went to try to integrate this library to learn more about those crashes, but quickly realized that this only works on Linux at the moment.

cc @compnerd, any advice?

Its a non-trivial amount of work to support this on Windows.  I assume that you are trying to do this for the non-current thread?  Is this in process or out-of-process?

@compnerd this is in-process and at least on Linux on the current thread which has hit the signal. We install the signal handler such that it runs on the thread that sees SIGILL. So we just grab the backtrace by walking the current stack.

@weissi oh, if it's current thread, in process that might be a bit easier to do.
Signals don't exist on windows, and SEH exception trapping does require that you don't use clang.  But, perhaps a first chance continuing VEH handler might do the trick.  VEH might let us get away with it since it doesn't require the SEH setup.  Might require some experimentation to validate the idea.

The bottom portion of the stack traces seem to be roughly close to what I believe the output should be on Linux.  I'll upload patches for that soon.

Wow, that was super quick. Thank you @compnerd !!

You're welcome! 😄


Stash RPC logic refactoring

Fixes https://github.com/rgb-org/rgb-node/issues/135
depends on https://github.com/rgb-org/rgb-core/pull/5

Updated undoing validation() changes.

Needs rebase.
There is a potential attack when we merge transitions and anchors without checking that we already have them: if the new consignment in its history re-uses known state transitions & anchors they will have a different reveal options and will replace older ones, leaving to a de-facto fund loss. So can you pls do a separate PR which will change the Storage logic such that it will properly merge transition and anchor data if they are already known? (I.e. take both old and new copies from stash and consignment and create a third one containing all revealed info from both, which should replace a previously stored one)

Rebased with requested changes.

There is a potential attack when we merge transitions and anchors without checking that we already have them: if the new consignment in its history re-uses known state transitions & anchors they will have a different reveal options and will replace older ones, leaving to a de-facto fund loss. So can you pls do a separate PR which will change the Storage logic such that it will properly merge transition and anchor data if they are already known? (I.e. take both old and new copies from stash and consignment and create a third one containing all revealed info from both, which should replace a previously stored one)

Will start working on this.


StoreClass.state access

Reflux creates singletons for stores, and stores them at StoreClass.singleton. So accessing a store's state directly (for example, property foo) goes StoreClass.singleton.state.foo.
For convenience, StoreClass.state can be a getter that gets StoreClass.singleton.state in order to simplify that to StoreClass.state.foo.

done in v6.4.0


improve the availablity message for deprecate manifest APIs

motivation: existing message is generic and does not provide an actionable fix
changes: add information to the message to make it more actionable

@swift-ci please smoke test


Add coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2fd1fa6). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #13   +/-   ##
=========================================
  Coverage          ?   91.87%
=========================================
  Files             ?        5
  Lines             ?      197
  Branches          ?        0
=========================================
  Hits              ?      181
  Misses            ?       16
  Partials          ?        0

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 2fd1fa6...9b3a528. Read the comment docs.


node cloud-config systemd-networkd units should be updated to use [Link] Unmanaged=true

As a fix for #1264, the CoreOS cloud-config used by Kontena plugins ships the following /etc/systemd/networkd units to prevent systemd-networkd from managing the weave and veth interfaces, causing netlink races:

50-docker.network -> /dev/null
50-docker-veth.network -> /dev/null
zz-default.network with [Match] Name=...

However, these network units have also been updated by CoreOS to fix the same issues in a different manner:

https://github.com/coreos/systemd/pull/73 added support for [Link] Unmanaged=true
https://github.com/coreos/coreos-overlay/pull/2300 changed the 50-docker.network and 50-docker-veth.network units to use [Link] Unamanged=true in order to fix the same issue for Docker interfaces
https://github.com/coreos/coreos-overlay/pull/2306 renamed the 50-docker-veth.network to 90-docker-veth.network meaning that our /etc/systemd/network/50-docker-veth.network no longer masks it out (?)

This combination continues to work correctly on most CoreOS platforms, leaving both the Weave and Docker interfaces unmanaged. However, it unnecessarily diverges from the upstream CoreOS fix for the same issue.
The current Kontena CoreOS cloud-configs are also broken on VMWare platforms, since CoreOS also ships a yy-vmware.network unit which does the same thing as zz-default.network, meaning that our network units overrides do not prevent the yy-vmware.network from matching the docker0 bridge, since we mask out the 50-docker.network.
Instead of masking out the 50-docker.network units and overriding the zz-default.network to limit the [Match] criteria, we should instead utilize the new support for [Link] Unmanaged=true, by reverting the masking out of the 50-docker.network and *-docker-veth.network units, and instead adding in a new 50-weave.network that also marks the weave and datapath bridges as unmanaged. Then we should be able to revert back to the unmodified upstream zz-default.network unit.

Weave-related interfaces that need to matched and explicitly configured as unmanaged on CoreOS to prevent the zz-default.network from matching:

datapath Driver=openvswitch
weave Driver=bridge
dummy0 Driver=dummy (but udevadm info /sys/class/net/dummy0 is missing any DEVTYPE?)
vethwe-datapath Driver=veth
vethwe-bridge Driver=veth
vxlan-6784 Driver=vxlan

The suggested network units for this:
50-weave.network
[Match]
Name=weave datapath

[Link]
Unmanaged=true

This is the critical configuration required to prevent systemd-networkd from causing netlink errors or orphaned veths when weave tries to setup the container veth interfaces.
50-weave-vxlan.network
[Match]
Type=vxlan
Name=vxlan-6784

[Link]
Unmanaged=true

Not yet 100% sure what the best way to match this is... if the vxlan-6784 name is stable, then this could just be merged into the 50-weave.network... otherwise, this should be 90-vxlan.network with just Type=vxlan?
90-dummy.network
[Match]
Name=dummy0

[Link]
Unmanaged=true

I don't think the dummy0 interface is actually used by weave (the interface is down), but launching weave seems to load the dummy module, which will always create the dummy0 interface... and the CoreOS yy-default.network will then bring it up and attempt to configure it. I doubt that will ever do anything, but best to avoid it.

Note that updating an existing node with masked 50-docker.network units to use the new 50-weave.network and removing the zz-default.network override will result in a broken system, if the network units for unmanagingthe  docker0 and veth interfaces remain masked out. Must also remember to clean out any /etc/systemd/network/50-docker*.network -> /dev/nullsymlinks.

Simplest configuration that would work:
50-weave.network
[Match]
Name=weave datapath vxlan-6784

[Network]
Description=Network interfaces managed by weave

[Link]
Unmanaged=true

This is the critical configuration required to prevent systemd-networkd from causing netlink errors or orphaned veths when weave tries to setup the container veth interfaces.
This assumes that the vxlan-6784 name is stable.
90-dummy.network
[Match]
Name=dummy0

[Link]
Unmanaged=true

This could also be merged into the 50-weave.network unit, but I think it's clearer to keep it separate.


Feat/forgot password flow

This fixes #12 . It makes use of the localstorage as a stub for link authentication.
It also adds a loading screen as well as fixes a couple of issues with the UI's copy.
@devvspaces please review

Good work @orunto


[ic-dialog]: Dismiss button on dialog does not appear correctly

Summary of the bug
The dismiss button in the top right does not appear. However, when hovering in the area, the hover state for the button appears
🪜 How to reproduce

Navigate to the "Code" tab of the "Dialog" component page on the guidance site
Select a dialog
Hover in top right

🖥 📱 Device

Device: MacBook
Browser version: Safari 16

🧐 Expected behaviour
Dismiss icon button should be displayed.
Additional info
May be an issue with the SVG rather than the button itself
Raised by: @jd239

Closed as duplicate of #1242


Document prefer_system_executable for chrome-headless

The recommended setup instructions for chrome-headless, which tell the user to install the dependencies globally using npm -g install, only work if we set prefer_system_executable: true in the generator options.
This should definitely be mentioned in the docs, as it currently requires digging through the code to find this line: https://github.com/gutschilla/elixir-pdf-generator/blob/master/lib/pdf_generator.ex#L184

Hi @richeterre – will be published with a bunch of other things in v0.5.5 later today. Thanks a lot for spotting the missing documentation and coming up with a PR. Veeerrrryy nice! :100:

Oh thanks for fixing the "shrome" typo as wee :grimacing:

Awesome! If you could also add some instructions for getting chrome-headless to work on Heroku (e.g. what buildpacks to install etc), that would be 😑👌 Or even better, would it be possible to ship the dependencies via local node_modules?

I have no experience with Heroku, unfortunately. The current Heroku documentation is a contribution from a user. But I'll ask him.
For the node_modules one could link the package.json from _deps/pdf_generator/package.json to your project directory and run "npm install" there and configure the chrome-path accordingly.
The right way would be to have the external dependency downloaded in the "mix.deps" task. I am right now unsure how to achieve this.

The right way would be to have the external dependency downloaded in the "mix deps.get" task. I am right now unsure how to achieve this.

This sounds like the perfect way – no additional steps needed beside installing the library 👍 Perhaps you could open a "Help wanted" issue? I'm still quite a noob at this stuff, but could this package  be useful?
I agree that the npm approach is not ideal, especially since for Phoenix apps there is already a package.json in the assets directory…


Update OSO Proxy URL to external route name

Fixes openshiftio/openshift.io#4125

Ike Plugins (test-keeper)
Thank you @aslakknutsen for this contribution!

It appears that no tests have been added or updated in this PR.
Automated tests give us confidence in shipping reliable software. Please add some as part of this change.
If you are an admin or the reviewer of this PR and you are sure that no test is needed then you can use the command /ok-without-tests as a comment to make the status green.
For more information please head over to official documentation. You can find there how to configure the plugin.

/ok-without-tests


feat: Add string repr for Record struct in pyauditor

This closes #596

Codecov Report

Merging #626 (8e7f5a5) into main (1f163ce) will increase coverage by 1.30%.
Report is 2 commits behind head on main.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #626      +/-   ##
==========================================
+ Coverage   63.13%   64.43%   +1.30%
==========================================
  Files          46        1      -45
  Lines        5807      388    -5419
  Branches       58       74      +16
==========================================
- Hits         3666      250    -3416
+ Misses       2141      138    -2003

Components
Coverage Δ

apel_plugin
64.43% <ø> (-3.05%)
:arrow_down:

auditor
∅ <ø> (∅)

slurm_collector
∅ <ø> (∅)

slurm_epilog_collector
∅ <ø> (∅)

htcondor_collector
∅ <ø> (∅)

priority_plugin
∅ <ø> (∅)


Missing config file info in log file

Hi Toby,
I tried to follow your description on bad robot, but still have problem. The temperature-machine.log file says this:
^@2018-05-11 03:58:29:887+0000 [main] INFO The config file /home/pi/.temperature/temperature-machine.cfg doesn't exist, run "temperature-machine --init" to create it.
^@2018-05-11 03:58:30:145+0000 [main] ERROR There was an error loading config; /home/pi/.temperature/temperature-machine.cfg (No such file or directory)
to create it.
^@2018-05-11 03:58:30:145+0000 [main] ERROR There was an error loading config; /home/pi/.temperature/temperature-machine.cfg (No such file or directory)
Any advice would be highly appreciated! :)

Hi,
tl;dr - ignore the blog post, install via apt-get instead
The blog article is out of date now, I literally just switched to install things via apt-get which should make things a lot easier. If you're attempting to install from source, you should switch to the new model. See
http://temperature-machine.com/docs
Let me know if that makes sense and you can make progress.

Thanks for the quick reply!
The apt-get install seems to be working! A lot easier for sure!


[BUG] rke2-coredns and rke2-ingress-controller pod in crashloopbackoff for imported rke2 cluster post k8s upgrade

Information about the Cluster
Rancher Server Setup

Rancher version: v2.6.6 upgraded to v2.6.7-rc3
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1, v1.23.6 , 1.3.11

Proxy/Cert Details: Self-signed

Information about the Cluster

Kubernetes version: v1.23.8+rke2r1 upgraded to v1.24.2+rke2r1
Cluster Type (Local/Downstream): Downstream imported cluster

Describe the bug
After upgrading the k8s version of the downstream imported cluster, rke2-coredns-rke2-coredns pod and rke2-ingress-nginx-controller are in crashloopback off state and never comes up active.
To Reproduce

Create a standalone rke2 cluster with 3 control planes and 1 worker node on k8s version v1.23.8+rke2r1 and import the cluster to rancher 2.6.6
Upgrade rancher server to v2.6.7-rc3
Upgrade the kubernetes version of the downstream rke2 imported cluster to v1.24.2+rke2r1

Result
From kube-system namespace, rke2-coredns and rke2-ingress-controller pod are in crashloopbackoff with the error
        message: 'failed to create containerd task: failed to create shim task: OCI
          runtime create failed: runc create failed: expected cgroupsPath to be of
          format "slice:prefix:name" for systemd cgroups, got "/kubepods/pod25d15bbd-8cca-48dc-9d00-f213a8d29049/5f23109c68600f5e8f370db076cd2c3529581595b6f1682798f87392aa5fc30e"
          instead: unknown'

CrashLoopBackOff (back-off 5m0s restarting failed container=rke2-ingress-nginx-controller pod=rke2-ingress-nginx-controller-bbgxb_kube-system(bb602ed0-ec83-406f-b340-e61923328962)) \| Last state: Terminated with 128: StartError (failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: expected cgroupsPath to be of format "slice:prefix:name" for systemd cgroups, got "/kubepods/burstable/podbb602ed0-ec83-406f-b340-e61923328962/6e067400106e6e36e4ec5996819f6d7b4e288183e3cff638916b7e60a9b10e24" instead: unknown),

Expected Result
expected no errors in the coredns and ingress controller pods.
Additional context
As a workaround when I re deploy the pods, the pods came back up active.

Here is a screenshot of the pod in crashing loop

the problem is not reproducible: following the same steps to import and then upgrade a rke2 cluster on the same setup does not hit the same problem.
Also, I can confirm that the workaround is deleting the broken pod.
Therefore, I do not think this is a release blocker and move this issue to to-test.

Can confirm the issue is not reproducible again. will close the issue and re open if seen again in the future.


Save function not working on iOS

Bug report
What I did
Run an app built with the latest version of Backpack and accessed the save function through Mobile Safari and Chrome on iOS 15.6.1.
What I expected to happen
That the entity changes would be saved.
What happened
Nothing. No error appeared, the changes were not saved, the page did not change.
What I've already tried to fix it
Nothing.
Is it a bug in the latest version of Backpack?
After I run composer update backpack/crud the bug is still there.
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 8.1.2-1ubuntu2.9 (cli) (built: Oct 19 2022 14:58:09) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.2, Copyright (c) Zend Technologies
with Zend OPcache v8.1.2-1ubuntu2.9, Copyright (c), by Zend Technologies
LARAVEL VERSION:
v9.46.0@62b05b6de5733d89378a279e40230a71e5ab5d92
BACKPACK VERSION:
5.4.14@f77c74c1d6ae8b0dedf825f74c6c1aea84ba1992

Hey @malle-pietje thanks for the report.
 Page don't refresh, nothing?
Does it happen with every save action, or only the actions that are inside the dropdown?
Cheers

Hi @pxpm , yes, nothing happens whichever save function from the dropdown is used. Not even an error message. This is what the page looks like:

Unfortunately I don't have access to the browser console on the iPad (don't use MacOS) so can't check any output there.

Updated the version details.

By the way, the issue also occurs when accessing the demo, for example here:
https://demo.backpackforlaravel.com/admin/cave/create

This is because Safari appears to have a problem with .requestSubmit()
Getting the same problem on Safari 15 on MacOS.
It is supposedly fixed in Safari 16, but I can't try because that seems to necessitate a MacOS update that I don't want at this point.
This renders Backpack unusable on some Safaris.

@pekka Thanks for confirming. I just tested this with Mobile Safari 16 (iOS update on my iPad from last night) and the save function now works again! 😄

Thanks for confirmation guys 🙏
@pekka from my research, we can replace requestSubmit by form[0].dispatchEvent(new SubmitEvent('submit')) in https://github.com/Laravel-Backpack/CRUD/blob/050b288caf2f60c79313f2b0b7d4fefd25177f3f/src/resources/views/crud/inc/form_save_buttons.blade.php#L88 and https://github.com/Laravel-Backpack/CRUD/blob/050b288caf2f60c79313f2b0b7d4fefd25177f3f/src/resources/views/crud/inc/form_save_buttons.blade.php#L103
I don't have an Apple product to test, would you mind manually testing yourself the change ? If it works feel free to submit the PR.
@tabacitu @maurohmartinez any of you guys has a way to test this ?
Cheers

@pekka from my research, we can replace requestSubmit by form[0].dispatchEvent(new SubmitEvent('submit')) in

This does not seem to be working yet - there are no errors anymore, but the form is not submitted either and the button remains forever in its clicked state (with the bright background colour):

Hmm. Trying to wrap my head around what requestSubmit() does in the first place, if I work it out I'll see if I can find a fix...

Nope. Can't get any version of
form[0].dispatchEvent(new SubmitEvent('submit'))

to work on Safari 15. Tried different ways to create the event (new Event()... with bubbles set to false and true), different ways to address the form... the event just doesn't seem to fire, regardless whether the form is filled correctly or not, or (this is what I suspect) the event gets cancelled at some point with no error message.
This SO question mentions a "fix" - firing a .submit() right after dispatching the event. But that just submits the form regardless of any validation errors, which seems to be the reason why .requestSubmit() is used in the first place.
I'm baffled!

Not sure if this is related or I should open a new issue, but save actions within the dropdown list do nothing. I am not using iOS (I am on Windows 11 using Chrome).

@pxpm, not sure what is the current status on this, but we might use something like this polyfill: https://github.com/javan/form-request-submit-polyfill/blob/main/form-request-submit-polyfill.js which should handle the case with Safari versions before 16.

@pxpm

@tabacitu @maurohmartinez any of you guys has a way to test this ?

I cannot reproduce this... it works without issues on my end. @tabacitu Have you been able to try this on your end?

@pxpm

@tabacitu @maurohmartinez any of you guys has a way to test this ?

I cannot reproduce this... it works without issues on my end. @tabacitu Have you been able to try this on your end?

As reported by me, it is now fixed with iOS 16.

I left the issue open because others were still seeing it.


Lazy inspection

Do not request anything from the kernel if the variable inspector is not currently open
This fixes performances issues, at least when the UI for the variable inspector is not open https://github.com/jupyterlab-contrib/jupyterlab-variableInspector/issues/307
cc. @achhina @trungleduc

The visual regression tests seem to fail on main too, this https://github.com/jupyterlab-contrib/jupyterlab-variableInspector/pull/310 should fix it


Setup release 24.0.1 branch

PR to allow stub.yml to trigger based on changes to release/24.0.1 branch.

Wrong branch to merge commit into. Closing.


how about enrich the output of duckdb_cli --version

the current output is:
➜ build/release/duckdb_cli --version
DuckDB c820266a6

rebuild duckdb_cli after some modification on the code without git commit, the output is changed:
➜ build/release/duckdb_cli --version
DuckDB 0e4b94f95

It would be nice to have these messages on the result of --version:

the latest release version on the current build branch, for example, "v0.1.7" on master branch
the git hash of the last commit, for example, it's 0e4b94f958b120fdaad45bda594933a2b84fced5 on master branch
is there some uncommitted changes on the current build branch

It would be helpful when we need to investigate issues reported by users

the latest release version on the current build branch, for example, "v0.1.7" on master branch

I think this is a good idea. We should have the tag name in there if there is one (and another marker like "unreleased version" otherwise).

the git hash of the last commit, for example, it's 0e4b94f958b120fdaad45bda594933a2b84fced5 on master branch

This is already there, no? Albeit a bit short.

is there some uncommitted changes on the current build branch

I don't see much of a reason for this.  It would also be a bit difficult to maintain this.

Should also be consistent to #672

When installed via homebrew, duckdb prints the version as b'XXXX', which looks somewhat odd. Is that expected?
> duckdb --version
DuckDB b'd9bcedd'

I think we fixed this, this was indeed an issue in our build script

Cool. I guess it will be fixed with the next release then.

This now outputs something like 0.2.4-dev389 fe8d8dd9f

This now outputs something like 0.2.4-dev389 fe8d8dd9f

Can confirm
$ duckdb --version
0.2.3 436f645

Can confirm
$ duckdb --version
0.2.3 436f645


id nextval in generic_cityobject

Is there a particular reason why the id column in the generic_cityobject table is not nextval incremented?

Yes. The id column of generic_cityobject references the id column of cityobject per foreign key constraint. The latter is nextval incremented using the cityobject_seq sequence.

Ok, makes sense!


Discontinue AuthService and consolidate logout function into UserDetails and pre/post-LogoutTasks

Now the logout function spreads across AuthService, UserDetails, and preLogoutTasks/postLogoutTasks services.
By consolidation, hawtio plugin authors should be able to customise logout behaviour via UserDetails and preLogoutTasks/postLogoutTasks services.

This requires pulling some code from hawtio-utilities into hawtio-core.

See https://github.com/hawtio/hawtio-core/commit/e7c0369980f72d2948146202635381c1ee9598b3#r27718579


[ACCSEC-22227] - Manage biometric authentication errors.

Jira Ticket
ACCSEC-22227
Github Issue

ISSUE-

Description

Add BiometricError enum.
Handler biometric errors using canEvaluatePolicy.

Commit message

Screenshot

Testing

[x] Added unit tests
[x] Ran unit tests successfully
[ ] Added documentation for public APIs and/or Wiki

Code coverage
Total coverage: 95.13%

File
Coverage

TwilioVerifySDK/TwilioSecurity/Sources/Biometrics/BiometricError.swift
95.65%

TwilioVerifySDK/TwilioSecurity/Sources/Storage/AuthenticatedSecureStorage.swift
94.50%

Powered by Slather

  Generated by :no_entry_sign: Danger

Code coverage
Total coverage: 95.13%

File
Coverage

TwilioVerifySDK/TwilioSecurity/Sources/Biometrics/BiometricError.swift
95.65%

TwilioVerifySDK/TwilioSecurity/Sources/Storage/AuthenticatedSecureStorage.swift
94.50%

Powered by Slather

  Generated by :no_entry_sign: Danger


update image version to latest stable one

@morvencao I think a lot of these changes already landed in master, can you rebase so we can see whats changed + the tests pass?

@howardjohn Looks like all changes have already in master. I'm going to close this.


Make tf.image.resize gradient computation compatible with XLA compilation

Issue Type
Feature Request
Source
binary
Tensorflow Version
tf 2.11.0-dev20220831
Custom Code
No
Current Behaviour?
Currently, XLA compilation does not work for gradient computation of tf.image.resize, for example for the default method ResizeMethod.BILINEAR:

ResizeBilinearGrad with align_corners=False or half_pixel_centers=True is not yet implemented

Support for forward pass has recently been added: https://github.com/tensorflow/tensorflow/issues/46447
This makes it impossible to XLA compile models for training that use resizing, such as RetinaNet.
Standalone code to reproduce the issue
Colab to reproduce error

@sachinprasadhs I was able to replicate the issue on colab, please find the gist here.
Thank you!

Still waiting this.
A lot of semantic segmentation models use bilinear upsampling. Without gradient xla support we can't use jit_compile=True in model.compile(). I know about autoclustering, but in my experience it works worse then jit_compile (uses more memory -> requires smaller batch size)

Thanks for flagging this again.  Let me assess how we would
prioritize/schedule this and get back to you.
On Mon, Jun 19, 2023 at 11:35 PM Shkarupa Alex @.***>
wrote:

Still waiting this.
A lot of semantic segmentation models use bilinear upsampling. Without
gradient xla support we can't use jit_compile=True in model.compile(). I
know about autoclustering, but in my experience it works worse then
jit_compile (uses more memory -> requires smaller batch size)
—
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/57575#issuecomment-1598194418,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQLFIWSR65CN6GF2VBVUS53XMFAERANCNFSM6AAAAAAQB35X4E
.
You are receiving this because you were assigned.Message ID:
@.***>

We are working on a fix for this.  Delivery should be expected in early
July.
On Wed, Jun 21, 2023 at 4:17 PM Catherine Payne @.***> wrote:

Thanks for flagging this again.  Let me assess how we would
prioritize/schedule this and get back to you.
On Mon, Jun 19, 2023 at 11:35 PM Shkarupa Alex @.***>
wrote:

Still waiting this.
A lot of semantic segmentation models use bilinear upsampling. Without
gradient xla support we can't use jit_compile=True in model.compile(). I
know about autoclustering, but in my experience it works worse then
jit_compile (uses more memory -> requires smaller batch size)
—
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/57575#issuecomment-1598194418,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQLFIWSR65CN6GF2VBVUS53XMFAERANCNFSM6AAAAAAQB35X4E
.
You are receiving this because you were assigned.Message ID:
@.***>

Hi @prouast ,
This issue seems to be fixed by https://github.com/tensorflow/tensorflow/commit/58308810880c6746cfa726d1108ff8f9c14a2248 and here is the working Gist in Tf-Nightly.
Please verify and feel free to close the issue. Thanks!

@sachinprasadhs , bilinear interpolation grad now (tf 2.13.0) works in XLA.
But non nearest one (which has forward XLA implementation).
2023-07-06 00:31:29.455196: W tensorflow/core/framework/op_kernel.cc:1828] OP_REQUIRES failed at xla_ops.cc:503 : INVALID_ARGUMENT: Detected unsupported operations when trying to compile graph __inference_train_815[_XlaMustCompile=true,config_proto=10632308226793381189,executor_type=11160318154034397263] on XLA_GPU_JIT: ResizeNearestNeighborGrad (No registered 'ResizeNearestNeighborGrad' OpKernel for XLA_GPU_JIT devices compatible with node {{node gradient_tape/model_1/tf.image.resize_1/resize/ResizeNearestNeighborGrad}}){{node gradient_tape/model_1/tf.image.resize_1/resize/ResizeNearestNeighborGrad}}

You can reproduce error with code from colab link in first message. Just add method=tf.image.ResizeMethod.NEAREST_NEIGHBOR to tf.image.resize

@changm, Could you please check this issue, which is related to your recent commit. Thanks!

Do you mean @mikedelorimier as commit is the author? Or did you have a different commit I wrote @sachinprasadhs ?

Do you mean @mikedelorimier as commit is the author? Or did you have a different commit I wrote @sachinprasadhs ?

Sorry my bad, that is the right commit and it was from @mikedelorimier . Thanks for correcting me.

layers.UpSampling2D(2,  interpolation='nearest') does not work with XLA in tf 2.12 :( . Has anyone tried with tf 2.13?? it would be so great to have this operation, specifically for generative models, This is a bottleneck in Tensorflow, it's so sad that we can't leverage XLA just because of this layer.

@milmor  did you try keras.layers.Resizing ?  it seems it works with XLA. Transpose conv also works

@kmkolasinski  layers.Resizing(64, 64, interpolation="nearest") not working with tf 2.13 :( so sad. Unfortunately with bilinear interpolation or transpose, it is not possible to build and replicate a lot of models.
Detected unsupported operations when trying to compile graph __inference_train_step_49273[_XlaMustCompile=true,config_proto=6001324581131673121,executor_type=11160318154034397263] on XLA_GPU_JIT: ResizeNearestNeighborGrad (No registered 'ResizeNearestNeighborGrad' OpKernel for XLA_GPU_JIT

@milmor  the problem is with the "nearest" interpolation, cannot you use "linear" ? which works

@kmkolasinski No :( there are some results and behaviors that can only be achieved with nearest interpolation.

Any chance to fix this finally?


ci(yaml): references to new builder image

changed the old hash with new hash of latest ockam-builder image
ref: #3702

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository.

@Dark-Knight11 sorry this close is accidental. Github has a bug where they close the PR if the you push to the fork PR branch and it the same name as the PR target branch - develop
I thought they had fixed this https://github.blog/changelog/2022-10-12-reverted-recent-change-that-caused-some-pull-requests-to-be-incorrectly-marked-as-merged/
I'm trying a fix.

@Dark-Knight11 need a little help from you:
Your commit is saved in this branch https://github.com/build-trust/ockam/tree/3705
I can just merge it. However if you're participating in hacktoberfest, I want to make sure you get credit for merging a PR. So:
If you're NOT participating in hacktoberfest:

this is simple I can merge the contribution.

If you're participating in hacktoberfest

we either need to reopen this PR, which I can't but I thin you might be able to - try it.
or you will have to create a new PR with your changes from this branch https://github.com/build-trust/ockam/tree/3705

Sorry about the confusion, let me know if you have questions.

I realized I can ensure Hacktoberfest credit but adding the accepted label to @Dark-Knight11's contributors PR.
Preparing to land @Dark-Knight11's changes in https://github.com/build-trust/ockam/pull/3719

Thanks a lot ❤


Use react-is instead of typeof on getTag

Fixes #221

Yup. It'll go out with v7
On Sat, Oct 20, 2018, 12:03 PM Haz<EMAIL_ADDRESS>wrote:

@diegohaz commented on this pull request.
In package.json
https://github.com/probablyup/markdown-to-jsx/pull/222#discussion_r226833250
:

@@ -63,6 +63,7 @@
},
"dependencies": {
"prop-types": "^15.5.10",

"react-is": "^16.5.2",

Sure. But it would be a breaking change, wouldn't it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/probablyup/markdown-to-jsx/pull/222#discussion_r226833250,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiy1jLYcLUGRjJazbfjB3C16AFxGrQEks5um1dEgaJpZM4XxwP3
.

I ended up fixing this a different way that doesn't need a major version bump :) 7258f196fd91e3bfab4df9dd948c8451f2e63990


added a new renderer which uses Datatables from datatables.net

had to recreate this pull request due to a weird error in github

so anything required from my side at this point or whats the status?

anything required here from my side?


Update Bitcoin Developer Guide url

current link is ending up on a 404.

just saw https://github.com/zig-bitcoin/.github/pull/1. closing this one


Sentiment went wrong

Some words like 'รัก', 'ชอบ' return with 'neg'.

Sentiment Analyzer based on thai2vec https://colab.research.google.com/drive/1ZZHAZhk15cHOeITVshhpcT9EYEiLbAyc


"Player" prefab issue after upgrading to v2.4.5

Hi there,
After upgrading* to the latest SteamVR plugin (2.4.5) whenever I use the player prefab, at runtime, the SteamVRObjects go automatically off and the WASD menu appears on the screen, while "Virtual Reality Supported" is activated.
Only by manually activating the SteamVRObjects in play mode, I manage to have VR on.
I didn't have this problem with a previous version of SteamVR.
I am using Unity 2019.2.0f1.
Any idea how to fix this?
*As instructed, I deleted the SteamVR folder before upgrading to the new version.

Are there any errors in unity when this happens?

The warnings above this seem to indicate that SteamVR is not being recognized. Are you on the latest version of the SteamVR client?

If for some reason, I cannot upgrade to latest version of SteamVR client, is there any way of understanding which version of plugin to use for which version of client?
(I also have the same problem on trying the Player prefab. I get IVR_ errors. My camera is working but controllers are not getting displayed even in the CameraRig prefab)

In the latest versions of the plugin we started appending the sdk version to the plugin version. So 2.4.5 (1.17.15) means you need at least SteamVR 1.7.15 for the plugin to work.

yes, I saw that. My problem is that I cannot upgrade SteamVR version. Is there some way to figure out compatible SteamVR version for an old release of plugin? I would try that old release of the plugin. Also, is there some way to fetch the plugin version information from the package contents?

Unfortunately not for these older versions. If you tell me what version of SteamVR you're targeting I can probably tell you what version of the plugin you'd need.
What is your scenario in which you can't upgrade SteamVR?

The warnings above this seem to indicate that SteamVR is not being recognized. Are you on the latest version of the SteamVR client?

Totally right, I was not... Working now, thank you!


Allow theme and lexer for RST and Markdown printing

As it stands currently, rich-cli prints the rst/markdown document without considering the lexer or theme argument
Markdown: https://github.com/Textualize/rich-cli/blob/main/src/rich_cli/main.py#L564
RST: https://github.com/Textualize/rich-cli/blob/main/src/rich_cli/main.py#L570
What I suggest is to get the --theme argument and pass it to the code_theme keyword argument of the Markdown and RestructuredText class, and optionally the --lexer argument to the default_lexer parameter of the RestructuredText class
I may open a PR later if @willmcgugan is intrested

Makes sense! 👍

PR coming :)


Use a namespace

Hi guys,
It would be very nice that you bracket all your class in a namespace Snowplow because it brings me a lot of collisions with my own classes in my code.
Thanks!

That's an excellent point, feel free to open a pull request :+1:

Working on prototype right now but will do when I'll have more time :)


No release notes or documentation for v3.20.0 release

The release notes link in the v3.20.0 release are returning a 404 and on further inspection of the docs site it looks like the docs for v3.20.0 are completely missing with the latest version being reported as v3.19.1.

This looks like it's been resolved.


release_unlocked_beta doesn't work when an install key is specified

Describe the bug
When I use the "cci flow run release_unlocked_beta --org dev" command, and specify an install key using the install_key yaml option for the create_package_version task, the package version creates, but later, it fails when it tries to query the SubscriberPackageVersion object. This error prevents the rest of the release_unlocked_beta from running
Error Details
Error: Malformed request
https://neocol.my.salesforce.com/services/data/v52.0/tooling/query/?q=SELECT+Dependencies+FROM+SubscriberPackageVersion+WHERE+Id%3
D%2704t8W000003JjVhQAK%27. Response content: [{'message': 'Please provide installationkey when querying against
SubscriberPackageVersion that is protected by installationkey', 'errorCode': 'INSTALL_KEY_REQUIRED'}]
[Success]: Package creation successful
[05/02/23 17:05:50] Exception in task create_package_version
Reproduction steps

In the cumulusci.yml file, override the install_key option for create_package_version to some value
Run cci flow run release_unlocked_beta --org dev
The package version will create, but it will fail when the task executes a query against the SubscriberPackageVersion object

Your CumulusCI and Python versions
CumulusCI version: 3.75.1 (/Users/kollu/.local/bin/cci)
Python version: 3.11.1 (/Users/kollu/.local/pipx/venvs/cumulusci/bin/python)
Operating System
Mac
Windows environment
No response
CumulusCI installation method
None
Error Gist
No response
Additional information
I was able to fix the issue locally by copying the create_package_version.py script from the cumulusci repo, and change the query as follows
install_key = self.options.get('install_key')
query = f"SELECT Dependencies FROM SubscriberPackageVersion WHERE Id = '{package2_version['SubscriberPackageVersionId']}'"
if install_key:
    query += f" AND InstallationKey = '{install_key}'"

Can you make a similar change to your repo so that you pass over the installation key if provided?

Looks like this is an issue with release_unlocked_production as well:
kollu@Krishnas-MacBook-Pro Solution_AsyncActionFramework % cci flow run release_unlocked_production --org dev
[05/03/23 09:21:05] ============================================================
Initializing flow: FlowCoordinator (release_unlocked_production)
Promote the latest beta 2GP unlocked package version and create a new release in
GitHub
============================================================
                Verifying and refreshing credentials for the specified org: dev.
                Getting org info from Salesforce CLI for<EMAIL_ADDRESS>

[05/03/23 09:21:16] Org info updated, writing to keychain
------------------------------------------------------------
Organization:
Username<EMAIL_ADDRESS>Org Id: 00DDR000000rRSh
Instance: CS251
------------------------------------------------------------
                ------------------------------------------------------------
                Steps:
                Description: Promote the latest beta 2GP unlocked package version and create a
                new release in GitHub

                Flow Steps
                1) task: promote_package_version [from current folder]
                2) task: github_release
                3) task: github_release_notes
                ------------------------------------------------------------

                Starting execution
                ============================================================

                ------------------------------------------------------------
                Running task: promote_package_version
                ------------------------------------------------------------

                Options:
                Getting org info from Salesforce CLI for NeocolDevHub

[05/03/23 09:21:18] Beginning task: PromotePackageVersion
                No version_id specified. Automatically resolving to latest available Beta
                version.

[05/03/23 09:21:20] Resolved to version: 04t8W000003JjWpQAK
[05/03/23 09:21:21] Exception in task promote_package_version
Error: Malformed request
https://neocol.my.salesforce.com/services/data/v55.0/tooling/query/?q=SELECT+Id%2C+Dependencies%2C+R
eleaseState%2C+SubscriberPackageId+FROM+SubscriberPackageVersion+WHERE+Id%3D%2704t8W000003JjWpQAK%27
. Response content: [{'message': 'Please provide installationkey when querying against
SubscriberPackageVersion that is protected by installationkey', 'errorCode':
'INSTALL_KEY_REQUIRED'}]

Just hit this today. Seems like CumulusCI effectively doesn't support install keys as only 1-2 tasks can actually work with it.


Research the near-social-bridge approach

Problem
Currently, we are not able to use npm packages like css libraries and third party react compoents in near social viewer. The event handler also has some limitations that prevent us from implementing a better search bar experience, see problem 1 in this comment: https://github.com/near/neardevhub-widgets/pull/85#issuecomment-1501391631.
User Story
As a developer, I want to use npm packages and reuse the react ecosystem's tooling.
Acceptance Criteria

Research https://github.com/wpdas/near-social-bridge, which implements a mechanism to create normal ReactJS App and inject it in a controlled way into a Widget on Near Social.
Experiment to ensure:

we can use npm packages, such as tailwindcss and nextjs
we can use the full apis of react-bootstrap-typeahead that was not available in near social widget. For example, feature in this comment blocked by this: https://github.com/near/neardevhub-widgets/issues/18#issuecomment-1510604454
above search bar problem can be solved by either use a form with submit button, or <input> with both onKeyDown and onChange event handlers
test whether we can access SocialDB / transaction committing functionality from inside near-social-bridge

Also figure out an estimation of cost (performance, effort) to migrate entire neardevhub-widgets to a standard react app

If everything goes well, scope after this ticket:

Re-architect the neardevhub-widgets to be standard react app, setup with standard tooling and common configuration
Inject it to BOS, make sure everything still works
Makes it run as a React App locally.
improve the search bar typing experience.
clean up and configure styles with proper css libraries and css files, adjust styles that more precisely follows the @Ori's design.
Reuse the react-bootstrap-typeahead or some similar library to address https://github.com/near/neardevhub-widgets/issues/18#issuecomment-1510604454

I just want to say that such an approach to components defeats the purpose of BOS as it would just store JS blobs that are not editable, but I see the benefits. I don't see an alternative solution to the limitations we face with BOS VM today.

Hi @ailisp thanks so much for creating this. Can you please add a problem statement and acceptance criteria to this? What else do we need to move this from triage to the backlog?

we can use npm packages, such as tailwindcss and nextjs

Speaking of nextjs, I would insist not to go with SSR solutions, since it almost kills decentralization; I think we should rather use PWA approach along with Preact, and web4 as a hosting solution

Summary for the recent discussions within the DevHub team
Topic: using near-social-bridge as an application entry point and BOS functionalities provider, and web4 as the deployment solution
Pros

This approach solves any issues caused by limitations of BOS component framework.
It’s much easier to deploy and inspect feature previews.
The opportunity to drastically improve DX.
We’re not obliged to keep the whole codebase outside SocialDB, the proposed solution is actually flexible: it allows balancing between the two approaches depending on complexity of different parts of the system. Plus, near-social-bridge acts as a provider pattern, which means we can utilize any APIs available to BOS components.
It’s possible to bring positive impact to BOS ecosystem, since we can standardize the resulting architecture over time.

Cons

This approach makes it harder to discover and reuse parts of project codebase for less experienced in frontend development users, since it’s not enough to just press the “fork” button on gateway.

💡 Addressing security concerns:
near-social-vm was created as a sandbox solution with the goal to restrict the access to LocalStorage and Cookies. But most of the modern browsers already have the sandbox – it’s called WebAssembly. Moreover, WebAssembly allows using more than just one language and its VM unlocks near-native performance. It’s also worth noticing that WebAssembly is a widely acknowledged open standard curated by a huge community, with W3C in its core.

Update: now the migration to this approach makes even more sense, as BOS moving towards embracing native JS, and we need to improve quality and Cycle Time metrics.

@carina-akaia I support this idea of exploring near-social-bridge as we've talked about this in length, but I see it more as an application wrapper and should be coupled with near-social-vm being installed in the bridged application, in order to retain composability.
What specific features are you trying to achieve by using near-social-bridge? This is an important consideration, as well.
I would suggest refactoring DevHub into a more typical, native BOS application before embarking on this. I would not group the limitations of BOS with the difficulties of developing DevHub -- I think we can draw inspiration from other BOS applications for how to make the development experience easier. Then we can use the near social bridge to provide specific external libraries.

@elliotBraem please read this document, it should make the topic more clear


WebP shrink-on-load rounding error produces "extract_area: bad extract area"

Appears there is some sort of rounding error going on. As I validated the inputs and found that if I change the top position from 1 to 0, it works.
Code to reproduce (sharp 0.15.0):
var sharp = require('sharp');

var image = sharp('./test/files/bad-crop.jpg');

image
  .toFormat('webp') // if i don't do this step, it won't fail
  .toBuffer(function(err, outputBuffer, info) {
    console.log('info:', info); // reports 1080x607
    sharp(outputBuffer)
     .ignoreAspectRatio()
     .resize(233, 131)
     .extract({ top: 1, left: 0, width: 233, height: 130 }) // notice, height 130 + top of 1 = height of 131 - VALID
     .toFormat('jpeg')
     .toFile('result.jpg')
     ;

  });

Results in:
Unhandled rejection Error: extract_area: bad extract area

    at Error (native)

It only happens with this image: https://img1.wsimg.com/isteam/stock/5518eebf9a5d704c916de1acd4fe355e2c14463b39e4852697e1ec62859b5f5a?download

Hi Aaron, v0.15.0 had a small rounding error fixed as part of #452. Are you able to test with v0.15.1?

Now I get:
Unhandled rejection Error: enum 'VipsOperationBoolean' has no member 'null', should be one of: and, or, eor, lshift, rshift
enum 'VipsOperationBoolean' has no member 'null', should be one of: and, or, eor, lshift, rshift
extract_area: bad extract area

    at Error (native)

Thanks for confirming this fails with v0.15.1 also (PR #511 on master should have fixed the contents of the error message). I'll make time to investigate further over the next couple of days.

I've created https://github.com/jcupitt/libvips/pull/489 for this.

Commit a5bd68e recalculates scaling factors after any use of shrink-on-load, as discussed at https://github.com/jcupitt/libvips/pull/489

Seems this bug is impacting more images than I thought. Any idea when you think this patch would be made available? Thanks @lovell !

@asilvas This will be in v0.16.0, which will ship with libvips v8.3.3 (v8.3.2 fixes a buffer overflow but introduces a performance regression - see https://github.com/jcupitt/libvips/blob/master/ChangeLog#L36-L42).

v0.16.0 is now available via npm.


Dart's element.text is up to 40x slower than the javascript equivalent

Dart VM version: 2.1.0 (Tue Nov 13 18:22:02 2018 +0100) on "windows_x64"
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.17763 N/A Build 17763
Browser: Google Chrome 71.0.3578.98 (Official Build) (64-bit)
Compiled with Dart Dev Compiler
(Compiling with dart2js+optimizations don't help)

Using these 'agressive' performance tests, it looks like this dart line is up to 40x slower than this javascript line.
For reference, the dart line takes up to 10 seconds on my device, while the javascript line is around 225ms.
Attached is a profile of the execution of the script as well as the profiler.
dart.zip
(Issue discovered thanks to @lukepighetti and @GregorySech)

As a note, this problem does not exist on Safari. It does exist on Chrome. Both on macOS.

This is a surprising result, especially that it occurs on Chrome and not Safari - can you double-check?
The profile in the zip file is for the development compiler (unoptimized).
e..text = stuff (using the cascade .. operator) might be slightly different to e.text = stuff when unoptimized that context, but not 40x different.
There should not be much difference when optimized.  Node.text corresponds directly to Node.textContent, and if you use dart2js+optimizations, the generated code should contain something like this.e.textContent = ....
Node that Dart's % operator is modulo, and not remainder like JavaScript's %.
For an apples-to-apples comparison replace i % 2 with i.remainder(2).

Hi there, apologies for all the screenshots, but I think it is appropriate.
Chrome Version 71.0.3578.98 (Official Build) (64-bit)

Safari Version 12.0.2 (136<IP_ADDRESS>.4)


IsEquivalentTo uses strict ordering

It appears that IsEquivalentTo uses strict ordering, with no way to turn it off. The following test succeeds:
    [Test]
    public async Task Test()
    {
        List<int> list1 = [1, 2, 3];
        List<int> list2 = [1, 2, 3];

        await Assert.That(list1).IsEquivalentTo(list2); // succeeds
    }

but the following test fails:
    [Test]
    public async Task Test()
    {
        List<int> list1 = [1, 2, 3];
        List<int> list2 = [2, 3, 1];

        await Assert.That(list1).IsEquivalentTo(list2); // fails
    }

FluentAssertions uses non-strict ordering by default when comparing two collections for equivalency. I had expected that TUnit would follow suit. Is there a way that strict ordering can at least be turned off?

Not currently. I could look at adding an overload though

Thanks, that would be useful. I have a collection of DTOs where the order of items in the collection is not important. I just want to assert that the collection contains the expected items.

As a workaround currently you could order both sides of the equivalent to

Thanks, I'll do that for the time being.
On Tue, 19 Nov 2024, 23:16 Tom Longhurst, @.***> wrote:

As a workaround currently you could order both sides of the equivalent to
—
Reply to this email directly, view it on GitHub
https://github.com/thomhurst/TUnit/issues/1257#issuecomment-2486944643,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJYYHTYZAWA45OULGUIED2BPBDLAVCNFSM6AAAAABSDHLQRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWHE2DINRUGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Should be fixed in 0.3.43


project offline TwinCAT demo add license TF6250  TC3 Modbus-TCP

Hello @benhar-dev,
The license TF6250  TC3 Modbus-TCP needs to be added to the project,
correct it...
with this and following the readme.md everything ok works correctly

I'm pleased you have it working.  Just to confirm, this is step 5 of Windows 10, or step 6 of Windows CE.

I'm pleased you have it working. Just to confirm, this is step 5 of Windows 10, or step 6 of Windows CE.

step5 of windows 10
The project does not have the license, if it is clicked by default better, then you don't have to worry about adding it...

step 5 now has a picture 👍


Consider adding "Overview" page to the documentation

Currently "Documentation" button on the main page redirects directly to https://tinkerbell.org/components/. Perhaps it would be nice to have some kind of overview page of what you can find in there, how to contribute etc.

This was closed when we added the /documentation page


Fails to run on current Godot 4 Build

Parser Error: Identifier "BUTTON_LEFT" not declared in the current scope. (Line 25, player.gd).
2bd89ac is the current pull of master that I tested it against.

Sorry what's the work around here if I want to detect button_left is clicked?

Sorry what's the work around here if I want to detect button_left is clicked?

BUTTON_LEFT is now MOUSE_BUTTON_LEFT.
Tip: Use Search Help in the top-right corner of the script editor to find this in the future :slightly_smiling_face:

Ah cheers! Sorry I usually use VS Code and I literally googled for fifteen minutes and checked the docs this way and found nothing.

Fixed by https://github.com/godot-extended-libraries/godot-interpolated-camera3d-demo/commit/6b7179d058975348e55f55f7caccad76b84c69f3.


DevOps server 2019 does not support variable groups

Currently, it is possible to select server 2019 and yet the documentation does not mention that the server does not support YAML variable groups ... the server will throw this error :

this is how i tried to use the declared variable group :

--> the documentation should be fixed

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

ID: 4827aa99-ae62-bd63-6f2f-a87a4065ed27
Version Independent ID: c9e461ee-7f42-3503-9460-18fa3a807bbb
Content: Variable groups for Azure Pipelines and TFS - Azure Pipelines
Content Source: docs/pipelines/library/variable-groups.md
Product: devops
Technology: devops-cicd-library
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

Similar issue found under https://github.com/MicrosoftDocs/azure-devops-docs/issues/5652.