Number of posts found: 0

Hi,
Thanks for this plugin. I have added to my theme but getting some issue. Every time I search it return Number of posts found: 0
here is a link to my blog
http://ghost.xvelopers.com/voltov/

Got it fixed .

I have the same bug. How to fix it? @naumanahmed19

@naumanahmed19 I've been having the same issue. It would be great if you could explain how you fixed it, or at least point others towards a solution. Thank you in advance.

Hi, I'm having the same issue, has anyone found a solution that you could share ?
Thanks a lot

Hi there!
Could you give me a link to your blog?
Thanks
Sent from BlueMailhttp://www.bluemail.me/r
On May 19, 2016, at 19:19, steven-tib <notifications<EMAIL_ADDRESS>wrote:
Hi, I'm having the same issue, has anyone found a solution that you could share ?
Thanks a lot
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com/jamalneufeld/ghostHunter/issues/11#issuecomment-220392714

I have same issue! http://twelvepurplepills.com/ thank you

@Windyo sorry I don't have deployed anything yet, just working locally. I will send you a link later cause I can't deploy right now for other reasons.
Maybe studying the case of @zebheone will help me as well.
Thank you

@steven-tib okay, let me know how it goes.
@zebheone : twelvepurplepills seems to work for me, but you're on the old version of Ghosthunter. I tried running a simple API call :
	        $.get(ghost.url.api('posts', {limit: "all", include: "tags"})).done(function(data){
	        	searchData = data.posts;
            console.log(searchData);
          })

and I got an exception "ghost is not defined", which means that you probably haven't activated the ghost public API through the admin panel > Labs.
Oliver-flipper is not running at the moment, so I can't test it.

@Windyo I had tried your test code and found an interesting thing, that on the error.hbs template the public api doesn't work )

@Windyo ty for helping, the production blog is, as you mention, working. Now I got the dev env online I hope you can check it, I will try to keep it online for 8 hour. Public api on the dev env is active and I got the last ghostHunter code form git.

Hi @Albi,
Following the link you posted for the dev env still returns an http 404.
Let me know where I can access it so I can troubleshoot this.
Kind regards,

@Windyo Hi! it's up and running! still gives you 404? http://oliver-flipper.codio.io:3000/

Works on mobile but not on my laptop fr some reason. I'll check on another connectio' in about 30 minutes or so.

@Windyo thank you again! I think it's your connection, I can't connect to my blog dev env on my job network because of port blocking (but I don't get 404, website does not load). I can connect on mobile and home network

@zebheone, I'm getting an error related to Jquery for some reason.
Could you try another CDN, or Zepto ? Thanks

@Windyo Hi in my default.hbs I got
<script type="text/javascript">
  if (typeof jQuery == 'undefined') {
    document.write('<script type="text/javascript" src="http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.7.1.min.js"></'+'script>');
  }
    </script>

I downloaded zepto and changed the code to

but nothing is working

@zebheone Yeah I tested with Zepto, that didn't change much, hence why I struck that part out.
In any case can you check if you specified to correct URL in your config.js file ? It probably doesn't specify the port.

@Windyo wow now works! so stupid me! so I guess it will work in production! thanks for your time and help

@zebheone glad to help. Closing this issue again.
@steven-tib let me know how it all works out.

Hi, I'm having a similar issue to this - the search function worked previously when it was on v0.4.0 when I first added it but now it doesn't return any results. I'm getting ghostHunter: init - so it seems to be partially working, also there are no JS errors in the console.
Any help would be appreciated please!


Simplify setup location

Ref #14
Simplify the location by creating the repository in the workspace directory directly. Could be updated to default to the current directory instead of ~/workspace
Also includes updating the error message to say which folder is needed but doesn't exist in order to be a bit more helpful.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.immersion-rops seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Matching changes will need to be made in the https://github.com/reactiveops/pentagon-workstation project. @sairez @robwar @tizzythegrey  as Daas team members who probably deal with the most infrastructure repositories, is this change helpful, neutral or harmful?
TL;DR;
~/workspace/projects//-infrastructure -> ~/workspace//-infrastructure

so ~/workspace/project/<project_name>/<project_name>-infrastructure to ~/workspace/<project_name>/<project_name>-infrastructure works fine for me.
~/workspace/project/<project_name>/<project_name>-infrastructure to ~/workspace/<project_name>-infrastructure is less than ideal, because tend to also keep application repos under the <project_name> directory alongside the infrastructure repo.

https://github.com/reactiveops/pentagon/blob/1bcc1e1e1b49fd5d9f01d2293d9674558e1b2e4c/lib/pentagon/config/local/ansible.cfg-default.jinja#L3 for ansible using ../repo as @sairez mentions
I don't know that there is a reason that we need to change the workstation layout at this point. The change in Pentagon just assumes less about your layout when it starts a project. If someone wants the previous behavior start-project needs to be run with --working-directory=~/workspace/projects/$client

There are several references to the project directory in the pentagon-workstation repo that will probably throw errors and add unexpected behavior. Its not a blocker, but it will be an annoyance until its fixed. https://github.com/reactiveops/pentagon-workstation/blob/master/files/pentagon-helpers.sh#L3
Also, the pentagon workstation hooks directory is in the ~/workspace directory. I see that as an aesthetic annoyance. It could probably be hidden.

Ah right, hooks.
The layout for pentagon-workstation seems to make sense then and those values in pentagon-workstation would remain the same.

Closes #26

Where did we land on this? @philipcristiano your last comment indicates that maybe the change isn't necessary?
I'm currently looking at how to update this to make it friendlier to the open source community doing away with the project directory (as you have done here), have working-directory default to ./
The rest it kind of specific to the way we use our workstation setup and we can use the PENTAGON-workspace-directory environment variable, set in reactiveops/pentagon-workstation to direct project creation to~/workspace/projects/ or ~/workspace depending on what you were thinking above.

+1 on moving to ./. I don't think any changes for the workstation setup are necessary.
Trying to emulate the current setup with this change is a little more challenging if we still wanted per-client projects folders. On the DaaS side, I think they rarely create new projects, mostly clone existing ones. So even if this option changes, the procedures on the DaaS side are unlikely to change.

Agreed on all counts. I'll PR that change into this branch later today.

Merged in changes from #50 by @ejether to use the current working directory.


Micrpython libaries are referenced

Hi I tried to run the driver and ran into the issue that it seems to reference the framebuf library from Micropython.
Not all circuitpython builds have that library available (mine definitely not) hence I am getting an error when I try to use your library. There seems to be some replacement for the framebuf library in the circuitpython library bundle: adafruit_framebuf.mpy

Same problem.


[TF 2.2.0] tf.io.decode_image caught CUDA_ERROR_NOT_INITIALIZED: initialization error when use_multiprocessing=True

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below):
Python version: 3.6.9
GCC/Compiler version (if compiling from source): 8.4.0
CUDA/cuDNN version: 10.1/7.6.5
GPU model and memory: 6GB

I try to decode a dataset in *.tfrecord type using tf.io.decode_image
def get_item(type, index):
    if type == 'trainval':
        item = images_trainval[index]
    else:
        item = images_val[index]

    image = item['image/encoded']
    image = tf.io.decode_image(image, 3)
    image = image.numpy()

    mask = item['image/segmentation/class/encoded']
    mask = tf.io.decode_image(mask, 1)
    mask = mask.numpy()
    mask = mask.reshape(mask.shape[:2])

    return image, mask

class DLDataset(Dataset):
    def __init__(self, split, dataset_dir):
        self.split = split

        self.transformer = data_transforms[split]

    def __getitem__(self, i):
        image, mask = get_item(self.split, i)

        image, mask = safe_crop(image, mask, size=512)
        image = transforms.ToPILImage()(image.copy().astype(np.uint8))
        image = self.transformer(image)

        mask = torch.from_numpy(mask)

        return image, mask

    def __len__(self):
        return get_len(self.split)

And it caught error:
...
2020-07-21 08:04:06.203528: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203533: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203532: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203538: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203537: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203547: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203559: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203561: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203556: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203564: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203568: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203572: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203571: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203568: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203578: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203577: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203585: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
2020-07-21 08:04:06.203585: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_NOT_INITIALIZED: initialization error
...

The error seems to be infinities. I had to press Ctrl + C to stop it.
But, when I try a clearly function (tf.io.decode_jpeg and tf.io.decode_png instead of tf.io.decode_image)
def get_item(type, index):
    if type == 'trainval':
        item = images_trainval[index]
    else:
        item = images_val[index]

    image = item['image/encoded']
    image = tf.io.decode_jpeg(image, 3)
    image = image.numpy()

    mask = item['image/segmentation/class/encoded']
    mask = tf.io.decode_png(mask, 1)
    mask = mask.numpy()
    mask = mask.reshape(mask.shape[:2])

    return image, mask

It work perfectly.
I noticed this error occurs when use workers > 1 and use_multiprocessing = True in model fit. If i don't use multi workers, It will work.

@vietnamican
Looks like code is incomplete.Request you to share colab link or simple standalone code with supporting files to reproduce the issue in our environment.It helps us in localizing the issue faster.Thanks!

@ravikyram. This is the simply version in colab:
https://colab.research.google.com/drive/1tt3DmJ7CPQXklKFhtPOl7bF8mBVff1ov?usp=sharing

I have tried in colab with TF version 2.2,nightly version(2.4.0-dev20200726).Please, find the gist here.You are also seeing the same behavior?.Thanks!

