HTTP 202: Accepted (body empty) and exit status 1 on most commands

Hi,
I downloaded an amd64 linux release and am trying to set it up now. After a (supposedly) successful login (the browser says "Login successful, return to the terminal" etc.) any command intended to manipulate Spotify status (i.e. not help or version) yields 2017/12/26 14:30:03 spotify: HTTP 202: Accepted (body empty) message and immediately exits with exit status 1. The terminal session is a bit mangled afterwards and needs a reset to behave properly back again.
It's likely I am doing something wrong; perhaps I omitted some setup step. Could it be so?
I use Ubuntu 16.04 amd64 if it's of any importance.

That's prob. you didn't open the Spotify app. Could you try opening that and run the command again? One possible improvement to spotctl is to make sure the Spotify app is open before running. But I'm not familiar with the location of Spotify app in Ubuntu. Any hints?

Hmm...according to the API doc:

When the device is temporarily unavailable the request will return a 202 ACCEPTED response code and the client should retry the request after 5 seconds, but no more than at most 5 retries.

I tried clicking the play button in the Spotify app and run the spotctl command again and it works. May need a better way to fix this...

@moon-musick: https://github.com/jingweno/spotctl/pull/4 should address this. Please make sure your local Spotify app is opened. Thanks.

Forgot to mention, please make sure you have latest version of spotctl which includes the fix: https://github.com/jingweno/spotctl/releases

I didn't have the app open indeed.
I downloaded the 1.0.1 release, but it seems it was not enough to have the app open to make it work. I got it to work by clicking the play button in the app first, just as you mentioned; after that spotctl was able to pick up the status or show the player.
Thanks!


Issue-Updates

Automated Review Comments
Issues in README.md:

(1, 'Line exceeds 80 characters')
(3, 'Line exceeds 80 characters')
(8, 'Line exceeds 80 characters')
Issues in package.json:
(2, 'Hardcoded string found')
(3, 'Hardcoded string found')
(12, 'Hardcoded string found')
(13, 'Hardcoded string found')
(14, 'Hardcoded string found')
(15, 'Hardcoded string found')
(16, 'Hardcoded string found')
(17, 'Hardcoded string found')
(20, 'Hardcoded string found')
(22, 'Hardcoded string found')
(27, 'Hardcoded string found')
(28, 'Hardcoded string found')
(29, 'Hardcoded string found')
(31, 'Hardcoded string found')
(32, 'Hardcoded string found')
(34, 'Hardcoded string found')
(35, 'Hardcoded string found')
(37, 'Hardcoded string found')
(40, 'Hardcoded string found')
(42, 'Hardcoded string found')
(47, 'Hardcoded string found')
(48, 'Hardcoded string found')
(49, 'Hardcoded string found')
(50, 'Hardcoded string found')
(51, 'Hardcoded string found')
(52, 'Hardcoded string found')
(53, 'Hardcoded string found')
(54, 'Hardcoded string found')

I got it.


Agave test

@PaulHax I am just getting a black canvas in the remote render -- do you the same? What is the issue?

I was getting error in browser console:
remote-machine.ts:587 Error while updating renderer. TypeError: server.getRenderTime is not a function
    at http://localhost:5173/@fs/home/paul/src/itk-viewer-stuff/itk-viewer/packages/remote-viewport/dist/remote-viewport.js:106:57

I published new itk_viewer_agave_renderer package to pypi.  Works for me now.

There is an error in the agave terminal: [error] Could not find subpath 2 in multiscaleDims.
Agave is not mapping multiresolution_level to the 'path' defined in the .zatters metadata.   Subpath should be 's2' for the zyx.ome.zarr image.
https://github.com/allen-cell-animated/agave/blob/main/renderlib/command.cpp#L656


bump to purescript-0.15

purescript-0.15 was released a few days ago.  It would be nice if purenix was compatible with it.  I'm not sure how much work would need to go into this:
https://github.com/purescript/purescript/releases/tag/v0.15.2

It looks like purescript-cst is marked as broken upstream:

@jonascarpay Ah, yeah, the stackage resolver used in purescript often lags behind the stackage resolver Nixpkgs.  So Nixpkgs is now on LTS-19 / GHC-9.0, but I think purescript is still on LTS-18 / GHC-8.10.  So it is sometimes difficult to keep purescript building in Nixpkgs.
However, there was recently a PR getting purescript building in Nixpkgs again.  Some of the last few commits here are purescript-related: https://github.com/NixOS/nixpkgs/pull/175328.  Although it is possibly only building in haskell.packages.ghc8107.  I haven't really looked closely at this.  You might be able to use one of the commits from that PR if you're looking to do this bump to purescript-0.15.

You might be able to use one of the commits from that PR if you're looking to do this bump to purescript-0.15.

If I use the haskell-updates branch I get the same error, but for purescript-0.15.2. I guess we just wait until the issue is resolved upstream?

@jonascarpay I think you have to explicitly get purescript from haskell.packages.ghc8107.
Here's what I just tried locally:
$ cd /path/to/my/nixpkgs/
$ git checkout haskell-updates
$ git pull
$ git rev-parse HEAD
1a2bb9918a9fcbe40a42f4bf0a17d571032fa933
$ nix-build -A haskell.packages.ghc8107.purescript
/nix/store/csz72sprx6k7f93vkvbyi26spfjfvwf7-purescript-0.15.2

So I imagine if you use nixpkgs at 1a2bb9918a9f, and make sure to switch all instances of haskellPackages to haskell.packages.ghc8107 in https://github.com/purenix-org/purenix/blob/main/nix/overlay.nix, purenix will build?  Or you're at least get everything up to purenix built.

Just a quick update: I took another look at this, and currently, on both unstable and release-22.05, and on both haskellPackages and haskell.packages.ghc8107, the purescript library fails to build because bower-json is outdated.
The way I see it is we have two options;

make an effort to get bower-json updated. It looks like the hackage version is broken, the github version is fine but not yet on hackage. We'd have to prod the maintainer.
Manually override the bower-json dependency with the github version and maintain the patch. I've never done this but I imagine it should just be a matter of changing the src in an overlay.

Thoughts @cdepillabout ?

Not sure if it helps, but I thought I'd share this.
We're on GHC 9.2.3 now as of 0.15.4 using the nightly-2022-06-09 stackage release.
Also, we no longer use purescript-cst. That were merged into the purescript package during the 0.15.0 release.

Thanks for the tip, on the haskell-updates branch everything builds with GHC 9! If tests pass I'll clean up the history and cut a release.


[co19] LibTest/ffi/Packed/Packed_A01_t02 expectations

https://godbolt.org/z/13nM7n18b
#pragma pack(push, 16)
typedef struct  {
  double x;
  int32_t y;
} MS16;
#pragma pack(pop)

This struct has a size of 12 bytes on Linux ia32, but the test expects 16.
Expect.equals(16, sizeOf<S16>());

https://dart-ci.appspot.com/log/vm-kernel-nnbd-linux-release-ia32/dartk-strong-linux-release-ia32/199/co19/LibTest/ffi/Packed/Packed_A01_t02

Fixed by 055b5c984613ec1b8ef76516db3ea99fee63acb9


maximum allowed to be analyzed for highlighting has exceeded!

Kibana's maximum allowed to be analyzed for highlighting is 1000000. Can't update kibana

To fix the issue please run the following curl cmd:
To set highlighting max to 60000000.
curl -XPUT "localhost:9200/YOUR-INDEX-NAME/_settings" -H 'Content-Type: application/json' -d' {
    "index" : {
        "highlight.max_analyzed_offset" : 60000000
    }
}
'


Benchmarking 1: Create a hash chain scenario for Rescue Prime of 1, 10 and 100 hashes

For the Delendum Benchmarking project our first benchmarking scenario will be to iterate a hash function - which we call a hash chain. We will iterate our default hash function Rescue Prime.
The scenario is defined as
Compute h(h(h(...h(x)))), where h() is a cryptographic hash function for some input [0u8; 32] (32-bytes).
We will benchmark three different chain lengths, 1, 10 and 100 hashes.
The benchmarking repo can be found here. https://github.com/delendum-xyz/zk-benchmarking
Steps:

[x] create 1-to-1 Rescue Prime
[x] create scenario for hash chains
[x] measure time to prove
[x] measure time to prove size
[x] measure time to verify
[ ] measure time to reject a false proof

PR is here https://github.com/delendum-xyz/zk-benchmarking/pull/5

I just wrote assembly routine for computing Rescue Prime digest over 32 -bytes input. See https://github.com/maticnetwork/miden/pull/576

Yes makes sense, much better way to solve this. Though we may consider to expose an API for hashing 32 -bytes ( 4 field elements ), for which we can keep https://github.com/maticnetwork/miden/pull/576.

When I use the above program, I get
thread 'main' panicked at 'Could not compile source: ParsingError("instruction 'swapw2' is invalid")', src/benches/iter_rescue_prime.rs:67:14

Can you provide such a program as @bobbinth sketches using your 1-to-1 RP hash @itzmeanjan ?
I would want to include it right here using the defined input vec![0_u8, 32] as stack_init

There is a typo - swapw2 should be swapw.2.

Maybe we can talk about Program 1 @itzmeanjan and see how we can write it such that it creates the most optimal hash chain for the given input [0u8; 32]? Do you have an idea?

I removed the push.<IP_ADDRESS> because we wanted to benchmark the systems using an external input of vec![0_u8, 32]. I am not sure if it makes a difference.

We can't do this. These are not a part of the input - these are needed to initialize capacity portion of the hasher state.

Program 1 takes a bit longer to be executed and proven

This is likely because the number of cycles for both programs gets rounded to the same power of two. Using back-of-the-envelope computations I get, for 1000 iterations:

Program 1: 1.1M cycles
Program 2: 1.9M cycles

But both of them get rounded to the next power of two which is about 2M cycles. This happens because trace length must always be a power of two.

I removed the push.<IP_ADDRESS> because we wanted to benchmark the systems using an external input of vec![0_u8, 32]. I am not sure if it makes a difference.

We can't do this. These are not a part of the input - these are needed to initialize capacity portion of the hasher state.

btw, we should really add an independently-computed result to make sure the program does the right thing.

I removed the push.<IP_ADDRESS> because we wanted to benchmark the systems using an external input of vec![0_u8, 32]. I am not sure if it makes a difference.

As @bobbinth said it will produce incorrect result.

Note

