[CUDA] Initial work for boosting and evaluation with CUDA

This PR initiates adding boosting objectives and evaluation metrics for cuda_exp (see #5163). This PR only creates interfaces for CUDA objectives and metrics, and default back to boosting and evaluation on CPU.

@guolinke @jameslamb @StrikerRUS Could you kindly help to review this PR? After merging this one, we can start adding more objectives for cuda_exp. That will make the single-GPU version of cuda_exp complete. Thanks a lot~

That will make the single-GPU version of cuda_exp complete.

I think you forgot about

#5086
#4781
#5062
#4785

please kindly help to review this PR

Before we put any time into this PR, can you please help with https://github.com/microsoft/LightGBM/pull/5287#issuecomment-1159597587?

That will make the single-GPU version of cuda_exp complete.

I think you forgot about

[CUDA] Enable use of subset Dataset in new CUDA version #5086
[CUDA] Monotonic Constraints on New CUDA Version #4781
[CUDA] Add support for min_data_in_group in new CUDA version #5062
[CUDA] Feature Interaction Constraints on New CUDA Version #4785

Thanks for the reminder. Definitely we also need those features to make our new CUDA version complete.

Close and reopen to trigger the ci.

Close and reopen to trigger ci tests.


feat (audiences): Audience combinations

Summary
This adds support for audience combinations on experiments. If experiment.audienceConditions is present, it will be used as a condition tree where the leaf conditions are audience Ids.

Experiments can now be evaluated on behalf of either complex audienceConditions or simple audienceIds
Audience conditions can either be a string defining array of conditions or simply a string of audience id which is then converted to an OR condition.
Priority will be given to audienceConditions if both audienceIds and audienceConditions are present.

Test plan

Added unit tests for APIs that pass/fail using various complex audiences with different match types.
Added new unit tests for calling condition tree and custom attribute evaluators.
Added unit tests for Decision Service to check User Targeting.

build


French translation

What this PR does / why we need it:
French translation based on the english file.

Awesome. Thanks for the contribution.
Would it be ok to ping you before a release to get this updated, if necessary?

Would it be ok to ping you before a release to get this updated, if necessary?

Yes, please do.


Search filter labels are not translated, like "any" or "studio"

Some of the fields on the filters form for both the home page and the listings filter form are not translated
Steps to reproduce the behavior:

Go to the home page or click on "filters" on the listings page
Change the language to something other than english
Most things are translated, but dynamic values like "any" and "studio" are still in english.

Labels that are not translated (could have more):

"Any"
"Studio"
"(For San Francisco listings, please go to DAHLIA)"

QA Notes:
https://dev.housingbayarea.mtc.ca.gov/

Start on the homepage and change the language
Notice that "Any", "Studio" and the Dahlia field note all have translations
Go to the listings page
Change the language and then open the filter form, checking for those same three translations
Repeat step 4 for each of the languages

This has been released


Enter Fullscreen changed (+maybe other)

INFO Zoom started!
INFO Join a meeting by ID..
INFO Joined meeting..
INFO Check continuously if meeting has ended..
INFO Join with computer audio..
ERROR No .wav files found!
INFO Enter fullscreen..
ERROR Could not find fullscreen!
ERROR Could not find view options!
INFO Enter fullscreen..
ERROR Could not enter fullscreen by image!

I thinks it's trying to find the following:

(according to: https://github.com/rkilchmn/zoomrec/blob/master/res/img/enter_fullscreen.png)
But it looks different now:

I was already in the process of fixing this (changing the image) but then other issues occurred.
Wanted to create this issue to keep track of zooms UI-changes.
If some changes are required anyway, I was thinking of upgrading to zoom 6.x in the process. As it will be enforced February 1, 2025 anyway.

For V2 I plan to move the whole screen control logic to a YAML configuration, such that zoom changes can be accommodated as well.
Ideally it should be verry flexible that it should be able to have a configuration for teams as well

Oh,
didn't realize there is a v2 branch. Thanks for the info, will check it out.
What all did change there / anything you need help with?

lets continue here #5 about V2 features


i18n

I guess that the i18n functions will be exposed in zen.
In zen you have string formatting for DateTime and maybe Currency, and so it seems to make sense to also have the i18n aspect there too ?  SO then you can do a template where you can say " Mr Kane made 2 apples on April 20th, 2019" in any language".

Moved to https://github.com/kyoto-framework/i18n/issues/2


Update Integration Test to use Go 1.19

Which area/kind this issue is related to?

/area ci
/area integration-tests
/area releng
Issue Description

To meet the objective of #1237, we need to ensure our integration test suite is using Go 1.19 with updated dependencies.
Acceptance Criteria

[ ] Update go.mod to use Go 1.19
[ ] Update dependencies under go.mod and go.sum and migrate any changes
[ ] Update workflows to use Go 1.19

/area ci
/area integration-tests
/area releng

The PR which also updates the go version to v1.19 now passes all checks and is good to be merged.

As PR is merged and now the Go version used for the repo is 1.19 I'm closing this issue


monaco editor is bad with font zoom event

steps to reproduce this issue:
step 1. type command: open package.json
step 2. put your cursor on the texts in the sidecar
step 3. press ctrl + multiple times to increase the font size
step 4. notice that the cursor in the editor may move
step 5. To see more funky stuff, try delete or insert texts in the editor

thanks! this seems to happening because both kui and monaco are responding to the font zoom events. if we remove zoomable from custom-content in the sidecar, this problem seems to away?

the PR merge seems to have somehow been reverted


Upgrade to ES 7.6.2 and release version <IP_ADDRESS>

@lukas-vlcek any plans to get it merged and released?

@ArtyomGabeev sorry for delay. I will get to this by the end of this week.


Console Warning from combineResultAsyncList()

I am getting a console warning from Neverthrow that is probably familiar:
[neverthrow] - fromPromise called without a promise rejection handler - Ensure that you are catching promise rejections yourself, or pass a second argument to fromPromise to convert a caught exception into an Err instance
However, it is being generated from inside neverthrow itself. It seems to be coming from the method combineResultAsyncList(), line 344-ish. Looks like we need a proper error handler method on there!

Hey @HyperCharlie,
This annoying little side effect was removed in January. See the following release:
https://github.com/supermacro/neverthrow/releases/tag/v4.0.0
Please upgrade your neverthrow version to >= v4


[DevMenu] fixing shake to open Dev Menu only work once

Fixing issues https://github.com/facebook/react-native/issues/10588
This bug has been introduced during refactoring UIActionSheet to UIAlertController https://github.com/facebook/react-native/commit/d368ebfab2c389cc093f6a73e5c1021408cc6a73#diff-f78a84ff95f2bcee5a70d3accb504528
Test plan

shake to open DevMenu, choose random menu item, it should close DevMenu and after another shaking it should open again

# Another solution
Actually, we can use OC's runtime to fix it if you just want still use the 0.37 version.
// JUST FOR DEVELOPMENT
// TODO: THE NEXT RN VERSION WILL BE REMOVED.

#import "RCTDevMenu+BugFixed.h"

@implementation RCTDevMenu (BugFixed)

static void (*originalImplementationShow)(id, SEL);

static void newImplementationShow(id self, SEL _cmd) {
    [self ivar_setNilValueForName:@"_actionSheet"];

    if (originalImplementationShow) {
        originalImplementationShow(self, _cmd);
    }
}

+ (void)load {
    SEL selector = @selector(show);
    Method originalMethod = class_getInstanceMethod(self, selector);
    originalImplementationShow = (void *)method_getImplementation(originalMethod);
    class_replaceMethod(self, selector, (IMP) newImplementationShow, method_getTypeEncoding(originalMethod));
}

- (void) ivar_setNilValueForName:(NSString *)name {
    unsigned int count;
    Ivar *iVars = class_copyIvarList(self.class, &count);
    for (unsigned int i = 0; i < count; i++) {
        Ivar iVar = iVars[i];
        NSString *theName = [NSString stringWithUTF8String:ivar_getName(iVar)];
        if ([name isEqualToString:theName]) {
            object_setIvar(self, iVar, nil);
            break;
        }
    }
    free(iVars);
}

@end

Good Luck!

@dlowder-salesforce tests added.
Have to slightly refactor the changes to be able to test the handlers, because i haven't found a way how to trigger UIAlertAction programatically.
What do you think?

@wuchu thanks for the another solution. Will use it as a workaround on my local! 👍

@dlowder-salesforce 😁

@dlowder-salesforce ping :)

@VojtechBartos I'm fine with the changes, but someone from FB will be needed to merge your PR :)

@dlowder-salesforce thanks!
@javache is there a chance you could merge this PR ? :)

@javache ping :)

@javache updated

@VojtechBartos Thanks for fixing this!
Tests failed on Travis, not sure if related. Restarted the build.
Circle CI tests failed with unrelated Flow errors. Can you try rebasing?

@mkonicek thanks for restarting the travis build, but it's failed again, not sure why, on local the iOS ones passing without any issue.


Contribute this package to JuliaSparse

@dpo I wonder what you think about moving this package to the JuliaSparse organization. We are doing this in order to collect various sparse matrix related codes in one umbrella organization. Of course, completely ok, if you prefer to keep things as they are.
It would also be great if the package could be licensed MIT/BSD.

Sure that sounds good! I'll add the Rutherford Boeing reader and update the license this weekend.

Thanks!

Should be good to go. I renamed the module HarwellRutherfordBoeing. I added a preliminary Rutherford-Boeing reader. I haven't tested it on the entire collection, but it's been working diligently so far. The Harwell-Boeing reader has been tested on the entire collection.
Once the transition is done, I'll set up TravisCI and Appveyor builds. My experience is that Appveyor doesn't like when repos move or change name.

I made you owner of JuliaSparse - so you should be able to transfer it.

Thanks @ViralBShah! It's done.


[QOL Suggestion] Make it so clicking on the code will copy to clipboard.

Right now, clicking on a code does nothing, i'd suggest making it so it would copy the code to clipboard.
I know there's already a little button for that, but at least personally i would much rather click the big code box when quickly trying to copy the code to a website. It also feels intuitive (personal opinion).

