GUACAMOLE-103: Implement SAML Authentication Extension

Initial cut at a SAML authentication extension.  Plenty of room for improvement, I'm sure - I welcome all comments/suggestions/changes.  I'll kick off my own review, here, shortly.

@necouchman how i can get Guacamole working with CAS for SAML authentication

@saydulk http://guacamole.apache.org/support/

I would like to donate some money to speed up the SAML SSO and SLO support for guacamole. I am waiting to upgrade my pam auth with SLO and SSO. I am using an ipsilon SAML IdP and I would like to test the new extension when ready. If you need a test infrastructure you can contact me and I will share some accounts and an IdP and SP setup.

@tuxcrafter: You're welcome to go ahead and try the extension, now.  It does not support SLO, yet, but should work with version 1.0.0 for logging in.

@tuxcrafter: You're welcome to go ahead and try the extension, now. It does not support SLO, yet, but should work with version 1.0.0 for logging in.

@necouchman We compiled and install the saml extension but I can not figure out how to configure the saml settings.
I probably need to configure the following settings somewhere:
idp-entityId  (metadata)
idp-singleLogoutService.url
idp-singleSignOnService.url
idp-x509cert
sp-privateKey
sp-x509cert
Then it would be good to have a mapping options for the username and groups.

@necouchman Could we get a sample configuration file for the saml extension? It would enable us to start hacking on our saml/guacamole setup.

@LeBrad @tuxcrafter
It's been a little while since I did any testing on this, but this is what I have in my guacamole.properties file for configuring the extension from when I wrote it a while back:
saml-idp-metadata: /etc/guacamole/saml-idp-metadata.xml
saml-entity-id: https://<IP_ADDRESS>/guacamole/api/tokens
saml-idp-url: https://<IP_ADDRESS>/cas/idp/profile/SAML2/Redirect/SSO
saml-callback-url: https://<IP_ADDRESS>/guacamole
saml-logout-url: https://<IP_ADDRESS>/cas/logout
saml-keystore-file: /etc/guacamole/saml-keystore
saml-keystore-password: secret
saml-pkey-password: secret

Note that if you have an XML metadata file from your SAML IDP, you should not need the rest of those details - all of those configuration items should be in the XML file.  Anyway, test away, feel free to let me know if you run into any issues with it.  I do need to rebase it against the latest master repo and redo some of the testing and make sure it's still good, but not sure when I'll get to that.

Thanks for the properties.

Where do we place the certificate for the IdP?
Where do we place the certificates for the guacamole saml server, public and private?
Where do we get the metadata of the guacamole saml server?
How's the single log-out support coming?

Here's my config at the moment:
saml-idp-metadata: /etc/guacamole/saml-idp-metadata.xml
saml-entity-id: https://guacamole.example/guacamole/api/tokens
saml-idp-url: https://ipsilon03.mctest.nl/idp/saml2/SSO/Redirect
saml-callback-url: https://guacamole.example/guacamole
saml-logout-url: https://ipsilon03.mctest.nl/idp/logout

Here are the answers...I think...

Where the certificate is placed will depend on whether you're configuring it with a Metadata file or with individual parameters.  If you have a metadata file, all of the certificates should be in the metadata file.  If you configure with individual parameters, then it'll be in the keystore file.
Would imagine this is the same as item 1.
The metadata file is generated by the IdP, so where you get it will depend on the IdP.  It's been a while since I did it with the CAS system, but I think there was a URL that was accessed that triggered the generation onto the filesystem.  Other IdPs probably have varying methods of generating it - I'd suggest consulting the documentation for the IdP.  I also found a few online metadata generators that will do most of the work for you if the IdP doesn't do it.
Ummmmmmmmm...slow.  Haven't had much time to work on this, sadly - what's even sadder (more sad?) is that I haven't had much time to work on anything Guacamole-related lately :frowning_face:

Hi,  I pulled this, and was attempting to test the SAML auth extension.
everything seems to be building / deploying fine.  but the issue I have is with setting the configuration.
I specified the idp xml file :
saml-idp-metadata: /etc/guacamole/sample-saml.xml
I'm running with tomcat 7,  and regardless of how I specify the saml-idp-metadata, or where I put the .xml file,  i always get the same error :
ERROR c.o.saml2.settings.IdPMetadataParser - XML file'/etc/guacamole/sample-saml.xml' cannot be loaded.XML file '/etc/guacamole/sample-saml.xml' not found in the classpath
I've tried specifying it in relative / absolute paths
I've tried putting it in /etc/guacamole, $TOMCAT_HOME, $TOMCAT_BASE, $TOMCAT_HOME/lib, $TOMCAT_BASE/lib,  the resources folder in the source code to get into the .jar extension.  I added /etc/guacamole to the catalina properties common.loader, and shared.loader
if anyone has any ideas, I'd love to hear them.
thanks

Adding myself to the CC list.

Okay, quite a bit of refactoring done, here, and I've tested successfully against the CAS implementation of SAML.

Well, that was fun. Should all be rebased on the current staging/1.2.0 branch with the new field.  Going to do some testing and review of the code to make sure it's all good, because that rebase was no fun.  Lesson learned.

What happened that made this rebase particularly hairy?

What happened that made this rebase particularly hairy?

The changes to implement the common RedirectField class were intertwined at various stages along the way throughout the rest of the changes.  In retrospect, I should have developed that separately from the other changes and then rebased.
Also, this has been going on for 18 months or so, now, I think - maybe 2 years at this point - so there were lots of version updates and license changes along the way.  Extracting the RedirectField and squashing down the other changes was interesting :-).

Yeah, pretty much.

One additional thing I'm seeing in the SAML client - when the IdP redirects back to the Guacamole Client and the login completes successfully, the responseHash URL parameter is still on the URL.  As long as the user navigates to another page this isn't a problem, as the navigation removes the parameter; however, if the user reloads the page or tries to go to logout, an error is received because it tries to process the responseHash parameter and cannot find it in the SAMLResponseMap.
Is there something I should do (similar to the OpenID extension, maybe?) to remove this after a successful login?

I don't think the OpenID extension removes this, either, but it handles the presence of an invalid token identically to the total absence of a token. You could do the same - log at the info or debug level that an invalid hash was received and then move forward requesting a new SAML response?

Ah, okay, yes - I've tweaked it so that it should behave that way - I'll verify when I get a moment to recompile and test.

Okay, redirect appears to be working okay, now.  One more issue I need to fix, though - when you try to specify the saml-idp-metadata option with a metadata file it throws an error:
ERROR c.o.saml2.settings.IdPMetadataParser - XML file'/etc/guacamole/saml-idp-metadata.xml' cannot be loaded.XML file '/etc/guacamole/saml-idp-metadata.xml' not found in the classpath

I guess whatever method I've used to load the file doesn't accept absolutely paths, or requires a URI or something like that.