May be avoid optimized version that @bobbinth suggested ( in https://github.com/0xPolygonMiden/examples/issues/14#issuecomment-1335680162 ) during first time and use https://github.com/maticnetwork/miden/pull/576 which exposes an API for hashing 32 -bytes input ( i.e. 4 field elements on stack, compared to 8 of them expected by rphash ) --- can be better choice, because that API won't let you misuse it and it's highly likely that it will produce correct result, though it's expensive. We can use optimized version in next round.

@Dominik1999 this is the version of rescue prime I mentioned in my last message.

We should use hash_elements() instead of hash() as these functions work differently when the underlying data contains valid field element. See note on hash output consistency here.

Ok, so I tried three different Rescue Prime Assmebly Programs now and compared it to a Rust Implementation
    let input = vec![BaseElement::ZERO; 4];
    let h_output = Rp64_256::hash_elements(&input);

I get different results.
Rust Hashing: [2526470497159956267,<PHONE_NUMBER>699805053,<PHONE_NUMBER>172155749,<PHONE_NUMBER>1891329886]
Assembly Program 1: [11330409471891329886,<PHONE_NUMBER>172155749,<PHONE_NUMBER>699805053,<PHONE_NUMBER>159956267]
Assembly Program 2: [11330409471891329886,<PHONE_NUMBER>172155749,<PHONE_NUMBER>699805053,<PHONE_NUMBER>159956267]
Assembly Program 3: [9233990305047322442,<PHONE_NUMBER>8640222486,<PHONE_NUMBER>6853856250,<PHONE_NUMBER>5577346877]

Here is the gist https://gist.github.com/Dominik1999/a984156dcafdeb9fa2d602ca67e79b74

Seems everything works as expected, right? Programs 1 and 2 give the same result as Rust (the result is reversed because it is in the stack order). Program 3 gives a different result because it hashes 8 elements rather than 4 (if you were to use let input = vec![BaseElement::ZERO; 8]; then assembly output would have been the same as Rust).

You are right. Took me a while to remember that Assembly returns the wrong order.


SEAB-6712: Prototype "custom" Dockstore DOIs

Description
This draft PR is a very rough proof-of-concept of a "custom DOI" scheme, in which the DOIs are generated via UC's EZID service https://ezid.cdlib.org/ and point at pages on the Dockstore site, "WorkflowHub style".  Currently, this prototype generates custom DOIs for versions, a productized system would generate DOIs for entries similarly.  This PR is not even close to complete/finished, so please do not spend any time critiquing code, tests, etc.  There are many known defects and missing parts.  The goal is to demonstrate the technique so we can determine whether to continue moving forward with it...
Please run this locally to see it in action.  That way, you can inspect/clear the db, etc.  Note that the new DOIs don't appear in the UI, I haven't tried to figure out why (yet).  You can view them via API responses, looking at the db, side effects, etc.
There is a lot to unpack here, thus many words.  Please read all of them, they will answer many of your questions...
About DOIs and EZID
A DOI has three components:

a name. for example 10.5072/FK2.24231.247355.  A DOI always starts with 10., some decimal digits, and a slash.
a target URL, which points at the referenced object.
metadata, describing the object.

An existing DOI's metadata and target url can be updated/changed at any time.  The name is immutable.
The EZID service is a wrapper for DataCite, run by the University of California.  The main advantage over using DataCite directly is that EZID is free to us because we are a UC-based project.  The EZID API is also quite simple.
Very High-Level Architecture
This PR introduces a DoiHelper class containing a method createDoi which creates a custom DOI for a specified entry version.  It delegates to an instance of DoiService, which currently has two implementations:

EzidDoiService: generates a test DOI via a single call to the EZID API.
DummyDoiService: logs the name, url, and metadata of the DOI to be created.  It doesn't actually create a real DOI, but always pretends that it did by returning successfully.

The DoiService interface is designed with generality in mind: that is, with the appropriate code layered on top, we could theoretically use it to generate a DOI for any object on Dockstore (an organization, collection, user, etc).
Metadata XML generation is encapsulated in the helper class DataCiteHelper.
Configuring the webservice
There are new configuration options ezidUser and ezidPassword to specify the EZID account information.  For this demo, we'll use the EZID test account, user apitest. I'll slack the password on devs.
If you specify the EZID account info in the config file, the webservice will use EzidDoiService, otherwise DummyDoiService.
Generating a custom DOI
There is a new generateCustomDoi Dockstore endpoint that will generate a DOI for a version that you have permission to modify, you can hit it with a command line something like:
curl -X POST -H 'Authentication: bearer '`cat /tmp/token` http://localhost:4200/api/entries/24231/versions/247355/generateCustomDoi

It will create an EZID DOI (if the webservice is configured to do so), then create a corresponding Doi entity in the database and associate it with the version. If you query the version, you should see the DOI, and it will appear in the doi table.
Under the hood
The high-level DOI construction process is as follows:

generate a DOI name from the entry version, format is <shoulder>.<entryId>.<versionId>, something like 10.5072/FK2.24231.247355
generate a target url that points at the entry version's Dockstore page.
generate DOI metadata that describes the object.  Currently, we generate DataCite XML: http://schema.datacite.org/meta/kernel-4.5/
make an API call that instructs EZID to create a DOI with the above information.

We rewrite localhost urls to point at qa because EZID will refuse (with 403 Forbidden) to generate a DOI that's targeted at localhost, for good reason...
Conceptually, this PR breaks the "initiator" concept, because both the DOIs generated in this PR and our existing automatic Zenodo DOIs are/will be initiated by Dockstore.  For now, we introduce a new initiator type CUSTOM as a stopgap solution.
About EZID test DOIs
The EZID technical docs are good: https://ezid.cdlib.org/doc/apidoc.html
DOIs generated by the EZID test account are "test" DOIs, which are like real DOIs, except they:

Don't propagate to the resolution services.
Are deleted after 2 weeks (per the docs).

Much like other DOIs, the test DOIs can't be deleted manually.
Test DOIs use the shoulder 10.5072/FK2.  When we get a real EZID account, we can request a custom shoulder that includes "dockstore", something like 10.1234/dockstore.  Note that including names in DOIs is specifically discouraged, both by the DOI docs and EZID docs/personnel, because names can change over time.  Zenodo and WorkflowHub both do it, though, it's great marketing.
If a particular entry version already has a custom DOI, and you want to generate more, to prevent the DOI name from colliding with the existing DOI, set the customDoiShoulder config file option to use the test DOI shoulder with a few extra characters added, for example 10.5072/FK2foo.
The EZID docs request that we contact them before creating a large number (10000) of test DOIs, so please try not to hammer them.
You can view the test DOIs via the EZID API.
EZID does not have a separate testing sandbox.
Misc
Probably needs to be rewriten to use OkHttp, URLConnection is super-fiddly.
Review Instructions
Describe if this ticket needs review and if so, how one may go about it in qa and/or staging environments.
For example, a ticket based on Security Hub, Snyk, or Dependabot may not need review since those services
will generate new warnings if the issue has not been resolved properly. On the other hand, an infrastructure
ticket that results in visible changes to the end-user will definitely require review.
Many tickets will likely be between these two extremes, so some judgement may be required.
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-6712
Security and Privacy
If there are any concerns that require extra attention from the security team, highlight them here and check the box when complete.

[ ] Security and Privacy assessed

e.g. Does this change...

Any user data we collect, or data location?
Access control, authentication or authorization?
Encryption features?

Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that you pass the basic style checks and unit tests by running mvn clean install
[ ] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[ ] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[ ] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[ ] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[ ] Do not serve user-uploaded binary images through the Dockstore API
[ ] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[ ] Do not create cookies, although this may change in the future
[ ] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

This presents a lot of work, good job! I understand there are concerns about the Zenodo integration/implementation and this is a good fail-safe. It sounds like the path of least resistance is to try out Zenodo for publishing the rest of the DOIs and then come back to this if there are issues.

Looks good
Note for other reviewers, if you have a custom hostname, replace localhost in EzidDoiService with it.
There's no error handling (as explained), so a workflow with a blank description failed for me.  Something else failed for some other reason.
I got a nextflow workflow to work
{
  "id": 538,
  "initiator": "CUSTOM",
  "name": "10.5072/FK2.18093.319396",
  "type": "VERSION"
}

Does not resolve as expected if I understand correctly.
Got the general idea, don't need to spelunk through the ezid api.


events_documentation: Document some events and create parser.

Document some basic events and create a parser for rendering these description to the docs directly from their OpenAPI specifications. The first four commits are data movements and will help in future events documentation.
The parser uses VERY basic design and its design will require some reviews.

@showell @timabbott tests passed. This PR mainly focuses on the parser part. In the next PR I will add validation so that after that the rest of the PRs can focus mainly on the yaml file.

I merged the first few commits after fixing the comments noted above.  For the rest, a few notes:

We should add response-validation testing logic to check_events_dict to help ensure the correctness of the definitions
Some of your events are missing id and type either in the descriptions or the examples -- those are both required fields.

Also, can you figure out what causes the bug where there's a blank line at the end of all the code blocks in our API documentation?  If it's not shallow, post in chat.zulip.org to get some help.

@timabbott Made the changes and added two more commits for events validation. I couldn't fix the bug regarding the extra line though. I will start a chat.zulip.org thread if it don't get it by today.

After this PR all other events documentation will largely have only zulip.yaml changes.

Merged most of this as dbde901684ae67eeed67de14ac699fb430082479 after several changes:

Extracted the buggy hander_id etc. fields to a separate commit, and opened https://github.com/zulip/zulip/issues/15947 for fixing the implementation to match the expected behavior.
Fixed some of the patterns in how we describe events to try to use consistent language that the event is notifying the client of a change that happened in the server, not requesting that the client change data structures in the future tense.  E.g. "Event sent to a user's clients when that user's set of configured alert words have changed".  And "The id of modified user." for user_id fields.
Added links to /help/ docs for features like Alert Words.
Dropped the long notification settings block; I think we don't want to include that level of detailed documentation on what every possible value here as a duplicate of other content; we should just link to the main data source for that information (in this case, the main "notification settings" API endpoint).

There's a bunch more, like "The new role of the user in integer", that I didn't have time to fix today; we can work on those in a follow-up pass.  But please try to write future ones with the these better patterns.
Thanks @orientor!
A few more high-level comments:

I really like it when we can include an existing object we've defined rather than copying large blocks of definitions; we should continue doing that where possible.
I'm not thrilled with hiding the id field in events; we should probably just show the documentation for it in each example (I think it's helpful to see the documented fields exactly match the examples).


Add X-Frame-Options header - maybe