I explained in the reddit reply (https://www.reddit.com/r/Windows11/comments/x0zkcy/comment/imeykl1/?utm_source=share&utm_medium=web2x&context=3) why I didn't add this. Personally I will not add it but if someone does a pr I will accept it. Closing this issue for now


Fix script hash bangs.

PR Overview:
Fix the hash bangs on all the tools scripts.
Documentation:
No documentation changes are needed
Integration Tests:
Probably should exist for these >.>

If you run them like below they would work fine. Potentially if your shell is bash they might work fine too, but that would be machine dependant (maybe your vagrant is happy to try running them with bash by default)
bash /script/name/here

My default shell is fish, so it can't make the assumption that executable text files are bash scripts, and the space in front of the hash throws it.


Add trace-context propagation helper for RxJava2

There are a number of issues on the sleuth project relating to RxJava2. Many of these have to do with TraceContext being lost during the library.  While automatic tracing of rxjava2 would be a potentially tricky task (with a lot of complexity on which threads to skip etc), continuing a trace context should be relatively straight-forward and prevent broken traces.
This issue could start a brave-context-rxjava2 whose only purpose is preventing people from breaking traces via a scheduler hook.
The propagation-only scheduler hook could be similar but smaller scoped than https://github.com/spring-cloud/spring-cloud-sleuth/pull/775
See similar issues about broken traces:
https://github.com/spring-cloud/spring-cloud-sleuth/issues/909
https://github.com/spring-cloud/spring-cloud-sleuth/issues/398

WIP https://github.com/openzipkin/brave/pull/665

couchbase-java-client is on RxJava 1.6.0-SNAPSHOT

@asarkar right.. seems https://github.com/couchbase/couchbase-jvm-core is where rxjava is defined, and yes it is still using rxjava 1.x

@asarkar I think we need to qualify the "rxjava" issue with that couchbase driver. For example, the internals are a somewhat complex mix of a span stack and opentracing. Can you please make an example project on https://github.com/openzipkin/sleuth-webmvc-example that reproduces your problem? For now, I'm going to focus on things that are more simply rxjava in nature

deferred the couchbase thing based on more details here. I'd like to see this reproducible as at the moment it doesn't seem like something generically addressing rxjava hooks will fix.

Little busy now, but I expect to be able to provide a reproducible problem by end of the week


Fix typo

I think the text is correct as is (though admittedly therefor is somewhat archaic). I don't really have an opinion, but would default to leave things as is. @danielshahaf ?
OT: Since you appear to be on a typo fixing spree, is there some linter you're using to find these typos? Might be handy to put into some CI pipelines.

Yes, it's correct as is.  I'm happy to consider alternatives that improve clarity, of course.  I was trying to describe a set of circumstances first and the behaviour therein in those circumstances second, and used therefor so as to not have to name the function the sentence talks about.  We could reverse that last criterion:
# will succeed.  In particular, if [-a function-]{+F+} has been marked for autoloading
# but is not available in $fpath, then {+calling+} this function {+on F+} will return [-False therefor.-]{+False.+}

I'll reopen this later pending decision on the proposed text in my last comment. And we did forget to thank you for the patch, so, thanks for the patch :-)


[Enhancement] Add illuminance sensor and state sensor support

Hello, thank you for your Matter hub.
Would it be possible to add an illuminance sensor and state sensor to the list of supported devices?
I am using the presence sensor below, which includes a state sensor with three possible values: move, presence, and none.
https://www.zigbee2mqtt.io/devices/ZY-M100-24GV3.html
If you need any additional information to include it, please let me know.

First,

illuminance sensor

state sensor

The developer tools only show that information. So I am attaching the relevant log for reference.

It has three stats; none, presence, move.
Second,
I understand the add-on policy. While this device may have multiple components, I have no problem if they are separated into individual entities as long as they can be passed to ST.
For your information, attaching the full entitiy of this device

The device has control entities and sensors, and currently, Presence(존재감지) is supported by "matter-hub." As for "Distance sensor", I don’t mind if it’s not supported (it’s not an issue for me), and I don’t mind if control entities aren’t supported right away either. For now, what I hope for are just the illuminance and state sensors.
Thanks for your project.
If you need any additional information to include it, please let me know.

Yes, the presence sensor (as shown in the above capture of "존재감지") which has value; away, home, and a device_class, can be registered in the Matter hub.

However , i when I tried to register "state sensor" without a device_class in hub, it wasn't possible.
So, does that mean it will technically remain impossible for the current "state sensor" without a device_class to be supported by the Matter hub in the future?
Additionally, is illuminance support possible?
Thanks.


Fixes a couple docs Issues

https://github.com/bitovi/canjs.com/issues/237
https://github.com/bitovi/canjs.com/issues/236

Thank you!

@daffl @julia-allyce is this not yet merged into the site because its waiting for the 2.2 release?

The site won't be deployed until the release.

@julia-allyce next time if you say "fixes bitovi/canjs.com#237" or "fixes #1672" or whatever the issue number is, it will close the ticket automatically when the PR is merged into master.


Improve Django version check

The current check works only for Django 3.xxx:
django.VERSION[0] >= 3 and django.VERSION[1] >= 1:

Recently a new Django version was released 4.0..., with the old check the package is not working because of:  django.VERSION[1] >= 1

@bhch May I ask you for review and merge if possible? 💪

Fixed in #24.

I've released a new version ([v2.7.0](https://github.com/bhch/django-jsonform/releases/tag/v2.7.0. Please upgrade.
Thank you for the PR.


Moving LCO related files to modules

@aurianer could this failure be related to the recent changes to the base image: https://app.circleci.com/pipelines/github/STEllAR-GROUP/hpx/6946/workflows/397303e6-e791-42f4-aff3-910373d7f5d9/jobs/241472?

Possibly the code coverage PR also modified the way we installed cmake, will have a look

Actually it was an old leftover, for the checkout and install step we were still using the image 1, @msimberg has a PR on its way :)

Actually it was an old leftover, for the checkout and install step we were still using the image 1, @msimberg has a PR on its way :)

See #5226.


Really alphabetize the SingleResourceNameConfigs

Emphasize that InterfaceConfig.getSingleResourceNameConfigs is an unordered collection, and that it's up to the transformers to order the configs as they see fit.
This reduces the diff between a GAPIC config v2 -generated client and one generated with GAPIC config v1.

PTAL


Cannot disable input dynamically with disable prop

Hi @jacobmischka! Thanks for you great work on this project!
I found a strange thing, REPL: https://svelte.dev/repl/e112a7119f2041fcbe8c5237f2f6138a?version=3.24.1.
It doesn't disable input if I change the disabled at runtime.
If I change the code to let disabled = true the input is disabled and then I cannot change it anymore with the button click.
Is this something wrong with me? :smile:

I think this is actually the same problem as https://github.com/haoxins/react-flatpickr/issues/125: the disabled prop applies to the underlying input element, not the flatpickr component. I think you should use one of the flatpickr options instead of toggling disabled directly.
Let me know if this doesn't make sense.

Oh wow. I think it works now: https://svelte.dev/repl/e112a7119f2041fcbe8c5237f2f6138a.
Crazy things! 🤣

Sick! Must have been an underlying flatpickr issue that was addressed. I'm going to close this in that case. Thanks for writing back!


edit JavaScript formatting in index.html

This pull request regularizes whitespace rules in index.html.
Background
This does basically the same thing as my README pull request.
Screenshots
I'm lazy this time, and it's just a text file.

@apotheon: Thanks for submitting a pull request. During the next couple of weeks, this repository is going to have a major overhaul. When that process is over, please submit another pull request with any changes you feel would benefit the repo. I'll make sure that it takes less time to get a reply :).


Tweak Status.exception() protocol

Description
Make it return Optional[BaseException] like Future.exception()
Motivation and Context
So it's easier to make ophyd.v2.core.AsyncStatus.exception (as this is what Task.exception() returns)

@tacaswell mind if I merge this?


Fixes vulnerabilities identified via dependabot

LGTM assuming that there is no negative impact on the Azure tests

@mkulke can this PR be tested via Azure e2e ci ?

LGTM assuming that there is no negative impact on the Azure tests

@mkulke can this PR be tested via Azure e2e ci ?

we don't have a label toggle for that yet. so, the tests only run on main. If the code compiles but the tests break due to a bump in dependencies, I'd be surprised.

As mentioned on slack. I think we need to decide what to do with respect to the release:

Ignore it and continue even with a go vuln complaint (probably not ideal)
Merge it before the release, but don't worry about re-creating and re-tagging the pre-release on the assumption it doesn't significantly impact testing (if possible this is the least disruptive)
Merge it and re-start the pre-release to create a new pre-release build

As mentioned on slack. I think we need to decide what to do with this PR with respect to the release:

Ignore it and continue even with a go vuln complaint (probably not ideal)
Merge it before the release, but don't worry about re-creating and re-tagging the pre-release on the assumption it doesn't significantly impact testing (if possible this is the least disruptive)
Merge it and re-start the pre-release to create a new pre-release build

it being an alpha release I would go with 1) or 2) we can add an checklist item to the release doc that we want to verify vulns and bump revisions early in the process

Let's go for 2. and merge this now. I will re-run the libvirt e2e tests on this once merged too and I guess the Azure ones will as well then, so that should be enough.


Possible to fall through nearby region tiles

In FPS mode, walking to the border of the map and attempting to jump onto a neighboring region causes one to fall off the world. The neighboring region tiles' floors, though contiguous with the map, appear to have no collision properties.

Yeah, I never really got around to adding collisions to them. I'll try to get it done in the next release.


Make async-io optional for people who only want to use the executor.

Currently, async-io is marked as an optional dependency in Cargo.toml, but when not on wasm, it's always turned on on async-global-executor. Would it be possible to make it truly optional for people who only want to use the executor?

I too would like to see this as in my current project I want to use the task::spawn function without pulling other dependencies.
A way could be to put the task module or it's related functions on a gated feature (similar to how tokio does it) and include it in the default feature, so that no downstream code breaks.


option work when out of game

I don't have much to say, but this option will be very helpful if you want to be out of the game.

Press F3+P


Fixing errors in GitHub actions

the changes in this PR were already added in PR #22 ... closing PR


[EventHubs] Add unit test for 32 partition greedy ownership to attempt and validate issue #13546 having been fixed

Tests seem to indicate it's been dealt with via. latest load balancing changes.
closes #13546

/azp run python - eventhub - tests

/azp run python - eventhub - tests

/azp run python - eventhub - tests


What is the password to log in as administrator

replace administrator password with this ciphertext $2y$08$StPt5ZOa4fKr8XyIpISit.YunvpisPP2gHeGCkVMeJIEG.QWN1b2O
and then try the password 12345678