Look like tf.io.decode_image and torch.utils.data.Dataset is not compatible. I do not know where the error occurred, it maybe in tensorflow or it may be in pytorch. But now we can still handle it by using altenative function to decode image from TFRecord.
Are you going to investigate it?

@vietnamican Were you able to find the cause of the error?


get sample files from public repository

Sample files are not available anymore from https://genomics-solutions-shared-assets.s3-us-west-2.amazonaws.com
Copy is  taken from public repository
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Maybe.. needs an modification for R2 file in below.
ftp://ftp-trace.ncbi.nih.gov/ReferenceSamples/giab/data/NA12878/Garvan_NA12878_HG001_HiSeq_Exome/NIST7035_TAAGGCGA_L001_R2_001.fastq.gz


SW-Indexer should manage the 856 tag generation

Move 856 tag generation to indexer so that the tag will be regenerated for updates that might affect the contents of the 856.
in searchworks indexer, if there is a catkey, call the 856 web service

dor-services 856 method will need to move to PURL

Lynn's ticket: We also have to figure out how to tie the addition or removal of a catkey with rerunning the release workflow or perhaps just invoking the 856 logic. Perhaps a catkey management blue button?

Original JIRA ticket https://jirasul.stanford.edu/jira/browse/JUMBO-37

Call the marc record service if the object has either a current or previous catkey


Webpack support for google-auth-library

Problem Statement
Hi,
We are trying to setup frontend and backend service communication through
https://cloud.google.com/run/docs/tutorials/secure-services#shipping-frontend.
In frontend service, we use webpack for transpiling our code.
When we try to use google-auth-library with webpack bundle we are receiving the below error
ERROR in ./node_modules/google-auth-library/build/src/auth/googleauth.js 17:24-48
Module not found: Error: Can't resolve 'child_process' in '/workspace/node_modules/google-auth-library/build/src/auth'

ERROR in ./node_modules/google-auth-library/build/src/auth/googleauth.js 18:11-24
Module not found: Error: Can't resolve 'fs' in '/workspace/node_modules/google-auth-library/build/src/auth'

ERROR in ./node_modules/google-auth-library/build/src/auth/googleauth.js 20:11-24
Module not found: Error: Can't resolve 'os' in '/workspace/node_modules/google-auth-library/build/src/auth'

same error for stream, crypto, fs, assert, tls packages.

Please let us know how can we use OAuth Token-based communication with frontend cloud run service (uses webpack)  and backend cloud run service.
Environment details

OS: Windows
Node.js version: 14.15.0
google-auth-library version: 6.1.3

Steps to reproduce

Setup frontend service with webpack (https://cloud.google.com/run/docs/tutorials/secure-services#shipping-frontend)

Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!

Hi @sofisl ,
Can you please look into this and provide us a solution?
Thanks

@beingminimal our client libraries, at this time, do not fully support usage in a frontend context. We make an effort to make this possible, but we don't run integration tests against webpack, nor do we provide many samples for running our libraries in the browser.
Having said this, we do make an effort to make our libraries function with Webpack when possible. The problem you're bumping into here is that our library requires the Node.js modules child_process, fs, and os. You can eliminate these errors by creating a webpack config that replaces these with alternate resolutions:
https://webpack.js.org/configuration/resolve/
You should be able to make each of these modules resolve false, and in turn your project should start building.


Allow mitmweb to be embedded

Is your feature request related to a problem? Please describe.
I'm planing to integrate mitmweb into the smarthome system Home Assistant. For that I run it inside a docker container which gets all ports correctly and let mitmweb start as usual.
For a full integration it should be displayed inside the UI of Home Assistant as a panel. This is currently not possible since the X-FRAME-OPTION header is set to DENY.
Describe the solution you'd like
The direct solution would be configurable flag for the X-FRAME-OPTION header.
Describe alternatives you've considered
Add an option to set own headers for the mitmweb application.
Additional context
Screenshot how it looks right now.

I think you can easily work around this by running a reverse proxy in front of mitmweb which strips the x-frame-option header.
Such an option would only cover a very specific corner case but introduce 1) complexity and 2) a potential security issue.


Adding GA4GH 0.5.1 converter for reads.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1276/
Test PASSed.

Closing in favor of moving over to Mango.


Add declaritive pstn handlers

What

Adds the following handlers to the Declarative Calling API
Why

Allows for these functions to be used with the calling stateful client.

Follows up on this issue https://skype.visualstudio.com/SPOOL/_workitems/edit/2865531
How Tested

Built and ran samples to validate changes didn't break existing functionality, will test with PSTN POC to see if new functionality works.

@dmceachernmsft I would recommend pointing this branch to main and pointing CallingStatefulHandlersUpdatePSTN to it.
Since this is an independent branch but CallingStatefulHandlersUpdatePSTN is dependent on it. :)
That allows us to merge it in to main and keep CallingStatefulHandlersUpdatePSTN minimal.
Also, I would recommend adding unit tests for the new context functions you have added in this branch.


FCM Token Nil Error code 1003

Environment

Xcode version: 9.4.1
Firebase SDK version: 5.4.0
Firebase Component: Messaging
Component version: 3.0.3

Problem
I keep receiving a 1003 Error and always get nil when trying to get the FCM token. I assume that I've setup my APNs correctly and I'm using the correct GoogleService file since I was able to authenticated via Phone Number without seeing the recaptcha.
Also, none of the delegate's functions get called.
I tried using messaging.retrieveFCMToken(forSenderID:)  and it provided me the fcm token. I used the token I received from the handler to send a message using Firebase Console and I didn't receive anything. However, I tried using another service (PushTry) using the Server Key and the FCM token and I got the notification.
Important: My Application setup separates my Firebase dependencies in another Cocoa Touch framework which might be the cause of the problem?
Steps to reproduce:
Follow the steps in the guide:

Configure the Firebase App
Register for remote notificaitons
Set the messaging delegate
Add a listener for the Instance ID