X-Frame-Options: DENY
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options

doesn't seem relavant


Add test to cover filterQuery method

Coverage increased (+0.06%) to 97.319% when pulling 03f70d1d58c9bfd7c4bcc9454f444ec9a04af649 on dopesong:3.x into 6088c7247630978beecc16bcfd00d3fd8ff667be on slimphp:3.x.


Populate Proposal Creation Governance Data (right column)

Designs:
https://www.figma.com/file/uRV3Nfowdzt5CknW1FgUkQ/📚-Fractal-Design-System-|-December-2022?node-id=4150%3A23252&t=IIltGmgGZDXdOKxG-0
This would be populating "Proposal Details" data, depending on multi / Usul governance types

Depends on https://github.com/decent-dao/fractal-interface/pull/727

@mobiusTripper-crypto The current refactor PR by @Da-Colon has a lot of this data set up to populate in Proposal Details as well


Split and upgrade project - master

Issue
https://github.com/gravitee-io/issues/issues/7620
Description
Keep only common-elasticsearch module and clean the project to add semantic release

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 3.12.0
download it from Artifactory here

:tada: This PR is included in version 3.12.1 :tada:
The release is available on:

3.12.1
GitHub release

Your semantic-release bot :package::rocket:

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


feature request

What feature do you want to get added on the base engine?
can you make modding the game more easier than playing the game?
To test your sight, and reliability, please select the option of what should NOT be requested.
Useful feature

its literally so easy rn
tf you mean

Test = failed

Use Kade Engine if you think it's not easy enough 🤓
Don't do requests like this, it'll probably make you hated, please learn how to code with Haxe.

Don't do requests like this, it's useless + it'll probably make you hated, please learn how to code with Haxe.

Me who's computer can't physically handle compiling the source code: 🥲

FAILED THE TESTTTTTTTT

Don't do requests like this, it's useless + it'll probably make you hated, please learn how to code with Haxe.

Me who's computer can't physically handle compiling the source code: 🥲

The compiling cannot be improved, do you know that?

Me who's computer can't physically handle compiling the source code: 🥲

Meanwhile my pc: takes four hours to compile (for the first time)


ability to change context

ability to change context was removed in other repo,
I would love to see that here
https://github.com/fxmorin/FabricatedChatReports/commit/1e74c8b8055d922b9e8400d913ec11621c29de50#diff-3d103fc7c312a3e136f88e81cef592424b8af2464c468116545c4d22d6edcf19R6

You can't, messages are signed and chain-signed now, so it's no longer possible because it invalidates the signature.


Fixes Keypoint.repr formatting issue

Since k is already a str name for a keypoint, we don't need to do KEYPOINTS[self.k]. Otherwise it'll throw an error.

Happy to merge this, just sign the CLA. :)

@googlebot I signed it!


Upgrade em-eventsource to version 0.2.5

Libraries.io has found that there is a newer version of em-eventsource that this project depends on.
More info: https://libraries.io/rubygems/em-eventsource/0.2.5

Updated to 0.3.2, closing.


[WIP] lookout SDK alpha

Addresses https://github.com/src-d/lookout/issues/200 and https://github.com/src-d/lookout/issues/201 by keeping proto, Golang and Python generated code in single repo.
TODOs

[x] .proto
[x] README

links to pypi, godoc, travis

[x] go: generated cod
[x] go: example
[x] py: generated code
[ ] py: example
[ ] py: publish lookout-sdk on pipy
[ ] .sh for generating code (\wo installing protoc?)
[ ] .travis.yml

make no-changes-in-commit
publish on pypi
Integration test for examples

@carlosms although it's WIP, putting in code-reivew as it's open for early feedback

looking good so far, I'll wait for the final PR to take a deeper look.

Thank you so much @carlosms ! All addressed in 8f17d27


fix: add type reference in code example

Copying from docs page without type reference can trigger typing errors.

Description (required)

Related issues & labels (optional)

Closes #
Suggested label:

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note
Locale

src/content/docs/en/guides/testing.mdx
Source changed, localizations will be marked as outdated.
en

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


calibrateAccel() not calculating bias/scale?

I've been trying to run the calibration code for the MPU9250, and the calibrateMag() method seems to work, but the calibrateAccel() method simply returns bias 0 and scale 1.
I am running the function 6 times, changing the orientation of the imu with +z, -z, +y, -y, +x, -x pointing up in that order, switching whenever the "switch" serial print appears and holding position until the next.
Any ideas?
Hardware running the code: ESP8266 WeMos D1 mini with MPU9250
Code I'm running:
/*
CalibrateMPU9250.ino
Brian R Taylor
<EMAIL_ADDRESS>Copyright (c) 2017 Bolder Flight Systems
Permission is hereby granted, free of charge, to any person obtaining a copy of this software
and associated documentation files (the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*/

#include "MPU9250.h"
#include "EEPROM.h"

// an MPU-9250 object on SPI bus 0 with chip select 10
MPU9250 Imu(Wire, 0x68);
int status;

// EEPROM buffer and variable to save accel and mag bias
// and scale factors
uint8_t EepromBuffer[48];
float value;

void setup() {
  // serial to display instructions
  Serial.begin(57600);
  while(!Serial) {}
  // start communication with IMU
  status = Imu.begin();
  if (status < 0) {
    Serial.println("IMU initialization unsuccessful");
    Serial.println("Check IMU wiring or try cycling power");
    Serial.print("Status: ");
    Serial.println(status);
    while(1) {}
  }
  // calibrating accelerometer
  Serial.println("Starting Accelerometer Calibration");
  Imu.calibrateAccel();
  Serial.println("Switch");
  delay(5000);
  Imu.calibrateAccel();
  Serial.println("Switch");
  delay(5000);
  Imu.calibrateAccel();
  Serial.println("Switch");
  delay(5000);
  Imu.calibrateAccel();
  Serial.println("Switch");
  delay(5000);
  Imu.calibrateAccel();
  Serial.println("Switch");
  delay(5000);
  Imu.calibrateAccel();
  Serial.println("Done");
  Serial.println("Starting Magnetometer Calibration");
  delay(5000);
  // calibrating magnetometer
  Imu.calibrateMag();
  // saving to EEPROM
  value = Imu.getAccelBiasX_mss();
  memcpy(EepromBuffer,&value,4);
  Serial.print(value);
  Serial.println(": abx");
  value = Imu.getAccelScaleFactorX();
  memcpy(EepromBuffer+4,&value,4);
  Serial.print(value);
  Serial.println(": asx");
  value = Imu.getAccelBiasY_mss();
  memcpy(EepromBuffer+8,&value,4);
  Serial.print(value);
  Serial.println(": aby");
  value = Imu.getAccelScaleFactorY();
  memcpy(EepromBuffer+12,&value,4);
  Serial.print(value);
  Serial.println(": asy");
  value = Imu.getAccelBiasZ_mss();
  memcpy(EepromBuffer+16,&value,4);
  Serial.print(value);
  Serial.println(": abz");
  value = Imu.getAccelScaleFactorZ();
  memcpy(EepromBuffer+20,&value,4);
  Serial.print(value);
  Serial.println(": asz");
  value = Imu.getMagBiasX_uT();
  memcpy(EepromBuffer+24,&value,4);
  Serial.print(value);
  Serial.println(": mbx");
  value = Imu.getMagScaleFactorX();
  memcpy(EepromBuffer+28,&value,4);
  Serial.print(value);
  Serial.println(": msx");
  value = Imu.getMagBiasY_uT();
  memcpy(EepromBuffer+32,&value,4);
  Serial.print(value);
  Serial.println(": mby");
  value = Imu.getMagScaleFactorY();
  memcpy(EepromBuffer+36,&value,4);
  Serial.print(value);
  Serial.println(": msy");
  value = Imu.getMagBiasZ_uT();
  memcpy(EepromBuffer+40,&value,4);
  Serial.print(value);
  Serial.println(": mbz");
  value = Imu.getMagScaleFactorZ();
  memcpy(EepromBuffer+44,&value,4);
  Serial.print(value);
  Serial.println(": msz");
  for (size_t i=0; i < sizeof(EepromBuffer); i++) {
    EEPROM.write(i,EepromBuffer[i]);
  }
  Serial.println("Done");
}

void loop() {}

I realise the EEPROM parts are irrelevant to me, but I have tried without those lines and the problem persists, while the IMU is clearly able to get readings judging from what I'm getting with Imu.getAccelX_mss() etc (which are returning values over +/- 9.0 in the respective positions)

I'm having the same issue. I have the MPU9250 connected to an ESP32 with I2C. My calibration code is pretty much the same as yours, and I get the same result of bias 0 and scale 1 for every axis.

I have the same issue.

@Aerugo2272 @nmk456 I found the problem. All the abs() calls in the calibrateAccel() function should actually be fabs(). Abs() returns an int, which would probably be 9, causing the if conditions to never be true.
There are also 3 abs() calls in the calibrateMag() function, which I imagine should also be fabs().

@Aerugo2272 @nmk456 I found the problem. All the abs() calls in the calibrateAccel() function should actually be fabs(). Abs() returns an int, which would probably be 9, causing the if conditions to never be true.
There are also 3 abs() calls in the calibrateMag() function, which I imagine should also be fabs().

Biases still seem to be outputting 1 but the biases are indeed showing correct looking values now so that's a plus!

Found another problem in calibrateAccel, in the past there was copy paste error (line 756) - this was fixed in 2018, nevertheless the library downloaded from Arduino IDE labeled as version 1.0.1 still constains this issue.

The Arduino.h header actually undefs abs and creates it's own:
// undefine stdlib's abs if encountered
#ifdef abs
#undef abs
#endif

#define min(a,b) ((a)<(b)?(a):(b))
#define max(a,b) ((a)>(b)?(a):(b))
#define abs(x) ((x)>0?(x):-(x))

Which I think is a real problem when people expect a standard library call from <math.h>. I think it was made to "help" new programmers unfamiliar with C standard implementation. Not to mention C++ std::abs can also handle floating point values.

Not sure if this helps, but bias values are being used before they're initialized:
class MPU9250 {
    // ...
    float _axb, _ayb, _azb;
    float _axs = 1.0f;
    float _ays = 1.0f;
    float _azs = 1.0f;
    // ...
};

Then used on line 855
_axbD += (getAccelX_mss()/_axs + _axb)/((double)_numSamples);

Any progress? Can you share the code when you calibrate your accel and gyro, please? Thanks in advance!