[feature] Enable 3G Dongles

To get 3G Dongles working, we'll need to update some dependencies on the device, add a udev rule, and finally add logic to the CLI to write the appropriate options to the /etc/config/network file. This issue is about that final piece which needs to be in t2-cli.
To see how to do this, check out https://wiki.openwrt.org/doc/recipes/3gdongle.

This would still be a great feature and we can't use 3G dongles smoothly until it's added. If anyone is interested in contributing and needs more help, feel free to ping me here.

Hi, @johnnyman727 , this would be a great feature. Looking forward that we can use 3G dongle automatically.
I opened https://wiki.openwrt.org/doc/recipes/3gdongle but feel completely confused (I'm a web developer and not familiar with OpenWRT/hardware/system programming). Does it mean we need to ssh to Tessel machine and run several commands there?
Thanks

Hi @shaochuancs, thanks for getting involved!

I opened https://wiki.openwrt.org/doc/recipes/3gdongle but feel completely confused (I'm a web developer and not familiar with OpenWRT/hardware/system programming)

No worries - I felt the same way when I first started perusing through OpenWRT docs (and still do sometimes). Feel free to ask me any questions that come up.

Does it mean we need to ssh to Tessel machine and run several commands there?

Yes, that's exactly right. If your Tessel is connected to your wifi, you can get a shell with t2 root. That's the preferred way to work with Tessel's console (it uses ssh internally). If not, you can still get a shell over USB but you'll need to use a tool like dterm or screen (you'd use the command like screen /dev/usbmodem1422).
Typically, the way we build things for the CLI, is we'll use the shell to figure out what commands we need to run to get some feature to work. Once we have a list of commands to run, it becomes relatively simple to automate those commands with the CLI.
As an example, here is how we enable access points. You can see that we have a lot of commands that use:
tessel.simpleExec

This is basically a wrapper over:
tessel.connection.exec(SOME_COMMAND, () => {});

and it's a shorthand way of saying "run this shell command and then resolve a Promise once that command completes.
We have one file where we list all the commands we use on Tessel (and pass to simpleExec or tessel.connection.exec).
I hope that all makes sense - let me know if you have any questions!

Hi, @johnnyman727, Thank you so much for the explanation! I'll read some OpenWRT docs and try to enable my 3G dongle.
Thanks

No problem. Let me know how it goes!

+1

+1

Hey, @mittalshravika and I have been trying this issue. We used a shell over USB (screen) to update the "opkg" but are encountering the following issues (as in the screenshot)

We tried looking up the error here and here but there has been no progress.
Could you please help?
@Frijol @johnnyman727

Hi @brihijoshi, did you ensure that the Tessel has an internet connection before running opkg update?

Hey, No it was not connected to the Internet. That is one reason why I opted for running the shell over USB. Thanks a lot!

:+1: Good luck!

Hey, so after we got our Tessel connected to the WiFi, we started downloading the packages as given in here - https://wiki.openwrt.org/doc/recipes/3gdongle
One issue came up in the command "opkg update" and an error is being thrown named "Signature Check Failed" as in the image below

However, the remaining packages have been successfully installed.
Any help would be amazing 😄

possibly need to update your DNS address? https://forum.arduino.cc/index.php?topic=199167.0

@brihijoshi Yes, I've seen that warning message shown when using opkg update. It's a problem with how something unrelated is configured but it shouldn't block OpenWRT from downloading system updates.

Any updates so far? I also would like to use an USB 3G dongle from Huawei to access the internet with a Tessel 2 from all over the world.

@bart I've not had any progress, mostly because I don't have a USB 3G dongle for testing. If you would like to give it a shot, I'll provide any insight with OpenWRT and adding features to the CLI to help out.

All right @HipsterBrown I'll see if I can do anything here. As far as I understood it's "just" about some linux settings that has to be made, right? I have a Huawei E173 which should work.

All right it looks like OpenWRT is able to find my USB dongle without any problem. But when it comes to the chat script unfortunately it fails to connect. I'm using a Things Mobile SIM card here. No idea what the reason is.
Thu Dec 20 22:36:23 2018 local2.info chat[12186]: AT+CGDCONT=1,"IP","TM"^M^M
Thu Dec 20 22:36:23 2018 local2.info chat[12186]: +CME ERROR
Thu Dec 20 22:36:23 2018 local2.info chat[12186]:  -- failed
Thu Dec 20 22:36:23 2018 local2.info chat[12186]: Failed (ERROR)
Thu Dec 20 22:36:23 2018 daemon.debug pppd[12184]: Script USE_APN=TM DIALNUMBER=*99# /usr/sbin/chat -t5 -v -E -f /etc/chatscripts/3g.chat finished (pid 12185), status = 0x6
Thu Dec 20 22:36:23 2018 daemon.err pppd[12184]: Connect script failed
Thu Dec 20 22:36:24 2018 daemon.info pppd[12184]: Exit.

@bart Good to hear that OpenWRT is finding the USB dongle. To what chat script are you referring? Also, have you confirmed the SIM is activated?

Ha! It works now. Was my bad because I put in a SIM card of wrong format... please, say nothing ;) All right, so now I must adapt the CLI to at least give users the possibility to configure their USB dongle that works out of the box without having to map it as serial device. Should I just check out the code myself or do you have something like a guide for adding new CLI commands?

