Breaks on "use strict" line 1

You can test it on:
http://spcultura.prefeitura.sp.gov.br/busca/##(global:(enabled:(event:!t),filterEntity:event))

PR #62 looks more sensible regardless, so it's merged. I still get a cryptic error on this tho, so I'll leave the issue open until we figure it out.


Is there a way to update query params?

Is it possible to update / alter query params after subscribing? The reason why I'm asking is that I'm working on a data table and it should be possible to change sorting persistently. Currently I'm just refetching the data, however on a create or update it goes back to the original defined sorting.
I guess the proper way is to unsubscribe and then subscribe again with the new query params?

I did that with RXJS directly:
const service = app.service('messages');
const query = new RxJS.BehaviorSubject(props.query || {});

const find = query.mergeMap(query => service.find({ query }));

find.subscribe(data => console.log('Data is', data));

query.next({ $skip: 10 });

Awesome thank you


Add BackgroundLogger to robot.api.logger

The robot.api.logger should provide a helper class to log from background threads. https://github.com/robotframework/robotbackgroundlogger provides such functionality and it should be included in our api.

Reverted the BackgroundLogger from 2.8.7 (02fcc63). We were not sure what the API should be to support use cases in #1791 and #1887 so we decided remove it for now because we dont want to commit to an API that might change.

We decided to descope this from RF 2.9 because there still are open question related to how this should actually work. We also want to get RF 2.9 is released ASAP and don't thus have time to investigate this at the moment.

Unfortunately no time for this in 3.0.


Make chart config UI reflect the state of the data in the chart.

At the moment, if you change the global UI, it updates the charts for that dashboard, but doesn't update the UI for each chart accordingly.

Moved to https://github.com/Financial-Times/next-beacon-dashboard/issues/288


CMake build system: PDBs are not being installed for libraries

On Windows, when using MSVC compiler and configuring CMAKE_BUILD_TYPE to "Debug" or "RelWithDebInfo" the build system does not produce consistently named debug symbols across generators (vc140.pdb with Ninja vs libname.pdb with Visual Studio). More, the debug symbols (*.PDB) are not being installed.
The missing PDBs generate ugly flood of warnings when one tries to link to the gRPC libraries from an own project:
5>grpc++.lib(insecure_credentials.cc.obj) : warning LNK4099: PDB 'vc140.pdb' was not found with 'grpc++.lib(insecure_credentials.cc.obj)' or at '<OWN_PROJECT>\vc140.pdb'; linking object as if no debug info 5>grpc++.lib(channel_cc.cc.obj) : warning LNK4099: PDB 'vc140.pdb' was not found with 'grpc++.lib(channel_cc.cc.obj)' or at '<OWN_PROJECT>\vc140.pdb'; linking object as if no debug info

See pull request #9599


Phoenix v1.7.14 released

Change Overview

assets/.eslintrc.js: modified
assets/.gitignore: added
assets/jest.config.js: added
assets/js/phoenix/socket.js: modified
assets/package-lock.json: modified
assets/package.json: modified
assets/test/channel_test.js: modified
assets/test/presence_test.js: modified
assets/test/serializer_test.js: modified
assets/test/socket_test.js: modified

Updates done ✅


No longer able to use write_smt2 with circuits that have async-reset FFs (without clk2fflogic)

I have a project that calls the write_smt2 backend on a circuit that has asynchronously reset flip-flops. I was originally using techmap to replace them with an equivalent circuit, but that no longer works after commit 09071afe. Here's an example input file:
module test(
    input clk,
    input rst,
    input d,
    output reg q
);
always @(posedge clk or negedge rst) begin
    if (!rst) begin
        q <= 1'b0;
    end else begin
        q <= d;
    end
end
endmodule

Running the following:
read_verilog test.v
prep
techmap -map +/adff2dff.v

