Feature: Derive supported locales from the path

Thoughts on reading the filenames in the path to dynamically determine what the supported locales are?

@codegrue Sounds good 👍


Allow actors to control log sequence number for replay after loading a snapshot

We have a use-case in which we want to speed up recovery and minimize snapshot size (currently it is around 700mb, its size being determined by the days of transaction history being kept in memory).
To minimize the snapshot size and reduce the replay duration the actor memorizes before which point in time (= log sequence number) historical data "can be forgotten". The log sequence number is therefore persisted as (part of) its snapshot. The "forgotten data" does therefore not need to be replayed during recovery, reducing replay/recovery (down)time.

Thanks for the pull request @danbim. Replaying from a custom position is definitely a missing feature in Eventuate and should be added. However, I think it should not be coupled to snapshot loading for two reasons:

it doesn't allow replay from a custom position when there's no snapshot for that actor
it may break consistent recovery of actor state when the replay position is not snapshot.metadata.sequenceNr + 1L

I want to propose the following alternative implementation for EventsourcedView (which is what EventsourcedWriter already implements):

read a custom start sequence number from somewhere. This can be a custom data source, a constructor argument or whatever.
if a custom start sequence number could be read (Some(snr)), start event replay from snr, otherwise (None) start the default snapshot loading procedure. If no snapshot exists, start replay from sequence number 1L, otherwise start replay from snapshot.metadata.sequenceNr + 1L.

This would solve the issues described above and allows to implement EventsourcedWriter in terms of EventsourcedView. If you additionally need to initialize actor state with a custom value, you can do that via the actor's constructor.
WDYT?

Sounds pretty good to me 👍 AFAICS. I'll try to update the PR soon

@krasserm I've been trying to implement what you suggested (see updated PR) but I'm not sure how to implement EventsourcedWriter in terms of EventsourcedView. EventsourcedWriter is type-parameterized for the type of the read operation while EventsourcedView is not.
I'm gonna do some thinking / reading on this. Meanwhile, maybe you have a hint for me? :)

Had an attempt at implementing EventsourcedWriter in terms of EventsourcedView. However, the implementation doesn't really feel "elegant" to me yet. WDYT?

A thinking a while, I propose to follow this approach. It's much easier than my initial implementation proposal, still has all its the advantages. Not documented/tested yet but I hope the idea is clear. Thoughts?

Looks similar to mine with the one difference: in your proposal the "calculation" of the replaySequenceNr is a synchronous process.
My assumption was that typically an EventsourcedView would have to retrieve the replaySequenceNr from some kind of storage or other (remote) service and would therefore require to do so asynchronously, thus the Future return type (which might also fail, obviously).
Do you think my assumption is wrong?

Please see the comments in https://github.com/RBMHTechnology/eventuate/issues/302

Aah! I didn't see that discussion yet. Let's continue over there...

LGTM, thanks a lot! I'll merge after the API doc has been added.


CircleCI: fuzz and e2e test failed

cannon-fuzz, op-e2e-fuzz, op-e2e-HTTP-tests, op-e2e-action-tests, op-e2e-fault-proof-tests and the final bedrock-go-tests are failed
Also need to check the following action status when our credits are available:

check-generated-mocks-op-node
check-generated-mocks-op-service
cannon-go-lint-and-test
cannon-build-test-vectors
todo-issues
shellcheck/check

The fuzz tests are fixed by installing Python on AX101.
The e2e tests disappeared or were renamed after the latest merge with upstream.
Now all the jobs mentioned in this issue pass, except one test in op-e2e-HTTP-tests that is moved to go-tests, and is now tracked by https://github.com/ethstorage/optimism/issues/136


Removal of unused CSS

Description

The only search result corresponding to the id greenbanner is in the style.css file.
There is no HTML div with id greenbanner corresponding to it.

Therefore, the following piece of code is redundant:

Reproduction

Navigate to https://github.com/creativecommons/cc-resource-archive/blob/main/docs/style.css

Lines 114-118 form the redundant piece of code.

Expectation

Removal of unused CSS
Additional Context
I have tried removing the piece of code locally and confirmed to the best of knowledge that it does not affect the site in any particular way.
Resolution

[x] I would be interested in resolving this bug.

To add to my point

Here, the image is as shown in the picture below:

Therefore, the green color of the CC logo comes from the image itself and has no relation with the id greenbanner.

I want to work on this issue.

@Anju3750 The issue hasn't yet been approved by the maintainers so no one can work on it at the moment. Also, I have already mentioned that I would like to resolve the issue while raising it. So I suggest that you find another issue.

@justaskulkarni Nice find, please go ahead!


Fix pip install in python based action step

Changes

Fix pip install in python based action step

Relate to:
https://github.com/knative/infra/issues/530
/cc @upodroid @skonto @cardil

/lgtm
/approve
/hold for others

/hold cancel
/override "Lint / style / suggester / yaml (pull_request)"

/override "style / suggester / yaml"


XCode8 + Cocoapods 1.1.0.rc.2

Hi there,
I'm having trouble building our project after upgrading to XCode8 and Cocoapods 1.1.0.rc.2. Our project is objective-c based and everything was working fine until today. Basically I'm seeing 76 errors in the Pod when it tries to build it.
We are currently importing OAuthSwift using @import OAuthSwift statement. I've tried to switch that to #import "OAuthSwift-swift.h" but there issues are still there. Kind of makes sense as it isn't actually able to build the pod.
A lot of the issues appear to be related to syntax error which leads me to believe it is something to do with Swift 3 or 2.3 updates. I'm not up on Swift yet but an example error is "Expected 'let' in conditional"
Our Podfile.lock file shows that we are using OAuthSwift 0.6.0
Any ideas?

please check if you really use 0.6.0 (28 Jul )
and not last commit of master branch (use swift 3 but not yet released)
I will create a swift 2.2 branch now

Hi @phimage
My Podfile only specifies the pod nae 'OAuthSwift' so I can only assume that it is the commit specified in the pod repository at Cocoapods.
pod 'OAuthSwift'

I'm not sure a 2.2 branch helps. XCode 8 expect Swift 2.3 or Swift 3. I saw that there were 2.3 and 3.0 branches in your repository after creating this issue so I was going to update my Podfile to point to one of those and try again. I assume Pods can reference a repo/branch instead of a version

yes if you use XCode8 you must choose one branch
you can try swift 2.3 branch
or point to master by specifying the git link

Hi @phimage that seemed to sort it out. I pointed to the swift 3.0 branch
thanks

the swift 3.0 branch is just a "fast" and temporary xcode conversion, master branch have more commit but I don't know its status about compatibility with objective c (due to function renaming)

Hi @phimage ,
You seem to have deleted the swift3.0 branch but now I seem to be stuck again. If I point to the swift2.3 branch, the version reverts to 0.6 and I get a lot of compile errors. If I use master, I don't get any compile errors but the authorizeWithCallback:scope:state:params:headers:success:failure: method is not available or any similar method signatures
any ideas how to proceed?
thanks