@bart That's great you got it working! :clap: We don't have a guide for adding new command (good point though), but you can take a look at a previous PR like (https://github.com/tessel/t2-cli/pull/985/files) to see an example of adding a new command. Please let me know if you have any questions and feel free to open a PR at any point for early review.


reset button next in Path2D "curve" property not working.

Godot version:
3.2
OS/device including version:
Windows 10
Issue description:
The  reset button does not reset to an empty curve. (See .gif animation)

Steps to reproduce:

Create "Path2D" node.
Draw your curve.
Now press the reset button. Curve disappears, but when you now draw a new curve, the reset button is also gone.
If you select "New Curve2D" from the dropdown, and then reset, it will default to the previous curve you had drawn.
Minimal reproduction project:

Same kind of bug is present in spatial path.
It can be fixed by using an empty Ref<Curve2D> and Ref<Curve3D> for curve property of Path2D and Path respectively.
@shafnaz If the above fix is applied then you have to assign a new Curve2D to Path2D through drop down menu before editing it or after a revert.
@KoBeWi  If that sounds good to you then I will issue a PR (already tested).

@simpuid If you have a PR ready, just open it and someone will review whether the fix is good or not.


Checkout management

Description
Why is this change required? What problem does it solve? Describe your changes in detail:
Managing the write and read enable stock object is not seamless. This is a reasonable attempt to solve the UX
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Documentation update
[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist
List of items to check before submitting your PR. Note that this are only for helping
you remember what you might (also) need to do and are not mandatory requirements

[ ] Documentation is updated
[ ] docs/changelog.md is updated
[ ] Added test cases

Codecov Report

Merging #37 into master will decrease coverage by 0.52%.
The diff coverage is 86.73%.

@@            Coverage Diff             @@
##           master      #37      +/-   ##
==========================================
- Coverage   91.53%   91.00%   -0.53%
==========================================
  Files          21       21
  Lines         685      745      +60
  Branches       51       56       +5
==========================================
+ Hits          627      678      +51
- Misses         47       52       +5
- Partials       11       15       +4

Impacted Files
Coverage Δ

stockroom/cli.py
81.33% <75.00%> (-4.59%)
:arrow_down:

stockroom/core.py
77.77% <75.00%> (+0.69%)
:arrow_up:

stockroom/storages/model.py
84.61% <95.00%> (+1.48%)
:arrow_up:

stockroom/storages/experiment.py
85.36% <100.00%> (+1.15%)
:arrow_up:

tests/conftest.py
100.00% <100.00%> (ø)

tests/test_cli.py
100.00% <100.00%> (ø)

tests/test_data.py
100.00% <100.00%> (ø)

tests/test_multiple_instances.py
100.00% <100.00%> (ø)

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 9a21522...2f0fa84. Read the comment docs.


Add Livewire widget

This adds an official Livewire widget.
DOCUMENTATION
The following section can be added to the documentation of Widgets:
Livewire Widget
You can easily load a Laravel Livewire component as a widget, all you have to specify is the component name and the parameters it expects. As an example, if a Livewire component is loaded regularly in this way:
<livewire:livewire-column-chart :column-chart-model="$columnChartModel" />

...it can be loaded in a widget using this configuration:
[
   'type' => 'livewire',
   'component' => 'livewire-column-chart',
   'params' => ['columnChartModel' => $columnChartModel],
   // 'wrapper' => ['class' => 'col-md-6'], // optional
   // 'class'   => 'card bg-dark text-white', // optional
]

Sometimes you may need to put additional HTML attributes in the container for the component – you can just pass them to the attributes key as an array:
[
   'attributes' => ['rel' => 'chart', 'style' => 'height: 250px;']
]

HOW TO TEST
It can be tested with any Livewire component, here I am using https://github.com/asantibanez/livewire-charts as an example.

Install Livewire in a project where Backpack is already configured:
composer require livewire/livewire

Install the Livewire Charts library:
composer require asantibanez/livewire-charts
php artisan vendor:publish --tag=livewire-charts:public

Create resources/views/vendor/backpack/base/dashboard.blade.php file with the below content:
@extends(backpack_view('blank'))

@php
    $pieChartModel = (new \Asantibanez\LivewireCharts\Models\PieChartModel())
        ->setTitle('Expenses by Type')
        ->addSlice('Food', 100, '#f6ad55')
        ->addSlice('Shopping', 200, '#fc8181')
        ->addSlice('Travel', 300, '#90cdf4');

    $widgets['before_content'][] = [
        'type' => 'livewire',
        'component' => 'livewire-pie-chart',
        'wrapper' => ['class' => 'col-md-6 col-lg-4 mt-3'],
        'params' => ['pieChartModel' => $pieChartModel],
        'attributes' => ['style' => 'height: 250px; padding-top: 20px;'],
    ];
@endphp

@push('after_scripts')
    <script src="//unpkg.com/alpinejs" defer></script>
    <script src="https://cdn.jsdelivr.net/npm/apexcharts"></script>
    @livewireChartsScripts
@endpush

Visiting the dashboard will now show a chart loaded through a Livewire component:

Closing in favor of https://github.com/Laravel-Backpack/theme-tabler/pull/20 - widgets should live in CRUD, not themes.

In favor of #20 ? Isn't this the same as...this ?:)

Haha good catch. It's https://github.com/Laravel-Backpack/CRUD/pull/4971


Drop ghc closure

Summary:
Drop server-invoker from playgrounds to drop the (huge) ghc-closure from the playground servers
Details:

The server-invoker is a wrapper that adds ghc with all required packages to an environment in which the respective playground server is then started. This is not necessary for production since we have a dedicated ghc-web instance to which all compilation requests are forwarded (currently rather implicitly via nginx).
In order to not break the local development workflow the start-backend scripts ( -> plutus-playground-server and marlowe-playground-server in the nix-shell environment) have been updated - no changes to your workflow are required.
The closure of the playground deployment went down by several GBs

I tested these changes locally and also deployed them to https://tobias.marlowe.iohkdev.io/#/haskell and https://tobias.plutus.iohkdev.io

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] nix-shell shell.nix --run updateMaterialized to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[ ] nix-shell shell.nix --run fix-stylish-haskell to fix any formatting issues

If you changed any Purescript files:

[ ] nix-shell shell.nix --run fix-purty to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

There's quite a bit of commented out stuff, are you going to fix that or is it dead?

There's quite a bit of commented out stuff, are you going to fix that or is it dead?

Oh indeed, thanks. let me take care of that...

@michaelpj @merivale I wanted to "get done" with the change and got sloppy towards the end which i shouldn't have.
I fixed everything up now:

All tests back
Workflow as before


Ground clamping broken in 2D and CV

As discussed in #4240

Load the KML demo.
Switch to 2D
Billboards are broken (Similar problems in Columbus View)

May be the same root cause as #4300 and #4062.
We should really fix this before the next release.

We should really fix this before the next release.

+1

I'm about to open a pull request which fixes several clampiing issues, but it turns out that this particular issue is fundamentally a performance problem.  If you just sit there and wait forever it eventually finishes and fixes itself.   You can also see this by disabling the time slicing (which also makes it go a bit faster).  In addition to simply profiling  and improving the hot spots, we might need a slightly different approach here in order to keep this acceptably fast (I have some ideas, but I need to experiment some more first).

Also, we disabled billboard clamping by default for KML because of this, so in order to reproduce this you need to set clampToGround to true in the Sandcastle example

I'm removing the "next release" tag since this is no longer the default behavior.


Firebase apm

I have included screenshots of the console with varied information and explanations. This information is a sample and should have more data as we use the app more.
https://github.com/irinafakotakis/simpleCamera390/wiki/Firebase-APM


Should id be included in AnonCreds W3C credential, or is it 'valid' to only include it in the W3C credential

When creating a W3C credential with both an anoncreds and eddsa signature, should we add the id property to the AnonCreds schema and cred def, or can we issue the anoncreds cred without the id property, and only include it in the signature of the eddsa signature?
cc @swcurran @Artemkaaas @gvelez17 @2mau

We can only use W3C VCs with AnonCreds that adhere to AnonCreds limitations — no complex structures, no arrays.  As such, I think this should also align to that.  My suggestion:

to have eddsa holder binding the AnonCreds schema MUST have an id field in it.
if not — the eddsa signing amounts to a bearer/unbound token.

Is that a reasonable way to go?
I think that adding an id to AnonCreds "under the covers" is problematic.

Updated in test vectors


[$250] Android - Scan - Pay elsewhere greyed on submitting expense with currency other than local

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.69
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4534392
Issue reported by: Applause - Internal Team
Action Performed:
Pre-condition: Workspace set in local currency and submission frequency set to manual

Launch app
Open Workspace chat
Create an expense with local currency
Tap submit and pay elsewhere
Note paid without any issue
Create an expense with currency other than local currency
Tap submit
Note pay elsewhere button greyed out
After tapping greyed out pay elsewhere button few times user able to pay

Expected Result:
In workspace, expense created with currency other than local currency when submitted, greyed out pay elsewhere button must not be displayed
Actual Result:
In workspace, expense created with currency other than local currency when submitted, greyed out pay elsewhere button displayed
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/2b2fe875-9b30-4d93-a673-0cf5543f311f
https://github.com/Expensify/App/assets/78819774/ce0183d7-9121-49cd-a40f-e4ff3c847943
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0198922fe1d95a1791
Upwork Job ID:<PHONE_NUMBER>730265600
Last Price Increase: 2024-05-25

Issue OwnerCurrent Issue Owner: @rayane-djouah

@bfitzexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Please re-state the problem that we are trying to solve in this issue.
In the workspace, expenses created with currency other than local currency when submitted, the pay elsewhere button is disabled while it should not be disabled as mentioned above.
What is the root cause of that problem?
There is a condition written in the code which checks if the local currency matches the selected currency and if they don't match then the SettlementButton is being shown as disabled.
What changes do you think we should make to solve the problem?
We can remove the condition from the code which can display the button as enabled even if the currency doesn't match.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01d56d7360118cadc8

Hi @rayane-djouah , Please check if the proposal is okay now...?

@rayane-djouah Sorry, I didn't get the time to read the mentioned issue fully. I'll make sure to update you tomorrow about this issue clearly.

@rayane-djouah, I've gone through #35062, and it appears that when submitting expenses with currencies other than the local one, the "pay elsewhere" option is being greyed out. This occurs because the currency is first converted to the local currency before enabling the option. The button remains disabled until the converted currency is fetched through the backend.
A similar issue was encountered before, and the solution was to inform the user to wait while the currency is being converted, rather than simply showing the button as disabled. The currency condition cannot be removed because it affects payment calculations when the user is offline, as mentioned in #35062.
To address this, we can implement a toast notification to inform the user why the button is disabled.

After reading the thread and issue I feel like there's a few solutions to this. Ultimately we want the user to wait until the conversion is done and by putting it as disabled it looks like an action is not possible, which isn't the case, it's more that the user needs to wait until they can press the button.
Here's the three solutions I've come up with (though I'm sure there's more):

Changing the label of the button while it's converting to Converting... or something similar
Replacing the button for a spinner while the conversion is done, then replacing it back to a button
Adding a new loading state in our button component that allows for a spinner inside the button while an action is performed (this might be handy for other things in the future too).

Keen to hear what @Expensify/design thinks here. I'm okay with all though option 3 could be useful elsewhere. I've found that a loading state on buttons are handy on other areas of the app where a network request is happening or you tap a button waiting for something but instead of showing a separate loading state you can just change the button state. Open to other solutions too though.

Oh are we? Awesome find @rayane-djouah!
If so, then that's my vote, but let's hear from @shawnborton and @dannymcclain first.

I can get down with that (third option above), that makes sense to me.

Yup I'm down for option 3 as well. And we definitely already have that pattern elsewhere in the app, so that's cool! You should be able to see it in Storybook (although Storybook isn't working for me anymore...)

So, I think that when we click on the submit button offline it should become disabled, and when online it should shows a loading state, and when we get response from backend, we should display the Settlement button.

That seems right to me, but keen to hear what @Expensify/design and @trjExpensify thinks about this

@rayane-djouah please check if the proposal is ok and sorry for the late response.

@rayane-djouah I'm unable to log in to the app whenever I try to click on previous chats it just shows something went wrong.

@rayane-djouah, I tried doing that too but I'll check once again.

@shreykul any luck getting in?

Adding a second BZ team member to keep an eye on this while I'm OOO until June 11th.
Current status: waiting on proposals. Since this is 4 weeks old, we might want to consider doubling this bounty.

Asking SWM if they might be able to grab this - https://expensify.slack.com/archives/C04878MDF34/p1717127772013379

The PR is ready for review cc @rayane-djouah

Update for Melvbot - monitoring - https://github.com/Expensify/App/pull/42981

Thanks for the heads up @rayane-djouah! I am going to assign another C+ to keep this PR moving!

Gonna move this to weekly since the PR is reviewing

Just a heads up - I'm going to be ooo until June 24th. I'm not going to assign anyone new since @bfitzexpensify is on this!

Hey, the PR has been approved by C+, but the internal hasn't been assigned.

Hmm seems I didn't get assigned to this issue via "C+ approving a proposal" - so maybe that's why i didn't get assigned to review the PR 🤔  anyway, will do today!

Payouts due:

Contributor+: $250 @eVoloshchak (thorough NewDot)

@eVoloshchak let us know if you think a regression test is needed for this

This is ready for NewDot payment based on this payment summary - https://github.com/Expensify/App/issues/41445#issuecomment-2197411374
@eVoloshchak let me know about a regression test!

The PR that introduced the bug has been identified. Link to the PR: N/A, the behavior wasn't implemented initially
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: additional discussion isn't needed, the bug is very minor

Regression Test Proposal

Go to workspace, press + next to the Composer and "Track expense".
Change the currency to a different one than the default one.
Typ in an amount and press "Next" -> "Track expense".
Veirfy that the settlement button that a loading spinner is shown.
Go offline and repeat step 3.
Verify that the settlement button is disabled.
Go online again and repeat step 3.

Do we agree 👍 or 👎

Thanks @eVoloshchak! Regression test is here - https://github.com/Expensify/Expensify/issues/409726
NewDot payment summary here - https://github.com/Expensify/App/issues/41445#issuecomment-2197411374
Closing as complete!

$250 approved for @eVoloshchak based on summary above.


docs: Example of setting setuptools_scm and DynamicVersion

This is from a small project of mine CmakeExtraUtils that makes the git version of setuptools_scm available for cmake projects as well.

pre-commit on this fails because of disallow-caps. I don't know where to find it and edit it to allow for the changes here.

It really should be called CMakeExtraUtils, IMO :)

Edit .pre-commit-config.yaml to look like this:
        exclude: ^(.pre-commit-config.yaml|docs/configuration.md)$

GitHub's inline editing tools have been a little broken lately, or I'd do it.

Disallow caps does not allow "Cmake", as it should be "cmake" or "CMake". Your package is called "CmakeExtraUtils" which breaks the check. The best "fix" would be to rename the package. The second best fix is just ignoring this file, though it's not ideal. I do want this check running on the source code, to make sure any CMake* class added in the code follows a consistent naming style.

I can do the former

Ok, feel free to push/rebase on top of it or merge it if needed


Adding keep number causes cycler to fail

Just set up backup for the first time, ran the default generator and set up a simple backup, ran it and got this error:
[2015/10/08 19:32:41][info] Storage::Local Started...
[2015/10/08 19:32:41][info] Storing '/Users/Matthew/backups/my_backup/2<IP_ADDRESS>.31.35/my_backup.tar'...
[2015/10/08 19:32:41][info] Cycling Started...
[2015/10/08 19:32:41][error] Model::Error: Backup for Description for my_backup (my_backup) Failed!
[2015/10/08 19:32:41][error] --- Wrapped Exception ---
[2015/10/08 19:32:41][error] ArgumentError: negative array size
[2015/10/08 19:32:41][error]
[2015/10/08 19:32:41][error] Backtrace:
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/storage/cycler.rb:25:in `last'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/storage/cycler.rb:25:in `cycle!'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/storage/base.rb:47:in `perform!'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/model.rb:334:in `block in store!'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/model.rb:332:in `map'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/model.rb:332:in `store!'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/model.rb:306:in `block in procedures'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/model.rb:269:in `call'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/model.rb:269:in `block in perform!'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/model.rb:268:in `each'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/model.rb:268:in `perform!'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/lib/backup/cli.rb:156:in `perform'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/thor-0.18.1/lib/thor/command.rb:27:in `run'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/thor-0.18.1/lib/thor/invocation.rb:120:in `invoke_command'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/thor-0.18.1/lib/thor.rb:363:in `dispatch'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/thor-0.18.1/lib/thor/base.rb:439:in `start'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/gems/backup-4.2.1/bin/backup:5:in `<top (required)>'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/bin/backup:23:in `load'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/bin/backup:23:in `<main>'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'
[2015/10/08 19:32:41][error]   /Users/Matthew/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `<main>'

After some debug, I found that the local.keep = 5 command was failing.  I've tried it with different numbers, same result.  If I disable the keep completely, the backup works perfectly.
Not sure if this is an issue with my configuration, or if this is a bug.   Considering this is a very simple backup, I assume it's a bug.
My specs:  Mac OSX 10.11 El Capitan, Backup 4.2.1 : ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-darwin14]
My backup file:
# encoding: utf-8