Gives:
3.1. Executing Verilog-2005 frontend: /usr/local/bin/../share/yosys/adff2dff.v
Parsing Verilog input from `/usr/local/bin/../share/yosys/adff2dff.v' to AST representation.
/usr/local/bin/../share/yosys/adff2dff.v:14: ERROR: syntax error, unexpected TOK_REG

I figured that this approach may now be deprecated in favor of async2sync, however this results in a different issue since as of 4a05cad7 async2sync replaces adffs with sdffs, which are also not supported by the write_smt2 backend. For example, running this on the same input file:
read_verilog test.v
prep
async2sync
write_smt2

Gives:
4. Executing SMT2 backend.
; SMT-LIBv2 description generated by Yosys 0.9+3911 (git sha1 cc7d18d2, clang 12.0.0 -fPIC -Os)
Creating SMT-LIBv2 representation of module test.
ERROR: Unsupported cell type $sdff for cell test.$procdff$3.

One way I can get this circuit into a state accepted by write_smt2 is by using clk2fflogic, but this feels a bit heavy-handed to me.
Is this considered an issue? I'd be happy to help by contributing a PR, but I'm not sure what the best approach to resolving this would be. I could imagine either fixing write_smt2 to transform sdff cells, or modifying async2sync to no longer emit them (like it was prior to 4a05cad7).

Regarding the techmap issue:
The declaration in adff2dff.v is illegal. Per Section 6.7.1 of the LRM:

A net type keyword shall not be followed directly by the reg keyword

I believe we should:

Declare NEXT_Q as simply a reg in adff2dff.v
Add proper test coverage for the adff2dff functionality, if it is still relevant
Consider adding coverage that ensures everything in techlibs gets past the frontend. It may prudent to run certain files through with, say, multiple LUT_WIDTHs

3. Consider adding coverage that ensures everything in techlibs gets past the frontend. It may prudent to run certain files through with, say, multiple LUT_WIDTHs

Agreed, this would be very nice to have!

Run dffunmap after async2sync — this will break up the $sdff.

I've submitted #2601, which will at least give a hint on how to solve the problem.

Thanks all for the quick replies and fixes! In particular, thanks @mwkmwkmwk for the pointer to dffunmap and including that tip in error messages - that seems super helpful.


Autocomplete for model names not working

Expected behavior
whenever I type {{ ref() }} there should be list of suggestions showing all the models in my project.
Actual behavior
There is no suggestion list and pressing ctrl + space does not show any of the models in the project.
Steps To Reproduce

Create a .sql file
In the from clause type {{ ref() }}
Press ctrll + space
The list of suggestions does not contain any models from the project

Log output/Screenshots

Operating System
macOS Monterrey (Intel)
dbt version
1.3.0
dbt Adapter
Snowflake
dbt Power User version
0.8.7
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

The autocomplete is triggered by entering a quote.
This is actually something that can be improved.

Fixed in 0.8.8. Let me know if it works.


Update dependencies

Replace this line:
- **Breaking** Updated to half 1.8, smallvec 1.7, winit 0.26, raw-window-handle 0.4.

with this:
- **Breaking** Updated to ash 0.35, half 1.8, smallvec 1.7, winit 0.26, raw-window-handle 0.4.

And add:
- **Breaking** `ColorSpace::DciP3Linear` is renamed to `DisplayP3Linear` to match an equivalent change in the Vulkan naming.
- Updated vk.xml to 1.2.203.

Just keeping up to date. vk-parse had an update that fixed some errors, so an updated vk.xml can be used now too.

@Rua Merged. :+1:


Add Feature Completions and Remote Kills to Split details screen

Summary
Since we added "remote kills" and "feature completions" to the TestTrack feature set, we have not updated the Admin UI to display them. This PR adds both of these features as tables on the split details screen.
feature gate with feature completion and remote kill

feature gate with no completions

experiments don't use feature completions

experiment with no completions and no remote kills

Other Information
I also upgraded to mini_racer because i couldn't run the app locally otherwise.
/domain @Betterment/test_track_core
/no-platform

One comment on wording

One comment on wording

bump!
i ended up having to sneak some rails 5.2 stuff in here because the app was not working properly locally without those changes. there's still some funkiness with auto-loading, but we can figure that out separately

bump!
i ended up having to sneak some rails 5.2 stuff in here because the app was not working properly locally without those changes. there's still some funkiness with auto-loading, but we can figure that out separately

bump @aburgel
i'm just trying to determine if we can remove some of the environments/ files

bump @aburgel
i'm just trying to determine if we can remove some of the environments/ files

i'm just trying to determine if we can remove some of the environments/ files

determined! and deleted.

i'm just trying to determine if we can remove some of the environments/ files

determined! and deleted.

domainlgtm!
looks like travis is choking on the ruby 2.4 build. i'd say it's time to retire that version.

domainlgtm!
looks like travis is choking on the ruby 2.4 build. i'd say it's time to retire that version.


Problems with yarn start on localhost

yarn start on localhost is pointing to https://api.kitwallet.app and getting error blocked by CORS policy: No 'Access-Control-Allow-Origin' header
Should yarn start be pointing to testnet (https://testnet-api.kitwallet.app) and CORS policy allow localhost?

NETWORK_ID=testnet yarn start solved the problem above

The app is behaving like this on localhost, is it expected?
https://github.com/near/fast-auth-signer/assets/11918567/459f5b98-89e9-4f68-9ed9-74f413de3314

@johnnynanjiang
I just pulled our latest main branch and run it locally with NETWORK_ID=testnet yarn start on YOURDIRECTORY/fast-auth-signer/packages/near-fast-auth-signer and I got:

It should still work. The account you have used above, have you created them with fast-auth first? if not, you should create via http://localhost:3000/create-account.

Thanks @hcho112
I think the UI is a bit confusing, I got signed in button in RED, then it turned BLUE after seconds.
There is no clear message saying everything is ok, somehow I assume this is the expected behaviour, is that correct?

@johnnynanjiang what you need to understand is that this repo has to be used in a specific way. Not just on it's own.
(Signed in button on red to blue was just there for quick UI check. In real world it is not being used. )
Check how it is being used on here
In terms of implementation, how it is being used is:
test.near.org (running on top of https://github.com/near/near-discovery) is using
setupFastAuthWallet from (https://github.com/near/near-fastauth-wallet)
which it points to testnet or mainnet
It may look overly complicated, but it is designed in a way that it naturally integrates with existing NEAR applications and multiple vendors.
Please take a look and let us know if you struggle to understand the flow. Meanwhile, if this issue of problem with yarn start on local environment is not an actual issue, will close the issue shortly

Thanks @hcho112 for giving me some context, it is helpful for me as a newcomer.
Yes I think it is not a real issue, just some confusion for me to try it out. I believe it would be much clearer overtime with help from community members like you, which is great.

@johnnynanjiang
Thank you for quick feedback and we actually feel sorry that you had to go through bad experience. We are well aware of lack of documentation around fast-auth repos and we are planning to improve them shortly. Thank you for being patient and please feel free to ask questions.


Lumen support

Added support for Lumen

thanks @lucacri! we've included example apps for the various versions of laravel we support - would you mind adding a lumen example app?

You are welcome ;-)
I created the example app, it should be ready for a merge

Great, thanks again!


Add support in LookupResources for caveats

Fixes #937
In this initial implementation, any caveated paths are treated the same way an intersection or exclusion are treated, and a followup check is issued (with the proper context). There are almost certainly improvements we can make in the future to do proper book keeping of the actual caveat expressions and therefore just run the caveat expression without a full check, but as there are plans to optimize the checks as well, it remains to be seen whether that will be desirable

Updated

The TestStableCacheKeys tests serializing request content are flaking. Unfortunately, Google deliberately added randomization to prevent users from relying on it as a stable output.

As discussed offline, I manually implemented sorting of keys and walking the struct directly


Kindly suggest: Move the "close diagram" button

Describe what problem your feature request solves
The close diagram button, a custom drawn "x" 2nd from the left in the edit pallet, is very difficult to discover as the "close diagram button". Normally this would be positioned all the way to the right (or maybe left on mac... but that's not an X). It is thicker than windows or XWindows style X's used for closing windows.
This so eluded our grasp that we thought we had to save and close the whole threat model file in order to access a different diagram... for more than 6 months until I tried clicking on the X.
I don't claim to be a UX expert or anything, but a smart team of 3 security engineers with a combined industry experience exceeding 70 years... could not figure it out. It's ok if you dont' fix this because we figured it out at this point. I know. RTFM.

Describe the solution you'd like
-Move the X all the way to the right
-Less delay on the fly-over help when the mouse is over the X
-Extra credit: Use the window close button and intercept the javascript; ask the user if he would like to close the diagram or the whole report. Then ask if they would like to SAVE first! :-)
Additional Context
LOL this drove us batty for months. But we finally did get it.

Hello @storkinsj - this is a very good suggestion, thanks for raising it. The Threat Dragon core repo is the best place for this issue, would yuo like to move it to there?
https://github.com/OWASP/threat-dragon-core/issues
If you can provide a solution as well then that would be great - otherwise it will get changed in version 2.0 which should be out sometime late this year. Anyhow, thanks again for the suggestion.

Threat Dragon version 2 is still in development, so the layout of the edit pallet may change before it's released.  That said, I think a good temporary solution is to simply highlight the main save/cancel actions by having the label next to the buttons as well:

Hi,
The layout seems much clearer; however, is it a "cancel" button... or the "close" button?
It is normal to make edits in one diagram and close it then go to the appropriate other diagram. I think the word "cancel" will keep people from pressing it. I think the undo button is more about cancelling what you have done.
 By the way this does seem to belong in core. Should we move it there?

Excellent points!  I'm also hoping to implement the "you have unsaved changes" reminder you mentioned as well. If we change it to say "close", do you think that is sufficient, or do you have another idea on how to make it a bit clearer?
I'm by no means a UI expert, so the feedback is extremely helpful!

Hello @storkinsj many thanks for the good feedback, which certainly makes sense.
We have also reworked the repositories for Threat Dragon, and now Threat Dragon core and webapp repos have been combined ... hence us moving your issue into this repo. The core repo should now probably be archived

A pull request has been made so that the buttons are shuffled around and a different image used for the return button for versions 1.x:

This issue will be kept open because the long term solution is being provided in version 2.0

Closing as this is complete in v2


Typo in Status Messenger Address placeholder

Typo in Status Messenger Address placeholder (should be messanger)

I don't believe this is a typo. Messenger seems to be the preferred spelling.
https://en.wiktionary.org/wiki/messenger


Build essentials on centos/redhat

Can you please add "sudo yum groupinstall 'Development Tools' as instructions to add support for event loop monitoring on centos/rhel?

Done via https://github.com/instana/nodejs-sensor/commit/fb75a8930285106b77fc789c29ce03f2cc4c8b53


Downloader functional tests

This change is

r1:
Change title to "downloader: Use only permitted chars for directory names".
Also the explanation could be improved, e.g.:
"Package names are used to create directories, which fails when they contain characters which are not allowed for directory names (e.g. "project :module_name").
Add a dynamic property normalizedName to the Package class that contains only characters which are valid for directory names, ..."
r2:
Change title to "Resolve #92: Add functional tests for downloader"
See: https://help.github.com/articles/closing-issues-using-keywords/
Also the tag is not new anymore.

Review status: 0 of 5 files reviewed at latest revision, 7 unresolved discussions.

downloader/src/funTest/kotlin/DirectoryTest.kt, line 40 at r2 (raw file):

gradle
Gradle

downloader/src/funTest/kotlin/DownloaderTest.kt, line 59 at r2 (raw file):

                    vcsProvider = "Git",
                    vcsUrl = "https://github.com/heremaps/oss-review-toolkit.git",
                    vcsRevision = "",

Please add a revision here.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 69 at r2 (raw file):

            workingDirectory.isValid() shouldBe true
            outputDirList.indexOf(submoduleName) should beGreaterThan(-1)
            outputDirList.indexOf("downloader") shouldBe -1

Please also check, that the created directory is a Git repository, and that the correct revision was cloned. Same for the tests below.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 97 at r2 (raw file):

        }.config(tags = setOf(Expensive))

        "Downloads single revision of package from git" {

This test can be merged with the one above if we check for the correct revision there.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 111 at r2 (raw file):

                    vcsProvider = "Git",
                    vcsUrl = "https://github.com/heremaps/oss-review-toolkit.git",
                    vcsRevision = "",

"revision" should be used here.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 136 at r2 (raw file):

                    vcsProvider = "Mercurial",
                    vcsUrl = "https://bitbucket.org/creaceed/mercurial-xcode-plugin",
                    vcsRevision = "",

"revision" should be used here.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 150 at r2 (raw file):

            = vcs.getWorkingDirectory(File(outputDir, "${pkg.normalizedName}/${pkg.version}"))

}

I would like to separate the tests for each VCS in a separate test class to improve overview, and to make sure that the same features are tested for each VCS. Check the proposal below, should be easy to adapt:
GitTest {
"Git should clone HEAD if no revision is provided"
"Git should clone correct revision" - with revision=sha1
"Git should clone correct branch" - with revision=some branch name
"Git should clone correct tag" - with revision=some tag name
And a test for the fallback:
"Git should guess correct tag" - when the provided revision is invalid but a tag can be guessed from the version
}

Comments from Reviewable

Review status: 0 of 5 files reviewed at latest revision, 8 unresolved discussions.

model/src/main/kotlin/Package.kt, line 141 at r1 (raw file):

    /**
     * The normalized package name, so it can be used as downloaded package directory.

The normalized package name.
@see normalizePackageName

Comments from Reviewable

Review status: 0 of 5 files reviewed at latest revision, 8 unresolved discussions.

model/src/main/kotlin/Package.kt, line 141 at r1 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
The normalized package name.
@see normalizePackageName

Overlooked that you already have the @see :)
Would maybe rephrase to "The normalized package name, can be used to create directories."

Comments from Reviewable

Reviewed 3 of 3 files at r1, 2 of 2 files at r2.
Review status: all files reviewed at latest revision, 8 unresolved discussions.

Comments from Reviewable

Done.

Review status: 2 of 5 files reviewed at latest revision, 8 unresolved discussions.

downloader/src/funTest/kotlin/DirectoryTest.kt, line 40 at r2 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…

gradle
Gradle

Done.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 59 at r2 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
Please add a revision here.

Done.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 69 at r2 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
Please also check, that the created directory is a Git repository, and that the correct revision was cloned. Same for the tests below.

workingDirectory.isValid() shouldBe true checks if directory is git repository, doesn't it?
Added check of revision.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 97 at r2 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
This test can be merged with the one above if we check for the correct revision there.

Done.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 111 at r2 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
"revision" should be used here.

Done. (Actually now it's used in testcase where sparse checkout is being checked, called now: "Downloads subpath of package at specified revision from git")

downloader/src/funTest/kotlin/DownloaderTest.kt, line 136 at r2 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
"revision" should be used here.

In this case revision should be determined for given version before projects is checked out from mercurial.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 150 at r2 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
I would like to separate the tests for each VCS in a separate test class to improve overview, and to make sure that the same features are tested for each VCS. Check the proposal below, should be easy to adapt:
GitTest {
"Git should clone HEAD if no revision is provided"
"Git should clone correct revision" - with revision=sha1
"Git should clone correct branch" - with revision=some branch name
"Git should clone correct tag" - with revision=some tag name
And a test for the fallback:
"Git should guess correct tag" - when the provided revision is invalid but a tag can be guessed from the version
}

I wasn't very happy  with how the tests are grouped, but didn't have a better idea.
We already have MercurialTest, but there, Mercurial is being called directly, instead of withMain.download(pkg, outputDir) like it is here.
I think we should either call Mercurial via Main class,  or call Git directly in here as well.
Then we should add some tests for Main.download(pkg, outputDir) to cover cases that are not covered by Git and Mercurial tests.
I like refactoring MercurialTest option better. What do you think?

model/src/main/kotlin/Package.kt, line 141 at r1 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
Overlooked that you already have the @see :)
Would maybe rephrase to "The normalized package name, can be used to create directories."

Done.

Comments from Reviewable

Can you please confirm that the expensive tests succeed, because they are not run in Travis CI? I would approve this PR then.

Reviewed 1 of 3 files at r3, 1 of 2 files at r4.
Review status: 4 of 5 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 69 at r2 (raw file):
Previously, pnowakowski wrote…
workingDirectory.isValid() shouldBe true checks if directory is git repository, doesn't it?
Added check of revision.

True.

downloader/src/funTest/kotlin/DownloaderTest.kt, line 150 at r2 (raw file):
Previously, pnowakowski wrote…
I wasn't very happy  with how the tests are grouped, but didn't have a better idea.
We already have MercurialTest, but there, Mercurial is being called directly, instead of withMain.download(pkg, outputDir) like it is here.
I think we should either call Mercurial via Main class,  or call Git directly in here as well.
Then we should add some tests for Main.download(pkg, outputDir) to cover cases that are not covered by Git and Mercurial tests.
I like refactoring MercurialTest option better. What do you think?

We could call tests that call Mercurial directly MercurialTest, and tests that call Main.download MercurialIntegrationTest. But now that I think about it I think we should call Mercurial directly in all Mercurial tests (same for Git), and have separate tests for Main.download which test its specific functionality. Most of it is in VersionControlSystem.forProvider which should also be tested separately (and already is partly).

Comments from Reviewable

Reviewed 1 of 2 files at r4, 4 of 4 files at r5.
Review status: 3 of 5 files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable


adapt startIPC so it can take any fromjson/tojson message pair

this PR moves the handler for the IPC into Cardano.Shell.NodeIPC.SimplePortServer along with the types for the protocol
and then adapts all related code to take a handler and generic FromJSON and ToJSON types, so that another program can just provide its own replacement of Cardano.Shell.NodeIPC.SimplePortServer and reuse the bulk of the logic
todo:

[ ] rebase once https://github.com/input-output-hk/cardano-shell/pull/186 is merged
[ ] clean up imports and stylish-haskell
[ ] replace stack exec node-ipc with $(stack path --local-install-root)/bin/node-ipc so the haskell mode with stdin/out isnt needed

@cleverca22 We will take a look at what to do on Monday and will respond with a comment/review then.

@cleverca22 We are going to use the existing implementation from the wallet-backend, the original code is going to remain the same. Closing.


Button displayed as "Unknown" in Snapshot Tests

What RMWC Version are you using [major.minor.patch]: 5.1.8

Name your build system [Webpack, Rollup...]: create-react-app-ts

Describe the bug with as much detail as possible:

Error while executing a test:
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){export default () => {
                                                                                ^^^^^^
    SyntaxError: Unexpected token export

Code:
import * as React from 'react';
import { configure, shallow } from 'enzyme';
import * as ReactSixteenAdapter from 'enzyme-adapter-react-16';
// @ts-ignore -> somehow no typescript typings were found for this
import rmwcTestPolyfill from '@rmwc/base/test-polyfill';
configure( {adapter: new ReactSixteenAdapter()} );

rmwcTestPolyfill();

The test fails on the line configure. If I don't include the call to rmwcTestPolyfill(); though, everything runs through. So I think this issue is with rmwc instead of enzyme.
If I don't include the polyfill I get Unknown objects in the snapshots though. I hoped that the polyfill would fix that as documented in the Getting started guide. Example:
<Unknown
          dense={true}
          onClick={[Function]}
          raised={true}
>
          Text
</Unknown>

What happened, and what was supposed to happen:

An error occured while executing my tests.
The test code should run through.

Thanks for reporting this. A few questions.
There is create-react-app-ts (the fork of 1.x) and CRA2 using typescript. Which one is this?
You definitely need the polyfill in certain situations where you are testing interactions because MDC uses some DOM apis not available in jsdom.
A minimal repro of this would be very helpful. It almost sounds like jest is expecting the polyfill you are importing to be ES5 and you’re getting ES6. I’m not exactly sure which module is being resolved in the example you posted. You might try @rmwc/base/dist/test-polyfill which will be a direct path to the ES5 code.
I personally am not experiencing this issue with CRA2 TS so I’ll be interested to see what the cause is!

I'm using create-react-app-ts. Haven't moved over to CRA2 yet because it misses some features so far.
I don't need to test such interactions. The reason why I tried to use the polyfill (didn't use it before the upgrade) is because I saw that in the Snapshots all "Button" Elements were replaced with "Unknown" Elements.
Do you have an idea why this happens?
If not I will try to create a minimal repro.

This could just be an issue with the displayName of the button. I can take a look at that.
Either way the other thing you’re encountering is also an issue, but rheee is no reason the polyfill should impact the display name of a component.

Ok thanks for looking into the snapshot naming issue.
For the issue about the polyfill I created a minimal reproduction for this error in this repository: https://github.com/maracuja-juice/rmwc-error-reproduction
I created the component MyButton and the test MyButton.test.
I also tried it out with your suggestion of using a different import. This ends in this error though:
Cannot find module '@rmwc/base/dist/test-polyfill' from 'MyButton.test.tsx'

Also while you're at it: could you look into it why no typings are found for that polyfill?

Were you able to confirm the behaviour?

I'm adding types to the polyfill for the next release, it was just a plain js file. There is nothing interesting about it, but having it as a .TS file will stop your IDE from complaining.

The Unknown component I'm still not sure about. Per the screenshot above, the displayName is being use properly. I still don't think the polyfill update will fix this issue, but you never know.
Release should be up by Monday. This one is taking a bit longer since MDC just converted over to Typescript which has had a major (positive) impact on RMWC.

This should be fixed in the 5.2.0-alpha.0. Please verify if you get a chance.

By "this" you mean the Unknow button?
I'll try it out.

In the alpha, your non-typed "export" error from the polyfill should be fixed.
I'm still not aware of what would be causing the Unknown Button Issue. If the polyfill fixes it, great. If not we'll have to see how we can get a repro.

My repository reproduces this error though. Couldn't you reproduce it?

No, I cannot reproduce it. Please add a repro case in the code sandbox, or in a publicly accessible repository. At the very least, paste a more comprehensive example.

 I can link to it again:
https://github.com/maracuja-juice/rmwc-error-reproduction

I missed that before, thanks! Will check it out.

Just double checked this against rmwc@next and it is working correctly now

You have to use import rmwcTestPolyfill from '@rmwc/base/dist/test-polyfill';
I updated this in the docs now
The snapshot test is passing as well
Cutting an official release shortly

What do you mean by passing? Is the Button in your snapshot written as "Button" or "Unknown" ?

I cloned the repo
Ran npm i
Ran npm i rmwc@next --save
Updated the polyfill import path as mentioned above
Ran npm test

Tests pass green. Did I miss something?

If the snapshot display issue was fixed, the test should actually go red because in the initially generated snapshot from the thest, the Button is defined as "Unknown".
I renamed the issue to reflect better what my actual issue is and suggest to reopen it. (I found the other problem while searching for the solution to the "Unknown" button issue.)

Sorry for all the confusion, and thank you for clarifying. Could you hit me up on discord so we can have a quick back and forth on this?

I have a discord account but not sure how to contact you there. Can't find any references to a discord in the readme.md and contributing.md.

Which is precisely why this now exists :)
https://jamesmfriedman.github.io/rmwc/resources

Dug as deeply as I could into this issue. Seems to be related to issues with Enzyme when using React.Portal not properly using the displayName, or the name of the function as documented in the React Docs. I'm going to leave this open for reference, but I would definitely suggest opening up an issue with the Enzyme team.

As an update:
With Jest 24 it is required to use a custom serializer for this Enzyme testing so we switched over to enzyme-to-json which proved to have the following advantages:
1: The Snapshots are a lot clearer!
2: This issue is gone.

Woot woot! Great to hear.


[Fix #10174] Fix inherit_from_remote should follow remote includes path starting with ./

Fixes #10174.
This PR is fix inherit_from_remote should follow remote includes path starting with ./
In the example of issue, it tries to load ./base.yml in the same hierarchy as ruby-2.7.yml, but the uri of ./base.yml is
https://raw.githubusercontent.com/testdouble/standard/main/config/./base.yml.
If the uri is https:// ~ /./base.yml,  ConfigLoaderResolver#remote_file? returns false, so an instance of URI::Generic is created and an error occurs.
In this PR, if remote includes path starts with ./, it will be removed.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Can you please add tests for this change?

Thanks!


403 simple oauth provider

#403. Ready for a bit of review. This is a simple docker file to run an example OIDC provider from pyoidc. You can start it (alongside the gh4gs server) using 'docker-compose up'.
Now looking more at adding RP capability to the main server.

This looks good @jbu, thanks. I wonder if we really need Docker for this though. If I'm interpreting things correctly, we're running a provider using the example code from PyOIDC, which we could just bake into a script that we run locally (say, scripts/oauth_provider.py). To me this would be more straightforward and transparent than pushing this logic into a Docker image, and it would make it easier to work with the files it depends on.
However, it's entirely possible I'm not understanding this very well, so I'm not closed to the idea to using Docker for this.

I agree with @jeromekelleher.  It makes sense to add Docker-related stuff to our codebase for packaging functionality to deploy so other people can use our code without having to perform excessive configuration.  But it seems like it's breaking the pure-python simplicity of our codebase to introduce docker into other areas.  It makes sense to hook any auth things into the existing code more closely: we're going to want to run tests with this, etc.
Looking back on the old OAuth issue here https://github.com/ga4gh/server/issues/31 it seems like basically the only point that was decided upon was to use OAuth 2.  I'd like to have a better idea of what our use cases are before I'm ready to incorporate any oauth code into the repo.

I'll have a look at doing this without docker. @dcolligan, the direction of the discussion yesterday is that using OIDC would allow us to make the first steps without precluding more difficult use cases in the future. The uses cases I'm aware of are a straight-forward RP-OP authorisation flow, and a federated system where a central 'client' server has static authorisation with a set of ga4gh servers (which might just as well be handled by tls client certs).

I've removed docker, but have still used virtualenv to help keep the requirements for this server isloated. The ./run.sh script sets everything up and runs the server.

Excellent, thanks @jbu. This looks a lot easier to work with to me, and it worked fine on my system once I added the bit above. I it would be good to add a quick README explaining what this directory is, where the code came from, and how we can run it.
After that, I'm +1. Once we're all happy with the PR and it's ready to be merged, we'll ask you to rebase the PR against the current state of the 'develop' branch and squash the commits.
@bartgrantham and @knoxcarey, would you like to weigh in here?
@dcolligan, @jbu and others are working on adding OAuth support to the server. This is a critical feature for people with non-public data (which is almost everyone), so that they can selectively share their data. We're coordinating with members of the security working group (@bartgrantham and @knoxcarey) to make sure that what we're doing here conforms to their recommendations.

Thanks for the update @jbu, +1.

commits need to be squashed

Commits have been squashed. I'll leave it to others ( @jeromekelleher ?) to merge.

Thanks @jbu. The convention here is that no-one merges their own code, and in practice either me, @dcolligan or @macieksmuga do the merging. Let's see if @dcolligan is happy with this being merged, and go from  there.

+1

Merged: thanks @jbu!


Moving on from Katacoda

As the katacoda.com has shut down from 15th of June, and our scenario is no longer available we have to look up for other alternatives outside to keep this contributor-katacoda running.
Here are few of the alternatives to look after:

https://killercoda.com/, also some discussions regarding this has been mentioned here: https://github.com/kubernetes/website/issues/33918#issuecomment-1144786114
https://instruqt.com/, this suggestion came as a discussion here: https://github.com/kubernetes/website/issues/33918#issuecomment-1136372030

/label help-wanted
/label contributor-comms

Blasted things

/help

Interesting
According to the source of truth: https://github.com/kubernetes/test-infra/blob/master/label_sync/labels.yaml, the contributor-comms labels is only enabled on a select few repos. We'll need to add an entry for this repo in labels.yaml if we want to use that label here.

Hello Folks, I have recently migrated Katacoda(Thanos) to Killercoda(Thanos) if you want any help I am happy to help you out 🙂

Hi @Akshit42-hue thanks for your interest, could you please try and make a POC for the scenario-setup-linux katacoda in Killercoda so that it could give us an idea on how things work on Killercoda because at the moment we are also considering using GitHub codespace.

Yes @Debanitrkl, will be creating a Killercoda scenario and sharing the link with you ASAP

I'd be thrilled to help get this going with GitHub Codespaces - I am a Codespaces product manager. Are the scenarios that were on https://katacoda.com/k8scontributors archived anywhere?

I'd be thrilled to help get this going with GitHub Codespaces - I am a Codespaces product manager. Are the scenarios that were on https://katacoda.com/k8scontributors archived anywhere?

No the oriely platform isn't available now so it couldn't be archived.

Hey @Debanitrkl, here is the link for Killercoda. Sorry for the delay


Update for i386 missing

Hi there!
Am trying to update Home Assistant on my netbook but it's having issues updating the core DNS addon. Can you help? Am updating from 2020.12.1 to 2021.1.0 and installed using generic x86 installer. Thanks!
21-01-12 20:08:53 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install homeassistant/i386-hassio-dns:None -> 404 Client Error: Not Found ("manifest for homeassistant/i386-hassio-dns:None not found: manifest unknown: manifest unknown").
21-01-12 20:08:53 ERROR (MainThread) [supervisor.plugins.dns] CoreDNS update fails
21-01-12 20:08:53 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<Tasks._update_dns() done, defined at /usr/src/supervisor/supervisor/misc/tasks.py:238> exception=CoreDNSUpdateError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/misc/tasks.py", line 244, in _update_dns
    await self.sys_plugins.dns.update()
  File "/usr/src/supervisor/supervisor/plugins/dns.py", line 210, in update
    raise CoreDNSUpdateError() from None
supervisor.exceptions.CoreDNSUpdateError

Try this.
ha su reload
ha su repair
ha dns update

Try this.
ha su reload
ha su repair
ha dns update

Thanks for this, @ludeeus. Fixed this by clearing space in the end. Still having issues with updating supervisor so will give those steps a whirl.
See https://github.com/home-assistant/supervisor/issues/2410

Thanks for this, @ludeeus. Fixed this by clearing space in the end. Still having issues with updating supervisor so will give those steps a whirl.
See https://github.com/home-assistant/supervisor/issues/2410

That is something else, closing this issue and will have a look at the other one :+1:

That is something else, closing this issue and will have a look at the other one :+1:


Update the sawtooth publisher and remove deprecated mqtt_client crate

Proposed changes

Move the sawtooth publisher in crates/tests.
Update the publisher to use the new mqtt_channel crate.
Remove the mqtt_client crate.

WARNING after this change, to run system tests, you will have to change the EXAMPLEDIR environment variable to point to the target/debug or target/release directory, as the sawtooth publisher is no more an example but a plain binary crate.
Types of changes
What types of changes does your code introduce to thin-edge.io?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

https://github.com/thin-edge/thin-edge.io/issues/777

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

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

No concerns, looks good for me. We still need to update the workflows to use the new publisher


IOS - FaceID Check always return "unavailable"

Bug report
Summary
Checking FaceID permission (PERMISSIONS.IOS.FACE_ID) always return false.
On all cases:

Fresh Install of the app.
After Disabling the permission from system settings.
After Enabling the permission from system settings.

Environment info
react-native: 0.63.2
react-native-permissions: 2.1.5
iOS: 13.3.1
xCode: 11.6
iPhoneX: MQAD2AH/A
react-native info output:
# System:
    OS: macOS 10.15.4
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    Memory: 51.33 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.6.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.7 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.8.4 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 21, 26, 28, 29
      Build Tools: 28.0.3, 29.0.1, 29.0.3
      System Images: android-26 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_241 - /Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/bin/javac
    Python: 2.7.15 - /usr/local/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2
  npmGlobalPackages:
    *react-native*: Not Foundpaste it here

Library version: 2.1.5
Steps to reproduce

Create a react-native project
install react-native-permissions 2.1.5
cd ios && pod install
Create a simple button, and inPress: check(PERMISSIONS.IOS.FACE_ID)
'check' will return RESULTS. UNAVAILABLE

Describe what you expected to happen:
'check' should return RESULTS.DENIED on a fresh install
Reproducible sample code
I couldn't provide a sample code at the moment.

Could you provide your Podfile?

I'm facing the same issue with the following:
->PERMISSIONS.IOS.PHOTO_LIBRARY
->PERMISSIONS.IOS.MOTION
->PERMISSIONS.IOS.LOCATION_ALWAYS
->PERMISSIONS.IOS.LOCATION_WHEN_IN_USE
Alsway UNAVAILABLE

Hi @DaniShalash
Have you tried to remove the "derived data" for your application in ~/Library/Developer/Xcode/DerivedData?

I have same issue

I have the same issue

Well, upgrade to version 3 and clear the build folder in xcode, fix the problem for me

Still have same issue here, always getting unavailable using version 3.6.1 of react-native-permissions on iOS 16.0.2 when using request(PERMISSIONS.IOS.FACE_ID). Although if we use other solutions like react-native-biometricsor expo-local-authentication it prompts correctly for FaceId permission. We have as well NSFaceIDUsageDescription correctly defined in Info.plist.

still always return unavailable, on version "react-native-permissions": "^3.4.0", and ios 16.1.1 Iphone 12 Pro how come it's closed

For version 3.8.4, you may be using "reactNativePermissionsIOS" in the package.json file instead of the Podfile changes. Please check that "FaceID", like so:
{
  "dependencies": { /* ... */ }
  "reactNativePermissionsIOS": [
    /* ... */
    "FaceID"
  ],
}

Then:

Run react-native setup-ios-permissions or npx react-native setup-ios-permissions
Delete your derived data (~/Library/Developer/Xcode/DerivedData) or use Xcode's "Clean Build Folder" (Shift+CMD+K)
Re-build


openssl.cnf not generated during an installation from source

Hello,
I used this script to install locally openssl to $HOME/.local/openssl on a Ubuntu 16.04 machine. After that, I run the following command to check the installation:
openssl req -x509 -newkey rsa:2048 -keyout delete_me.pem -out delete_me_cert.pem -days 3653
and got this error message:
Can't open /home/username/.local/openssl/openssl.cnf for reading, No such file or directory
I check /home/username/.local/openssl/ and indeed the file is not there. I checked another machine of mine where I used the same script to install openssl, the file is there.
Could you please help me to find out what's wrong?
Thank you in advance for your help!

Do you have a log of the output from your installation script? Probably something went wrong during that process.

Marking as inactive to be closed at the end of 3.4 dev, barring further input


Change the tutorials and docs to amoy testnet

with the migration of the polygon testnet, mumbai chain will be deprecated. So we plan to move the docs and tutorial to Amoy testnet.
https://polygon.technology/blog/introducing-the-amoy-testnet-for-polygon-pos

So we plan to move the docs and tutorial to sepolia testnet.

You mean Amoy testnet?

yes, changed

@B-Venkatesh7210 can we mark this closed?


fix: allow GPBayesianOptimization to set batch_size argument

Description of changes: allow to change the batch_size argument in GPBayesianOptimization

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi,
I prefer this interface of external objective function evaluation. But I found it doesn't support batch_size. So what I have done is to modify the class and pass this information to the base class.


Is it only restricted to the default data or should it work on other datasets. Because I have tried it but doesn't work on other datasets other than restaurant dataset.

You can use it for any dataframe.
Just restart your kernel and pass different dataframe.

I am closing this issue.


This table is failing on geocoding and I suspect is due to the first two rows

[from jira: https://cartodb.atlassian.net/browse/CDB-3905]
Imported without those 2 rows is working perfectly. This is the table - https://team.cartodb.com/u/saleiva/tables/marias.copy_20of_20location_20listing_208132004_20age

Lost debugging information, closing this


Cannot set property 'outlineProperties' of null (v3.8.2)

This issue is closed https://github.com/exceljs/exceljs/issues/655, but that bug is still exists:
TypeError: Cannot set property 'outlineProperties' of null
    at WorkSheetXform.parseClose (E:\test\parser\node_modules\exceljs\lib\xlsx\xform\sheet\worksheet-xform.js:388:40)
    at saxStream.sax.on.node (E:\test\parser\node_modules\exceljs\lib\xlsx\xform\base-xform.js:91:21)
    at SaxesParser.closeTag (E:\test\parser\node_modules\saxes\saxes.js:2012:65)
    at SaxesParser.sCloseTag (E:\test\parser\node_modules\saxes\saxes.js:1601:18)
    at SaxesParser.write (E:\test\parser\node_modules\saxes\saxes.js:483:36)
    at SAXStream._write (E:\test\parser\node_modules\exceljs\lib\utils\sax-stream.js:11:14)
    at doWrite (_stream_writable.js:415:12)
    at writeOrBuffer (_stream_writable.js:399:5)
    at SAXStream.Writable.write (_stream_writable.js:299:11)
    at resolve (E:\test\parser\node_modules\exceljs\lib\utils\stream-buf.js:205:14)
    at new Promise (<anonymous>)
    at write (E:\test\parser\node_modules\exceljs\lib\utils\stream-buf.js:204:14)
    at Array.map (<anonymous>)
    at StreamBuf._pipe (E:\test\parser\node_modules\exceljs\lib\utils\stream-buf.js:210:34)
    at StreamBuf._flush (E:\test\parser\node_modules\exceljs\lib\utils\stream-buf.js:275:14)
    at writeComplete (E:\test\parser\node_modules\exceljs\lib\utils\stream-buf.js:288:14)

v3.8.2

@tpkn It seems to be a typo according to the code below! To let us better determine the cause of the problem, would you mind providing your file? I will submit a PR as soon as possible.
if (this.map.sheetPr.model && this.map.sheetPr.model.outlineProperties) {
     // outlinePropertiesx
     properties.outlineProperties = this.map.sheetPr.model.outlinePropertiesx;
}

@Alanscut sure, here's my test file
test.xlsx

@tpkn Please tell me the version of excel software you are using, because I found that the structure of the xml file in text.xlsx is very different from my newly created file, I can’t know if it needs to be compatible.
For example

The target  attribute of text.xlsx is an absolute path and the other is a relative path.

//  workbook.xml
<Relationship Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/worksheet" Target="/xl/worksheets/sheet1.xml" Id="rId6" />

<Relationship Id="rId1" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/worksheet" Target="worksheets/sheet1.xml" />

The **sheet1.xml ** in the newly created file should have the sheetFormatPr tag and default attributes, but the test.xlsx file does not have.

// sheet1.xml
 <sheetFormatPr defaultRowHeight="13.5" x14ac:dyDescent="0.15" />

@Alanscut the whole engine that creates that xlsx files is a black box.
Is it possible to inject sheetFormatPr node with manually setted attributes?

@tpkn See https://github.com/exceljs/exceljs/blob/master/README.md#worksheet-properties.
const Excel = require('../../lib/exceljs.nodejs');

const workbook = new Excel.Workbook();
workbook.xlsx.readFile('./test.xlsx').then(function () {
  const worksheet = workbook.getWorksheet(1);
 // setting
  worksheet.properties.defaultRowHeight = 15;
  workbook.xlsx.writeFile('./target.xml').then(() => {
    console.log('ok_write')
  });
});

@Alanscut example crashes with the same error.

@tpkn  The error is caused because there is no sheetFormatPr tag, but there are other errors. I will come up with my solution and then need to ask the authors and members of excel.js for suggestions.
@Siemienik @guyonroche any thoughts?
Problems and solutions

The target attribute of workbook.xml.rels is an absolute path issue.

Solutions

// workbook.xml
// worksheet = model.worksheetHash[`xl/${rel.Target}`];
worksheet = model.worksheetHash[`xl/${rel.Target.replace(/^(\s|\/xl\/)+/, '')}`];

The sheet1.xml in the newly created file should have the sheetFormatPr tag and default attribute.

Solutions

// worksheet.-xform.js
// const properties = this.map.sheetFormatPr.model;
const properties = this.map.sheetFormatPr.model || {};
if (this.map.sheetPr.model && this.map.sheetPr.model.outlineProperties) {
   properties.outlineProperties = this.map.sheetPr.model.outlineProperties;
}

// sheet-format-properties-xform.js
 const attributes = {
    // defaultRowHeight: model.defaultRowHeight
    // outlineLevelRow: model.outlineLevelRow,
    // outlineLevelCol: model.outlineLevelCol,
    // 'x14ac:dyDescent': model.dyDescent,
    defaultRowHeight: model.defaultRowHeight || 15,
    outlineLevelRow: model.outlineLevelRow || 0,
    outlineLevelCol: model.outlineLevelCol || 0,
    'x14ac:dyDescent': model.dyDescent || 55,
};

Error messag: Deleted record: Document subject (workbook) in **xl / workbook.xml** section.

Solutions

// workbook-properties-xform.js
 render(xmlStream, model) {
    xmlStream.leafNode('workbookPr', {
      date1904: model.date1904 ? 1 : undefined,
      // defaultThemeVersion: 164011,
      defaultThemeVersion: 124226,
      filterPrivacy: 1,
   });
}


build-odata-apis-with-rest-best-practices

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: build-odata-apis-with-rest-best-practices
Document link: build-odata-apis.md
My Issue/Suggestion
The problem is this part:
The microflow uses a Java action to translate the OData query to an OQL expression using the OQL Dataset as the base query. This ensures that filtering, sorting, and paging work as expected.
Because where do I find this Java action? I have downloaded the OQL module as I was expecting it there. There is an Execute OQL Statement there but it differs from the example because I have the Amount and Offset and Preserve paramaters options in that action. So state where this Java action can be found and if it is the one in the OQL module then you should update the screenshots.
Regards,
Ronald

@RCatersels  Thank you for flagging this. Additional information has been added in this PR to clarify the issue.


Reindex Does not Document the ResourceLogicalId behavior in the Search Guide

Describe the bug
Reindex Does not Document the ResourceLogicalId behavior in the Search Guide
Environment
Which version of IBM FHIR Server?
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

Doc update, it's on thes ite


Consider removing build step for examples and have dev-server serve the browser builds.

Use budo to do the magic

Need the build step to include aframe still.


use new version and show more log

change mermaid version to 8.13.4
set mermai logLevel to warn, will show mermaid syntax error info in console

Thank you!

Version 0.1.11 released


Fix streams merge issues + merge latest kafka/3.0 to confluent/3.0

Fixes the merge issues from this job https://jenkins.confluent.io/job/apache-kafka-test/job/3.0/142/
Fixes https://confluentinc.atlassian.net/browse/KSE-612
The merge issue was caused by https://github.com/confluentinc/kafka/commit/5af411734c4654428e68c340880a14f6d2156af7
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

We cannot merge this until 7.0.0 is released.

Will close this now the AK sync job is green.


MTSJ should only use spring-data based on devon4j-jpa-spring-data

Category: enhancement
Severity: High
Description : MTSJ is currently using JPA based on oasp4j 2.4.0, as per the oasp4j release 3.0.0 it should be updated to spring-data
Also MTSJ should Update to spring boot 2
Your environment - windows/Linux, Devonfw version , component

Solved with PR #135


Update README with example for multiple forwarded ports

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@SathyaBhat

Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.


Setting the fader volume doesn't work on QU-16

On a Qu-16, I could easily mute and unmute a channel or an aux. But when I'm trying to set the volume fader of any input or an aux, it doesn't work.
Also, it would be great to have a option to increase/decrease the volume from 1 dB, instead of having to choose at which level you have to set it up.

In this module will be remove any referring to QU16 because will be build a specific module for all QU models.
Architecture of iLive is similar but not the same of the QU so it's preferable separate it.

In this module will be remove any referring to QU16 because will be build a specific module for all QU models.

Ok, thank you for your answer. Do you already know when the QU module will be available?
Meanwhile, is there a way to trigger the sending of TCP packets with companion? This would enable us to "build" some commands ourselves. Allen&Heath explains how to do so here, but it is with the native app of Elgato stream deck. Is there a way to do the same with Bitfocus Companion?

Now I'm working on it and is in a good point. I think in the next few days I release first version.
Answering your second question, there are generic modules for send packet, one is "Generic TCP-UDP", but I don't know if it's works in this case so you will have to try.

That's great news!
Thanks to all the team for your great work, it is really appreciated!


added missed info about rt and test artifacts

@kaishh check this out

LGTM

@kaishh check this out

LGTM


Workflow Step deployed in a Serverless environment executes multiple times

Description
I wish to post custom weekly reports with data collected from 3rd party APIs in our organization's Slack channels. My approach is to develop a custom Workflow Step which can be used in a Workflow Builder with various triggers in front of it. I have been using Bolt JavaSscript SDK for development. I have completed early development in Socket Mode, which worked perfectly, but switching to Serverless environment for deployment as described in Slack documentation resulted in repeated invocations of the execute function of the WorkflowStep. Multiple invocations are triggered by multiple API calls from Slack's Events API (can be seen via ngrok and serverless logs).
I wasn't able to find any guidelines / revised documentation regarding WorkflowStep deployments in Serverless environments so tagging this as a bug.
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: 3.7.0
node version: 14.18.0
OS version(s): Windows 10 / AWS Lambda node 14.x runtime
Steps to reproduce:

Create Slack App using Bolt JS SDK; Full app code:

const { App, AwsLambdaReceiver, LogLevel, WorkflowStep } = require('@slack/bolt');

const awsLambdaReceiver = new AwsLambdaReceiver({
  signingSecret: process.env.SLACK_SIGNING_SECRET,
});

const app = new App({
  token: process.env.SLACK_BOT_TOKEN,
  receiver: awsLambdaReceiver,
  processBeforeResponse: true,
  logLevel: LogLevel.DEBUG
});

var step = new WorkflowStep('post_weekly_report', {
  edit: async ({ ack, step, configure }) => {
    await ack();
    let blocks = [
      {
        "type": "section",
        "block_id": "select_channel",
        "text": {
          "type": "mrkdwn",
          "text": "Pick a channel from the dropdown list"
        },
        "accessory": {
          "action_id": "select_channel",
          "type": "channels_select",
          "placeholder": {
            "type": "plain_text",
            "text": "Select an item"
          }
        }
      }
    ]

    await configure({ blocks });
  },
  save: async ({ ack, update, view }) => {
    await ack();
    const { values } = view.state;
    const selected_channel = values.select_channel.select_channel.selected_channel;
    const inputs = {
      selected_channel: { value: selected_channel }
    };

    await update({ inputs, outputs: [] });
  },
  execute: async ({ step, client, complete, fail }) => {
    try {
      const { inputs } = step;
      let channel = inputs.selected_channel.value;
      await client.chat.postMessage({
        channel,
        blocks: [{
          "type": "section",
          "text": {
              "type": "mrkdwn",
              "text": "Hello!"
          }
        }],
        text: 'Hello!'
      });
      await complete({ outputs: {} })
    } catch (err) {
      await fail({ error: { message: "Error posting" }})
    }
  }
});

app.step(step);

module.exports.handler = async (event, context, callback) => {
  const handler = await awsLambdaReceiver.start();
  return handler(event, context, callback);
}

Deploy locally using npx serverless offline --noPrependStageInUrl and ngrok http 3000 or in AWS Lambda env.
Configure URLs in Slack App console.
Setup 2-step workflow, e.g. Shortcut (or any other) + Post Weekly Report step from the app above.
Trigger via shortcuts in a channel.

Expected result:
Message "Hello!" posted once per invocation.
Actual result:
Message "Hello!" posted multiple times within few minute interval (not immediately).
Few 'trigger_exchanged' errors logged in a console

Hello @dsedleckas
Can you describe how you set up your app URLs (step 2 in your repro steps)? That will be helpful to reproduce your configuration.
Thanks

Actually, I suppose that last error I can ignore (though it does seem like an odd experience) - onwards I go to try to reproduce the issue!

OK, confirmed, I can reproduce the issue when running locally with npx serverless offline + ngrok. Here is what the application logs look like:
offline: POST /slack/events (λ: slack)
[DEBUG]  web-api:WebClient:0 initialized
[DEBUG]  web-api:WebClient:0 apiCall('auth.test') start
[DEBUG]  web-api:WebClient:0 will perform http request
[DEBUG]  web-api:WebClient:0 http response received
[DEBUG]  web-api:WebClient:1 initialized
[DEBUG]  bolt-app No conversation ID for incoming event
workflow.execute <------- my own logging of the execute function
[DEBUG]  web-api:WebClient:1 apiCall('chat.postMessage') start
[DEBUG]  web-api:WebClient:1 will perform http request
[DEBUG]  web-api:WebClient:1 http response received
[DEBUG]  web-api:WebClient:1 apiCall('workflows.stepCompleted') start
[DEBUG]  web-api:WebClient:1 will perform http request

offline: POST /slack/events (λ: slack)
[DEBUG]  web-api:WebClient:0 initialized
[DEBUG]  web-api:WebClient:0 apiCall('auth.test') start
[DEBUG]  web-api:WebClient:0 will perform http request
[DEBUG]  web-api:WebClient:0 http response received
[DEBUG]  web-api:WebClient:1 initialized
offline: (λ: slack) RequestId: ckuyb2m92000qq0m0cwfm7c0c  Duration:
151.00 ms  Billed Duration: 152 ms

offline: POST /slack/events (λ: slack)
[DEBUG]  web-api:WebClient:0 initialized
[DEBUG]  web-api:WebClient:0 apiCall('auth.test') start
[DEBUG]  web-api:WebClient:0 will perform http request
[DEBUG]  web-api:WebClient:0 http response received
[DEBUG]  web-api:WebClient:1 initialized
[DEBUG]  bolt-app No conversation ID for incoming event
workflow.execute <------- my own logging of the execute function
[DEBUG]  web-api:WebClient:1 apiCall('chat.postMessage') start
[DEBUG]  web-api:WebClient:1 will perform http request
[DEBUG]  web-api:WebClient:1 http response received
offline: (λ: slack) RequestId: ckuyb2ljt000nq0m0c6kf2sjw  Duration:
3483.16 ms  Billed Duration: 3484 ms
[DEBUG]  web-api:WebClient:1 http response received
[DEBUG]  web-api:WebClient:1 apiCall('workflows.stepCompleted') start
[DEBUG]  web-api:WebClient:1 will perform http request
[DEBUG]  web-api:WebClient:1 http response received
[DEBUG]  web-api:WebClient:1 apiCall('workflows.stepFailed') start
[DEBUG]  web-api:WebClient:1 will perform http request
[DEBUG]  web-api:WebClient:1 http response received
[ERROR]  bolt-app Error: An API error occurred: trigger_exchanged
    at Object.platformErrorFromResult
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@slack/web-api/dist/errors.js:51:33)
    at WebClient.apiCall
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@slack/web-api/dist/WebClient.js:158:28)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async execute (/Users/filmaj/src/slack-bolt-serverless/app.js:70:7)
    at async processStepMiddleware
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@slack/bolt/dist/WorkflowStep.js:98:9)
    at async Array.<anonymous>
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@slack/bolt/dist/conversation-store.js:70:9)
    at async Array.<anonymous>
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@slack/bolt/dist/middleware/builtin.js:284:9)
    at async App.processEvent
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@slack/bolt/dist/App.js:533:13)
    at async /Users/filmaj/src/slack-bolt-serverless/node_modules/@slack/bolt/dist/receivers/AwsLambdaReceiver.js:106:17
    at async InProcessRunner.run
(/Users/filmaj/src/slack-bolt-serverless/node_modules/serverless-offline/dist/lambda/handler-runner/in-process-runner/InProcessRunner.js:213:24)
    at async LambdaFunction.runHandler
(/Users/filmaj/src/slack-bolt-serverless/node_modules/serverless-offline/dist/lambda/LambdaFunction.js:355:20)
    at async hapiHandler
(/Users/filmaj/src/slack-bolt-serverless/node_modules/serverless-offline/dist/events/http/HttpServer.js:602:18)
    at async exports.Manager.execute
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
    at async Object.internals.handler
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@hapi/hapi/lib/handler.js:46:20)
    at async exports.execute
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@hapi/hapi/lib/handler.js:31:20)
    at async Request._lifecycle
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@hapi/hapi/lib/request.js:371:32)
    at async Request._execute
(/Users/filmaj/src/slack-bolt-serverless/node_modules/@hapi/hapi/lib/request.js:281:9)
{
  code: 'slack_webapi_platform_error',
  data: {
    ok: false,
    error: 'trigger_exchanged',
    response_metadata: { scopes: [Array], acceptedScopes: [Array] }
  }
}
[ERROR]   An unhandled error occurred while Bolt processed an event
offline: (λ: slack) RequestId: ckuyb2o2h000tq0m0gi7vhext  Duration:
476.26 ms  Billed Duration: 477 ms

Note the second request from the Slack API causes an error to be raised.
Alright, I will dig in and see if I can determine why this is happening.

I'm having trouble with assembling the workflow using the step defined in your app. After adding the workflow step to a new workflow, I see the edit function gets executed in the app, but then selecting a channel in the UI that the edit function returns causes some event to go unanswered, and I see in the app logs an error that there was no response within 3 seconds, and in the "Pick a channel from the dropdown list" workflow edit step UI I see a warning icon next to the workflow edit select input.
Is there perhaps some additional code related to handling the workflow edit step UI responses that is missing?
In the mean time I will review the workflow docs to see if I can figure out what is missing.

I have seen the same behavior as well, but it kind of went through anyway, so I left this information out to make my issue more clear; But yes, can confirm that I encounter the same behavior.

Hah, in fact, in my case, the workflow step executes four times: twice within a few seconds of each other, then a third time after about a minute, and a fourth time after about 5 minutes. I imagine this is due to failed requests being retried twice by the Slack API, since the second request errored out and returned an HTTP 500 response to the Slack backend.

Yes, I was seeing the same, more or less (I've never exactly timed when the messages are posted)! You succinctly explained what I meant by "Message "Hello!" posted multiple times within few minute interval (not immediately)." 😄

One more update here: I'm in the process of following up with someone from the Slack backend API team as I believe this is an issue that is deeper than just bolt-js or any API client libraries. Will keep you posted on what I hear, and thanks for your patience with us as we figure this out 🙏

I am using AWS + Lambda Functions. I used a similar approach that @filmaj mentioned. The difference is -- Function A is calling a state machine, which runs a series of functions.
Even though my Workflow + Custom Workflow Step + State Machines are working flawlessly, I notice that the Activity is showing "In Progress". Is this an expected behavior if I am not await complete?

My code is below:
const initStateMachine = async (event: any, context: any, callback: any) => {
  const ws = new WorkflowStep("inquiry", {
    edit: async ({ ack, step, configure }) => {
      await ack();
      await configure(editForm.init());
    },
    save: async ({ ack, step, update, view }) => {
      await ack();
      await update(saveForm.init(view.state.values));
    },
    execute: async ({ step, complete, fail, client }) => {
      const { priority, title, description, acceptanceCriteria } = step.inputs;
      const outputs: StepCompleteArguments["outputs"] = {
        priority: priority.value,
        title: title.value,
        description: description.value,
        acceptanceCriteria: acceptanceCriteria.value,
      };

      const startExecutionCommand = new StartExecutionCommand({
        stateMachineArn: process.env.STATE_MACHINE_ARN,
        input: JSON.stringify({
          title: title.value,
          description: description.value,
          acceptanceCriteria: acceptanceCriteria.value,
          priority: priority.value,
        }),
      });

      try {
        const response = await sfnClient.send(startExecutionCommand);
      } catch (error) {
        console.error("sfnClient.error", error);
      }

      /**
       * https://github.com/slackapi/bolt-js/issues/1156
       * @filmaj (2021/10/26) says to NOT await complete
       */
      complete({ outputs });
    },
  });

  app.step(ws);

  const receiver = await awsLambdaReceiver.start();
  return receiver(event, context, callback);
};


Fixing new_without_default

The positioning of the replacement seems to be off.
Trying https://github.com/killercup/rustfix/tree/6937912bb89da024f6da89a35b2308f31af7663d on https://github.com/bluejekyll/trust-dns/tree/26b44483b0151682a7d835ddbd6ff9261c0651b6
Info: you should consider adding a `Default` implementation for `rr::resource::Record`
      #[warn(new_without_default)] on by default
  --> src/rr/resource.rs:78:3-78:3
Suggestion - Replace:

    pub fn new() -> Record {

with:

    impl Default for rr::resource::Record {
          fn default() -> Self {
              Self::new()
          }
      }

based on:
{
  "message": "you should consider adding a `Default` implementation for `rr::resource::Record`, #[warn(new_without_default)] on by default",
  "code": null,
  "level": "warning",
  "spans": [
    {
      "file_name": "src/rr/resource.rs",
      "byte_start": 40920,
      "byte_end": 41185,
      "line_start": 78,
      "line_end": 87,
      "column_start": 3,
      "column_end": 4,
      "is_primary": true,
      "text": [
        {
          "text": "  pub fn new() -> Record {",
          "highlight_start": 3,
          "highlight_end": 27
        },
        {
          "text": "    Record {",
          "highlight_start": 1,
          "highlight_end": 13
        },
        {
          "text": "      // TODO: these really should all be Optionals, I was lazy.",
          "highlight_start": 1,
          "highlight_end": 65
        },
        {
          "text": "      name_labels: domain::Name::new(),",
          "highlight_start": 1,
          "highlight_end": 40
        },
        {
          "text": "      rr_type: RecordType::A,",
          "highlight_start": 1,
          "highlight_end": 30
        },
        {
          "text": "      dns_class: DNSClass::IN,",
          "highlight_start": 1,
          "highlight_end": 31
        },
        {
          "text": "      ttl: 0,",
          "highlight_start": 1,
          "highlight_end": 14
        },
        {
          "text": "      rdata: RData::NULL(NULL::new())",
          "highlight_start": 1,
          "highlight_end": 38
        },
        {
          "text": "    }",
          "highlight_start": 1,
          "highlight_end": 6
        },
        {
          "text": "  }",
          "highlight_start": 1,
          "highlight_end": 4
        }
      ],
      "label": null,
      "suggested_replacement": null,
      "expansion": null
    }
  ],
  "children": [
    {
      "message": "try this",
      "code": null,
      "level": "help",
      "spans": [
        {
          "file_name": "src/rr/resource.rs",
          "byte_start": 40920,
          "byte_end": 40920,
          "line_start": 78,
          "line_end": 78,
          "column_start": 3,
          "column_end": 3,
          "is_primary": true,
          "text": [
            {
              "text": "  pub fn new() -> Record {",
              "highlight_start": 3,
              "highlight_end": 3
            }
          ],
          "label": null,
          "suggested_replacement": "impl Default for rr::resource::Record {\n      fn default() -> Self {\n          Self::new()\n      }\n  }\n\n  ",
          "expansion": null
        }
      ],
      "children": [],
      "rendered": "  impl Default for rr::resource::Record {\n      fn default() -> Self {\n          Self::new()\n      }\n  }\n\n  pub fn new() -> Record {"
    },
    {
      "message": "for further information visit https://github.com/Manishearth/rust-clippy/wiki#new_without_default",
      "code": null,
      "level": "help",
      "spans": [],
      "children": [],
      "rendered": null
    }
  ],
  "rendered": null
}

does this:
@@ -75,6 +75,12 @@ impl Record {
   ///
   /// There are no optional elements in this object, defaults are an empty name, type A, class IN,
   /// ttl of 0 and the <IP_ADDRESS> ip address.
+  impl Default for rr::resource::Record {
+      fn default() -> Self {
+          Self::new()
+      }
+  }
+
   pub fn new() -> Record {
     Record {
       // TODO: these really should all be Optionals, I was lazy.

And this:
Info: you should consider deriving a `Default` implementation for `rr::domain::Name`
      #[warn(new_without_default_derive)] on by default
  --> src/rr/domain.rs:37:3-37:3
Suggestion - Replace:

    pub fn new() -> Self {

with:

    #[derive(Default)]

based on:
{
  "message": "you should consider deriving a `Default` implementation for `rr::domain::Name`, #[warn(new_without_default_derive)] on by default",
  "code": null,
  "level": "warning",
  "spans": [
    {
      "file_name": "src/rr/domain.rs",
      "byte_start": 95979,
      "byte_end": 96046,
      "line_start": 37,
      "line_end": 39,
      "column_start": 3,
      "column_end": 4,
      "is_primary": true,
      "text": [
        {
          "text": "  pub fn new() -> Self {",
          "highlight_start": 3,
          "highlight_end": 25
        },
        {
          "text": "    Name { labels: Rc::new(Vec::new()) }",
          "highlight_start": 1,
          "highlight_end": 41
        },
        {
          "text": "  }",
          "highlight_start": 1,
          "highlight_end": 4
        }
      ],
      "label": null,
      "suggested_replacement": null,
      "expansion": null
    }
  ],
  "children": [
    {
      "message": "try this",
      "code": null,
      "level": "help",
      "spans": [
        {
          "file_name": "src/rr/domain.rs",
          "byte_start": 95979,
          "byte_end": 95979,
          "line_start": 37,
          "line_end": 37,
          "column_start": 3,
          "column_end": 3,
          "is_primary": true,
          "text": [
            {
              "text": "  pub fn new() -> Self {",
              "highlight_start": 3,
              "highlight_end": 3
            }
          ],
          "label": null,
          "suggested_replacement": "#[derive(Default)]\n  ",
          "expansion": null
        }
      ],
      "children": [],
      "rendered": "  #[derive(Default)]\n  pub fn new() -> Self {"
    },
    {
      "message": "for further information visit https://github.com/Manishearth/rust-clippy/wiki#new_without_default_derive",
      "code": null,
      "level": "help",
      "spans": [],
      "children": [],
      "rendered": null
    }
  ],
  "rendered": null
}

does this:
@@ -34,6 +34,7 @@ pub struct Name {
 }

 impl Name {
+  #[derive(Default)]
   pub fn new() -> Self {
     Name { labels: Rc::new(Vec::new()) }
   }

cc @mcarton

Hum, clippy never sees regular comments (//) so they might be tricky to always handle properly. Doc comments (///) we see, I could fix that.
 I've been meaning to switch to a more diff-like output anyway.
Stupidity is good – 'cause that can be easily fixed! 😜

Am 11.07.2016 um 12:30 schrieb Martin Carton<EMAIL_ADDRESS>Hum, clippy never sees regular comments (//) so they might be tricky to always handle properly. Doc comments (///) we see, I could fix that.

Reply to this email directly, view it on GitHub, or mute the thread.


Workbooks stuck adding System.Numerics.Tensors nuget package

Steps to Reproduce

Add https://dotnet.myget.org/F/dotnet-corefxlab/api/v3/index.json NuGet feed (I did this in VS)
Create a workbook, Add NuGet package.  Select the above feed as the Package Source.
Search for "Tensor" and check "show pre-release"
Add System.Numerics.Tensors 01.0-preview2-180607-3

Expected Behavior
The package should be added successfully.
Actual Behavior
The UI just spins.  I let it go for over a minute, and finally canceled.
Environment
Xamarin Workbooks

Detail
Value

Version
1.4.0

Git Branch
master

Git Hash
b3f92f9

VSTS Definition
Workbooks & Inspector (Win)

System Info

Component
Value

Windows
Microsoft Windows NT 10.0.17134.0 (64-bit)

CPU Cores
8

Physical Memory
32 GB

VisualStudio.15.IntPreview Components

Component
Version

Visual Studio Enterprise 2017
15.8.0-pre.3.0+27804.1.d15.8

Log File

Yes, I am using a .NET Core workbook.
FWIW, I also tried it with

And the experience was the same.

Wow, just tried on Mac and lost count of my timing but that took forever. At least the UI did not hang. It was definitely a couple of minutes or so before it came in. This will make a great test case.

I let it run in the background while I did something else, and it appears to have completed and I can use the package now.
It would be great to investigate why it takes so long for a simple package and what we can do to make it better.


Install Ubuntu 16.04 does not work

Maybe the mirror has changed location for image and kernel.

PRs merged


Added authSource configuration to the "Start from Scratch" section for MongoDB.

Update 100-connect-your-database-typescript-mongodb.mdx
Added authSource configuration to the "Start from Scratch" section for MongoDB.
Reason for this update: The authSource option was not mentioned in the "Start from Scratch" section, which could be particularly crucial for new developers. Including this tip here can help address potential authentication issues for those setting up their environment from the beginning, whereas experienced developers might already be familiar with such details.
Reference: Issue

@Dev-Connections Kindly check if this is a valid change.

Not sure what the convention is to bring attention from Dev team for PR reviews, so hence I'm tagging 😅
@jharrell


Proposed Solution: buy an iPhone

Wow... great attitude.
uninstalled.

Hahaha ok bud 🤣


Update file version list after adding new version

When adding a new version of a Project File or Defined File, the list of file versions was not refreshing in the UI until after a page reload because we were relying on refetchQueries. But refetchQueries only refreshes "live" queries, meaning those currently being used in mounted components. Since the FileVersions component is not mounted when a new version is added, refetchQueries did not serve our purpose.
Instead, we now call the update method of all mutations that add new file versions. This creates an updateCachedVersions function that can be passed the Apollo cache instance provided by the update method, the new array of FileVersions, and the id of the file whose versions need to be updated. We also update all relevant mutations to use this function.

file.children.total isn't updated in cache which renders the dividers weird

🤦♀ Fixed


Iris 2.0 and 2.1 does not work with netcdf4=1.4.0

when installing iris via anaconda with the usual  conda install -c conda-forge iris this will automatically pick up iris=2.0 and now it will pick up netcdf4=1.4.0. Iris does not work with this latest version though:
In [1]: import iris
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-089b5db944e7> in <module>()
----> 1 import iris

~/anaconda3/lib/python3.6/site-packages/iris/__init__.py in <module>()
    111 import iris._constraints
    112 from iris._deprecation import IrisDeprecation, warn_deprecated
--> 113 import iris.fileformats
    114 import iris.io
    115

~/anaconda3/lib/python3.6/site-packages/iris/fileformats/__init__.py in <module>()
     27                                    UriProtocol, LeadingLine)
     28 from . import abf
---> 29 from . import um
     30 from . import name
     31 from . import netcdf

~/anaconda3/lib/python3.6/site-packages/iris/fileformats/um/__init__.py in <module>()
     29 from ._ff_replacement import um_to_pp, load_cubes, load_cubes_32bit_ieee
     30 from ._fast_load import structured_um_loading
---> 31 from ._fast_load_structured_fields import FieldCollation
     32 __all__ = ['um_to_pp', 'load_cubes', 'load_cubes_32bit_ieee',
     33            'structured_um_loading', 'FieldCollation']

~/anaconda3/lib/python3.6/site-packages/iris/fileformats/um/_fast_load_structured_fields.py in <module>()
     29 import itertools
     30
---> 31 from netCDF4 import netcdftime
     32 import numpy as np
     33

ImportError: cannot import name 'netcdftime'

reverting to netcdf4=1.3.1, it works fine.
@bjlittle are you Iris folk aware of this? I am assigning a coule guys @mattiarighi and @bouweandela just so we are aware of this when we go to iris 2.0 and this issue will not have been sorted :grin:

@valeriupredoi This seems to be purely an issue with iris. Maybe it would be better to open an issue on the github page of iris instead of on the esmvaltool page?

@bouweandela yep, agreed, man, I added the iris label, it's just for bookkeeping for us here just in case someone hits this issue and doesn't know how to fix it. I emailed @bjlittle about it as well, am sure the Iris guys are aware of it nonetheless :)

@valeriupredoi There has been a bit of necessary churn in iris for various reasons.
To cut a very long story short, we've now cut iris version 2.1, which unpins matplotlib to 2.2.2 and numpy to 1.14.3. This will work with the latest netcdf4 version 1.4.0 and pull in the new cftime package, which is a replacement for the netcdf4.netcdftime package which has been removed from netcdf4 version 1.4.0, see https://github.com/Unidata/netcdf4-python/blob/master/Changelog#L12.
If you're going to use iris version 2.0 then you must pin netcdf4 to be <1.4
We also renamed cf_units package to be cf-units, and the nc_time_axis package to be nc-time-axis, and bumped both of these up to new releases, which also now pull in the new cftime package.
HTH :smile:

@bjlittle thanks a bunch, man! Yes, we'll do that, once the switch from iris 1.13. So we'll go straight to 2.1 then. In factanything that uses nc-time-axis will not work unless the iris plot is changed or 2.1 is used, I had this issue on Friday with a diagnostic plotting and was quite bedazzled :grin:
I suggest keeping this issue and #404 open just as references for when we switch to 2.1. BTW 2.1 doesn't yet work with netcdf4=1.4

@valeriupredoi No worries.
Also, slightly confused about you saying that iris version 2.1 is not working with netcdf4 version 1.4.0.
According to travis-ci on our latest upstream/master branch of iris... all is working just fine.
Infact, we've just added a conda list --explict to our travis-ci logging, so that you can easily recreate the travis-ci conda environment locally, see here.
Perhaps you should compare and contrast the packages in our travis-ci conda environment with your local conda environment to see if there are any obvious differences...

hey @bjlittle have a looksee:
(esmvaltool_autoassess) [valeriu@jasmin-sci2 esmvaltool_autoassess]$ conda install -c conda-forge iris=2.1
Solving environment: done

# All requested packages already installed.

(esmvaltool_autoassess) [valeriu@jasmin-sci2 esmvaltool_autoassess]$ conda list netcdf4
# packages in environment at /home/users/valeriu/anaconda3/envs/esmvaltool_autoassess:
#
# Name                    Version                   Build  Channel
netcdf4                   1.3.1                    py36_3    conda-forge
(esmvaltool_autoassess) [valeriu@jasmin-sci2 esmvaltool_autoassess]$ conda install -c conda-forge netcdf4=1.4
Solving environment: done

## Package Plan ##

  environment location: /home/users/valeriu/anaconda3/envs/esmvaltool_autoassess

  added / updated specs:
    - netcdf4=1.4

The following packages will be REMOVED:

    iris:    2.1.0-py36_0 conda-forge

The following packages will be UPDATED:

    netcdf4: 1.3.1-py36_3 conda-forge --> 1.4.0-py36_0 conda-forge

Not pretty :grin:

@valeriupredoi Awesome, thanks.
We simply forgot to unpin netcdf4 in the conda-forge iris recipe ... I'm on that right now!
Cheers :wink:

whoopsy :grin:

Yeah, guess we're human after all :stuck_out_tongue:
See https://github.com/conda-forge/iris-feedstock/pull/36
Cheers @valeriupredoi

what, I thought iris is the precursor of Skynet :grinning: Cheeers @bjlittle

@valeriupredoi My PR just got merged, so the fix should be available shortly from conda-forge.

@valeriupredoi The fix is now available from conda-forge.
Let me know if this resolves your issue.

it do indeed:
iris version:  2.1.0
cf_units version:  2.0.1
netCDF4 version:  1.4.0

cheers @bjlittle and the other iris eggheads :grin:
To be absolutely nitpicky, it would be nice if you guys pinned netcdf4=1.3.1 for iris=2.0 so people don't get confusado, at the moment with netcdf4=1.4 it will revert to iris 2.0 but not to netcdf4=1.3.1:
(esmvaltool_autoassess) [valeriu@jasmin-sci2 ~]$ conda install -c conda-forge iris=2.0
Solving environment: done

## Package Plan ##

  environment location: /home/users/valeriu/anaconda3/envs/esmvaltool_autoassess

  added / updated specs:
    - iris=2.0

The following packages will be DOWNGRADED:

    iris: 2.1.0-py36_1 conda-forge --> 2.0.0-py36_1 conda-forge

Proceed ([y]/n)? y

am gunna close this, @bjlittle and the iris gang, great job, but pls bear in mind the last comment above :)
point to us -- go straight to iris 2.1+ when switching from 1.13


chore: update the file headers to SPDX style

update the file headers to SPDX style
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM, can also add ltag to Makefile / CI for automatic checking of the header being present: https://github.com/kunalkushwaha/ltag

@ginglis13 Yeah. Let me track and explore this later in a separated PR.


Breakpoints not working in debugging a vscode extension

VSCode Version: Code 1.19.3 (7c4205b5c6e52a53b81c69d2b2dc8a627abaa0ba, 2018-01-25T10:32:23.601Z)
OS Version: Linux x64 3.13.0-141-generic
Extensions:

Extension
Author (truncated)
Version

vscode-boot-java
Piv
0.1.3

vscode-boot-properties
Piv
0.1.3

vscode-bosh
Piv
0.1.3

vscode-concourse
Piv
0.1.4-201802010127

vscode-manifest-yaml
Piv
0.1.3

java
red
0.18.1

vscode-java-debug
vsc
0.6.0

vscode-java-pack
vsc
0.2.0

vscode-spring-initializr
vsc
0.1.0

Steps to Reproduce:

Generate a brand new vscode extension using the yo code generator
Place a breakpoint  on line 12 in extension.ts
Press F5 to launch debugger
In the launched vscode instance, press CTRL-SHIFT-P and select "Hello World" command

=> Observe that...

Extension is activated message 'Congratulations....' is printed in DEBUG CONSOLE
The Debugger did not stop in the breakpoint where this message is printed.

Note: I have also tried to make set
 "stopOnEntry": true,

In launch.json, but also in this case the debugger doesn't seem to work at all. I.e. the process just runs and doesn't stop anywhere, not on entry and not on any breakpoint I have put.
I first observed this in one of my own extension, trying to debug it. Then I verified it with brand-new generated 'sample' from the yo-code generator.
I can attach the generated project (didn't make any changes to it though, just generate, put breakpoint and run). Or let me know if there's any other information that might be useful and I'll do my best to provide it.

Reproduces without extensions: Yes

Attaching a screenshot showing active breakpoint and 'proof' that corresponding line of code was indeed executed (output in debug console).

PS: I also tried putting a breakpoint directly in the .extension.js file rather than the typescript source. That breakpoint also doesn't trigger.

Attaching a .zip with the 'toy project'. I just zipped up the directory and then deleted node_modules to save some space. Need to run npm install to get them back.
my-new-extension.zip

Hi,
First, thanks building an extension! In your package.json you have defined
    "activationEvents": [
        "onCommand:extension.sayHello"
    ]

this means that we'll first activate your extension if this event is triggered, so if you set a breakpoint inside activate method it will only get invoked when the sayHello command is executed from the command pallette.
If you had the following```
"activationEvents": [
"*",
"onCommand:extension.showNetworkTool"
]