Okay, I switched the saml-idp-metadata parameter to be a URIGuacamoleProperty instead of FileGuacamoleProperty and this seems to have done the trick.  It makes configuration a little bit nuanced, but actually provides the flexibility to have it pull metadata from either a local file (via a file:// URI) or a remote URI.

I've tested successfully with the CAS SAML provider, both with a metadata file (using a file:// URI) and with manually specifying the parameter for accessing the server.  If I can find another SAML provider or two to test with I will try to get that done, but I don't have ready access to any aside from CAS.

@necouchman Hello can you provide information how to provide connection to user logged in with saml authentication?

@puneetshukla-siemens: This is a closed pull request, and is not intended to be a support forum.  Please subscribe to the mailing list and ask your question, there:
http://guacamole.apache.org/support/

I tried with OKTA pulling the metadata from a file. Problem I get is an endless loop between OKTA and the url callback. Somehow  after OKTA authenticates successfully, Guacamole is not capturing that.

@JPedroGon: Please post your questions to the mailing list.  This is a closed/merged pull request and is not designed to be a support forum.
http://guacamole.apache.org/support/


protostar format in docs

#617

I would write a short guide about formatting code in order to make this feature more visible.


Ajax 500 error when i get table custom-tables.php

Hello, I'm trying to get, and I have a 500 error in the POST

Make sure that your PHP version is somewhere at 7.4 or above.

But php is PHP Version 8.0.12

Alert when i got to main page DataTables warning: table id=miner-table - Ajax error. For more information about this error, please see http://datatables.net/tn/7

A miner could have sent an invalid hashrate (known problem), you could replace your database with a clean one (backup any configurations if you have made any)

but if I click on the id, then the table is loaded, maybe the fact is that nothing comes to the id from the very beginning?

No (because that's not how it's designed), you can check for an error.log file somewhere among the files to see if it has generated any.

PHP Parse error:  syntax error, unexpected token "$",  in database.php


Switch from rusttype to rustybuzz

This is necessary for better text shaping.

Turns out this is quite slow, around 800us per frame, out of 1ms total (so a 5x slowdown). This is still easily without the 16.6ms you'd have for 60 FPS, but it still seems like too much of a slowdown to just merge. We may want to fold this into some refactor that doesn't need to recalculate everything every frame.


rendercontent does not take whole height of bottomsheet

Hello guys, I don't know if I am missing anything but the component which I have passed to rendercontent prop does not have a whole height of bottomsheet. please help me with this.
Sharing with you the code
bottom sheet
<BottomSheet
     ref={filterSheetRef}
     snapPoints={snapPoints}
     borderRadius={borderRadius}
     renderContent={renderContent}
     renderHeader={renderHeader}
     initialSnap={initialSnap}
     enabledInnerScrolling={false}

   />

render content
const renderItem = useCallback(({item}) => (
    <CheckBox
      containerStyle={Style.filterCheckboxContainer}
      title={item.name}
      checked={item.checked}
    />
  ));

  return (
    <View style={Style.filterSheetView()}>
      <FlatList
        data={data}
        showsVerticalScrollIndicator={false}
        keyExtractor={keyExtractor}
        style={Style.filterSheetList}
        contentContainerStyle={Style.filterSheetListContainer}
        renderItem={renderItem}
      />
      <TouchableOpacity style={Style.filterSheetButton}>
        <Text style={Style.filterSheetButtonText}>{hardcodes.DONE}</Text>
      </TouchableOpacity>
    </View>
  );

style.js
filterSheetView: (devHeight) => ({
    backgroundColor: UIColors.background_color_primary,
    padding: verticalScale(15),
  }),

  filterSheetList: {
    flexGrow: 0,
  },
  filterSheetListContainer: {},
  filterCheckboxContainer: {
    backgroundColor: UIColors.background_color_primary,
    borderWidth: 0,
  },
  filterSheetButton: {
    justifyContent: 'center',
    alignItems: 'center',
    borderWidth: 1,
    borderRadius: 5,
    padding: moderateScale(8),
    marginTop: moderateVerticalScale(10),
    marginHorizontal: moderateScale(15),
    marginBottom: moderateVerticalScale(10),
  },

I am having this same issue. I can't seem to figure it out either

You can put height as 100% on render content view. https://github.com/osdnk/react-native-reanimated-bottom-sheet/issues/188#issuecomment-613520615

@ridhuandaud
Thank you. I added height: '100%', and it worked.
However, I got another problem that content is not scrollable.
Can you still scroll content after adding height: '100%'?

@yoshifumi4423 have you solved this issue? I am also facing the same issue. Once the height is set to 100%, i cannot scroll anymore. My content has dynamic height and cannot predefine with a specific number..

@Aung-Myint-Thein
Yes, I solved it. I wrote below code.
      <BottomSheet
        ref={bottomSheetRef}
        snapPoints={[props.height || '90%', 0]}
        initialSnap={1}
        renderHeader={renderHeaderModal}
        renderContent={
          props.hasScroll
            ? () => props.children
            : () => (
                <ScrollView
                  style={{
                    height: '100%',
                    backgroundColor: 'white',
                  }}>
                  {props.children}
                </ScrollView>
              )
        }
        onOpenStart={() => (canCloseModal = false)}
        onOpenEnd={() => (canCloseModal = true)}
        onCloseEnd={closeModal}
      />

*props.hasScroll means if props.children has ScrollView or Flatlist, and when it is false wrap props.children with ScrollView  to scroll the content.
*Maybe you can remove props.hasScroll if you don't need it.
*I don't know about what initialSnap={1} effects.
Also, I have another problem that BottomSheet can not be closed by swiping down the content area.
And this is what  I want  the BottomSheet  to behave.
https://github.com/osdnk/react-native-reanimated-bottom-sheet/blob/master/gifs/1.gif

@yoshifumi4423 have you solved this issue? I am also facing the same issue. Once the height is set to 100%, i cannot scroll anymore. My content has dynamic height and cannot predefine with a specific number..

You can just use minHeight instead of height and you'll have the best of the two worlds


Motion detection not kicking in on Solocam S230

If I walk in front of one of my cameras and see that the IR light kicks in, but the integration is not picking up motion on one of my cameras (the other one seems like it might be picking it up).  In other words, the "Motion detected" and "Person detected" sensors but are off.
A clear and concise description of what the bug is.
To reproduce
Steps to reproduce the behavior:

Go to settings
Click Devices & services
Open the Eufy security integration
Choose one of the devices
Walk in front of the camera.
Observe that the sensor states don't change.

Expected behavior
The motion/person sensors turn on.
Additional information
Home Assistant Installation Type (OS - Supvervised - Core):
Home Assistant OS
Home Assistant Core Version:
core-2024.9.2
Eufy Security Add-on Version:
1.9.0
Eufy Security Integration Version:
8.0.4
Hardware Information;
Camera Model: Solocam S230

Debug Logs from Home Assistant (https://github.com/fuatakgun/eufy_security/discussions/624) - Without this, I will automatically resolve this issue

home-assistant_eufy_security_2024-09-21T01-39-25.332Z.log

Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):

Would you share your device with me in case further debugging required? (Yes/No):
No

Additional context
Add any other context about the problem goes here. Mainly, share everything as log files and use screenshots as last resort.

Did you enable full push notifications on the mobile app for motion events?

I have automations set up to only put me on one of the 3 custom modes. 2 and 3 give me notifications, but 1 does not. I was testing this in 2 and 3. One of my cameras was sending me push notifications AND was updating the state in HA. The other camera did neither.

The integration fully relies on push notifications for events (motion, person etc).
Can you confirm if you are receiving notifications into your mobile app from the second one?

According to my settings, I should have been getting push notifications when I was testing this. It looks like the camera that's not working not only isn't sending notifications, it doesn't look like it's saving any recordings in the Eufy Security app.

According to my settings, I should have been getting push notifications when I was testing this. It looks like the camera that's not working not only isn't sending notifications, it doesn't look like it's saving any recordings in the Eufy Security app.
Update: no idea what I did, but my camera is saving events on the Eufy Security app now. Since the other cameras are working fine with this integration, the questionable one should hopefully be good now.

@fuatakgun while I'm on the topic though, I'm noticing that the reported battery percentage as well as the charging state aren't matching what I see in the Eufy app. Let me know if you want me to open a separate issue for this.


remove unnecessary test suite

As title, test log:
mac:kcp-tests jianzhang$ ./bin/kcp-tests run all --dry-run|grep 2800712
I0627 11:42:12.387923   18683 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
"[kcp] Kcpsanity Author:knarra-Medium-2800712-Checking oc version show clean as gitTreeState value [Suite:openshift/conformance/parallel]"
mac:kcp-tests jianzhang$ ./bin/kcp-tests run all --dry-run|grep 2800712|./bin/kcp-tests run -f -
I0627 11:42:35.846784   18708 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
I0627 11:42:35.879139   18710 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
Jun 27 11:42:35.879: INFO: The --provider flag is not set. Continuing as if --provider=skeleton had been used.
started: (0/1/1) "[kcp] Kcpsanity Author:knarra-Medium-2800712-Checking oc version show clean as gitTreeState value [Suite:openshift/conformance/parallel]"

I0627 11:42:45.559437   18753 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
Jun 27 11:42:45.559: INFO: The --provider flag is not set. Continuing as if --provider=skeleton had been used.
Jun 27 11:42:45.592: INFO: Waiting up to 30m0s for all (but 100) nodes to be schedulable
Jun 27 11:42:47.446: INFO: Unschedulable nodes:
Jun 27 11:42:47.446: INFO: -> ip-10-0-164-130.us-east-2.compute.internal Ready=true Network=false Taints=[{node-role.kubernetes.io/infra  NoSchedule <nil>}] NonblockingTaints:node-role.kubernetes.io/master
Jun 27 11:42:47.459: INFO: -> ip-10-0-212-38.us-east-2.compute.internal Ready=true Network=false Taints=[{node-role.kubernetes.io/infra  NoSchedule <nil>}] NonblockingTaints:node-role.kubernetes.io/master
Jun 27 11:42:47.460: INFO: -> ip-10-0-155-102.us-east-2.compute.internal Ready=true Network=false Taints=[{node-role.kubernetes.io/infra  NoSchedule <nil>}] NonblockingTaints:node-role.kubernetes.io/master
Jun 27 11:42:47.460: INFO: ================================
Jun 27 11:42:51.745: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Jun 27 11:42:52.527: INFO: 0 / 0 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Jun 27 11:42:52.527: INFO: expected 0 pod replicas in namespace 'kube-system', 0 are Running and Ready.
Jun 27 11:42:52.527: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start
Jun 27 11:42:52.831: INFO: e2e test version: v0.0.0-master+$Format:%h$
Jun 27 11:42:53.127: INFO: kube-apiserver version: v1.23.5+3afdacb
Jun 27 11:42:53.440: INFO: Cluster IP family: ipv4
[BeforeEach] [Top Level]
  /Users/jianzhang/goproject/src/github.com/kcp-dev/kcp-tests/test/extended/util/test.go:60
[BeforeEach] [kcp] Kcpsanity
  /Users/jianzhang/goproject/pkg/mod/github.com/openshift/kubernetes@v1.17.0-alpha.0.0.20200120180958-5945c3b07163/test/e2e/framework/framework.go:154
STEP: Creating a kubernetes client
[BeforeEach] [kcp] Kcpsanity
  /Users/jianzhang/goproject/src/github.com/kcp-dev/kcp-tests/test/extended/util/client.go:115
Jun 27 11:42:55.840: INFO: configPath is now "/var/folders/2c/4whhm34n7892mf9l2j02cf480000gn/T/configfile1706327596"
Jun 27 11:42:55.840: INFO: The user is now "e2e-test-kcp-vjoer2wr-mbh77-user"
Jun 27 11:42:55.840: INFO: Creating project "e2e-test-kcp-vjoer2wr-mbh77"
Jun 27 11:42:56.204: INFO: Waiting on permissions in project "e2e-test-kcp-vjoer2wr-mbh77" ...
Jun 27 11:42:56.460: INFO: Waiting for ServiceAccount "default" to be provisioned...
Jun 27 11:42:56.929: INFO: Waiting for ServiceAccount "deployer" to be provisioned...
Jun 27 11:42:57.290: INFO: Waiting for ServiceAccount "builder" to be provisioned...
Jun 27 11:42:57.736: INFO: Waiting for RoleBinding "system:image-pullers" to be provisioned...
Jun 27 11:42:58.250: INFO: Waiting for RoleBinding "system:image-builders" to be provisioned...
Jun 27 11:42:58.867: INFO: Waiting for RoleBinding "system:deployers" to be provisioned...
Jun 27 11:42:59.478: INFO: Project "e2e-test-kcp-vjoer2wr-mbh77" has been fully provisioned.
[It] Author:knarra-Medium-2800712-Checking oc version show clean as gitTreeState value [Suite:openshift/conformance/parallel]
  /Users/jianzhang/goproject/src/github.com/kcp-dev/kcp-tests/test/extended/kcpsanity/kcp_basics.go:31
Jun 27 11:43:00.725: INFO: output is:{
  "clientVersion": {
    "major": "1",
    "minor": "16",
    "gitVersion": "v1.16.3",
    "gitCommit": "b3cbbae08ec52a7fc73d334838e18d17e8512749",
    "gitTreeState": "clean",
    "buildDate": "2019-11-13T11:23:11Z",
    "goVersion": "go1.12.12",
    "compiler": "gc",
    "platform": "darwin/amd64"
  },
  "serverVersion": {
    "major": "1",
    "minor": "23",
    "gitVersion": "v1.23.5+3afdacb",
    "gitCommit": "3c28e7a79b58e78b4c1dc1ab7e5f6c6c2d3aedd3",
    "gitTreeState": "clean",
    "buildDate": "2022-05-10T16:30:48Z",
    "goVersion": "go1.17.5",
    "compiler": "gc",
    "platform": "linux/amd64"
  }
}
[AfterEach] [kcp] Kcpsanity
  /Users/jianzhang/goproject/src/github.com/kcp-dev/kcp-tests/test/extended/util/client.go:106
Jun 27 11:43:00.987: INFO: Deleted {user.openshift.io/v1, Resource=users  e2e-test-kcp-vjoer2wr-mbh77-user}, err: <nil>
Jun 27 11:43:01.253: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-kcp-vjoer2wr-mbh77}, err: <nil>
Jun 27 11:43:01.525: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens  sha256~VfZacdlscoXjk7fkReUAKjwXDu6-CBdMxTJypqSkDf0}, err: <nil>
[AfterEach] [kcp] Kcpsanity
  /Users/jianzhang/goproject/pkg/mod/github.com/openshift/kubernetes@v1.17.0-alpha.0.0.20200120180958-5945c3b07163/test/e2e/framework/framework.go:155
