PushNotificationIOS

@MoOx @sgny FYI: I started to work on PushNotificationIOS.

Thanks for that. I started on that but cast it aside as I don't have time to figure out all types and couldn't test on a real device for the moment. I have included my draft below, perhaps it would be of help to you.
type path;
type category;
type userInfo;

type handler;

type d;

type error = {
  .
  "message": string,
  "code": int,
  "details": d,
};

external fromObject: (pushNotificationIOS => unit) => handler = "";
external fromHexString: (string => unit) => handler = "";

type permissions = {
  .
  alert: option(bool),
  badge: option(bool),
  sound: option(bool),
};

type t1;
<EMAIL_ADDRESS>external t1:
(
  ~alertBody: string,
  ~alertAction: string=?,//The "action" displayed beneath an actionable notification. Defaults to "view";
  ~soundName: path=?, //The sound played when the notification is fired (optional).
  ~isSilent: bool=?, //If true, the notification will appear without sound (optional).
  ~category: string=?, // The category of this notification, required for actionable notifications (optional).
  ~userInfo: userInfo=?, // An optional object containing additional notification data.
  ~applicationIconBadgeNumber: int=?
unit
) =>
t1 =
"";

type fireDate;

type t2;
<EMAIL_ADDRESS>external t2:
  (
    ~fireDate : fireDate,
    ~alertTitle: string,
    ~alertBody: string,
    ~alertAction: string=?,//The "action" displayed beneath an actionable notification. Defaults to "view";
    ~soundName: path=?, //The sound played when the notification is fired (optional).
    ~isSilent: bool=?, //If true, the notification will appear without sound (optional).
    ~category: string=?, // The category of this notification, required for actionable notifications (optional).
    ~userInfo: userInfo=?, // An optional object containing additional notification data.
    ~applicationIconBadgeNumber: int=?
    ~repeatInterval<EMAIL_ADDRESS>[ | `minute | `hour | `day | `week | `month | `year ]=?,
    unit:
  ) =>
  t2 =
  "";

type t3 = {
  .
  "identifier": string,
  "title": string,
  "body": string,
  "category": Js.Nullable.t(category),
  "userInfo": Js.Nullable.t(userInfo),
  "thread-id": Js.Nullable.t(string),
};

type func1 = array(t3) => unit;

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
external presentLocalNotification: t1 => Js.Promise.t()

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
external scheduleLocalNotification: t2 => unit = "";             // unit may be incorrect

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
external cancelAllLocalNotifications: unit => unit = "";        // unit may be incorrect

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
external removeAllDeliveredNotifications: unit => unit = "";    //  √

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
external getDeliveredNotifications: func1 => unit = "";         // need to determine object's type

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
removeDeliveredNotifications: array(string) => unit = "";      // √

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
setApplicationIconBadgeNumber: int => unit = "";                // √

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
getApplicationIconBadgeNumber: (int => unit) => unit = "";     // √

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
cancelLocalNotifications: userInfo => unit = "";

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
addEventListener<EMAIL_ADDRESS>[ | `notification | `register | `registrationError | `localNotification ], handler) => unit = "";

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
removeEventListener<EMAIL_ADDRESS>[ | `notification | `register | `registrationError | `localNotification ], handler) => unit = "";

<EMAIL_ADDRESS>"react-native"]<EMAIL_ADDRESS>"PushNotificationIOS"]
requestPermissions: permissions => Js.Promise.t(permissions) = "";

// todo

// abandonPermissions
// checkPermissions
// getScheduledLocalNotifications
// getInitialNotification
// constructor
// finish

Thanks!

Done in #458.


trailingCommas

life is easier, if trailing commas are everywhere
especially for git: history and rebasing
(it has happened to me sometimes that git rebase (or was it merge?) broke because of absence of commas)
the commas will be automatically added (IntelliJ will add them on every save), so this should be an effortless rule

@augi @hanny24 @tomasherman
I would like us to start using trailingCommas, I think it is a good practice
we can kicking off the discussion with this PR

I'm sorry but after I've gone through the code... TBH honest I'm confused by some pieces of code :smiley:
I like the trailing comma for varargs (multiline Seq(... ...)), I'm able to survive it in SBT config and imports, but adding trailing comma after last parameter of function - :no_entry_sign: please. It doesn't happen very often but now I agree with @jakubjanecek :wink:

My 2 cents: if we were to use scalastyle , we would end up with a bad time:( Maybe it's solved by newer version of scalastyle)

i am not a fan of trailing commas - they make life a little bit easier but they add more noise and make code more confusing :( i don't like that scalafmt should be adding them everywhere automatically
i don't see how they make working with git easier - can you elaborate?


Reproducing VCMR results for didemo video only

Hi @linjieli222,
I have reproduced didemo_video_only, the results results I reproduced are much better than those in the paper.
The reproduced results are as follow:
672 03/02/2022 21:22:48 - INFO - main -   validation finished in 3 seconds
673 03/02/2022 21:22:51 - INFO - main -   start running  full VCMR evaluationon didemo_video_only test split...
674 03/02/2022 21:22:54 - INFO - main -   metrics_no_nms_VCMR
675 {   '0.5-r1': 3.590012556504269,
676     '0.5-r10': 16.97737066800603,
677     '0.5-r100': 44.225404319437466,
678     '0.5-r5': 11.299871923656454,
679     '0.7-r1': 2.9875866398794573,
680     '0.7-r10': 14.11497237569061,
681     '0.7-r100': 37.99495228528378,
682     '0.7-r5': 9.289997488699145}
 And the results in paper:

I don't find the reason for this result.

Hi there,
Thanks for your interests in our HERO project. The release checkpoint is a stronger pre-trained model with longer pre-training steps than what's reported in the paper.


How can we check the /health status of our UAA deployment

Is there an application /health uri that can be enabled like in some of the SpringBoot applications that would show the basic status of the application?  We need to register some reliable mechanism in Kubernetes to check the application status so it can be aware when the application becomes unstable and may require a re-start.
What version of UAA are you running?
"app":{"version":"74.7.0"}
How are you deploying the UAA?
Helm deploy into a Kubernetes 1.16 cluster
I am deploying the UAA

helm deploy command into a running Kubernetes cluster

/healthz is the uaa monitoring endpoint. It will check the tomcat is reachable, but will not check for uaa state or healthy DB connection.

Thanks @mwdb!


(Added)[JIRA-2751] Adding post payment flow support for SEMOVI

What have changed?
Adding a new PXPostPaymentConfiguration in MercadoPagoCheckoutBuilder in order to support navigation to integrator post payment flow.
This navigation to the post payment flow will be possible due to the implementation of a new series of notifications MercadoPagoCheckout.NotificationCenter that will tell the integrator whenever they should start their new custom flow and will provide a resultBlock where the integrator will be able to return a PXBasePayment to the PX flow in order to show a custom congrats.
New Clases Added in MercadoPagoSDK:

PXPostPaymentConfiguration  Config class used in the builder to enable the post payment flow
MercadoPagoCheckout.NotificationCenter.SubscribeTo This extension allows integrators to suscribe to post payment notification
MercadoPagoCheckout.NotificationCenter.PublishTo This extension allows PX to post the post payment notifications
MercadoPagoCheckout.NotificationCenter.UnsubscribeTo This extension allows integrators to unsubscribe observers for post payment flow

New Classes Added in ExampleSwift (Only used for testing):

CustomCheckoutWithPostPaymentViewController New view controller that provides an entry point to the post payment flow
PostPaymentViewController New view controller that will be called after getting the post payment notification
CustomPostPaymentProcessor Custom processor used for adding post payment test cases

How to test:
The integration documentation can be found in the following link:
https://docs.google.com/document/d/1ND4qQlo_MmOfySHX-B5yB8PjIYhJhPxf1JSMPeVM5GU/edit#
Prints for layout changes:

SEMOVI Integrated in SP
SEMOVI Success
SEMOVI Failure
SEMOVI Payment Failure

Extras:
Current Unit tests are passing successfully but more will be added in a separate PR.

Unit Tests

          1 Error

:no_entry_sign:
The PR title should follow the title convetion: (Added,Changed,Deprecated,Removed,Fixed,Security)[JIRA-XXX] - (brief description here)

          1 Warning

:warning:
SwiftLint also found 67 more violations with this PR.

          1 Message

:book:
JIRA: JIRA-2751

Current coverage for MercadoPagoSDKV4.framework is 3.14%

Files changed
-
-

PXPaymentFlowModel.swift
0.00%
:skull:

PXNotificationManager.swift
0.00%
:skull:

OneTapFlowModel.swift
0.00%
:skull:

MercadoPagoCheckout.swift
0.00%
:skull:

PXPaymentFlow.swift
0.00%
:skull:

MercadoPagoCheckoutViewModel.swift
0.00%
:skull:

MercadoPagoCheckout+NotificationManager.swift
0.00%
:skull:

LocationService.swift
0.00%
:skull:

PXAnimatedButton.swift
0.00%
:skull:

PXPaymentFlow+Services.swift
0.00%
:skull:

MercadoPagoCheckoutBuilder.swift
20.00%
:skull:

Powered by xcov

  Generated by :no_entry_sign: Danger


SITL (jMAVSIM)  broken on master

@tumbili Would be great if you could have a look as soon as feasible.
To repro:
make posix jmavsim
pxh> commander takeoff

@LorenzMeier also gazebo SITL stopped working for me on master, Iris and Standard VTOL. Takeoff makes it crash pretty much right away.

https://github.com/PX4/Firmware/issues/3990

Fixed


Assets: Implement Inactive balance tracking in Assets pallet

Balances pallet tracks the inactive balance, allowing an accurate active issuance amount to be calculated. Assets pallet doesn't have this functionality, so for things like checking accounts where one or more accounts have a balance which is fundamentally unusable, the total issuance becomes potentially quite far away from the real issuance.
It should be introduced.

I'd love to work on this @gavofyork

This is somehow related to https://github.com/paritytech/substrate/issues/13253


Support create java function project

Work Item: #48
Support create java function project. Currently we will use Maven archetype (call mvn cli) to create a Java typed function project. And we'll change it to function cli when the related part in cli is ready.
UI:

Todo:

Add Java function (#49)
deploy Java function (#50)

-------------- Update on Wed Nov 08 2017 09:59:31 GMT+0800 (China Standard Time) --------------
Add code to support add Java function.

Using Maven plugin to do this job.
Confirmed from Maven plugin team, this command has no batch mode, so I send it to terminal and user can fill in the parameter in the terminal
Currently, we determine whether the project is Java based or not by finding pom.xml in the selected folder.

Close this PR since the code structure has changed largely. See #66


Expose Timer API on OpenThread Instance.

This PR just exposes Timer related APIs for application layer of baremetal OpenThread stack. Users can utilize the otInstance class to call Timer related APIs.

I'm not sure Openthread should be in the business of providing Kernel / System level services to an application.

@pvanhorn @bukepo Thanks for your suggestion and concern. This PR was intended to expose related APIs for one Timer instance to handle periodic tasks in users' single-thread application in case of only running baremetal OpenThread stack. That seems to be more overhead for attaching an underly OS just for a single-thread application. The choice of whether or not utilizing OpenThread Timer API will be up to users according to their practical case. Meanwhile considering the restricted RAM size of embedded devices, I'm not sure if it is a good idea to allow users to allocate the desired memory per their requests. Maybe in this case we really need one OS to support multiple timer and tasks schedule instead of OpenThread itself in a powerful chip. Thoughts? Thanks.

My thoughts are that Openthread should limit itself to providing wireless communication through a Thread network.  I feel a timer API is outside the intended scope.

I also lean towards having timer functionality be provided by the underlying platform/OS to the application (even in baremetal case) and not have it as an OT API.

It's argueable if it's in the scope but I still think it comes in handy and is just a very small change, as it's already there.

My vision of OpenThread aligns with @pvanhorn and @abtink comments (to not provide OT API to internal stack timer and so timer scheduler).
However if its realy needed, maybe we can make it optional in configure.ac like we did with CoAP or DNS Client right now?

Yes, we should limit OpenThread to focus on Thread networking. However, it's really handy when there's no underlying platform/OS and user just wanna make simple products. I think that's why we also provided application CoAP API.

I find the different views on how Openthread should evolve, very interesting.  I'm always surprised when I encounter views that differ so strongly with my own.  Human nature I guess.  In any case, I do feel strongly that Openthread should work very hard to limit its feature set to its core responsibilities; Thread networking.  If we abandon this tenet, it is my belief, we will find ourselves sliding down a slippery slope, forced to adopt an ever growing set of responsibilities that have little to do with moving packets on a Thread network. The larger the code base, the more maintenance effort is required and its this growing burden that I want to contain.
Previously we had a similar discussion about providing a flash API (read, write, erase you get the idea).  This API was in some cases needed for OT Settings storage (there is no rule that says settings must be stored in flash). In the end we agreed, that a pure flash API was more than OT should provide and a more direct otPlatSettings API was appropriate.  With that said, the flash API did not completely vanish.  It was repositioned in the examples folders and given a utils- prefix. In my mind, example code falls outside of the guaranteed source arena, meaning that the OT group is not required to maintain the examples code as strongly and diligently as the core.  It is here, in examples, that I believe we could add a hw timer api, if the desire is as strong as some here suggest. It could likewise be assigned the utils- prefix and implemented on an as needed basis for those platforms where it has use.
In this way the OT group provides source that can serve this need, but it is not required to do so for every platform that gets added to the supported set. Finally, bugs in the examples code base should naturally be assigned a lower priority over bugs in the core code.

Thanks for the detailed explanation for your concern, @ , I understand your suggestion, actually Alarm service implemented in the example directory has already provided some Timer related APIs for upper software timer implementation such as Timer class and TrickleTimer class. It seems a little redundant to add new HW timer api, and it's a burden for each platform. Previously I tried to use otPlatAlarmStartAt,otPlatAlarmStop and something else directly to implement a timer on application layer, however, it's pity that there is compile conflict because Timer class already utilizes these APIs as well. Therefore, I thought of putting a Timer class instance on the otInstance class for reusing the Alarm service.
Yes, we can make this as an optional feature in configure.ac somewhat like CoAP API.  If user has this kind of  requirement, they can enable this compiling option, otherwise, it's disabled by default. I believe that this might not have conflict with OpenThread's responsibility and meanwhile we can provide one possible method for baremetal OpenThread without underlying platform/OS. Does this make sense? Thanks. And very glad to have the discussion on this topic.

I'm sorry but, for the reasons already stated, I just don't agree that Openthread should be providing system / OS level services. It matters little to me if its optional and off by default.  I wouldn't expect these sorts of services from a WiFi stack or a Bluetooth stack, and so I don't expect them from a Thread stack either.

I have also found a need to access OT timers when integrating a third_party module to implement new core functionality.  In my case, I want to allocate the Timer class itself into the third_party component (not be limited to exactly one Timer provided by the public API), and be able to initialize that Timer after the constructor is called.
As a hard example of this, the coap module requires a core OT timer for timeouts and retries, but is able to access that because it is part of src/core.  If we had instead used a third_party coap library and wanted the same tight integration with examples/platforms (just share the multiplexed platform alarm), exposing access to the internal Timers makes sense.

Closing this PR according to above discussion, do not expose the Timer API temporarily.


bruno: 1.4.0 -> 1.5.0

Description of changes
https://github.com/usebruno/bruno/releases/tag/v1.5.0
https://github.com/usebruno/bruno/compare/v1.4.0...v1.5.0

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 275101 run on x86_64-linux 1

1 package built:

bruno


How to Not Use Privacy Mode

I hope to use the previous login information of the browser when starting next time

If you want the browser to persistent your data, you need to specify the user data directory with the chromedp.UserDataDir option. Remember to call chromedp.Cancel to close the browser gracefully. Otherwise, you're at the risk of corrupting the data stored in the user data directory.
If you know what the login information is and how it works, and you can provide it to the browser directly, then you don't need to specify the user data directory. For example, if the login information is a cookie, you can set it directly. See the cookie example here: https://github.com/chromedp/examples/blob/master/cookie/main.go.


[Feature request] Autogenerate boilerplate

This is a request to implement what I wrote about at https://internals.rust-lang.org/t/tools-team-tell-us-your-sorrows/9657/27?u=ckaran.  Below is the copy/paste of what I wrote.
Area
Source code generation
Basically, I find myself writing what a lot of what is essentially boilerplate.  For example, if I have the following function:
pub fn foo(a: Bar) -> bool {
// stuff here.
}

I will thereafter have to expand it into something like:
/// # Foo's Bars
///
/// Will Foo a Bar if it hasn't already been Foo'd.  Will not Foo a
/// if it has already been Foo'd, so this is safe to use on any Bar
/// you come across, without checking to see if it has already
/// been Foo'd.
///
/// # Example - added if needed
///
/// ```rust
/// use crate::bar::Bar;
/// fn main() {
///     let bar = Bar::new();
///     match foo(bar) {
///         true => println!("Did foo the bar"),
///         false => println!("Bar was already foo'd, not doing anything")
///     };
/// }
/// ```
///
/// # Parameters - added if needed
///
/// - `a` - A Bar that may or may not have already been Foo'd.
///
/// # Returns - added if needed
///
/// `true` iff `a` wasn't Foo'd before this call.  If this call returns,
/// rather than panics, then `a` will have been Foo'd successfully.
///
/// # Panics - added if needed
///
/// Will panic if `a` has been Baz'd.
///
/// # Errors - added if needed
/// # Safety - added if needed
/// # Aborts - added if needed
/// # Undefined Behavior - added if needed
pub fn foo(a: &mut Bar) -> bool {
// stuff here.
}

// A whole bunch more functions

#[cfg(test)]
mod tests {
    use super::*;

    fn test_foo() {
        // Some kind of test
    }
}

That is a lot of boilerplate for each function, struct, union, etc.  What I want is a tool that is able to analyze the contents of a module (probably via the AST) and generate the boilerplate in place as needed (kind of like how cargo fmt figures out where whitespace should be added).  It should do the following:

If there are no module-level docs, add the appropriate block at the top.  Put in a FIXME comment anywhere I need to fill something in.
For each member of a struct, enum, union, etc., make sure that there is documentation in place.
For each function/method, add in the docs as shown above intelligently.  That is, if my function doesn't have any parameters, don't bother with that section.  If it does have parameters, add in a single stub line for each parameter.  Same for every other heading.
For each chunk of executable code, add in a unit test stub whose contents are assert!(false), so that I know what I need to fill in.
Don't overrwrite what is already there! I want this to be an idempotent operation, so that I can run it whenever I want, kind of like how I run cargo fmt --all on my code right before each commit.

Is there a tool for this already?
Not as far as I can tell, but I may not be looking in the right places.
If not: which tool do you think it should be included in?
cargo fmt, probably with a new switch like cargo fmt --generate_doc_stubs --generate_test_stubs
Did you manage to work around the lack of tooling?
Copy/pasting of function names, and then prefixing with test_, or copy/pasting home-grown documentation stubs, etc.

My first impression is that this is not the responsibility of rustfmt, but rather the one for IDE or an editor plugin (e.g., yasnippet).

I agree. I can certainly see the value in the request capabilities, but strikes me as outside the scope of rustfmt

@topecongiro I can see where you're coming from, but I think it would be better to have it in one of the rust tools (maybe rustfmt, or maybe rustdoc).  There are two big advantages to doing so:

With an official tool in place, all IDEs, plugins, etc., can use the tool to generate the same boilerplate.  That will ensure that everyone is using the same standard, which will be helpful when developing new tools to ingest the information.
Command-line tools can be scripted.  This makes it particularly easy to write commit hooks that automatically check to make sure that the code is documented, etc.

That said, both @topecongiro and @calebcartwright are probably right that this should be in a different tool.  Maybe rustdoc?  What about the automatic test generation code, is there a better place for it?

this should be in a different tool. Maybe rustdoc? What about the automatic test generation code, is there a better place for it?

One option would be to build out some new cargo subcommands, which seems to be a pretty popular path for extending functionality.
For baking the capabilities into some existing tools..
Not sure how the rustdoc team would feel about adding the doc generation feature, but I could see the logic in that feature being part of rustdocs capabilities.
For the test stub generation, maybe as a new sub-subcommand of cargo test 😄? Again I've no idea of that's something the cargo team would consider, but perhaps that'd be an option since cargo does generate a test stub as part of cargo new

@calebcartwright OK, thank you!  I'll raise the issues with those teams.  Thanks!


Levels and Occlusion Mode: Vision

Expected Behavior
I expect, with Levels and Perfect Vision enabled and two tiles placed down, one of which is a roof, for a token's vision to look something like this when Occlusion Mode is Vision and Occlusion Alpha is 0 (Screenshot taken with Perfect Vision disabled):

Current Behavior
Instead, upon enabling Perfect Vision it looks like:

Steps to Reproduce

Install Levels and Perfect Vision.
Create a Level.
Place a tile on the level.
Place a roof on the level.
Change the roof's Occlusion Mode to Vision.
Set the Occlusion Alpha to 0.
Use a token with vision to observe.

Context
No response
Version
v4.0.39
Foundry VTT Version
v10.288
Operating System
Windows
Browser / App
Native App (Electron)
Game System
dnd5e (2.0.3)
Relevant Modules
levels (3.5.2)

It's a core bug that's causing this issue. But I shipped a fix for in PV 4.0.40.
Thanks for the report!


odict_entry union segfaults

Problem
https://github.com/baresip/baresip/blob/master/modules/mqtt/subscribe.c#L77:
	debug("mqtt: handle_command:  cmd='%s', token='%s'\n",
	      oe_cmd->u.str,
	      oe_tok ? oe_tok->u.str : "");

If odict_entry type is a not string this produces a segfault, because  struct odict_entry u is a union and for example could be a integer value instead of a pointer.
struct odict_entry {
	struct le le, he;
	char *key;
	union {
		struct odict *odict;   /* ODICT_OBJECT / ODICT_ARRAY */
		char *str;             /* ODICT_STRING */
		int64_t integer;       /* ODICT_INT    */
		double dbl;            /* ODICT_DOUBLE */
		bool boolean;          /* ODICT_BOOL   */
	} u;
	enum odict_type type;
};

Its very easy to crash baresip mqtt with:
/baresip/01/command/ {"command":"example","params":null,"token":11}

Solution 1 - struct instead of union
struct odict_entry {
	struct le le, he;
	char *key;
	struct {
		struct odict *odict;   /* ODICT_OBJECT / ODICT_ARRAY */
		char *str;             /* ODICT_STRING */
		int64_t integer;       /* ODICT_INT    */
		double dbl;            /* ODICT_DOUBLE */
		bool boolean;          /* ODICT_BOOL   */
	} u;
	enum odict_type type;
};

Pros

We can add optional type conversions (like string to int with atoi) if possible.
It's backwards compatible

Cons

Higher memory usage (+32 Bytes per entry)
Slower?

Solution 2 - Hide odict_entry struct
If we hide the struct odict_entry, direct access with e->u.str is not possible anymore.
We can add safe getters like these:
/* Odict entry Helpers */
const char *odict_entry_str(const struct odict_entry *e);
int64_t odict_entry_int(const struct odict_entry *e);
bool odict_entry_bool(const struct odict_entry *e);

or use const char *odict_string(const struct odict *o, const char *key);
Pros

We can enforce strict type handling

Cons

Not backwards compatible (breaks API)

Solution 3 - Has to be handled by implementation
Instead of handling this in libre and preventing misuse, we can fix all direct accesses to u.str and other types with strict type checks before access.
Pros

backwards compatible ;-)

Cons

It`s easy to overlook the union type and a simple json int instead of string
can result in a segfault.

@alfredh do you have a preference or another solution?

no strong opinions from me ...
but I know that these helpers are in the api:
/* Helpers */

const struct odict_entry *odict_get_type(const struct odict *o,
					enum odict_type type, const char *key);
const char *odict_string(const struct odict *o, const char *key);
bool odict_get_number(const struct odict *o, uint64_t *num, const char *key);
bool odict_get_boolean(const struct odict *o, bool *value, const char *key);

I would prefer solution 2 a little bit. It seems to be the perfect solution. Further an API change means that the compiler tells the developer where the application code has to be changed. The benefit is that a segv can be avoided.

I added PR #130 for solution 2. Rewriting is not hard this helped me to update most of the retest code baresip/retest#26 (must be checked carefully afterwards):
sed -i "s/\([a-z0-9]*\)\->u\.\(key\|str\|boolean\|dbl\)/odict_entry_\2(\1)/g" src.c
sed -i "s/\([a-z0-9]*\)\->u\.integer/odict_entry_int(\1)/g" src.c

Maybe some setters would be nice too.

The getters look ok.
Rewrite code with sed is super advanced. ;-)
Do we need setters already?
Is it possible to crash a program with a call to odict_entry_add() somehow?

I don`t know if it was used (with retest not) but I can think of this code:
struct odict_entry *e;
...
e->u.integer = 32;

To modify a odict_entry. I think the normal way is to delete and add a new entry or build a complete new odict (for response). A crash should not possible.

Ok, then odict_entry_set() would combine the calls to odict_entry_del() and odict_entry_add() which would be a simpler for the user if he wants to change only parts of the odict. Currently we dont't need this, but if you like ...
The second question was a little bit off topic. What if someone calls:
odict_entry_add(o, "foo", ODICT_INT, "jackson");

The man page of va_arg() tells that "random erros will occur".

Ah I see, hm. I would say this is not so easy to overlook since you provide a explicit type in this case, but yes bad things could happen. Maybe we can also use the setters for this:
int odict_set_str(struct odict *o, const char *key, const char *str);
...

And assume if key does not exists a new entry is wanted? Or more explicit with separate functions?:
int odict_add_str(struct odict *o, const char *key, const char *str);
int odict_set_str(struct odict *o, const char *key, const char *str);
...

Yes, if you like.
But was thinking again about this. We can't make it 100% save. There are many function with variable parameters. E.g. re_printf(). Maybe we should simply accept that the app/baresip developer also is responsible for the stability.

@sreimers Should we close this? Or do you plan to hide struct odict_entry?

#130 is merged now.


为什么自定义数据集传不上去，显示不出来

Reminder

[X] I have read the README and searched the existing issues.

System Info
0.9.0
Reproduction

微调界面数据集无法选中
Expected behavior
No response
Others
No response

https://github.com/hiyouga/LLaMA-Factory/blob/main/data/README_zh.md


Add Stock Master to the list of showcase apps

Add Stock Master to the list of showcase apps

Thanks for sending this pull request. According to the guidelines in that file, "infoLink" must be one of:
1/ An English-language news article discussing the app, built either by a funded startup or for a public company
2/ An English-language technical post on a funded startup or public company blog discussing React Native
I am going to close this, but if you have one of those two things, feel free to reopen with a new link.


WIN+ScrollUp/Down shortcut not working anymore depending of the window focused

Hi.
I've been using 3rvx for several years, and I have noticed that something is different after installed it on my new computer.
My usual config is Win + Mouse Wheel Up / Win + Mouse Wheel Down to Increase/Decrease the volume, as shown in this image: http://i.imgur.com/F9rMuHT.png
The expected behavior is to press Win + MW_Up, then the volume is increased and the display is shown, regardless of the focused application.
Now, if try to do this in an app such as Google Chrome (Independently of having a "scrollable" page or not), or Visual Studio with an opened document, it priorizes the scroll function of the app.
However, if i tap Win key (to show start menu and change the focus to explorer.exe) and then Win + Mouse Wheel Up, it works perfectly.
If is there any log/screenshot that can help to figure why is this happening, just let me know.
ps. my current O.S. is Windows 10 (64-bit).
Thanks Matthew, 3RVX is one my favorite apps, today it is on my "essential" list!

Just checked and I was running the B7 executable. Updated to B9 (using MSI Installer) and everything is working fine now.

Oops..
Since a couple weeks ago, the "WinKey + Mouse Wheel Up / WinKey + Mouse Wheel Down to Increase/Decrease the volume" stopped working again.
I've tried to delete my Hotkeys and create it again in the "Hotkey Input" dialog, but now it don't even recognizes the "WinKey+Scroll" as a valid option.
Does anything have changed in the last updates that can affect on this behavior?
thanks!


Issue while installing calico - remote-exec error

module.oke.null_resource.install_calico[0] (remote-exec): unable to recognize "calico-policy-only.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp <IP_ADDRESS>:8080: connect: connection refused
module.oke.null_resource.install_calico[0]: Creation complete after 14s [id=310330431674851063]
Error: error executing "/tmp/terraform_812903520.sh": Process exited with status 1
Error: error executing "/tmp/terraform_1105940682.sh": Process exited with status 1
================================================

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version and Provider Version

Affected Resource(s)

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.
# Please remove any sensitive information from configuration files before sharing them.

Debug Output

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

terraform apply

Important Factoids

References

found out the root cause of this issue. oci cli tool is not getting installed on admin host
==================
module.oke.null_resource.write_kubeconfig_on_admin[0] (remote-exec):   Checking Host Key: false
module.policies.null_resource.update_dynamic_group[0] (remote-exec): Connected!
module.oke.null_resource.write_kubeconfig_on_admin[0] (remote-exec): Connected!
module.policies.null_resource.update_dynamic_group[0] (remote-exec): /home/opc/update_dynamic_group.sh: line 5: oci: command not found

The fix is to modify the following script
/modules/oke/scripts/install_kubectl.template.sh
and add the following line
sudo yum install -y python-oci-cli-2.9.0-1.el7
this will install oci-cli tool.

Ok thanks. I will fix this in the base module accordingly

Hi, I was not able to replicate the issue. oci-cli installed correctly as the generation of kubeconfig and the subsequent installation of calico. Can you please share your var file (minus the credentials)?

This issue was because of the new OL image for Admin server. The oracle-oclne-release-el7 package was broken. I tested with old OL image and it was fine.

The oracle-oclne-release-el7 is used only for kubectl, not for oci-cli which is what you reported the issue. Does the problem still exist or we can close this?

Closed this issue, since this problem was due to OL image.


Support conditional sections in csproj

Dependabot wants to update the netstandard2.0 section - but that would be wrong.
https://github.com/IdentityModel/IdentityModel.AspNetCore/pull/18/files

Duplicate of #1303


mullvad-vpn: 2019.10 -> 2020.1

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[X] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Handled in #80159, this PR should probably be closed.


(waterfox) Classic and Current support

@gep13 @pascalberger @majkinetor @AdmiringWorm
Description

This will make the waterfox package a stream package to support Classic and Current
The Classic readme might need a hyperlink to Current
Motivation and Context

The issue #1440
How Has this Been Tested?

Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

Original Location

Original Repository
Open Issues Add the different issues underneath, and tick those that are fixed in this PR

[x] Issue 1 #1440
[ ] Issue 2 Link

[ ] Include the link to the opened PR that removes the package from the original location
[ ] The migration guidelines have been followed

:x: Package verification failed, please review the Appveyor Logs and the provided Artifacts before requesting a human reviewer to take a look.

:white_check_mark: Package verification completed without issues. PR is now pending human review

Just creating a empty file named waterfox.json cause a fault, but making it have { } fixed the error from yesterday.
Ready for your reviews

:white_check_mark: Package verification completed without issues. PR is now pending human review

:white_check_mark: Package verification completed without issues. PR is now pending human review

Waterfox Classic new version 2020.4 is available.

Waterfox Classic new version 2020.4 available.

@mstick99 we can not update the package until the first version is approved.
After that has happened, the package will be updated when there is a new version together with every other package in the repository (every 6th hour).


Add transform operation: subset data

New transform feature that can be added during the preprocessing step to subset the adata on .obs variables.

Thanks @FrancescaDr  could you add some simple tests for it, in the meantime I will try to connect CI to the tests


Get storagecluster Api , should return type of storagecluster

Get Storagcluster Api  doesn't return  type of storage cluster block or object  as shown

software version
master : 851d41fa


Dynamic changing of toolbar buttons

There is a problem with dynamic changing of toolbar buttons in current implementation:
Right now the only possibility is to disable toolbar button in helper method build_toolbar_disable_button, but in this method I'm only able to disable buttons on server side e.g. on summary screens, which is not usefull, when I need to change button on client side e.g. after selecting record in list of all records.
This leads to bugs with not implemented actions for record (BZ12588270, #4827) and ugly fixes (#5529).
@martinpovolny

New issue with suggestion how to fix this: #5597. Closing this one.


/bin/sh: gs: command not found

Something went wrong: Error reading pdf: Error: Command failed: /bin/sh -c gs -q -dNODISPLAY -c "(cards/flashcards.pdf) (r) file runpdfbegin pdfpagecount = quit"
/bin/sh: gs: command not found
ts-node

https://www.drupal.org/project/pdf_to_imagefield/issues/826194


Add more LLVM build info to numba -s

Feature request

Recently there have been a number of issues reported in relation to the way in which LLVM is built/linked into the Numba toolchain. It might be useful to add the following to the numba -s output to help quickly diagnose whether a reported issue is essentially a known LLVM packaging problem/provide information to help with spotting patterns in issues.

Is it possible to test if all of the patches that Numba requires have been applied to LLVM? Examples:

The ARM consecutive registers patch, which manifests as a segfault if it is not applied (impacts ARM linux and ARM/M1 OSX systems).
GlobalValue name size limit patch, this leads to issues with duplicate names in IR if not applied (impacts all builds).

Is it possible to show whether LLVM was built with/without assertions?
Is it possible to show whether llvmlite is dynamically or statically linked against LLVM?

Starter patch for 1:
diff --git a/numba/misc/numba_sysinfo.py b/numba/misc/numba_sysinfo.py
--- a/numba/misc/numba_sysinfo.py
+++ b/numba/misc/numba_sysinfo.py
@@ -9,6 +9,7 @@ from contextlib import redirect_stdout
 from datetime import datetime
 from io import StringIO
 from subprocess import check_output, PIPE, CalledProcessError
+import subprocess
 import numpy as np
 import llvmlite.binding as llvmbind
 from llvmlite import __version__ as llvmlite_version
@@ -54,6 +55,7 @@ _python_locale = 'Python Locale'
 # LLVM info
 _llvmlite_version = 'llvmlite Version'
 _llvm_version = 'LLVM Version'
+_llvm_issues = 'LLVM bugs/issues patched'
 # CUDA info
 _cu_dev_init = 'CUDA Device Init'
 _cu_drv_ver = 'CUDA Driver Version'
@@ -401,6 +403,10 @@ def get_sysinfo():
         sys_info[_numpy_AVX512_SKX_detected] = \
             __cpu_features__.get("AVX512_SKX", False)

+    # LLVM state information
+    llvm_patch_state = _check_llvm_patches()
+    sys_info[_llvm_issues] = llvm_patch_state
+
     # SVML information
     # Replicate some SVML detection logic from numba.__init__ here.
     # If SVML load fails in numba.__init__ the splitting of the logic
@@ -513,6 +519,44 @@ def get_sysinfo():
     return sys_info

+def _check_llvm_patches():
+    def _check_aarch64_consecutive_registers_patch():
+        # This source segfaults during compilation on an unpatched LLVM running on
+        # Aarch64 (for clarity, this includes Apple M1).
+        # See: https://github.com/numba/numba/issues/8215#issuecomment-1172472321
+        # The patch required to fix is this one (or variants of):
+        # https://github.com/numba/llvmlite/blob/6e8a86449e92a6b78498ec64922c39e2bd4f7a61/conda-recipes/llvm_11_consecutive_reg
+        uname = platform.uname()
+        # Identify M1 in ARM64 mode, see:
+        # https://github.com/numba/numba/issues/7822#issuecomment-1040342576
+        M1_ARM64_mode = uname.system == "Darwin" and uname.machine == "arm64"
+        machine = platform.machine()
+        ret = f"N/A for {machine}."
+        if machine == "aarch64" or M1_ARM64_mode:
+            src = """if 1:
+                import numba
+                import numpy as np
+
+                op_axis = ((0, True),)
+
+                @numba.njit((numba.float64[::1],), # Compile for this signature only
+                            no_cpython_wrapper=True, # don't generate a cpython wrapper
+                            no_cfunc_wrapper=True) # don't generate a cfunc wrapper
+                def test(x):
+                    numba.literal_unroll(op_axis)
+
+                """
+            cmd = [sys.executable, '-c', src]
+            status = subprocess.run(cmd, timeout=15)
+            ret = str(status.returncode == 0)
+        return ret
+
+    info = {'Aarch64 consecutive registers bug patched:':
+                _check_aarch64_consecutive_registers_patch()}
+
+    return info
+
+
 def display_sysinfo(info=None, sep_pos=45):
     class DisplayMap(dict):
         display_map_flag = True
@@ -576,6 +620,7 @@ def display_sysinfo(info=None, sep_pos=45):
         ("",),
         ("__LLVM Information__",),
         ("LLVM Version", info.get(_llvm_version, '?')),
+        (DisplayMap(info.get(_llvm_issues, {})) or ('Not found.',)),
         ("",),
         ("__CUDA Information__",),
         ("CUDA Device Initialized", info.get(_cu_dev_init, '?')),

Looking at 2. and 3.
I think 2. can be found via:
$ llvm-config --assertion-mode
ON

at build time for llvmlite, but this isn't going to work in the case of dynamically linked LLVM, as versions with/without assertions could be swapped out at runtime. @apmasell any idea if there's an API call for this, or perhaps some bit of code that could be run to trigger an assertion to test if they are present?
I think 3. is a little easier perhaps and can be just inferred at llvmlite build time by looking at the LLVMLITE_SHARED env var in the CMakeLists.txt used to build a llvmlite with optionally shared llvm linkage and propagating this through to a ffi->python function via a definition flag added to the compilation flags cf. SVML detection.

I don't think there's an official API for that, but all llvm-config is doing is check if NDEBUG is set and that's used everywhere. I'd have to search through all the uses of it, but checking if llvm::dbgs() != llvm::errs() should be true only when in debug mode. I can rummage to find a less gross API though.


Restrict VRF names

They should only be allowed to contain numbers, Latin letters, hyphens, and underscores.

Resolved by https://github.com/OSU-Net/cyder/issues/872


[QUESTION] Any plans to make Kiwi a persistent store?

I had plans of working on v2 which would also persist data. Current API isn't suitable for that and would require a lot of major changes.
But, work on v2 won't be started soon since the current implementation fulfils what was required for our use.

I had plans of working on v2 which would also persist data. Current API isn't suitable for that and would require a lot of major changes.
But, work on v2 won't be started soon since the current implementation fulfils what was required for our use.

I see. I think this project can be a good base to understand and develop many interesting ideas. Durability is one aspect whose implementation would require interesting design choices i.e., whether to optimize for read-heavy or write-heavy workloads, how to store data on disk, how to index files(e.g. bloom filters), how and when to perform compactions, and many more. Could be a fruitful exercise!

I see. I think this project can be a good base to understand and develop many interesting ideas. Durability is one aspect whose implementation would require interesting design choices i.e., whether to optimize for read-heavy or write-heavy workloads, how to store data on disk, how to index files(e.g. bloom filters), how and when to perform compactions, and many more. Could be a fruitful exercise!

Yes. This is something I have been reading about and learning from other such projects like RocksDB or BoltDB. It's definitely something I would like to work on.

Yes. This is something I have been reading about and learning from other such projects like RocksDB or BoltDB. It's definitely something I would like to work on.


fix(api): Disallow uploading a protocol with non matching references

Overview
Closes https://opentrons.atlassian.net/browse/RSS-81.
Disallow uploading a protocol when referencing a none existed model Id.
Changelog

Added validation method to protocol_reader

Review requests

should I add more validations?
is the code clear?
tests sufficient?
should I add it to read_saved for old uploaded protocols?

Risk assessment
Medium. added another step when uploading a protocol.

Another totally different approach would be to try out Pydantic validators.

tested this with a dev server. uploading an invalid json v6 protocol ends with a 422 Unprocessable Entity. The exception is caught in the protocol_reader and propagates the error "JSON file ref_fail.json did not match a known Opentrons format".

Spoke to @mcous about propagating this. He mentioned we might need to update the package for this to happen so this will need to wait for 6.2 release.

The exception is caught in the protocol_reader and propagates the error "JSON file ref_fail.json did not match a known Opentrons format".

In another PR, we might want to reconsider this code so that the nice messages you've added here propagate all the way up. I wouldn't do it in this PR, though; I think this PR is doing its job solidly.

Was merged to 6.1.0 release branch by this PR.


kltint fails for indents using 2 interfaces

Hey! Not entirely sure who is wrong here, either the auto-format from IntelliJ or ktlint. Weird thing is that ktlint succeeds if i reduce it to one interface.
Expected Behavior
Ktlint shouldn't not complain about the indention.  Unexpected indentation (4) (should be 8) (indent)
https://kotlinlang.org/docs/reference/coding-conventions.html#class-header-formatting
Observed Behavior
Ktlint fails with  Unexpected indentation (4) (should be 8) (indent).
Steps to Reproduce

Checkout http://github.com/neugartf/ktlint-gradle
Set Kotlin Coding Conventions as default for the project
Run :samples:kotlin-gradle:ktlintMainSourceSetCheck

Your Environment

Version of ktlint used: 0.40.0
Name and version (or code for custom task) of integration used (Gradle plugin, Maven plugin, command line, custom Gradle task): https://github.com/JLLeitschuh/ktlint-gradle/commit/10509e9e74213c03aaeda678a2410aa9efbf30d5
Version of Gradle used (if applicable): gradle-6.6.1
Operating System and version: MacOS 10.15.7
Link to your project (if it's a public repository): https://github.com/neugartf/ktlint-gradle

I think https://github.com/pinterest/ktlint/pull/961 is the cause of this issue.

Thanks for the quick fix, wanted to provide one during the weekend, but you are really fast :)


Typo "pass@word1"→"pass@word1"

Bold with escape characters
related #8689
https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-cm/deploy-windows-10-using-pxe-and-configuration-manager

#sign-off


Articles created from WP do not work on Android devices

I've noticed that articles created from WP and sent to the Content Producer work fine on iOS devices but get a "Download failed" error on Android devices. However, when I download the article.zip created by the WP plugin onto my Desktop, then use the Adobe 'HTML Article Packager' and reupload, the article works fine for both iOS and Android devices. I did some investigation, and the only difference I could spot was in the manifest.xml being created.

@jeffreyflores we're going to look into it. Do you mind shooting us an export of your article.zip? I'd want to take a peak at what might be causing the error in the manifest.xml. You can shoot an e-mail to<EMAIL_ADDRESS>

Sent an e-mail over just now. These two things are outlined in the e-mail, but here they are again:
In the references to the wp-content folder, there is a leading “/“ there in the SM manifest for the resource href attribute  (line 51)
Vs. no leading “/“ in the ADOBE manifest resource href attribute (line 63).
The fonts in the ADOBE manifest have specific resource types according to type of font
Vs. "application/octet stream” resource type for all fonts in SM manifest.

+1 we are also experiencing this issue. Last tested with v2.0.9.

@StudioMercury can you let me know if you've received my emails thus far? Please and thanks. Would really like to help fix this issue.

@jeffreyflores we got your emails and put a fix in for packaging article files (there were other issues with the packager too).
We just released an update 2.0.10 with an improvement to the packaging of the article. We updated the way the template. If you look inside the article.php file you'll see we're looking for full paths (or relative paths to the server now). This is part of a larger goal to allow any template (or theme) to be used for creating an article. Relative paths are no longer relative to the article. You can manually specify relative paths in the filter (dpsfa_bundle_article). It's been committed to github but will be available via wordpress's plugin portal within the hour.

@jeffreyflores this should be resolved in the newest issue. Please let us know if you still have problems with article files in android.


Expression syntax can change the type of a record field (but probably shouldn't)

Elm 0.16 is stated to have dropped support for changing record types in expressions. According to that, the following program should not be accepted, but it is:
type A = A
type B = B

rec1 : { x : A }
rec1 = { x = A }

rec2 : { x : B }
rec2 = { rec1 | x = B }

Did it state that?

Didn't you? I have certainly seen you state something like "there is no syntax for record type changes anymore". Should I do a search where that was?

In https://github.com/elm-lang/elm-compiler/issues/1088#issuecomment-146658115:

Record extension literally does not exist in syntax anymore, and this is one form of it.

"This" = "generated function for extensible record" like in the title of that issue.
You seem to be talking about changing the type of a field. You can express that in terms of a record addition and deletion. I consider that a convenience for writing a nicer paper though.
Maybe it's true this should be gotten rid of as well, but I think that's a totally separate discussion from the extension/deletion topic.

I know and knew what "This" was referring to in the sentence I quoted. What I was quoting this sentence for was its first half sentence, about "Record extension literally does not exist in syntax anymore".
It's true that this does not imply that also "changing the type of a field" is out. I assumed that was the intention, though. In discussions back then, I think the aim was to avoid that { rec | ... } has a different type than rec. So it doesn't seem to be a totally separate discussion.
In any case, yes I think that "changing the type of a field" should be gotten rid of as well. And I'm happy to change the title of this issue to make this more explicit.

Can you open a new issue that explains why you think it should be removed?
Please do not link to other discussions to explain your reasoning. I need the ideas to be organized in a single location. I may need to come back to this at a later time, and the best results will come from clear, concise, self-contained issues.

Done.


Questions

Can we add questions to each element so we can have a questionnaire view?

 We can add more per element as needed.


Change term - originalNameUsage

Term change

Submitter: Quentin Groom

Efficacy Justification (why is this change necessary?): To improve clarity of the term usage, particularly to distinguish the different terms that can hold a scientific Latin name

Demand Justification (if the change is semantic in nature, name at least two organizations that independently need this term): This is largely for people and organizations publishing Darwin Core files to avoid repeated questions that keep cropping up. The issue #28 highlighted that the definitions of scientificName, acceptedNameUsage and originalNameUsage are all similar to one another, however, their intended usage is quite distinct, even though they are not clearly documented. The intension of this suggested change is to add to the comments of the term to help users understand the use of the terms more easily. The suggested explanations were given by @deepreef in #28, but are only preliminary.

Stability Justification (what concerns are there that this might affect existing implementations?):  The intension is that the comments would reinforce the existing definition and thus improve stability.

Implications for dwciri: namespace (does this change affect a dwciri term version)?: No implication

Current Term definition: https://dwc.tdwg.org/list/#dwc_originalNameUsage
Proposed attributes of the new term:

Usage comments (recommendations regarding content, etc., not normative): Essentially intended to capture the basionym.

See also the discussion at https://github.com/tdwg/dwc/issues/105#issuecomment-862219110 which shows that the definition for originalNameUsage and originalNameUsageID don't match up.

With the recent discussion under #105 for the related term originalNameUsageID I would propose the following usage comments:

The full scientific name, with authorship and date information if known, of the name usage in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode. For example, for names governed by the ICNafp, this term would indicate the basionym of a record representing a subsequent combination. Unlike basionyms, however, this term can apply to scientific names at all ranks.

Done.


Some HTML data are not found - looks like images out of view not loaded, try this

Hi @kensoh , I was just testing the lazada sample script with a little modification. It shows an error saying the html class is not found after it runs for the first 20 pictures.  I inspected the HTML codes, the HTML code didn't change. I am not sure what is causing the error.

https://www.google.com/search?q=indonesian+car+license+plate&rlz=1C1CHBF_enSG917SG917&hl=en&sxsrf=ALeKk027L568aIL3WeZQGgHuKmOiv_6Q1A:1620290243419&source=lnms&tbm=isch&sa=X&ved=2ahUKEwig_pDD07TwAhXE8HMBHZMoB2AQ_AUoAXoECAEQAw&biw=1536&bih=750
all_images = []
total_images = count('//[@class="isv-r PNCib MSM1fd BUooTd"]/a/div/img')
for n from 1 to total_images
if(//[@class="isv-r PNCib MSM1fd BUooTd"]/a/div/img)[n]
read (//*[@class="isv-r PNCib MSM1fd BUooTd"]/a/div/img)[n]/@src to image_link
js all_images.push(image_link)
for n from 1 to total_images
https://all_images[n-1].split('//')[1]
snap page

Thanks @kensoh. That works. Appreciate your help :)


Add spend a time to commit messages

I working on a few projects where we use Assembla.com, redmine, youtrack and etc. all of this platforms support parsing commit messages for link commits with a task and spended time. It will be very cool if wakatime plugin for AppCode (and similar IDE by JB) add spend timer to commit message, for each platform separately.

This would be pretty awesome!

Added support for time spent per commit with the GitHub integration (https://wakatime.com/features).

Hello! How to add time to commit message?
Is it works only with GitHub? How about GitLab?


InternalServerError: https://my-domain.de is not supported

Hello everybody,
I want to run the CSS on my domain css.janschill.de behind an nginx reverse proxy, but I am encountering some issues.
Error
InternalServerError: https://css.janschill.de/ is not supported
    at SingleRootIdentifierStrategy.getParentContainer (/var/www/css.janschill.de/css/node_modules/@solid/community-server/dist/util/identifiers/SingleRootIdentifierStrategy.js:24:19)
    at WebAclAuthorizer.getAclRecursive (/var/www/css.janschill.de/css/node_modules/@solid/community-server/dist/authorization/WebAclAuthorizer.js:147:48)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Setup
CSS version: v0.7.0
Server: Ubuntu 20.10 (GNU/Linux 5.8.0-25-generic x86_64)
nginx version: nginx/1.18.0 (Ubuntu)
nginx configuration for css.janschill.de
I am using the community-server-recipes mashlib project. The installation is in /var/www/css.janschill.de/css/ where I then use the npx community-solid-server -c config-mashlib.json -f ./live/ command to start it. The live folder has an .acl file which was created from the CSS.
Logs
CSS Debug Logs
https://gist.github.com/janschill/8dffd5d1cdc49b7285853212df8ad9cc
Nginx Access and Error
2021/02/11 11:55:42 [error] 97931#97931: *968 connect() failed (111: Connection refused) while connecting to upstream, client: ip address, server: css.janschill.de, request: "GET / HTTP/1.1", upstream: "http://<IP_ADDRESS>:3000/", host: "janschill.de"

ip address - - [11/Feb/2021:12:54:00 +0000] "GET / HTTP/2.0" 500 475 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.3 Safari/605.1.15"

Ports and their Processes

The node process on 8443 is the NSS running on https://janschill.net/.
The node process on 3000 is the CSS running on https://css.janschill.net/.
PS: I couldn't find a template for issue/bug reporting, so I hope I have given enough information for you to help me debug this issue I am facing.
Thanks a lot.

This should be fixed by adding -b https://css.janschill.de/ to the command you use to run the server. So that would be npx community-solid-server -c config-mashlib.json -f ./live/ -b https://css.janschill.de/.
When sending requests, the server checks if the incoming URLs match its known domain, which by default is set to http://localhost:$port

Fantastic. Thank you so much.


[Proposal] Support distributed transactions.

Most users of dapr are microservice architectures . In the development of microservices, distributed transactions should be solved.
DTM is a widely used distributed transaction framework. I'm trying to support DAPR services in DTM, and there are some design issue that needs help from DAPR.
DTM use url and request body to specify the services participating Saga/Tcc, but DAPR services does not seem to have a commonly used url format. Other services like HTTP/gRPC have urls like: "http://localhost:8080/api/TransOut", "http://localhost:8080/api/TransIn". and also many gRPC based micro-services have urls too, eg. "discovery://etcd1:2379,etcd2:2379,etcd3:2379/service1/busi.TransOut"
I want to define urls for DTM to access DAPR services, my proposal is:
For DAPR created gRPC services: daprgrpc://localhost/appid1/dapr.proto.runtime.v1.Dapr/InvokeService/method1
For raw gRPC services deployed by DAPR: daprpgrpc://localhost/appid1/
For DAPR created HTTP services: daprhttp://localhost/v1.0/invoke/appid1/method/method1
For raw HTTP services deployed by DAPR: daprphttp://localhost/appid1/
Any advice is appreciated.
After url format is confirmed, I can use HTTP/gRPC middleware to parse urls, add needed headers, update request bodies and make DAPR services calls.
After the DTM's supporting of DAPR, outbox may easily supported by DTM's 2-phase message.

I am not familiar with DTM. Can you provide an example on how it could work with Dapr?

OK, I will share a Golang runnable example using dapr in this week.

saga examples for each case can be found here: https://github.com/yedf2/dtm-dapr-sample

For dapr created http service, is there a way to return custom http status code? dtm needs this feature

Most users of dapr are microservice architectures . In the development of microservices, distributed transactions should be solved.

I'm not an expert but I thought distributed transactions were an anti-pattern in a micro-service architecture?
My preference would be to use higher-order paradigms if possible i.e. lean into workflows to orchestrate services and perform compensations - there already is a proposal in development for this https://github.com/dapr/dapr/issues/457
Can/Should DTM capabilities co-exist alongside Dapr Workflows?

In the micro-services area, it's great if it's possible to be both highly cohesive and loosely coupled while avoiding distributed transactions. But there are many scenarios where there is a need to maintain data consistency across multiple services, when distributed transactions have to be introduced, e.g. interbank transfers, multiple micro-services in an order system.
dtm is a microservice orchestration system specifically for distributed transactions, which can also be thought of as a workflow of sorts. dtm is more lightweight and more performant than cadence/temporal.
Unique support for distributed transactions includes.

Support for Saga, Tcc and XA patterns
Outbox pattern support
Support for transaction to rollback on timeout, rollback on retry limit reached, and the ability to handle exceptions in this case


MB 3459 select move type page updates Move

Description
This PR hooks up the select move type page to the updateMove endpoint, so that the move type is stored on the move. This type is used for the logic in routing from the Landing page to the next page, as well as from the select move type page to either the PPM or HHG flow.
Reviewer Notes
Setup
Run server and client and go through the flow as a new Customer. Select PPM for move type on the select move page - ensure that the next page is the ppm-start page. Hit "back" (on the browser, not on the wizard ;)), and select "HHG" instead. Ensure that the next page is the hhg-start page.
Continue through the flow and ensure existing functionality is in place to submit the move, etc.
Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against b0d5fccc6015e0bfc4f0f1eb9664f14a245599e0


Spawn ctest ENOENT

Every time when I start an already configured CMake project (quickstart example) and click build or debug after load then I get the following error:
[CMakeTools] 2018-05-13T14:43:55.401Z [fatal] [rollbar] Unhandled exception: Unhandled Promise rejection: configure Error: spawn ctest ENOENT {}
logging.js:152
Error: spawn ctest ENOENT
rollbar.js:98
	at exports._errnoException (util.js:1050:11)
	at Process.__dirname.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)

Platform and Versions

Operating System: Windows 10
CMake Version: 3.11
VSCode Version: 1.23.0
CMake Tools Extension Version: develop

@KoeMai try on develop with @physhh's changes. He may have fixed this one.

I'm going to close this, but re-open it if you still see this happening


fix: allow maxMultiplexForwards to be set to zero

Checklist

[ ] I have read the coding guide.
[ ] My change requires a documentation update, and I have done it.
[ ] I have added tests to cover my changes.
[ ] I have filled out the description and linked the related issues.

Description
If maxMultipleForwards is set to zero, pushsync is completely disabled.   This is not good.
Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)
Ensure that future coders don't run into this unintended issue if they set this to zero.
Related Issue (Optional)
#4681
Screenshots (if appropriate):

thanks for the PR! we can merge after you fix the lint issue, namely https://github.com/ethersphere/bee/actions/runs/9134143920/job/25119098349?pr=4682

thanks for the PR! we can merge after you fix the lint issue, namely https://github.com/ethersphere/bee/actions/runs/9134143920/job/25119098349?pr=4682

Hopefully fixed.


Bootstrap plugin setup with create-guten-block

What's our PR etiquette here? @melchoyce @abdullah1908

Do you have a preference? I'm fine with us playing fast & loose with PRs, but I'm also happy to defer to whatever etiquette you prefer.

@raquelmsmith I've added some status labels to the repo, so if this is ready to be reviewed it can be labelled "Status: Needs Review" (if it's not, you can use "Status: In Progress") - I like the process where PRs need an approved review before being merged, I think we have enough people where that shouldn't hold anything up too long.

Ok great! Thanks @ryelle. Since this is really just an initial commit, are you guys okay with me merging it?

Yup!

Should we change the CGB to our package name before merging? It's used in quite a few places (the @package comments, block name, etc)
If you plan on changing these later then we can merge this now 👍

I was going to change the references later, but I went through and cleaned most of them up yesterday while on the plane (in Cancun right now!). I'll merge this and then we can work on making sure all CGB references are removed and start building out the actual functionality 😀


Recognized Text Formatting

First, thank you so much for your work.
I have a local node system all setup and working well on a Linux VM. I cant seem to figure out why the recognized text prior to final result is being displayed as one long string. Maybe cause im tired, but it's not clear to me. I would like each word regardless of final result to be displayed separately.
Currently pre final result it looks like this:
Thequickbrownfox
I would like it to display
The quick brown fox
Regardless of whether this gets corrected/changed.
Thanks!

Hi Solanine,
That does sound like a problem.. a few questions:

Have you made any changes to the demo app?

If yes, can you post your code anywhere (be sure to remove any passwords you may have added first)

Do you experience the same behavior with out public demo? (https://speech-to-text-demo.mybluemix.net/)
You may also want to try out our beta Speech JavaScript SDK, as it's generally easier to work with - https://github.com/watson-developer-cloud/speech-javascript-sdk/releases (there is work in progress to convert this demo to using the SDK)

Nathan,
Thanks for the fast response. With the exception of changing to a secure server to deal with the getusermedia issue no, I've made no other changes. But it did this prior to using TLS as well. In fact I blew away the whole install and re-built it to make sure it was vanilla.
The demo app works as expected. I'll check out the JS SDK, but I would like to try and get this one running.. any other thoughts?  Thanks!

That is really strange. Hang on a few minutes. I have a fork with an in-progress update to use the JS SDK, let me try and clean that up and have you test it.

Just for posterity, here is an image of what it does....  :)

Wierd.
It seems that there have been some significant changes since I initially started the JS SDK branch.. this is going to take a bit longer than I had hoped :/

No rush, appreciate the help..

Hey @Solanine,
Sorry this fell off the radar a while back, but we just launched the new version of the demo where this should be fixed. Please re-open if you can still reproduce the issue on the new demo.


Cheers - will keep testing.

This won't be fixed as it's a side effect of how the enchants work.


Add explorer creator

Create a new explorer app given a react native version for either new or old architecture.

I haven't used it myself yet, but what do you think about using something like https://github.com/microsoft/react-native-test-app instead?

Closing in favour of the react-native-test-app implementation


Episode-scrolling in player causes volume change

Using the scroll bar changes the volume, but the episode viewer may require scrolling, thus changing your volume

dont think its a bug... most of the players use the scroll as input for volume change

well I think when the Episode browser is open, the volume change logic should be disabled


Non reproducibility of CLI tests

Ref #370
CLI tests are passing ~ half of the times.
One reason may be because the test specs files contains ordered commands that are not executed in order.

Why not a to level array? eg:
- remove-service:
  cmd: amp service rm
  args:
    - pinger
  options:
  expectation: (pinger)
- list-service:
  cmd: docker service ls
  args:
  options:
  expectation: ((ID)(\s)+(NAME)(\s)+(REPLICAS)(\s)+(IMAGE)(\s)+(COMMAND)((.)|(\s))+)

Many integration test runners support running tests both sequentially (ordered) and in parallel. Within our framework, it would seem natural to expect that any yaml file defines a test suite boundary for being able to run in parallel with any other test suite, and within the yaml file, without needing to complicate things each test case should just default to running sequentially as this probably aligns the most with what a test author intuited.
However, the sequence is based on the previous test exiting with a non-error exit code and doesn't mean that in fact the work was finished and that the next test can proceed, even if most of our test cases seem to be working that way right now. We probably need to introduce a few test constructs for specifying how long to wait or an api call to wait on (with corresponding regex defining the expected response, such as state information).
So providing some degree of parallelism between execution of test suites (independent yaml files) is an optimization that we can and should make. Supporting sequential execution of test cases within each test suite is also something we can do.
I'm thinking that if the top test elements are defined as an array, I would expect them to be executed sequentially (as @generalhenry pointed out). If the top level is a map, then I think it's reasonable to run them in parallel, but it's also reasonable to think that they at least start in the order that they are defined (as @bquenin already pointed out, MapSlice would take care of that).

main issue with ordering has been fixed by #398


initial review

Includes mostly cosmetic changes (tests, docstrings, types, vectorization).

This looks great, Joe!


fix code

https://github.com/hashie/hashie/blob/v4.1.0/lib/hashie/mash.rb#L248
to ``
if each_pair is not available.
fixed error while retrieving client.room_channels('ROOM_ID') using ruby-gitter-0.1.0. last line of error was ->
mash.rb:248:in `_deep_update': undefined method `each_pair' for ["error", "Not Found"]:Array (NoMethodError)
Did you mean?  each_index

not fixed.

@ret394 care to (re)open a PR with a failing spec or an issue with a repro so we don't drop this?


adding an as_prop arg to patch causes the html doc to set the name to None

nbdev_build_docs creates the correct entries for patched method (using @patch)  but not
for patched properties ( @patch(as_prop=True)) which creates None entries:
For the code sample:
...
@patch
def __setattr__(self:th_data.DataLoader, attr, val):
    'remove sampler,batch_sampler from list of attrs which should not be set after init'
    initialized = getattr(self,'__initialized', False)
    if initialized and attr in (
            'batch_size', 'drop_last', 'dataset', 'persistent_workers'):
        raise ValueError('{} attribute should not be set after {} is '
                            'initialized'.format(attr, self.__class__.__name__))
    super(th_data.DataLoader, self).__setattr__(attr, val)

@patch(as_prop=True)
def after_batch(self:th_data.DataLoader):
    'return empty pipeline when fastai learner looks for after_batch'
    return Pipeline()

@patch(as_prop=True)
def bs(self:th_data.DataLoader):
    'return fastai synonym for torch batch size'
    return self.batch_size

@patch(as_prop=True)
def device(self:th_data.DataLoader):
    'return null device'
    device = getattr(self,'_device', torch.device('cpu'))
    return device

@patch
def to(self:th_data.DataLoader, device):
    'add impl for to(device)'
    self._device = device
    return self

@patch
def set_distributed_sampler(self:th_data.DataLoader, rank, world_size):
    'replace sampler with torch distributed sampler'
    distrib_sampler = th_distrib.DistributedSampler(self.dataset,
                                                    num_replicas=world_size,
                                                    rank=rank, shuffle=True)
    self.sampler = distrib_sampler
    batch_sampler_klass = self.batch_sampler.__class__
    self.batch_sampler = batch_sampler_klass(self.sampler,
                                             self.batch_size,
                                             self.drop_last)

This is the generated html output (note that the 3 methods with the as_prop arg generate None entries):

Removing the as_prop arg creates the correct entries (see below).

i think this is fixed now


importlib.resources does not work when installing with apt

When installing plingo with apt on Ubuntu, it is using the system python 3.8 version which does not have importlib.resources.file. This gives an error for --frontend=plog.
I had added the following two lines when we put everything in the plingo folder for pip packaging. This import the meta.lp file which needs to be added for P-log.
from importlib.resources import files as importfiles
meta_path = importfiles('plingo').joinpath('meta.lp')

@rkaminsk Do you have an idea how to fix this? Do we even need the importlib library?
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/clingo/application.py", line 293, in _pyclingo_application_main
    app.main(Control(control), [ _to_str(files[i]) for i in range(size) ])
File "/usr/lib/python3/dist-packages/plingo/plingo_app.py", line 291, in main
    obs = self._preprocessing(ctl, files)
File "/usr/lib/python3/dist-packages/plingo/plingo_app.py", line 205, in _preprocessing
    from importlib.resources import files as importfiles
ImportError: cannot import name 'files' from 'importlib.resources' (/usr/lib/python3.8/importlib/resources.py)
*** ERROR: (plingo): no message UNKNOWN`

You could just put the file as a string in the python source code.

I had a look at the documentation. If there were a lot of resources that had to be loaded, I would conditionally import the pkg_resources package. With just one or two encodings this is not worth the effort, though. I'ld just use
encoding = '''
...
...
...
'''

That sounds good to me. I will implement it


Add trigger via URL

Feature request
Add the ability to show settings modal via URL like https://www.example.com/#cookie-settings. Whenever is the anchor tag present on the page. Consider implementation, when the anchor tag is added via GTM etc.

Just like #111, I think this falls in the cool/very optional feature group. Not saying no, but will have to wait until v3 comes out with a "plugin" system.


feat: update content on have your say views

Describe your changes

update content on hys/rthys confirmation (registration/submission) pages
remove unused template vars from controllers

https://pins-ds.atlassian.net/browse/APPLICS-953?atlOrigin=eyJpIjoiYjE2OWEzMDlmM2E2NGM5ZWIyN2MwOWQ2MmIwYjQxNmEiLCJwIjoiaiJ9

Useful information to review or test

Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[x] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.31.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.37.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Service Worker + Opera Mobile (Android) not working

Service Worker not working on actual Opera Version. All others Browsers working great with my PWA.

Fixed by clear Browser cache.


Sign kapp binaries while releasing them

Describe the problem/challenge you have
All published kapp binaries should be signed so that it can be verified that they were published through official channels.
Describe the solution you'd like
The changes proposed in this proposal for signing binary artifacts must be made a part of the release pipeline.

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

hey @100mik I would like to work on this issue.

@prashantrewar Thank you for showing your interest. You can go ahead and raise PR with your changes.


Groups not available in reviewer list

Extension version: 0.12.0
VSCode Version: 1.39.2
OS: Windows 10 (1903)

Steps to Reproduce:

Create a pull request
Click on the plus next to reviewers to add a reviewer

The pick list that is presented contains all the people that would be presented on the website, but not the groups.

@SimonWilliams-STL This looks like a duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/1126, let's track it there


Annotation action doesn't work

Annotate menu item is disabled (while History works for this file)

At the same time I see I can execute annotate action by right-click on file. But it opens external view in my browser  with annotated class. This is not so convenient obviously.


windows 7 support

How to use this on Windows 7 ?

This package use Microsoft WebView2 SDK version 1.0.1418.22
According to this article,
any version below 1.0.1519.0 should support Windows 7 & 8
I have no Windows 7 environment so I cannot debug if this package not working on it...
By the way, Microsoft has already stopped support newer WebView2 on Windows 7 & 8.

Thanks for rich replay,


DeclaredDependencies, ResolvedDependencies ( and GradleBuildAdapter)

This is a pre-flight checkin to run the test suite while I do other things. Do not merge.

retest this please

@bobmcwhirter I think based on this, we can start a review.

@bobmcwhirter I'll leave it to you to review/merge.

Looks like there's some variation from the code styles in some files, could that be fixed?
Also, I think we need to add license header to new files

@kenfinnigan I've added the license headers, but regarding the codestyles I need some pointers. Skimming through the changeset nothing jumps to my eye.

Couple of ones I noticed were https://github.com/wildfly-swarm/wildfly-swarm/pull/191/files#diff-19ea8f5ef8720c17e258f006837c82b1R17 and https://github.com/wildfly-swarm/wildfly-swarm/pull/191/files#diff-7497a7e221ac79d07edb8b9cd6eee7cbR87

@bobmcwhirter thanks, i'll have a look. That test did fail for me every once in a while i was working on this.

@bobmcwhirter I think the error in camel-mail is unrelated, but brought forward by my changes. It looks like the test driver executes before the swarm server has been started (i.e. you can see that when running with -Dmaven.failsafe.debug=true). This executes the assertion that checks the log lines, but since the server isn't fully started yet, it blows up.  A less ideal, but working solution, is to add a client wait time (see https://github.com/wildfly-swarm/wildfly-swarm-examples/pull/102) which fixes the problem.

Okay. That's an area I want to improve this week with arq anyhow. +1.
On Monday, October 31, 2016, Heiko Braun<EMAIL_ADDRESS>wrote:

@bobmcwhirter https://github.com/bobmcwhirter I think the error in
camel-mail is unrelated, but brought forward by my changes. It looks like
the test driver executes before the swarm server has been started (i.e. you
can see that when running with -Dmaven.failsafe.debug=true). This
executes the assertion that checks the log lines, but since the server
isn't fully started yet, it blows up. A less ideal, but working solution,
is to add a client wait time (see wildfly-swarm/wildfly-swarm-examples#102
https://github.com/wildfly-swarm/wildfly-swarm-examples/pull/102) which
fixes the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wildfly-swarm/wildfly-swarm/pull/191#issuecomment-257238716,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA-Tz-WqPpLVyYeaj90UK41-ss3IUIuks5q5afugaJpZM4Keuu3
.

@bobmcwhirter All squashed into one.


Add e2e test for multiple scalers per ScaledObject

Existing e2e tests are testing individual scalers, but in each e2e test, there is just a scenario where only 1 scaler is defined per ScaledObject.
We should add a test where we test multiple scalers (at least 2) in ScaledObject, we can reuse one of the extisting e2e tests for scalers and extend some.

I'd be interested in helping with this. Not sure if I totally understand though. Would the multiple scalers in the ScaledObject be the same kind of scaler? Or different?

Thanks @andschneider! I think the same kind of scaler is ok for this test case. The reason is to really test that scaling on multiple triggers really works in KEDA.


AndroidSupportedAbis problem

The latest version (1.2.1) makes my project support the x86_64 abi even if i haven't selected it. I figured this out when i tried to upload an .apk update to google play console.
Can i exclude it somehow?

What is the specific error message you are seeing?

It's not an error, it's the fact that i want to support only armeabi, armeabi-v7a, x86 and the lib forces me to support x86_64 too.
I don't want to do that because Xamarin specifically says that x64 is still in experimental stage:

Note: 64-bit runtime support is currently an experimental feature in Xamarin.Android 5.1.x. Remember that 64-bit runtimes are not required in order to run your app on 64-bit devices.

Ah.
I'm still trying to figure out more precisely what you mean when you say the lib is forcing you to support x86_64.
It is true that SQLitePCL.raw includes a native lib for x86_64.  Are you saying that you are seeing that file is still in the apk even though you didn't choose that abi in your project options?

Yes that's exactly what's happening.
When you upload an .apk to the google play store, there is a field called "Native platforms" which is displaying the supported abis. My .config file includes only armeabi, armeabi-v7a, x86 but the "Native platforms" fields shows also the x86_64 abi. I tried to downgrade your lib to 1.0.11 and the x86_64 abi removed.

The nuget package SQLitePCLRaw.lib.e_sqlite3.android contains an assembly which contains several native sqlite3 libraries as embedded resources.  One of those libraries is for x86_64, so that projects using SQLitePCL.raw can support x86_64 if they want to.
The Xamarin tooling extracts those library files from the resources and places them in the apk.  I would assume that it should only copy the libraries needed for the native platforms you have selected in your project options.  In other words, if you do not select x86_64 in your project options, it should not copy the x86_64 library into your apk.  Or at least that is how I assume things would work.
Neither SQLitePCL.raw nor sqlite-net-pcl (AFAIK) do anything to change the configuration of your project options to change which native platforms you selected.
I do not know how the "Native platforms" field you mentioned gets its value.  It is apparently not based on the values in your config file.  Is it including x86_64 in the list simply because it sees an x86_64 library in the apk?
Bottom line:  I still don't know where in the build pipeline this is going wrong.

@ptsiogas Sorry but this seems to be more of a limitation of Xamarin than this library. Good luck!


Admin: Create Event

Build the "Create Event" and "Create Event 2" for the Admin View of the Events page.
Just create frontend components, no need to connect to backend yet.

/cib

Branch 31-admin-create-event created!


fix: Add login token lifetime to consts and use it in all API clients

fix: Add the token lifetime to const.py and use the value across all API endpoints.

I don't think the USA token is valid for 24 hours.  Have you tested to see if they are now valid for that long?    Historically they were much shorter than other regions.

I don't think the USA token is valid for 24 hours. Have you tested to see if they are now valid for that long? Historically they were much shorter than other regions.

Can you point out where this was discussed? I'd like to know how the lifetime was determined.
I've been running it on my local instance for a few hours and the integration has not encountered any problems with fetching data, but it's been less than the full 23 hours.
During the time that it's been running, the car has not been exhibiting the periodic wake ups that I'm trying to fix.

Looking back at some of the code I think a short token was used to cover when the token was invalidated. Back when this was written if you used the mobile app it would invalidate the token.  The code now can recover from this.   USA Kia code is largely unmaintained as we don't have very many active USA devs here.  Have had some recent interest though!
Since you tested out I am happy to merge this.   Worst case we revert!


FIPS provider issue

Hello
I am getting FIPS provider error when I try to run acvp app. Could you please guide me on this please?
I have reviewd other answers with same issue. And I tried those suggestions but still got errors.
Here are what I did: (I installed all these on my home directory)
(1) I installed Openssl 3.0.0 version with "enable--fips"
(2) run "openssl fipsinstall" with fips.so input and got fipsmodule.cnf (I checked inside of fipsmodule.cnf)
[fips_sect]
activate = 1
install-version = 1
conditional-errors = 1
security-checks = 1
module-mac = some numbers
install-mac = some numbers
install-status = INSTALL_SELF_TEST_KATS_RUN
(3) modify ssl/openssl.cnf with these
.include /my absolute _path/fipsmodule.cnf
[openssl_init]
providers = provider_sect
alg_section = algorithm_sect
[provider_sect]
default = default_sect
fips = fips_sect
base = base_sect
[default_sect]
activate = 1
[base_sect]
activate = 1
[algorithm_sect]
default_properties = fips=yes
(4) after I modified openssl.cnf
Do I need to configure/make/make_install again of openssl and acvp?
I re- configure/make/make_install acvp, is this correct step?
But I still got errors.
Crypto module returned failure code when running quick digest.
Error occured when testing FIPS at startup (rv = 10). Please verify the FIPS provider is
properly installed and configured. Exiting
./app/acvp_app --version
ACVP library version: libacvp_oss-2.1.1
ACVP protocol version: 1.0
Compiled SSL version: OpenSSL 3.0.0 7 sep 2021
Linked SSL version: OpenSSL 3.0.0 7 sep 2021
   FIPS requested: yes

FIPS Provider Version: (null)
Thank you so much

Hi,
If you run openssl list -providers and the FIPS provider is properly configured, it should appear there.
You do not need to rebuild/reconfigure/etc libacvp after changing the OpenSSL configuration.
You may need to set LD_LIBRARY_PATH to the directory of your OpenSSL library if you are on a platform that has a built-in OpenSSL, otherwise acvp_app will likely link to the system's OpenSSL instead of your configured one. You also, in this case, may need to use the OPENSSL_CONF variable (see OpenSSL documentation) to make sure your OpenSSL build is using your cnf file instead of the system's cnf.
Thanks,
Andrew

Hi, Andrew
Thanks for the reply, I think I finally set up correct Openssl, but I got these errors.
Also, to avoid TOTP errors, I copied the content of totp.txt to nist_setup.sh file.
Could you please guide me the reason of error below?
./app/acvp_app --verbose --aes
Using the following parameters:
ACV_SERVER:     demo.acvts.nist.gov
ACV_PORT:       443
ACV_URI_PREFIX: /acvp/v1/
ACV_CA_FILE:    certs/acvp.nist.gov.crt
ACV_CERT_FILE:  <My_path>_Demo.cer
ACV_KEY_FILE:   <My_path>_Demo.key

[ACVP]: HTTP User-Agent: libacvp/2.1.1;Linux;4.18.0-372.9.1.el8.x86_64;x86_64;AMD Ryzen Threadripper PRO 3945WX 12-Cores;GCC/8.5.0
[ACVP]: Logging in...
[ACVP][ERROR]: Curl failed with code 60 (SSL peer certificate or SSH remote key was not OK)
[ACVP]: POST Login...
Status: 0
Url: https://demo.acvts.nist.gov:443/acvp/v1/login
Resp: Recieved
[ACVP][ERROR]: Received no response from server.
[ACVP][ERROR]: Login Send Failed
[ACVP][ERROR]: Failed to login with ACVP server

Hi, Andrew
I think I can log in now, I checked other closed issue, and tried to change
ACV_CA_FILE to another one, it seemed works.
Thank you for help


updated path provider in order to work with other packages like scree…

packages like screen shot use higher version of path_provider so there is a conflict with this package in compile time.
I added the current version of path provider.

Oh I just posted an issue about that, didn't notice you had it as a PR.
The plugin doesn't actually depend on path_provider, I think we should remove it from the pubsec.yaml file

Thanks @lambasoft and @mehdimsv for bringing this to our attention. Please note PR's must first go through the staging branch. We have removed path_provider. New version coming shortly.


Feature format

resampling implemented in javascript. slight lag if a feature is very dense and will run into trouble if greater than 10Hz sampling, but for now this works and is fast enough, don't need python. Everything 10hz, +scrubbing smoothed and addressed #11 . exports working , everything .tsv


"Network Update" doesn't work

Issue checklist
Note: these are not necessarily requirements

[ ] I have checked existing OPL issues for duplicates and found none @ http://psx-scene.com/forums/official-open-ps2-loader-forum/ & https://github.com/ifcaro/Open-PS2-Loader/issues

Open PS2 loader version
0.9.3+.1440-Beta-3b37e1
Open PS2 loader mode (USB, SMB, HDD)
SMB
Open PS2 type (Normal, Childproof, VMC, GSM, PS2RD)
Complete?
Issue description - Describe the problem you are having
Network Update gives a "Failed to connect to update server"
Expected result
Network Update to be working
Actual result
OPL-CL seems to be down.
http://sx.sytes.net/oplcl/games.aspx
How to reproduce the issue
Just try to use Network Update on the main menu.

Thanks for bringing this up.

This site has been down for at least last week...
Also PSX-Scene is unavailable with this topic dedicated for this service:
http://psx-scene.com/forums/f150/open-ps2-loader-compatibility-list-site-132906/.
Mirror:
https://web.archive.org/web/20160815000210/http://psx-scene.com/forums/f150/open-ps2-loader-compatibility-list-site-132906/.
Maybe someone can get in touch with @IcySon55 and report it?

Thanks for the heads up guys. I've rectified the issue on my end and the server is back up.

OPL-CL site should be working now, thanks.


Remove need to check ready before calling getGeometryInstanceAttributes

This leads to workarounds like:
var frameNumber = 0;
var scratch = new Cesium.Cartesian3();
var ready = false;

viewer.clock.onTick.addEventListener(function() {
    var length = updates.length;
    var k;
    var u;

    if (!ready && primitive.ready) {
        ready = true;
        for (k = 0; k < length; ++k) {
            u = updates[k];
            u.attributes = primitive.getGeometryInstanceAttributes(k);
        }

        return;
    }

    if (ready) {
        for (k = 0; k < length; ++k) {
            u = updates[k];
            scratch = Cesium.Cartesian3.multiplyByScalar(u.direction, (Math.sin(frameNumber * u.speed) * u.maxHeight), scratch);
            u.attributes.offset = Cartesian3InstanceAttribute.toValue(scratch, u.offsetArray);
        }
    }

    ++frameNumber;
});

Full example: https://gist.github.com/pjcozzi/4bc8fbf5a2907de6c3a9
We can just buffer the attributes, which will also eliminate the need for a scratch variable each time an attribute is set (u.offsetArray above), which caught me recently.  I suspect this can be done without creating GC pressure so the performance drop should be insignificant compared to the usability gain.
CC #766

@bagnell any chance this was part of the batch table changes?

The batch table fixes this mostly. The only thing that needs to wait for the primitive to be ready is the bounding sphere. If it's OK to return undefined for the bounding sphere until it's ready, this would be a simple change.

Yeah, I think it will be fine for the bounding sphere property to require the primitive being ready.  Labeled this as beginner.

@pjcozzi will the bounding sphere waiting synchronously or asynchronously for the primitive to be ready?

The bounding sphere get property function could just throw a DeveloperError if the primitive is not ready.


CCSHS variable count disagrees from dataset index

382 vs 366 variables. I just pushed a new dataset versio today, though I think the discrepancy existed prior. I didn't locate this on any other datasets. Wasn't sure how to refresh the count on the datasets index.

The following variables didn't have a folder assigned to them (nil), and weren't showing up in the search. I've updated them to all be under the "Spectral Analysis" folder. This accounts for the 16 variable difference between the counts.
["delta_lognrem", "delta_nrem", "beta_nrem", "alpha_sleep", "beta_lognrem", "beta_logsleep", "delta_logsleep", "fastsigma_lognrem", "fastsigma_sleep", "sigma_logsleep", "alpha_logsleep", "beta_sleep", "delta_sleep", "fastsigma_nrem", "fastsigma_logsleep", "sigma_lognrem"]


[Bug]: The message notification does not have line breaks.

ODC version
ODC 4.3.1
OB version
No related.
What happened?

Message notification shows "\n", no line breaks.
What did you expect to happen?
Display message notifications with line breaks.
How can we reproduce it (as minimally and precisely as possible)?
Send Message Notification.
Anything else we need to know?
No response

Fixed In Commit 8e5c660f3ec447e4d9e93bfd33f1b604e28f1c0a
------
畅晚
Wed Sep 11 10:00:03 2024 +0800

pass