##
# Backup Generated: my_backup
# Once configured, you can run the backup with the following command:
#
# $ backup perform -t my_backup [-c <path_to_configuration_file>]
#
# For more information about Backup's components, see the documentation at:
# http://backup.github.io/backup
#
Model.new(:my_backup, 'Description for my_backup') do

  archive :my_archive do |archive|
    archive.root '~'
    archive.add "rails/misc/"
  end

  store_with Local do |local|
    local.path       = "~/backups/"
    local.keep       = 5
  end

  compress_with Gzip
end

I have this error too, when I'm trying analogy configuration.
My specs: ubuntu 14.04, Backup 4.2.1, ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]

I see where it's coming from. I'll fix it when I get home. For now you can use version 4.2.0 where it works.

I am experiencing this with db.keep being set in the dropbox configuration.
My specs: ubuntu 14.04, Backup 4.2.1, ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux]
I think that in the cycler.rb file, the cycle! method needs to check whether the excess is > 0 before setting cycled packages.
Locally I tried that (and reset my Dropbox location)  and it then works and cycles correctly.

I yanked 4.2.1 and will work on a fix

Thanks @tombruijn - I was just forking to create a pull request, but I will stop for now :)

@jamesjefferies I'm not saying that you shouldn't make a PR. Makes my live a little bit easier ;)

@tombruijn hope this PR makes your life a little bit easier ;)

Closed by #712
Released v4.2.2 with the fix


npm package CSS imports not working in unbundled build

Discussion here: https://www.pika.dev/npm/snowpack/discuss/401
Problem
When loading CSS from an npm package (import 'my-package/dist/styles.css'), the dev server runs fine but on snowpack build, that *.css.proxy.js file isn’t making it in the final build output.
Add that proxy file to snowpack build.

I've been trying to troubleshoot this and crack into the world of Snowpack/Rollup for roughly an hour now, but I haven't been able to make any progress at all. I've tried to add some console.logs to rollupPluginCss, just to get a sense of when it's called and with what parameters, but at some point the terminal screen is cleared and I can't see any of my logs...
I've also noticed that even if I comment out rollupPluginCss() from dist-node/index.js, CSS proxy files are somehow still being generated, even though I don't see any other plugin that could possibly be doing that, so it's all been really confusing and frustrating, and it's starting to remind me of WebPack way too much. I thought maybe it had something to do with caching, but CSS proxy files were still being generated even with --reload and rollupPluginCss() commented out. w00t?
It looks like I'm basically running into https://github.com/rollup/rollup/issues/1215 here. A few pointers to understand how to solve this would be nice, but making Snowpack/Rollup easier to debug would be ideal 😄

I believe that this was fixed by @drwpow in #595


I haven't looked into graphviz but I think the mermain graph looks fine, what's the problem with it?

Its "supposed" to resemble something like this

This has been implemented already


GPIO problem

In RPi_DALI_drv.c , it use GPIO_14 & GPIO_15 and it refer to Pi Click RST & Pi Click INT
however, according to the specifcation from Click,
https://download.mikroe.com/documents/add-on-boards/click-shields/pi-shield/pi-click-shield-schematic-v100.pdf
Connecting to DALI click (TX/RX) is using RST & INT but it is not GPIO_14 & 15
Is there any trick to use GPIO 14 & 15?
Now I can run the app and use the kernel module, but cannot control the Lights. It feels like not sending message to Dali Bus

It was supposed to be serial communication.
I am not sure about the final GPIOs used.
Indeed we had similar problems with lights control (seems like not sending message to Dali Bus). Perhaps use an oscilloscope to measure the output control signals frequency.
I have tried to find out a few things, but it is not feasible anymore, since as I said, the hardware setup is withdrawn. Neither of my collegaues in the team is at position to provide solutions. We are all heavily engaged in other projects. So, I can't see how I can help you any further.

I think the entire problem is below
RPI’s GPIO14 pin out, connected to RST pin in Pi click shield, is used to transmit commands (DALI_TX) to the DALI
LED driver. On the other hand, RPI’s GPIO15 pin in, connected to INT pin in Pi click shield, is used to receive feedback (DALI_RX) from the DALI LED driver
Understand that you may busy on other projects, but this research is awesome and less people is doing such things via RaspberryPi. Hope I can contribute more and expand the research works.
GPIO 14 is not connect to RST pin in Pi click shield. I purchased all the hardware equipment that mentioned in the research paper.
Hope you could give me some hints on how to get GPIO 14 to connect RST pin in Pi Click Shield via Serial connection

using the multimeter, I can verified that, the TX of DALI Board is sending out signal, that means, the GPIO mapping is cleared.
However, the DALI Bus is not sending signal out some how V_V


Starrocks spark connector reading a table with JSON type will cause an exception

error position:

Exception：

BackendClient: The status of open scanner result from StarRocks BE{host='xxxxx', port=xxxx} is 'INVALID_ARGUMENT', error message is: [Unknown primitive type(27)].

I think the spark connector doesn't support the JSON type.


replace --stake-verification-key-file with --deposit-return-stake-verification-key-file on all action commands

We disambiguated treasury withdrawals which require 2 stake credentials with --deposit-return-stake-verification-key-file and --funds-receiving-stake-verification-key-file.
Well, users will appreciate if we have the same clarity on all other action commands, so we want to replace the existing --stake-verification-key-file flag with the more descriptive  --deposit-return-stake-verification-key-file on all other governance actions
The same for --stake-verification-key and --stake-verification-key-hash
Replaced with
--deposit-return-stake-verification-key and
--deposit-return-stake-verification-key-hash, respectively.

Marking blocked, because solving this issue will affect the same places as:

https://github.com/input-output-hk/cardano-cli/pull/442
https://github.com/input-output-hk/cardano-cli/issues/447

So those two should be tackled first, to avoid merge conflicts hell. This will happen soon, so no worries about getting to this one soon.

Looking at --stake-verification-key-file, I believe the occurrences to change are as follows (red arrows):

I'm omitting:

the pStakeAddressCmds caller in Cardano.CLI.Legacy.Options, because it's legacy.
the pGovernanceActionTreasuryWithdrawalCmd caller. This one has been changed already, as stated in the issue's description.
the pStakeVerifier caller in Cardano.CLI.Erabased.Options.Cmd, because it goes into non-governance commands.


wip

This is already there in AppsmithRepository.

Test failure because of mocked mongo template, which needs to go away anyway in moving to Postgres.


pypi release broken (installing from github release is OK)

(myenv)root@201b2ba19e7c:~# pip install numba==0.22.0
Collecting numba==0.22.0
  Downloading numba-0.22.0.tar.gz (749kB)
    100% |████████████████████████████████| 749kB 932kB/s
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/tmp/pip-build-_puxbp2o/numba/setup.py", line 14, in <module>
        import versioneer
    ImportError: No module named 'versioneer'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-_puxbp2o/numba

But this works:
(myenv)root@201b2ba19e7c:~# pip install https://github.com/numba/numba/archive/0.22.0.tar.gz
Collecting https://github.com/numba/numba/archive/0.22.0.tar.gz
  Downloading https://github.com/numba/numba/archive/0.22.0.tar.gz
     - 1.1MB 11.9MB/s
Requirement already satisfied (use --upgrade to upgrade): llvmlite in ./pyenvs/myenv/lib/python3.4/site-packages (from numba==0.22.0)
Requirement already satisfied (use --upgrade to upgrade): numpy in ./pyenvs/myenv/lib/python3.4/site-packages (from numba==0.22.0)
Installing collected packages: numba
  Running setup.py install for numba
Successfully installed numba-0.22.0

looks like a duplicate for #1513.  Closing


Honor nested beforeEvaluate requests and others

Current Behavior
Consider this code in settings.gradle:
// settings.gradle
gradle.rootProject {
    beforeEvaluate {
        println "> Outer"
        beforeEvaluate {
            println "Inner"
        }
        print "< Outer"
    }
}

This now prints:
> Outer
< Outer

And the Inner part is silently ignored.
Expected Behavior
The nested requested should be honoured asynchronously and print:
> Outer
< Outer
Inner

Context
Hooks such as beforeEvaluate and afterEvaluate are used in a lot of ways to work around ordering problems, and it's easy to end up nesting two of them. Debugging such issues can be pretty hard.
See #3411 and #5200

@bamboo That syntax isn't supported in the Gradle Kotlin DSL. What is this in the scope of the gradle.rootProject?