Relevant Code:
InstanceID.instanceID().instanceID { (result, error) in
                if let error = error {
                    print("Error fetching remote instance ID: \(error)")
                } else if let result = result {
                    print("FCM Token: \(result.token)")
                }

or
Messaging.messaging().fcmToken

However, this one returns an FCM Token
Messaging.messaging().retrieveFCMToken(forSenderID:)

Error 1003 is a upstream error when you try to send a upstream message with empty to address.
https://github.com/firebase/firebase-ios-sdk/blob/master/Firebase/Messaging/NSError%2BFIRMessaging.h#L45
Can you send me your debug log so I can take a look?

Closing for now. Will reopen with a log or more info.


Wrap traverseArrayImpl IIFE in parentheses

Just wondering, since it's not clear to me - what do we gain by doing this?

👍 The gain here is in readibility by conforming to a very common syntactic pattern.  This is of increasing aid the longer a function's implementation is as it can be easy to miss the () on the very last line.

Right, makes sense, thanks. I think we should hold off merging until #48 is resolved though.

Thanks!


Add to_ieee754_32 scalar function for velox

Resolves #4425

@majetideepak - Kindly review this pull request. Thanks.

@aditi-pandit - Kindly review the pull request. Thanks.

@Krishna-Prasad-P-V Is this ready for review?

@Krishna-Prasad-P-V Is this ready for review?

Yes, it is ready for review. Thanks.

Thanks @Krishna-Prasad-P-V. In the future, please help ping the reviewers to remind them.
@aditi-pandit Can you please review? Thanks!

@Krishna-Prasad-P-V : We typically add our commits in a branch and rebase from main to it. Please can you collapse your work to a single commit.

@Krishna-Prasad-P-V : Please can you rebase your code and update the PR. The linux-build was previously failing, would be good to retrigger it.

I need to check why their are fuzzer test errors. Will work on it.


Improve Spock tests

This is in preparation to upgrade to Groovy 2.5 (#6324) that is a bit more strict in some places. It also doesn't like the notion IllegalStateException e = thrown().

These changes are now incorporated in #6682. The change to use def e = thrown Exception also doesn't seem to be needed since the upgrade to Spock 1.2 (#6669).


No devices found after adding integration.  xxx is not available for backend.

DONT'T DELETE THIS.
Please answer all questions as good as possible.
Language: english/german
Make sure you have read the documentation at https://github.com/danielperna84/custom_homematic#custom_homematic.
Make sure you have read the release notes at https://github.com/danielperna84/custom_homematic/releases.
Make sure you are running the latest version of the custom_component (and Home Assistant) before reporting an issue.
custom_component/hahomematic version (if applicable):
1.12.5 (Homematic(IP) Local from HACS)
Home Assistant version (if applicable):
2022.07.0
CCU version:

Model (CCU2/3, Raspi3/4, NUC, ProxmoxVE, HA-Addon ...): HA-Addon
OS (Original, RaspberryMatic, debmatic ...): RaspberryMatic CCU
Version: <IP_ADDRESS>20723

Problem-relevant configuration:
Do you use tls? no
Do you use callback? no
Do you use username and password? yes
Which interfaces do you use (hmip/bidcos/wired)? hmip
Describe the bug
A clear and concise description of what the bug is.
After installing and configuring the Homematic(IP) Local  integration, only one service and no devices or entities are discovered.
From the logs, it appears to have something to do with SSL?
And it says that the service xxx is not available for backend.
To Reproduce
Steps to reproduce the behavior:

Install HACS and the  Homematic(IP) Local integration following this instructions: https://github.com/jens-maus/RaspberryMatic/wiki/HomeAssistant-Integration
While adding the integration, only one service is discovered.

Screenshots (if applicable)

CCU firewall

integrations config

integrations page

integration view

Relevant HA log entries (full log)
Logger: hahomematic.central_unit
Source: /usr/local/lib/python3.10/site-packages/hahomematic/central_unit.py:345
First occurred: 3:33:04 PM (198 occurrences)
Last logged: 4:08:50 PM

_create_clients: Interface: HmIP-RF is not available for backend.
_create_clients: Interface: VirtualDevices is not available for backend.
_create_clients: Interface: BidCos-RF is not available for backend.

Logger: hahomematic.json_rpc_client
Source: /usr/local/lib/python3.10/site-packages/hahomematic/json_rpc_client.py:183
First occurred: 3:33:04 PM (198 occurrences)
Last logged: 4:08:50 PM

_post: Error while logging in via JSON-RPC.

Logger: hahomematic.json_rpc_client
Source: /usr/local/lib/python3.10/site-packages/hahomematic/json_rpc_client.py:157
First occurred: 3:33:04 PM (406 occurrences)
Last logged: 4:08:50 PM

_do_login: Unable to open session: Cannot connect to host de838cd8-raspberrymatic:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:997)')]

Logger: hahomematic.json_rpc_client
Source: /usr/local/lib/python3.10/site-packages/hahomematic/json_rpc_client.py:300
First occurred: 3:33:04 PM (406 occurrences)
Last logged: 4:08:50 PM

_do_post: ClientConnectorError

Logger: hahomematic.json_rpc_client
Source: /usr/local/lib/python3.10/site-packages/hahomematic/json_rpc_client.py:214
First occurred: 3:33:04 PM (208 occurrences)
Last logged: 4:08:50 PM

_post_script: Error while logging in via JSON-RPC.

Logger: hahomematic.central_unit
Source: /usr/local/lib/python3.10/site-packages/hahomematic/central_unit.py:931
First occurred: 3:33:05 PM (72 occurrences)
Last logged: 4:08:49 PM

check_connection: No clients exist. Trying to create clients for server RaspberryMatic

Diagnostic Information (available on every device)
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2022.7.7",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.5",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Vienna",
    "os_name": "Linux",
    "os_version": "5.15.32-v8",
    "supervisor": "2022.07.0",
    "host_os": "Home Assistant OS 8.4",
    "docker_version": "20.10.14",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "homematicip_local": {
      "version": "1.12.5",
      "requirements": [
        "hahomematic==2022.7.14"
      ]
    },
    "hacs": {
      "version": "1.26.2",
      "requirements": [
        "aiogithubapi>=22.2.4"
      ]
    }
  },
  "integration_manifest": {
    "domain": "homematicip_local",
    "name": "Homematic(IP) Local",
    "config_flow": true,
    "documentation": "https://github.com/danielperna84/custom_homematic",
    "issue_tracker": "https://github.com/danielperna84/hahomematic/issues",
    "requirements": [
      "hahomematic==2022.7.14"
    ],
    "ssdp": [
      {
        "manufacturer": "EQ3",
        "manufacturerURL": "http://www.homematic.com"
      }
    ],
    "zeroconf": [],
    "homekit": {},
    "dependencies": [],
    "codeowners": [
      "@danielperna84",
      "@SukramJ"
    ],
    "iot_class": "local_push",
    "loggers": [
      "hahomematic"
    ],
    "version": "1.12.5",
    "is_built_in": false
  },
  "data": {
    "config": {
      "entry_id": "8d1b71169082f402839d09cfc90081a8",
      "version": 1,
      "domain": "homematicip_local",
      "title": "RaspberryMatic",
      "data": {
        "instance_name": "RaspberryMatic",
        "host": "de838cd8-raspberrymatic",
        "username": "**REDACTED**",
        "password": "**REDACTED**",
        "tls": false,
        "verify_tls": false,
        "callback_host": null,
        "callback_port": null,
        "json_port": null,
        "interface": {
          "HmIP-RF": {
            "port": 2010
          },
          "BidCos-RF": {
            "port": 2001
          },
          "VirtualDevices": {
            "port": 9292,
            "path": "/groups"
          }
        }
      },
      "options": {},
      "pref_disable_new_entities": false,
      "pref_disable_polling": false,
      "source": "user",
      "unique_id": "unknown",
      "disabled_by": null
    },
    "platform_stats": {},
    "devices": []
  }
}

Expected behavior
A clear and concise description of what you expected to happen.
I expect the devices from RaspberryMatic to be found by the integration.
Additional context
Add any other context about the problem here.
After reviewing this issue. I discovered that the enable Homematic (Bidcos-RF) setting automatically re-enables after disabling it.

[SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:997)')]

Looks like you enabled SSL/TLS in your CCU, and not in this integration.
Disable SSL/TLS in your CCU or enable it in this integration.

Thanks for the quick response.  Yup, that was my problem. I'm really embarrassed to not have tried that...

No problem


QA React challenges 1-6

Conforms the text in the React section's challenges (1-6) to other curriculum expansion sections. All challenge tests still pass in the browser.
One point potentially for discussion:
Challenge 2: Create a Complete JSX Element adds a multi-line code example. It's wrapped in blockquote tags, which what the FCC site uses to style these, then wrapped in code tags to get the pink text. The current formatting looks a bit rough using the code tags. We can remove the example entirely if it's not needed, move it into a comment in the source code (it won't show on this site, but would get seeded when the challenges are ported to FCC), or keep as-is.

Looks good I'll take a look at this point about Challenge 2.


Sys.getenv('SPARK_HOME') returns empty string

I tried to connect to local spark cluster, but it fail to connect because the default code could not find my spark_home directory.
When I tried typing:
Sys.getenv('SPARK_HOME') , it returns a empty string.
In order to connect to spark I have to manually type this everytime:
sc <- spark_connect(master = "local", config = config, spark_home = '~/Library/Caches/spark/spark-1.6.2-bin-hadoop2.6')
The default code works before I install the newest edition of sparklyr a few days ago by typing:
devtools::install_github("rstudio/sparklyr"
I am wondering if there's any alternative way to fix this.

@dwy904 try updating sparklyr again; a fix was merged yesterday.

Thank you so much, it works now.


Generate DTS wrangler-overrides.d.ts from config

The type command aggregates the bindings from config and the rules for modules, then generates a DTS file for both service workers declare global { ... } or the preferred module workers interface Env { ... }
The rules for modules generates declare module based on the module type, the 3 types Text, Data & CompiledWasm
Module Example Outputs:
CompiledWasm
declare module "**/*.wasm" {
const value: WebAssembly.Module;
export default value;
}

Data
declare module "**/*.webp" {
const value: ArrayBuffer;
export default value;
}

Text
declare module "**/*.text" {
const value: string;
export default value;
}

resolves #2034
resolves #2033

Also @JacobMGEvans the force pushing means it's impossible to use the "changes since last review" view on GitHub (unless there's some workaround for that)

Also @JacobMGEvans the force pushing means it's impossible to use the "changes since last review" view on GitHub (unless there's some workaround for that)

You technically can look at the commit's between the forces, it usually diffs them.


build/compile_commands.json only includes main.cpp

First off I want to say thanks for the great work on this, setup was a breeze.
The problem I'm having is that I have created a new header file along with its .cpp implementation file and then included that header into main.cpp.  What I noticed is that when pressing the build button in VS Code only the main file is ever built and my new file is not nor is it linked.
Is it correct to assume that the build is searching for all files in the same directory as main.cpp and if not what should I edit to make this work?  Using Arch Linux.

DOH!  Of course CMakeLists.txt has the add_executable line and adding my files to that made it work.


enable z_index in Circumscribe

Overview: What does this pull request change?

adds z_index parameter to Circumscribe constructor so it can be used for the z_index of the frame (SurroundingRectangle or Circle)

Motivation and Explanation: Why and how do your changes improve the library?

Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

That SGTM, but I'd rather wait for @behackl approval.
Do you mind trying to add some test about that ? It's actually a corner case of manim interesting to test (the behaviour of surrounding shapes when z_index is special)

Sure - I'll take a look at the test suite at the weekend and see what I can do.

Keep in mind the effects for the opengl renderer! It doesn't support z_index

Keep in mind the effects for the opengl renderer! It doesn't support z_index

Just to piggyback on what MrDiver said :sweat: I don't really like the concept of z_index in general and IMO it is more intuitive to replace that with a change of the Z-coordinate in general.
But apart from that, I think that everything that the three of us said is not really in the scope of this PR, and I also like the changes.
I would like to again spark some discussion about this :eyes:

I would be on team @behackl and think we should move it and maybe also have something like a Constructor parameter for a more general Circumscribe animation? But that's just an idea.
But mainly moving the parameters would be great!

Closing due to inactivity.


Use shared code for emoji typeahead