The function has been renamed to follow Swift 3 rules see release note : authorize(withCall...
But I don't know the result using obj c.
Maybe a swift-version file is missing for Swift 2.3 branch. (I think cocoapod use this file to choose Swift version)

So any suggestions on how I can proceed?

I have checked the swift2.3 branch, there is the swift-version file
I create an obc project and add a podfile
    pod 'OAuthSwift', :git =>  'https://github.com/OAuthSwift/OAuthSwift.git',  :branch => 'swift2.3'

maybe try to clean derived data, builds folders
I will test with swift 3 branch now

as information it seems that swift3 branch doesn't expose some functions to objective c
SWIFT_CLASS("_TtC10OAuthSwift10OAuthSwift")
@interface OAuthSwift : NSObject
@property (nonatomic, strong) OAuthSwiftClient * _Nonnull client;
@property (nonatomic, strong) id <OAuthSwiftURLHandlerType> _Nonnull authorizeURLHandler;
+ (void)handleWithUrl:(NSURL * _Nonnull)url;
SWIFT_CLASS_PROPERTY(@property (nonatomic, class, readonly, strong) NSNotificationCenter * _Nonnull notificationCenter;)
+ (NSNotificationCenter * _Nonnull)notificationCenter;
SWIFT_CLASS_PROPERTY(@property (nonatomic, class, readonly, strong) NSOperationQueue * _Nonnull notificationQueue;)
+ (NSOperationQueue * _Nonnull)notificationQueue;
- (void)removeCallbackNotificationObserver;
- (void)cancel;
- (nonnull instancetype)init SWIFT_UNAVAILABLE;
@end

SWIFT_CLASS("_TtC10OAuthSwift11OAuth1Swift")
@interface OAuth1Swift : OAuthSwift
@property (nonatomic) BOOL allowMissingOAuthVerifier;
- (nonnull instancetype)initWithConsumerKey:(NSString * _Nonnull)consumerKey consumerSecret:(NSString * _Nonnull)consumerSecret requestTokenUrl:(NSString * _Nonnull)requestTokenUrl authorizeUrl:(NSString * _Nonnull)authorizeUrl accessTokenUrl:(NSString * _Nonnull)accessTokenUrl OBJC_DESIGNATED_INITIALIZER;
- (nullable instancetype)initWithParameters:(NSDictionary<NSString *, NSString *> * _Nonnull)parameters;
@property (nonatomic, readonly, copy) NSDictionary<NSString *, NSString *> * _Nonnull parameters;
@end

SWIFT_CLASS("_TtC10OAuthSwift11OAuth2Swift")
@interface OAuth2Swift : OAuthSwift
@property (nonatomic) BOOL accessTokenBasicAuthentification;
@property (nonatomic) BOOL allowMissingStateCheck;
- (nonnull instancetype)initWithConsumerKey:(NSString * _Nonnull)consumerKey consumerSecret:(NSString * _Nonnull)consumerSecret authorizeUrl:(NSString * _Nonnull)authorizeUrl accessTokenUrl:(NSString * _Nonnull)accessTokenUrl responseType:(NSString * _Nonnull)responseType;
- (nonnull instancetype)initWithConsumerKey:(NSString * _Nonnull)consumerKey consumerSecret:(NSString * _Nonnull)consumerSecret authorizeUrl:(NSString * _Nonnull)authorizeUrl accessTokenUrl:(NSString * _Nonnull)accessTokenUrl responseType:(NSString * _Nonnull)responseType contentType:(NSString * _Nonnull)contentType;
- (nonnull instancetype)initWithConsumerKey:(NSString * _Nonnull)consumerKey consumerSecret:(NSString * _Nonnull)consumerSecret authorizeUrl:(NSString * _Nonnull)authorizeUrl responseType:(NSString * _Nonnull)responseType OBJC_DESIGNATED_INITIALIZER;
- (nullable instancetype)initWithParameters:(NSDictionary<NSString *, NSString *> * _Nonnull)parameters;
@property (nonatomic, readonly, copy) NSDictionary<NSString *, NSString *> * _Nonnull parameters;
@end

it's a little weird...because there is no "@noobjc" annotation. but I understand why, I create two function with same signature for objective c
func authorize(withCallbackURL callbackURL: URL, success: @escaping TokenSuccessHandler, failure: FailureHandler?) -> OAuthSwiftRequestHandle? {

func authorize(withCallbackURL urlString: String, success: @escaping TokenSuccessHandler, failure: FailureHandler?) -> OAuthSwiftRequestHandle? {

maybe I will rename the second one  authorize(withCallbackURLString

I think that would solve it. Methods with same signature but different types are not allowed in a lot of languages. I'm surprised it's ok in swift. Can you create a branch and I'll try it tomorrow morning.. It's late here in Amsterdam :)

same time here in paris :p
swift3.0objc branch created, you can test it  ("Use legacy swift language version" => No in target build settings)

I'm still not getting any love. I can see you changed the signature but its still not picking it up. I think the bridging doesn't understand the authorize(withCallbackURL syntax
Any chance we can try an old syntax like authorizeWithCallbackURL. Maybe this is a method that just passes to the authorize(withCallbackURL method?
I've tried to use the 2.3 branch again and get a lot of errors in the library itself. I've taken a screenshot and put it up at https://drive.google.com/file/d/0B1JerioCGxaKRExjN3czN2wzanM/view?usp=sharing
It fails if I try to convert the 2.3 branch

If you use cocoapod you have this settings
In workspace created by cocoadpod you must have a "Pod" project (in Finder, under Yourproject/Pods/Pods.xcodeproj)
In this project you must have one target by framework imported, and OAuthSwift must be there
I find why the function is not shown. The failure handler contain typed OAuthSwiftError that cannot be converted to NSError
Without that, swift will ask me to add the @noobjc annotation because of the two functions authorize(withCallbackURL
I add an objc_authorize... function to test

I implement CustomNSError protocol but any change
I see an other issue with the return type OAuthSwiftRequestHandle(I will add an annotation @objc)
I  make a new swift3.0objc branch and test that

k. should I just hold off and wait for your go ahead?

So in swift3.0objc I add prefixed function with bridge_ (bridge_authorizeWithCallbackURL)
that take a string as URL
You can go with that, but you can use "client" functions... In Bridge.swift you must add to fix that all functions : "bridge_get", "bridge_post", etc... (I have no more time)
There is again a problem with "OAuthSwiftHTTPRequest.Method : String" that is not bridged to objc (need NSString maybe but I thinks that's a swift/objc bridging issue in compilator)

I've given it a try and we have LOVE!! :) Thanks for the getting this to work so quickly.
Not sure if I should close the ticket or if you intend to tidy things up so we can remove the swift3.0obj branch in the future

I will try to do better so let's open this issue
I don't want to maintain objc branch
I want to keep compatibility with objc but use swift with its full potential (ie. typed error)
so maybe

I will add some preprocessor macros (to force use of Error instead of OAuthSwiftError)
or add Bridge.swift in main branch (maybe optional with cocoapod subspec)

next version (1.1.0 in master branch), soon released
functions will be prefixed with objc_ instead of bridge
580c85feccaec3b924347fb28c1cad82911f8828

Thanks @phimage . I'll review and update the project


Create temporary backup log file

Hello
I use the application traccar with remote connection to a database.
Is it possible in a future upgrade to be able to create temporary backup log file when connection is lost with the database, and then sent when the connection is restored ?
Thank you

There is a script to recover data from log:
https://github.com/tananaev/traccar/blob/master/tools/recover.py


remove vavr from public make methods

Closes https://github.com/biscuit-auth/biscuit-java/issues/66

@divarvel @Geal

So the private version takes a java option, and two overloaded variants are exposed? why not.
If you're changing the public interface, something that would be beneficial would be to hide symbol tables.

So the private version takes a java option, and two overloaded variants are exposed? why not.
If you're changing the public interface, something that would be beneficial would be to hide symbol tables.

Good idea. I'll do it in another PR. Let's merge this.


Rotated text results in wrong Boundingbox

When individual characters are rotated, the boundingbox is calculated as if no rotation took place, yet the render is working correctly (see the png file which is generated from the attached svg (renamed to test.txt since github doesn't allow svg uploads)
The png was generated use the tool from the examples folder and resvg version 0.3.0.

test.txt

Interesting. It's definitely a bug. The bbox detection is a separate code, sadly. So it may work differently.

Done.
I don't plan to release a new version any time soon, so you have to use the master branch.
Note that text-decoration (underline, etc.) will also be ignored. I still don't know should it impact the bbox or not.


Update to 'upTime' validator field to include block uptime

Currently, validatorDetails response data includes upTime field which doesn't actually show uptime of a validator. Instead, it returns getOracleUptime, i.e. a relative amount of missed oracle blocks.
It would make more sense to return a number which indicates how many oracle votes as well as block commits the validator has missed.
This pull request updates upTime to include block uptime and oracle uptime in one number. E.g. if the block uptime is 0.8 and oracle uptime is 0.9 then upTime will be 0.72. If both are 1 then upTime remains 1.

How do you think of this? @terra-money/dev-releations

The combined metric is also misleading. We could provide both uptimes separately. They have different reward bands, and different implications. A combined metric could then be determined by whoever queries the oracle and block uptimes.
However, providing a combined metric as the only option on such a base level would be misleading.

@Jared-Warn I changed it to provide upTimeOracle and upTimeBlock separately. Is this preferable?

The 2 uptimes proposed are easy to understand, and add value for validators. This allows them to pinpoint operational issues with more accuracy. IE is the oracle malfunctioning, or is the whole machine down.
I say, let's do it.

Validator uptime calculation will be provided from another service. (api.terra.dev). Closing this issue.


Note Sharing

In the spirit of simple and database-less, the current plan is to generate temporary pre-signed URLs but this needs to be explored.

Great Idea!

might be worth looking at projects like markdownpastebin and rentry

Any progress on this? I'd really like to share notes publicly. Perhaps even a page showing all public notes would be great.

No progress as yet I'm afraid but it's still high up on my list. It's just a case of getting some time to work on it.
In the meantime, a somewhat clunky workaround might be to run a separate no-auth or read-only instance for the shared notes. Maybe you could use the same directory to store them but docker mount the individual files you want to share for the shared instance.

@dullage maybe create this as a feture-flag on ENV disable by default, if someone don't want just keep disabled.

any chance of getting this?

any chance of getting this?

There's certainly a high chance as I really want this feature myself. I'll try and find some time to finish off the work I started on it.


How to retain original image size?

@LukasStruppek is there any option to retain the original image size because when I run the attacks, the result is seems to  be a resized image?!?

Hey,
yes, there should be an option included in the code by calling a script using the option --optimize_original. This should optimize the image before resizing.
Best,
Lukas

@LukasStruppek That option is not included in adv1_collision_attack.py file

Oh, I see. We only implemented this option for adv2_evasion_attack.py. However, it should be easy to add, just remove the resizing option from the preprocessing step and instead add it before feeding the image to the model. Since resizing operations are differentiable in PyTorch, the optimization should still run as usual. Best way is have a look at the adv2_evasion_attack.py script and how it is implemented there.
Best,
Lukas

I added it like exactly you said but the resulting image kinda gives an opacity over top of image
https://gist.github.com/artyres1/6d0516d2ebc916c8ad84a742679f7534
This is the code..I use Mac M1 MPS engine..instead cuda..

What exactly do you mean by "an opacity over top of image"? You should make sure that the image is correctly saved in the end + that the updates are also correctly applied to the correct image tensor. Maybe check which tensor is optimized by the optimizer and use a debugger for localizing the problem. I currently do not have the capacity to implement this functionality into our code, I am sorry.


Ensure terraform provider passes properly formatted mac address to XO api

Hello,
First of all thank you for this great plugin !
I’m currently testing it and I have notice that the Mac Address format is important, where you should use colon : instead of dash -.
I believe this is a Terraform limitation with identifiers
Since Go doesn’t have any issue to parse any common type of Mac Address
Maybe good to mention it in the documentation.
This does work correctly.
data "xenorchestra_template" "template" {
    name_label = "windows_2012_r2_Galaxy_Template"
}

data "xenorchestra_network" "net" {
  name_label = "ETH"
}

resource "xenorchestra_vm" "bar" {
    memory_max =<PHONE_NUMBER>
    cpus  = 1
    name_label = "MyName"
    name_description = "Mydescription"
    template = data.xenorchestra_template.template.id
    network {
	  network_id = data.xenorchestra_network.net.id
    mac_address = "6E:84:EE:7B:33:25"
    }

    disk {
      sr_id = "c7e5cf80-2b3e-c0ed-6f1e-09f1417b7d24"
      name_label = "W2012Disk"
      size =<PHONE_NUMBER>0
    }
}

but this doesn’t work
data "xenorchestra_template" "template" {
    name_label = "windows_2012_r2_Galaxy_Template"
}

data "xenorchestra_network" "net" {
  name_label = "ETH"
}

resource "xenorchestra_vm" "bar" {
    memory_max =<PHONE_NUMBER>
    cpus  = 1
    name_label = "MyName"
    name_description = "Mydescription"
    template = data.xenorchestra_template.template.id
    network {
	  network_id = data.xenorchestra_network.net.id
    mac_address = "6E-84-EE-7B-33-25"
    }

    disk {
      sr_id = "c7e5cf80-2b3e-c0ed-6f1e-09f1417b7d24"
      name_label = "W2012Disk"
      size =<PHONE_NUMBER>0
    }
}

hope that help

This has nothing to do with the HCL language itself. The provider's validation allows for all possible mac address inputs but the XO api needs to a mac address with colons.
The provider needs to convert all mac addresses to use colons before making the request to XO. I found this from looking at the XO server's logs while creating a VM.
Jan 28 01:12:17 xoa xo-server[510]: 2021-01-28T06:12:17.182Z - xo:api - [WARN]<EMAIL_ADDRESS>| vm.create(...) [55s] =!> XapiError: MAC_INVALID(6E-84-EE-7B-33-25)

This has nothing to do with the HCL language itself. The provider's validation allows for all possible mac address inputs but the XO api needs to a mac address with colons.
The provider needs to convert all mac addresses to use colons before making the request to XO. I found this from looking at the XO server's logs while creating a VM.
Jan 28 01:12:17 xoa xo-server[510]: 2021-01-28T06:12:17.182Z - xo:api - [WARN]<EMAIL_ADDRESS>| vm.create(...) [55s] =!> XapiError: MAC_INVALID(6E-84-EE-7B-33-25)

@Vagrantin #115 should fix this problem. Thanks for highlighting this issue!

@Vagrantin #115 should fix this problem. Thanks for highlighting this issue!

Super thank you !
Once PR is done will test it and let you know.

Super thank you !
Once PR is done will test it and let you know.

This is available in v0.13.1


Vanilla DXVK doesn't work

In fact client.useVanillaDxvk doesn't even seem hooked anywhere inside the code.
[01:41:26.269] info:  Found user config file: C:\Program Files (x86)\Origin Games\Mass Effect 2\Binaries\.trex\bridge.conf
[01:41:26.270] info:  Effective configuration:
[01:41:26.270] info:    client.useVanillaDxvk = true
[01:41:26.270] info:    client.setExceptionHandler = true
[01:41:26.270] info:    server.useVanillaDxvk = true
[01:41:26.270] info:    client.overrideCustomWinHooks = True
[01:41:26.271] info:  ==================
[01:41:26.271] info:  NVIDIA RTX Remix Bridge Server
[01:41:26.271] info:  ==================
[01:41:26.271] info:  Version: remix-0.4.1+856260f4
[01:41:26.271] info:  Running in x64 mode!
[01:41:26.271] info:  Launched server with GUID d6042417-b57c-4eaa-9a69-a8b7038ca3ff
[01:41:26.272] info:  Server started up, waiting for connection from client...
[01:41:26.272] info:  Registering exit callback in case client exits unexpectedly.
[01:41:26.272] info:  Registering message channel for asynchronous message handling.
[01:41:26.272] info:  Initializing D3D9...
[01:41:26.273] info:  Message channel MessageChannelServer established.
[01:41:26.959] info:  D3D9 interface object creation succeeded!
[01:41:26.970] info:  Loaded D3D9 from C:\Program Files (x86)\Origin Games\Mass Effect 2\Binaries\.trex\d3d9.dll

I verified with procmon that no d3d9vk* query ever happens.

Still obviously a thing with remix-0.5.0+dac740ce
There's no d3d9vk_x86.dll anywhere in the sources.


add gene counting feature for direct RNA sequencing

https://github.com/a-slide/NanoCount
NanoCount estimates transcript abundance from ONT direct-RNA Sequencing reads mapped to a transcriptome. It uses an expectation-maximization approach like RSEM, Kallisto, salmon, etc to handle multi-mapping reads. The reads must be mapped to the transcript set using minimap2.

I sent you the gff file that you need for this test through email.

thanks!

PS: I would need fast5 files for testing.

Hi Luca,
You might have missed the email i sent. The path to the fast5 files is '/no_backup_isis/enovoa/data/ont/rt_cDNA/cDNAB120905_both_good' .
Let me know if you can access it.
Thanks.

Duplicate of https://github.com/biocorecrg/master_of_pores/issues/17


TimeZone: delegate to ICU on Windows

Unfortunately, Windows does not have full time zone information
available.  For many cases we can make do with the system information,
augmented with alternate names (the Olson-to-Windows conversion
database).  This papers over the inability to deserialize the full
information in the registry by falling back to ICU to get the
information for the DST time conversion.

Otherwise approved.

@swift-ci please test Linux platform


Bot Migration to Raspberry Pi

Feature Description
Rather than continue to use a system that will inevitably not fit our server's needs (50MB of space for data will fill up quickly) and use inefficient key-value stores for static data, I've decided to migrate to a Raspberry Pi.
Desired Solutions

[x] Get Raspberry Pi working w/ Desktop
[x] Connect VNC Viewer to Raspberry Pi
[ ] Get Necessary Software installed and working

[x] Git
[x] MySQL Workbench

[ ] Set up DB to contain all data from bot previously

[x] Python, including the following non-base packages (w/dependencies):

[x] discord
[x] d20

[x] Ensure Bot can run on the Raspberry Pi

Considered Alternatives
N/A
Additional context
N/A at this time, will be included as comments if need post-submission.

Chances are, code will need to be streamlined and made to work with MySQL rather than the repl database. Luckily the database.py file should help with streamlining most of that interaction fairly easily.

Everything is working as intended except for db-related functionality.
Going to be hashing out the db architecture in the hopes of finishing it tonight

Bot is working properly and sustained on the raspberry pi without issues. Closing this out.


2024-01-30 check formulas on E101

Formler på skilt E101: Er de riktige?

I've investigated all the Lua formulas on the JBTSA_MSS ERTMS ID board object type. They all seem correct, with the following exception:

Here there's a mismatch between is text and the code. Is the code supposed to be switched, as indicated in the image above?
@clfey Is the text correct or is the code correct (or neither)?

Should prbably be
Attachment and Attachment.code or ""
But I wonder why the formula was not in order, it is just a very small one.

f0a8e61bfa8a22607849621b61d66e2fb8f58041
Fixed above bug. In my opinion the E101 Lua formulas are now correct.


Codesmon/SetInternalServerErrorOnUnknownError

When handling an error, if there is no HTTP Status Code in the response (maybe there is no response as the call failed completely), set the Status to 500 to let the caller know that it failed.

Fixed in main repo by author


Added Revolution R Open 3.2.1

There was no Cask for Revolution R, so I added one.

Thank you for the contribution. It needed some fixes, so they were made in 85d8a587321f4a28226f2eab58bc1037084714f5. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

@Ngrd That's all I needed. Thanks


Impl Index for EnumSet

This is not possible. An EnumSet<T> does not contain actual values of T and cannot return a borrow to one without unjustifiably complex code. Furthermore, the Index operation will not be O(1) as it would generally be expected to be.

I misunderstood this as an issue, not a pull request in my previous comment, opps.
I'm not sure why you would need this API. [Index] is normally usually used for collections that contain objects, and EnumSet<T> contains neither Ts nor bools.

I made it for just syntax sugar but I agree with EnumSet don't contains bools
Can I close this pr?


🐛 BUG: remove init from list of commands when running npx wrangler

Which Cloudflare product(s) does this pertain to?
Wrangler core
What version(s) of the tool(s) are you using?
⛅ wrangler 3.51.2
What version of Node are you using?
No response
What operating system and version are you using?
mac
Describe the Bug
Observed behavior
running npx wrangler lists wrangler init command, which then tells you it's deprecated
Expected behavior
not list it
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response

npx wrangler generate displays the same message.
However, I without this message I would not have known that npm create cloudflare exists, and I would be lost not knowing how to start using Wrangler.

Came here with same problem, but different suggestion on how we solve it.
When I run npx wrangler@latest init from a directory without a wrangler.toml file — npm create cloudflare runs — this is what should happen!
brendan@N64W27QG5Q test % npx wrangler@latest init

 ⛅ wrangler 3.61.0
-------------------

Using npm as package manager.
▲ [WARNING] The `init` command is no longer supported. Please use `npm create<EMAIL_ADDRESS>instead.

  The `init` command will be removed in a future version.

Running `npm create<EMAIL_ADDRESS>
...but when I run this from a directory that has a wrangler.toml already, the old wrangler init runs:
brendan@N64W27QG5Q remix-d1 % npx wrangler init
 ⛅ wrangler 3.57.1 (update available 3.61.0)
-------------------------------------------------------
Using npm as package manager, as there is already a package-lock.json file.
▲ [WARNING] wrangler.toml already exists!

✔ Do you want to continue initializing this project? … yes
? Would you like to create a Worker at src/index.ts? › - Use arrow-keys. Return to submit.
    None
❯   Fetch handler
    Scheduled handler

...and if I run wrangler generate, in either scenario, ye ole wrangler init command runs:
brendan@N64W27QG5Q test % npx wrangler@latest generate

 ⛅ wrangler 3.61.0
-------------------

Using npm as package manager.
▲ [WARNING] The `init` command is no longer supported. Please use `npm create<EMAIL_ADDRESS>instead.

  The `init` command will be removed in a future version.

✨ Created wrangler.toml
✖ Would you like to use git to manage this Worker? … yes

What should we do about it?

In all cases, we should run npm create cloudflare@latest. There should never be a case where we run the old init command runs, regardless of where you run it from.
We should remove the deprecation message about wrangler init and wrangler generate. It's just noise. There are tons of projects floating out there that reference the command directly. We should make things clear and easy and simple for people coming from these paths. We already hide init and generate from Wrangler's list of commands, and in the docs.


Redirect to AWS by Default (unless customers are from Google)

Our current logic is to default to Google for traffic not from AWS.
We should update the logic to default to AWS if not Google.
This will directly address our top two priorities from our meeting last week.

-1 : GCP spend HAS to go down (So we stay within budget and make room for other things we need the $$'s for)
0 : AWS spend HAS to go up (If we don't use it, we will end up not getting more)

Our main logic for handling redirects is here:
https://github.com/kubernetes/registry.k8s.io/blob/main/cmd/archeio/app/handlers.go#L123-L131
		// check if client is known to be coming from an AWS region
		awsRegion, ipIsKnown := regionMapper.GetIP(clientIP)
		if !ipIsKnown {
			// no region match, redirect to main upstream registry
			redirectURL := upstreamRedirectURL(rc, rPath)
			klog.V(2).InfoS("redirecting blob request to upstream registry", "path", rPath, "redirect", redirectURL)
			http.Redirect(w, r, redirectURL, http.StatusTemporaryRedirect)
			return
		}

I'm suggesting the following or similar:
	// initialize map of clientIP to AWS region
	regionMapper := gcp.NewGCPRegionMapper()
       //... snip ...//
		// check if client is known to be coming from an GCP region
		gcpRegion, ipIsKnown := regionMapper.GetIP(clientIP) //
		if !ipIsKnown {
			// no region match at GCP, redirect to main upstream registry
			redirectURL := upstreamRedirectURL(rc, rPath)
			klog.V(2).InfoS("redirecting blob request to upstream registry", "path", rPath, "redirect", redirectURL)
			http.Redirect(w, r, redirectURL, http.StatusTemporaryRedirect)
			return
		}

We will need to create a net/cidrs/gcp similar to main/pkg/net/cidrs/aws
It should be nearly the same code, with minor changes to main/pkg/net/cidrs/aws/internal/ranges2go/genrawdata.sh
Swapping out the AWS ranges with GCP ranges:

https://ip-ranges.amazonaws.com/ip-ranges.json
https://www.gstatic.com/ipranges/cloud.json (from  https://cloud.google.com/compute/docs/faq#find_ip_range)

cc @BenTheElder @thockin @ameukam

SGTM on principle.

Yeah:

Doing this is an obvious next step now that we have a real budget from amazon. We've been discussing that since last year following the announcement in the SIG meeting and other forums.
Adding the GCP ranges is relatively easy, however matching them separately is inefficient, so we should refactor a bit.

The main detail that needs settling is how we handle routing non-AWS users to AWS.
@ameukam suggested perhaps we should just go ahead and switch to cloudfront.
Otherwise I think we should probably need to switch from IP => region to cloud run instance => region, and figure out and configure a reasonable mapping.

Are we switching layer serving to CloudFront, or https://registry.k8s.io/ itself? The first option is straightforward but doesn't cut the GCP bill.
To tell the truth, I'm not sure how the second option helps the GCP bill either.

Perhaps we're thinking of using AWS (and CloudFront) to serve the lot, and not use GCP at all?

The blobs are the vast majority of the bandwidth spend. The registry itself
just serves JSON and 302s.
On Mon, Jan 30, 2023, 7:33 AM Tim Bannister @.***>
wrote:

Perhaps we're thinking of using AWS (and CloudFront) to serve the lot, and
not use GCP at all?
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/registry.k8s.io/issues/143#issuecomment-1408836693,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKWAVCG6DZ4TGI2LL66WQ3WU7NLLANCNFSM6AAAAAAUKL5EU4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ameukam was suggesting migrating to cloudfront for layer serving instead of regionalizing to s3 ourselves.
We either have to do that or update how we regionalize to work with non-AWS users, as a prerequesite to "default layer serving to Amazon".
As Tim said, serving content blobs is the only expensive part.
The option to regionalize by assigning a default S3 bucket per cloud run region is potentially less work than spinning up cloudfront, depending on who's working on it. It doesn't require new infra but the mapping would take some thought.

Ah, right. Then we either:

serve direct from AWS for clients already inside AWS, and use a CloudFront distribution for the rest of the world (low-cost price class / backed by a cheap region)
serve everything through CloudFront
one of the above two options with a fallback to GCP in case S3 is offline

Serving directly from S3 for clients inside AWS has benefits (that mainly accrue to the client) - for example, they can use a gateway-type VPC endpoint for image pulls and avoid using the public internet. Switching away might merit a notification that people who relied on this property now cannot.

OK; I do think we should announce the change though.

one of the above two options with a fallback to GCP in case S3 is offline

We have to do this not just because S3 offline (seems unlikely anyhow) but the more common problem that async layer population hasn't happened yet. Synchronous promotion to AWS has not landed in the image promoter / release process.
This part is already implemented. https://github.com/kubernetes/registry.k8s.io/blob/main/cmd/archeio/docs/request-handling.md

serve everything through CloudFront

I think people here are conflating sticking cloudfront in front of the entire service, which I do not agree with and had not been suggested previously, as opposed to sticking cloudfront in front of the layer store, it doesn't make technical sense when registry.k8s.io itself is serving nothing* but redirects.
We should look at cloudfront for the layer hosting.

I amended https://github.com/kubernetes/registry.k8s.io/issues/143#issuecomment-1408979874 to clarify

Also, in the future we'll want to do different cost routing (say we start to also use fastly, or azure), which is easier to do if it's just updating the redirect logic.

/retitle Serve container image layers from AWS by default (make exception when clients are from Google)

Serving directly from S3 for clients inside AWS has benefits (that mainly accrue to the client) - for example, they can use a gateway-type VPC endpoint for image pulls and avoid using the public internet. Switching away might merit a notification that people who relied on this property now cannot.

That's an interesting point, though our stance so far has very much been that:

We don't have a mechanism to notify all users.
Users may not depend on any implementation details, only OCI compliance https://github.com/kubernetes/registry.k8s.io#stability is at the top of the README that https://registry.k8s.io redirects to and outlines this in more detail.
Due to 2) we don't need a mechanism to notify all users / we are understaffed and funded to manage this.

This sort of detail is what prevented us from redirecting k8s.gcr.io and bringing our costs down immediately, we cannot dig ourselves back into that hole.
If anything we should make "breaking" changes to those depending on implementation details more often (e.g. perhaps renaming the buckets) to underline the point that they're just implementation details and we will use whatever we can fund.

BTW https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/#why-isn-t-there-a-stable-list-of-domains-ips-why-can-t-i-restrict-image-pulls is a better link for “don't depend on any implementation details”.

PRs are ready, https://github.com/kubernetes/registry.k8s.io/pull/147 and https://github.com/kubernetes/k8s.io/pull/4739

https://github.com/kubernetes/k8s.io/pull/4741 promoted the image. last step updating prod.
this change is safe, because even if we misconfigured a default url we will detect the content as not available on AWS and fallback to upstream registry on AR. the runtime logic diff is pretty small, mostly of the diff is in refactoring the cloud IP management and updating the runtime deployment configs to map cloud run region to default s3 region (for clients where we cannot detect a known region based on IP).
will follow-up with a prod deployment PR shortly. sandbox is running smoothly.

https://github.com/kubernetes/k8s.io/pull/4742 this is deployed

AFAICT the simple per-cloud-run-region regionalizing approach is working well, based on logs etc.
For example pulling from the California Bay area, I am redirected to GCP us-west2 Artifact Registry (Los Angeles) and AWS us-west1 S3 bucket (N. California).
We can revisit cloudfront later, but I don't think we need to rush.
We might want to visit adding more S3 regions, notably South America where we have cloud run / artifact registry but no AWS presence https://github.com/kubernetes/k8s.io/pull/4739#discussion_r1100671677


Start refactoring of events

See commit for implementation details. Events are a somewhat easy target because the seperate parts are pretty self-contained.
Since we now have a somewhat recent version of v8 (\o/ finally), we can start refactoring our stuff really nicely with "real" private variables and we should also start to remove the level thing and get some proper prototype-chains in there, since that's currently severly lacking and/or just wrong.
The structure is just some initial draft which we'll probably have to improve incrementally. Comments?
(Since this is based on #1001, the same tests fail, however the refactor didn't break anything... yet.)

Done.
With Symbols we once again can't totally remove public properties since Symbol access apparently differs from property access in v8 and the vm module only forwards property access. However we can reduce all public properties to a single "empty" map.

the vm module only forwards property access.

AAAAARGH :( more vm bugs :( :( :(

@domenic Pls fix :p

We have another vm bug/incompat:
this in non-strict contexts when undefined, should refer to window. This is currently not the case for example in EventTarget (after removing use strict) and crashes the w3c tests since they require this behaviour in their test runner.

My interpretation of what's happening here is that the W3C tests use
addEventListener("error", ...);

in their global <script> context. The global object inside of <script> is window, i.e. the window proxy. The window proxy doesn't have a addEventListener method, but the vm module will fall back to the sandbox object (a Window instance), which does. When it calls Window.prototype.addEventListener, it does so with the window proxy as this, instead of the Window instance. Since the window proxy doesn't have any internal state---i.e., it doesn't have the __jsdom property---this fails.
This seems OK, in that I think it's how browsers work too. The question is, what do browsers do to make this work? I can think of a couple alternatives:

Add the private state to the window proxy.
Make private state transparently redirect so that when it tries to get it from the global proxy, it instead gets it from the window.

I will ask around on public-script-coord. I also might be missing something entirely.

Oh wait, I think I see the problem. addEventListener should reference the global, not the global proxy. Hmm..... that is not how the vm module behaves.

Hmm but why does window.addEventListener(...) work, but addEventListener fail?? Given that window is a window proxy?
Maybe there is a bug in vm here that does not correctly set the this of calls in the global scope?

Oh, I see. Yes.

Maybe there is a bug in vm here that does not correctly set the this of calls in the global scope?

is correct. It's always using undefined.

Looks like saucelabs is broke, but we have passing node tests \o/

Oh, our rewriting is buggy, need to fix that :(

There we go, also fixed.

Okay, the event target migration is done, I think.
There's a failing test in there, but I think since it's accessing private APIs the test is wrong; I'm not sure how to rewrite it to match public APIs or just remove it. @domenic?

I think we should not use symbols until we fix vm.
That test looks removable, yeah.

I'm actually going to implement my suggestions and then create a new PR with them :). No need to jump on this quite yet.


Overhaul Nix's error types

For many of Nix's consumers it be convenient to easily convert a Nix
error into a std::io::Error.  That's currently not possible because of
the InvalidPath, InvalidUtf8, and UnsupportedOperation types that have
no equivalent in std::io::Error.
However, very few of Nix's public APIs actually return those unusual
errors.  So a more useful API would be for Nix's standard error type to
implement Intostd::io::Error, and the few functions that must return
unusual errors like InvalidUtf8 should use bespoke error types.
This commit prototypes that approach by modifying just one function, for
now, to use the new error type.

bors r+


@vue/babel - dynamic import fail

Version
3.0.0-beta.2
Reproduction link
https://github.com/maxpou/gitvub/pull/43
Steps to reproduce

vue create test-dyn-import
pick vue-router, vuex, sass, babel, pwa, eslint, unit-jest
add new file users.json under test/unit

{
  "data": ["bob", "max"]
}

add the following test

  it('should import my file', async () => {
    const userFile = './users.json'
    const users = await import(userFile)
    console.log(users)
  })

run npm run test

What is expected?
test should be green and print something like this { data: [ 'bob', 'max' ] }
What is actually happening?
~/sites/lab/test-dyn-import(master*) » npm run test

><EMAIL_ADDRESS>test /home/maxence/sites/lab/test-dyn-import
> vue-cli-service test

 FAIL  tests/unit/HelloWorld.spec.js
  ● Test suite failed to run

    /home/maxence/sites/lab/test-dyn-import/tests/unit/HelloWorld.spec.js:35
                return import(userFile).then(function (someModule) {
                       ^^^^^^

    SyntaxError: Unexpected token import

      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:316:17)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.488s
Ran all test suites.
 ERROR  jest exited with code 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test: `vue-cli-service test`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/maxence/.npm/_logs/2018-03-02T17_51_40_312Z-debug.log

I'm trying to switch to the new file architecture for one of my side project (https://github.com/maxpou/gitvub).
I solved this issue with the past architecture by the following babelrc file
{
  "presets": [
    ["env", {
      "modules": false,
      "targets": {
        "browsers": ["> 1%", "last 2 versions", "not ie <= 8"]
      }
    }],
    "stage-2"
  ],
  "plugins": ["transform-runtime"],
  "env": {
    "test": {
      "presets": ["env", "stage-2"],
      "plugins": ["transform-es2015-modules-commonjs", "dynamic-import-node"]
    }
  }
}

Looks like we need to enable dynamic-import-node for test environments in the preset.

Thanks!
@yyx990803, I forget to say thank you for this new vue-cli. You definitely gonna make our life easier :+1:

The exact same error still happens with 3.0.0-beta.11.
Settings used:
Manually select features
---
Babel
Router
CSS Pre-processors
Linter / Formatter
Unit testing
---
LESS
---
ESLint + Prettier
---
Jest
---
config: In dedicated config files

The exact same error still happens with 3.0.0-beta.11.
Settings used:
Manually select features
---
Babel
Router
CSS Pre-processors
Linter / Formatter
Unit testing
---
LESS
---
ESLint + Prettier
---
Jest
---
config: In dedicated config files

@yyx990803 Would mind taking a look? Thanks ;)


JPA fetchCount() and group by not working

This is a bug resulting from this posting on Google Groups (see https://groups.google.com/forum/#!topic/querydsl/WH582YIY98I):
I found a strange problem with a rather complex group by query when it comes to counting the number of rows that will be returned for the query - the created HQL query contains a having clause (which is correct), but omits the group by clause (which is not correct and leads to an exception, stating that having was encountered without group by). I debugged the problem and found this code in JPQLSerializer.serialize():
    // group by
    if (!groupBy.isEmpty() && !forCountRow) {
        append(GROUP_BY).handle(COMMA, groupBy);
    }

    // having
    if (having != null) {
        append(HAVING).handle(having);
    }

My wish would be that a count query with group by + having would work, because I have a use case where I need exactly that. If that doesn't work out, then at least the having part should be omitted when fetchCount() is called.
Thanks in advance (for fixing this bug) and thanks for QueryDSL in general, which is truly awesome!

Any updates on this issue?

Have the same, didn't fixed it in 4.1.4

.groupBy().count() is trying to shove a null into a long.
workaround is using .groupBy(element).singleResult(element.count()) that returns Long and coalesce in code until the bug is fixed.

I'm also hitting this problem, using version 4.2.1. My query has multiple expressions in the groupBy() clause and singleResult() is no longer available in QueryDSL 4. Any ideas on how to apply the workaround above when doing .groupBy(element1, element2, ...)?

Also still running in to this unfortunately. Has anyone found a workaround?
(Other then having to use native JPA)

JPAQuery<Tuple> countQuery = factory.getCacFactory().select(
        qReceive.licenseId,
        qReceive.domain,
        qReceive.cycle,
        qReceive.subject,
        qReceive.tag
).distinct().from(qReceive);
...
long total = countQuery.fetchCount();

I found this might work when I want to get row count of groups.

Still raised same error in 4.2.1
@svenpanko point out exactly, so I removed all having expressions..
Even need it, change native sql temporarily.

Any progress in this?

Yes, we're going to deprecate/remove it entirely for JPA: https://github.com/querydsl/querydsl/pull/2605 . The computation will fall back to an implementation in memory, as it simply can not be done with plain JPA.


Changes in @only1chunts' new XLSX representation of MIxS

Note that these revert away from NCBI's structured comment names in several places, presumably to keep the SCN lengths under 20 characters.
See https://www.ncbi.nlm.nih.gov/biosample/docs/attributes/
Where does it say that the SCN's length must be less than N characters? (Ideally the source would be a computable file, not a narrative.)
Also: shouldn't we be consistent in the tokens composed together? See the keyword notes in XXX

see also

#50
#51
#53

GSC 6.1: air_particulate_matter_concentration GSC 6.1: MIXS:0000108 CH: air_PM_concen. NCBI: air_pm_concen
GSC 6.1: host_family_relation GSC 6.1: MIXS:0000872 CH: host_fam_rel NCBI: host_family_relationship (underspecified)
GSC 6.1: host_family_relationship GSC 6.1: MIXS:0000872 CH: host_fam_rel NCBI: host_family_relationship (underspecified)
GSC 6.1: host_infra_specific_name GSC 6.1 MIXS:0000253 CH: host_infra_spec_name NCBI: host_infra_specific_name (24 chars)
GSC 6.1: host_infra_specific_rank GSC 6.1 MIXS:0000254 CH: host_infra_spec_rank NCBI: host_infra_specific_rank ()
GSC 6.1: microbial_biomass_meth GSC 6.1: MIXS:0000339 CH: micro_biomass_meth NCBI: host_infra_specific_rank ()
GSC 6.1: non_mineral_nutr_regm MIXS:0000571 GSC 6.1: non_min_nutr_regm NCBI: non_mineral_nutr_regm ()
GSC 6.1: previous_land_use_meth GSC 6.1: MIXS:0000316 CH: prev_land_use_meth NCBI: previous_land_use_meth ()
GSC 6.1: samp_collec_device GSC 6.1: MIXS:0000002 CH: samp_collect_device NCBI: samp_collect_device
GSC 6.1: samp_collec_method GSC 6.1: MIXS:0001225 CH:samp_collect_method NCBI: samp_collect_method
GSC 6.1: single_cell_lysis_appr GSC 6.1: MIXS:0000076 CH: sc_lysis_approach NCBI: ???
GSC 6.1: single_cell_lysis_prot GSC 6.1: MIXS:0000054 CH: sc_lysis_method NCBI: ???

Incomplete salinity remodeling?

GSC 6.1: salinity_meth GSC 6.1: MIXS:0000341  GSC 6.1: salinity_meth Reference or method used in determining salinity
GSC 6.1: samp_salinity GSC 6.1: MIXS:0000109

salinity	salinity	The total concentration of all dissolved salts in a liquid or solid sample. While salinity can be measured by a complete chemical analysis, this method is difficult and time consuming. More often, it is instead derived from the conductivity measurement. This is known as practical salinity. These derivations compare the specific conductance of the sample to a salinity standard such as seawater.	measurement value	{float} {unit}	25 practical salinity unit	X	practical salinity unit, percentage	1	MIXS:0000183

I'm not entirely sure what all of this ticket means, but one part of it was about seeing the strucutred comment name length written down somewhere, I can answer that bit: Its from the INSDC feature table documentation here https://www.insdc.org/submitting-standards/feature-table/#3.1

3.1 Naming conventions
Feature table components, including feature keys, qualifiers, accession
numbers, database name abbreviations, and location operators, are all named
following the same conventions. Component names may be no more than 20
characters long  (Feature keys 15, Feature qualifiers 20) and must
contain at least one letter. The following characters are permitted to
occur in feature table component names:

Uppercase letters (A-Z)
Lowercase letters (a-z) Numbers (0-9)
Underscore (_)
Hyphen (-)
Single quotation mark or apostrophe (')
Asterisk (*)

I would like to review whether there are slots whose names must contain uppercase letters, like ...

The names for classes (checklists, environmental packages, extensions) should be PascalCase aka UpperCamelCase. I have just forced all of those already but we should review the consequences of that. The title can always match something historical and non-PascalCase.

I have tomorrow off, and I'm now about to log-off!


Ensure that connecting method is synchronized

When there are competing publisher threads, there is a chance that the
publisher has not been initialized when Hutch is registered as
connected.  This happens when connections are lazily created vs at application load (for example).
The following diagram should shed some light on the race condition:
        Thread 1                  Hutch                   Thread 2
        --------                  -------                 ---------
t1      Hutch.publish()  --->  connected? (FALSE)
                           |-> open_connection!
t2                             connected? (TRUE)  <--- Hutch.publish()
                               @broker.publish()   |-> NoMethodError (@publisher)
t3                         |-> declare_publisher!
        PUBLISHED        <-|   @broker.publish()

Wrapping the Hutch.connect call should resolve this issue.

Thank you.
There is one thing I'd like to point out. Every Hutch broker also uses at least one channel. Channels are not supposed to be shared between threads for many operations, in particular publishing. This PR does not address that, so application developers need to bring their own synchronization at least for Hutch.publish.

@michaelklishin I agree that the Hutch.publish calls should be synchronized since the callers might be sharing a channel across threads. I was going to open up a PR for that case after seeing feedback from this PR. Would you be open to that or would you rather leave the publish synchronization up to the application devs?

Synchronization introduced a 10-11% throughput drop (measured a few years ago when the same thing was considered Bunny), less so with Monitor than Mutex.
I'm not sure how many people actually publish concurrently with Hutch, although some may end up doing so without knowing it.

Ya, I figured the performance overhead would be something to consider in the library making this the default behavior. I'll stand down on the other PR.
Have a good one!


fix deoplete base source import

fixes the error after updating deoplete
[deoplete] Traceback (most recent call last):
  File "/Users/jay/.vim/plugged/deoplete.nvim/rplugin/python3/deoplete/child.py", line 103, in _add_source
    Source = import_plugin(path, 'source', 'Source')
  File "/Users/jay/.vim/plugged/deoplete.nvim/rplugin/python3/deoplete/util.py", line 69, in import_plugin
    spec.loader.exec_module(module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 205, in _call_with_frames_removed
  File "/Users/jay/.vim/plugged/vim-javacomplete2/rplugin/python3/deoplete/sources/javacomplete2.py", line 1, in <module>
    from .base import Base
SystemError: Parent module 'deoplete.source' not loaded, cannot perform relative import
Could not load source: /Users/jay/.vim/plugged/vim-javacomplete2/rplugin/python3/deoplete/sources/javacomplete2.py.  Use :messages / see
 above for error details.

Thank you.


ESP32 TWAI/CAN self reception not working (IDFGH-10458)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.0.2
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
Development Kit.
ESP32-WROOM-32
Power Supply used.
USB
What is the expected behavior?
After a successful twai_transmit of data to the Tx line connected directly to the Rx line the twai_receive should return ESP_OK and parse the frame into twai_message_t.
Attached image. Tx pin in yellow and Rx pin in magenta. Frame is correctly decoded by scope.

What is the actual behavior?
twai_receive times out
Steps to reproduce.

Connect CAN_TX_PIN to CAN_RX_PIN directly
Send TWAI frames with twai_transmit
Read TWAI frames with twai_receive
Check returned value of twai_receive

Debug Logs.
No response
More Information.
I started from the twai_self_test example and simplified it to the core which only involved removing the task and semaphore structure.
Source Code
#include <stdio.h>
#include <stdlib.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "esp_err.h"
#include "esp_log.h"
#include "driver/twai.h"
//Example Configurations
#define CAN_TX_GPIO_NUM             15
#define CAN_RX_GPIO_NUM             13
#define EXAMPLE_TAG             "TWAI Self Test"
static const twai_timing_config_t t_config = TWAI_TIMING_CONFIG_500KBITS();
static const twai_filter_config_t f_config = TWAI_FILTER_CONFIG_ACCEPT_ALL();
static const twai_general_config_t g_config = TWAI_GENERAL_CONFIG_DEFAULT(CAN_TX_GPIO_NUM, CAN_RX_GPIO_NUM, TWAI_MODE_NO_ACK);
static void twai_transmit_frame(uint32_t msg_id, uint8_t tx_data[], uint8_t dlc, uint32_t rtr, uint32_t extd)
{
twai_message_t tx_msg = {
.identifier = msg_id,
.extd = extd,
.rtr = rtr,
.data_length_code = dlc,
};
for (uint8_t i = 0; i < dlc; i++)
{
tx_msg.data[i] = tx_data[i];
}
ESP_ERROR_CHECK(twai_transmit(&tx_msg, portMAX_DELAY));
ESP_LOGI("Tx", "Completed");

}
static void twai_receive_frame(twai_message_t *rx_msg)
{
if (twai_receive(rx_msg, pdMS_TO_TICKS(500)) == ESP_OK)
ESP_LOGI("Rx", "Completed");
else
ESP_LOGI("Rx", "Failed");
}
void app_main(void)
{
//Install TWAI driver
ESP_ERROR_CHECK(twai_driver_install(&g_config, &t_config, &f_config));
ESP_LOGI(EXAMPLE_TAG, "Driver installed");
//Start TWAI driver
ESP_ERROR_CHECK(twai_start());
ESP_LOGI(EXAMPLE_TAG, "Driver started");
while(1)
{
    uint32_t msg_id = 0x69;
    uint8_t tx_data[] = {0x71, 0x72, 0x73, 0x74, 0x75};
    uint8_t dlc = sizeof(tx_data);
    uint32_t rtr = 0;
    uint32_t extd = 1;
    twai_transmit_frame(msg_id, tx_data, dlc, rtr, extd);

    twai_message_t rx_msg;
    twai_receive_frame(&rx_msg);

    vTaskDelay(pdMS_TO_TICKS(500));
}

// This is never reached

//Stop TWAI driver
ESP_ERROR_CHECK(twai_stop());
ESP_LOGI(EXAMPLE_TAG, "Driver stopped");
//Uninstall TWAI driver
ESP_ERROR_CHECK(twai_driver_uninstall());
ESP_LOGI(EXAMPLE_TAG, "Driver uninstalled");

}
An interesting fact I think is that the transmit doesn't take place unless the Tx pin is connected to the Rx pin. This is curious in two accounts: 1. The TWAI mode is set to 'TWAI_MODE_NO_ACK', 2. this means the Rx side of the CAN controller is doing something.
If anyone can help I would greatly appreciate it.

Forgot to set tx_msg.self = 1


Replace Tracker with Mooncake in Bayesian neural networks example

Let's depreciate the support for Tracker (we mention Trackerin various autodiff doc pages) since it is no longer actively maintained and is known to be problematic for some Bijectors.

Also need to mention Mooncake in the main AD page: https://turinglang.org/docs/tutorials/docs-10-using-turing-autodiff/


Once Swift Package Manager has iOS support, update project to support it properly

Currently, SPM does not support iOS, but once it does, the preliminary support included currently should be fixed.
xcodeprojs could be generated directly from SPM, too.

Is this a possibility now?

Just came across this https://developer.apple.com/documentation/swift_packages/bundling_resources_with_a_swift_package is there anything specific keeping SwiftMonkey from supporting Swift 5.3?

I'm running into two issues trying to quickly implement this.

I'm not sure how make SwiftMonkey and SwiftMonkey paws separate packages. If you don't have the Package.swift file at the root of your project Swift Package manager gets angry and says there is no package manifest.
Ignoring the above issue and just testing isolating the package from the project I'm getting this error when trying to run the package in my testing environment ld: warning: Could not find or use auto-linked library 'XCTestSwiftSupport' ld: warning: Could not find or use auto-linked framework 'XCTest' I'm assuming this is because XCTest is necessary to compile SwiftMonkey? it's just weird that the package builds on its own but fails to build in a project. I'm not sure how to add XCTest as a dependency to the package however I do think that Swift 5.3 allows for this. Another direction that could be taken is compiling SwiftMonkey as an xcframework and adding that to SPM.


[release-1.25] Update cri-dockerd

Backport:

#6794

Validated using commit id 8fc229521a0b5aeafd6da6f1c715e53462d87052 on release-1.25 branch. cri-dockerd version is bumped as expected.

From the logs:
cri-dockerd version v0.3.2-0.20230123224908-ae42b30520de

Created a cluster using one server one agent, confirmed nodes are up and pods are in running state

Steps:

Install docker on the server node as well as the agent node
Install server passing --docker flag

curl -fL https://get.k3s.io | INSTALL_K3S_COMMIT=8fc229521a0b5aeafd6da6f1c715e53462d87052 sh -s - server --docker

Join the agent passing --docker flag

curl -fL https://get.k3s.io | INSTALL_K3S_COMMIT=8fc229521a0b5aeafd6da6f1c715e53462d87052 sh -s - agent --token <TOKEN> --server https://ip:6443 --docker

Confirm cluster is up and running

ubuntu@ip-172-31-6-0:~$ kubectl get nodes
NAME               STATUS   ROLES                  AGE   VERSION
ip-172-31-11-186   Ready    <none>                 20m   v1.25.6+k3s-8fc22952
ip-172-31-6-0      Ready    control-plane,master   24m   v1.25.6+k3s-8fc22952
ubuntu@ip-172-31-6-0:~$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   coredns-597584b69b-4bth7                  1/1     Running     0          24m
kube-system   local-path-provisioner-79f67d76f8-hnmn8   1/1     Running     0          24m
kube-system   helm-install-traefik-crd-cc4sm            0/1     Completed   0          24m
kube-system   svclb-traefik-7210b76d-xr2cm              2/2     Running     0          24m
kube-system   helm-install-traefik-57sf4                0/1     Completed   1          24m
kube-system   metrics-server-5f9f776df5-kxgbf           1/1     Running     0          24m
kube-system   traefik-66c46d954f-g2l8n                  1/1     Running     0          24m
kube-system   svclb-traefik-7210b76d-pbp2d              2/2     Running     0          20m
ubuntu@ip-172-31-6-0:~$


Improvements

I was just using this today and I noticed some typos, I have corrected them here.

There were the following issues with your Pull Request

Commit: b8c2cc3229144eced343aee21e6b4cd3f4bfbf44

Your commit message does not contain a body

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 16163a4d32af2e758fdd4c5d4961427d4c7bc2f0

Your commit message does not contain a body

Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/lettre/lettre/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Coverage remained the same at 85.879% when pulling 16163a4d32af2e758fdd4c5d4961427d4c7bc2f0 on craftytrickster:improvements into f347dcc97b61c4e983fe0362af617f877a538618 on lettre:master.

There were the following issues with your Pull Request

Commit: a8324795e5b74c4d57b465bd70006d4cab1be700

Your commit message does not contain a body

Commit: 4f4a1436aea78d3f6c9f756930e748bebdf028c8

Your commit message does not contain a body

Guidelines are available at https://github.com/lettre/lettre/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Coverage remained the same at 85.879% when pulling 4f4a1436aea78d3f6c9f756930e748bebdf028c8 on craftytrickster:improvements into f347dcc97b61c4e983fe0362af617f877a538618 on lettre:master.

Thanks!


KYLIN-4686 clean metadata support to delete all jobs

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Kylin?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have create an issue on Kylin's jira, and have described the bug/feature there in detail
[ ] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin project open-source"
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If this change need a document change, I will prepare another pr against the document branch
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at user@kylin or dev@kylin by explaining why you chose the solution you did and what alternatives you considered, etc...

Pull Request Test Coverage Report for Build 6225

1 of 7 (14.29%)  changed or added relevant lines in 2 files are covered.
3 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.0004%) to 28.031%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tool/src/main/java/org/apache/kylin/tool/MetadataCleanupJob.java
0
6
0.0%

Files with Coverage Reduction
New Missed Lines
%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
1
78.12%

tool/src/main/java/org/apache/kylin/tool/MetadataCleanupJob.java
1
0%

tool/src/main/java/org/apache/kylin/tool/query/ProbabilityGenerator.java
1
83.33%

Totals

Change from base Build 6212:
-0.0004%

Covered Lines:
26229

Relevant Lines:
93573

💛  - Coveralls

Dear @bigxiaochu , in which case should delete all jobs regardless of its state? Is it a common case?

@hit-lacus You are right. Modify use message

@hit-lacus update issue content

Thank you for information provided. In general, this code change looks good to me.

Since it should be a non-breaking enhancement, I will merge it.


List transcripts in ListAIResponses for debugging purposes

coverage: 88.353% (-0.02%) from 88.374% when pulling 0bf2fe0474aaf05761d733b849e90808de44588f on ai-transcript-list into a98b608cee047943d3c273f6c8daa047fb7a46cd on ai-transcript.

Current dependencies on/for this PR:

refactor-ai-resp

PR #309

PR #315

PR #313   👈

This comment was auto-generated by Graphite.


Update configure-proxy-internet.md

Added more information about what URL's to open in firewall.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5751

@msbemba

@JohanFreelancer9


1.4.0 regression on 'es6 functions not allowed'

This code fails in 1.4.0, but passes in 1.3.x
Foo.prototype.toString = function toString(){...}

Cursory glance, it looks like this commit might be the culprit: https://github.com/nkt/eslint-plugin-es5/commit/84504e7162b7b796adbc4e22adf8db9cbb52df28#diff-fc9d2adbd42af3a2b5385af5ab88241a

I've reverted this PR. Fix published under 1.4.1.
Thanks!


Proposal to limit @objc inference.

I think you've been using an old template here, as the Rationale does not have its own header anymore?


Customize a11y for rating dialog cancel action.

Description
LEARNER-298
Please refer the to following url for the functionality implemented in this story.
https://openedx.atlassian.net/browse/LEARNER-298?focusedCommentId=254793&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-254793
Details:

Now, we are customizely focusing the a11y control on Play/Pause button when user cancel the rating dialog. (It goes sync with action now when user go to play store or give feedback via email and come back to player fragment.)
Submit button doesn't appear disabled on Galaxy S4 when rating bar has zero rating which is pending to be fixed.

Codecov Report

Merging #944 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #944      +/-   ##
============================================
- Coverage     16.64%   16.62%   -0.02%
  Complexity     1010     1010
============================================
  Files           467      467
  Lines         19885    19902      +17
  Branches       2295     2295
============================================
  Hits           3309     3309
- Misses        16219    16236      +17
  Partials        357      357

Impacted Files
Coverage Δ
Complexity Δ

...g/edx/mobile/view/dialog/RatingDialogFragment.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ain/java/org/edx/mobile/player/PlayerFragment.java
9.11% <0%> (-0.05%)
19 <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 d08df5c...548a696. Read the comment docs.

@miankhalid changes addressed, approved may be 😉


[Bug]: Buttons styling needs to be done

Give a brief about the bug ✍
Buttons in contribute page are not styled
What is the expected behavior? 🤔
It should be styled as other buttons
Provide step by step information to reproduce the bug 📄

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hi @Ridhima10 ,
Sorry for the delay caused by my ongoing exams. I had initially assigned it as a level 1 task. If you look at the "Play Games" page, you'll see that the buttons are already styled. You can simply add that same class or copy and paste the code to achieve the same button styles on different pages.
If the problem is complex, I will automatically upgrade it to a level 2 issue after reviewing your work.
Thank you.

Nicely Done @Ridhima10! keep the work up.
also I can't see leaderboard working, navbar menu button working in smaller screens, and many more can you fix it?
Thank You, and again great work!

@Manaregr8 yes ofc, I can do it. list the tasks need to be done. I'll create issues accordingly and complete it as soon as possible!

@Manaregr8 yes ofc, I can do it. list the tasks need to be done. I'll create issues accordingly and complete it as soon as possible!

Menu button not working in home page {for smaller screens}. {BUG}
Leaderboard not showing up {BUG}
Search bar not functioning {BUG}
DARK to Light theme switch toggle not working {BUG}
In home page the chrome gaming animation is bigger than screen width for smaller screens (it should act like Plag Games Page in smaller screens) {ENHANCEMENT}
In about us page the content of about us section is squeezed up in smaller screens (Fix that to have full screen width) {ENHANCEMENT}

This is it for now try raising issues regarding these and will deliver more one's these are done.

@Manaregr8 I have raised issue for 1,4,5,6
For 2 and 3 i need some clarity

in 2nd tasks do you want to show a table format in which there will be name and achievement of users or something else. please provide me the data. Then i will raise an issue for this
in 3rd you want me to fix the Search-bar so it would open and close or you want me to also add the functionality of searchbar to search the items as well?


Creating Azure AI Workspace fails, (Azure resources are created)

System Information (please complete the following information):

Model Builder Version:
16.3.2056001
Visual Studio Version:
Microsoft Visual Studio Enterprise 2019 Preview
Version 16.9.0 Preview 1.0

Describe the bug
Creating a Object Detection workspace
To Reproduce

Start the model builder
Choose "Object Detection"
3, Click Add new workspace
Set a name, select region, and resource group
Click Create
After approx. 90 seconds, error is shown

Expected behavior
To complete without error
Screenshots
Results in Azure portal after two attempts

Error message:

Additional context
   at Microsoft.Rest.ClientRuntime.Azure.LRO.AzureLRO`2.CheckForErrors()
   at Microsoft.Rest.ClientRuntime.Azure.LRO.PutLRO`2.CheckForErrors()
   at Microsoft.Rest.ClientRuntime.Azure.LRO.AzureLRO`2.<StartPollingAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Rest.ClientRuntime.Azure.LRO.AzureLRO`2.<BeginLROAsync>d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Rest.Azure.AzureClientExtensions.<GetLongRunningOperationResultAsync>d__1`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Rest.Azure.AzureClientExtensions.<GetLongRunningOperationResultAsync>d__0`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Rest.Azure.AzureClientExtensions.<GetPutOrPatchOperationResultAsync>d__5`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Microsoft.Azure.Management.ResourceManager.Fluent.DeploymentsOperations.<CreateOrUpdateWithHttpMessagesAsync>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Microsoft.Azure.Management.ResourceManager.Fluent.DeploymentsOperationsExtensions.<CreateOrUpdateAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.Azure.Management.ResourceManager.Fluent.DeploymentImpl.<CreateResourceAsync>d__60.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.Azure.Management.ResourceManager.Fluent.DeploymentImpl.<CreateAsync>d__59.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Azure.MachineLearning.Services.Workspaces.WorkspaceOperations.<CreateAsync>d__10.MoveNext() in /_/src/Microsoft.ML.AzureMLClient/Workspaces/WorkspaceOperations.cs:line 193
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Azure.MachineLearning.Services.AMLRest.AzureAttachManager.<PutCreateWorkspaceAsync>d__10.MoveNext() in /_/src/Microsoft.ML.ModelBuilder.AutoMLService/AMLRest/AzureAttachManager.cs:line 127
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.ML.ModelBuilder.AutoMLEngine.<PutCreateWorkspaceAsync>d__40.MoveNext() in /_/src/Microsoft.ML.ModelBuilder.AutoMLService/AutoMLEngineService/AutoMLEngine.cs:line 251

Same problem. I have attached a little more info from my attempt.

Hi @frankhaugen @lridgard  sorry for the trouble. Could you try creating workspace in azure portal instead and let us know if it works or not. It can be a temporary work around plus helping us locate the bug.
Regards

Hi @frankhaugen @lridgard , we reproduced the error and are working on a fix for that, in the meantime, one work around is to go to azure portal to create workspace.
Regards

I tried two things.

I deleted the 4 successful resources and then tried the redeploy option from the portal. This created 4 of the 5 resources and failed on the 5th with the same error. as above.

Using the marketplace, I selected the Machine Learning resource, configured it to use the 4 resources successfully created in the earlier step, selected the resource group etc. matching the successful deployments, all other values were left at default, and deployed it. This also failed with the same error as above.

The resource is: Microsoft.MachineLearningServices/workspaces
The error is: "An invalid value was provided for 'accessPolicies'."

This seems to be a problem for new subscriptions or subscriptions with no existing key vaults. You should be able to unblock yourself by creating a brand new workspace in the poral at https://ms.portal.azure.com/#create/Microsoft.MachineLearningServices.
We're working on a fix on our side.

This is fixed! Please download the new build from the VS Marketplace.


Add Settings to WebUI

Short summary about the issue/question:Add Settings to WebUI include Auto refresh setting (moved from NAV), Location of download file ...
Brief what process you are following: Completed draft UI design

How to reproduce it:

nni Environment:

nni version:
nni mode(local|pai|remote):
OS:
python version:
is conda or virtualenv used?:
is running in docker?:

need to update document(yes/no):
Anything else we need to know: Need more ideas and suggestion what should be added in the Settings

@yangou1988 have we supported it?

No, we are not going to support it since the content of the setting is not ready.


Do not paste assistant description when pasting message

When copying text with an assistant mention, the assitant's description is copied, which should be avoided. See https://github.com/dust-tt/tasks/issues/882

Description is copied from the mention's tooltip.
Unusually challenging to solve; spent ~1h30 on it.

user-select: none doesn't work
div inert disables the tooltip
catching & cleaning from copy/paste events is non-trivial

Exploring a little more, then back to Olympus

Catching the full clipboard after copy is also not desirable => triggers a permission request from the browswer

Found a way, PR incoming


Adding Tests

You can run test by npm run test

ok, I made the changes

@ZaynMalloc Please look at the travis-ci issues i think you forgot to import mocha module

I fixed the travis-cli issue

Congratulations for your first merge with us! @ZaynMalloc !


[Feature Request]: useCollection hook for generic Table components

Description
Hello 👋 ,
The useCollection hook has proven to be very useful with the Cloudscape Table component and it is amazing, thank you guys.
I've got an application with extensive usage of the both (hook and Table component) and because all tables needed all table features was decided to implemented it in a generic way.
Something like so:

// AppTable.tsx  component
const useCollectionResult = useCollection<T>(data, {
    pagination: { pageSize: preferencesAtomState!.pageSize },
    propertyFiltering: {
      filteringProperties: filteringProperties,
    },
    filtering: {},
    sorting: { ...collectionHookOptions?.sorting },
    selection: {
      keepSelection: true,
      trackBy: otherTableProps.trackBy,
      defaultSelectedItems,
    },
  });

The hook handles all logic with table sorting/selection/filtering etc., but there is a issue when the parent component of the generic AppTable needs to modify something in the table (for example the selectedItems).
And there is currently no proper way to do it from the parent component.
Intercept of onSelectionChange can set the parent component selectedItems state and notify when it changes like so:
// AppTable.tsx  component
const interceptoOSelectionChange = (event) => {
  actions.setSelectedItems(event.detail.selectedItems);
  props.onSelectionChange?.(event.detail.selectedItems);
};

But when the selectedItems are passed as props to AppTable (that internally has its own collectionProps.selectedItems state) it is hard to keep it in sync with the useCollection hook internal state.
A workaround would be using an useEffect in AppTable in order to listen when parent component changes the selectedItems and updating the useCollection selectedItems state by invoking the right action setter.
// AppTable.tsx  component
useEffect(() => {
  console.log(
    "selected items changed from parent component: ",
    props.externalSelectedItems
  );
  // you can do a diff here between collectionProps.selectedItems and externalSelectedItems
  // to call actions.setSelectedItems only when those are different
  actions.setSelectedItems(props.externalSelectedItems);
}, [props.externalSelectedItems]);

This is quite inconvenient and results into a lot of manual syncing between the Parent component state and generic table component state.
I think this could be easily solved by extending the UseCollectionOptions<T> selection option (and other if needed) with
props from TableProps
selectedItems: T[].
onSelectionChange: NonCancelableEventHandler<TableProps.SelectionChangeDetail<T>>;

and if provided directly to the useCollection hook it will represent the single source of truth
 const useCollectionResult = useCollection<T>(data, {
    // ... other properties
    selection: {
      onSelectionChange: props.onSelectionChange,
      selectedItems: props.selectedItems
    },
  });

Here is a small repro of the current workaround
Let me know what do you think
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate requests

Hello Nichita,
Thank you for reaching out. Answering this question may take extra time because it requires a discussion inside Cloudscape team. We will update the ticket after as soon as find a solution.

Closing due to inactivity. We did not receive any more instances of this ask, so not planning to work on this


(PUP-1890) Reinstate URI encoding fixes

CLA signed by all contributors.

Using  the following external facts on an agent:
space='foo bar'
ampersand='foo&bar'
equals='foo=bar'
hash='foo&bar'
percent='foo%bar'
plus='foo+bar'
star='foo*bar
all='foo&bar=foo#bar%$foo+bar foo*bar

validated that when run from a stable agent (4.10.x), which defaults to pson serialization as well as a master agent (5.0.0), which defaults to json serialization, that they are submitted to the master correctly, and are displayed correctly in the console inventory for the node. The facts are cached correctly in the yaml fact cache file on the master:
137   ampersand: foo&bar
138   hash: foo#bar
139   percent: foo%bar
140   plus: foo+bar
141   star: foo*bar
142   equals: foo=bar
143   space: foo bar
144   all: foo&bar=foo#bar%foo+bar foo*bar

The same values are correctly stored as parameters on the node in the node cache file on the master with node_cache_terminus set.

Per comments on PUP-7665, I believe the test above should have failed when running the agent from master/5.0.0 (which was a naive merge-up that did not result in URI encoded JSON facts). need to investigate why that did not fail.


Document declaring discriminants in Union types

Foo:
  union:
    bar1: Object1
    bar2: Object2
  discriminant: myString

Hello Sir,
I have gone through the repository and the given instructions. The issue seems to attract my interest and excites me to work on it. I humbly wait for you to assign the task to me if your analysis of my profile allows.
Yours Sincerely,
Giriraj Roy.

I've added this to the docs. Thanks @Giriraj-Roy for the offer!


fix a few typos

:wave:
Found this page via http://blog.atom.io/2016/01/07/latest-v8-chromium-features.html

(I signed the CLA)

Thank you Zeke!


Add tests for adding, removing, and modifying modules

Since ref.mli does not contain a module. Created a mod_ref.mli for testing module changes.

The test file seems a bit messy. Is there something we can do to make it easier to understand? Maybe we could add a module to ref.mli or try another solution?

The test file seems a bit messy. Is there something we can do to make it easier to understand? Maybe we could add a module to ref.mli or try another solution?

To make *these& test cases simpler, you could remove the types and values and only have a module which is added, removed, and changed. If you don't have reason to object, I suggest we do that here.
For the file as a whole, I think adding a module to the main ref.mli will only make things more complicated, since all the other cases will also need to account for it.
We could bread these tests into separate files/directories tho. That might help. I suggest we hold off on this until the tests get more complicated however, which they will do shortly :)

Looks great. Thanks!


Search isn't enabled with @searchEnabled=true

<form.element @searchEnabled=true @searchField="company.name" @controlType="power-select" @property="company" @label="Company" @options={{@model}} @optionLabelPath="company.name" />

I expect there to be a search field displayed, but I only get the list of items to select from.

Haven't tested it, but I think the @searchEnabled and @searchField arguments mist be set on the <PowerSelect> component. It is yielded as control component.
<form.element @controlType="power-select" @property="company" @label="Company" @options={{@model}} @optionLabelPath="company.name" as |el|>
  <el.control @searchEnabled={{true}} @searchField="company.name" />
<form.element>

Haven't tested it, but I think the @searchEnabled and @searchField arguments mist be set on the <PowerSelect> component. It is yielded as control component.
<form.element @controlType="power-select" @property="company" @label="Company" @options={{@model}} @optionLabelPath="company.name" as |el|>
  <el.control @searchEnabled={{true}} @searchField="company.name" />
<form.element>

Thanks for the reply @jelhan. I tried this approach, but I end up with a blank select field whenever I select a value after making this change, but I do end up getting the search field so that's a plus I suppose.
What I have now is
<form.element @searchEnabled=true @searchField="company.name" @onChange={{this.changeCompany}} @controlType="power-select" @property="company" @label="Company" @options={{@model}} @optionLabelPath="company.name" as |el|>
  <el.control @searchEnabled={{true}} @searchField="company.name" @optionLabelPath="company.name" />
</form.element>

Not sure if @optionLabelPath is needed on the control as well, but it doesn't give the expected result with or without it there.

I tried this approach, but I end up with a blank select field whenever I select a value after making this change

You are passing a custom onChange event handler. By doing so, you are opting out of the default handling of @property on form's @model. The issue you are describing sounds being related to that one.


feat: add conditional rendering

Render content according to the database_edition in mkdocs.yml.
Added two scripts to process markdown files and the mkdocs.yml separately.
Rules for processing the mkdocs.yml file (here keeping something means hiding it with the exclude plugin, while deleting something means releasing it):

When database_edition is community, keep all content between tags # ent.begin and # ent.end, and delete all content between tags # comm.begin and # comm.end.
When database_edition is enterprise, keep all content between # comm.begin and # comm.end, and delete all content between # ent.begin and # ent.end
When database_edition is both, delete all content between # ent.begin and # ent.end, and between # comm.begin and # comm.end.
Always keep the tags.

Rules for processing the markdown files in the docs-2.0 directory (here deleting something means don't show it, and keeping means show it):

If database_edition is enterprise, the content between {{ ent.ent_begin }} and {{ ent.ent_end }} is kept and the content between {{ comm.comm_begin }} and {{ comm.comm_end }} is removed.
If database_edition is community, the content between {{ comm.comm_begin }} and {{ comm.comm_end }} is kept and the content between {{ ent.ent_begin }} and {{ ent.ent_end }} is removed.
If database_edition is both, both types of content are kept.
Deletes all the tags once the script is run.

The scripts are run in the prepare.sh script before building the docs.
REMEMBER: Write enterprise-only content between {{ ent.ent_begin }} and {{ ent.ent_end }} in markdown files, and community-only content between {{ comm.comm_begin }} and {{ comm.comm_end }}.

You could do more (if you want)
Change the action file. If database_version == all is set, you can run the build process twice to make two separate packages.


Add special handling for disconcerting behaviors like data protection on products provided by producers

We need to document those disconcerting behaviours (including data protection on products provided by producers) and add special handling for it
Originally posted by @teolemon in https://github.com/openfoodfacts/smooth-app/issues/3788#issuecomment-1479611929

Please see: https://github.com/openfoodfacts/openfoodfacts-server/issues/8282


Capture re-exported definitions & multi-level inherited local definitions

https://linear.app/cardstack/issue/CS-6110/load-code-to-identify-carddeffielddef-capture-re-exported-definitions
https://github.com/cardstack/boxel/assets/8165111/a72e0ba6-0f78-4621-8bb9-4402f69e728a
https://linear.app/cardstack/issue/CS-6113/fix-post-card-need-to-consider-arbitrary-depth-inheritance
now, in-this-file panel should capture all cards/fields that are defined locally and its inheritance should be displayed in card inheritance
https://github.com/cardstack/boxel/assets/8165111/bc0a3699-0d60-4352-9b14-a5f7d926c556
here is for the post card
https://github.com/cardstack/boxel/assets/8165111/ac475a50-5546-47e2-91fe-278684c5a6ef
For the 2nd ticket, I still need to enable clicking the inherited local parent card. working on it now

Fixing a bug that is setting wrong local card or field