Jun 27 11:43:01.526: INFO: Waiting up to 7m0s for all (but 100) nodes to be ready
STEP: Destroying namespace "e2e-test-kcp-vjoer2wr-mbh77" for this suite.
Jun 27 11:43:03.665: INFO: Running AfterSuite actions on all nodes
Jun 27 11:43:03.669: INFO: Running AfterSuite actions on node 1

passed: (27.8s) 2022-06-27T03:43:03 "[kcp] Kcpsanity Author:knarra-Medium-2800712-Checking oc version show clean as gitTreeState value [Suite:openshift/conformance/parallel]"

1 pass, 0 skip (27.8s)

@kasturinarra Could you help merge it? Thanks!


chore(dependencies): upgrade TS to latest minor

Short description of what this resolves:
Allows upgrading to TypeScript 2.x (e.g. to 2.1.6) because:

it is backward compatible
users of ionic-app-scripts may use other modules requiring 2.1.x and higher.

Changes proposed in this pull request:

update package.json

Fixes: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/14579

Thank you very much.
Related to https://github.com/DefinitelyTyped/DefinitelyTyped/issues/14579 👍

We can't use TS 2.1 until Angular supports it, so once Angular 4 is out, we'll move to it.
Thanks,
Dan

@danbucholtz Doesn't Angular 2 support Typescript 2.1+? Latest versions of starter apps (e.g. https://github.com/AngularClass/angular2-webpack-starter) all have Typescript > 2.1. Angular 2.2.1 (latest used by recent ionic release) supports 2.1+.

Hi @noomorph,
Thanks for the PR. We already implemented this though. Thank you for contributing to Ionic!
Thanks,
Dan


path messed up on Linux in newest release

Hello! The path on Linux (Debian 13 testing) looks like "path/to/executable/file:/path/to/actual/file" in the newest release 0.8.4. In the previous release this doesn't happen. This also leads to for example readBytesto fail.

Hi! Thanks for reporting this! Sorry for the regression 😅 I'm going to take a look

Does version 0.8.5 fix the problem?

Now the pickFile function throws an exception before completion:
Exception in thread "AWT-EventQueue-0 @coroutine#184" java.lang.IllegalArgumentException: URI is not absolute
	at java.base/java.io.File.<init>(File.java:418)
	at io.github.vinceglb.filekit.core.platform.xdg.XdgFilePickerPortal.pickFiles(XdgFilePickerPortal.kt:116)
	at io.github.vinceglb.filekit.core.platform.xdg.XdgFilePickerPortal.access$pickFiles(XdgFilePickerPortal.kt:29)
	at io.github.vinceglb.filekit.core.platform.xdg.XdgFilePickerPortal$pickFiles$2.invokeSuspend(XdgFilePickerPortal.kt)

I intercepted the URI using the debugger and it looked like this "file%3A%2F%2F%2Fhome%2Fuser%2FDownloads%2Fdirectory%2Ffile.txt". I don't know how it looks in the other versions but maybe something is off with the encoding?

Thank you for your suggestion. I added the scheme in the tests.
When receiving the URI string, I removed the scheme part and encoded the rest. Then I created the URI from the encoded rest without the scheme. It's working in the tests, but I haven't a Linux to test it on my own.
I created version 0.8.6. I hope it's fixed now!

Hm, I still got the same error message. I think maybe the scheme in val (_, rest) = splitUrl(this) shouldn't be discarded but like after url encryption of the path added again because this is what I think where the exception is thrown:

Really hope I don't mislead you in some way :worried:, but I think it should work after that. I feel a bit bad already to cause all these new releases 😅

No problem, it's my bad at the end. I downloaded an Ubuntu VM this time to test my changes.
Version 0.8.7 is out, it should be good now 😂🤞

It's resolved for me now, thank you!


MGDSTRM-10232 initial configuration to control the ic scope

Adds a new stanza to the agent spec to control the scope of the ic NLBs.
Since we have a timed job for reconciliation, we don't need to add a specific event handler for the managedkafkaagent - an assumption we were already making about the profile logic.

Consider using network instead of net

That's one vote for an annotation, one vote for network, and one vote for access.

Rather than boolean _private use String visibility with enumeration Public and Private

We want to leave open the possibility that this won't be a single case - there could be separate public and private configurations.

To round things out here:

If we switch to an annotation we'll need to update the managedkafkaagent sync logic as it currently only copies the spec.  It shouldn't have the same problem as managedkafka with both control plane and data plane managed annotations.
It probably doesn't matter what change we make to the spec, it will just be a throw-away once we have a better understanding of the pod.  Since there's no real public usage of the crd that is fine.

To combine the above and most of the suggestions, how about just:
spec:
  access: Private

which we will likely throw away once we need refine things further.

To combine the above and most of the suggestions, how about just:
spec:
  access: Private

which we will likely throw away once we need refine things further.

I'm fine with this ^

do we need changes here to refelect the above?

do we need changes here to reflect the above?

Oh, I thought we said on the issue / standup before break, just to leave the pr as is because it's likely a throw away in any case.

:)


OMPL installation fails

When running ./install_ompl_1.5.2.sh --python, the following error occurs:
(...)
Length: unspecified [application/x-gzip]
Saving to: 'STDOUT'

-                                                                   [         <=>                                                                                ]  22.01M  12.5MB/s    in 1.8s

2024-12-22 01:22:12 (12.5 MB/s) - written to stdout [23082698]

-- The CXX compiler identification is GNU 13.3.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Build type: Release
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1")
-- Checking for module 'ode'
--   Found ode, version 0.16.2
-- Checking for module 'flann'
--   Package 'flann', required by 'virtual:world', not found
-- Checking for module 'libspot'
--   Package 'libspot', required by 'virtual:world', not found
-- Could NOT find spot (missing: SPOT_LIBRARIES SPOT_INCLUDE_DIRS)
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- Found PY_numpy: /usr/lib/python3/dist-packages/numpy
-- Could NOT find PY_pyplusplus (missing: PY_PYPLUSPLUS)
-- Could NOT find PY_pygccxml (missing: PY_PYGCCXML)
-- Found castxml: /usr/bin/castxml
-- Checking for module 'yaml-cpp'
--   Found yaml-cpp, version 0.8.0
-- Found yaml-cpp: yaml-cpp
-- The following features have been enabled:

 * OMPL_VERSIONED_INSTALL, Whether to install header files in
   <prefix>/include/ompl-X.Y/ompl, where X and Y are the major and minor
   version numbers
 * OMPL_BUILD_TESTS, Whether to build the unit tests.
 * OMPL_BUILD_DEMOS, Whether to build the OMPL demo programs.

-- The following OPTIONAL packages have been found:

 * Threads, <https://en.wikipedia.org/wiki/POSIX_Threads>
   Pthreads is sometimes needed, depending on OS / compiler.
 * pypy, <https://pypy.org>
   Used to speed up the generation of python bindings.
 * ODE, <http://ode.org>
   The Open Dynamics Engine can be used as a "black box" for kinodynamic planning.
 * castxml, <https://github.com/CastXML/CastXML>
   Used to generate Python bindings.
 * PkgConfig, <https://www.freedesktop.org/wiki/Software/pkg-config/>
   Used to find (compilation flags for) dependencies.
 * yaml-cpp, <https://github.com/jbeder/yaml-cpp>
   Used for parsing input data for the PlanarManipulator demo.
 * Python, <https://www.python.org>
   Used for python bindings.

-- The following REQUIRED packages have been found:

 * Eigen3, <http://eigen.tuxfamily.org>
   A linear algebra library used throughout OMPL.
 * Boost (required version >= 1.58), <https://www.boost.org>
   Used throughout OMPL for data serialization, graphs, etc.

-- The following features have been disabled:

 * OMPL_BUILD_PYBINDINGS, Whether to build the Python bindings.
 * OMPL_BUILD_PYTESTS, Whether to build/run the python binding unit tests.