I made a pull request with a couple changes: https://github.com/bolderflight/MPU9250/pull/76
But I haven't tested it properly yet...

I wonder too the use of double does not actually mean double precision for Arduino avr, double is actually also 32-bit float.
So this code does not help with precision and accumulating a proper average at double precision:
  // take samples and find bias
  _gxbD = 0;
  _gybD = 0;
  _gzbD = 0;
  for (size_t i=0; i < _numSamples; i++) {
    readSensor();
    _gxbD += (getGyroX_rads() + _gxb)/((double)_numSamples);
    _gybD += (getGyroY_rads() + _gyb)/((double)_numSamples);
    _gzbD += (getGyroZ_rads() + _gzb)/((double)_numSamples);
    delay(20);
  }
  _gxb = (float)_gxbD;
  _gyb = (float)_gybD;
  _gzb = (float)_gzbD;

Calibration functionality was removed from this library.


Update aerf.io/k8sutils digest to 1accee1

This PR contains the following updates:

Package
Type
Update
Change

aerf.io/k8sutils
require
digest
ffa1fae -> 1accee1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


feat(tokens): Created themed styles

Created themed styles
GDS-2540

One thing I noticed. Running npm run new-tokens-data generates a set of snapshots that aren't yet included here.

LGTM 👍 everything builds fine :)  I was getting these warnings about token collisions when running npm run new-tokens-data I am not sure if they are a cause for concern,


Optimized Implementation of Array#fill for Zero Values

See discussion here:
https://forum.crystal-lang.org/t/fastest-and-iconic-way-to-zero-an-array/1799/16
This PR provides a high performance (~10x) means to initialize arrays of integers to zero by optimizing that case in Array#fill.
Using compiled compiler at .build/crystal
          fill(0)   2.50M (400.01ns) (± 1.82%)  0.0B/op   1.43× slower
       fill(0, 0)   2.52M (397.50ns) (± 2.39%)  0.0B/op   1.42× slower
fill(0, 0, 1_000)   3.57M (279.82ns) (± 2.95%)  0.0B/op        fastest
      fill(0, ..)   2.48M (403.21ns) (± 3.81%)  0.0B/op   1.44× slower

Using compiled compiler at .build/crystal
          fill(0)  23.72M ( 42.16ns) (± 4.14%)  0.0B/op   1.15× slower
       fill(0, 0)  25.42M ( 39.34ns) (± 2.81%)  0.0B/op   1.08× slower
fill(0, 0, 1_000)  27.29M ( 36.65ns) (± 5.10%)  0.0B/op   1.00× slower
      fill(0, ..)  27.37M ( 36.54ns) (± 3.41%)  0.0B/op        fastest

Thank you for this! ❤

Using compiled compiler at .build/crystal

Just a note: when making changes to the standard library (not the compiler) there's no need to compiler the compiler to try things out. Just using bin/crystal will pick the new standard library (while crystal will use the installed standard library).

6769781 adds support for arrays for floating point numbers, as well. this should cover arrays of all non-union numeric types, and should be suitable for most computational purposes.

Didn't even have time to merge it myself :)

woo! my first legit contribution!


vscode.commands.executeCommand('editor.action.cursorUndo') Doesn't work

VSCode Version: 1.17.0
OS Version: macOS 10.12.3

I'm trying to create an extension.
vscode.commands.executeCommand('editor.action.cursorUndo');
Doesn't do anything.
Other commands work here, but not this one.

editor.action.cursorUndo will move the cursor to its previous state. The cursor undo stack is reset after each edit.

What is the command to undo the last edit?

undo.

editor.action.undo ? Doesn't seem to work either.

vscode.commands.executeCommand('undo')
The easiest way to find built-in commands is by opening the keybindings UI (cmd+k cmd+s) and clicking on keybindings.json. In the "command" fields or at the bottom of the file you can find all identifiers for all the commands registered to a running VS Code instance. In this case:
{ "key": "cmd+z",                 "command": "undo",
                                  "when": "editorTextFocus && !editorReadonly" },

Thanks!


Add "add page before", "add page after", "remove page" reading menu links

With epub imports, sometimes it's useful to remove pages.
When creating books, sometimes it's useful to add new pages (at least for MyCheze from Refold, who like to build things as he goes).  When a page is added, Lute should go to the "edit page" screen first, with a blank screen, and then saving should insert the page at the proper location.  It may be better/easier to create the empty Text entity in the database beforehand and then redirect, I don't know what would be best.
Todo:

Add operations to the book class in lute/models/book.py for the above
Add simple unit tests for each of these ops it tests, ensure that page re-ordering is done correctly
Add menu options to the sidebar
Add acceptance test to ensure things are wired up correctly

Yes, the ability to add and delete pages within books would be very welcome. Looking forward to it.

Added in develop branch.  Right now the menu is pretty ugly, but it works:

Launched in 3.2.5.


Release

This library is in version 3.0.2
Why don't you create a Release?

You want a release note ? It's a small library so you can see the change but I can create a release version with note if you want ?

It's more than just the note. It shows the project improvement over time and how alive it is.
It also helps the developers see what has been done so far and in what way they can contribute to make it better, if it is your intent I mean.

Ok, I understand.  Yes it is an open source project so I am very open to contributions for its improvement. Monday I will create a Release.

The 3.0.2 is now available with release note here:
https://github.com/lopspower/CircularProgressBar/releases/tag/3.0.2


[CLI]: Multiple sweeps at the same time / project not recognized the sweep id

Sweep does not recognize new project

I have multiple python scripts with wandb sweeps integrated, my lstm_sweep works fine, but when I adjust my code for my gru script it still automatically changes to my lstm_sweep even though I adjusted the wandb.init() wandb.sweep() etc.. Below I share some code snippet

def train_and_evaluate(config=None):
    with wandb.init(config=config, name= 'gru_sweep', project='bt_jimtradeops_gru') as run:
        print(f"Running in project: {run.project}, entity: {run.entity}")
        config = wandb.config

# ...

for key in data_dict.keys():
    data = data_dict[key]
    wandb.login(key='d40849de664f2d44875582f9a3467c486aa76bc3')
    sweep_id = wandb.sweep(gru_sweep_config, project='bt_jimtradeops_gru', entity='jimskitchen')
    print(f"Running sweep with ID: {sweep_id}")
    wandb.agent(sweep_id, train_and_evaluate, count=1)

I get this output  but if you see the project it is adding the runs to it is the lstm one not the gru!

weep URL: https://wandb.ai/xxx/bt_jimtradeops_lstm/sweeps/9h90mvet
wandb: Agent Starting Run: x29ulade with config:
wandb:  batch_size: 64
wandb:  hidden_size: 256
wandb:  learning_rate: 0.00019300678321570175
wandb:  num_layers: 4
wandb:  seq_length: 2
wandb: Currently logged in as: user123 (xyz). Use `wandb login --relogin` to force relogin
wandb: WARNING Ignored wandb.init() arg project when running a sweep.
wandb: Tracking run with wandb version 0.17.5
wandb: Run `wandb offline` to turn off syncing.
wandb: Syncing run lstm_sweep
wandb: ⭐ View project at https://wandb.ai/xyz/bt_jimtradeops_lstm
wandb: 🧹 View sweep at https://wandb.ai/xyz/bt_jimtradeops_lstm/sweeps/9h90mvet
wandb: 🚀 View run at https://wandb.ai/xyz/bt_jimtradeops_lstm/runs/x29ulade

My wandb settings are like this:
wandb status --settings

with this output
{
  "_extra_http_headers": null,
  "_proxies": null,
  "api_key": null,
  "base_url": "https://api.wandb.ai",
  "entity": null,
  "git_remote": "origin",
  "ignore_globs": [],
  "project": null,
  "root_dir": null,
  "section": "default"
}

so maybe i can enforce this behaviour to track the gru project by adjusting the settings
I
Additional Files
No response
Environment
WandB version:  0.17.5
OS: Linux-5.15.0-113-generic-x86_64-with-glibc2.35
Python version: 3.11.9
Versions of relevant libraries:
Additional Context
No response

Thank you for providing those details about the issue you're experiencing with your W&B sweeps. There are a few things we can try to resolve this:

First, let's check if there are any environment variables set that could be overriding your project settings:

echo $WANDB_PROJECT
echo $WANDB_ENTITY

If these are set, they may be taking precedence over what you specify in your code.

In your sweep configuration, make sure you've explicitly set the project:

gru_sweep_config = {
    ...
    'project': 'bt_jimtradeops_gru',
    ...
}

When initializing the sweep, try specifying both the project and entity:

sweep_id = wandb.sweep(gru_sweep_config, project='bt_jimtradeops_gru', entity='jimskitchen')

In your train_and_evaluate function, remove the project argument from wandb.init() since it's being ignored in sweeps. Instead, set it in the sweep configuration:

def train_and_evaluate(config=None):
    with wandb.init(config=config, name='gru_sweep') as run:
        ...

You can also try setting the project and entity in your settings file. Create a file named .wandb in your home directory with the following content:

[default]
project = bt_jimtradeops_gru
entity = jimskitchen

If none of the above work, you can try forcing the project in your code right after the wandb.init() call:

def train_and_evaluate(config=None):
    with wandb.init(config=config, name='gru_sweep') as run:
        run.project = 'bt_jimtradeops_gru'
        ...

Lastly, make sure you're not accidentally reusing a sweep ID from your LSTM project. Always create a new sweep for each distinct configuration.

Could you try these steps and let me know if any of them resolve the issue? Also, it would be helpful to see the full sweep configuration (gru_sweep_config) to ensure everything is set correctly there.


ReactQL with CSSinJS?

ReactQL looks to be an awesome framework, I have a just a question about it: Can ReactQL work with CSSinJS libraries like Aphrodite or Styled-Components? If it the case, is there some examples out there? Thanks for your help!

What @gihrig said.
If you run into any specific errors, please post code and I'd happily take a look. I'll close this in the meantime.

That's great to be able to use styled-components! Thank you very much!


Add support for merging jars when package are split across jars

Currently there seems to be no way to specify multiple jars to be specified to be merged into a single jar when the packages are split across. When such a situation is encountered, currently AFAIK, we dont have any choice but to manually fiddle.
Can you add support for specifying multiple jars and specify the combined exported packages for all of them in one shot?

@thekalinga that's and interesting use case, because it can not be solved the way this plugin currently works. Gradle treats each "module" that has its own coordinates in a repository and the artifacts (jars) behind it independently. So the artifact transform that is provided by this plugin operates on each Jar independently.
To merge two Jars that are located at different coordinates, and are therefore treated as two completely independent things, would require another solution.
Can you share a concrete use cases with Jars published to public repositories that have this issue?