Closing as closed in #5200


Test debugging in python using pythonVScode stopped working upon removal of command 'vscode.startDebug'

VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T12:32:39.870Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

Bookmarks
ale
0.17.0

vscode-standardjs
che
1.2.0

githistory
don
0.2.3

python
don
0.7.0

preview-vscode
sea
1.4.2

Steps to Reproduce:

Reproduces without extensions: Yes/No

Please report this against the Python extension your are using.


request: creates separate modules for server settings

Is there an existing issue or pull request for this?

[X] I have searched the existing issues and pull requests

Feature description
It would be good to separate the parameters into several independent modules.
I was thinking of three particular modules Birthday Announcement, Birthday Overview and Birthday Role.
They could be activated/deactivated independently depending on what the users want.
Desired solution
Here are the models you want:
model Birthday_Announcement {
    status         Boolean  @default(true)
    guildId        String   @id @map("guild_id") @db.VarChar(19)
    channelId      String   @map("channel_id") @db.VarChar(19)
    messageContent String   @map("message_content") @db.VarChar(2000)
    createdAt      DateTime @default(now()) @map("created_at")

    @@map("birthday_announcement")
}

model Birthday_Overview {
    status    Boolean  @default(true)
    guildId   String   @id @map("guild_id") @db.VarChar(19)
    channelId String   @map("channel_id") @db.VarChar(19)
    messageId String   @map("message_id") @db.VarChar(19)
    createdAt DateTime @default(now()) @map("created_at")

    @@map("birthday_overview")
}

model Birthday_Role {
    status    Boolean  @default(true)
    guildId   String   @id @map("guild_id") @db.VarChar(19)
    roleId    String   @map("role_id") @db.VarChar(19)
    createdAt DateTime @default(now()) @map("created_at")

    @@map("birthday_role")
}

Alternatives considered
An alternative would be to create several enter status in the Guild but that would make a lot of settings to my taste.
Additional context
No response

This is already done by just not setting the value. If a configuration is not set, it is automatically disabled! I don't see useful usecase where this could be applied to


Real Variable Type - Precision addition

For certain cases, the Real value data type might not need a default numpy precision for sampling, if we could set precision for every variable, that would prevent unnecessary exploration in the search space

First of all, thank you for your contribution!
The main problem I see here is that this only is used in the sampling. However, the mutation and crossover would still allow in any type of precision. An elegant way to restrict the search is implementing a Repair.
e.g.
from pymoo.core.repair import Repair
from pymoo.algorithms.moo.nsga2 import NSGA2
from pymoo.problems import get_problem
from pymoo.optimize import minimize
from pymoo.visualization.scatter import Scatter

import numpy as np

problem = get_problem("zdt1")

class RoundingRepair(Repair):

    def _do(self, problem, X, **kwargs):
        return np.round(X, decimals=1)

algorithm = NSGA2(pop_size=100, repair=RoundingRepair())

res = minimize(problem,
               algorithm,
               ('n_gen', 200),
               seed=1,
               verbose=True)

plot = Scatter()
plot.add(problem.pareto_front(), plot_type="line", color="black", alpha=0.7)
plot.add(res.F, facecolor="none", edgecolor="red")
plot.show()

For mixed variables, this would look a little different though (you would have to iterate over each variable and round it).
Or is your use case strictly restricted to having a specific precision during sampling?

Hi @blankjul ,
Thank you for your response. I tried the approach after modifying the code for my use case, using the following custom "Repair" class -
`class RoundingRepair(Repair):
        def _do(self, problem, X, **kwargs):
            m = pd.DataFrame(X).round(rounding_off_by_features).to_dict('records')
            vals = []
            for i in m:
                vals.append(list(i.values())[0]
            return vals`

Although, the res.X does not abide by the same laws, is there a way I can restrict mutation and crossover to also abide by the laws of precision I'm setting for each element in the decision space ?

Do you have a solution without pandas? So far pymoo does not have pandas as a dependency and I would not like to add it for one line of code at this point.

@blankjul I completely understand your concern. I tried this solution, although it involves for loops (which I ideally don't like to add to numpy calculations), but for my case, this worked perfectly. Please let me know your thoughts on this. I can help to test this comprehensively if needed.

Did you test the code above on a purely vectorized problem? For example, NSGA-II on ZDT1?
Without testing it I think it would break running on other problems.
Originally, I was not planning to add mixed variables because it breaks whenever a numpy array is expected. I think this is a very good example where operators don't really work for all variable types at the same time.


Should add to the Production note how to get a signature hash when using Google Play managed signing

The steps here are appropriate for getting the correct signature hash when using Google Play managed signing.
How to configure Signature Hash with Google Play Signing · Issue #1550 · AzureAD/microsoft-authentication-library-for-android

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

ID: 9257b263-b12e-4e0a-74d3-e2657567aed5
Version Independent ID: 7fe7472b-7f0d-b7c3-3202-c31cef3c2673
Content: How to enable cross-app SSO on Android using MSAL - Microsoft identity platform
Content Source: articles/active-directory/develop/msal-android-single-sign-on.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: marsma

@spoelstraethan
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

#reasssign: @henrymbugakiaire


Filter/search chores: show chores from a certain tag on the CLI, and other filters

After #33.

This issue has become obsolete. See #135.


Finish troubleshooting the server rebuild

Learned a few things today:

Never throw anything away when unboxing
Power supply (PSU) cables are not interchangeable

Am waiting for another cable to complete the rebuild. Then:

[x] Finish installing and testing hardware
[x] Assert the hard drive isn't fried
[x] Proceed to housekeeping tasks

The hard drive is fried. Most certainly. So I'll be replacing that.


Consolidate make functions

As part of the effort to consolidate common functionality and reduce reliance on auto-generated code, the "Make" methods are being moved to a central location.

@tst-sbayard You've got a commit on here that doesn't have your name on it, so the PR is flagged as not having CLAs signed. I think you can change it using this procedure: https://stackoverflow.com/questions/3042437/how-to-change-the-commit-author-for-one-specific-commit. @tst-basilhuffman this means you will have to rebase on the updated branch as well.

Unit tests, integration tests, and tutorial tests have passed for me, so aside from my previous comments everything looks good.


Units more separated from variables

Hi,
currently, units are entered like variables and only differ by the color. So when typing an equation, some variables have to be defined while others (whose symbols are the same as those of some units) are treated as units. It can become a bit confusing with larger equations when you get a result (incorrect one) even though a variable is undefined (because it's treated as a unit). Thus, I would like to suggest an optional (many users may not like it if it's obligatory) key stroke to enter units. Like in SMath where you have to press ' first before adding a unit symbol. Maybe it could also add space between the value and the unit (after all, that's the correct notation for msot units). I hope that it makes sense.

Hi! Maybe you are using an older version. :)
There is such an option already. Type a dot "." before the name to force it to be unit and make difference in case you have a variable with the same name. Also variables are italic and units are normal style. There is also a space before the unit.

There is such an option already. Type a dot "." before the name to force it to be unit and make difference in case you have a variable with the same name.

Thanks for the reply. I was thinking about something a bit different - adding an option to enable a mode where you are forced to press an additional key to enter a unit (e.g. you press ' or . and only then m becomes a unit). I know that many people wouldn't like it because it would increase the number of necessary key strokes so it should be optional. The benefit would be no more confusion and variables becoming units before they are defined (I often enter the equation first and then define its variables). Maybe it's not worth implementing but I thought that it could make sense to make it work similar to SMath. The ' or . symbol could even disappear for clarity or it could be a mode where you have to hold some key when adding a unit.

There is also a space before the unit.

Right, it just appears to be small sometimes so I thought there was no space ;-)


Fixing problems with custom color and image infowindow templates

It will fix https://github.com/CartoDB/cartodb/issues/10975.
Steps to test

Create a map of points with several columns.
Add a click popup and select the color one.
Select several columns.
Open a popup in order to see it.
Choose html and check that the html is representing the same thing you chose in the form (visit https://github.com/CartoDB/cartodb/issues/10975 in order to check differences).
Same for image 💋 .

This work as expected. One thing I noticed (out of scope, happening in production) is that if you sort the selected fields, when the form is render again, the selected fields are put at the bottom. likely outside of the view because of the scroll:

Not sure if we should render those fields at the top.

Ouch, could you open a ticket with that please? Let's try to fix in another ticket. Thanks for that!

On premise failed because an ECONNREFUSED trying to download phantomjs. I'm deploying 🚀


Feature Request
Describe the Feature Request

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

Originally posted by @gator6615 in https://github.com/dogecoin/dogecoin/issues/2199

Possibly a spam issue.


Not possible to bind through ng-model

I've trying to use ng-model="aModel" inside js-tag element. But nothing gets bound.
With this code, as in the examples, I can get the value selected through $scope.tags.tags:
$scope.tags = new JSTagsCollection([]);
$scope.jsTagOptions = {
  'tags': $scope.tags,
  "texts": {
    "inputPlaceHolder": "diag..."
  },
  'edit': false,
  'breakCodes': [13, 32] //32 for space
};

The format of the value of $scope.tags.tags I get is
{"0":{"value":"first","id":0},"1":{"value":"next","id":1}}

The keys "0", "1" and the property "id" need some explanation.
Thank for opening your code. It's been of great value for me.

Thank you for opening the issue both will be fixed.
As you saw in the documentation there is currently another way to access the JSTagCollection object and the tags inside.


Adding Matt Parker

Accept me please
i will bribe @Devoxin for this

This pull request was created using the https://discordbots.co.uk/edit menu.

closes


BER decoding failed

I am trying to make certlint work on Windows, but when I run it gives the following error:
ruby -I lib:ext c:\certlint\bin\certlint c:\Temp\test-cert.der
F: ASN.1 Error in Certificate: BER decoding failed at octet 408: Unexpected end of input        test-cert.der
Cablint works just fine FWIW.

This is almost certainly caused by the input certificate not being well-formed BER.  Can you share the input file that is failing?

I did try on Gmail certificate:
ruby -I lib:ext C:\certlint\bin\certlint C:\Temp\gmailcert.cer
F: ASN.1 Error in Certificate: BER decoding failed at octet 151: Unexpected end of input        gmailcert.cer
Please find it attached.
Thank you!
gmailcert.zip

@mpalmer did you get a chance to investigate this?


Remove character count when checking for existing petitions

Drop the character counter (as it is a guide only) and truncate action
at 255 instead of 80

Nice and simple, putting this through


Child modal closes parent

Is there any way of having two modals open at the same time?
If I open a modal from another modal, it will close the parent and then open the child.

If you close the child modal the parent open will open again automatically.


Added touch event support

Hey,
I have added multi touch support to this regardig https://github.com/Fuzzyma/svg.resize.js/issues/7
I am in a bit of rush so my apologies for the duplicate function wrappers 168-178.

Awesome (again^^). I have to review that one :)