-- The following OPTIONAL packages have not been found:

 * MORSE, <https://www.openrobots.org/wiki/morse>
   OMPL includes a plugin for the MORSE Robot Simulation engine.
 * Triangle, <http://www.cs.cmu.edu/~quake/triangle.html>
   Used to create triangular decompositions of polygonal 2D environments.
 * flann (required version >= 1.8.3), <https://github.com/mariusmuja/flann>
   If detetected, FLANN can be used for nearest neighbor queries by OMPL.
 * spot, <http://spot.lrde.epita.fr>
   Used for constructing finite automata from LTL formulae.
 * Doxygen, <http://doxygen.org>
   Used to create the OMPL documentation (i.e., https://ompl.kavrakilab.org).

-- The following Python modules were found:

 * numpy

-- The following Python modules were NOT found:

 * pyplusplus pygccxml

-- Configuring done (1.4s)
-- Generating done (0.2s)
-- Build files have been written to: /root/RoboGen/ompl-1.5.2/build/Release
make: *** No rule to make target 'update_bindings'.  Stop.
(robogen) root@8d9e3c06d12f:~/RoboGen#

Have you tried the prebuilt wheels?


Alert is not affected by Paper prop square

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Alert component is not affected by the square prop of the Paper component.
Expected behavior 🤔
Alert component should be affected by the square prop of the Paper component and remove the rounded corners.
Steps to reproduce 🕹
Steps:

Use Alert component with square prop
Sandbox

Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Browsers:
    Chrome: 95
  npmPackages:
    @emotion/react: ^11.6.0 => 11.6.0
    @emotion/styled: ^11.6.0 => 11.6.0
    @mui/core:  5.0.0-alpha.54
    @mui/lab: ^5.0.0-alpha.54 => 5.0.0-alpha.54
    @mui/material: ^5.1.0 => 5.1.0
    @mui/private-theming:  5.1.0
    @mui/styled-engine:  5.1.0
    @mui/system:  5.1.0
    @mui/types:  7.1.0
    @mui/utils:  5.1.0
    @mui/x-data-grid: ^5.0.0-beta.7 => 5.0.0-beta.7
    @types/react: 17.0.30 => 17.0.30
    react: 17.0.2 => 17.0.2
    react-dom: 17.0.2 => 17.0.2
    typescript: ~4.3.5 => 4.3.5

Duplicate of #28193

Please use sx instead.
<Alert sx={{ borderRadius: 0 }} />

@siriwatknp The Alert component has the properties of Paper. It should work! With that reasoning we can use sx for almost anything and props have no purpose.


Feature: Provide a Record Button

Instead of recording as soon as the webcam becomes available and shows on screen. There should be an option for the user to push a 'button' to record when they are ready. It is rare that someone would be "ready" and in scene when the camera first comes up.

Thanks for the input! I'm closing this issue since we aren't adding the video portion of the project anymore.


Add inventory sub-command to return inventory JSON content

Add @wenottingham for additional comments

My first question is how this request is different from running the command:

tower-cli inventory list --format=json

This returns the JSON output which contains all of the inventory records. Once we get more people to weigh in on this issue, I predict that the requirements will go beyond this. For now, I just want to get this out there to establish a baseline functionality which already exists and is almost trivial to use.

@AlanCoding the provided command would be expected to list the json output of the /api/v1/inventories/N/ endpoint from Tower.
You want the equivalent of /api/v1/inventories/N/script/ surfaced through tower-cli inventory script?

RIght, we'd want the json form of a particular inventory, including variables - it would be more 'tower-cli inventory get 3 --format=json'

Thanks, I'm understanding better now. /api/v1/inventories/N/ is a completely different animal from /api/v1/inventories/N/script/. I picture this being returned by a command like tower-cli inventory_script get N --format=json. Maybe that syntax could use some tweaking as well. Depending on what the usage scenario is, we might want something more than a get request, but I'm not sure yet.

Make sure you use /api/v1/inventories/N/script/?hostvars=1 to return the host variables in the response.


using lua functions without onCreate callback

lua: 📈
for example, u can use this line as .lua file, and it will work:
setProperty('skipArrowStartTween', true)

all pr just about do callbacks BEFORE loading lua file (game doing it AFTER)

what exactly does this do? im kinda confused

what exactly does this do? im kinda confused

earlier u can use script only like this:
function onCreate()
    setProperty('skipArrowStartTween', true)
end

now u can use this script too:
setProperty('skipArrowStartTween', true)

loving this


SpecMath Service implementation and testing

Implemented the SpecMath service to make backend calls
Tested the service with mock http requests and mock requests
Added a shared directory with routes and interfaces

In this PR or one in the near future, lets update the README.md to say what ng test does....ie grab all files that end in spec.ts and run them, so consumers know to add tests all they have to do is add files and not mess with any of the project bootstrapping.

LGTM


Issues with emoji

Expected behavior
Emoji is correct
Actual behavior
Emoji in demo was cut off, and emoji as unicode is marked as 1ch (it should be 2ch).
The fix for css:
.cmd .emoji, .terminal-output>:not(.raw) .emoji {
    background-size: contain;
    background-repeat: no-repeat;
}

and solution for width, the formatter need to add style attribute.

It's seems that there is only unicode character with 1ch that I was using, rest the of emoji have 2 characters size.

released in 2.8.0


Spotify API error: invalid type: null

Everytime I launch Spot via Flatpak, I get a notifcation in Spot that says:
"An Error Occured. Check logs for details!"
Distro: Fedora 40 (Workstation) (Desktop)
Spot Version: 0.4.1
Logs:
6:47:20 PM spot: [2024-05-14T22:47:20Z ERROR spot::app::components] Spotify API error: invalid type: null, expected a sequence at line 1 column 3696
 6:47:20 PM spot: [2024-05-14T22:47:20Z ERROR spot::app::components] Spotify API error: invalid type: null, expected a sequence at line 1 column 3696
 6:47:20 PM spot: [src/api/cached_client.rs:256:17] e = Error("invalid type: null, expected a sequence", line: 1, column: 3696)
 6:47:20 PM spot: [src/api/cached_client.rs:256:17] &cache_key = "me_playlists_0_30.json"
 6:47:19 PM spot: [2024-05-14T22:47:19Z ERROR spot::app::components] Spotify API error: invalid type: null, expected a sequence at line 1 column 3696
 6:47:19 PM spot: [src/api/cached_client.rs:256:17] e = Error("invalid type: null, expected a sequence", line: 1, column: 3696)
 6:47:19 PM spot: [src/api/cached_client.rs:256:17] &cache_key = "me_playlists_0_30.json"
 6:47:17 PM spot: [src/api/cached_client.rs:256:17] e = Error("invalid type: null, expected a sequence", line: 1, column: 3696)
 6:47:17 PM spot: [src/api/cached_client.rs:256:17] &cache_key = "me_playlists_0_30.json"
 6:47:17 PM spot: GtkLabel 0x55855edf5ca0 (label) reported min height 26 and natural height 22 in measure() with for_size=-1; natural size must be >= min size

Stack Retrace:
(process:2): Adwaita-CRITICAL **: 18:55:32.911: adw_leaflet_set_visible_child: assertion 'contains_child' failed
[src/api/cached_client.rs:256:17] &cache_key = "me_playlists_0_30.json"
[src/api/cached_client.rs:256:17] e = Error("invalid type: null, expected a sequence", line: 1, column: 3696)

(spot:2): Gtk-WARNING **: 18:55:33.105: GtkLabel 0x557cce4bcca0 (label) reported min height 26 and natural height 22 in measure() with for_size=-1; natural size must be >= min size
[src/api/cached_client.rs:256:17] &cache_key = "me_playlists_0_30.json"
[src/api/cached_client.rs:256:17] e = Error("invalid type: null, expected a sequence", line: 1, column: 3696)
[2024-05-14T22:55:35Z ERROR spot::app::components] Spotify API error: invalid type: null, expected a sequence at line 1 column 3696
[src/api/cached_client.rs:256:17] &cache_key = "me_playlists_0_30.json"
[src/api/cached_client.rs:256:17] e = Error("invalid type: null, expected a sequence", line: 1, column: 3696)
[2024-05-14T22:55:35Z ERROR spot::app::components] Spotify API error: invalid type: null, expected a sequence at line 1 column 3696

I did some testing on the repo. It doesn't know how to handle playlists with no images, and crashes...
In the meantime while this isn't fixed, add an image or delete any playlists you have that has the default double-eighth-note image.


Add slot related helper interfaces

This adds Content and Render, two interfaces that should help us ensure the correct types are passed to our slot code. This is a first pass only and does not fix all instances of content and renderings.

This is probably failing the tslint check for no-any. You need to disable that for the specific lines where any is used.

I think it would be better to spend a little more time nailing down the actual types there.


Update website 7/6/2018

\cc @DevExpress/testcafe-docs
Update the website to fix the star counter,
Preview at: https://vasilystrelyaev.github.io/testcafe/ (ideally, in different browsers and on Mac). Also, please check the search panel.
(CSS for the Studio landing page block also appear in this PR. No need to worry - it's just CSS.)

Button is sticking out little bit (under search panel)

#2607 was merged (instead of this PR)


App in Openliberity can't be started

Expected Behavior
Can deploy and start the openliberity app https://github.com/showpune/sample-getting-started
Current Behavior
Got error duiring start
{"type":"liberty_message","host":"8de54b813d7a","ibm_userDir":"/layers/paketo-buildpacks_liberty/base/wlp/usr/","ibm_serverName":"defaultServer","message":"tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)","ibm_threadId":"00000038","ibm_datetime":"2023-09-10T08:45:32.502+0000","module":"SystemErr","loglevel":"SystemErr","ibm_methodName":"","ibm_className":"","ibm_sequence":"1694335532502_00000000000A9","ext_appName":"app","ext_thread":"Default Executor-thread-14"}
{"type":"liberty_message","host":"8de54b813d7a","ibm_userDir":"/layers/paketo-buildpacks_liberty/base/wlp/usr/","ibm_serverName":"defaultServer","message":"tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)","ibm_threadId":"00000038","ibm_datetime":"2023-09-10T08:45:32.503+0000","module":"SystemErr","loglevel":"SystemErr","ibm_methodName":"","ibm_className":"","ibm_sequence":"1694335532503_00000000000AA","ext_appName":"app","ext_thread":"Default Executor-thread-14"}
{"type":"liberty_message","host":"8de54b813d7a","ibm_userDir":"/layers/paketo-buildpacks_liberty/base/wlp/usr/","ibm_serverName":"defaultServer","message":"tat java.base/java.lang.Thread.run(Unknown Source)","ibm_threadId":"00000038","ibm_datetime":"2023-09-10T08:45:32.503+0000","module":"SystemErr","loglevel":"SystemErr","ibm_methodName":"","ibm_className":"","ibm_sequence":"1694335532503_00000000000AB","ext_appName":"app","ext_thread":"Default Executor-thread-14"}
{"type":"liberty_message","host":"8de54b813d7a","ibm_userDir":"/layers/paketo-buildpacks_liberty/base/wlp/usr/","ibm_serverName":"defaultServer","message":"CWWKZ0002E: An exception occurred while starting the application app. The exception message was: com.ibm.ws.container.service.state.StateChangeException: org.jboss.weld.exceptions.DeploymentException: Invalid token=EOF at (line no=1, column no=0, offset=-1). Expected tokens are: [CURLYOPEN, SQUAREOPEN, STRING, NUMBER, TRUE, FALSE, NULL]","ibm_threadId":"00000038","ibm_datetime":"2023-09-10T08:45:32.632+0000","ibm_messageId":"CWWKZ0002E","module":"com.ibm.ws.app.manager.AppMessageHelper","loglevel":"ERROR","ibm_sequence":"1694335532632_00000000000AE","ext_thread":"Default Executor-thread-14"}

Possible Solution

Steps to Reproduce

git clone code https://github.com/showpune/sample-getting-started
run ./pack.sh to deploy the app and run it locally
open localhost:9090, just see the default server page but not the app page
use docker logs , you can see the error above

Motivations

@showpune Paketo buildpacks will only include built artifacts in the run image and the app is relying on files from the source.  See https://paketo.io/docs/howto/java/#include-or-exclude-custom-files.  You can include specific files but they weill be in the /workspace directory in the image.  The app source will need to be modified to look for files in that location.

Hi @kevin-ortega ,
I can't reproduce the problem, possible a issue from online liberity. I will close the bug first


Disqus comments not displaying

[x] This is a question about using the theme.
[ ] This is a feature request or enhancement.
[ ] I believe this to be a bug with the theme.

[ ] I am using the latest version of the theme.
[ ] I have updated all gems with bundle update.
[x] I have tested locally with bundle exec jekyll build.

Environment informations

Minimal Mistakes version:
**Jekyll version:**3.7.2
GitHub Pages hosted: no
Operating system: Linux

Expected behavior
Disqus comments to appear on my blog posts.
Steps to reproduce the behavior

Go to https://cloudbuilder.io/career/Life-Starts-at-Systems-Engineer/
See the comments are not loaded even though the view source-code shows the disqus

Have you set JEKYLL_ENV=production?

Comments are disabled by default in development. To enable when testing/building locally be sure to set JEKYLL_ENV=production to force the environment to production.

crap sorry that was it. I did a :
$ JEKYLL_ENV=production jekyll build
and then pushed the static to my s3 bucket and it loaded.
I've run into another issue but I'll open a separate ticket for that. thank you!

If appropriate I can open a new item, but I had the same exact issue.
I've done every step mentioned above, excepting including comments:true in each post. Instead I included in single layout, which didn't fix this.
In addition, my Netlify build script is
[build]
  command = "JEKYLL_ENV=production jekyll build && jekyll algolia"
  publish = "_site"

Didn't want to open a new issue if this exact same issue is what I'm experiencing. I tested local with production variable in docker, and also have tried with the command and environmental variable from Netlify, but no result.

@sheldonhull Not sure what else to tell you as I don't use Docker or Netlify. The issue does seem to be related to them and setting environment variables.
This is the line in the theme that sets that condition.
{% if jekyll.environment == 'production' and site.comments.provider and page.comments %}
  {% include comments.html %}
{% endif %}

It only shows comments when Jekyll's environment is set to production, comments.provider is set in _config.yml, and the post has comments: true in its YAML Front Matter.
If you're having trouble properly setting production then my suggestion would be to remove the condition in the theme.

Hey,
I have also added everything as described in the documentation but the comment just does not appear:
https://richstone.github.io/blog/test
Setting JEKYLL_ENV=production bundle exec jekyll build/serve in my mac terminal does not help as well.
shortname is indeed datagooide (with typo in it)

@RichStone Check your config file. You have two default keys in _config.yml... the first set of defaults that assigns comments: true to all your posts is being replaced with the second set you're using for pages.
defaults:
  # _posts
  - scope:
      path: ""
      type: posts
    values:
      layout: single
      author_profile: true
      read_time: true
      comments: true
      share: true
      related: true

defaults:
  # _pages
  - scope:
      path: ""
      type: pages
    values:
      layout: single
      author_profile: true

It should be this instead (note there's only one default key with all post/page scopes indented under it:
defaults:
  - scope:
      path: ""
      type: posts
    values:
      layout: single
      author_profile: true
      read_time: true
      comments: true
      share: true
      related: true
  - scope:
      path: ""
      type: pages
    values:
      layout: single
      author_profile: true


GRPC streaming deadline not applicable

GRPC streaming only supports a deadline for the entire stream connection, and cannot be defined per query since GRPC is not implemented to expect a response for each request.
Solution
Move away from GRPC

Or handle the timeouts in the application layer instead.


Implement proof-of-possession for deposit method in deposit contract.

This might requite some BLS precompiles first. Discuss and design before jumping in :)

This is where it needs to go.
https://github.com/Zilliqa/zq2/blob/ff923524b14ced96c5c003d7b4b77f1ae22caa5b/zilliqa/src/contracts/deposit.sol#L63


Error: Could not find or load main class org.apache.spark.launcher.SparkCLRSubmitArguments

Hi I'm getting this issue when I submit when using the spark-cler_2.11.-2.0.000 Preview.
Currently this is running on OSX with the following environment variables set:
export SPARK_HOME="/Users/myuser/Development/Tools/spark-2.0.0-bin-hadoop2.7"
export JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home"
export SPARKCLR_HOME="/Users/myuser/Development/Tools/spark-clr_2.11-2.0.000-PREVIEW-1/runtime"
Funny thing is, this works great with the 1.6.2 version of both spark and the spark-clr.
But when I start to use the 2.0 apache spark, and 2.0 preview of spark-clr, it throws this error:
Error: Could not find or load main class org.apache.spark.launcher.SparkCLRSubmitArguments
Here's the full output:
./sparkclr-submit.sh --verbose --exe apacheSpark.exe /Users/myuser/Development/Projects/apacheSpark/apacheSpark/bin/Debug/apacheSpark.sh
SPARKCLR_CLASSPATH is /Users/myuser/Development/Tools/spark-clr_2.11-2.0.000-PREVIEW-1/runtime/lib/spark-clr_2.11-2.0.000-PREVIEW-1.jar
[sparkclr-submit.sh] LAUNCH_CLASSPATH=/Users/myuser/Development/Tools/spark-clr_2.11-2.0.000-PREVIEW-1/runtime/lib/spark-clr_2.11-2.0.000-PREVIEW-1.jar:/Users/myuser/Development/Tools/spark-2.0.0-bin-hadoop2.7/jars*
Error: Could not find or load main class org.apache.spark.launcher.SparkCLRSubmitArguments
[sparkclr-submit.sh] Command to run

LAUNCH_CLASSPATH variable is not correct in the output you shared. It should be /Users/myuser/Development/Tools/spark-2.0.0-bin-hadoop2.7/jars/* - "/" between "jars" and "*" is missing.
Try changing the backslash to forward slash at https://github.com/Microsoft/Mobius/blob/master/scripts/sparkclr-submit.sh#L58 to see if it helps.

@shakdoesgithub Is your issue resolved? Can we close this issue?

@skaarthik thanks, that was it.  I noticed this is still causing issues in AWS EMR which is based off centos.  Do you want me to create a pull request for this?

@shakdoesgithub - yes, please send PR. I am closing this issue.

I have an issue
whenever i checking pio status
Error: Could not find or load main class org.apache.predictionio.tools.console.Console
eleastic search and HMaster running
jps -l
21012 sun.tools.jps.Jps
20934 org.apache.predictionio.tools.console.Console
20714 org.apache.hadoop.hbase.master.HMaster
20619 org.elasticsearch.bootstrap.Elasticsearch


type changes not updated during watch mode

Issue
When you make changes to the types, e.g. renaming a type, the changes cause the test to fail, even if the change actually works fine.
Need to quit jest watch and start again for the changes to be picked up correctly.
causes
My guess is that during rename, multiple files are affected and ts-jest only detect one file has been changed, so the cache of other files are not invalidated, thus containing outdated information.
This happens whenever I make changes to multiple files and save them at the same time.
Another example would be moving a type from one file to another.
Minimal repo
I encounter this in multiple situations. For example, https://github.com/unional/progress-str
To reproduce the issue, you need to run the test in watch mode (npm run watch in the repo above),
and then make some changes such as rename or move types.

Seeing this issue as well. It's really frustrating. I can even clear out a whole file that has types and it isn't picked up.

I stumble upon of similar issue. And I guess I have an explanation of what's going on.
As you may know TS type information only exists during development and removed upon compilation. Jest compiles files one by one and stores result in cache.
Now consider following example:

File1: type definitions
File2: imports File1

Run tests. All is OK. Jest will cache compiled File1 and File2.
Scenario 1:

Change File1 and break type (rename, change signature, etc.). What will happen?
File2: still the same, cached version is used. Therefore tests are green.

Scenario 2:

Now change File1 and File2. Save them both together.
File2: new, Jest will compile it.
File1: new, Jest will compile it. TS will pickup breaking change reporting an error.

Workaround: use --no-cache when running tests.

I am running into this problem also. Any updates?

hi @unional @aaw5017 @antonovicha @nathanmarks would you please help us to test the fix ? You can download tgz file here and install it. Remember to clear cache before you run your tests

Hi @ahnpnl , my current projects do no do type checks through jest anymore, because it slow me down unnecessary.
So my projects are not using ts-jest now. Since this will likely require bigger project to reproduce, I won't be able to help testing the fix at the moment. Thanks. 🌷

I also experienced this, I made a minimal repository with steps to reproduce:
https://github.com/kevinsimper/jest-ts-jest-import-error
Steps to reproduce:

run jest with watch $ npm test -- --watch
go into src/add.test.ts and edit the import from add1 to add2 in both import and where the function is used
see the error:

 FAIL  src/add.test.ts
 ● Test suite failed to run

 src/add.test.ts:1:10 - error TS2305: Module '"./add"' has no exported member 'add2'.

1 import { add2 } from "./add";

go into ./add and fix the function to be called add2.
see that the jest runner still say the same error
restart the runner and see it works now

I have been frustrated by this too. Would love to know if you find a solution.

At least I now know it is not a problem with my environment.

omg i just had this problem, arrives here after googling, saw you fixed it 5 hours ago: awesom

Nice, which version will contain this fix and when can you release it?

v27 :)

Not sure it is linked to this issue, but at my first jest --watch after clearing jest cache I receive the expected typescript errors of
TS2532: Object is possibly 'undefined'.
When saving a test file (without resolving any of the type errors), tests are run again and all TS2532: Object is possibly 'undefined'. errors disappear and tests are now all successful.
I need to relaunch the tests after yarn --clearCache for the type errors to appear again.
If this is not related I can create an issue about it.

@bidoubiwa are you using next tag ?

Unfortunately, I'm not able to see where the error comes from.
    tests/typed_search_tests.ts:266:13 - error TS2532: Object is possibly 'undefined'.

    266             response.hits[0]?._matchesInfo?.title[0]?.start === 6

I tried changing the tag to next (do you mean in the tsconfig.json?) but it did not change the problem. As soon as I refresh the tests this error disappears.

@bidoubiwa Without seeing the code it's difficult to figure out what could possible be undefined. In the line you posted it could be response.hits or response.hits[0]?._matchesInfo?.title, so try to use the optional chaining operator here too:
response.hits?.[0]?._matchesInfo?.title?.[0]?.start

Your error does sound a lot like the one from this issue. You're having a TypeScript error, but upon further runs the error is not shown anymore (despite still being present).
The reference to next refers to a previous version of ts-jest: https://www.npmjs.com/package/ts-jest/v/27.0.0-next.4

Hey! @MartinJohns. I thank you a lot for helping with this error, but this is not the issue I'm raising.
This error is disapears when I do not clear the cache of jest.

Run jest
Errors are raised and test fail
Run jest again without changing the code
No errors, all tests are successfull
Clear the jest cache jest --clearCache
Run jest again
Errors are raised and tests fail

Thanks a lot, MartinJohns, I'm not sure I understand your last sentence.
Does this mean that after the next release of ts-jest, errors will still be present without having to clear the cache between each test?

I'm also experiencing this issue with version 27.2.0
This doesn't only apply to types though. If I change a function signature in an imported file, the test doesn't pick up on that change until I kill the test watcher and re-run it

Also running into this issue with the most recent version of ts-jest (28.0.3)

Also running into this issue with the most recent version of ts-jest (28.0.3), please consider reopening this issue until it is fixed. Thanks a lot.

Running into the same issue as well.

I'm experiencing this issue in a fresh project with jest 29.3.1 and ts-jest 29.0.3. It's very frustrating, makes "watch" mode unusable :disappointed:

Also seeing the same issue.

Same issue here, very frustrating as this feature really makes TDD fluent...

ts-jest 29.0.5 here, same issue

Just noticed the same problem, ts-jest 29.0.5

Still happening on newest versions, do we have tests to ensure this specific issue is fixed? It feels like either we're not ensuring the right fix is occurring, or regressions are slipping through.

Same issue on 28.08


test3

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #10

PR #11

PR #12   👈

This stack of pull requests is managed by Graphite.


[DOC] Adding architecture documentation to explanations

Closes #11
Closes #27
Closes #28
Closes #29
Closes #30
Closes #31
This is still a work in progress.

ping @costrouc  - there are changes requested. Also, where are we up to with the new architecture diagrams?

@kcpevey I will mark your suggestions above as "resolved" as I plan to re-write everything, I will keep them in mind though.

@costrouc what is needed to move this PR forward? it has been in progress for a while and it would be great to add it to the docs ASAP

It was originally owned by @costrouc, then @viniciusdc took over. It definitely needs to be merged ASAP.

Based on what has been discussed so far and the reviews. We could avoid describing the diagrams in detail (no details at all for now) and refactor the page layout to show the images. We can then have another issue to update them at a later time. This way, we can move forward with this.
Currently, the missing thing on this is that we only added the images but did not explain where these resources are used or how they are used (a.ka Jupyterlab pods are initiated by a user trigger that spawns a Pod with the requested resources.... and is scaled down once idle)

It was originally owned by @costrouc, then @viniciusdc took over. It definitely needs to be merged ASAP.

Based on what has been discussed so far and the reviews. We could avoid describing the diagrams in detail (no details at all for now) and refactor the page layout to show the images. We can then have another issue to update them at a later time. This way, we can move forward with this.
Currently, the missing thing on this is that we only added the images but did not explain where these resources are used or how they are used (a.ka Jupyterlab pods are initiated by a user trigger that spawns a Pod with the requested resources.... and is scaled down once idle)

Self-review: I will remove the unused images from this PR as well as mention the source of one of the terraform images as it comes from their docs (thus needs citation)


Not able to set value for input text field with type=number

Using Watir-webdriver with Firefox. It's not allowing to set value for input textfield with type=number
Below is my html element
<input id="payment_amount_as_float" type="number" value="0" style="width:
200px;"step="any"name="payment[amount_as_float]"></input>

Output from my watir script :
irb(main):041:0> browser.text_field(:id,"payment_amount_as_float")
    => #<Watir::TextField:0x48127438 located=false selector={:id=>"payment_amount_as_float",
    :tag_name=>"input or textarea", :type=>"(any text type)"}>
irb(main):042:0> browser.text_field(:id,"payment_amount_as_float").set(200)
    => ""

As you can see, it is not setting the value to 200 and returns "". I tried with set("200"), value=(200), value=("200"), append("200"), append(200), but none of those worked

I'm having similar issues when not running headless.
browser.text_field(id: 'transfer_in_amount').set(amount)
# amount is 2000, but field gets value 200

However, if I set the amount twice, it sets the correct value the second time.
2.times { browser.text_field(id: 'transfer_in_amount').set(amount) }

Using Firefox 41.0.2 and watir-webdriver 0.9.1.
@jarib what's the best way to report this issue? Create a new one here or on Google Code?

Create a new one here and one of the current maintainers will take a look at it.


Error on Velocity Startup

http://prntscr.com/o52ppi
i use Velocity 1.0.0 release

See https://github.com/egg82/AntiVPN/issues/19 for more info on this, but basically we're waiting for Aikar to push ACF velocity to his private repo. Once that happens, the plugin will automagically work on its own without needing an update.


Not an issue but a newbie question

Very nice book. I bought it an hour ago.
Syntax of code for get_fitness(genes, target):  has stumped me.
what does
sum(1 for expected, actual in zip(target, genes) if expected == actual)
mean?
return 1 if for all {expected, all} tuples if one comes across a value of expected equaling actual Else do nothing?
Please bear with me for such silly question

I think I got my answer after conducting some simple tests. Let's close this issue (which it never really was) 🥇


Set radio button as selected by default

Hello,
I am saving the selected radio button in user defaults by the text of that button as string. How can we set the selected button by default according to what was saved in the user defaults?

@JumanaAlhaddad Hi Did you get solution?


⚠ PostgreSQL has degraded performance

In c10bb54, PostgreSQL (https://news.ycombinator.com) experienced degraded performance:

HTTP code: 200
Response time: 2545 ms

Resolved: PostgreSQL performance has improved in 6493a2e after 5 minutes.


UpdateDeveloper modified

removeDeveloper() call is not required any more.

@rupam-rai please look at https://github.com/apigee/edge-php-sdk/pull/74
Addressed the developer assignment issue

It looks like #74 handled this @giteshk @rupam-rai , but let me know if I am wrong and reopen.  Will close for now.


add /latest path to redirects config

Closes #190
Just added the /latest path which should be used to handle redirects to the current social media campaign's Medium blog post.

@andrewzulaybar LGTM :) See https://deploy-preview-191--ubclaunchpad.netlify.app/latest

Yay! Thanks for the quick review 🎉


Installation fails after 1.5.0-1 release

Not possible to install/upgrade cloudvision-python via pip since release 1.5.0-1.
Workaround:
pip install 'cloudvision!=1.5.0.post1'
debug-cloudvision# pipenv install cloudvision
Installing cloudvision...
Error:  An error occurred while installing cloudvision!
Error text: Collecting cloudvision
  Using cached cloudvision-1.5.0-1.tar.gz (151 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'

  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/private/var/folders/4y/hlz9dntn5_q1b6z_5zk93mj4lt2gx5/T/pip-install-9zdi21q2/cloudvision_6925c7e856a64ed59bd7f989bad802cd/setup.py", line 12, in <module>
          with open("requirements.txt", "r") as fh:
      FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

This is likely caused by a bug in cloudvision. Report this to its maintainers.
✘ Installation Failed

Thanks for opening the issue, I am currently investigating this. Will update when I can

I believe this has been resolved. pip install --upgrade cloudvision now works.
The requirements files were not being bundled in the source distribution due to an oversight, which will be addressed.
Please use the --no-cache-dir option if installation has been attempted and failed to force the download of 1.5.0-post3


Trouble starting services on boot in RancherOS v0.2.1

/opt/rancher/bin/start.sh doesn't seem to make it: vagrant up just stalls and I don't know what's going on.
/opt/rancher/bin/start.sh:
#!/bin/sh
nohup /opt/rancher/bin/do-start.sh >/var/log/start.log 2>&1 &

/opt/rancher/bin/do-start.sh:
#!/bin/sh
set -x -e
docker stop nginx && docker rm nginx && :
docker run -d --name=nginx -p=8080:80 nginx

Both start.sh and do-start.sh are executable.
OS appears to hang on after Running [7/13] cloud-init-pre:

If  /opt/rancher/bin/start.sh fails it shouldn't fail the boot, but  /opt/rancher/bin/start.sh is actually executed by the console container.  So in this situation the reason it isn't booting is not related to you script.  If cloud-init-pre is hung that means it can't talk to the cloud config data source.  In the Vagrant setup there is a file /var/lib/rancher/conf/user_config.yml.  If you delete that file, the boot will hang forever.  You have to also edit rancher.yml and remove the reference to it.  This is a bug and should be fixed.

I created #107 to track this issue.

The file is there. I didn't delete it, just added start.sh. To reproduce,
just add my start.sh and do-start.sh
On Thu, Mar 26, 2015, 19:46 Darren Shepherd<EMAIL_ADDRESS>wrote:

I created #107 https://github.com/rancherio/os/issues/107 to track this
issue.
—
Reply to this email directly or view it on GitHub
https://github.com/rancherio/os/issues/106#issuecomment-86546184.

@ibuildthecloud, actually, you are right: I just tried to reproduce this anew and it worked.
OK, this got the boot to hang (not forever, just for a very long time):
# rancherctl c get cloud_init.datasources
- file:/home/rancher/cloud-init.sh

cloud-init.sh being an executable script:
#!/bin/sh
set -x -e

mkdir -p /opt/rancher/bin

cat <<EOF >/opt/rancher/bin/start.sh
#!/bin/sh
nohup /opt/rancher/bin/do-start.sh >/var/log/start.log 2>&1 &
EOF

chmod +x /opt/rancher/bin/start.sh

cat <<EOF >/opt/rancher/bin/do-start.sh
#!/bin/sh
set -x -e
docker stop nginx && docker rm nginx && :
docker run -d --name=nginx -p=8080:80 nginx
EOF

chmod +x /opt/rancher/bin/do-start.sh

Hangs exactly the same way after this:
rancherctl c set cloud_init.datasources [file:/home/rancher/my_config.yml]

my_config.yml contains:
#cloud-config
write_files:
- path: /opt/rancher/bin/start.sh
  permissions: 0755
  owner: root
  content: |
    #!/bin/sh
    nohup /opt/rancher/bin/do-start.sh >/var/log/start.log 2>&1 &
- path: /opt/rancher/bin/do-start.sh
  permissions: 0755
  owner: root
  content: |
    #!/bin/sh
    set -x -e
    docker stop nginx && docker rm nginx && :
    docker run -d --name=nginx -p=8080:80 nginx

@imikushin Can you put the file into /var/lib/rancher/conf?  I know this is confusing, but cloud-init doesn't have access to /home.

@imikushin I have created #108 for this, cloud-init should have access, but it is not setup that way.

Thanks, @ibuildthecloud, placing the file into /var/lib/rancher/conf helped!
Now, there's a problem with YAML cloud-config: write_file instruction doesn't seem to work. But the other option (cloud-init.sh) does run all right.

No write files, should work.  let me try your cloud config and try to reproduce.

@imikushin Closing this as logic is in console. Let's discuss if it's still not working.


Win32 autocompletion during open generate wrong file path

Tab completed file path during open leads to fail for open
> open .config\\micro\\settings.json => open .configmicrosettings.json: The system cannot find the file specified.
> open .config/micro/settings.json works but without TAB completition
Specifications

micro -version
Version: 1.3.4
Commit hash: 5fc8f84
Compiled on November 24, 2017

Terminal: cmd.exe
MS Win 10

on windows 10 autocomplete puts  \\ also, but micro can not open file specified that way
if I replace manualy \\ put by autocompletter with / mico is able to open file


Luokat jaettu paketteihin

Codecov Report

Merging #38 into dev will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##              dev      #38   +/-   ##
=======================================
  Coverage   13.03%   13.03%
=======================================
  Files          17       17
  Lines         629      629
  Branches       59       59
=======================================
  Hits           82       82
  Misses        544      544
  Partials        3        3

Impacted Files
Coverage Δ

...c/main/java/hifian/hintahaukka/Domain/Product.java
0% <ø> (ø)

...a/hifian/hintahaukka/GUI/SplashScreenActivity.java
0% <ø> (ø)

.../java/hifian/hintahaukka/Service/StoreManager.java
87.8% <ø> (ø)

...va/hifian/hintahaukka/Service/EnterPriceUtils.java
88.88% <ø> (ø)

...src/main/java/hifian/hintahaukka/Domain/Store.java
68.42% <ø> (ø)

...java/hifian/hintahaukka/Service/PriceListItem.java
0% <ø> (ø)

...ava/hifian/hintahaukka/GUI/ListPricesFragment.java
0% <ø> (ø)

...n/java/hifian/hintahaukka/Service/GpsActivity.java
0% <ø> (ø)

...va/hifian/hintahaukka/Service/HttpServiceMock.java
0% <ø> (ø)

...n/java/hifian/hintahaukka/Service/HttpService.java
0% <ø> (ø)

... and 7 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c11288...f06133e. Read the comment docs.


Appveyor test

This PR only exists to test the appveyor logic. Please ignore.

[Current coverage][cc-pull] is 87.46%

Merging [#1883][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master      #1883   diff @@
==========================================
  Files           292        292
  Lines         51981      51981
  Methods           0          0
  Messages          0          0
  Branches       5368       5368
==========================================
  Hits          45461      45461
  Misses         5603       5603
  Partials        917        917

Powered by Codecov. Last updated by [1c6d133...ce2fe49][cc-compare]
[cc-base-branch]: https://codecov.io/gh/numba/numba/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/numba/numba/compare/1c6d1338da4635646ca769f24802fff442922b98...ce2fe4981712c216faf552c9a15770301b1d2ef6
[cc-pull]: https://codecov.io/gh/numba/numba/pull/1883?src=pr


What does ddd stands for in this repository?

I would like to understand what does ddd stands for in this repository?
It is a task of the train.sh or test.sh files and I was wondering what it stands for.

I found the answer to my question. It is a nomenclature introduced in the repository CenterNet that is used in this repository.
ddd stands for 3D bounding box detection
More details in this issue:
https://github.com/xingyizhou/CenterNet/issues/478


Use of X-Correlation-Id of CT as Idempotency-Key for  Adyen API call ?

As suggested by Adyen to avoid duplicate request on failure, Idempotency-Key (a unique request id usually uuid) should sent in the header in each API call from extension.
Why not use the CT event X-Correlation-Id  header as  Idempotency-Key  for each API call in extension ?
This helps to avoid duplicate refunds.
Please refer to:
https://docs.adyen.com/development-resources/api-idempotency
https://docs.commercetools.com/api/general-concepts#correlation-id

Hi @milindsingh
Thank you for the suggestion. I will take this topic and discuss internally with the team. I will get back to you once we have an agreement how to approach this.

Hi @milindsingh Did extension produced a duplicate request or the issue is hypothetical? In case you hit a real case scenario would you please describe how it can be reproduced?

Hi @milindsingh - is it still a topic or the issue can be closed?

This can happen when we do multiple refund.
First refund failure to receive response due network failure or adyen fails to return reponse but got created.
Second refund created, causes all intial state refund to be sent adyen again.
Notification can be delayed.
So finally we have 3 refunds.

Thanks for the input. Would it be an option for you to include Idempotency-Key in the commercetools payment transactions you add as a custom field? In this case you would be responsible for the uniqueness of the Idempotency-Key.

Yes that is something I was planning to do. I have made some changes to my fork and will be testing this week

Hi @milindsingh
We added idempotency key in these releases: https://github.com/commercetools/commercetools-adyen-integration/releases/tag/v9.13.0, https://github.com/commercetools/commercetools-adyen-integration/releases/tag/v9.11.0. Therefore I'm closing this issue. If you have further questions, feel free to reopen or create another issue.


Show description with an offer to define more specific selector when several elements are found

@MarinaRukavitsyna How you imagine that?


Prepare merge spring boot 3 to main

Description
We plan to stop releasing Spring Cloud Azure 4.x and only release Spring Cloud Azure 5.x in the future, so we will only maintain the main branch for Spring Boot 3 in the future.
Changelogs:

Merge branch feature/spring-boot-3 to main branch, only keep the source code from sdk/spring directory same with feature/spring-boot-3; also keep the monitor modules.
Spring models will pick up the external dependency versions of Spring Boot 3 managed, and tagged with a fixed prefix springboot3_ in eng/versioning/external_dependencies.txt; except for monitor 2 modules;
Non Spring models will still pick up the external dependency of Spring Boot 2 managed, their dependency versions will be decoupled from the Spring module dependencies.
Remove cosmos test emulator with java 8.
Add java 17 and more test agents for Spring combability test.

Ref test PRs:

https://github.com/Azure/azure-sdk-for-java/pull/41026
https://github.com/Azure/azure-sdk-for-java/pull/40700

All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - spring - tests

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

Hi @JimSuplizio, @benbp, @hallipr, @weshaggard, can any of you please approve this PR? Thanks in advance!

/azp run java - spring - tests


Add videakid as an alias for videa

It seems that videakid.hu is just an alternative domain for videa.hu
serving up the same videos, supporting the same download procedure.
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[ ] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.

@dstftw - Thank you for the quick review! I made the requested changes.


In candidate detail page, add signs list, add reward list

We should add 2 lists:

[x] list of signs of candidate
[ ] list of reward of candidate

fix #152


Documentation - Make F1 doc about current options

and then refer to the general documentation with some kind of link.
eg so when users press F1 they see the docs about what their current endpoint is configured as. Its like the cmd hover thing we have today.
Its like this screenshot
https://github.com/davsclaus/camel-idea-plugin/blob/master/img/early6.png
And then if we have some kind of link in top so the user can see the general component docs.
As the cmd however thingy is obscure and not many people know it exists.

I am not sure how to make an inline link in IDEA docs so we can link to the complete documentation.


Context.Database.EnsureDeleted(); error -> The convention invocations have reached the recursion limit. This is likely an issue in EF Core, please report it.

From VS Feedback:
after calling:
context.Database.EnsureDeleted();
app break on error ->
"The convention invocations have reached the recursion limit. This is likely an issue in EF Core, please report it."

EF Team Triage: This issue is lacking enough information for us to be able to effectively triage it. In particular, it is missing the following information requested in the new issue template. Can you please provide this information?

Steps to reproduce

Ideally include a complete code listing that we can run to reproduce the issue.
Alternatively, you can provide a project/solution that we can run.
BTW we're not just doing this to be mean :smile:... we get a lot traffic on this project and it takes time to attempt to reproduce an issue based on fragments of information. In addition, our attempt is often unsuccessful as the exact conditions required to hit the issue are often not explicitly included in the code provided. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we ask that folks give us a self-contained way to reproduce an issue.
For a guide on submitting good bug reports, read Painless Bug Tracking.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


An odd layout shows when selecting an access policy with long id on SAS dialog

Storage Explorer Version: 1.8.0_20190422.2
Platform/OS: Linux Ubuntu/macOS High Sierra/Windows 10
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Expand one normal account -> Blob Containers.
Right click one blob container then select 'Manage Access...'.
Add an access policy with long id like 'ンライン ストレージなどのサービスが含まれるので、さらに快適にデバイスや アプリ'.
Right click the same blob container then select 'Get Shared Access Signature...'.
On the opened SAS dialog, select the added policy then check the layout.

Expect Experience:
The layout shows well.
Actual Experience:
Show an odd layout.

Won't fix.


should there are way for non adding pro components

Description of the bug
Right now there is hack where hilla.jar includes a vaadin-core-versions.json with all (core and pro) components.
There should be vaadin-versions.json and vaadin-core-versions.json instead, probably having two artifacts hilla and hilla-core like in flow
Take a look to this block

Looks like a missing feature to me.


Fix the elasticity solver to handle multiple Dirichlet boundary conditions

The current implementation of ElasticitySolver will not save the eliminated stiffness entries for multiple essential boundary conditions. We want to make this elasticity code look like this thermal code to fix it.

Wait, this is the dynamic operator. This isn't a bug.


About inference.py

I run the inference.py and have an error:
Traceback (most recent call last):
File "inference.py", line 149, in
main()
File "inference.py", line 127, in main
model = VoxelNet.load_from_checkpoint(args.model)
File "/home/mxp/anaconda3/lib/python3.7/site-packages/pytorch_lightning/core/saving.py", line 156, in load_from_checkpoint
model = cls._load_model_state(checkpoint, strict=strict, kwargs)
File "/home/mxp/anaconda3/lib/python3.7/site-packages/pytorch_lightning/core/saving.py", line 198, in _load_model_state
model = cls(_cls_kwargs)
File "/home/mxp/atlas/Atlas-master/atlas/model.py", line 93, in init
self.hparams = hparams
File "/home/mxp/anaconda3/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1178, in setattr
object.setattr(self, name, value)
AttributeError: can't set attribute

parameters are not passed in correctly

Was facing the same issue. Replacing self.hparams = hparams with self.save_hyperparameters(hparams) solved it https://github.com/magicleap/Atlas/blob/bee3ddbdb0935cf9aa9fc810e829115c6ab74dc5/atlas/model.py#L93


correct Network protection config settings

Learn Build status updates of commit ae8751b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/defender-endpoint/android-configure.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 47bbee5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/defender-endpoint/android-configure.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit e8cb632:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/defender-endpoint/android-configure.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Update in config.py to solve error with get_issue_infos()

Updated API_ISSUE_URL, force sorting of output image files before renaming and update of AES syntax (3.8.10)

Fix for #21


Builds in readthedocs fail since updates in plot example

I've modified the example plot.md to consider a larger database, as detailed in #8.
For some reason, builds in readthedocs are failing: https://readthedocs.org/projects/jupysql/builds/
I created a new branch with diferent table sizes to verify if it was the problem and also tried with a bigger timeout from jupyterbook config. In all cases builds failed, so we need to verify why this is happening and build the new docs with the updated examples.

We can run builds fro other branches for testing, onces it is solved it must be changed back to master in readthedocs's config.


Fix typo in nextjs-on-wsl.md

parody -> parity

@ynx0 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[Bug]: Dependency resolution is happening when installing latest version of apache-beam[gcp]

What happened?
Installing apache-beam into a clean environment now shows following logs:
 pip install --no-cache-dir --pre apache-beam[gcp]==2.56.0
...

Collecting grpcio-status>=1.33.2 (from google-cloud-pubsub<3,>=2.1.0->apache-beam[gcp]==2.56.0)
  Downloading grpcio_status-1.64.1-py3-none-any.whl.metadata (1.1 kB)
  Downloading grpcio_status-1.64.0-py3-none-any.whl.metadata (1.1 kB)
  Downloading grpcio_status-1.64.0rc1-py3-none-any.whl.metadata (1.1 kB)
  Downloading grpcio_status-1.63.0-py3-none-any.whl.metadata (1.1 kB)
  Downloading grpcio_status-1.63.0rc2-py3-none-any.whl.metadata (1.1 kB)
  Downloading grpcio_status-1.63.0rc1-py3-none-any.whl.metadata (1.1 kB)

That means, when analyzing dependency ranges, pip cannot take the latest allowed version for each dependency, and has to do dependency resolution. This is suboptimal and can result in failed installations (https://s.apache.org/beam-python-dependencies-pm). We should check what combination of packages requires the resolution and work with maintainers of Beam dependencies to remove the need for resolution if possible.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

* grpcio-status==1.66.1
 - protobuf [required: >=5.26.1,<6.0dev, installed: 4.25.5]

Should be fixed  by upgrading Beam to 2.53.0 or mitigated by
adding a bound "grpcio-status<1.63.0"


[WIP] User Validations

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@ergonzalezpmp Take a look at https://github.com/Code-for-Miami/lobbster/blob/master/CONTRIBUTING.md#updating-the-code-open-a-pull-request
Specifically the section on testing. Take a look and see if there is anything you need to change to conform.

@ergonzalezpmp How's this going?


extensions/common/redis coverage

Hello,
The Envoy project has recently started collecting per-extension coverage. You have been tagged with this issue as you are a co-owner of an extension, extensions/common/redis, which is below the 96.6 percent coverage mark.
Could you please take a look at coverage results (https://storage.googleapis.com/envoy-postsubmit/master/coverage/index.html) and add more tests when you get a chance? Once this is done you should be able to remove your extension from the exempt extensions in test/per_file_coverage.sh
Thanks!

Hmmm, I think this was mis-tagged.  Looks like @HenryYYang co-owns
//extensions/clusters/redis
//extensions/common/redis
but coverage outliers are
"source/extensions/filters/network/common/redis:96.2"
"source/extensions/health_checkers/redis:95.9"
If the outliers are still in your domain it'd be awesome if you'd be willing to take a look but if they're not just let me know and I'll unassign.  Sorry for the noise!


Added my school.

I have added my school COMSATS University Islamabad, Sahiwal Campus. Looking forward to your response and getting free license.

@Awais-019 First stage of verification passed, official domain is sahiwal.comsats.edu.pk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://sahiwal.comsats.edu.pk/IT_Forms/Student_Email_ID_Request_Form_converted.pdf


Feature reports junit

Coverage decreased (-2.8%) to 97.222% when pulling a6c80dcfa25a0df2b84e731a3ed0ff11f4adbdf4 on feature-reports-junit into b85557e35be1711c4b3b97d5d64eff8aa25e4670 on master.

Coverage remained the same at 100.0% when pulling 8ebd178d8bdf10aac5b66541fcaba64362a5142f on feature-reports-junit into b85557e35be1711c4b3b97d5d64eff8aa25e4670 on master.


cpp appears to trip up hlint

https://github.com/kazu-yamamoto/logger/blob/master/monad-logger/Control/Monad/Logger.hs

I think this is a dupe of #53. @malcolmwallace: did we get anywhere with that?

I think it's fixed with cpphs 1.20.1 - see my response at https://github.com/ndmitchell/hlint/issues/53#issuecomment-193265800

@bitemyapp - if it does appear that cpphs 1.20.1 fixes it, I'll adjust the cabal bounds.

OK, I've added the minbound. @bitemyapp - please shout if cpphs doesn't fix it. I'll be making a new release in an hour or so.


SemVer 2 version number breaks helm package for internal builds using commit short SHA version

At some point between Helm version 3.3.1 and 3.5.0, the helm package command started erroring when packaging a chart with a non-SemVer 2 version number in Chart.yaml. Defining this in the Chart.yaml file was a bit of a workaround for helm package --version x.y.z which has needed a SemVer 2 version number for a while.
This change has consequently broken our internal build pipelines, which use git commit short SHA's as version numbers. We do not increase a chart's SemVer for every change; this is done when we manually decide to make a release. It does not make sense for us to take the latest released version and add the commit SHA as pre-release or build information since that does not conform to SemVer. Equally, it would be inappropriate to arbitrarily decide to bump a patch, minor or major version just so that we could use pre-release/build information.
Why is the version number restricted to SemVer? It is a well known versioning scheme but by no means are any others invalid: CalVer is popular and I'm sure we're not the only teams using git short SHA's as unique internal versions either.
Can the SemVer 2 version numbering requirement be relaxed to allow other versioning schemes?

I see from https://github.com/helm/helm/issues/9102 that it was suggested to use pre-release metadata. This means having to decide on a next version before even the first commit is made.
If Helm's internals are so tied to SemVer that this is not going to change, what are the alternatives?

I see from https://github.com/helm/helm/issues/9102 that it was suggested to use pre-release metadata. This means having to decide on a next version before even the first commit is made.
If Helm's internals are so tied to SemVer that this is not going to change, what are the alternatives?

This means having to decide on a next version before even the first commit is made.

Is there any issue using the next patch version as the next version, prior to the version being bumped?
Does something like this work for you?
$ helm create mychart
Creating mychart
$ CHART_PATH="./mychart/"
$ NEXT_PATCH_VERSION="$(cat ${CHART_PATH}/Chart.yaml | grep ^version: | cut -d ' ' -f 2 | awk -F. '{print $1 "." $2 "." $3+1}')"
$ GIT_SHORT_COMMIT="$(git rev-parse --short HEAD)"
$ helm package "${CHART_PATH}" --version "${NEXT_PATCH_VERSION}-rc-${GIT_SHORT_COMMIT}"
Successfully packaged chart and saved it to: /myrepo/mychart-0.1.1-rc-ab12382d.tgz

This means having to decide on a next version before even the first commit is made.

Is there any issue using the next patch version as the next version, prior to the version being bumped?
Does something like this work for you?
$ helm create mychart
Creating mychart
$ CHART_PATH="./mychart/"
$ NEXT_PATCH_VERSION="$(cat ${CHART_PATH}/Chart.yaml | grep ^version: | cut -d ' ' -f 2 | awk -F. '{print $1 "." $2 "." $3+1}')"
$ GIT_SHORT_COMMIT="$(git rev-parse --short HEAD)"
$ helm package "${CHART_PATH}" --version "${NEXT_PATCH_VERSION}-rc-${GIT_SHORT_COMMIT}"
Successfully packaged chart and saved it to: /myrepo/mychart-0.1.1-rc-ab12382d.tgz

That could work, thanks for the suggestion. I was thinking I could actually just use 0.0.0-${GIT_SHORT_COMMIT}, but that's a reasonable approach too.

That could work, thanks for the suggestion. I was thinking I could actually just use 0.0.0-${GIT_SHORT_COMMIT}, but that's a reasonable approach too.


Adding Conditional Tybalt Model

Major change is adding new class cTybalt - which implements a cVAE. The implementation is modified from a blog post.
Other changes include an increased abstraction step (class VAE) which now inherits from BaseModel. Both Tybalt and cTybalt now inherit from VAE. These base models are moved to a new file (tybalt/utils/base.py), which is imported by tybalt/models.py.

Thanks for comments @danich1 - I believe I addressed them in the most recent commits. Thanks!

This might be my lack of Python/Keras knowledge talking, but it looks to me like the only difference between Tybalt and cTybalt is a few lines adding the conditional vector -- is there a reason one would need to write "new" encoder/decoder functions @gwaygenomics? Thinking about this from a code repetition point of view

but it looks to me like the only difference between Tybalt and cTybalt is a few lines adding the conditional vector --  is there a reason one would need to write "new" encoder/decoder functions?

Yeah, I was weighing pros/cons here too. The differences are fairly small between the two models - the inputs and input/output dimensions are different and some of the layer connections are slightly different as well. While I could abstract some of this away and thus reduce the number of lines, I think it would come at a cost of interpretability. Having each autoencoder model build their own graph makes things easier to read I think.


remove update_listen_.py

There are nonchanhes in this PR. Can you double check your commits?

*changes

I am trying to delete the file update_listen_.py which is empty but should not be there.