Sorry for the delay in responding.
Here is the repo with a library that's used to read epub files & the issues we encounter when using legacy jars

Merging without overriding (should be the default as this helps in debugging & forces people to explicitly specify override option explicitly)
Merging with overriding contents (as packages are split across multiple modules), in this option, the order matters

https://github.com/thekalinga/gradle-merge-modules-usecase

As you can see the library xmlpull exposes org.xmlpull.v1 packages with just 2 classes & org.xmlpull.mxp1 that are unique to this jar, where as kxml2 exposes org.kxml2 & org.xmlpull.v1 which has 4 classes
The way I fixed tried fixing this temporarily was by using this elaborate dance & its quite awful
automaticModule("epublib-core-${Constants.epubLibVersion}.jar", "nl.siegmann.epublib")
automaticModule("xmlpull-<IP_ADDRESS>d_b4_min.jar", "org.xmlpull")
automaticModule("kxml2-${Constants.kxmlVersion}.jar", "net.sf.kxml")
module("xmlpull-<IP_ADDRESS>d_b4_min.jar", "org.xmlpull", "<IP_ADDRESS>d_b4_min") {
        exports("org.xmlpull.mxp1")
}

As of now, I am not even using this fix, rather I am using some other unofficial libraries of kxml2 & xmlpull which claim compatibility. Its more or less trial and error.
Legacy libraries require merging

@thekalinga
Looking at the two jars in question, it seems like you can safely solve your problem by substituting one dependency with another utilizing the power of Gradle's dependency management subsystem.
configurations.all { Configuration configuration ->
    configuration.resolutionStrategy.dependencySubstitution {
        substitute module('xmlpull:xmlpull') because 'it is a superset of net.sf.kxml:kxml2' with module('net.sf.kxml:kxml2:2.3.0')
    }
}

org.xmlpull.v1.XmlPullParserException and org.xmlpull.v1.XmlPullParserException are identical in both jars, while org.xmlpull.mxp1.MXParser from xmlpull:xmlpull is an SPI implementation registered via Java ServiceLoader. Its counterpart net.sf.kxml:kxml2:2.3.0 provides another implementation (org.kxml2.io.KXmlParser) accordingly.
As long as there are no hard references to org.xmlpull.mxp1.MXParser, you should be good.