review img-to-doc-csv.yml & img-to-doc-csv.py (last line)

there is an error related to the output file path indicated in the img-to-doc-csv.py https://github.com/auden-in-austria-digital/aad-data/blob/cd2156d7bc93bda6a1826ddc8bf63e8382871b97/scripts/img-to-doc-csv/img-to-doc-csv.py#L45
 Traceback (most recent call last):
  File "/home/runner/work/aad-data/aad-data/scripts/img-to-doc-csv/img-to-doc-csv.py", line 45, in <module>
    transform_csv('https://raw.githubusercontent.com/auden-in-austria-digital/aad-data/main/doc-data/csv/img_doc_id.csv', 'doc_id', 'img_id', '../../doc-data/csv/doc_img_id')
  File "/home/runner/work/aad-data/aad-data/scripts/img-to-doc-csv/img-to-doc-csv.py", line 33, in transform_csv
    with open(output_file, 'w', newline='', encoding='utf-8') as newfile:  # open/create output CSV file in write mode
FileNotFoundError: [Errno 2] No such file or directory: '../../doc-data/csv/doc_img_id.csv'
Error: Process completed with exit code 1.

the path does work when run locally, but not when run in the GitHub Actions environment

from where do you run the script locally? because running it from the root fails on my machine as well.
changing the last line to:
transform_csv('https://raw.githubusercontent.com/auden-in-austria-digital/aad-data/main/doc-data/csv/img_doc_id.csv', 'doc_id', 'img_id', './doc-data/csv/doc_img_id') works

works, thank you very much for your help


main readme group review for v1

Please review and suggest any needed changes in preparation for v1 release.
We'll try to do this for most docs to get multiple reviewers.
Contributing issue: TBA
Original PR: https://github.com/open-telemetry/opentelemetry-demo/pull/451

We could potentially tighten this up some more. Maybe link only to the docs readme instead of the contents list.
Features and tests could be segmented out as well. Open to suggestions


Rename @Incoming and @Outgoing topic

Right now the @Incoming and @Outgoing annotations have a topic attribute. The word topic does not always make sense depending on the transport layer.
We can change it to:

value - so we can use @Incoming("my-source")
from and to:

@Incoming(from="my-source")
@Outgoing(to="my-destination")
public void PublisherBuilder<String> doSomething(Publisher<Integer> source) {
    // ...
}