your extension would get activated when VS Code starts up, but we don't recommend this for performance reasons. An extension should only get activated when it's used.

I just pulled down your project, updated the launch.json to
        {
            "name": "Extension",
            "type": "extensionHost",
            "request": "launch",
            "runtimeExecutable": "${execPath}",
            "args": ["--extensionDevelopmentPath=${workspaceRoot}" ],
            "outFiles": [ "${workspaceRoot}/out/**/*.js" ],
            "preLaunchTask": "npm: watch"
        },

and is able to break when your command is run:

@kdvolder I've installed your my-new-extension.zip on ubuntu 16.04, ran npm install, opened the project in VS Code 1.19.2, set a breakpoint in line 12, and pressed F5.
In the new window I pressed F1, then typed "hello.." and "Return" which immediately hit the breakpoint.
So your problem does not seem to be easily reproducible.

What type of linux are you using?
if you set another breakpoint in line 21 and then run the "Hello World" action, do you you hit the breakpoint? (my hypothesis: the breakpoint in line 12 is only hit on activation very early in the startup process. It could be that the code line has already been executed before the debugger could register the breakpoint. For the breakpoint in line 21 this shouldn't be a problem).

My Ubuntu version is Ubuntu 14.04 LTS.
@weinand You may be on to something that this is timing issue of some kind. So it could be a race condition which would explain why its not easy to reproduce.
I put a breakpoint in line 21. The breakpoint did not get hit the first time I invoked the 'Hello World' command. I.e. execution passed right through it. However the breakpoint did get triggered the second time. Also the third time etc. Just not the first time.
It is worth mentioning that even the first time it was not 'very early in the startup process'. Because the plugin extension does not get loaded until the command is actually invoked. So the log message only gets printed when the command is invoked the first time. I.e. when I press 'CTRL-P' and execute the command. Typically this some time after vscode debug instance's startup.
It still seems some timing issue are at hand here though. Do breakpoints get registered dynamically only when a corresponding source file is loaded? If so, maybe the response to activate the breakpoint to this 'load event' is too slow?
@auchenberg Yes, I understand that you need to invoke the 'Hello World' command to activate the extension. And I would expect that is when the breakpoint should get hit, but it doesn't. At least not for me.

Also worth mentioning again the 'stopOnEntry' flain in launch.json seems to have no effect. I'm pretty sure this used to work in the past. Not sure this is the same, related or different problem. I can raise a separate bug for that if you wish.

More info that may help... Following up on @auchenberg suggestion. I changed my 'launch.json' according to his example. Basically... I removed the 'sourceMaps: true' piece and 'stopOnEntry: ...' piece.
With this change the breakpoint on line 12 is still skipped, but the breakpoint on line 21is hit even the first time.
It also doesn't make much sense to me that I should remove 'sourceMaps: true'. These are typescript compiled to .js with sourcemap files generated on the side. So don't we need the debugger to make use of these sourcemaps?

Can you repro this when running code --disable-extensions?

Yes, as mentioned in original report, though it may be hard to see amongst all the other auto-generated infos.

More info.
I noticed that @weinand mentioned using VS Code 1.19.2. I think I'm using 1.19.3 (according to auto generated bits of the report).
Decided to give code-insiders a try as well. My breakpoints in the sample project work perfectly in code-insiders. Perhaps this means bug is already fixed? Or maybe its just different timings at play. 'stopOnEntry: true' still has no effect.

@kdvolder the default for 'sourceMaps' is true anyway. So removing that attribute from a launch configuration cannot have any effect.
Yes, trying Insider is always a good strategy as we are fixing issues all day ;-)