We'd like to switch to sharing the webapp's code for the emoji typeahead. This will let us fix various aspects of that UI all at once, like #3833 -- and fundamentally it will be easier for the Zulip project to maintain one high-quality implementation of choosing what emoji you might mean as you're typing a message, rather than try to maintain two.
The work on the webapp side has already been done (with zulip/zulip#13739 and some followups shortly after) to free that code of webapp-specific dependencies and to move it into our shared package, in the file typeahead.js there. So what's needed now is the work on the mobile side to start using that.
We've also previously taken a different piece of webapp code (the typing-status implementation) all the way to using it in the mobile app, so we know we have all the infrastructure for this set up and working end to end. We've only done it that once, though, so there may still be rough edges or gaps in our docs.
Here's the next steps, as described at zulip/zulip#13728:

The roadmap for doing this would be a lot like our initial proof-of-concept for shared code, with typing_status.js (in zulip/zulip#13253, zulip/zulip#13315, zulip/zulip-mobile#3638, zulip/zulip-mobile#3662):

[done!] Move the relevant code into static/shared/. […]
On the mobile side, we'll update to a new version of the @zulip/shared NPM package (which comes from static/shared/, and replace our own implementations with calls to the shared code.
The process can be iterative; as we migrate in the mobile app, we may spot further refactors that'll be helpful to make to the shared code.

So we need to bump the version of @zulip/shared that we use, and adapt our code to use the shared functions typeahead.get_emoji_matcher and typeahead.sort_emojis in place of our own implementations of the same functionality.
In the process of doing that, we may see refactors we want to make to the shared code and perhaps the webapp code that uses it, and if so we can do those along the way.
For how to go about doing this:

See our docs on the @zulip/shared workflow:

the README of the @zulip/shared package's tree, which discusses how it's deployed;
docs/howto/yarn-link.md, which describes a key piece of dev workflow for developing changes in @zulip/shared together with the mobile app.

See the four PRs (two zulip-mobile, two zulip/zulip) I linked in the quote above for an example (but note they include some work we only had to do once, and some work on the zulip/zulip side that corresponds to what's already been done now for emoji typeahead.)

One thing we'll definitely want to do in zulip/zulip is to add types for the interface of this shared code; see https://github.com/zulip/zulip/commit/b70b7df22c36b6f3bf92fb99734cb22697b0a3ee for the previous example of that.

This was partly done in #5326 -- in particular the sorting step is now from shared code. Still to do is the filtering step.


Code overgrabs all contributors to updated threads

If someone comments on a thread three months ago, and someone else comments a day ago, both will be pulled if I am searching within the past week. This is a serious bug that devalues the stats about the size of a community. Each object will need to be date-sorted, not just the top-level issues and PRs.

Assigning to myself for logging purposes, but help would be great if anyone wants to jump in!

Working on this now.

@tgetgood Not sure this is working. Any ideas?
$ name-your-contributors -u RichardLitt -r name-your-contributors --after=2017-10-06T01:01:01Z

```json
{
  "prCreators": [
    [
      "dignifiedquire",
      "Friedel Ziegelmayer"
    ],
    [
      "jozefizso",
      "Jozef Izso"
    ],
    [
      "greenkeeper",
      null
    ],
    [
      "RichardLitt",
      "Richard Littauer"
    ]
  ],
  "prCommentators": [
    [
      "dignifiedquire",
      "Friedel Ziegelmayer"
    ],
    [
      "RichardLitt",
      "Richard Littauer"
    ],
    [
      "tgetgood",
      "Thomas Getgood"
    ]
  ],
  "issueCreators": [
    [
      "jbenet",
      "Juan Benet"
    ],
    [
      "gr2m",
      "Gregor Martynus"
    ],
    [
      "kentcdodds",
      "Kent C. Dodds"
    ],
    [
      "RichardLitt",
      "Richard Littauer"
    ],
    [
      "jywarren",
      "Jeffrey Warren"
    ],
    [
      "diasdavid",
      "David Dias"
    ],
    [
      "tgetgood",
      "Thomas Getgood"
    ]
  ],
  "issueCommentators": [
    [
      "RichardLitt",
      "Richard Littauer"
    ],
    [
      "gr2m",
      "Gregor Martynus"
    ],
    [
      "kentcdodds",
      "Kent C. Dodds"
    ],
    [
      "jywarren",
      "Jeffrey Warren"
    ],
    [
      "diasdavid",
      "David Dias"
    ]
  ]
}

The filtering works, the problem is that long options don't. I'll put in a patch for that.


Sap hybris profile quickstart

please do not merge to master

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Koniew, Marek:x: aartekKoniew, Marek seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Koniew, Marek:x: aartekKoniew, Marek seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


add Joystick Component

Description
Add JoystickComponent
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:
If something is unclear, please submit the PR anyways and ask about what you thought was unclear.

[x] This branch is based on develop
[x] This PR is targeted to merge into develop (not master)
[x] I have added an entry under [next] in CHANGELOG.md
[x] I have formatted my code with flutter format
[x] I have made corresponding changes to the documentation
[x] I have added examples for new features in doc/examples
[ ] The continuous integration (CI) is passing

Way to go!
Just left some minor comments, loking good!


unused_result lint is triggered on import

a.dart
import 'package:meta/meta.dart';

@useResult
int foo() => 42;

b.dart
import 'a.dart' show foo;
import 'a.dart' hide foo;

Problem
The Analyzer reports The value of 'foo' should be used.' on both imports in b.dart. I would not expect the unused_result rule to trigger on import statements.
$ dart --version
Dart SDK version: 2.18.4 (stable) (Tue Nov 1 15:15:07 2022 +0000) on "macos_arm64"

https://dart-review.googlesource.com/c/sdk/+/269460


dredd Incorrectly Handles Macro Expansion

Minimal Reproducible Example
#define BEGIN x =

int main() {
  int x, y;
  BEGIN(y);
}

dredd output
/* DREDD PRELUDE */

#define BEGIN x =

int main() {
  int x, y;
  if (!__dredd_enabled_mutation(6)) { BEGIN__dredd_replace_expr_int((y), 0); }
}

where BEGIN__dredd_replace_expr_int causes an error.

Dredd is doing the right thing here, except that it needs to insert a space before __dredd_replace_expr_int, because otherwise this is immediately preceded by the BEGIN token.
A solution would be to find the source location loc immediately preceding the begin source location for the (y) expression, and if loc is found not to be in the main source file (which is deemed to be the case for macros) to insert a space.
Another solution would be to always insert a space, but that would seem like overkill.
I'll look into the first.


[WIP] Lazy interface

As it turns out, the macro interface is probably possible using just macro-by-example, even if it has a few shortcomings (read: the #[ci] has to come before the doc comments).
I still need to convert the other added providers (or at least AppVeyor and Travis) to the new format, but everything should transfer over, though I'll probably have to flatten Jenkins' GHPRB.
Does this shape meet your use case, @epage ? We can add a trait on top and provide a ci_info() -> dyn CommonCIInfo for portable information.

I've also added examples/circle and plan to to the rest in order that we can run the example on CI to make sure that it doesn't panic when we're on that CI.

OK, this needs a rebase because of the several complete refactors, but I think this is a good direction.
@epage how does the basic functionality look to you? We can then put the traits suggested in #2 on top of this struct shape.

I'm a bit limited on time and the heavy use of macros is making it more difficult to see what you are intending with the API.  Honestly, I wonder if a build.rs would serve you better than macros, or just letting keeping it written out by hand.

No bother. Actually, representing this as a DSL and transforming using a build step doesn't sound that bad.
The current implementation looks roughly like this:
#[derive(Clone, Debug)]
pub struct Circle {
    /// Your home directory.
    home: Option<PathBuf>,
    ...
    /// The name of the git tag being tested.
    tag: Option<String>,
    ...
}

impl Circle {
    pub fn lazy() -> Option<Self> {
        Circle {
            home: None,
            ...
            tag: None,
            ...
        }
    }

    pub fn eager() -> Self {
        let this = Self::lazy().unwrap();
        let _ = this.home();
        ...
        let _ = this.tag();
        ...
        this
    }
}

impl Circle {
    /// Your home directory.
    pub fn home() -> &PathBuf {
        if self.home.is_none() {
            self.home = env("HOME")
                .map(|it| it.parse().unwrap());
        }
        self.home.as_ref().unwrap()
    }
    ...
    /// The name of the git tag being tested.
    pub fn tag() -> Option<&String> {
        if self.tag.is_none() {
            self.tag = env("TAG")
                .map(|it| it.parse().unwrap());
        }
        self.tag.as_ref()
    }
    ...
}

Except with actual panic messages.

I assume the impl Circle fns are home(&mut self)?  My concern is that requiring that much mutable state (mut for read operations) could cause problems with the borrow checker and isn't leveraging the capabilities of Rust..  The alternative is to directly access the member but then the user has to juggle the Options, again not leveraging the capabilities of Rust.
A very rough idea of where I lean on an API is:

state-less structs that support serde
data-only structs that can be loaded from serde
It'd take seeing a prototype and playing with it to iterate on what the best way to handle things is.

This would allow lazy loading, loading into custom structs, and a default struct implementation that contains everything for the person who needs it.  There might need to be some ergonomic improvements for that case, like a From<> or something.

You're correct, fixed the missing &mut self.
Another proposal: create a LazyEnv type.
struct LazyEnv<T> {
    inner: Option<Option<T>>
    var: &'static str
}
impl<T> LazyEnv<T> {
    pub fn get(&self) -> Option<&T> {
        self.inner
            .get_or_insert_with(|| env(self.var))
            .as_ref()
    }
}

And then the CI structs would have an abundance of those? Pending making a version for expected versions as well as the maybe-absent.

But I'll spend some time investigating building on top of serde deserialization.


Cow: Watch anwhatapps.com

Cow requests the watch of the watch_keyword anwhatapps\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

anwhatapps\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Allow specifying categories, tags and more

@gedw99 Hi, this feature should be supported since v0.2.0, I forgot to close this issue.
https://github.com/hugomods/releases-builder?tab=readme-ov-file#params.

nice . thanks


az artifacts universal download (ArtifactTool) fails on windows 10 pc with company proxy

Describe the bug
Attempting to download universal package times out and does not appear to be using environment variables. AZ can sucessfully add the extension and do other web requests, but when ArtifactTool is getting invoked it appears to be timing out.
Various proxy environment variables are set for a variety of tooling requirements:

Command Name
az artifacts universal download Extension Name: azure-devops. Version: 0.8.0.
Errors:
Encountered an unexpected error.
System.Net.Http.HttpRequestException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)

...
   at McMaster.Extensions.CommandLineUtils.CommandLineApplication.ExecuteAsync[TApp](IConsole console, String[] args) in C:\projects\commandlineutils\src\CommandLineUtils\CommandLineApplication.Execute.cs:line 130

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az artifacts universal download --debug --organization {} --feed {} --name {} --version {} --path {}

Expected Behavior
Artifact is downloaded.
Environment Summary
Windows-10-10.0.16299-SP0
Python 3.6.6
Shell: powershell.exe

azure-cli 2.0.64

Extensions:
azure-devops 0.8.0

Additional Context

@geverghe : Any idea how this can be routed to artifacts team?
cc: @snankani

Closing this issue in favor of tracking it in the azure-devops extension repo.
Please see https://github.com/Azure/azure-devops-cli-extension/issues/830 for updates.


"Uncaught exception" when calling rust function from event callback

#[macro_use]
extern crate stdweb;

fn bla(){
    println!("blarg");
}

fn main() {
    js!{
        document.addEventListener("click", @{bla} );
    }
}

Click anywhere on page with console open, see bug.

This is expected. The way a function is called from JS must match the prototype of the function on Rust's side. In this case the function you've set as the event handler will get called with a single argument (which will be the event object), and you've passed it a function which takes no arguments. This will fail at runtime.
The error you're getting could probably be more descriptive; I have plans to improve them.
Anyhow, you should probably use IEventTarget::add_event_listener if you want to set an event handler.

Sorry about that, was trying to create the simplest possible repro case.
If you change it to use an anonymous function like so
document.addEventListener("click", function(){@{bla}()})

then, at least on my copy of firefox, it does not print "blarg" in the console as it should. It does say warning: build with  -s DEMANGLE_SUPPORT=1  to link in libcxxabi demangling

Updated example, doesn't use addEventListener:
#[macro_use]
extern crate stdweb;

fn say( msg:String ){
    println!("I say: {}", msg);
}

fn main() {
    js!{
        let say = @{say};
        say("a");
        (function(){say("b")})();
        setTimeout(function(){say("c")},100);
    }
}

Hmmm... this happens because you havent called stdweb::event_loop`, so Emscripten's runtime gets deinitialized.
I could have sworn this used to work....
Thanks for the report! Reopening!


Jest emits a Babel warning when run with the coverage option

Do you want to request a feature or report a bug?
What is the current behavior?
When running jest on some of the files with large dependencies in our code base, we are seeing the following babel warning get emitted:
[BABEL] Note: The code generator has deoptimised the styling of "[path to file]" as it exceeds the max of "500KB".
Further investigation into this warning revealed that this is expected behavior in babel when the compact option has the default value of auto.
What is the expected behavior?
No warning should be emitted.
Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.
Jest 22.4.2, Windows 10

Addressed with #5704


Updated gradebook find

Made changes according to Yuan Cai's feedback

Coverage remained the same at 73.499% when pulling bfa3d86965c22af13fc0fd77f7a18b5dbd0e8ec4 on tristyxxnana:updateFind into 50779e853f079ced1862f7deb18d1d85bfb3555e on CS2113-AY1819S1-T16-1:master.


Adding/Deleting stops in Pattern Causes Alignment to Draw Incorrectly

 Issue by demory
Wednesday May 02, 2018 at 19:21 GMT
Originally opened as https://github.com/catalogueglobal/datatools-ui/issues/105

Create a new pattern
Add three stops
Delete stops 2 and 3
Add a new, different 2nd stop
Blue Line will draw as bidirectional:

Line is wonky from that point forward

 Comment by landonreed
Thursday May 03, 2018 at 18:40 GMT

Related to this: when deleting a pattern stop, it appears that control points between the deleted stop and other remaining pattern stops are not always deleted/cleaned up nicely.

 Comment by landonreed
Sunday May 06, 2018 at 16:33 GMT

This hasn't been entirely fixed, but the behavior is improved somewhat in the pattern-fixes branch

:tada: This issue has been resolved in version 4.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[tag, input-tags] added accessibility

Description

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 not work as expected)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

InputTag doesn't have a11y tab, should we make up something?


Bug in ItemPayloadIncludedRelationshipsStorageData serialization

I believe there is a bug in ItemPayloadIncludedRelationshipsStorageData specifically in the following line
https://github.com/autodesk-platform-services/aps-sdk-net/blob/e9b599be00f6d38157adb0b8a48b060b07513494/datamanagement/source/Model/ItemPayloadIncludedRelationshipsStorageData.gen.cs#L55-L56
EmitDefaultValue should be true as currently the object is serialized to the following (missing the type property); which in turn causes CreateItemAsync to fail
{
    id = "ID value"
}

@EMostafaAli ,
Thanks for reporting. Let us look into the issue and we'll revert back

@EMostafaAli that looks to be correct.
The other classes that use the specific type of object (TypeVersion, TypeFolder, etc.) have that set to true & I missed that when submitting PR #101 & just submitted the fix in PR #109:

ItemPayloadDataRelationshipsTipData
ItemPayloadDataRelationshipsParentData
ItemPayloadIncludedRelationshipsStorageData
StoragePayloadDataRelationshipsTargetData

@EMostafaAli this has been resolved with the merge of the latest PR #106. Just tested it & it is working with the Data Management v2.0.0 package.


passing server JSX into island props

After #1285, it became possible to pass server-generated JSX to islands through children. The natural next step is to allow the same for arbitrary props (children is also just a prop after all).
This works today:
<IslandComponent>
  <ServerComponent />
</IslandComponent>

This fails silently:
<IslandComponent
  slot1={<ServerComponent1 />}
  slot2={<ServerComponent2 />}
/>

Is anyone looking into this? I have a few different controls that could use this.


Uncaught (in promise) Error: Unexpected close tag ; Chrome User-Agent?

I am currently seeing inconsistent behavior across browsers using rss-parser.
I am testing with this RSS feed: http://www.marketwatch.com/rss/topstories
I do get the same error for all RSS feeds I have tried on the same domain.
Here is the relevant code, Vue-flavored:
const CORS_PROXY = 'https://cors-anywhere.herokuapp.com/'

export default {
...
  mounted() {
    require('../../node_modules/rss-parser/dist/rss-parser.js')
    this.getFeeds()
  },

  methods: {
    async getFeeds() {
      const parser = new RSSParser({
        headers: {
          'User-Agent': 'rss-parser',
          'Cache-Control': 'no-cache',
          'Pragma': 'no-cache'
        },
        defaultRSS: 2.0,
        xml2js: {
          strict: true
        }
      })
      const feedRequests = this.$page.frontmatter.feeds.map(feed => {
        return parser.parseURL(CORS_PROXY + feed)
      })
      this.feeds = await Promise.all(feedRequests)
    }
  }
}

In Firefox, this will make a request that returns a valid RSS XML response; in Chrome, this is returning HTML, which makes rss-parser return the following error:
Uncaught (in promise) Error: Unexpected close tag
Line: 9
Column: 7
Char: >
    at error (rss-parser.js?e48f:12624)
    at strictFail (rss-parser.js?e48f:12648)
    at closeTag (rss-parser.js?e48f:12834)
    at SAXParser.write (rss-parser.js?e48f:13397)
    at Parser.parseString (rss-parser.js?e48f:11945)
    at Parser.eval [as parseString] (rss-parser.js?e48f:11620)
    at eval (rss-parser.js?e48f:8448)
    at new Promise (<anonymous>)
    at Parser.parseString (rss-parser.js?e48f:8447)
    at exports.IncomingMessage.eval (rss-parser.js?e48f:8520)

I can change all of the header attributes using the headers option, but User-Agent is the only one that will not change on Chrome (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36). I suspect this has something to do with what I'm seeing.
Is there any way I can work around this? I will provide more information if necessary.

Sounds like this is an issue with MarketWatch rather than rss-parser. Unless you can figure out how to get marketwatch to respond to an AJAX request with XML rather than HTML, I think you're out of luck.
Sorry I can't be of more help here.

Thanks for the reply @bobby-brennan, I figured as much.
At least this serves as a good example of why User Agent sniffing is nasty business.

Were you able to find a solution to this? I'm running into these issues too it seems...which is really sad

I would contact MarketWatch (or the provider of the RSS feed) to ask them what you need to do to guarantee an XML response.
Setting the Accept header to text/xml or application/xml might do the trick...

It's broken on a few feeds, quite a few it seems. This seems like a pretty large issue, unless I'm doing something wrong, but it's kind of making rss-parser unusable for quite a few feeds it seems

Setting the accept header didn't help, and I'm using the cors-anywhere url

@lastmjs I'm getting the same issue with multiple feeds.*.org links trying to grab podcast rss feeds.

Yes, this is an issue with the folks serving the RSS feeds. They see that the request is coming from a browser (by checking the User-Agent header) and decide to show an HTML page instead of RSS. Unfortunately you can't change the User-Agent header due to browser security.
The only solution here is to create a proxy that lets you set the User-Agent header, e.g. by setting an X-Fake-User-Agent header.

@bobby-brennan is absolutely right, it's the responsibility of the feed maintainer to implement RSS XML correctly. If I request XML, but they send HTML just because I'm using Chrome, then that's a gaffe on their part.
I have attempted to contact MarketWatch (which is owned by WSJ) about this and have not received a reply; we ended up using a different feed that is properly implemented. Our clients were satisfied, but everyone involved is still annoyed.
It is clear that a large number of RSS feed implementations were built without considering the caveats of User-Agent sniffing. As clearly stated on MDN, it should be avoided whenever possible. I have had no luck finding any authoritative source that says otherwise.
There's only a few solutions to this for us developers making RSS clients:

Enforce browsers that allow modifying the User-Agent header (please don't do this)
Implement a proxy that allows you to overwrite the User-Agent header (effective, but gross)
Hound the feed maintainers until they make the necessary adjustments (good luck)

It's likely not technical, but non-functional requirements that drive poorly-implemented solutions like this. The fault lies with the feed maintainers for using ill-advised techniques to approximate what should be a common standard.

I understand, thanks everyone. I have found a workaround for now: https://jsonp.afeld.me
It's working perfectly for every feed I've thrown at it so far, better than cors-anywhere.

I'd bet cors-anywhere could do whatever jsonp.afeld.me is doing, it would be good to contact that project to see if they can fix themselves for the RSS feeds that break.

As pointed out in #111, adding ?format=xml may fix this issue for some feeds.


Feature Request : Configure the Checkpoint interval (checkpointOffset in the CheckpointManager constructor)

[ Adding the ability to configure the checkpoint interval to rootchain ]
Description
Having the ability to configure how many checkpoints are submitted per epoch would be beneficial to users in terms of security , gas optimization\configuration,
Proposed solution
Add a flag for the genesis command to configure it, to be passed as the checkpointOffset arg for the checkpointmanager constructor
If there's another way to do this, would appreciate a pointer in the right direction

@goran-ethernal fantastic! ETA on release?

I see that this contract
https://github.com/0xPolygon/core-contracts/blob/5a68054893e8a9755645b11528221e3c68c2af29/contracts/child/NetworkParams.sol
For release 1.1 did have the ability to change the checkpoint interval, is it possible on 1.1 to configure the checkpoint interval using this?

Those contracts were added in earlier releases, but they are not utilized nor have any purpose without the changes to the client itself on that branch I sent you in the earlier comments.


Cannot use the newest version with SonarQube Plugin

We are using the Node Plugin to handle our Node environment.
After updating to the newest version of the Gradle Node Plugin, the SonarQube task throws an error.
plugins {
    id "org.sonarqube" version "3.0"
    id "com.github.node-gradle.node" version "3.0.1"
}

node {
    version = "${nodeVersion}"
    download = true
}

Executing ./gradlew sonarqube fails with:
Execution failed for task ':sonarqube'. groovy.lang.MissingPropertyException: Could not get unknown property 'variant' for extension 'node' of type com.github.gradle.node.NodeExtension.
Variant is not mentioned in the documentation, but of course part of the Code
https://github.com/srs/gradle-node-plugin/blob/3052d9bd2db5c8fbe4bc3fd0306fcb8a805c0577/src/main/groovy/com/moowork/gradle/node/NodeExtension.groovy#L32
Do we have to set variant? Or does the SonarQube Plugin tries to access something which it should not care about?

This one looks like an interesting case, so first of all, I have no idea why sonarqube would be looking at the node-plugins extension
Secondly, yes, in the old version of this plugin the one that's in this repository (and abandoned by its author see #315 for details)
However, the plugin you're using is the maintained fork and that fork does not have a variant on NodeExtension https://github.com/node-gradle/gradle-node-plugin/blob/3.0.1/src/main/kotlin/com/github/gradle/node/NodeExtension.kt
But to get an idea on where it goes wrong you probably have to run with --stacktrace and an issue should probably be reported at sonarqube's issue tracker

Actually this might not be caused by sonarqube, but without --stacktrace and/or your full build-script it's hard to say for certain

Thank you for the fast response.
I didn't recognize that we are using a fork ... sorry for creating the issue here.
I think I will open the issue in the repository of the fork because we used that fork for a time, and just updated to a newer version.
I am sorry for the circumstances. Think the issue can be closed here.


fixes a wordswap typo

Heh, yup.
LGTM, once signed off

See https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work

Closing, because this is missing a sign-off, so we cannot merge or carry


Link to new executions for more event types

What was changed

After https://github.com/temporalio/temporal/pull/1866 (to be released in 1.13), more event types can have a link to a new execution. This exposes them in the status summary, and also history events table summary mode. The field name is the same for all events, so not much else had to change.
Why?

So that users can still easily navigate to the next execution after a retry or cron.
Checklist

How was this tested: Updated unit tests

awesome, thx!


Checkout history

I think a feature like checkout history could be a very useful thing. I'd see it as some receipt/note icon next to the "Settings" one in the bottom expandable menu. There we could see all past checkouts with basic filtering and sorting, and each record would contain checkout date and time, product list and group.

I'm not against this as long as it doesn't get in the way of users that don't want to use it, but I don't think I'll have time to work on this any time soon.

The status is that I'm slow >_>. I was working on the 1.1 update (which added the pullout bottom nav drawer and item groups), and was mostly finished before I started working on another app. After resuming work on this app, I decided to just go ahead and migrate the app to use compose before I released the update. That migration is also nearly finished. After I do get that update pushed out I plan to probably focus on other things for the time being.
TL,DR: The 1.1 update is still being worked on, but I don't intend to add anything big to the app afterwards (at least in the near future).


Work on build repository

This needs to be done in the quantecon.build.lectures repo:

[x] integrate _static files to _build_website target directories
[x] provide execution json report to _static folder
[x] integrate Julia compilation chain
[x] assemble complete site and update make preview
[x] add all necessary theme elements and static objects to support the theme to themes/qe/
[x] add #85 logic for code checker

Future

[x] add cache to compilation chain for notebooks
[x] add execution and error reporting to Jupinx
[ ] add containerised execution control

This needs to be done in ``QuantEcon.admin` repo:

[x] add interface with s3 bucket for uploading updates (current solution relies on aws cli)

the only item not done is docker containerised execution. We will implement that as a lower priority feature later on.


[FEATURE REQUEST] Generating Light and Dark Colors

I would like to be able to generate only light or only dark colors.  Since generally you need a color that either works on a dark or light background I think it would be useful.  I'm certainly running into this issue with my project right now.  I was digging into the library a bit, but wasn't sure how I would best implement it.  Light and dark is somewhat subjective.  Any suggestions on how it should best be implemented?
For now I'm using something similar to marked answer in this question.
http://stackoverflow.com/questions/11225050/how-to-generate-light-colour-shades-in-javascript

I thought about this a bit, and maybe it would would work best if we can just send a minimum and maximum rgb or hex values.  I might try and implement something like this.

So after looking through the code a bit I made a change that works well for RGB.  This essentially lets you generate and RGB color within any range you like making it easy to generate light and dark colors.
        function rgb(hasAlpha) {
            var rgbValue    = (hasAlpha)    ? 'rgba' : 'rgb';
            var alphaChanal = (hasAlpha)    ? (',' + this.floating({min:0, max:1})) : "";
            var colorValue  = (isGrayscale) ? (gray(this.natural({min: minR, max: maxR}), ',')) : (this.natural({min: minR, max: maxR}) + ',' + this.natural({min: minR, max: maxR}) + ',' + this.natural({max: 255}));

            return rgbValue + '(' + colorValue + alphaChanal + ')';
        }

        function hex(start, end, withHash) {
            var symbol = (withHash) ? "#" : "";
            var expression = (isGrayscale ? gray(this.hash({length: start})) : this.hash({length: end}));
            return symbol + expression;
        }

        options = initOptions(options, {
            format: this.pick(['hex', 'shorthex', 'rgb', 'rgba', '0x', 'name']),
            grayscale: false,
            casing: 'lower',
			minR: 0,
			maxR: 255,
			minG: 0,
			maxG: 255,
			minB: 0,
			maxB: 255
        });

However for hex colors I feel like we need a new basic random function to specifically generate hex numbers with the option of minimum and maximum values.  This would help me finish the random colors with minimum and maximum values for Red Green and Blue.  Can someone let me know if they think I'm on a good track here?  I've never contributed to an open source project so I would be interested to know what anyone thinks so far.

I ended up spending quite some time with this and have tried to standardize things naming wise a bit with the rest of the library.  It is currently working now.  I'm still trying to think of ways to reduce the number options you need to send.  However more options are always better I think.  It will even let you grayscale certain color range.  Will likely do some more testing and review before I do an actual pull request, but this will give you an idea of what you can do with it.
//Random Light Red sending minimum needed options
var light_red = chance.color({format: 'hex', min_red: 200, max_red: 255, max_green: 0, max_blue: 0, min_alpha: .2, max_alpha: .3});

//Random Light Blue by sending all options
var light_blue = chance.color({format: 'rgba', min_red: 0, max_red: 0, min_green: 0, max_green: 0, min_blue: 200, max_blue: 255, min_alpha: .2, max_alpha: .3});

//Random Green Grayscalled
var c = chance.color({format: 'hex', grayscale: true, max_red: 0, min_green: 200, max_green: 255, max_blue: 0});

Also in order to program the above I needed a random hex number generator with minimum and maximum range.  So I've added this.
     /**
     *  Return a random hex number as string
     *
     *  NOTE the max and min are INCLUDED in the range. So:
     *  chance.hex({min: '9', max: 'B'});
     *  would return either '9', 'A' or 'B'.
     *
     *  @param {Object} [options={}] can specify a min and/or max and/or casing
     *  @returns {String} a single random string hex number
     *  @throws {RangeError} min cannot be greater than max
     */
    Chance.prototype.hex = function (options) {
        options = initOptions(options, {min: 0, max: MAX_INT, casing: 'lower'});
        testRange(options.min < 0, "Chance: Min cannot be less than zero.");
		var integer = chance.natural({min: options.min, max: options.max});
		if (options.casing == 'upper') {
			return integer.toString(16).toUpperCase();
		}
		return integer.toString(16);
    };

As I said before I'm very new to github and open source contribution, if I'm doing something wrong please let me know!

@victorquinn I'm interested in submitting a pull request with these changes.  Do I need permission from you to do that?  So far I've been getting permission issues.

You shouldn't need any permission to submit a pull request and this would be a welcome addition!
You won't be able to push directly to this repo but you should be able to fork the repo, make your changes there, and submit your PR.
Once it's submitted I'll just review and merge.
Cheers,
Victor

On Dec 5, 2016, at 11:41 AM, Adam Rochford<EMAIL_ADDRESS>wrote:
@victorquinn I'm interested in submitting a pull request with these changes. Do I need permission from you to do that? So far I've been getting permission issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Now that PR #290 has been merged, I think it's safe to close this issue.


Completed nullability annotation pass, code tweaks

This PR includes a few code tweaks, but no functional changes.
Changes included:

Completed the nullability annotations in the UWP project
Some code tweaks (eg. == null ---> is null)
Fixed some incorrect mixed spaces/tabs in a few files
Updated and streamlined the NuGet dependencies for the UWP projects

Sergio pls
https://github.com/jenius-apps/ambie#contributors

Whoops! That wasn't there last time I made a PR! 🤣
I was just completing my own work ahahah
Do you want me to open an issue anyway?
(Really sorry I missed it 😅 )

Ambie has matured a lot. I'm not comfortable with a large pr like this that makes different types of changes across the entire repo all at once. I see syntactic sugar changes but also changes to if statement conditions and optimizations that go beyond syntactic sugar.
If you could reduce this pr to purely syntactic sugar changes, I'll be okay with that. But the mix mediaplayer optimizations you're proposing should be a separate pr so it can be tested and reviewed more carefully. Although even before you make a PR for that, what's the reason for those optimizations? Was there a bug in code? Does it measurably improve UX? Or are the optimization just nice to have? Just curious since that affects my own priority levels on whether I should investigate the issue asap or not.
The changes to if statements might also be a separate pr for more careful testing.

I like the use of new c# features though. Would love to take those in

"I'm not comfortable with a large pr like this that makes different types of changes across the entire repo all at once. I see syntactic sugar changes but also changes to if statement conditions and optimizations that go beyond syntactic sugar."

That's fair, sure. My rationale here was that almost all the PR is just sugar changes, so I figured it made sense to apply them everywhere since despite the PR involving many different files, the changes are still always the same in general, so splitting that just based on groups of files seemed like unnecessary overhead for you to track/review/approve multiple PRs.

"If you could reduce this pr to purely syntactic sugar changes, I'll be okay with that. But the mix mediaplayer optimizations you're proposing should be a separate pr so it can be tested and reviewed more carefully."

So essentially you'd just like me to remove that optimization? Because everything else in this PR is really just sugar 🙂
If so, just let me know and I can definitely undo that part, not a problem!

"what's the reason for those optimizations? Was there a bug in code? Does it measurably improve UX? Or are the optimization just nice to have? Just curious since that affects my own priority levels on whether I should investigate the issue asap or not."

There wasn't a measurable difference (by that I mean I haven't tested for that, not that it couldn't possibly be measured), it's just one of those changes where I think it makes sense to optimize "by default". As in, instead of just optimizing when there's a measurable slowdown, there's a whole set of minor improvements that one can do just as standard practice (eg. avoiding duplicate copies and using Span<T> instead, using a more appropriate data structure for temporary locals, etc.). In this case the functionality of the code is identical, I just replaced that ToList() call with a HashSet<string>, but the semantics is the same. As in, if you have to use a temporary data structure (which you do already), you might as well use the one that runs faster in this scenarios, and since you're repeatedly calling Contains(...) in a loop, a hashset just seemed more appropriate, is all. I'd consider this just a minor tweak rather than an actual optimization (since it's just a small change with no functional difference), but that said I'm happy to roll that back if you feel more comfortable having that in a separate PR. Just let me know! 😄

@dpaulino I've removed that optimization and only left the nullability annotations and code tweaks, let me know if this is alright or if there's anything else you'd like me to remove from this PR (and possibly move to another one if you're interested) 🙂

Alright, I've rebased and resolved all conflicts and addressed the things you mentioned, let me know how it looks! 😄

Thanks @Sergio0694  😊

Awesome! Happy to help, Ambie is great! 🥳🎉


Add two specs for missing arrays and hashes

A value of nil was chosen in the case of optional hashes with required
keys.  A value of nil should bypass the optional requirement whereas a
default value of hash or array might trigger the nested required flag.
The corresponding issue is here: https://github.com/intridea/grape/issues/892

See @dm1try's comment in https://github.com/intridea/grape/issues/892#issuecomment-74437376, is this still legit?

See #994.It can be closed, I think.

Closing, @adamcooper please confirm.


Obfuscation chr and the Status field

When the obfuscation_chr is available (by default) it makes no sense to allow the Status of a subscriber to change if the subscriber details have been obfuscated, which occurs after a successful subscription in any case.
Status field could be made read-only.

Resolved with v0.2.2


Qt 5.6

We need Qt 5.6 since it's Long Term Support

https://github.com/hunter-packages/Qt/issues/10


Time to train?

Hi,
thanks for you work and for sharing, any idea how long it would take to train on a "common PC", RAM 16GB and 2GB 3 years old GPU?
Also are there any restrictions on the size (resolution) of the input and output images?

Hey Stéphane,
Training time will vary considerably based on input size and parameter
values. The restrictions on input and out sizes will depend on GPU memory.
I used rather small dimensions for my examples because they were simply
faster to train. It ultimately depends what you're trying to use the model
for.
On Thu, Dec 6, 2018 at 4:52 AM Stéphane Debove<EMAIL_ADDRESS>wrote:

Hi,
thanks for you work and for sharing, any idea how long it would take to
train on a "common PC", RAM 16GB and and 2GB GPU?
Also are there any restrictions on the size (resolution) of the input and
output images?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mohamedkeid/Feed-Forward-Style-Transfer/issues/3, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADlBSvQpsP6_32BMLlWzzEaaIbFapTVCks5u2PbXgaJpZM4ZGQ3T
.

Thanks for the reply. Can you give examples of your own parameters and running times? I just want to know if it's more something like a couple of minutes, a couple of hours or a couple of days, I don't need an exact time.

With a Titan X Pascal, 64 gigs of RAM, and 3.5ish GHz i7 it took me a few
hours I believe. The parameters vary based on the artwork.
On Thu, Dec 6, 2018 at 10:04 AM Stéphane Debove<EMAIL_ADDRESS>wrote:

Thanks for the reply. Can you give examples of your own parameters and
running times? I just want to know if it's more something like a couple of
minutes, a couple of hours or a couple of days, I don't need an exact time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mohamedkeid/Feed-Forward-Style-Transfer/issues/3#issuecomment-444924282,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADlBSpRySC0_gwSwfplq9AubRgN6lPlAks5u2T_6gaJpZM4ZGQ3T
.


GUI export network to hdf5 button

Add feature to export simulations and parameters to hdf5.

Exports network object as an hdf5 file
Should have an option to exclude simulation data
Should only export the latest simulation?

Edge cases to consider: The user changes parameters but does not run a new simulation. The parameters will not match the simulation on save.

Where should this button be located?

Closed because hdf5 files are too large for this purpose. Continuing work in https://github.com/jonescompneurolab/hnn-core/issues/756 instead.


feat!: drop support for python 3.7

Related Issues
Fixes https://github.com/descope/etc/issues/8209
Description
Dropping support for python 3.7

@yaelt47 @descope/sdk-admins fyi this requires a major release


Package Dependencies

It is my understanding that most applications will use either TinyMCE -or- TinyMCE.jQuery, but not both. This package creates a dependency on both packages. Installing this package requires the user to install both versions of TinyMCE and to do so in the correct order since they will overwrite each other. Perhaps a separate tinymce-jquery-knockout-binding is required.

This caused me some headscratching... I had simply installed the tinymce-knockout-binding nuget package (but unfortunately said "no to all" at the point where the tinymce.jquery package wanted to replace the files previously installed by the tinymce package).  This resulted in the editor box appearing with style visibility="hidden" - and basically tinyMCE not working at all.
Until this is tidied up, then:

as per the comment by @mdurling: the order the dependent packages are installed is crucial to getting everything working.
and when prompted by the package manager, ensure that the tinymce.jquery package overwrites all of the files previously installed by the tinymce package itself.


cypress test for table block

@iFlameing can you please update this, and make sure it works?

@sneridagh I fixed the test and Travis is happy :)


feat(core): add useMeasure and useSetState

@Daydreamer-riri help review💘

I need merge first, there is something I need to attend to

Sorry, I have so many things to attend to today that I haven't had time to review this PR🥹


After upgrading to beta6, my OpenAI plugin doesn't work anymore

Describe the bug
I have a .NET console application using an OpenAI plugin which worked just fine until today, when I upgraded the project to beta6. Now, the following code:
const string pluginManifestUrl = "https://semantickernel-unitedstatesdata.azurewebsites.net/api/.well-known/ai-plugin.json";
await kernel.ImportOpenApiPluginFunctionsAsync("UnitedStatesPlugin", new Uri(pluginManifestUrl));

returns the following exception:
Exception has occurred: CLR/Microsoft.OpenApi.Readers.Exceptions.OpenApiUnsupportedSpecVersionException
An exception of type 'Microsoft.OpenApi.Readers.Exceptions.OpenApiUnsupportedSpecVersionException' occurred in System.Private.CoreLib.dll but was not handled in user code: 'OpenAPI specification version '' is not supported.'
   at Microsoft.OpenApi.Readers.ParsingContext.Parse(YamlDocument yamlDocument)
   at Microsoft.OpenApi.Readers.OpenApiYamlDocumentReader.<ReadAsync>d__3.MoveNext()
   at Microsoft.OpenApi.Readers.OpenApiTextReaderReader.<ReadAsync>d__3.MoveNext()
   at Microsoft.OpenApi.Readers.OpenApiStreamReader.<ReadAsync>d__3.MoveNext()
   at Microsoft.SemanticKernel.Functions.OpenAPI.OpenApi.OpenApiDocumentParser.<ParseAsync>d__1.MoveNext()
   at Microsoft.SemanticKernel.Functions.OpenAPI.Extensions.KernelOpenApiPluginExtensions.<RegisterOpenApiPluginAsync>d__3.MoveNext()
   at Microsoft.SemanticKernel.Functions.OpenAPI.Extensions.KernelOpenApiPluginExtensions.<ImportOpenApiPluginFunctionsAsync>d__1.MoveNext()
   at Program.<<Main>$>d__0.MoveNext() in D:\src\events\Codemotion2023\SemanticKernel\SemanticKernel.OpenAIPlugin\Program.cs:line 23

I've tried to upgrade my OpenAI plugin to use OpenAPI 3.0.1 and to switch to the YAML format, but nothing changed.
Expected behavior
I didn't see any breaking change around OpenAI plugins (other than the new name of the method to import them), so I expect them to still work after upgrading to beta6.
Platform

OS: Windows
IDE: Visual Studio Code
Language: C#
Source: NuGet package, version 1.0.0-beta6

Hi @qmatteoq, sorry about the issue you're experiencing. I believe the problem is that as of beta6, there is an import method specifically for OpenAPI specs which is used to load an OpenAPI spec directly (without an ai-plugin.json), and a separate import method for OpenAI plugins that use an ai-plugin.json.
Can you change ImportOpenApiPluginFunctionsAsync to ImportOpenAIPluginFunctionsAsync and let us klnow if that fixes your issue?

Hello @alliscode , thanks for the support! I tried but it doesn't seem to work. I've changed the import code to:
const string openApiUrl = "https://semantickernel-unitedstatesdata.azurewebsites.net/api/swagger.json";
await kernel.ImportOpenAIPluginFunctionsAsync("UnitedStatesPlugin", new Uri(openApiUrl));

However, I'm getting now the following exceptions:
Exception has occurred: CLR/Microsoft.SemanticKernel.Diagnostics.SKException
An exception of type 'Microsoft.SemanticKernel.Diagnostics.SKException' occurred in System.Private.CoreLib.dll but was not handled in user code: 'Unexpected API type '' found in Open AI manifest.'

Moreover, I would like to understand better why my previous code doesn't work anymore. Shouldn't the ai-plugin.json manifest continue to be supported, so that Semantic Kernel can be fully compatible with OpenAI plugins?
Thanks!

I also get this error when testing an OpenAI plugin with the latest commit in microsoft/chat-copilot (which is using SK beta6).

I see this issue as well

I'm truly sorry @alliscode, I realize only know what you meant. Indeed, I didn't catch the difference between OpenAI and OpenAPI in the name of the method, so I was using ImportOpenApiPluginFunctionsAsync() to import an OpenAI plugin. I switched to ImportOpenAIPluginFunctionsAsync() and now everything works as expected. Sorry for the trouble!

agreed, this fixed the issue, I was playing with the Chat Copilot demo app and had to change the code to fix this.

Glad to hear this fixed the issue.


Expected onnx model input mismatch with name in test_onnx.py

When trying test_onnx.py with the model from https://huggingface.co/onnx-community/metric3d-vit-large I got the following error: ValueError: Required inputs (['pixel_values']) are missing from input feed (['image'])
due to mismatch between the onnx_input dictionary used in the script and the input dictionary expected by the model.
Changing the key name from "image" to "pixel_values" in the code below will solve the issue.
onnx_input = {
"image": np.ascontiguousarray(
np.transpose(rgb, (2, 0, 1))[None], dtype=np.float32
),  # 1, 3, H, W
}
to
onnx_input = {
"pixel_values": np.ascontiguousarray(
np.transpose(rgb, (2, 0, 1))[None], dtype=np.float32
),  # 1, 3, H, W
}

Thanks for your sincere report and I will update this in ReadMe.


Bug: helper cookie not working

cookie helper not working,
helper("cookie");
$app = config("App");
set_cookie(
"token",
"test",
time() + 3600,
$app->cookieDomain, // "localhost:8080"
$app->cookiePath, // "/"
$app->cookiePrefix, // ""
$app->cookieHTTPOnly, // false
true
);
dd(get_cookie("token")); // null
I tried to refresh the browser, but the result was the same // null

This is a common pitfall with cookies. Quoting PHP.net:

Cookies will not become visible until the next loading of a page that the cookie should be visible for.

CI4's set_cookie sets a new cookie in the Response object but it sits there until the headers are sent. get_cookie uses the Request object to retrieve the cookie in the $_COOKIE array. In your example, since you are setting and getting the same cookie on the same page, then cookies are not sent to the browser and therefore the $_COOKIE is not populated with the cookies in the Response. That's why you are getting null (i.e., cookie not in $_COOKIE).
To achieve your desired result, create two pages: (1) setting the cookie; (2) getting the cookie. In your cookie-setting page, you will redirect with cookies to the cookie-getting page, something like redirect('/my-cookie-getter')->withCookies();. Then, there the dd should show the cookies.
Side note: The arguments supplied in set_cookie in your example is wrong.

This is a common pitfall with cookies. Quoting PHP.net:

Cookies will not become visible until the next loading of a page that the cookie should be visible for.

CI4's set_cookie sets a new cookie in the Response object but it sits there until the headers are sent. get_cookie uses the Request object to retrieve the cookie in the $_COOKIE array. In your example, since you are setting and getting the same cookie on the same page, then cookies are not sent to the browser and therefore the $_COOKIE is not populated with the cookies in the Response. That's why you are getting null (i.e., cookie not in $_COOKIE).
To achieve your desired result, create two pages: (1) setting the cookie; (2) getting the cookie. In your cookie-setting page, you will redirect with cookies to the cookie-getting page, something like redirect('/my-cookie-getter')->withCookies();. Then, there the dd should show the cookies.
Side note: The arguments supplied in set_cookie in your example is wrong.


fix/kanbanBoardcolumn

Functionality:
made the kanban Board columns dynamic and implemented a dropdown menu
Solution:
Risk level:

[ ] high
[ ] medium
[X] low

How to test:
Check in the Kanban Board Columns

Fix merge conflict


New: Navi Search Bar

Resolves #

Description
Adds Navi Search Bar with a dummy app
Proposed Changes

Screenshots

License
I confirm that this contribution is made under an MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Currently the search bar does not fail gracefully when a search provider breaks and doesn't return results, since the solution is more involved I'll open a separate PR for it: https://github.com/yahoo/navi/issues/758

Bug found on the asset search provider to be dealt separately: https://github.com/yahoo/navi/issues/764


bigger k for bench

bench them from k=19 to k=24.

The rationale behind the choice of the values is to make the benchmark run on interactive and even low-end systems such as laptops without straining the system. Point is that if you oversubscribe readily available resources, the results would be skewed and hence misleading. Maybe it would be more appropriate to let the user override the value at run-time by setting an environment variable. This way you won't have to wait for a result that you consider relevant for your application, but just choose it. [And naturally ensure resource availability.] We do it like this  in poc/msm-cuda@sppark.

Make sense. Thx for your explain. And I've maken the degree mutable with evn var.

There was a compilation error and warnings, so I've reimplemented it to harmonize with sppark PoC and fix the warnings. Thanks!


[BUG] Updating a Communities Properties Breaks the Website

When updating the name or the slug URL of a community, it causes the image field for the communities database entry to go null and breaks the whole website. This is a follow-up for #12

Fixed int eh latest release.


deep link additions

@MikePlumleyMSFT @markjjo @robmazz  - Leslie and i are adding deep links to mentions of the compliance center and metadata to track topics with them. please take a look and lmk if you have any issues with these changes by Friday

@pebaum, @lhcole613 The deep link in my articles look fine

@pebaum the deep link in my article looks fine.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

  Caution: Large pull request
This public repo applies limits on the number of files that can be merged in a single pull request (PR):

Warning Warning message and ability to unblock PR using the Merge large pull request* label - 30
Block Block message and PR is blocked - 100

This pull request will change 59 files, which exceeds the warning limit of 30.
Before this pull request can be merged, you must review the list of files it contains and their changes to confirm they are correct and intentional. This includes files you did not change and/or do not own. If there are changes you aren't familiar with, contact the individuals who submitted the commits included in this pull request and review the changes with them.
The individual who merges this pull request is responsible for ensuring the changes included in it are correct, and for resolving any issues that might result in merging it.
To merge this pull request
If you have determined that the changes in this pull request are correct, add the Merge large pull request* label to it, wait for the max/pr-file-count check to pass, and then click Merge. To add a label, click the gear icon next to Labels and then select Merge large pull request*.

To reject this pull request
If you can't confirm the changes in this pull request are correct, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.
* You must have write or triage access to this repo to add labels.