Agree that topic does not always make sense.
Not sure about value, since if you want to pass multiple parameters to the annotation, then you need to say value="my-source", which is a bit odd.
from and to make sense, though I wonder whether something even more generic, such as name (which you mentioned in #43), would be better.

Yes, name might we simpler, better and symmetric.

The argument for "value" depends on how frequently the annotation will not have more than one parameter. Name seems inoffensive to me.

@hutchig there is at least the providerattribute - not necessary set, but they are use cases where it needs to be set. We are also discussing theconfig-key` attribute in #43 (the attribute name may change).

The discussion that we had in the Reactive Hangout on Tuesday was that we should change it to value. The reason for this is that the rest of the parameters that are likely to be added to Incoming and Outgoing are in most common use cases going to be left as the default, so the name value will rarely show in user code. The result is, for most cases, user code code will be more readable as it will just be Incoming("foo"), and the name of the parameter won't get in the way with the underlying naming used by the message broker.

I will open a PR with the change.

Migrated to https://github.com/eclipse/microprofile-reactive-messaging/issues/8.


Adding a zfs backed disk doesn't create the storage

I am trying to add a second disk backed by zfs I have the following in my file:
    disk {
        id = 0
        size = 64
        type = "scsi"
        storage = "storage"
        storage_type = "zfspool"
    }

    disk {
        id = 2
        size = 128
        type = "scsi"
        storage = "storage"
        storage_type = "zfspool"
    }

The plan executes happily and all seems well, but the second disk is never created. In the proxmox console I see under the "configure" task for the VM:
**TASK ERROR: zfs error: cannot open 'storage/vm-114-disk-2': dataset does not exist**

It seems it's not creating the underlying storage before it tries to use it? Have I missed a step or something?
The first disk is there as I would expect (but I think it's copied from the template anyway).

Hi,
I just succeeded, inspired of your config to correct my mistake. But...
Your error seems to indicate that your dataset does not exist, which I find a bit deceiving since the value for storage in my setup IS NOT my actual dataset name, but the storage name I choose to attach to a dataset (name you can get in your proxmox webUI::Datacenter/storage).
I think it's worth checking (and for the dev team, maybe change the error message ?).
Also, are you sure [ you're not | you don't want to ] use 'virtio' ?
My working config:
  disk {
    id              = 0
    size            = 20
    type            = "virtio"
    storage         = "local-zfs"
    storage_type    = "zfspool"
    iothread        = true
  }

Hope it helps,
Good luck !


[Test] Mark distributed_actor_remoteCall_argument_labels.swift unsupported for use_os_stdlib.

This is already unsupported on back_deployment_runtime, but we also want to mark it unsupported on use_os_stdlib for old OSes that shipped with a stdlib.

@swift-ci please smoke test

LGTM thank you @mikeash !

@swift-ci please smoke test Linux


Unable to runsupabase init

Bug report
Describe the bug
When running supabase init I get the following error:
Error: Project already initialized. Remove supabase/config.toml to reinitialize.
Try rerunning the command with --debug to troubleshoot the error.

The --debug displays no extra info
To Reproduce
temp-folder $ mkdir temp
temp-folder $ cd temp
temp (main) $ supabase init
Error: Project already initialized. Remove supabase/config.toml to reinitialize.
Try rerunning the command with --debug to troubleshoot the error.
temp (main) $ ls
temp (main) $

Expected behavior
Initialise a new supabase project locally
Screenshots
N/A
System information
Mac M1
Additional context
I do have supabase/config.toml in other directories, but I really do not want to delete them just to make a new project work. And I am sure I have been able to setup supabase locally at different locations before (not simultaneously obviously).
I have tried uninstalling and reinstalling supabase CLI, deleting docker containers, images and volumes which are used by Supabase.

closing as not reproducible

Hi. I installed CLI version 1.33.0 and having the same issue:
temp-folder $ mkdir temp
temp-folder $ cd temp
temp-folder $ supabase -v
1.33.0
temp (main) $ supabase init
Error: Project already initialized. Remove supabase/config.toml to reinitialize.
Try rerunning the command with --debug to troubleshoot the error.
temp (main) $ ls
temp (main) $

Also tried with latest 1.34.2
$ supabase -v
1.34.2

Found the issue, a supabase directory was at $HOME/supabase. Once I removed that I was able to initialize within the project.


The ability to download images taken on Strabo to your device

User request...
Is your feature request related to a problem? Please describe.
Images don't save to the Camera Roll on device
Describe the solution you'd like
Saving the images to the Camera Roll on device.
Describe alternatives you've considered
A toggle button letting the user choose to save the images to the camera roll.

added feature with commit b4bf2fc6651b61f99a2ec4828f11d073cf7dd698. Currently saves images automatically.


Opponent disconnected from game - alert player

alert player that the opponent has disconnected, send player back to home screen on confirm

duplicate?


irrlicht:blocked on macOS

This port is blocked on macOS but this platform is supported. From the Irrlicht website:
The Irrlicht Engine is platform independent, currently there is official support for:
XP, XP64, Vista, CE, Windows 7,Windows 8 and Windows 10
Linux
OSX
Sun Solaris/SPARC
All platforms using SDL

SDL is also available on ARM so Irrlicht being blocked for that target is likely also a mistake but a separate issue.

Hi @virtualritz
Thanks for posting this issue.
Currently, irrlicht  failed on osx due to these errors:
In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/COpenGLDriver.cpp:21:
3391 /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/MacOSX/CIrrDeviceMacOSX.h:12:1: error: unknown type name '_'
3392 _
3393 ^
3394 In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/COpenGLDriver.cpp:21:
3395 In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/MacOSX/CIrrDeviceMacOSX.h:13:
3396 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:8:
3397 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSArray.h:5:
3398 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObject.h:7:
3399 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:492:1: error: expected u     nqualified-id
3400 @class NSString, Protocol;
3401 ^
3402 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:494:9: error: unknown ty     pe name 'NSString'
3403 typedef NSString * NSExceptionName NS_EXTENSIBLE_STRING_ENUM;
3404         ^
3405 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:495:9: error: unknown ty     pe name 'NSString'
3406 typedef NSString * NSRunLoopMode NS_EXTENSIBLE_STRING_ENUM;

But I don't know how to fix this problem.
@strega-nil  Do you have any suggestions about this issue?

This I do not know. I can look at it next week, perhaps?

It looks like you are trying to compile Irrlicht/COpenGLDriver.cpp with a C++ compiler, but you have to use an ObjC compiler instead:
Getting error while using ObjC class include in .cpp file (unqualified-id @class)

iOS build error: expected unqualified-id @class NSString

Hi @virtualritz
Thanks for posting this issue.
Currently, irrlicht  failed on osx due to these errors:
In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/COpenGLDriver.cpp:21:
3391 /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/MacOSX/CIrrDeviceMacOSX.h:12:1: error: unknown type name '_'
3392 _
3393 ^
3394 In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/COpenGLDriver.cpp:21:
3395 In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/MacOSX/CIrrDeviceMacOSX.h:13:
3396 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:8:
3397 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSArray.h:5:
3398 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObject.h:7:
3399 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:492:1: error: expected u     nqualified-id
3400 @class NSString, Protocol;
3401 ^
3402 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:494:9: error: unknown ty     pe name 'NSString'
3403 typedef NSString * NSExceptionName NS_EXTENSIBLE_STRING_ENUM;
3404         ^
3405 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:495:9: error: unknown ty     pe name 'NSString'
3406 typedef NSString * NSRunLoopMode NS_EXTENSIBLE_STRING_ENUM;

But I don't know how to fix this problem.
@strega-nil Do you have any suggestions about this issue?

I do not know if it related, but the homebrew's Formula of irrlicht has two macOS-specific patches to the 1.8.4 codebase, one of which is related to the source/Irrlicht/MacOSX/CIrrDeviceMacOSX.m source code, perhaps it could make sense to try to use them also in the vcpkg port of irrlicht.

Hi @virtualritz
Thanks for posting this issue.
Currently, irrlicht  failed on osx due to these errors:
In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/COpenGLDriver.cpp:21:
3391 /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/MacOSX/CIrrDeviceMacOSX.h:12:1: error: unknown type name '_'
3392 _
3393 ^
3394 In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/COpenGLDriver.cpp:21:
3395 In file included from /Users/vcpkg/Nancy/vcpkg/buildtrees/irrlicht/src/de69ddd2c6-1cdb4cb3bd/source/Irrlicht/MacOSX/CIrrDeviceMacOSX.h:13:
3396 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:8:
3397 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSArray.h:5:
3398 In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObject.h:7:
3399 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:492:1: error: expected u     nqualified-id
3400 @class NSString, Protocol;
3401 ^
3402 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:494:9: error: unknown ty     pe name 'NSString'
3403 typedef NSString * NSExceptionName NS_EXTENSIBLE_STRING_ENUM;
3404         ^
3405 /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:495:9: error: unknown ty     pe name 'NSString'
3406 typedef NSString * NSRunLoopMode NS_EXTENSIBLE_STRING_ENUM;

But I don't know how to fix this problem.
@strega-nil Do you have any suggestions about this issue?

I do not know if it related, but the homebrew's Formula of irrlicht has two macOS-specific patches to the 1.8.4 codebase, one of which is related to the source/Irrlicht/MacOSX/CIrrDeviceMacOSX.m source code, perhaps it could make sense to try to use them also in the vcpkg port of irrlicht.

Furthermore, the homebrew formula is using the included Xcode build system (https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/irrlicht.rb#L40), while the vcpkg port is using a custom CMake build system.

Furthermore, the homebrew formula is using the included Xcode build system (https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/irrlicht.rb#L40), while the vcpkg port is using a custom CMake build system.

Another useful reference is patch https://sourceforge.net/p/irrlicht/patches/320/ by @shybovycha that provides a CMake build script for irrlicht that seems to support macOS as well.

Another useful reference is patch https://sourceforge.net/p/irrlicht/patches/320/ by @shybovycha that provides a CMake build script for irrlicht that seems to support macOS as well.

I am not currently interested in having irrlicht working on vcpkg on macOS, but for anyone interested in getting this to work in https://github.com/conda-forge/staged-recipes/pull/13900 I added a conda-forge recipe for irrlicht, and the fix to the CMake build system to fix the compilation were the following.

Remove the -no-rtti flag in https://github.com/microsoft/vcpkg/blob/2020.11/ports/irrlicht/CMakeLists.txt#L190
Add a block to add .mm files to the compilation and enable Objective C++ compilation for mixed files (https://github.com/conda-forge/staged-recipes/pull/13900/files#diff-2c220af85fe5d0a51fea98e69ead2630be651545ff3f2912005aa5cc91cfb6d7R99):

if(APPLE)
    file(GLOB IRR_SRC_FILES_MACOS "${IRR_SRC_DIR}/MacOSX/*.mm" "${IRR_SRC_DIR}/MacOSX/*.h" )
    list(APPEND IRR_ALL_SRC_FILES ${IRR_SRC_FILES_MACOS})
    set_source_files_properties("${IRR_SRC_DIR}/Irrlicht.cpp" PROPERTIES COMPILE_OPTIONS "-x;objective-c++")
    set_source_files_properties("${IRR_SRC_DIR}/COpenGLDriver.cpp" PROPERTIES COMPILE_OPTIONS "-x;objective-c++")
endif()

Add a block to link macOS's System Frameworks ( https://github.com/conda-forge/staged-recipes/pull/13900/files#diff-2c220af85fe5d0a51fea98e69ead2630be651545ff3f2912005aa5cc91cfb6d7R225 ):

    if(APPLE)
        find_library(COCOA_LIB Cocoa)
        find_library(CARBON_LIB Carbon)
        find_library(IOKIT_LIB IOKit)
        target_link_libraries(Irrlicht PRIVATE ${IOKIT_LIB} ${COCOA_LIB} ${CARBON_LIB})
        target_compile_definitions(Irrlicht PRIVATE MACOSX)
        target_include_directories(Irrlicht PRIVATE ${IRR_SRC_DIR}/MacOSX)
    endif()

Hi all,
irrlicht has supported osx in vcpkg now, please try to update to the latest vcpkg to rebuild this port.


Fix: set-default-repositories-type-to-sources changes unrelated URLs

Currently all tabs get the ?type=source
Test URLs
https://github.com/microsoft
Screenshot
None

Let's rename set-default-repositories-type-to-sources to something shorter at some point 😅


SpeechLM：KeyError: 'text_transformer' while initing the SpeechLMConfig

Hi，I'm trying to use the script in README to Extract features using pre-trained models, I used the model  speechlmp_base_asr_checkpoint_best.pt.But I encountered an error while initing the SpeechLMConfig：

Traceback (most recent call last):
File "/remote-home/jzhan/SpeechT5/SpeechLM/test.py", line 7, in
cfg = SpeechLMConfig(checkpoint['cfg']['model'])
File "/SpeechT5/SpeechLM/SpeechLM.py", line 128, in init
self.update(cfg)
File "/SpeechT5/SpeechLM/SpeechLM.py", line 132, in update
self.text_transformer = TransformerConfig(model_cfg['text_transformer'])
KeyError: 'text_transformer'

Am I missing any model files?

Hello, @guokr233
For now, only pre-trained models could be directly used to extract features, you have 3 choices of the model as the readme provided,

While the one you used, speechlmp_base_asr_checkpoint_best.pt, is a fine-tuned ASR model, which can not be directly loaded by SpeechT5/SpeechLM/SpeechLM.py.

The configuration descriptions saved in checkpoints are different between pre-trained models and fine-tuned models, that's why you got this error when loading fine-tuned models.

What's the difference between the models listed in the above figure and the models listed in the Pre-Trained and Fine-tuned Models Table? The 3 models listed in the above figure are made from the original checkpoints by copying parameters and removing unused modules.

Hope the above information helps you.

I used the model mentioned in "Extract features using pre-trained models"，it worked，thank you very much！


at_c: discussion on removing string lengths as part of function signature

Brief Overview
We want to remove string lengths from all function signatures and simply assume that the programmer is passing in a null-terminated string.
Issue
Here is an example of the problem at hand:
int atclient_atnotification_set_encKeyName(atclient_atnotification *notification, const char *encKeyName, const size_t encKeyNamelen);

// Frequently, this function would be called like this:

atclient_atnotification_set_encKeyName(&atnotification, "123abc", strlen("123abc"));

But the proposal is to remove string lengths and to always assume null-terminated strings.
// So it would be called like this after this discussion is passed and approved:
atclient_atnotification_set_encKeyName(&atnotification, "123abc");

The reason why we want to remove string length is because it can get repetitive, tedious and an eyesore when debugging code. This function for example has at most 4 strings in its function signature which ends up being 9 function arguments. yuck!
int atclient_atkey_create_publickey(atclient_atkey *atkey, const char *name, const size_t namelen, const char *sharedby,
 const size_t sharedbylen, const char *namespacestr, const size_t namespacestrlen);

// Example call

atclient_atkey_create_publickey(&atkey, "name", strlen("name"), "@jeremy", strlen("@jeremy"), "@xavier", strlen("@xavier"), "wavi", strlen("wavi");

// What we want it to be

atclient_atkey_create_publickey(&atkey, "name", "@jeremy", "@xavier", "wavi");

Cons
Someone may not have the null-terminated strings on-hand and have them in something like a buffer.
For example, I could do something complicated like this
char my_string[] = "name|bob|jeremy"
atclient_atkey_create_publickey(&atkey, my_string[0], 4, my_string[5], 3, my_string[9], 6);

If this ticket is approved, their new implementation could be something a little more tedious like this:
char my_string[] = "name|bob|jeremy";
my_string[4]='\0'
my_string[8]='\0'
my_string[15]='\0'

But even this doesn't work all the time. What if their string buffer was no delimited. Then they would have to do some funky string splitting.
Alternatives
We could provide two function signatures for the caller to have the flexibility, but our code base could become quite bloated.
For Example, we could follow the strcmp/strncmp where they provide options on assuming a null-terminated string vs. providing a string length:
strcmp("jeremy", "jeremy123") != 0
strncmp("jeremy", "jeremy123", 6) == 0

Naming could be something like this:
// _s function hedaer
atclient_atkey_create_publickey_s(atclient_atkey *atkey, const char *name, const char *sharedby, const char *sharedwith, const char *namespacestr);

// _sn function header
atclient_atkey_create_publickey_sn(atclient_atkey *atkey, const char *name, const size_t namelen, const char *sharedby, const size_t sharedbylen, const char *sharedwith, const size_t sharedwithlen, const char *namespacestr, const size_t namespacestrlen);

From @XavierChanth :

My 2 cents on the con listed in that ticket: yes, we lose some flexibility with null terminated strings. But the only time where a null terminated string is actually going to limit you is if you try to hyper optimize your program. At that point, you are sacrificing a lot of maintainability and creating a surface for bugs and thus I don’t think it is very practical to worry about it. There are going to be much better and safer ways to optimize first, if someone really wants to optimize further, we can leave it to them to override the implementation with a more optimal solution for their specific scenario.

Oh I missed this until now - +1 to @XavierChanth's comments ... null-terminated strings gets my vote for sure

I've got +2 for null-terminated strings so I will be editing the title and allocating SP.

I would like to make the decision to keep strlengths as part of the function signatures in atchops exclusively because there comes a lot of good situations where it is better to provide string lengths.
For example,
int atchops_rsa_sign(const atchops_rsakey_privatekey privatekey, const atchops_md_type mdtype,
                     const unsigned char *message, const size_t messagelen, unsigned char *signature)

It would be easy to do something like this:
const char *data = "data:abcdefghijk";
atchops_rsa_sign(&privatekey, ATCHOPS_MD_SHA256, data + 5, strlen(data) - 5);

No string manipulation was required
Another benefit of having string lengths in atchops is that no work needs to be done because it is already implemented like this everywhere in atchops