@weinand I assume you closed this because it works in Insiders?
Note however that stopOnEntry: true still has no effect, even in insiders. I don't really care about that as much (if breakpoints work early on) but it seems like a bug to me. Do you want me to raise as a new bug ticket?

@kdvolder yes, closed because it works in Insiders (and I assume in the upcoming January stable release as well).
Yes, please file a new issue about the stopOnEntry: true issue.


Provide project description for Pypi

https://pypi.org/project/iopipe/
The Pypi page says that the author has not provided a description.

Duplicate of #202


ability  to replace "" inside tags which contain js code or variable to { } as svelte

What problem does this feature solve?
{ } more readable than " "especially when containing multiple lines of code for example
<button @click="some_action ">
<button @click={some_action }>
i think the second one is more readable
by using { } inside tag instead of " " we can ignore using  :  before props name to indicate it as reactive because any sing inside {} will be reactive but when using " " we must use : before prop name
What does the proposed API look like?
more readable code with adding this option.

https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue-jsx

This is not something we will consider, because it makes the markup no longer syntactically valid HTML.


Webapp refactor

From @lgeorge-idm , relating to https://github.com/InstituteforDiseaseModeling/covasim/pull/171:

[ ] Fix <img src="assets/idm-logo.png" height="30px"/>
The class is 'img-fluid'. You should also add in cova_app.css a max-height for the footer images of 2em and make sure the text aligns properly.

[ ] Fix sidebar height when "General" option is collapsed: <b-collapse visible id="general">

[ ] Overriding the nav-text class and adding the spans is unnecessary. Instead, just override the nav-link class.

[ ] Please use the {{app.github_url}} tokens instead of hard-coded links.

[ ] Overriding the nav-text class and adding the spans is unnecessary. Instead, just override the nav-link class.

[ ] Merge parheader and card-header class.

Adding comments from PR #171 -

[ ] Revisit font for webapp
Quicksand is hard to read on non-Ultra HD monitors. Please pick another font or choose a heavier default weight.

Closed by #200