E2: Add "Namer" functionality (Fixes #1365)

Fixes:
#1365
This pull request (after merged) would add the following to Expression 2 gate:
 Functions:

Signature
Description
Cost

String=entity:getComponentName()
Returns the component name of another Wire entity. This is NOT the same as e:getName() function if called on E2 entity! This functions exists to allow E2 to get its own component name.
2

void=entity:setComponentName(string)
Set the component name of another Wire entity. This is NOT the same as setName function if called on E2 entity! This functions exists to allow E2 to set its own component name.
20

void=entity:setName(string)
Depending on the type of entity provided, if it is E2 then it will set the name of another E2; otherwise, it will set the component name of another Wire entity instead.
20

I have tested in-game, it works as expected. Here is the test code:
print("Test: Default Component Name")
print(entity():getComponentName() == "Wire Expression 2")             # Pass / True

print("Test: entity:setComponentName")
entity():setComponentName("Test entity:setComponentName")             # Pass / True
print(entity():getComponentName() == "Test entity:setComponentName")  # Pass / True

print("Test: entity:setName")
entity():setName("New E2 Name")                                       # Pass / True
print(entity():getName() == "New E2 Name")                            # Pass / True

Votes
Do you want to keep 3 non-entity: E2 functions? : ✖ : Ok I removed them.
Demo
Demo GIF (~22MB, will load slowly for the first time, open it in a new browser window or you will get hotlinking error).

I would integrate setComponentName into setName (if entity.type ~= expression2) to reduce confusion why setName doesn't work like the Namer tool and not adding too many functions.
This would prevent setting the component name of E2's, but i don't see any practical usecase for that. (There is no need to have 200+ chars in the tooltip, if you hit the char limit of E2 name you are doing something wrong)

Update incoming.

I agree with adosikas. Delete the setComponentName and getComponentName functions and add that functionality to the setName and getName functions instead. That way, there is only one new function: E:setName(S) but we still get the same functionality.

Pushed a new commit.
@Divran

Delete the setComponentName and getComponentName functions

You know I am against that? :(

add the features of these to the E:setName(S)

Added only to `entity:setName(string) function. See the update.

That way, there is only one new function: E:setName(S) but we still get the same functionality.

It is not the same functionality; Component Name != E2 Name.

Also, the setters should probably cost at least 20, not 5, since it uses SetNWString

Committed within the update.

IMO, all that needs to be done is:

add entity:setName(string) with if type==E2: set name else: set component name
modify entity:getName() to do: if type==E2: get name else: get component name

No need for helper functions etc

Vote: Do you want to keep non-entity: E2 functions? React with emote either thumbs-up to remove those, or thumbs-down to keep them.
If there are 3+ upvotes on this comment, I will remove those E2 functions:

setComponentName(string)
String=getComponentName()
String=getName()

NOTE: These two functions are already there in the E2: String=entity:getName() and setName(string).

And no need to allow setting name (or component name) of other e2.

I am strongly against this... -_-
Why is there no need?  Like I have mentioned in my previous comment, debugging is the main reason here why I want to keep setComponentName for E2 as well.

Well there is setCode for other chips I think, so setName should be available too. But yeah, those all functions should be under setName and getName, no need for functions that do same thing as setName just in some other cases...

no need for functions that do same thing as setName just in some other cases

How many times do I need to repeat myself? They are not the same when called on E2 itself.
And having setComponentName for E2 is handy because when debugging, you have twice as much space to visually debug it (398 characters instead of just 199)...

So you actually say name size should be increased? Because clearly doubling space by 2 separate functions isnt a good thing.

So you actually say name size should be increased?

It can't not be increased. Thus why they are also two separate networked-strings. One is E2 name, another is E2 component name.
While for other Wire entities, that fact is not true. There is only component name for other Wire gates.

The setName function for E2 had a cap of 12000 characters. https://github.com/wiremod/wire/blob/master/lua/entities/base_wire_entity.lua#L292

The setName function for E2 had a cap of 12000 characters.

According to the wiki, Entity:SetNWString(string) is limited to 199 characters. So, having such limit is literally useless.

!(something is wrong)[http://s.damianu.me/NightMask]
I am clearly doing something wrong, because without your functions I still get whole screen covered :<

I am clearly doing something wrong, because without your functions I still get whole screen covered :<

Then I blame GMod wiki.

Yeah, next time check before you say something, because I really can cover almost whole screen:
http://s.damianu.me/NightGust

According to the wiki, Entity:SetNWString(string) is limited to 199 characters. So, having such limit is literally useless.

The SetOverlayText function doesn't use SetNWString

Pushed (probably) the last commit to this PR. Please read the commit message.
I have updated the PR description too, also added a demo.

I have two ways that I can allow this to be merged:
A. Either you only add E:setName(S) and you make this set the E2 name on E2, and component name on everything else. Then you edit the existing E:getName() function to work the same way.
or B. You add E:setName(S) which ONLY sets the E2 name, and if the entity is not an E2 then it does nothing. Then you add E:setComponentName(S) and E:getComponentName() which get/set the component name on any entity, and these never interact with the E2 name in any way. Like you yourself said @CaptainPRICE

E2 has setName(string) function which allows it to set the name of E2, do not confuse the two!

and I agree. Either you merge the two into one, or you keep them completely separate. Don't merge them sometimes and other times not. That's just confusing.

@Divran Okay, then I pick B. Working on it...

One last thing before I go. Since this will set a networked variable (NWString), maybe it would be good to limit the rate at which you can change it (to, for example, once per 0.1 seconds or something). Not sure how much you could lag servers and/or every client connected to said server if this was spammed a few hundred times per tick.

FWIW I prefer #1368 (which implements @Divran's option A) to this PR (which will soon implement option B). I'd rather present a clean and consistent API, including doing work to make things cleaner, than exposing underlying ugliness that we'd rather wasn't there in the first place for a very niche and questionable use case.

@AbigailBuccaneer keep in mind that the value E2's setName funtion changes is the same value that users define in @name when creating their E2. This value shows up in the tooltip overlay thingy that you see when you aim at entities. For wiremod, this overlay text is synced using net messages in a small bit of custom code in the base wire entity, which I wrote.
This name is displayed in the top center of the overlay, and supports up to 12000 characters thanks to net messages + an arbitrary limit I added.
This is inherently different from the way the namer tool works.
The wire namer tool, is far, far older than E2 itself, and what it does is simply set an NWString variable called WireName on the target entity. Then, when you aim at that entity to view its tooltip overlay thing, wire's code that renders said overlay will check if WireName is defined (it used to do this before as well, and I kept it as I changed the tooltip code). If WireName is not defined, it will display the default name of the entity, which is stored in PrintName. PrintName is a recommended thing to have on all entities in gmod, not just for wiremod.
This name is displayed in the bottom left corner of the overlay, and supports up to around 200 characters according to the gmod wiki.
So the wire namer does allow you to set this value on any entity, but it'll only be displayed on entities which inherit from the base wire class and/or use its overlay rendering code.
In this way, it does kinda make sense to keep them separate, since they are in fact separate things. I think I've changed my mind and option B is probably the better choice here. The question now is whether or not we should add this at all. Is it really necessary? Will anyone ever use this? I'm not sure if people even use the namer tool right now to begin with, much less if they would use an E2 function that has the same behavior.
Also,
In a different section of github you said this (I just thought it would be better to clear all these things up for you in the same place rather than spread it out).

Is there any reason why E2 uses a different network var for this than other things?

The truth is that it doesn't. As mentioned above, the value that setName changes is the same one that is parsed out of the E2 code from the @name field. This text is then sent to the client using SetOverlayText which is a standard function on every single entity in all of gmod.

I have pushed a new update, now everyone should be happy. There we go.

I have pushed a new updated with changes as requested by @TomyLobo, and improved anti-spam system as suggested by @adosikas, and also made some other small changes.
@Divran @AbigailBuccaneer Thoughts?

@CaptainPRICE in future please break up your commits so it's more like one bullet-point item per commit, rather than a nondescript first line and then some non-standard bullet point markup that contains the actual useful info. It makes for a cleaner history and is easier to review.

Small update incoming.

I have released a small update to anti-spam system. Now it is actually adding the correct length towards the limit-per-second value.
@Divran I expect your positive review at this point 😄


Expose buildModuleUrl as part of the Cesium API

It's been used in Sandcastle examples forever, but has always been marked as private in jsdoc. In order to make it available in TypeScript, we need to expose it.
Also cleaned up the doc to be more inline with what the current version actually does.
Fixes #8922

Thanks for the pull request @mramato!

:heavy_check_mark: Signed CLA found.
:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

@kring I think you were requesting this as well?  Can you do a quick review/merge?

Looks good to me! Tested that it appears correctly in the doc and in Cesium.d.ts.


TypeError: Attempted to assign to readonly property - Lottie crashes on start

Description
I was using Lottie without a problem for a while but since 3-4 days it gives me error without any change. It crashes on start on a brand new android project as well after importing the Lottie.
It gives TypeError: Attempted to assign to readonly property.
Steps to Reproduce

Start a new react-native project
Install the latest Lottie as on the documentation
add  import LottieView from 'lottie-react-native'; to your App.js
Run react-native run-android

Versions
"dependencies": {
    "lottie-ios": "^3.1.9",
    "lottie-react-native": "^3.5.0",
    "react": "16.13.1",
    "react-native": "0.63.4"
  },
  "devDependencies": {
    "@babel/core": "7.12.10",
    "@babel/runtime": "7.12.5",
    "@react-native-community/eslint-config": "1.1.0",
    "babel-jest": "25.5.1",
    "eslint": "6.8.0",
    "jest": "25.5.4",
    "metro-react-native-babel-preset": "0.59.0",
    "react-test-renderer": "16.13.1"
  },

Android 10 API 29
Also tried on actual device with a lot of linking/rerunning/cleaning the project/restarting everything combinations.

Hi guys

Hi guys

I solved it. It is silly why it works but I was trying to debug the LottieView file in lottie-react-native/lib/LottieView.js just to see what breaks it. And this file was all one line so I made it parsed with prettier and actually without any change it worked.

I solved it. It is silly why it works but I was trying to debug the LottieView file in lottie-react-native/lib/LottieView.js just to see what breaks it. And this file was all one line so I made it parsed with prettier and actually without any change it worked.

Hi, I have encountered same problem. Actually, just need to reload your simulator/app & it will work just fine.

I had the same problem but i don't know what the error was, i saw this method from youtube and i have followed it and had the same problem and tried to follow the video but couldn't solve the problem either
import React from "react";
import { View } from "react-native";
import LottieView from 'lottie-react-native'
export default class Splash extends React.Component{
render(){
return (

<LottieView
source={require('../Asset/Lottie/69069-white-hand.json')}
loop={true}
autoPlay={true}
            />
        </View>
    )
}

}

I have then same issue. Restarting expo helps to get rid of the error. But then the screen with the lottie file will crash the app. Any ideas?

I'm having the same issue, restarting the expo app does not solve the problem.

Any news?

Seeing the same problem a year later. @Twos22 any luck fixing it? I tried a few lottie json files (some online) and still got the same crash. Thanks!


Added leetcode solution 185

Related Issue #3130
[Cite any related issue(s) this pull request addresses. If none, simply state "None”]
Description
[Please include a brief description of the changes or features added]
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Security enhancement
[ ] Other (specify): _______________

Screenshots / Videos (if applicable)

[Attach any relevant screenshots or videos demonstrating the changes]
Checklist

[ ] I have performed a self-review of my code.
[ ] I have read and followed the Contribution Guidelines.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have followed the code style guidelines of this project.
[ ] I have checked for any existing open issues that my pull request may address.
[ ] I have ensured that my changes do not break any existing functionality.
[ ] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[ ] I have read the resources for guidance listed below.
[ ] I have followed security best practices in my code changes.

Additional Context
[Include any additional information or context that might be helpful for reviewers.]
Resources for Guidance
Please read the following resources before submitting your contribution:

[ ] Code Harbor Hub Community Features
[ ] Docusaurus Documentation
[ ] React.js Documentation
[ ] Markdown Guide
[ ] MDX Documentation
[ ] Mermaid Documentation

Resources for DSA Features on Our Site:

[ ] Tabs: Switch Languages
[ ] Line Numbering
[ ] Math Equations

Contribution Guidelines
Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:
Issue Creation

Limit on Issues:

Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.

Contribution Levels

Basic Contributions:

This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
For these tasks, issues will be assigned the level1 label.

Acknowledging Hard Work:

If a contributor puts in significant effort on a task, the issue will be upgraded to level2. This is our way of recognizing and appreciating extra effort.

Feature Additions and Component Work:

Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
The more complex and valuable the contribution, the higher the level assigned.

Level Definitions

Level1:

Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.

Level2:

Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.

Level3:

Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.

We look forward to your contributions and appreciate your effort in helping us improve the project!

Hey @Utsavladia Please find your own issue don't raise the same issue again(#3130). I have already raised the issue in #3096 regarding thesolution of leetcode question - 185 @Ajay-Dhangar why did you assign him the same issue and you also assigned the same issue to @pallasivasai as well. What is happening??


Exclude failure test on Macosx with jdk11 and up

Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

related #1267


multiple bind_volume for a a container : conflicting mount point

Hello,
I am trying to deploy a gitlab ce docker image in a bosh deployment.
The docker image is designed with 3 volumes, for log / config / data disctinct externalization (in our case, i expected 3 subdirs mountpoints in /var/vcap/store/containers/gitlab)
It seems the docker launch job-propertie.sh script uses a single directory for the 3 volumes
# Create a bind mount to a directory
export gitlab_bind_volumes="--volume=${CONTAINERS_STORE_DIR}/gitlab:/etc/gitlab --volume=${CONTAINERS_STORE_DIR}/gitlab:/var/log/gitlab --volume=${CONTAINERS_STORE_DIR}/gitlab:/var/opt/gitlab"

Here the bosh manifest snippet for the gitlab docker image
      containers:
        - name: gitlab
          image: "gitlab/gitlab-ce:rc"
          hostname: "gitlab.example.com"
          #command: "--dir /var/lib/redis/ --appendonly yes"
          bind_ports:
            - "80:80"
            - "443:443"
            - "2222:22"
          bind_volumes:
            - "/etc/gitlab"
            - "/var/log/gitlab"
            - "/var/opt/gitlab"
          memory: "2024m"

Not sure you report on the right project? This project here is about Docker-based services. It basically includes a generic service broker for CF through which CF users can instantiate services (from a limited/prepared list of Docker images following the containers-broker contract - at present 19, e.g. Postgres, MariaDB, RabbitMQ, Redis, InfluxDB, Spark, etc.) and bind their apps to it.

My issue is on the basic container support of this project (not the cf-broker part), i am using release 23
https://github.com/cloudfoundry-community/docker-boshrelease/blob/master/CONTAINERS.md
So i think its the right project

I think this issue might be best raised in the https://github.com/cloudfoundry-community/cf-containers-broker project where the configuration is being used. Also, if you want to help debug why this is generating a bad docker command then that's the code base.

Sorry, that's wrong of me. Reading the bosh release now.

https://github.com/cloudfoundry-community/docker-boshrelease/blob/master/jobs/containers/templates/bin/job_properties.sh.erb#L220-L223 is the code that's trying to create your bind volumes

correct
<% unless container['bind_volumes'].nil? || container['bind_volumes'].empty? %>
# Create a bind mount to a directory
export <%= container['name'] %>_bind_volumes="<%= Array(container['bind_volumes']).join(',').split(',').map { |vol| "--volume=${CONTAINERS_STORE_DIR}/#{container['name']}:#{vol}" }.join(' ') %>"
<% end %>

The local dir location is only based on container name in /var/vcap/store/containers. Should find a way to give dedicated directory per bind volume.
Maybe the manifest syntax could be extended to specify both local dir and container dir, like this
          bind_volumes:
            - "etc:/etc/gitlab"
            - "log:/var/log/gitlab"
            - "data:/var/opt/gitlab"

What about changing
"--volume=${CONTAINERS_STORE_DIR}/#{container['name']}:#{vol}"

To
"--volume=${CONTAINERS_STORE_DIR}/#{container['name']}#{vol}:#{vol}"

not sure as vol is a path (/var/opt/gitlab). This would directly map the this path locally. And i think docker expects the mount dir to be created before...

So we just need to create the host dirs beforehand?
On Thu, Jan 7, 2016 at 12:44 AM, Pierre Oblin<EMAIL_ADDRESS>wrote:

not sure as vol is a path (/var/opt/gitlab). This would directly map the this path locally. And i think docker expects the mount dir to be created before...
Reply to this email directly or view it on GitHub:
https://github.com/cloudfoundry-community/docker-boshrelease/issues/45#issuecomment-169598913

yes could try this.
Anyway the whole purpose of docker is to map container directories/ports to custom host ones.
Guess we should not propagate internal container directories in bosh host
@frodenas what do you think ? could we extend the bind-volume syntax to specify a local directory name?

I don't see a problem with borrowing the internal path for use within the containers' private set of host paths. Also makes the configuration simple; and backwards compatible.
Do you see issues?
On Thu, Jan 7, 2016 at 10:57 AM, Pierre Oblin<EMAIL_ADDRESS>wrote:

yes could try this.
Anyway the whole purpose of docker is to map container directories/ports to custom host ones.
Guess we should not propagate internal container directories in bosh host
@frodenas what do you think ? could we extend the bind-volume syntax to specify a local directory name?
Reply to this email directly or view it on GitHub:
https://github.com/cloudfoundry-community/docker-boshrelease/issues/45#issuecomment-169773440

Using the internal path is the pattern I used for the cf-containers-broker.
If you're going to append the #{vol} to the volume directive (as @drnic suggested), the control script must also create the appropriate host directories (docker deprecated the auto-creation of missing host paths in v1.9).

Ok thanks for the pointers
The only issue i can see is the coupling to internal container directory. For example, we could expect to add bosh logsearch shipper to collect the logs mounted, and he d be nice to not change the log collection configuration if the docker container log location changes.
On the other side, the approach you both suggest keeps manifest backward compatibility (only manifest, as persistent directory location will change when upgrading the release, implying "optical" dataloss ...).

we have started the PR for the fix suggested. https://github.com/cloudfoundry-community/docker-boshrelease/compare/master...Orange-OpenSource:fix-multi-volume?expand=1
Remain the data migration from 23 location to release 24 location. Probably a drain script with file tag (migrated_from_23), ensuring this is applied only once. We could propose a default move of the data from /var/vcap/store/containers/ to the first volume mount point ...
cc @fbonelle

Any updates on this?

+1, any updates on this?

@Onke I've tried like this and it was working. Would you check that?
      volumes:
        - "/var/vcap/store/gitlab/etc/gitlab:/etc/gitlab"
        - "/var/vcap/store/gitlab/var/log/gitlab:/var/log/gitlab"
        - "/var/vcap/store/gitlab/var/opt/gitlab:/var/opt/gitlab"


Remove tabs from membersrvc.yaml

Description

Removed tab characters from membersrvc/membersrvc.yaml. See #1308. I also aligned the fourth column of the tables that had included tabs - that may have been why the tabs were inserted in the first place.
Motivation and Context

This fixes an issue on my system; The Tcl YAML parser does not allow tabs to appear outside of comments and quoted strings
How Has This Been Tested?

This change is so straightforward that I did not run the standard test suite, I assume it will pass the CI suite.
Checklist:

[x ] I have added a Signed-off-by
[ x] Either no new documentation is required by this change, OR I added new documentation
[ x] Either no new tests are required by this change, OR I added new tests
[ ] I have run goimports, go vet, and golint. I have cleaned up all valid errors and warnings in code I have added or modified. These tools may generate false positives.  The goal is clean, consistent, and readable code.

Signed-off-by: Bishop Brock<EMAIL_ADDRESS>

LGTM


Adds a shortest walking distance functionality for all transit routes…

…, and adjusts the format out the output to match.
Slightly messy code format - would benefit from moving into functions. Needs unit testing.
This is deployed to live api

Merging so we can use for demo. Should be revisited w/ testing and another set of eyes.


Fixed NameError: global name 'abspath' is not defined

Recently I've got this error:
Traceback (most recent call last):
  File "/Users/bjanda/.pyenv/versions/t/bin/jenkins-makejobs-git", line 9, in <module>
    load_entry_point('jenkins-autojobs==0.16.1', 'console_scripts', 'jenkins-makejobs-git')()
  File "/Users/bjanda/Downloads/OtherProjects/jenkins-autojobs/jenkins_autojobs/git.py", line 129, in _main
    main.main(argv[1:], config=config, create_job=create_job, list_branches=list_branches)
  File "/Users/bjanda/Downloads/OtherProjects/jenkins-autojobs/jenkins_autojobs/main.py", line 95, in main
    print('loading config from "%s"' % abspath(yamlfn))
NameError: global name 'abspath' is not defined

There is missing import or path to function. Please can you fix (merge) it ASAP.

Really sorry for that. I'll merge your patch and review my previous commits
for more errors as soon as I get home.

Thanks for the catch. Jenkins-autojobs 0.16.2 has been released with your fix.


Index Beluga documentation and sources

Please Add This Package to be indexed in the rosdistro.
beluga
The source is here:
https://github.com/Ekumen-OS/beluga
Checks

[x] All packages have a declared license in the package.xml
[x] This repository has a LICENSE file
[x] This package is expected to build on the submitted rosdistro

FYI @nahueespinosa @glpinuga. Note this is proactively indexing Beluga in all target distributions we will soon release binaries for. It is also a prerequisite to request a release repository (as documented).

New package review checklist

[x] At least one of the following must be present

[x] Top level license file: https://github.com/Ekumen-OS/beluga/blob/main/LICENSE
[ ] Per package license files:

[x] License is OSI-approved: Apache-2.0
[x] License correctly listed in package.xmls
[x] Public source repo: https://github.com/Ekumen-OS/beluga
[x] Source repository contains ROS packages
[x] Each package meets REP-144 naming conventions

@clalancette the sync is out!


Move datasets repository from dirty_cat to skrub

Describe the bug
Move https://github.com/dirty-cat/datasets to skrub repository.
Steps/Code to Reproduce
/
Expected Results
Some links will probably have to be fixed, for instance in the examples.
Actual Results
/
Versions
/

Done!


nft.go -> minting token

### Tasks
- [x] address to send token to
- [x] config env variable to reduce spammed contract calls
- [x] delegated call to OZ Defender relayer
- [ ] geth integration

This ticket is being modified per new discussion around batteries not included vs batteries included. See https://www.notion.so/labdao/Web3-UI-52899d57a153476fb25178fd76f01c0e for more details

[ ] web3 wallet integration with geth
[ ] user pays gas fees to call contract
[ ] auto message for option to upgrade to JupyterHub for gas-free minting


Cannot perform transcription, permission error.

Error executing Whisper: Error: Command failed: "/Users/devopt/Documents/IA-software/assistant/whisper/main" -m "/Users/devopt/Documents/IA-software/assistant/whisper/models/ggml-model-whisper-base.bin" -f "/var/folders/zh/2d746fqj511d8__4d1h7xjr80000gn/T/62c57b26-7404-47f3-80ed-4fc80b8c4cf5.wav" -l "es" -nt
/bin/sh: /Users/devopt/Documents/IA-software/assistant/whisper/main: Permission denied
at checkExecSyncError (node:child_process:890:11)
at execSync (node:child_process:962:15)
at handleAudioMessageWithWhisperLocal (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/audio-message/whisper-local.ts:12:31)
at handleAudioMessage (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/audio-message/index.ts:22:38)
at async generateCompletionWithBing (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/llm-models/generate-completion-with-bing.ts:21:32)
at async getCompletionWithBing (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/llm-models/completion-bing.ts:39:24)
at async handleMessage (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/message/index.ts:19:32)
at async Client.<anonymous> (file:///Users/devopt/Documents/IA-software/assistant/src/clients/whatsapp.ts:68:16) {

status: 126,
signal: null,
output: [
null,
'',
'/bin/sh: /Users/devopt/Documents/IA-software/assistant/whisper/main: Permission denied\n'
],
pid: 34020,
stdout: '',
stderr: '/bin/sh: /Users/devopt/Documents/IA-software/assistant/whisper/main: Permission denied\n'
}
Error: Error executing Whisper
at handleAudioMessageWithWhisperLocal (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/audio-message/whisper-local.ts:20:15)
at handleAudioMessage (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/audio-message/index.ts:22:38)
at async generateCompletionWithBing (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/llm-models/generate-completion-with-bing.ts:21:32)
at async getCompletionWithBing (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/llm-models/completion-bing.ts:39:24)
at async handleMessage (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/message/index.ts:19:32)
at async Client. (file:///Users/devopt/Documents/IA-software/assistant/src/clients/whatsapp.ts:68:16)
Error: Error transcribing audio
at handleAudioMessage (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/audio-message/index.ts:26:19)
at async generateCompletionWithBing (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/llm-models/generate-completion-with-bing.ts:21:32)
at async getCompletionWithBing (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/llm-models/completion-bing.ts:39:24)
at async handleMessage (file:///Users/devopt/Documents/IA-software/assistant/src/handlers/message/index.ts:19:32)
at async Client. (file:///Users/devopt/Documents/IA-software/assistant/src/clients/whatsapp.ts:68:16)

Is there any model inside whisper/models with the name of ggml-model-whisper-base.bin?

Should be fixed with #267


feat: Updated Azure.AppService.AvailabilityZone

PR Summary
Fixes #2986
Updated Azure.AppService.AvailabilityZone with default reason.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

Other code changes

[ ] Unit tests created/ updated
[ ] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

Ready for review @BernieWhite.


Update kube version to test against to 0.16.2

e2e has been failing, can you take a look @vishh?

@vmarmol: E2e passes now.

LGTM


SIGN_UP_BUTTON DESIGN. Please design this Sign-up button...

Inline with our "session of Buttons", We would be building different kinds of buttons..
Design a Button that looks like the button in this image...
Create a file "SIGN_UP_BUTTON_BY_YOUR_NAME.html" in the modules/buttons folder.
Use simple HTML and CSS to create the button. You can use the interface development https://kwickerhub.com (This project) or you can write the lines of code yourself.
Step by Step Guide.

Fork this project(Use the 'fork' button in the top right corner) and Clone your Fork.
git clone https://github.com/YOUR_USERNAME/frontend

Open your code Editor and Create a file "SIGN_UP_BUTTON_BY_YOUR_NAME.html" in the "modules/buttons" folder of this project you just cloned. No need to create head, title and body tags, Just Add a div tag with some embedded style(i.e use the style tag) and the script tag where necessary.
If you want to add an image resource, please add it in the folder "modules/buttons/images_and_icons". We recommend you use an svg for your image/icon.

Push your Code: You need to push your recent changes back to the cloud. Use the command below in the main directory of this Repository

git push origin dev
or use a GUI tool to avoid mistakes or complexity. LOL.

Make you Pull Request... if you do not know how to go about it, Just visit your fork on GitHub and you would see the button/suggestion to make a pull request to this project(the upstream)

Good-luck.
You can check out examples from the "modules/buttons" folder.
For some additional info, You should read the instructions.txt file in "buttons" folder.

I am interested to work on this issue under Quine. So please assign me this issue to me.

Assign me this issue

Good evening from the corner of the world.
Please that's a general issues... Just start and make a pull request don't
wait for the "assigning"👍
On Jun 14, 2023 16:25, "harshitcompcode" @.***> wrote:
Assign me this issue
—
Reply to this email directly, view it on GitHub
https://github.com/KwickerHub/frontend/issues/210#issuecomment-1591471299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOKWIBNR6YW2LOC46GYGMHLXLHJV3ANCNFSM6AAAAAAXBJJHPM
.
You are receiving this because you authored the thread.Message ID:
@.***>


How to transparent telescope ?

Question or Suggestion

Set borderless_telescope = false inside the setup() function in your config 🙂

Thank you very much ! 🙂


createServerClient deprecated?

Hey there!  I'm noticing that this line has been marked deprecated in @supabase/ssr.  It says the get/set/remove needs to be replaced with getAll/setAll and that the current method won't be supported in the next release.  I haven't dug in much further but wanted to raise the issue here as soon as I noticed it.
https://github.com/vercel/nextjs-subscription-payments/blob/25a19504c85a2353f23e907521d0cdb1979c66d6/utils/supabase/server.ts#L10C10-L10C28

Ported the latest code over from the Supabase docs and opened a PR :)

I have updated my middleware (updateSession) as suggested.  I am getting intermittent 502 errors, which I can resolve by deleting cookies for the site and re-logging on.  When in the 502 'dead-end', if I comment out
cookiesToSet.forEach(({ name, value, options }) =>
            supabaseResponse.cookies.set(name, value, options),
          );

The 502 error disappears and the page renders.  I have spent hours trying to catch errors in ever more granular ways but I'm none the wiser.  Every solution involves preventing a set cookies call in some way.

Discussion here. https://github.com/orgs/supabase/discussions/30185


Does this work with todo comments with assignees?

The eslint unicorn plugin allows also specifying an assignee to the todos.
Is this action able to parse those todo comments too?
Examples:
// TODO @cseas [2019-11-15]: Refactor this code before the sprint ends.
// Todo: @cseas [2019-11-15]: Refactor this code before the sprint ends.

Currently, this pattern of TODO comments is not supported.
However, we plan to review and enhance the functionality to include parsing such patterns in future versions.

Supported in v2.1.0.
https://github.com/aki77/expiring-todo-comments-action/releases/tag/v2.1.0


Design how the different work item types will be saved in our existing dataverse structure

Currently, our Dataverse assumes there is only one work item type and value per Product. After working on the dashboard aggregation data we realized this is not correct and that we need different work item types to track different type of information.
The purpose of this issue is to come up with a design on how we are going to reflect that design into our existing Dataverse

I have created this document for the chosen design and other discarded alternatives.

I added the new column in Service Profile, Product Profile and Base Workflow tables


ST_MGCN

Windows 10　无GPU,
python==3.6
tensorflow==1.13
Keras==2.2.4
h5py==2.9.0
UCTB==0.3.0
运行文件：UCTB/Experiments/ST_MGCN/bike_trial.py 报错：
想请问一下原因？一定要使用GPU吗？
Using TensorFlow backend.
2021-10-09 18:10:20.332752: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
[2021-10-09 18:10:20] WARNING (tensorflow/MainThread) From C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\framework\op_def_library.py:263:
colocate_with (from tensorflow.python.framework.ops) is deprecated and will be removed in a future version.
Instructions for updating:
Colocations handled automatically by placer.
[2021-10-09 18:10:20] WARNING (tensorflow/MainThread) From C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model\ST_MGCN.py:86: dense (from tensorflow.python.layers.core) is deprecated and will be removed in a future version.
Instructions for updating:
Use keras.layers.dense instead.
[2021-10-09 18:10:20] WARNING (tensorflow/MainThread) From C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\keras\backend.py:4010: calling dropout (from tensorflow.python.ops.nn_ops) with keep_prob is deprecated and will be removed in a future version.
Instructions for updating:
Please use `rate` instead of `keep_prob`. Rate should be set to `rate = 1 - keep_prob`.
[2021-10-09 18:10:21] WARNING (tensorflow/MainThread) From C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\ops\math_ops.py:3066: to_int32 (from tensorflow.python.ops.math_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.cast instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/multi_gcl/gcl_0/weights:0 is illegal; using CGRNN_Graph0/multi_gcl/gcl_0/weights_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/multi_gcl/gcl_0/biases:0 is illegal; using CGRNN_Graph0/multi_gcl/gcl_0/biases_0
instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/dense/kernel:0 is illegal; using CGRNN_Graph0/dense/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/dense_1/kernel:0 is illegal; using CGRNN_Graph0/dense_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/lstm/kernel:0 is illegal; using CGRNN_Graph0/lstm/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/lstm/recurrent_kernel:0 is illegal; using CGRNN_Graph0/lstm/recurrent_kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/lstm/bias:0 is illegal; using CGRNN_Graph0/lstm/bias_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/multi_gcl/gcl_0/weights:0 is illegal; using CGRNN_Graph1/multi_gcl/gcl_0/weights_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/multi_gcl/gcl_0/biases:0 is illegal; using CGRNN_Graph1/multi_gcl/gcl_0/biases_0
instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/dense/kernel:0 is illegal; using CGRNN_Graph1/dense/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/dense_1/kernel:0 is illegal; using CGRNN_Graph1/dense_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/lstm_1/kernel:0 is illegal; using CGRNN_Graph1/lstm_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/lstm_1/recurrent_kernel:0 is illegal; using CGRNN_Graph1/lstm_1/recurrent_kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/lstm_1/bias:0 is illegal; using CGRNN_Graph1/lstm_1/bias_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/multi_gcl/gcl_0/weights:0 is illegal; using CGRNN_Graph2/multi_gcl/gcl_0/weights_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/multi_gcl/gcl_0/biases:0 is illegal; using CGRNN_Graph2/multi_gcl/gcl_0/biases_0
instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/dense/kernel:0 is illegal; using CGRNN_Graph2/dense/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/dense_1/kernel:0 is illegal; using CGRNN_Graph2/dense_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/lstm_2/kernel:0 is illegal; using CGRNN_Graph2/lstm_2/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/lstm_2/recurrent_kernel:0 is illegal; using CGRNN_Graph2/lstm_2/recurrent_kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/lstm_2/bias:0 is illegal; using CGRNN_Graph2/lstm_2/bias_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name dense/kernel:0 is illegal; using dense/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name dense/bias:0 is illegal; using dense/bias_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name dense_1/kernel:0 is illegal; using dense_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name dense_1/bias:0 is illegal; using dense_1/bias_0 instead.
Bike NYC ST_MMGCN_DCI_K1L1_V_F5
3818
No model found, start training
Running Operation ('train_op',)
Traceback (most recent call last):
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1334, in _do_call
    return fn(*args)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1319, in _run_fn
    options, feed_dict, fetch_list, target_list, run_metadata)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1407, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: You must feed a value for placeholder tensor 'Placeholder_3' with dtype float and shape [?,28]
         [[{{node Placeholder_3}}]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "ST_MGCN_Obj.py", line 122, in <module>
    batch_size=int(args['BatchSize']))
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model_unit\BaseModel.py", line 186, in fit
    op_names=op_names)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model_unit\BaseModel.py", line 91, in _run
    outputs = self._session.run(output_tensor_list, feed_dict=feed_dict_tf)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 929, in run
    run_metadata_ptr)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1152, in _run
    feed_dict_tensor, options, run_metadata)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1328, in _do_run
    run_metadata)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1348, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: You must feed a value for placeholder tensor 'Placeholder_3' with dtype float and shape [?,28]
         [[node Placeholder_3 (defined at C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model\ST_MGCN.py:110) ]]

Caused by op 'Placeholder_3', defined at:
  File "ST_MGCN_Obj.py", line 102, in <module>
    ST_MGCN_Obj.build()
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model\ST_MGCN.py", line 110, in build
    external_input = tf.placeholder(tf.float32, [None, self._external_dim])
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\ops\array_ops.py", line 2077, in placeholder
    return gen_array_ops.placeholder(dtype=dtype, shape=shape, name=name)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\ops\gen_array_ops.py", line 6833, in placeholder
    "Placeholder", dtype=dtype, shape=shape, name=name)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\util\deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\framework\ops.py", line 3300, in create_op
    op_def=op_def)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\framework\ops.py", line 1801, in __init__
    self._traceback = tf_stack.extract_stack()

InvalidArgumentError (see above for traceback): You must feed a value for placeholder tensor 'Placeholder_3' with dtype float and shape [?,28]
         [[node Placeholder_3 (defined at C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model\ST_MGCN.py:110) ]]

Windows 10　无GPU, python==3.6 tensorflow==1.13 Keras==2.2.4 h5py==2.9.0 UCTB==0.3.0 运行文件：UCTB/Experiments/ST_MGCN/bike_trial.py 报错： 想请问一下原因？一定要使用GPU吗？
Using TensorFlow backend.
2021-10-09 18:10:20.332752: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
[2021-10-09 18:10:20] WARNING (tensorflow/MainThread) From C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\framework\op_def_library.py:263:
colocate_with (from tensorflow.python.framework.ops) is deprecated and will be removed in a future version.
Instructions for updating:
Colocations handled automatically by placer.
[2021-10-09 18:10:20] WARNING (tensorflow/MainThread) From C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model\ST_MGCN.py:86: dense (from tensorflow.python.layers.core) is deprecated and will be removed in a future version.
Instructions for updating:
Use keras.layers.dense instead.
[2021-10-09 18:10:20] WARNING (tensorflow/MainThread) From C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\keras\backend.py:4010: calling dropout (from tensorflow.python.ops.nn_ops) with keep_prob is deprecated and will be removed in a future version.
Instructions for updating:
Please use `rate` instead of `keep_prob`. Rate should be set to `rate = 1 - keep_prob`.
[2021-10-09 18:10:21] WARNING (tensorflow/MainThread) From C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\ops\math_ops.py:3066: to_int32 (from tensorflow.python.ops.math_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.cast instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/multi_gcl/gcl_0/weights:0 is illegal; using CGRNN_Graph0/multi_gcl/gcl_0/weights_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/multi_gcl/gcl_0/biases:0 is illegal; using CGRNN_Graph0/multi_gcl/gcl_0/biases_0
instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/dense/kernel:0 is illegal; using CGRNN_Graph0/dense/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/dense_1/kernel:0 is illegal; using CGRNN_Graph0/dense_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/lstm/kernel:0 is illegal; using CGRNN_Graph0/lstm/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/lstm/recurrent_kernel:0 is illegal; using CGRNN_Graph0/lstm/recurrent_kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph0/lstm/bias:0 is illegal; using CGRNN_Graph0/lstm/bias_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/multi_gcl/gcl_0/weights:0 is illegal; using CGRNN_Graph1/multi_gcl/gcl_0/weights_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/multi_gcl/gcl_0/biases:0 is illegal; using CGRNN_Graph1/multi_gcl/gcl_0/biases_0
instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/dense/kernel:0 is illegal; using CGRNN_Graph1/dense/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/dense_1/kernel:0 is illegal; using CGRNN_Graph1/dense_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/lstm_1/kernel:0 is illegal; using CGRNN_Graph1/lstm_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/lstm_1/recurrent_kernel:0 is illegal; using CGRNN_Graph1/lstm_1/recurrent_kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph1/lstm_1/bias:0 is illegal; using CGRNN_Graph1/lstm_1/bias_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/multi_gcl/gcl_0/weights:0 is illegal; using CGRNN_Graph2/multi_gcl/gcl_0/weights_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/multi_gcl/gcl_0/biases:0 is illegal; using CGRNN_Graph2/multi_gcl/gcl_0/biases_0
instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/dense/kernel:0 is illegal; using CGRNN_Graph2/dense/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/dense_1/kernel:0 is illegal; using CGRNN_Graph2/dense_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/lstm_2/kernel:0 is illegal; using CGRNN_Graph2/lstm_2/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/lstm_2/recurrent_kernel:0 is illegal; using CGRNN_Graph2/lstm_2/recurrent_kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name CGRNN_Graph2/lstm_2/bias:0 is illegal; using CGRNN_Graph2/lstm_2/bias_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name dense/kernel:0 is illegal; using dense/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name dense/bias:0 is illegal; using dense/bias_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name dense_1/kernel:0 is illegal; using dense_1/kernel_0 instead.
[2021-10-09 18:10:23] INFO (tensorflow/MainThread) Summary name dense_1/bias:0 is illegal; using dense_1/bias_0 instead.
Bike NYC ST_MMGCN_DCI_K1L1_V_F5
3818
No model found, start training
Running Operation ('train_op',)
Traceback (most recent call last):
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1334, in _do_call
    return fn(*args)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1319, in _run_fn
    options, feed_dict, fetch_list, target_list, run_metadata)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1407, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: You must feed a value for placeholder tensor 'Placeholder_3' with dtype float and shape [?,28]
         [[{{node Placeholder_3}}]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "ST_MGCN_Obj.py", line 122, in <module>
    batch_size=int(args['BatchSize']))
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model_unit\BaseModel.py", line 186, in fit
    op_names=op_names)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model_unit\BaseModel.py", line 91, in _run
    outputs = self._session.run(output_tensor_list, feed_dict=feed_dict_tf)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 929, in run
    run_metadata_ptr)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1152, in _run
    feed_dict_tensor, options, run_metadata)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1328, in _do_run
    run_metadata)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\client\session.py", line 1348, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: You must feed a value for placeholder tensor 'Placeholder_3' with dtype float and shape [?,28]
         [[node Placeholder_3 (defined at C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model\ST_MGCN.py:110) ]]

Caused by op 'Placeholder_3', defined at:
  File "ST_MGCN_Obj.py", line 102, in <module>
    ST_MGCN_Obj.build()
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model\ST_MGCN.py", line 110, in build
    external_input = tf.placeholder(tf.float32, [None, self._external_dim])
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\ops\array_ops.py", line 2077, in placeholder
    return gen_array_ops.placeholder(dtype=dtype, shape=shape, name=name)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\ops\gen_array_ops.py", line 6833, in placeholder
    "Placeholder", dtype=dtype, shape=shape, name=name)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\util\deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\framework\ops.py", line 3300, in create_op
    op_def=op_def)
  File "C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\tensorflow\python\framework\ops.py", line 1801, in __init__
    self._traceback = tf_stack.extract_stack()

InvalidArgumentError (see above for traceback): You must feed a value for placeholder tensor 'Placeholder_3' with dtype float and shape [?,28]
         [[node Placeholder_3 (defined at C:\LSHApp\anaconda3\envs\tfv1\lib\site-packages\UCTB\model\ST_MGCN.py:110) ]]

您好：
UCTB支持CPU以及GPU运行，从您的报错原因上来看，是在运行时喂入external_input数据出现了问题。


Error: search AndroidManifest.xml in gradle project

For gradle project, AndroidManifest.xml file normally placed in app/src/main/AndroidManifest.xml but this library always find in app/AndroidManifest.xml then never see it.

same here.

should be duplicate of #53


[Tool] update text_content_list in utilities

related PR: https://github.com/Azure/azure-sdk-for-python/pull/25264

/check-enforcer override


Loose Connection

in your code the bot looses connection, it gets a on_close and exits

Can you be more specific about what causes the connection to be lost?

thats a problem to be more specific, because the bot looses connection after a few seconds, there isnt coming any message why, just closes the connection

Hmm. Can you provide your system information and the output log when you run testsocket.py?

Sorry, it was my mistake. I had sending "2::" when receiving "2::" with a wrong intent so it didnt answer "2::".
Your Code is working well
sorry

Ok, I've never had a problem with the "2::" ping response, but that's apparently what happens if the ping response gets sent incorrectly. Thanks for the information, marking this as closed.


Pretty format timestamps in router logs

Currently timestamps for the gorouter logs appear to be formatted in epoch time, this is mildly inconvenient for humans as we have to go and convert the timestamps. It would be nice to have them formatted in ISO 8601 notation as that is both easily parseable by computers and humans alike.
Most CF components use this format.

Hello,
Currently gorouter.log includes messages with both timestamp formats:
{"timestamp":"1469578199.066300869","source":"vcap.gorouter","message":"vcap.gorouter.proxy.request-handler.handling-websocket-request","log_level":1,"data":{"Host":"doppler.superman.cf-app.com:4443","Path":"/apps/6a64c663-651f-4cd2-8994-d31d4f381704/stream","RemoteAddr":"<IP_ADDRESS>:45270","Upgrade":"websocket","X-Forwarded-For":null,"X-Forwarded-Proto":null,"session":"4.149178"}}
[2016-07-27 00:09:59+0000] {timestamp:1469578199.066300869,source:vcap.gorouter,message:vcap.gorouter.proxy.request-handler.handling-websocket-request,log_level:1,data:{Host:doppler.superman.cf-app.com:4443,Path:/apps/6a64c663-651f-4cd2-8994-d31d4f381704/stream,RemoteAddr:<IP_ADDRESS>:45270,Upgrade:websocket,X-Forwarded-For:null,X-Forwarded-Proto:null,session:4.149178}}

It appears that we have duplicate log messages (one message uses both ISO 8601 and epoch). We consider this a bug and will fix this.
It is also strange that we're using both timestamp formats in one message. We'll probably pick one and remove the other. In terms of which timestamp format we'll use, it is not clear to me that there is a convention in CF currently; cloud_controller uses epoch.
{"timestamp":1469579302.272368,"message":"Statsd: cc.requests.outstanding:-1|c\ncc.requests.completed:1|c\ncc.http_status.2XX:1|c","log_level":"debug","source":"statsd.client","data":{},"thread_id":47367051452260,"fiber_id":47367032802760,"process_id":5497,"file":"/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.3.0/gems/statsd-ruby-1.2.1/lib/statsd.rb","lineno":254,"method":"send_to_socket"}

We have a story to dedup our logs here: https://www.pivotaltracker.com/story/show/127119107
As a result we may only use an epoch timestamp for some period. We have requested that the lager library we use support the ISO 8601 timestamp; when that lib is updated you'll see human readable gorouter logs.

@APShirley : Closing this PR because we have removed duplicate log msg with non-human readable timestamps.
Regards
Aaron && @shashwathi


Clean up Login/Languages Code

Description
This cleans up all code related to the Login, Languages, Landing project.
Specifically:

Removes all instances of TODO(#4705)
Removes loginAsGuest, which is now redundant since we login as a guest by default
Removes the usages of selectApplicantLanguage when it selects English, since this is now redundant.
Removes the LoginForm view and the ApplicantInformationView, which was just the language selection screen.

Release notes
None.
Checklist
General

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[ ] Created tests which fail without the change (if possible)

Not necessary; code cleanup

[ ] Extended the README / documentation, if necessary

Not necessary; code cleanup

User visible changes
None.
New Features
None.
Issue(s) this completes
Relates to #4705.

TODO: remove instances of the string loginForm


592 Fix CQL Value Tuples so that they are serializable with custom Json Converters

Fix for

#592

Also see discussion

#605

Value Tuples must have first item of type CqlTupleMetadata
Fixes value tuples by including its metadata as first item in the tuple. The metadata is stored as static property on the library and it contains the item names and types. At this stage only the item names are required for serialization, but it doesn't hurt to include the item types as well for future possibilities. (Also, it always adds value to see types in the generated c# code)
New types added to Hl7.Cql.Runtime:

class Hl7.Cql.Runtime.CqlTupleMetadata
class Hl7.Cql.Runtime.Serialization.CqlValueTupleJsonConverter
class Hl7.Cql.Runtime.Serialization.CqlValueTupleJsonConverterFactory

Libraries will have private static properties for the tuple metadata as follows:
    private static CqlTupleMetadata CqlTupleMetadata_FPVdJEEOUKFVhQPTfKhShUNO = new([typeof(IEnumerable<Practitioner>)], ["Practitioners"]);

and usage in the library is as follows:
// Note that CqlTupleMetadata is always the first type in a value tuple
public (CqlTupleMetadata, int? IdentifierCount)? Get_Prescriber_NPI_from_Claims(CqlContext context, IEnumerable<Claim> claim) {

   // Declaring a new value tuple
   (CqlTupleMetadata, IEnumerable<Practitioner> Practitioners)? aw_ = (CqlTupleMetadata_FPVdJEEOUKFVhQPTfKhShUNO, av_);

}

Serialization
A unit test was added, see CqlTupleTests in CoreTests project. The CqlValueTupleJsonConverterFactory must be added as a converter in the JsonSerializationOptions
Refactoring
The ExpressionToCSharpConverter was cleaned up, so that indentation parameters are carried between methods as a context type, instead of individual parameters. The context also needed an additional parameter to build tuple property names. This was necessary, so that TupleMetadataBuilder could be passed along.
The same cleanup was appied on CSharpLibrarySetToStreamsWriter, to reduce the parameter count being passed around, instead wrapping them up into contexts.
Also, libraries were indented with a mix of tabs and spaces. This was fixed to be using spaces consitently

Will fix compiler error soon

The SDK version need to be incremented when the generated c# changes significantly...

cc @and-hus

Thanks for the ping - looks interesting. I am just taking a closer look at it...

@baseTwo :
I am not sure if it's related to my own setup, but I am getting a weird error message like

when I trying to setup a simple unit test to verify our use-case...
Just added some CQL example for a nested tuple and compiled to a dll.
I am getting the error when loading the dll and trying to run the code like this:
[TestMethod]
public void ExpressionReturningNestedTuples_ResultCanBeSerialized()
{
    var file = @"Dlls/CqlNestedTupleTest-1.0.0.dll";
    var filePath = Path.GetFullPath(file);

    var asm = new AssemblyLoadContext("CqlNestedTupleTest");
    asm.LoadFromAssemblyPath(filePath);

    var ctx = FhirCqlContext.ForBundle();
    var result = asm.Run("CqlNestedTupleTest", "1.0.0", ctx);
    Assert.IsNotNull(result);

    result.TryGetValue("Result", out var obj);
    Assert.IsNotNull(obj);
    Assert.IsInstanceOfType(obj, typeof(ValueTuple));

    // serialization works out of the box
    //var str = JsonSerializer.Serialize(obj);
    //Assert.AreEqual("{\"status\":\"success\",\"result\":\"some result\"}", str);
}

This is the patch file to add the test:
0001-Add-unit-test-to-retrieve-tuple-across-assembly-boun.patch

It seems as if the code-generation creates only a private default constructor:
[System.CodeDom.Compiler.GeneratedCode(".NET Code Generation", "<IP_ADDRESS>")]
[CqlLibrary("CqlNestedTupleTest", "1.0.0")]
public partial class CqlNestedTupleTest_1_0_0 : ILibrary, ISingleton<CqlNestedTupleTest_1_0_0>
{
    private CqlNestedTupleTest_1_0_0() {}

@baseTwo It seems as if the code-generation creates only a private default constructor:
[System.CodeDom.Compiler.GeneratedCode(".NET Code Generation", "<IP_ADDRESS>")]
[CqlLibrary("CqlNestedTupleTest", "1.0.0")]
public partial class CqlNestedTupleTest_1_0_0 : ILibrary, ISingleton<CqlNestedTupleTest_1_0_0>
{
    private CqlNestedTupleTest_1_0_0() {}

That's correct. For performance reasons, libraries are accessible through a singleton property Instance on the library type. (see PR# 585. This has been applied on v1.0 too.

Why CqlTupleMetadata_FPVdJEEOUKFVhQPTfKhShUNO?  Are you still creating new types programmatically?
The purpose of shifting away from having tuple types dynamically generated was to prevent the awkwardness of having a separate Tuples assembly that was scoped to a particular build.  It created dependency management problems and was hard to operationalize in a system with many different libraries.
Shouldn't CqlTupleMetadata literally just be a string[]?  Tuples have Item1, Item2, and so on.  The only data you need is what the actual member name of Item1 was, so that define tuple: Tuple { x: 1, y: 2 } when translated into C#'s (1,2) tuple can remember that the names of those two Item props were x and y so they can be serialized at runtime.

@baseTwo
I am really sorry. I completely missed the discussion on #605 and I feel bad to throw in another idea so late in the process and after you already spent so much time to implement the current approach. :-(
But have you considered to represent the CQL Tuples in C# as a string-object dictionary (Dictionary<string, object>) instead of ValueTuples with the additional CqlMetadata entry for the field names?
Something along these lines:
Dictionary<string, object> tuple = new()
{
    { "status", "success" },
    { "result", "some result" },
    { "isOK", true },
    { "someNumber", 3045 },
    { "nestedTuple", new Dictionary<string, object>
    {
        { "nestedValue", "some nested Value"},
        { "2ndNestedValue", "another nested Value"}
    }}
};

From my perspective this would have multiple advantages over the current approach:

using C# native type in a standard way vs. ValueTuple with extra convention for the first element
doesn't require any extra types like CqlTupleMetadata
serializes directly to JSON, without additional serializer options
reduced complexity and therefore improved maintainability
easier to handle in consuming code
possible to define a type alias via using CqlTuple = System.Collections.Generic.Dictionary<string, object>;

I am not sure about the cons, especially with respect to performance or if it would conflict with general design decisions for the SDK.
If you're interested, I am happy to give it a try and provide some sample implementation via a separate PR - what do you think?

But have you considered to represent the CQL Tuples in C# as a string-object dictionary (Dictionary<string, object>) instead of ValueTuples with the additional CqlMetadata entry for the field names?

@EvanMachusak took this approach in an early version of this SDK but found that is was too slow. Many measures, by absence of a data definition language in CQL, produce and work with these anonymous tuples, so the use of a Dictionary versus direct properties becomes a burden. Evan might chime in if he wants to add more about his experience on using this approach.

Why CqlTupleMetadata_FPVdJEEOUKFVhQPTfKhShUNO? Are you still creating new types programmatically?

No, we luckily don't need to generate types anymore! But Paul needed a unique name for a shared instance of the metadata per library. It does not matter if other libraries use the same type of tuple with another instance of the same metadata however, the equality on Tuples takes care of that. It's just making sure you only need to create this metadata once for a type of tuple.

For the reviewers of the generated code: since this PR changes tabs into spaces in the generated code, you need to tell Github to ignore whitespace while making diffs like so:

But have you considered to represent the CQL Tuples in C# as a string-object dictionary (Dictionary<string, object>) instead of ValueTuples with the additional CqlMetadata entry for the field names?

@EvanMachusak took this approach in an early version of this SDK but found that is was too slow. Many measures, by absence of a data definition language in CQL, produce and work with these anonymous tuples, so the use of a Dictionary versus direct properties becomes a burden. Evan might chime in if he wants to add more about his experience on using this approach.

@ewoutkramer Great - thanks for the background info!

Mmmm....the auto-merge got me here. I reviewed this because I think this is a nice solution, but I think I really wanted @EvanMachusak to take a look at it too.  Seeing Evan's question above on whether this needs generated types (no), then if that was the only hesitancy Evan had, I think it is ok to proceed, but just want to make sure....


Adjust helm install command in managed public EKS directions to match…

… regular helm

Product Version(s):

Issue:

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

LGTM, merge when ready. Thanks!


Input crashes in RTL with uncaught exception in Chrome V69

Bug Report
In RTL, text input (Input, TextArea) crashes with uncaught exception:
TypeError
keyCombinations.map is not a function
This causes bad rendering behavior.
Steps
A clear and concise description of steps to reproduce the problem.
Use this example:
https://codesandbox.io/s/stardust-ui-example-p3n6j
See that text input both in RTL and LTR work normally.
Download Chrome V69
https://www.slimjet.com/chrome/google-chrome-old-version.php
See that when RTL is false, text input works normally. Then set it to true. See that any text input now causes an uncaught exception to be thrown.
Expected Result
Text input to work normally.
Actual Result
Uncaught exception causes crash.
Version
Chrome: Version 69.0.3497.92 (Official Build) (64-bit)
Stardust: Stardust UI @ 0.40.1
Testcase
N/A

getKeyDownHandlers expects keyCombinations to be an array:

But it can also be false:

That leads to an uncaught error:


Output obsolete snapshots to testResultsProcessor

Feature request
I'd like to be able to fail a build in Jenkins if there are any obsolete snapshots hanging around.  One thought was to get that information in the results processor and tell the suite to fail that way.
Not sure if anyone has found a way to do this with the current Jest build but it would be very helpful.

Yea, I think it makes sense to add such behavior on CI environments.

Should --ci do this by default?

Thoughts on doing this by default for --ci?

Should always do it

This is a legit feature request — not stale!

@fbartho would you be willing to send a PR for this? I would have thought the information was available already (since the reporter prints it), but I might be wrong


request : more toolbars

Hello !
So this is a pretty big request, and I don't know if it"s feasable, but here we are. I (and others before me) have asked in the Reaper forum for more toolbars, 16 being a limiting factor for some people, but there is no sign of any new toolbars being implemented natively in Reaper.
Question is : could it be something that SWS could provide via the extension ?
If so consider this message a new feature request :p !!!
xxxxxxx
louis

Sorry to say, but I'm rather sure it's on REAPER side to implement this and SWS can do nothing about it, so I'm closing this.
(@cfillion if you think otherwise feel free to reopen.)

ok thx :)


When loading a new Stencil file, old stencil(s) are still used until new option selected.

Describe the bug
When a new stencil JSON file is uploaded, the old stencils remain in effect until a new menu is selected. I changed the plug in at the top to reload, but I assume simply selecting a new stencil application would also have the same effect. I haven't tested as such.
To Reproduce
Have a stencil selected and ready to select IEDs. Click the 'Open' button and load a new stencil JSON file. Select IEDs and apply stencil. The original version of the stencil will still be used.
Expected behavior
When loading a new stencil file, it takes effect immediately.
Screenshots

System
Windows, MS Edge Version 131.0.2903.99 (Official build) (64-bit)

Quite right - it should reset the window, and leave no application selected. Fix soon.

This should be fixed now - thanks for reporting - the distribution has been updated, you may need to do a refresh with Ctrl + F5


buildreference, added 2017cu23

thanks @DiHo78, I saw https://github.com/sqlcollaborative/dbatools/pull/7170 and jumped on it ^_^

yeah, sorry, I was a bit stupid this morning. Sometimes it is better if I do not do 1000 things at the same time

ok, now I got the full picture
I think I can decline my PR then  :-D
because: https://github.com/sqlcollaborative/dbatools/pull/7172


There should be "Title" in placeof "sliders" while creating sliders

Bug report
Title
There should be "Title" in placeof "sliders". while creating sliders
Issue Description
Sliders is written where there should title
Preconditions
1. framework Version.v0.1.8

Steps to reproduce
1. step1: go to settings and click on Create Slider in slider grid

Expected result
Title should be coming in place of sliders

Actual result

Framework version : v0.1.8
fixed


brew --build-from-source fails to find gcc on Linux

brew tap fortran/lang && brew install fpm fails on Lubuntu Linux 21.10.  The error message recommends building from source, but brew --build-from-source fpm fails and recommends executing brew install gcc.  Executing the latter command puts gcc-12, g++-12, and gfortran in /home/linuxbrew/.linuxbrew/bin/ so I created soft links as follows:
cd /home/linuxbrew/.linuxbrew/bin/
ln -s gcc-12 gcc
ln -s g++-12 g++

after which brew install --build-from-source fpm works.  Any advice on how to tell Homebrew to use gcc-12 and g++-12 or how to tell Homebrew to create the aforementioned soft links so that I don't have to create them by hand?
In each of the above commands, I actually used -s in place of --build-from-source.  The two are equivalent.

This might be a question best asked at https://github.com/orgs/Homebrew/discussions


wiki quickie

In order to finish off the readme (which will be shorter than it currently is), I need to first have three wiki pages done (because the readme will point to them). They are

[ ] Overview
[x] Backup
[ ] Implementing

Overview: like what is a user.js, why have one (migration, enforcement etc), thats its editable in a text editor, how it works (process - case sensitive, what happens with syntax errors, what happens with type mismatches, the relationship between user.js->prefs.js->about:config and that it is a ff start that uses it), and how to use it (as in it's one way - so comment out in js, reset in about:config ) etc. How comment // works etc.
Backup - basically where to find your profile folder and to back that up. backing up prefs is not enough. There are other objects that can be changed, such as sqlite files.
Implementation: where to put the user.js. Either use in a new profile, and how to switch to it. Or how to grab a portable etc. Also to read it and make changes before jumping in. That kind of thing.
The next page on troubleshooting is all done (but I could improve it later).
That's all. If anyone wants to draft one or all of these up, please do. I've been ignoring doing this for a week or so (semi-procrastinating), especially as I wanted to keep the issues down (closed 28, yay!). That and the sexy new headers and forms sections are awesome. We've been here 3 weeks, and done a LOT, seriously, a LOT - well done. These pages won't take that long, but I'm kinda dreading writing them all myself and from scratch. I would love some help. Just paste in here or pastebin, and I can format it.

Oh yeah. I don't need or want plagiarized copies, and I don't really want tons of links to what other people have. We should all know this stuff, and be able to write our own original version. Ideas on what to add are good (and we can always do a revision later). PK's has a section on different OS on where to find the profile folder. But we can do that from within FF as well. So anything typed up off the top of your head to get me/us started would be excellent.

HI,
Just a rough thing:
Find and backup your Firefox profile
Launch Firefox then follow the path : Open menu > Open Help Menu > Troubleshooting Information,
search for Profile Directory then click on "Open Directory",
your current profile will be opened in your file manager.
The profile name is ., e.g. fg8ets6y.default . Note that prefs.js and user.js stands there.
Backup the entire profile in a safe location.

Thanks @2glops - FYI: go to about:profiles .. there is a "open folder" button right there. I don't know of an easier or faster way

Right, as you wish.
But, from about:profiles it could be easy to get confused and not saving the right profile. You have to select the Root Directory folder of the profile in use.
From the troubleshooting information page, there is no such risk. And the page list a lot of useful informations about the profile in use, including Important Locked Preferences.

@2glops Yep, it's all good stuff. I haven't written it yet :) I was just showing you a faster way

if it helps, you guys can copy/paste whatever you want from my stuff here - no credit or link-back needed

I agree. We shouldn't re-invent the wheel. If someone has already done the work, why shouldn't we get some "inspiration" from that ;)

Yeah, look, this stuff is documented and written about a thousand times - I'm just not going to copypasta ad verbatim, plus we can do better than most of them (go read a dozen and make sure to cover everything to get the best combined info). I opened this issue, because it would be nice to finish it off and the readme, so all we have to focus on is the js.
I have a timetable in mind (for martin's article about us which will include the move, the big changes, and future plans). I also want a little space between that article (which will drive a LOT of people here) and the 6 weekly stable changelog articles. FF53 lands 18 April, so maybe about a week prior for the article at latest (that's 4 whole weeks away), and then 2 weeks later, a week after stable lands, comes our first "changelog" .. and then 6 weekly after that. If the article is even earlier, then the better.
I can probably whip up the three wikis and the readme in one lazy Saturday/Sunday arvo, review them the next day etc. So it's not a major. For some reason in my head I am procrastinating over it. It's like the last thing I want to do (and has been for weeks). I'm so not into writing them right now, I'll drag this on for a couple of weeks :)
If I don't write it (hint hint), if I am just an editor and review it (and we can all review it), then I don't really care - I only care about it's quality. These are straight-forward technical/how-tos, so there's not much to get wrong or indeed include. Take @atomGit 's bits as a starting base (we have his blessing) and GIT to it

Re: 2.2. Lock Prefs - why don't we link to http://kb.mozillazine.org/Locking_preferences ??
I mean I could copy it all into a Wiki page but I don't see the need for that.
There's no need to dumb this down (with pics etc) since only "advanced users" would/should lock prefs anyway and they should be able to read and understand all the necessary things to do from that mozillazine.

I haven't really gotten round to that section. And I'm going to need to leave some numbers open for some ideas I have. Using numbers so the sidebar orders nicely (there are other solutions to that though). I just threw that section 2 and some subsection titles as a filler.
My plan is (to keep the readme short) to link to the section 1's etc. That's stage 1.
Later, after we branch to lite-medium-hardened, then I want to set up running multiple concurrent profile info wikis etc - with recommendations to set different themes to easily recognise what profile you're in. And of course lock_prefs is on the cards as well. But first things first.

Ok, I'll link 2.2 to that mozillazine for now. We can always change it later if necessary.

@earthlng I'm using this issue just to get those 3 pages done, cuz you seem antsy about them xD .. when this is closed, I will be creating a "sticky wiki"

@earthlng Ahh, I see what u did .. that mozillazine is horrible .. this is the one: https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment

@earthlng https://github.com/ghacksuserjs/ghacks-user.js/wiki/3.1-Greasemonkey

also chucked this up : https://github.com/ghacksuserjs/ghacks-user.js/wiki/3.3-uBlock-Origin . there's also pages for noscript and umatrix

Very nice. But as always I hate the formatting ;)

I'd move the "You can test..." lines for the 1st and 3rd script on a newline.
The 2nd script could use some fewer TABs.
2nd title should be Conceal window.name without the 's'
1st script has a single " before history.length in description

I was expecting some explanation for Greasemonkey based on the title, IMO we should name it UserScripts.
And maybe add a recommendation to use Greasemonkey. I member you once said something on ghacks about Tampermonkey, but Idk what that was about.
Also we can use the Anchors to link to scripts directly in the user.js fe. Clear window.opener

ps. Idk about that regex line, maybe it'd be better to add an @exclusion line for https://www.google.com/recaptcha/ - probably needs some testing. I think pastebin has a captcha, at least it always bothered me with one.

go for it man - edit as you like. You're the code monkey :)

I obviously use it differently than you, but for what it's worth, here are mine:
no-remote-fonts: * true
* * * noop
behind-the-scene * 3p noop
behind-the-scene * 3p-frame noop

This is where you can add some insight. The uBo stuff, such as no-remote fonts helped me. See, I don;t even know the diff that "behind-the-scene" makes. So we can rather than add big sets, add separate lines like the font one and explain what they are

I was expecting some explanation for Greasemonkey based on the title, IMO we should name it UserScripts.

nvm, it's under Scripts and then Greasemonkey. It's fine

nah, good stuff man .. changed the name to User Scripts. But i'm not sure on what to put for a short intro. Greasemonkey for sure, but what else - tampermonkey?

Very nice. But as always I hate the formatting ;)
I'd move the "You can test..." lines for the 1st and 3rd script on a newline.
The 2nd script could use some fewer TABs.
2nd title should be Conceal window.name without the 's'
1st script has a single " before history.length in description

can't move to a new line, you have to use a new paragraph :-(
title fixed
extra " fixed
will try to fix tabs but i'll prolly get it all wrong

My 2 cents for implementing:
Clone or download the user.js at :
https://github.com/ghacksuserjs/ghacks-user.js
First of all, read carefully the user.js and the documentation. Some site breakage could or will happen.
Second, make changes to the user.js according to your needs and expectations. You can change values or comment out any pref.
Backup and find you profile-s :
https://github.com/ghacksuserjs/ghacks-user.js/wiki/1.2-Backing-Up
You can also create a new profile by lauching the profile manager with the command :
firefox -P
Now, be sure Firefox is closed and put the user.js file in your Firefox profile directory.
Re-start Firefox, that's all.
You can now check your main or most visited sites to identify if there is any breakage.

I already wrote the backup, all off the top of my head - as is my draft for the overview page and implementing (and it's that page that has the create new profile info, where to put the user.js etc).
I still think the best way for users is to jump right in (after reading the [warning] and [setup] tags as well as the three items specifically mentioned in the header section) - Create a new profile and then copy their existing profile into it - basically to clone it. Or just back it up. This way they have all their bookmarks and cookies and extensions all ready to go - etc which would be easier for them to use/test with. SFA breaks anyway, seriously, it like 5 prefs max (indexeddb, workers) and some custom ones like what to clear, urlbar/searchbar, session restore, maybe plugins - nothing really. There's nothing harmful in the js that can't be tweaked to sort out site breakage or lost functionality, and as for losing anything - lost history is no big deal (you can regenerate more!) and they were warned, so I'm not counting that. It's not like we wipe people's passwords - its a pretty tight but generous js IMO. Once we land branches then people will have even less to think about.

Nice job on the backup page, Pants. It's a bit excessive for my taste but I guess that makes sense if someone needs a tutorial on how to backup their profile. some nits if you don't mind:

wouldn't the first paragraph fit better under the Implementation?
the 3rd paragraph is a bit confusing and could be dropped completely. Why make it more complicated - tell them to backup the whole profile (as you did) and don't even mention the prefs.js.
fe. "if you know what you're doing, you can do otherwise" - if they are reading that page they probably don't know what they're doing

We should try to keep everything as short and relevant as possible. for example

Alternatively you can use the menu item ....

Isn't one way to find the profile directory enough?

The next wiki section, Implementation, outlines some methods you could use to test out the user.js and preferences, such as using your existing profile, or a copy of it, or a new one and whether to implement piecemeal or whole hog

I would delete everything after test out the user.js and preferences because if it's outlined in the next section you don't need to already mention it in this section.

Well, got to use simple/layman terms if possible, use pictures, lower the bar and all that - I hate to say that, but it's a reality. It's also why I'm not going to quantify statements now (after the edit I just did) such as just using pref.js or rolling back/migrating specific data files. We can just recommend ONE way. If someone is an expert, good on them.
Also, think of the 4 pages like a single article - linkage previous at start, link next at end. It's not that bad.

First paragraph rams home the profound effect it can have - thus to backup - warning & seque in one. I have shortened the paragraph
i wanted to mention that prefs.js is not enough as a backup. because a lot of places suggest that (if u know what you;re doing it can be done no worries, but I'm not going to publicly endorse it). But yeah, TMI. Have merged those paragraphs and trimmed the fat
added the about:support page info because @2glops mentioned it above, reason: it only shows the CURRENT profile (so users can't screw up). That said the about:profiles also says which is the profile in use... (3 minutes later)  .. yeah, kinda looks cleaner, but man, we're getting down to twitter lengths...
trimmed last paragraph

check it out

draft up: https://github.com/ghacksuserjs/ghacks-user.js/wiki/1.1-Overview . Yes its long, but it covers a lot. It's actually very succinct for what it covers and I don't think anything else comes near to it on the web. All written off the top of my head.

@Atavic don't confuse your quiki's with stiki's - I answered your q in the stiki. This quiki is a one off to get my A into G and finish the wiki section1

Nicely done with the Overview wiki page. I made 2 small changes
teaching is a strong word, how about this instead:

It will teach you how to protect your privacy ...
==> Our user.js helps to better understand how to protect ...

And there's one typo in the 2nd image: collasible

damn .. not sure if i can be bothered to recreate that pic

np, nobody will notice it :) and remember our motto ...

Having issues with creating new profiles. Selecting the directory doesn't create it in that dir, but the one above it. Seems weird. Yeah, working on Implementation section.

An idea: we could provide an opensearch.xml file which would search the issue tracker for a given pref.
It would be nicer if we had a logo for this user.js page but I guess we can either take your avatar or the gh favicon for now.

And why would you want a user.js?
It can help you to better understand how to protect your privacy ...

"a" user.js is really just a list of prefs normally, but "our" user.js can help to better understand blablabla

All the previous points start with "It can..", so consistency. Clearly ours is very informative, I don't think that needs to be said and it sounds a little whats-the-word .. skiteful (boastful). Any user.js can be a basis for learning, any preference could teach someone something - because people (assumption) will read what they say or experiment what they do. Ours is not exclusive in this department. Bloody awesome, but not exclusive.
Dunno why people would want to search the issue tracker (don't answer that) - the whole point is that the user.js (should) holds everything they need to know about each preference and the ramifications

https://github.com/ghacksuserjs/ghacks-user.js/wiki/1.3-Implementation
Finished. Implementation (and the wiki home page) are all I need to link to in the readme. The implementation page lays out all the steps and pages to read in order to use this in a sensible manner, especially for people not familiar with it.
Closing this, but post feedback if required. Now I just need to rewrite and clarify our readme: sans any technical info (that's what the wiki is for), it's more of a mission statement. It will be as short and sweet as I can get it. Thumbs up if you like my work xD


Change default input_type to null. Add some warning regarding TYPE_TEXT_FLAG_NO_SUGGESTIONS

Maintainer merge checklist

[ ] Title is descriptive/clear for inclusion in release notes.
[x] Applied a Component: xxx label.
[ ] Applied the api-deprecation or api-break label.
[ ] Applied the release-highlight label to be highlighted in release notes.
[ ] Added to the milestone version it was merged into.
[ ] Unittests are included in PR.
[x] Properly documented, including versionadded, versionchanged as needed.

Some info regarding this PR:

Issue https://github.com/kivy/kivy/issues/7337 has been introduced via https://github.com/kivy/kivy/pull/7231.
Some (major) soft keyboard vendors are de-facto ignoring the TYPE_TEXT_FLAG_NO_SUGGESTIONS, so the workaround of disabling the suggestions doesn't work.
There are some issues on SDL regarding IME and SDL_TEXTEDITING, that we should track: https://github.com/libsdl-org/SDL/issues/4847, https://github.com/libsdl-org/SDL/issues/3385, https://github.com/libsdl-org/SDL/issues/3377
input_type is a great addition and is a step forward to support non-latin languages.
Some events from SDL2 are missing in order to fully support suggestions and swipes.
This PR should be considered as a temp fix, that reverts the default keyboard behaviour to the one we had prior to https://github.com/kivy/kivy/pull/7231, without completely reverting the great additions that have been made by @dwmoffatt. A new Kivy release, will likely land quite soon, and this is a main blocker.

The following code snipped could be used for testing:
from kivy.app import App
from kivy.lang import Builder

kv = """
BoxLayout:
    orientation: 'vertical'
    spacing: dp(20)
    TextInput:
        size_hint_y: None
        height: dp(45)
        hint_text: "input_type:null (default) and keyboard_suggestions: False"
        write_tab: False
        keyboard_suggestions: False
    TextInput:
        size_hint_y: None
        height: dp(45)
        hint_text: "input_type:null (default) and keyboard_suggestions: True"
        write_tab: False
        keyboard_suggestions: True
    TextInput:
        size_hint_y: None
        height: dp(45)
        hint_text: "input_type:text and keyboard_suggestions: False"
        write_tab: False
        input_type: 'text'
        keyboard_suggestions: False
    TextInput:
        size_hint_y: None
        height: dp(45)
        hint_text: "input_type:text and keyboard_suggestions: True"
        write_tab: False
        input_type: 'text'
        keyboard_suggestions: True
    BoxLayout:
        size_hint: 1, 1/2
"""

class Test(App):
    def build(self):
        return Builder.load_string(kv)

Test().run()

What is the implication of having null be the default? What is the difference between null and text? Is it just the same as text, except that it can't support suggestions? I don't have android setup for testing so can't test.

Prior to #7231 the default configuration for keyboard was InputType.TYPE_CLASS_TEXT | InputType.TYPE_TEXT_VARIATION_VISIBLE_PASSWORD. That configuration shows a latin-only keyboard without suggestions. The same behaviour looks like can be achieved via TYPE_NULL  (at least on my configuration, so tests on multiple configurations are really appreciated)
#7337 still remains open for input_type="text"
keyboard_suggestions only works on certain keyboards, when input_type="text". Unfortunately GBoard, is not one of them, cause https://developer.android.com/reference/android/text/InputType#TYPE_TEXT_FLAG_NO_SUGGESTIONS is ignored.

Ok, we'll have to make sure to document this clearly in the release notes, and possibly in the docs itself.
Because the change to default to null is technically a backward compat break, and for people who manually set it to text before, even if it was the default, it'll still be broken. Unless we change keyboard_suggestions to default to False, which we probably shouldn't.

Considering that for the vast majority of users keyboard_suggestion=False acts as the same of keyboard_suggestion=True when input_type="text", I can only totally agree about clearly specifying this behaviour in docs. The same applies for the breaking change.
I will be back here to update it just after the documentation review (WIP 🧐).


feat: Optimize handling of invalid addresses and remove the unused s7_errors variable

PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-examples/blob/master/.github/CONTRIBUTING.md.
What is the current behavior?

Issue Number:
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

New Imports
Are there any new imports or modules? If so, what are they used for and why?
Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 68 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (8abf735) to head (6e4f97d).

Files with missing lines
Patch %
Lines

internal/driver/driver.go
0.00%
68 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main     #25   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          3       3
  Lines        544     588   +44
=====================================
- Misses       544     588   +44

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@whxtpbnl You should squash this pr, each pr should contain one feature.

@whxtpbnl You should squash this pr, each pr should contain one feature.
Thank you for pointing this out! I understand the importance of having one feature per PR. I’ll squash the commits for this PR. If you have any additional preferences or best practices I should follow, please let me know.


slow start

VSCode Version: Code - Insiders 1.13.0-insider (376c52b955428d205459bea6619fc161fc8faacf, 2017-06-07T22:43:38.941Z)
OS Version: Darwin x64 16.5.0
CPUs: Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz (4 x 2600)
Memory (System): 16.00GB (10.98GB free)
Memory (Process): 230.62MB working set (0.00MB peak, 171.15MB private, 137.30MB shared)
Load (avg): 2, 2, 1
VM: 0%
Initial Startup: yes
Screen Reader: no
Empty Workspace: no
Timings:

Component
Task
Time (ms)

main
start => app.isReady
278

main
app.isReady => window.loadUrl()
111

renderer
window.loadUrl() => begin to require(workbench.main.js)
553

renderer
require(workbench.main.js)
515

renderer
create extension host => extensions onReady()
541

renderer
restore viewlet
201

renderer
restore editor view state
760

renderer
overall workbench load
891

main + renderer
start => extensions ready
2026

main + renderer
start => workbench ready
2365

:warning: Make sure to attach these files: :warning:
-/Users/Stern/d08a_main.cpuprofile.txt
-/Users/Stern/d08a_renderer.cpuprofile.txt

@sternzhang please attach those files


Duplicated "Create Integrated Terminal (With Profile)" commands

Testing #129429

press F1 and enter "Terminal"

Observe:

there are two "Create Integrated Terminal (With Profile)" commands and they are too long to see a difference in the QuickPick.

oops, duplicate created due to browser tab confusion...


Add headers for conditional request support

Added relevant request / response headers to support conditional resource retrieval.

Looks good to me


remove unused package imports; add needed get_var_char_values function

The code would not run with no definition for get_var_char_values()

Thanks for your very helpful code @raoofnaushad!

Thank you for the review @KarlAloYoga  Can anyone merge this if all looks good? Thank you!

@raoofnaushad


Streamline and redocument the new StellarGraph constructor

See: #723

Codecov Report

Merging #891 into develop will decrease coverage by 1.4%.
The diff coverage is 81.8%.

@@            Coverage Diff            @@
##           develop    #891     +/-   ##
=========================================
- Coverage     86.5%   85.1%   -1.4%
=========================================
  Files           49      49
  Lines         5691    5024    -667
=========================================
- Hits          4922    4274    -648
+ Misses         769     750     -19

Impacted Files
Coverage Δ

stellargraph/core/graph.py
97.9% <81.8%> (-0.9%)
:arrow_down:

stellargraph/random.py
94.7% <0%> (-3.1%)
:arrow_down:

stellargraph/mapper/sequences.py
92% <0%> (-1.5%)
:arrow_down:

stellargraph/data/explorer.py
94.8% <0%> (-0.9%)
:arrow_down:

stellargraph/core/element_data.py
92.2% <0%> (-0.8%)
:arrow_down:

stellargraph/mapper/sampled_link_generators.py
92.4% <0%> (-0.2%)
:arrow_down:

stellargraph/core/convert.py
100% <0%> (ø)
:arrow_up:

stellargraph/mapper/sampled_node_generators.py
93.4% <0%> (+0.3%)
:arrow_up:

Continue to review full report at Codecov.

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