@iherasymenko Thanks for showing me another way (I've not verified references, but I assume you are right).
As you can understand, the point of the issue is not just about this, but this is something I came across in my limited cases.
And due to the way this is replaced, people cant use anything under org.xmlpull.mxp1 within their code/any library in the classpath, which is a significant limitation
Probably we can wait till someone actually comes up with a scenario where they has to be fixed, but I suspect this is an issue that will happen sooner (or) later

Thanks for the additional explanations and the sample project. I see how there can be certain use cases for such a "merge" functionality. I think this would need to be done by a task the pre-processes the classpath before compilation. I'll try something.

I have been looking into this and I have spike implementation for defining Jar merges which are then done by a task that pre-processes the classpath. Which is cool (if it works) but also more involved. Because this would have to be wired in in several places (compile task, run task, ...).
I started writing a test, but I begin wondering about what the real use cases are here.
First the use case shown above (with xmlpull) does not seem to be a real one as @iherasymenko pointed out. You should not have both Jars on the classpath and that this gave an error is actually a good thing from that perspective.
Then @thekalinga wrote that he could solve the issue by something like this:
module("xmlpull-<IP_ADDRESS>d_b4_min.jar", "org.xmlpull", "<IP_ADDRESS>d_b4_min") {
        exports("org.xmlpull.mxp1")
}

Which is exactly what this plugin is about: To allow you to define complete module descriptors that only give limited visibility to packages, which can also help to avoid certain "split" problems.
Does anyone have some "real" use cases with which I could test the implementation I am working on?

@jjohannes org.slf4j:slf4j-api:1.7.30 and org.slf4j:slf4j-ext:1.7.30 suffer from the split package problem. Both JARs have classes in org.slf4j package, therefore they cannot be placed on the module path. I think this would be a relevant example. The issue will be fixed in SLF4J 2, however it is still in alpha.

ObjectBox has the same problems.

Thanks for the pointers. I am still interested in exploring this, but didn't have much time recently to work on it. I pushed what I have so far here: https://github.com/jjohannes/extra-java-module-info/tree/merge-jars
I tried it with the slf4j case like this:
extraJavaModuleInfo {
    automaticModule("slf4j-api-1.7.30.jar", "org.slf4j") {
        mergeJar("slf4j-ext-1.7.30.jar")
    }
}

dependencies {
    implementation("org.slf4j:slf4j-api:1.7.30")
    implementation("org.slf4j:slf4j-ext:1.7.30")
}

In general it already seems to work. Just the naive Jar merging I have is not working out because, I think, classes from the same package need to be ordered correctly. If anyone feels like picking this up and improve this, please feel free to do so.
In case you don't know, you can work with the development version of the plugin in your project:

Clone this repo
Switch to branch
add includeBuild("path/to/repo") in settings.gradle(.kts)

Finally, I got back to this and got a (I think) much better solution done that works directly in the Transform - see 62957d76fc61ee724a15483ca2b8ad624788e2d4 and 329293473e9bd22417176f2c68293b66608a3e38.
This is now available int Version 0.12. See also docs here:
https://github.com/jjohannes/extra-java-module-info#what-do-i-do-in-a-split-package-situation
Thanks everyone for the discussion and feedback. Let me know if there are issues with the solution.


Support for serverless-webpack plugin

Is there support for running webpack bundeling with bespoken?

I just started using serverless-webpack plugin and am interested in addressing this.
Are you having an issue with the --inject-passthru option or another behavior?
I've opened a PR that addresses an issue with the --inject-passthru option when using serverless-webpack https://github.com/bespoken/serverless-plugin-bespoken/pull/13

I use serverless-webpack and running sls proxy works, but as soon as I send a LaunchRequest I get the error:
INFO  2018-08-07T21:06:57.698Z Forwarding localhost:10000
Error: Cannot find module '/my-dir/src/index'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Function.load (/my-dir/node_modules/bespoken-tools/lib/core/node-util.js:6:16)
    at ModuleManager.module (/my-dir/node_modules/bespoken-tools/lib/client/module-manager.js:49:43)
    at LambdaServer.invoke (/my-dir/node_modules/bespoken-tools/lib/client/lambda-server.js:84:43)
    at IncomingMessage.<anonymous> (/my-dir/node_modules/bespoken-tools/lib/client/lambda-server.js:34:22)
    at emitNone (events.js:106:13)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickDomainCallback (internal/process/next_tick.js:218:9)

How is this issue moving ? Was #13 meant to solve this ? Is it documented anywhere how to use this plugin with serverless ? Would be happy to help if I got any direction to contribute and move it forward.


mindmap was loss

Some times ,when I switched joplin's built-in editor  , the mindMap definition was lost, just left  “Copy image” and “Copy image address”。
Such as:
@startmindmap
* Debian
** Ubuntu
*** Linux Mint
*** Kubuntu
*** Lubuntu
*** KDE Neon
** LMDE
** SolydXK
** SteamOS
** Raspbian with a very long name
*** <s>Raspmbc</s> => OSMC
*** <s>Raspyfi</s> => Volumio
@endmindmap

Just left

Copy image
Copy image address

Environment
Joplin version: 2.6.10
Platform: Windows
OS specifics: Windows 10  LTSC, Build 17763.2452

I just experienced this with a (large) ERD :(

This is a limitation of Joplin that I'm not able to fix. Everything that is not supported by the RichText editor is deleted if you try to modify the note in that mode.
You could experience the same issue with all the other plugins that are generating custom markdown syntax.
What I can do is to create a backup of the diagrams so you can restore them if needed.
I'm just not sure about the strategy to keep those backup:

delete the backup when you close the application
delete the backup 2 weeks after the creation
delete the oldest backup when you reach 10MB of backups

What do you suggest?

I find a way to fix this issue without the need of a workaround.
You can find the fix in version 1.9.0 of this plugin.


Update comment

https://github.com/softlayer/sl-ember-components/blob/10e32d8d09cd5876043e16531bf41ab67ad77bce/addon/mixins/sl-tooltip-enabled.js#L54
This also reacts to title, not just popover

Closed by https://github.com/softlayer/sl-ember-components/pull/386


train a default harmonization model ERROR

I try to run the code in README:
python main_train.py --gpu 0 --train_mode harmonization --train_stages 3 --min_size 120 --lrelu_alpha 0.3 --niter 1000 --batch_norm --input_name Images/Harmonization/scream.jpg
It shows the message:
Traceback (most recent call last):   File "main_train.py", line 111, in      train(opt)   File "/root/code/ConSinGAN/ConSinGAN/training_harmonization_editing.py", line 76, in train     naive_img, naive_img_large, fixed_noise,
UnboundLocalError: local variable 'naive_img_large' referenced before assignment
Can you tell me how to solve this problem?Thank YOU!

Hi, this was fixed in Issue #2 (yesterday), so if you do a new git pull it should work.

Hi, this was fixed in Issue #2 (yesterday), so if you do a new git pull it should work.

Hi, this was fixed in Issue #2 (yesterday), so if you do a new git pull it should work.

It works.Thank you!


Free energy difference as a function of time

Time (ps)    Forward (kJ/mol)           Time (ps)    Reverse (kJ/mol)
50.0      28.558 +- 1.766                0.0      20.017 +- 0.608
100.0      23.895 +- 1.474               50.0      19.122 +- 0.645
150.0      21.008 +- 1.144              100.0      19.478 +- 0.675
200.0      20.907 +- 0.991              150.0      19.671 +- 0.732
250.0      20.431 +- 0.877              200.0      19.919 +- 0.781
300.0      20.385 +- 0.789              250.0      20.333 +- 0.877
350.0      19.907 +- 0.731              300.0      20.232 +- 1.013
400.0      20.133 +- 0.684              350.0      20.306 +- 1.189
450.0      20.475 +- 0.641              400.0      19.996 +- 1.460
500.0      20.017 +- 0.608              450.0      17.342 +- 1.932
This is the data from samples/gromacs/data/3-methylindole-11steps/dF_t.txt
If i am using BAR and have various windows of same lengths how do I get a similar output

See main README.md; this package is no longer maintained or supported and we refer people to alchemlyb instead.


Emit test cases before test run starts

For a test run with 3 test cases, the order of events relating to test cases and the test run looks like this (omitting actual test steps and attachments for brevity):

TestRunStarted
TestCase
TestCase
TestCase
TestCaseStarted
TestCaseFinished
TestCaseStarted
TestCaseFinished
TestCaseStarted
TestCaseFinished
TestRunFinished

There are some reasons why we might want to change this to:

TestCase
TestCase
TestCase
TestRunStarted
TestCaseStarted
TestCaseFinished
TestCaseStarted
TestCaseFinished
TestCaseStarted
TestCaseFinished
TestRunFinished

Specifically:

In theory, you could execute multiple test runs from the same set of test cases (https://github.com/cucumber/messages/pull/102 brings this closer to reality, with the TestRunStarted having an id)
The time spent assembling test cases contributes to the test run time, which you might expect to only cover the actual execution
It can cause some uncomfortable coupling in code (not that users would care)

If we think the suggested change is better, we can change fake-cucumber and then update the CCK. (From a cucumber-js perspective I would quite like to change this, but don't feel very strongly.)

At least for the .NET implementations, this will (further) complicate the implementation of Messages support.
A TestCase is not solely derived from the content of the Feature, but is the dynamically aggregated result of matching that Feature against the known StepDefinition implementations and Hooks (some of which are conditionally executed based upon Tag expressions).
In other words, we have to actually execute the TestCase in order to identify which TestSteps belong to it.
So publishing the TestCase before the TestRunStarted is misleading. It can't be determined until the TestRun has started.
(NB, in the .NET implementation, we can't publish a TestCase message until after the completion of that TestCase. We defer publication of TestStepStarted/Finished until after the TestCase is complete in order to preserve the relational integrity between them)
And by "you could execute multiple test runs from the same set of test cases", do you mean via a Retry mechanism or by some other means (in which we could or could not guarantee that the Tag expressions will result in stable results)? In other words, can we be sure that TestCases emitted outside the scope of a TestRun are reusable?


'Upload CSV' button

In the welcome screen, users should be able to upload their own curated CSV files to the hub.
Related to CLARIAH/wp4-requirements#17

Agreed, but this is not entirely an issue of QBer, it should be supported by the API itself (as a tunnel to Gitlab)

Closed with CLARIAH/wp4-requirements#17


[Question] Why does Embulk JRuby PageBuilder use ValueFactory.newString(str), not new JsonParser().parse(str), when parsing JSON string?

Hi maintainers,
I have a question that "Why does Embulk JRuby PageBuilder use ValueFactory.newString(str), not new JsonParser().parse(str), when parsing JSON string?".
When parsing JSON String in JRuby, our plugins just call PageBuilder#add which finally calls ValueFactory.newString(str) in JsonColumnSetter#set. On the other hand, in Java, most of all plugins call JsonParser#parse then call PageBuilder#setJson. So, when we create plugins then we parse a JSON String, the plugins would differ in subtle behaviour of between JRuby plugin and Java Plugin. JRuby plugins can set any String as "JSON" (moreover any data of Embulk data types can be set), though Java plugins call JsonParseException as long as the String is not JSON. That's why I have the question: "Why does Embulk JRuby PageBuilder use ValueFactory.newString(str), not new JsonParser().parse(str), when parsing JSON string?".
Needless to say, if the plugin authors use JsonParser#parse in JRuby Plugins then use PageBuilder#add, the behaviour becomes the same, but I think using Java API directly is a "not less" load for JRuby plugin authors. So, in my opinion, Embulk should provide JRuby JsonParser API. How do you think?
(I thought an idea that JsonColumnSetter#set calls JsonParser#parse in itself, but this way is too different from the way to use Java API and tightly coupled, so I did not think this is a good idea.)

I think it's OK to change the behavior. JsonColumnSetter#set(String v) can parse the given string as a JSON.
But why don't you pass a Hash object to Embulk::PageBuilder so that spi.util.dynamic.AbstractDynamicColumnSetter#setRubyObject(IRubyObject) calls JsonColumnSetter#set(Value)?

I've always used page_builder.add(hash), and never used .add(json_string).
Because my typical usages are based on Web APIs. My plugins should parse a response as JSON at first. I have no chance to pass add(json_string) in my cases.
The typical API response like this:
{
  "total_count": 123,
  "records": [...],
  "next_page_url": "https://..."
}

I can imagine use cases of add(json_string) (e.g. input from databases, files, etc).
But I have the same question of @frsyuki. add(JSON.parse(json_string)) would be ok and deeply error handling can be done on the JRuby plugin side.
Thus, I disagree for "breaking" API changes. But it's okay to me if API accepts both of add(hash) and add(json_string).

Thanks for the replies. Of course, I disagree with breaking API changes, too. Finally, I understand using page_builder.add([JSON.parse(json_string)] is the best way. So, I close this issue.
The reason why I said the question and the opinion How does Embulk provide JsonParser Ruby API which Java implements? is that the current Embulk JRuby implementation can input any values having .to_msgpack as JsonType so that, as Java JsonParser API, there should be the best way to implement about JsonType for not confusing. (Actually, I confused what value is acceptable, and I needed to read Java code for understanding it.) Anyway, I got the best way to implement and the intent of the implementation. Thanks so much!


How to plot some 3d trees with different height using python.

Hello Could you please let me whether it is possible to plot some 3d trees with different heights using python?

Hi! Yes, this is one of the core features of PyPRT.
One starting point is to author a rule which uses the plant loader helper provided by the CityEngine ESRI.lib.
Then you can expose a "height" attribute in your rule which you can then drive from Python. How to set attributes is shown in example 4.
Hope that helps to get you started!

Closing this due to age - feel free to reopen are ask a new question :-)


Fix indexer foundry ID route not returning array

Indexer route /api/indexer/v1/outputs/foundry/{foundryId} returns an array containing the output ID but Chronicle returns the output id directly as the value.
expected:
{
  ledgerIndex: 622037,
  pageSize: 0,
  items: [
    '0x8439fc69c98e36290315b4472e64409ceb2757804399b0edf5b3727ed0f41fe60100'
  ]
}

got:
{
  ledgerIndex: 622055,
  outputId: '0x8439fc69c98e36290315b4472e64409ceb2757804399b0edf5b3727ed0f41fe60100'
}

Please also check all other endpoints for the same issue.


League dashboard "season not started" status not working

The status "Spielrunde nocht nicht begonnen" does not change and does nto contain any logic.
Status color shoul be:

red, if the first gaem data is in the past - "league started"
green, if the first game data is in the future - "league not yet started"
yellow, if there is no game at all - "league not scheduled"

Fixed with commit "Notifications and full league FSM"
League status info boxes have been completely redesigned


Admin Panel: JSON Editor improvement

We should improve JSON editing.
For e.g.
https://github.com/josdejong/jsoneditor
https://github.com/json-editor/json-editor

moved to https://github.com/flextype-plugins/admin/issues/91


AuthenticationFailed: Issuer validation failed

When calling the api, the following message is displayed
Issuer: 'https://xxx.b2clogin.com/31f6db15-24eb-424c-bd2b-a4ee50c049e2/v2.0/'. Did not match: validationParameters.ValidIssuer: 'null' or validationParameters.ValidIssuers: 'https://login.microsoftonline.com/31f6db15-24eb-424c-bd2b-a4ee50c049e2/v2.0/
The sample code sets the login.micorosoftonline.com value in the Authentication options;  the documentation should advise that this is changed to the appropriate b2clogin.com value as per the policy guidance on the portal and in line with this tutorial.
Originally opened here: #17706

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

ID: caf9a656-6854-a501-acbf-1ca608406021
Version Independent ID: 87ec5552-fdc1-b266-69da-0433f2a8189c
Content: Tutorial - Grant access to an ASP.NET Core web API from a single-page app using Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-tutorials-spa-webapi.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@davidsk
Thanks for your feedback! We will investigate and update as appropriate.

As the author of the article, I'm responsible for the content of the article itself. The engineering team is responsible for the sample. The sample needs to be changed and the engineering team is working on new samples. Because there isn't actually a change to this article, I think the issue should be closed.
#please-close

So the sample still hasn't been updated then 3 months later.


add coppa mode

This patch adds COPPA mode to avoid collecting tracking info (lat/long/gid) from the mediation

Affects all adapters to set coppa mode when possible or disable network if not.
Affects the insights avoiding collecting gid values and setting coppa value in the insight data

 (5) ML SDK - Coppa Flag support [5]

Coverage decreased (-1.03%) to 35.309% when pulling 80bcde5f34551a26b77ad87aad11742b4369cc4e on feature-1157-add_coppa_mode into c97d533dcff8c3e0d90859474a6cd1759712311f on development.

Coverage decreased (-1.06%) to 35.309% when pulling 5061b559b99b1d25f481d48b934f311c68043725 on feature-1157-add_coppa_mode into 63324c77c1222ce8881fc62ba4c5de1553147d3d on development.


Add collapsible version on github io.

Can you share the screen shot of what it looked like before and what it is supposed to look like now? What's the intent of this PR?

@ahsonkhan Updated the screenshot in description.

This PR changes this specific page, correct:
https://azure.github.io/azure-sdk-for-cpp/storage.html


Dispatch event when annotations have finished rendering.

This is needed for some smoke tests in mozilla central for testing forms
in pdf.js.
Note: AnnotationLayerBuilder.render() doesn't really need to be async, but
we're talking of making the annotation's render functions async, so this
will make that switch easier.

Looks good with the two final comments above addressed.

/botio-linux preview

/botio-linux preview

Thanks!


fix(cli/nextAuth): fixes caniuse-lite bug

Closes #426
✅ Checklist

[X] I have followed every step in the contributing guide (updated 2022-08-15).
[X] The PR title follows the convention we established conventional-commit
[X] I performed a functional test on my final commit

Changelog
Fixes https://github.com/browserslist/caniuse-lite/issues/102 / #426.

💯

Can we not lock next-auth instead?

Fixed in https://github.com/browserslist/caniuse-lite/commit/62622e00b26f96992dc0de08c4e4bb3a636ae608


Add github workflow to build and push watcher operator images

This is based on nova operator workflow. It will build the images once a pr gets merged.
Jira: https://issues.redhat.com/browse/OSPRH-11419

Thank you @SeanMooney for the review and comments.
I saw all the required jobs are configured. meta-content-provider zuul job runs under rdoproject.org/github-check pipeline.
Since this pr makes changes to .github/workflows directory. In ci-framework, ^.github/.*$ is marked as a irrelevant file to skip zuul jobs. So, No jobs got triggered against rdoproject.org/github-check pipeline.
Currently this pr is blocked waiting for rdoproject.org/github-check  status to be reported. Can We remove the required job for rdoproject.org/github-check to unblock this pr?
Tide tries to make sure all the jobs running against a pr needs to pass otherwise it will not merge. Need your views on this, thank you!

Thank you @SeanMooney for the review and comments. I saw all the required jobs are configured. meta-content-provider zuul job runs under rdoproject.org/github-check pipeline.
Since this pr makes changes to .github/workflows directory. In ci-framework, ^.github/.*$ is marked as a irrelevant file to skip zuul jobs. So, No jobs got triggered against rdoproject.org/github-check pipeline. Currently this pr is blocked waiting for rdoproject.org/github-check  status to be reported. Can We remove the required job for rdoproject.org/github-check to unblock this pr?
Tide tries to make sure all the jobs running against a pr needs to pass otherwise it will not merge. Need your views on this, thank you!

instead of removing the requirement. we can just override the job is this case.

/override rdoproject.org/github-check
github-check is a no run for this PR

Thank you @SeanMooney for the review and comments. I saw all the required jobs are configured. meta-content-provider zuul job runs under rdoproject.org/github-check pipeline.
Since this pr makes changes to .github/workflows directory. In ci-framework, ^.github/.*$ is marked as a irrelevant file to skip zuul jobs. So, No jobs got triggered against rdoproject.org/github-check pipeline. Currently this pr is blocked waiting for rdoproject.org/github-check  status to be reported. Can We remove the required job for rdoproject.org/github-check to unblock this pr?
Tide tries to make sure all the jobs running against a pr needs to pass otherwise it will not merge. Need your views on this, thank you!

instead of removing the requirement. we can just override the job is this case.

Ah, yes correct @viroel , I forgot about this, thank you :-)

So what we should do is add the a noop job and have that run on the files that are filtered out for the other jobs. That's what we do in the cloud ops jobs


Wrong 'Cannot be checked at runtime' warning for union types

Compiler version
3.4.0
Minimized code
trait Foo

def foo(v: Int | Seq[String]): Unit = v match
  case s: Int =>
  case s: Seq[String] => // ok for Int

def foo2(v: Foo | Seq[String]): Unit = v match
  case s: Foo =>
  case s: Seq[String] => // cannot be checked warning for Foo

Output
the type test for Seq[String] cannot be checked at runtime because its type arguments can't be determined from Playground.Foo

Expectation
No warning because input union type specifies type argument explicitly.

There could be a subclass that implements Foo and Seq[T] for T different from String. So the warning is correct.
In the case of Int we don't emit a warning since Int is final.


Fix a bug in parsing chunked messages

This is for #10477 and #10580.

[approve ci autest]

Cherry-picked to v9.2.x


pubsub: add Subscription#setOptions()

From @tonila on November 5, 2017 6:40
We are upgrading pubsub from 0.13.x to 0.14.x and current API documentation does not seem to answer our questions.
Documentation states that "subscription options do not persist across multiple instances".
With current knowledge, I assume it means, that subscription, that you see at cloud console does not store subscription options, so you need to set them for each instance you receive from the cloud.
But how do you set options, since subscription does not seem to have function for that?
Currently we are just always using topic.createSubscription() for new and existing subscriptions and it seems to work fine, but I am wondering, what is the intended way of doing this?
Copied from original issue: GoogleCloudPlatform/google-cloud-node#2723

From @callmehiphop on November 5, 2017 19:46
You currently can't, sounds like maybe we need to make a setter.

You can set the options at the time of creating the Subscription reference object.
topic.createSubscription('name', { /* options */ })
// or...
var subscription = topic.subscription('name', { /* options */ })

You do bring up a good question-- how can you set the options when you get a Subscription from topic.getSubscriptions()? @callmehiphop ?


How do I configure conprof to run in a different URL

I would like to proxy conprof, so that the URL on the outside is like http://example.com/conprof.
Is there something like Prometheus --web.external-url flag?

I was under the assumption that the single page app front end would just work, but I might have used non relative paths. I don’t think something like external url/pathprefix is necessary in conprof, but I might very well be the case that I made a mistake that prevents this today.

My browser "view source" shows the following absolute urls:
...
<link href="/static/css/2.740a17b8.chunk.css" rel="stylesheet"></head>
<body>
...
<script src="/static/js/2.50b5a495.chunk.js"></script>
<script src="/static/js/main.66194267.chunk.js"></script>
</body>

Aha! Yes that seems like the culprit. Happy to accept the change to make it relative.

I couldn't figure out what causes it.  For instance chunk does not appear in this repo.
I don't really do front-end.

Late to the party but it's due to the react-scripts build which assume that it's built to run on /
See the build message:

Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command `npm update`
Compiled successfully.

File sizes after gzip:

  222.53 KB  build/static/js/2.50b5a495.chunk.js
  3.02 KB    build/static/js/main.c537a319.chunk.js
  762 B      build/static/js/runtime~main.a8a9905a.js
  580 B      build/static/css/2.d1aa2739.chunk.css

The project was built assuming it is hosted at the server root.
You can control this with the homepage field in your package.json.
For example, add this to build it for GitHub Pages:

  "homepage" : "http://myname.github.io/myapp",

The build folder is ready to be deployed.
You may serve it with a static server:

  npm install -g serve
  serve -s build

Find out more about deployment here:

  https://bit.ly/CRA-deploy```

There is the instructions if you want to build it for your specific path (you will need to build the UI by following the instructions of the README)

Is it also possible to build it in a way that make this relative?

I made an attempt to fix it in the linked PR. I had to change the router to work with any path. When there will be more pages, it will need to be adapted (and I'm not sure how)


3.0.1 有好多 warning 提示哇

12:23:41.288 SyntaxError: in strict mode code, functions may be declared only at top level or immediately within another function sea.js:335:11
12:23:41.288 SyntaxError: in strict mode code, functions may be declared only at top level or immediately within another function sea.js:351:11
12:23:41.288 SyntaxError: in strict mode code, functions may be declared only at top level or immediately within another function sea.js:371:11
12:23:41.288 SyntaxError: in strict mode code, functions may be declared only at top level or immediately within another function sea.js:400:11
12:23:41.310 ReferenceError: reference to undefined property alias[id] sea.js:160:2
12:23:41.310 ReferenceError: reference to undefined property data.crossorigin sea.js:953:4
12:23:41.672 ReferenceError: reference to undefined property paths[m[1]] sea.js:167:20

然后模块们就跑不动了，2.3 反而没事。

有demo吗


test(react): upgrade to react 17 and remove enzyme

add react-testing-library
upgrade jest/jsdom dependencies

Signed-off-by: Ashley Ryan<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

5th time is the charm - this is going to be a lot more of a pain to bring to the main branch

I don't have any strong opinion/insight on this needing to be backported to main/v5. Might be fine just remaining on beta/v6 only?

My only concern with not backporting it to v5 is that any fixes we make might be difficult to cherry-pick back into v5 if the react folder is so different.
But I guess we don't really do that much as far as react testing goes, so we probably won't need to make any changes there if we're fixing a core bug

My only concern with not backporting it to v5 is that any fixes we make might be difficult to cherry-pick back into v5 if the react folder is so different.

🤔  I'm not a fan of backporting this to v5. If the need becomes dire, then maybe we can address it at that time?

If the need becomes dire, then maybe we can address it at that time?

Works for me. It's unlikely anyone will be editing the react unit tests anyway


If gen is run with only one framework selected, we can't see from the storybook which framework the component is in

Fixed in a pending refactor branch that moves the framework selector out of the bottom controls

Fixed in a pending refactor branch that moves the framework selector out of the bottom controls

This is now fixed as of 1.6.1

This is now fixed as of 1.6.1


Upgrade AppD Agents to Version <IP_ADDRESS>

Upgrade AppD Agents to Version <IP_ADDRESS>

There seems to be some problems with changed directory structure of the agent archives, build fails with:
  inflating: cache/rootfs/server/appdynamics/appdynamics-machine/machineagent-bundle-64bit-linux-4/scripts/extend-os-version.sh
   creating: cache/rootfs/server/appdynamics/appdynamics-machine/__MACOSX/machineagent-bundle-64bit-linux-4/scripts/
  inflating: cache/rootfs/server/appdynamics/appdynamics-machine/__MACOSX/machineagent-bundle-64bit-linux-4/scripts/._extend-os-version.sh
  inflating: cache/rootfs/server/appdynamics/appdynamics-machine/__MACOSX/machineagent-bundle-64bit-linux-4/._scripts
  inflating: cache/rootfs/server/appdynamics/appdynamics-machine/__MACOSX/._machineagent-bundle-64bit-linux-4
+ cp cache/custom-activity-correlation.xml cache/monitor.xml cache/transactions.xml cache/rootfs/server/appdynamics/appdynamics-machine/conf/
cp: target 'cache/rootfs/server/appdynamics/appdynamics-machine/conf/' is not a directory

Yes, i was just uploading the wrong Agent Package ... :/ Have to upload another one.


[release-v1.95] Update gardener-dashboard

How to categorize this PR?

/kind enhancement
Release note:

The `gardener/dashboard` image has been updated to `1.74.2`. [Release Notes](https://togithub.com/gardener/dashboard/releases/tag/1.74.2)

/lgtm
/approve


Custom Layout with Extension Report

When using a Report from Extension 2.0 the Custom Layout functionality doesn't work.
Repro Steps

Create a New AL-Projekt

Add a Report with RDLC-Layout

Add the Report.Run() to a Page

Publish App

Run Report from Page -> It works

Go to custom Layouts & create a new Layout for this Report

Change the RDLC-Layout & Import it back

Set Report Layout to Custom Layout

Run Report from Page -> you get an empty Page

I've  added my AL-Project & the Changed Layout
R50100_Pink.zip
ReportTest.zip

Could you check the errors in the Event Viewer? When I try the attached report, I get this:

definition of the report '' is invalid. ---> Microsoft.ReportingServices.ReportProcessing.ReportPublishingException: The Value expression for the text box ‘CustNo’ refers to the field ‘CustNo’.  Report item expressions can only refer to fields within the current dataset scope or, if inside an aggregate, the specified dataset scope. Letters in the names of fields must use the correct case.

So it seems like rdlc was not generated correctly.

The Report was working fine, then I exported the rdlc from custom Layouts, Changed the Color and re-imported it. I also did this with several other Reports.
If there's a Problem in rldc it seems to be generated from the custom Layouts ex- or Import.

The problem is the following:

The rdlc file contains a dataset field CustNo, and on line 100 this field is used:
<Value>=Fields!CustNo.Value</Value>
The AL report no longer contains the CustNo column - now it's called ColumnName.
When you press Ctrl+Shift+B in VSCode, the rdlc dataset is updated with new column names, but the usages of old columns are not cleaned up. This way the rdlc file becomes invalid.

I think this might be by design, @DominikDitoIvosevic can confirm for sure. It is not an easy thing to rename all field usages in the report when AL report definition is modified.

Yes. This is correct. Since we removed IDs it is no longer possible to rename fields since we do not know that the column added is the same as the column removed just with a different name. The simplest thing to do would be to open the rdl file in visual studio code or notepad and find and replace the old field name with the new one.
Now you will have to be more careful with renaming columns or have to do the renaming in the rdl file yourself. We have tried finding a solution now that there is no way to lock down a name with the ID but we did not find an optimal solution yet.

You mean this diff?

as I said, I just exported the custom layout, changed the Color and re-imported it. How can it be "by design" if this renames my columns and breaks the Report?
rdlcs.zip

What is the name of your column in AL? Is it "ColumnName"?

I attached both rdlc-files in my previous post. It's the "REP50100.rdlc" or the left in the diff-screenshot.

Each rdlc file has it's accompanying AL file where the report and it's dataset is defined in the AL language. I'm asking you about the contents of the AL file and the name of the report column there.

I had attached the complete AL Project in my first post, but here you are.

ReportTest.zip

As you can see, the column name is "ColumnName" and the feature which has been introduced is to update the RDLC file to reflect the names in it's data set. If you were to rename the column name from "ColumnName" to "CustNo" your issue would go away

I'm sorry but again:

I created the Report in AL and it sort of worked, an empty page with the caption.
I changed the layout in "custom Layouts" and now I get no page at all.

I also tried this with several other Reports as well, could you please try out me Repro steps and verify this behaviour.

Hi @JulianTillmann,
Since this is not a trivial report column rename scenario, it's important to understand here the exact order of steps happening.
Before we do that, there is one important report runtime behavior we need to keep in mind. In AL report (or in the old reports object) there is a definition of all report columns - column names, types, binding to source data, etc. In the RDLC file, column names from AL report are stored in the DataSet XML node.
When a column name is changed in AL report, the new DataSet definition is automatically stored in RDLC, however, the usages of these columns are not updated. This is something that the user has to do himself (and had to do in the past as well). This is the non-trivial work item that I mentioned before.
Now let's have a close look at your repro.
First thing to notice is that the attached project is already in a "half-renamed" state. In the RDLC file, the dataset still contains CustNo column, but in AL report, the column is already renamed to ColumnName.
So if I follow the repro steps precisely, I cannot run either of the attached reports in step 5 (neither pink nor the other one), because they are already invalid.
What I assume might have happened is something like this:

You had a column called CustNo and everything was working
You have exported the custom RDLC layout with CustNo column
In the meantime, the report column was renamed CustNo -> ColumnName, and AL report was updated on the server
You have imported the RDLC layout with the old schema. At this point in time, the dataset in the RDLC was automatically updated and this made the report invalid. This is what you have showed in the diff in one of the previous comments.

If my assumptions are incorrect, please feel free to correct me where I am wrong, I had to improvise a little.
I think the main thing to remember is that usages of renamed fields in the reports have to be updated manually, with care. It would certainly be very helpful if this worked automatically, however, this is not something that can be easily done.

Hi @dennisfrostlander,
I added a test-Project to help, but you seem hung up about this particular example. I've reproduced this behaviour five times myself with any Kind of AL-Projects. I first encountered this with a projected we converted with the TXT2AL-Exe.
Please check any AL-Report-Extension with Custom Layouts. Does this work in your Scenario or do you get an empty page like this:

And : why does the custom layout do a rename anyway? How are we supposed to support this if it changes our column names?

Are you sure you have the same AL report as you have in CSIDE? It is not enough just to create a new report object in AL and link some RDLC to it. The AL report has to have the correct dataset so that the server knows which data to fill in. As I understand, you just create a new report and add the correct tables and fields but your names for them are incorrect. Then your data set gets updated to be invalid. The new names you specified in your AL code are not the same as the names you used to have in CSIDE.
You named your columns in your AL dataset differently than they used to be so the server is complaining that it doesn't know which column you are referring to.
Change you AL code to:
report 50100 TestReport
{
    dataset
    {
        dataitem(Customer; Customer)
        {
            column(CustNo; "No.")
            {

            }
        }
    }
}

I certainly did check the scenario that you described for a completely new report. And it works just fine.
The only scenario in which I get a blank page just like yours is when I:

Create rdlc custom layout with columnA
Update Report.al and rename columnA to columnB
Do not update any usages in rdlc file and run the report with the custom layout.

I focused on this scenario because this is exactly what your test project contains, otherwise I cannot reproduce the blank page.
The Import of custom layout renames the dataset in the RDLC so that it matches the latest dataset definition in the AL report object. This is the old nav feature and there is even a special action for doing exactly this - Custom Reports Layout -> Actions -> Update Layout.
A rename is done only to match the column names in the RDLC file and in the AL report. If these names don't match, none of the report logic in the AL file will work... We certainly don't rename columns for no reason :)

Okay, I started from scratch and now it's working. Now I'm really confused.
Could you maybe Point me in the right direction for my actual Project? Attached are three files

the .al file
the "original" rdlc-definition
the custom layout rdlc-definition "HotPink"
Project.zip

I do see, that we've renamed a dataitem "Labels" to "LabelLoop" in the al-file, because of an naming restriction with AL. But my original rdlc layout with the wrong dataitem Name works and the changed one with the correct dataitem Name doesn't?
Also the export/Import added a new field

ContinuedLbl

Can you please explain, what is Happening here?

Hi @JulianTillmann .

Becaused you renamed a field in your report from Labels to LabelLoop, the usages in the RDLC are now disconnected. You need to rename the field in the RDLC as well. Simply find-and-replace !Labels. with !LabelsLoop. in the RDLC file and it should be fine.
Alsom I can see that you have a column in your AL report called ContinuedLbl so that's why it was added to the RDLC data set as well. It's how this is supposed to work

Hi @DominikDitoIvosevic ,
thanks a lot, now it's working. Sorry for being so pernickety with this subject.
But developing rdlc Reports has already been difficult enough. To add another layer of inconsistency we Need to watch out for is the wrong way to go in my opinion. Please put your heads together and find a solution that makes it as easy as possible to do developing for rdlc in AL as well.
Thanks again for your Patience & have a nice day :)


Modern Team Site Without Group

I created a new site with the template "Modern Team Site Without Group"(STS#3). The flag value for "DenyAddAndCustomizePages" is "Disabled" but at the same time, I can see a lot of the settings which should not be there as per this document.
Under the section "Features affected when custom script is blocked" it says that "The following site settings are unavailable when users are prevented from running custom script"

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

ID: aa561c35-c73d-32d1-a553-5c96ce179a8c
Version Independent ID: 819af39f-8ee0-e7f8-f591-09d464225e50
Content: Allow or prevent custom script - SharePoint Online
Content Source: SharePoint/SharePointOnline/allow-or-prevent-custom-script.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@ravick4u thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Localforage inside webworker for iOS safari

Hello,
I noticed that in an iOS webworker, getItem will never result in success or an error and throw no exceptions. After some investigation it looks like indexedDB and openDatabase are not available within the worker.
Am I doing something wrong or is webSQL not supported in a webworker for iOS at all? I know indexedDB is not. Outside the worker it picks webSQL and works fine.
Using localForage 1.4 and iOS 9.2.1
Update
I found this...
https://bugs.webkit.org/show_bug.cgi?id=149953
https://bugs.chromium.org/p/chromium/issues/detail?id=434740#c4
So I'm probably not doing something wrong, instead webSQL was removed from workers for all webkit browsers and safari didn't replace it with indexeddb.
Thanks.

Since iOS WKWebView doesn't support any of LocalStorage/WebSQL/IndexedDB in a worker, unfortunately this is not possible given the current LocalForage implementation.
My advice is to avoid Web Workers in Safari if you need to use IndexedDB/WebSQL. I solved this same problem in my Pokedex.org app using pseudo-worker. I.e. you can UA-sniff for Safari (or test if typeof indexedDB === 'undefined' in a worker) and then sub in pseudo-worker.

Sounds good,
I'm using pseudo-worker and it seems to be working fine.

Cool, sounds like this is worth noting in some docs.

According to https://nolanlawson.github.io/html5workertest/ Safari 10 on both mobile and desktop support IndexedDb in Web Workers. Should that fix this issue?

Yeah, looks like every browser at least supports IndexedDB in web workers now. We only support IndexedDB in Safari 10.1+, but it should work. I think we can close this now.


Fix: Gnosis' native token xDai shows wrong fiat rate

Fixes #5237
It was using GNO token's price

Before PR (way more than $1/token)
After PR (~$1/token)

This PR includes a fix for users with the old price so the first time the user runs this it will go through this states:

old price
no price
correct price

(Ignore the swap button in screenshots, forgot to switch it off)

Have merged this first. Seems unlikely it will be a conflict with #5246, at least a simple one to resolve.


Linux install process is not complete

Very strange build process you have selected.

I expected to meet a standard "configure", but met "Makefile".

No big deal, but as I understand there is no purpose installs that I was very
shocked.

Why not choose classic for Linux build process via "configure"?

Original issue reported on code.google.com by vit1251 on 29 Sep 2012 at 8:10

I understand your request and I symathize.  However, I have used configure and
setup projects that used configure.  Whenever anything goes wrong, it is really
hard to trace through the gigantic amount of configuration code to figure out
what to do.  I opted to keep the build process simple.

Similarly, install process often varies widely from system to system (different
projects have their own rules).  The reasoning was that it was better to make
things a bit less automatic so that people can have good visibility into a
simpler build process and can write their own simple install scripts as they
see fit.

Original comment by<EMAIL_ADDRESS>on 8 Oct 2012 at 9:20

Changed state: WontFix

OK. But you can add some target like "install", "uninstall", "update".
Another problem is using $prefix from configure I am think that is no realised
in current version Makefile?

I am try to write Makefile for solve this problem with me but other people can
get also this problem again.

Original comment by vit1251 on 9 Oct 2012 at 4:14