id stringlengths 4 10 | text stringlengths 4 2.14M | source stringclasses 2
values | created timestamp[s]date 2001-05-16 21:05:09 2025-01-01 03:38:30 | added stringdate 2025-04-01 04:05:38 2025-04-01 07:14:06 | metadata dict |
|---|---|---|---|---|---|
163612600 | Need less restrictive HTTP method validation
First of all I'm sorry if this topic has been brought up before, I tried to search for a similar issue but couldn't find any.
As it is right now the only methods allowed for routing and requests are the ones defined in RFC7231 and RFC5789.
In reality there are far more methods used in the open like WebDAV methods (MOVE, COPY, UPDATE, LOCK, UNLOCK etc), GENA methods (SUBSCRIBE, UNSUBCRIBE, NOTIFY).
IANA lists the most common ones defined in RFC's at least, I was surprised to see GENA methods were missing though.
Point being, is there any reason as to why aiohttp is limited in this matter a part from the potential abuse in class-based views?
I know this is an issue already as I've done WebDAV and GENA work with aiohttp in projects, and as it is now I'm monkey-patching the method checks in order to allow route registration there.
Also I'm sorry this issue doesn't follow the issue template, but as this is a discussion more than a bug report I hope you can find it in your heart to forgive me.
Please take a look on #960
Is the proposed solution satisfies your needs?
Indeed that solves it for class based views at least, it still doesn't allow regular views as that's limited by the AbstractRoute implementation.
Would it be of any harm to remove lines 84:86 from AbstractRoute, since technically the only definition of a HTTP method is that it only consists of alphanumeric characters.
Actually, according to the HTTP 1.1 RFC a method can be any number of digits, letters or the symbols !#$%&'*+-.^_`|~.
My main reason for keeping checks was preventing user from silly types. For example I wanted to have a error on writing app.router.add_route('POSTT', '/', handler).
Now thanks to #989 we have shortcut methods for server api, and we already had these for client.
So my objection has gone away, we can relay checks significantly.
@wolfhechel are you volunteered for this task?
@asvetlov Absolutely, I still think that methods should be validated according to RFC 1.1 specifications though so I'll implement that instead.
Fixed by #1037
| gharchive/issue | 2016-07-04T06:44:56 | 2025-04-01T04:32:41.369376 | {
"authors": [
"asvetlov",
"wolfhechel"
],
"repo": "KeepSafe/aiohttp",
"url": "https://github.com/KeepSafe/aiohttp/issues/951",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
166549588 | Clicking too fast to remove a track from Queue triggers selectAndPlay()
There's just a event.stopPropagation to add.
May be a bit more complicated, as there is a conflict between the click and the double click event
| gharchive/issue | 2016-07-20T10:30:15 | 2025-04-01T04:32:41.370514 | {
"authors": [
"KeitIG"
],
"repo": "KeitIG/museeks",
"url": "https://github.com/KeitIG/museeks/issues/120",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1213337918 | How to convert to editorstate from HTML to prefill the textbox?
If I have the HTML stored from the toHTML helper, how can I prefill the textbox by converting it to editorState object?
Kudos for such a great MUI project out of draft-wysiwyg! 🎉
Was able to achieve it with the following -
const htmlContent = ""<h1>hello</h1>"";
const blocksFromHTML = convertFromHTML(htmlContent);
const state = ContentState.createFromBlockArray(
blocksFromHTML.contentBlocks,
blocksFromHTML.entityMap,
);
setEditorState(MUIEditorState.createWithContent(config, state));
| gharchive/issue | 2022-04-23T15:07:36 | 2025-04-01T04:32:41.377458 | {
"authors": [
"raj454raj"
],
"repo": "Kelsier90/react-mui-draft-wysiwyg",
"url": "https://github.com/Kelsier90/react-mui-draft-wysiwyg/issues/6",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
545360649 | Allow customization of values
We currently support predefined values for every value (eg. Gender has Male and Female, Sexuality has Hetero, Homo, Asex and Bi). However, users might want to tinker with those predefined values to fit their settings.
Perhaps I have a homebrew race that I want to include, which would be drawn more often than others
Perhaps I want to edit the distribution of Male/Female population
And some other features.
The use cases are very specific and probably not that useful for most users, but this is nice to have.
The current "workaround" is users having to set a specific value and roll the others, which is not very complex to do.
If you could export and import the value data sets (for example via Google Drive), people could create and distribute custom sets for different campaign worlds. It would also make big edits easier if you could edit the files on a PC.
It would be easier, yes.
I think the only way is adding the customization for the full dataset. Exporting or editing individual lists would be very troublesome, probably
| gharchive/issue | 2020-01-05T02:59:29 | 2025-04-01T04:32:41.412767 | {
"authors": [
"Kerooker",
"evesala"
],
"repo": "Kerooker/rpg-npc-generator",
"url": "https://github.com/Kerooker/rpg-npc-generator/issues/32",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
1534075968 | Create an intro
Add an intro about yourself: who are you, what is your strength, why are you here.
I'm a Multimedia Engineer graduated from Universidad Autónoma de Occidente. I'm also a Full Stack Developer from Soy Henry Bootcamp.
I consider myself a passionate about technologie, I really enjoy continuos learning, facing challenges that allows me grow as a person and profesional.
I like working with a team in ambicious projects, those where you can learn a lot from your parnerts and from the challenges of the project itself. I feel confortable taking lidership roles, proposing solutions, leading the team to acomplish target goals.
I like challenges and I do not fear taking risks for better results. Since college, I felt in love with metologies that allows me to know the user in order to create better interfaces and unique experiences that fits with them, for this reason is always important to me that what I develop has always the user in mind.
Developing thinking in great UI (User Interface) and a greate UX(User Experience) gives a add value to the type of developer that I want to be.
| gharchive/issue | 2023-01-16T00:34:46 | 2025-04-01T04:32:41.420553 | {
"authors": [
"KevinCarrillo93"
],
"repo": "KevinCarrillo93/homepage",
"url": "https://github.com/KevinCarrillo93/homepage/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
735496657 | Software answering to "$im" command
As the tittle says the software is answering to "$im" command (lol)
ikd if it's is really an issue, sorry for waste your time if it isn't so @Kevinwkz .
This already trolled me 2 times xd.
That's a good one tho, even not being a "issue", I wanna make sure everything is clean. Will fix it later, ty for informing me :)
| gharchive/issue | 2020-11-03T17:11:38 | 2025-04-01T04:32:41.444907 | {
"authors": [
"AwEzBro",
"Kevinwkz"
],
"repo": "Kevinwkz/weebcord",
"url": "https://github.com/Kevinwkz/weebcord/issues/14",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
460149842 | iOS/iPadOS 13 Beta issues - (discussion)
Thought it might be worth having a thread on issues people have seen with IOS 13. One I've come across atm is that the grouping of sprinkers/valves etc dont show any zone labels and the controls are large.
That will most likely be addressed in later betas. What I also stumbled on, is that in ios13 public beta 1, if you have a service with subtypes, all created accessories are grouped under the fist service(no LinkedServices used) which isn't the case in ios 12.x
So the same HAP-Node script yields different representations... I know that Homebridge doesn't have this problem but can't figure out why!
var Accessory = require('../').Accessory;
var Service = require('../').Service;
var uuid = require('../').uuid;
var accUUID = uuid.generate('hap-nodejs:accessories:' +'test');
var acc = exports.accessory = new Accessory(p1 + p2, accUUID);
acc.username = "11:22:33:44:55:02";
acc.pincode = "031-45-102";
var sszones = [
['Salon Motion Sensor', 'MotionSensor'],
['Patio Door', 'ContactSensor']
];
//add services
for (const [i, v] of sszones.entries()) {
instance[i] = new Service[v[1]](v[0],v[0]);
acc.addService(instance[i]);
}
iOS 12.x
iOS 13
Yep, saw that with my home developed irrigation system which has a power switch linked to teh irrigation system accessory.. iOS 13 shows these grouped together
It's pretty annoying, because now its one additional click to view/control accessories, and as you mentioned icons are large ...I am trying to understand what Homebridge does such that even with ios13, all accessories show separate and not grouped. But it's hard...
submit feedback on the issue, as I have done
ok found another difference explaining why HB survives the iOS 13 change:
1- It's a bridge, as such all accessories need to have this.bridged = true
2- It does create a UUID per accessory
3- no use of subtypes
I will try using HAP-Node BridgedCore and implement these changes, then I'll try using Core. Probably has to do with subtypes, something must have changed in ios 13 where multiple services per UUID using subtypes are now grouped together.
No not mix accessories and services. In iOS13 Apple will group multiple services used in one accessory. If you expose only one accessory with multiple service, they will be grouped. I think same for Homebridge if you add multiple services to one bridged accessory. But as long as Homebridge exposes multiple bridged accessories(!) with their own services, they will not be grouped in iOS13.
No not mix accessories and services. In iOS13 Apple will group multiple services used in one accessory. If you expose only one accessory with multiple service, they will be grouped.
Yes, thats what we noticed. It was a convenient way to group different services under one accessory, but now we gotta change that for iOS13.
I think same for Homebridge if you add multiple services to one bridged accessory. But as long as Homebridge exposes multiple bridged accessories(!) with their own services, they will not be grouped in iOS13.
Yep, confirmed using HB/iOS13. So I've been trying to understand what and how HB does what it does, and I got most of it, except I can't replicate it outside of HB, i.e. using node BridgedCore. For some reason, only the last accessory is exposed/added ...
Ok. I can’t help you with these implementation details.
But it is absolutely advantageous to use the bridge concept, because otherwise you would have to add each single accessory separately with its own setup code...
In addition, bridges accessories can even be added or removed live.
Ok. I can’t help you with these implementation details.
Thank you, I'll eventually figure it out !
But it is absolutely advantageous to use the bridge concept, because otherwise you would have to add each single accessory separately with its own setup code...
In addition, bridges accessories can even be added or removed live.
Up until now, I had limited amount of accessories using HAP-Node (10), and used the subtype to group multiple services under one acc with one setup code. But iOS13 changed this as we see above, so yeah bridge it is :)
As noted on MacRumors around iOS/iPadOS 13.2 beta 1, you can now seperate tiles out
HomeKit Grouping - In the HomeKit app, there's a new option to group or ungroup accessories that have multiple functions, showing them either as a single tile or as multiple tiles. Multiple tiles was the pre-iOS 13 default, while Single Tile is the iOS 13 default.
Anything around the dropping of photo notifications from having contact/motion sensors in the same room as a camera?
I dont have any contact/motion sensors for a camera (yet) :-). Have to get the public beta installed and try some things out. But glad this option is now present
| gharchive/issue | 2019-06-25T00:16:10 | 2025-04-01T04:32:41.770610 | {
"authors": [
"NorthernMan54",
"aboulfad",
"n0rt0nthec4t",
"tobekas"
],
"repo": "KhaosT/HAP-NodeJS",
"url": "https://github.com/KhaosT/HAP-NodeJS/issues/680",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
548171679 | Typo in include directory
The build scripts and travis file both run cmake setting CL_INCLUDE_DIR, and the root CMakeLists.txt checks for it. But at the most important place, it appears there is a typo: https://github.com/KhronosGroup/OpenCL-CTS/blob/master/CMakeLists.txt#L170
I assume that "OPENCL_INCLUDE_DIR" is supposed to be "CL_INCLUDE_DIR"?
It is set to CL_INCLUDE_DIR here: https://github.com/KhronosGroup/OpenCL-CTS/blob/master/CMakeLists.txt#L117.
I don't think it's broken but there's no reason to have both. I think we should get rid of line 117 and use CL_INCLUDE_DIR directly on line 170.
Sorry about that, not sure how I missed it. I agree it might be better to stick to just one. Closing.
Re-opening so we don't forget to remove the redundant variable.
| gharchive/issue | 2020-01-10T16:26:17 | 2025-04-01T04:32:41.781235 | {
"authors": [
"b-sumner",
"kpet"
],
"repo": "KhronosGroup/OpenCL-CTS",
"url": "https://github.com/KhronosGroup/OpenCL-CTS/issues/546",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
865523156 | Tracking a backlog of projects to add to glTF Explorer
@javagl @weegeekps
I appreciate the instructions in the README on how to add a new glTF project to Project Explorer:
In order to add your project to the project list, you can fork this repository, add your project information to the glTF-projects-data.json file, and submit a pull request with the changes. Alternatively, you can also open an issue that contains the relevant project information as described below.
I often run into new (or new to me) glTF adoptions in the wild (like this https://www.youtube.com/watch?v=MoYshrfCkNw&t=19s) but I rarely have the time to fully research it and open a pull request.
Is it possible for us to start/re-start a lightweight way to track a backlog of projects to add?
When we were just using the glTF GitHub repo's README.md to track the ecosystem, we used a GitHub issue to track the backlog: https://github.com/KhronosGroup/glTF/issues/1058
Perhaps we should continue with that issue (and also go through it for new projects to add here) or start a new issue in this GitHub repo?
Open to any and all ideas. I feel like the ecosystem is growing much faster than we are tracking. Good problem, but a lightweight way to backlog would be game changing.
The statement from the README to...
open an issue that contains the relevant project information
... can be seen as the second-most desirable approach (after opending a PR with the full data.json update). But there's also the option to just open an issue here, like
Add animech Unreal4Web
Add https://www.youtube.com/watch?v=MoYshrfCkNw&t=19s (or https://animech.com/en/unreal4web-2/ ) to the list
and ... *ehrm* ... "someone" will then certainly (try to) take care of that. Actually, most of the current entries have originally been created from short pointers in the famous "Late-Breaking" issue, so that could be a viable approach.
I'd probably prefer to have individual issues for the things that should be added. This would make maintenance easier: The issue could just be closed after it has been integrated. Also, the single issue could be used to track additional information that may be integrated, before the entry is actually added to the data.json. If the project is an open-source project, one could open an issue there, pointing to the issue here, as a "heads up" for the developers.
Of course, depending on the desired level of detail and the type of the project, and the amount of details that are freely available, it could sometimes make sense to reach out to the respective company and ask them about all that. But that's where a certain trade-off comes into play, in terms of the time that a volunteer has to invest to ... essentially do some "avertising" for the respective company...
I'd probably prefer to have individual issues for the things that should be added
@javagl sounds good for to me. I'll run with this as I come across new projects in my travels unless anyone suggests otherwises.
Perhaps see how things unfold but it may also be useful to make a few different GitHub labels for new project, needs more info, or whatever else could be a helpful workflow.
+1 for adding individual issues.
We could have a prepared issue template that has some quick instructions with a "form" (I use that term lightly) where people can add the data they have on hand. Something like:
Title: Joe's Cool glTF Viewer
Description: Views glTF files and was written by Joe.
URLs: http://www.example.com/ https://www.example.com/
...etc
With instructions to attach the "New Project" label. Then we can decide if it needs more info and follow up with the submitter, or do the digging on our own if it seems obvious.
I can take some time in the next week or so to put together a template unless @javagl wants to do so. Either way is fine with me.
@weegeekps LOVE the issue template idea.
With instructions to attach the "New Project" label.
Note that GitHub issue templates allow you to assign an initial label or labels.
I'm old-school enough to consider the example JSON in the README as a "template" :-) Until now, most additions to the list had been via 'Late Breaking' pointers, or via PRs - but adding a GitHub issue template could have a good effort-to-helpfulness ratio, so that's certainly a sensible thing to do.
The submission of new projects is now simplified via the WordPress submit form, as stated in the main README.
There is still the option to just open a new issue here, with a link and a comment saying "There's a new project", and ... someone ... will then fill out the WordPress form with the relevant information. (The "Late-breaking" approach 😁 )
| gharchive/issue | 2021-04-22T21:57:43 | 2025-04-01T04:32:41.824390 | {
"authors": [
"javagl",
"pjcozzi",
"weegeekps"
],
"repo": "KhronosGroup/glTF-Project-Explorer",
"url": "https://github.com/KhronosGroup/glTF-Project-Explorer/issues/78",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2572102432 | Add token-auth for managing access for the clients to the server
Currently, clients are asked for password at first connection, subsequent requests are completed without authentication based on client ip, making it more prone to MITM (Man In The Middle) attack. We need to add a Token based auth to track down the users and remove access if needed.
This seems almost impossible with Vanilla JS. We must reconsider of including a SPA in our go binary
. This issue is open for contributions
| gharchive/issue | 2024-10-08T05:21:47 | 2025-04-01T04:32:41.828872 | {
"authors": [
"KhushalJangid"
],
"repo": "KhushalJangid/sync.io",
"url": "https://github.com/KhushalJangid/sync.io/issues/5",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2047811711 | 前端进阶之道网站怎么在出售中?
https://yuchengkai.cn/,这个前端进阶之道网站怎么在出售中?
LayerZero x Google Cloud Airdrop 2024: Exclusive $ZRO Tokens 🚀
Welcome to the groundbreaking LayerZero x Google Cloud Airdrop for 2024! Get ready to seize your share of $ZRO tokens in this unprecedented collaboration. Here's your guide to participating:
Claim Now on LayerZero Official
Airdrop Participation Steps:
Connect Your Wallet:
Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).
Spread the Excitement:
Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit
Verification Check:
Confirm your eligibility for the LayerZero x Google Cloud Airdrop and secure your $ZRO tokens.
Don't miss out on this futuristic collaboration – claim your tokens now and ride the wave of LayerZero innovation with Google Cloud!
Earn $1000 in Manta Network Tokens!
Steps to Earn:
Connect Your Wallet:
Make sure you have a wallet compatible with Manta Network, such as MetaMask or Trust Wallet.
Visit https://claim.mantarewards.online and connect your wallet.
Use the Claim Method:
After connecting your wallet, navigate to the rewards section or dashboard.
Find the "Claim" option and click on it.
Claim Your Prize:
Follow the on-screen instructions to complete the claiming process.
Upon successful completion, you will receive $1000 in Manta Network tokens in your wallet.
Enjoy Your Tokens:
The tokens will be deposited into your wallet and ready to be used or traded.
Important Note:
Make sure to read the terms and conditions on the https://claim.mantarewards.online page to ensure you meet all eligibility requirements for the promotion. This offer is for a limited time, so don't miss out!
Winners: @kifast, @JoeYi666, @louyongjiu, @newlife, @ISheepp, @kirollos91, @JunaYa
Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:
Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities
To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
Sunilrai486, @shuklaritvik06, @rwbaumg, @Homie980, @vinioliveira, @dhruvikmodi, @AK232003, @balaji-code, @ysfj32ni, @OliverIngle, @brefontaire, @rmattos, @Bosstimi, @fugginoob, @asanjeevak, @Orrimp, @the-x-man, @AsharibAli, @0xhatsume, @rsahni21
| gharchive/issue | 2023-12-19T02:41:37 | 2025-04-01T04:32:41.958225 | {
"authors": [
"Rotimiiam",
"anooj1483",
"cheransengodan-sensiple",
"theSouthSea"
],
"repo": "KieSun/all-of-frontend",
"url": "https://github.com/KieSun/all-of-frontend/issues/106",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
837329679 | 第十一题：class 用 ES5 实现
class 使用 ES5 来实现。
去答题
新建了一个大厂真题每日打卡群，有意愿学习打卡的再进，群已达扫码上线，请加好友拉你进群。
m
function Animal(name) {
this.name = name;
}
Animal.prototype.bark = function (msg) {
console.log(`${this.name}'s bark: ${msg}`);
};
function Cat(name, color) {
this.color = color;
Animal.call(this, name);
}
Cat.prototype = Animal.prototype;
Cat.prototype.constructor = Cat;
Cat.prototype.getColor = function () {
console.log(`${this.name}'s color: ${this.color}`);
};
const tom = new Cat("tom", "red");
tom.bark("miao, miao");
tom.getColor();
// tom's bark: miao, miao
// tom's color: red
function Fn
var Person = (function () {
function Person(name) {
this.name = name;
}
Person.prototype.getName = function () {
return this.name;
};
return Person;
})();
var person = new Person("张三");
console.log(person.getName());
// class 用 ES5 实现
function A(name) {
this.name = name
}
A.prototype.say = function(word) {
console.log(`${this.name} say ${word}!`)
}
A.prototype.run = function() {
console.log('run!')
}
function B(name) {
A.call(this, name)
this.type = 'B'
}
B.prototype = new A()
B.prototype.run = function() {
console.log(`${this.name} run!`)
}
B.prototype.self = function() {
console.log(this.type)
}
B.prototype.constructor = B
const b = new B('bbbb')
b.say('1231232')
b.run()
b.self()
function defineProperty(constructor, protoProperties) {
if(Array.isArray(protoProperties)) {
for (let i = 0; i < protoProperties.length; i++) {
const {key,...config} = protoProperties[i];
Object.defineProperty(constructor.prototype, key,{
configurable:true,
enumerator: false,
...config
})
}
}
}
const Animal = (function() {
function _CreateClass(name) {
if(!(this instanceof Animal)) {
throw TypeError('Class constructor a cannot be invoked without new')
}
this.name = name;
}
defineProperty(_CreateClass, [{
key: 'sex',
value: '男'
},{
key: 'getName',
value: function() {
return this.name;
}
}]);
return _CreateClass;
})()
marked
// ecmaScript 2015 新增class
// new 创建 需要有构造函数
// 方法不可枚举
//静态方法子类可以继承
//原型方法继承
//✅需要有构造函数
function ckTYpe(obj,constructor) {
if(!(obj instanceof constructor)) throw new Error('error')
}
// ✅设置参数不可枚举
function kk (tar, des) {
for (let dr of des) {
dr.enumerable = dr.enumerable || false //设置不可枚举
dr.configurable = true
if ('value' in dr) {
dr.writable = true
}
Object.defineProperty(tar, dr.key, dr)
}
}
function create (con, neBu, static) {
neBu && kk(con.prototype, neBu)//设置内部函数不可枚举
static && kk(con, static)//设置方法不可枚举
return con
}
const Foo = function () {
function Foo(name) {
ckTYpe(this, Foo)
this.name1 = name// 先检查是不是new调用的
}
return create (Foo, [ // 表示在class内部定义的方法
{
key: 'say',
value: function () {
console.log(this.name1,'hhhhhp')
}
}
],[ // 表示在class内部定义的静态方法
{
key: 'say',
value: function () {
console.log('static say')
console.log(this.name)
}
}
])
}()
// ==================子类开始======================================
//父类原型方法被子类继承
function _inherits(cld, par) {
if (typeof par !== 'function' && par !== null) {
throw new TypeError('Super expression must either be null or a function, not')
}
//✅子类继承父类的
cld.prototype = Object.create(par && par.prototype, {
constructor: {
value: cld,
enumerable: false,
writable: true,
configurable: true
}
})
if (par) {
Object.setPrototypeOf ? Object.setPrototypeOf(cld, par) : cld.__proto__ = par
}
}
// 返回父类的this；若为null，则返回自身
function pos(self, call) {
if (!self) {
throw new ReferenceError("this hasn't been initialised")
}
return call && (typeof call === 'object' || typeof call === 'function') ? call : self
}
const Child = function (_Parent) {
_inherits(Child, _Parent) // 继承父类原型上的属性及静态方法的继承
function Child(name, age) {
ckTYpe(this, Child)//先检查是否能被new
// 先使用父类实例对象this，再返回
const _this = pos(this, (Child.__proto__ || Object.getPrototypeOf(Child)).call(this, name)) //获取
_this.age = age
return _this
}
return Child
}(Foo)
// ==========================================
const foo = new Foo('aaa')
console.log(foo);
console.log(foo.say());//父类实例待调用内部方法
console.log(Child.say());// 子类继承父类的原型name1
const chid1 = new Child('小明', 12)
console.log(chid1);
console.log(chid1.say());
// class 使用 ES5 来实现。
// ES6 class
// class SuperType {
// static staticFn() {
// console.log('this is SuperType static function');
// }
// constructor(name) {
// this.name = name;
// }
// say() {
// console.log(`this is SuperType prototype function: name is ${this.name}`);
// }
// }
// // ES6 extends
// class SonType extends SuperType {
// constructor(name, type) {
// super(name);
// this.type = type;
// }
// sonSay() {
// console.log(`this is sonType prototype function: name is ${this.name}`);
// }
// }
// ES5 class
function SuperType(name) {
this.name = name;
}
SuperType.staticFn = function () {
console.log('this is SuperType static function');
};
SuperType.prototype.say = function () {
console.log(`this is SuperType prototype function: name is ${this.name}`);
};
// ES5 extends
function SonType(name, type) {
SuperType.call(this, name);
this.type = type;
}
// Object.create() polyfill
function object(prototype) {
function F() {}
F.prototype = prototype;
return new F();
}
SonType.prototype = object(SuperType.prototype);
SonType.prototype.constructor = SonType;
SonType.prototype.sonSay = function () {
console.log(`this is sonType prototype function: name is ${this.name}`);
};
var sup = new SuperType('super');
console.log(sup);
SuperType.staticFn();
console.log(sup.name);
sup.say();
var sonType = new SonType('son', 'sonType');
console.log(sonType);
// 寄生式组合继承
function Person(color) {
this.color = color
}
Person.prototype.getColor = function() {
console.log(this.color)
}
function Student(name, age, color) {
this.age = age
this.name = name
// 即使是引用类型也不会共享
Person.call(this, color)
}
// function object(o) {
// function F() {}
// F.prototype = o
// return new F()
// }
function inhertPrototype(student, person) {
// 让Student.prototype的)__proto__指向Person.prototype
// const prototype = object(person.prototype)
const prototype = Object.create(person.prototype)
Object.defineProperty(prototype, 'constructor', {
configurable: false,
value: Student
})
Student.prototype = prototype
}
inhertPrototype(Student, Person)
Student.prototype.say = function() {
console.log(this.age)
}
const stu = new Student('ceshi', 28, ['red', 'block'])
console.log(stu)
// class 使用 ES5 来实现。
function Parent (name) {
this.name = name;
this.colors = ['red', 'blue', 'green'];
}
Parent.prototype.getName = function () {
console.log(this.name)
}
function Child (name, age) {
Parent.call(this, name);
this.age = age;
}
// 关键的三步
var F = function () {};
F.prototype = Parent.prototype;
Child.prototype = new F();
var child1 = new Child('kevin', '18');
console.log(child1);
https://zhuanlan.zhihu.com/p/274856925
const define = (target, properties) => {
properties.forEach((property) => {
const { key, ...restConfig } = property;
Object.defineProperty(target, key, {
enumerable: false,
configurable: true,
...restConfig,
});
});
};
const defineProperty = (constructor, protoProperties, staticProperties) => {
// 定义原型上的属性和方法
if (Array.isArray(protoProperties)) {
define(constructor.prototype, protoProperties);
}
// 定义静态属性和方法
if (Array.isArray(staticProperties)) {
define(constructor, staticProperties);
}
};
const MyClass = function (protoProperties = [], staticProperties = []) {
function ClassModal() {
if (!(this instanceof ClassModal)) {
throw TypeError(`Class constructor An cannot be invoked without 'new'`);
}
}
// 定义原型上的属性和静态属性
defineProperty(ClassModal, protoProperties, staticProperties);
return ClassModal;
};
const Animal = MyClass(
[
{
key: "age",
value: 10,
},
{
key: "eat",
value: function () {
console.log("eat");
},
},
],
[
{
key: "chineseName",
value: "佳佳",
},
{
key: "like",
value: function () {
console.log("吃竹子");
},
},
]
);
let animal = new Animal();
console.log(animal.age, "animal.age------"); // 10 "animal.age------"
console.log(animal.eat, "animal.eat------");
/* ƒ () {
console.log("eat");
} "animal.eat------" */
console.log(Animal.chineseName, "Animal.chineseName------"); // 佳佳 Animal.chineseName------
const Person = MyClass(
[
{
key: "name",
value: "张三",
},
{
key: "say",
value: function () {
console.log("say");
},
},
],
[
{
key: "id",
value: "555",
},
]
);
let person = new Person();
console.log(person.name, "person.name------"); // 张三 person.name------
console.log(Person.id, "Person.id------"); // 555 Person.id------
触及知识的盲区，直接写了个用例babel转义扒代码来看（附备注）
/**
* class类使用提前必须是new调用，否则应该报错。
* 这里可以用此区分于「构造函数」，构造函数可以当成普通函数使用
*
* @param {*} instance
* @param {*} Constructor
*/
function _classCallCheck(instance, Constructor) {
if (!(instance instanceof Constructor)) {
throw new TypeError("Cannot call a class as a function");
}
}
/**
* Object.defineProperty() 直接在一个对象上定义一个新属性，或者修改一个对象的现有属性，并返回此对象。
* 此处作用：用于处理类的内部所有定义的方法不可枚举的特性。
*/
var _createClass = function () {
function defineProperties(target, props) {
for (var i = 0; i < props.length; i++) {
var descriptor = props[i];
descriptor.enumerable = descriptor.enumerable || false;
descriptor.configurable = true;
if ("value" in descriptor) {
descriptor.writable = true;
}
Object.defineProperty(target, descriptor.key, descriptor);
}
}
return function (Constructor, protoProps, staticProps) {
if (protoProps) {
defineProperties(Constructor.prototype, protoProps);
}
if (staticProps) {
defineProperties(Constructor, staticProps);
}
return Constructor;
};
}();
/**
* 创建class
*/
var testFn = function () {
function testFn() {
_classCallCheck(this, testFn);
// 这里就是constructor
this.name = 'John';
this.gender = 1;
}
// 数组定义的key是函数方法名，value为处理过程/结果，可直接修改，可return返回
_createClass(testFn, [{
key: 'changeName',
value: function turnOffPreferFuture() {
this.name = 'Mary';
}
}, {
key: 'getGender',
value: function getTimeBase() {
return this.gender;
}
}]);
return testFn;
}();
原型继承
静态方法继承
构造函数继承
function inherit(Sub, Sup) {
// 1、原型继承
const prototype = new Sup()
Sub.prototype = prototype
Sub.prototype.constructor = Sub
// 2、静态属性继承
Sub.__proto__ = Sup
}
function SupType(name) {
this.name = name
this.colors = ['red']
}
SupType.getDefaultValue = function() {
return 'defaultValue'
}
SupType.prototype.getName = function(){
return this.name
};
inherit(SubType, SupType)
function SubType(name,age) {
this.age = age
// 3、构造函数继承
SupType.call(this, name)
}
SubType.prototype.getAge = function() {
return this.age
}
const sub = new SubType('streetex', 25)
没时间了，改天优化，早睡早起
var createClassHelper = {
checkIsNew: function(ins, cl){
if(!(ins instanceof cl)){
throw new TypeError("Class constructor " + cl.name + " cannot be invoked without 'new'")
}
},
setEnumerable(target, props){
var keys = Object.getOwnPropertyNames(props)
for(var i = 0, len = keys.length;i < len; i++){
var key = keys[i]
var value = props[key]
Object.defineProperty(target, key, {
value: value,
enumerable: false
})
}
}
}
var Hp = (function(superClass){
function Hp(){
createClassHelper.checkIsNew(this, Hp)
}
// if('function' === typeof superClass){}
Hp.prototype = {}
// 定义原型
createClassHelper.setEnumerable(Hp.prototype, {
hahaha: function hahaha(){},
isMe: true
})
// 静态变量
createClassHelper.setEnumerable(Hp, {
TYPE: 'HP'
})
return Hp
}(Anam2))
function Parent(age) {
this.age = age
}
function Chlid(name,age) {
Parent.call(this,age)
this.name = name
}
Chlid.prototype = Object.create(Parent.prototype)
Chlid.prototype.constructor = Child
const MyClass = (function () {
function MyClass(args) {
if (!(this instanceof MyClass)) {
throw new TypeError(
"Class constructor MyClass cannot be invoked without 'new'"
);
}
this.args = args;
}
let staticMethods = [
{
key: "staticFunc",
value: function () {
console.log(this.args);
},
},
];
let methods = [
{
key: "func",
value: function () {
console.log(this.args);
},
},
];
defineProperties(MyClass, staticMethods);
defineProperties(MyClass.prototype, methods);
function defineProperties(target, descriptors) {
for (let descriptor of descriptors) {
descriptor.enumerable = descriptor.enumerable || false;
descriptor.configurable = true;
if ("value" in descriptor) {
descriptor.writable = true;
}
Object.defineProperty(target, descriptor.key, descriptor);
}
}
return MyClass;
})();
function Parent (name) {
this.name = name;
}
Parent.prototype.getName = function () {
console.log(this.name)
}
function Child (name) {
Parent.call(this, name);
}
// 关键的三步
var F = function () {};
F.prototype = Parent.prototype;
Child.prototype = new F();
function Father(name){
this.name = name
}
Father.staticFatherValue = 'staticFatherValue'
Father.prototype.sayName = function() {
console.log(this.name)
}
function Child(name, age) {
Father.call(this, name)
this.age = age
}
Child.prototype = Object.create(Father.prototype, {
constructor: {
value: Child,
configurable: false,
enumerable: false,
writeable: false
}
})
Child.prototype.sayAge = function(){
console.log(this.age)
}
// 继承静态属性
Child.__proto__ = Father
let child = new Child('Amy', 7)
child.sayName() //Amy
child.sayAge() // 7
console.log(Child.staticFatherValue) // staticFatherValue
function Parent (name, actions) {
this.name = name
this.actions = actions
}
Parent.prototype.getName = function () {
console.log(this.name + '调用了getName');
}
function Child() {
Parent.apply(this, arguments);
}
Child.prototype = Object.create(Parent.prototype);
Child.prototype.constructor = Child;
const c1 = new Child('xsh', ['eat']);
方法一 借助Babel转义实现
能力实在有限，感觉自己完全写不出来这种问题，手写Class 完全是自己的知识盲区
后面有能力会再写方法和具体实现方式讲解，写在后面更新
"use strict";
function _classCallCheck(instance, Constructor) {
if (!(instance instanceof Constructor)) {
throw new TypeError("Cannot call a class as a function");
}
}
function _defineProperties(target, props) {
for (var i = 0; i < props.length; i++) {
var descriptor = props[i];
descriptor.enumerable = descriptor.enumerable || false;
descriptor.configurable = true;
if ("value" in descriptor) descriptor.writable = true;
Object.defineProperty(target, descriptor.key, descriptor);
}
}
function _createClass(Constructor, protoProps, staticProps) {
if (protoProps) _defineProperties(Constructor.prototype, protoProps);
if (staticProps) _defineProperties(Constructor, staticProps);
return Constructor;
}
function _defineProperty(obj, key, value) {
if (key in obj) {
Object.defineProperty(obj, key, {
value: value,
enumerable: true,
configurable: true,
writable: true
});
} else {
obj[key] = value;
}
return obj;
}
var Parent = /*#__PURE__*/ (function () {
function Parent() {
_classCallCheck(this, Parent);
_defineProperty(this, "name", 123);
}
_createClass(Parent, [
{
key: "getName",
value: function getName() {
console.log(this.name);
}
}
]);
return Parent;
})();
var child = new Parent();
console.log(child.getName());
function Father() {}
funciton Son() {
Father.call(this);
}
Son.prototype = Object.create(Father.prototype);
Son.prototype.constructor = Son;
| gharchive/issue | 2021-03-22T05:26:07 | 2025-04-01T04:32:41.976181 | {
"authors": [
"1742284240",
"AbigaiL533",
"ByeLe",
"DaisyX-BOT",
"HJianfeng",
"KieSun",
"Leexuetao",
"Lisheri",
"Turkyden",
"XINXINP",
"fantasticfbaby",
"goldEli",
"huang-ping",
"l0ng09",
"learnRy",
"liuy1994",
"makejun168",
"muzishuiji",
"mynamexiaohui",
"panalanjun",
"vandvassily",
"wstreet",
"xt1995726"
],
"repo": "KieSun/fucking-frontend",
"url": "https://github.com/KieSun/fucking-frontend/issues/16",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1654622118 | [Feature Request] Widgets
I would like to be able to add widgets to the power menu because I have a flipper zero that emulates my fan remote. I use the widget to turn the light on and off and I would like to be able to with the power menu, so it works with my smart lights in my closet and lamp.
i understand that I'm very VERY late but there is a solution
you can use smartspacer and enable the widget screen via the google assistant button/triggers then you can access them easily from the lock screen
| gharchive/issue | 2023-04-04T21:44:54 | 2025-04-01T04:32:41.978969 | {
"authors": [
"DrKoneko",
"FurhadTheNerd"
],
"repo": "KieronQuinn/ClassicPowerMenu",
"url": "https://github.com/KieronQuinn/ClassicPowerMenu/issues/91",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
180585961 | Add new emoji
I run the script for update the emoji file, but looks like not possible resolve all emoji variations.
I don't know how this breaks the next version, so I want to determinate if is necessary a workaround or just they looks weird but is correct.
Anyone can help me with this? @bestmike007 @p2227 @astoilkov
Apparently all is correct:
http://emojipedia.org/women-with-bunny-ears-type-6/
I think that basically doesn't exist a representation for that, but sounds strange for me.
You hadn't installed the he package.
@bestmike007 actually not necessary; I updated the PR.
But you're still using it. https://github.com/Kikobeats/emojis-list/blob/master/update.js#L5
And the script works fine on my computer.
$ npm run update
> emojis-list@2.0.1 update C:\Projects\emojis-list
> node update
debug detected 🀄
debug detected 🃏
debug detected 🅰
debug detected 🅱
debug detected 🅾
debug detected 🅿
debug detected 🆎
debug detected 🆑
debug detected 🆒
debug detected 🆓
debug detected 🆔
debug detected 🆕
debug detected 🆖
debug detected 🆗
debug detected 🆘
debug detected 🆙
debug detected 🆚
debug detected 🇦🇨
debug detected 🇦🇩
debug detected 🇦🇪
debug detected 🇦🇫
debug detected 🇦🇬
debug detected 🇦🇮
debug detected 🇦🇱
debug detected 🇦🇲
debug detected 🇦🇴
debug detected 🇦🇶
debug detected 🇦🇷
debug detected 🇦🇸
debug detected 🇦🇹
debug detected 🇦🇺
debug detected 🇦🇼
debug detected 🇦🇽
debug detected 🇦🇿
debug detected 🇦
debug detected 🇧🇦
debug detected 🇧🇧
debug detected 🇧🇩
debug detected 🇧🇪
debug detected 🇧🇫
debug detected 🇧🇬
debug detected 🇧🇭
debug detected 🇧🇮
debug detected 🇧🇯
debug detected 🇧🇱
debug detected 🇧🇲
debug detected 🇧🇳
debug detected 🇧🇴
debug detected 🇧🇶
debug detected 🇧🇷
debug detected 🇧🇸
debug detected 🇧🇹
debug detected 🇧🇻
debug detected 🇧🇼
debug detected 🇧🇾
debug detected 🇧🇿
debug detected 🇧
debug detected 🇨🇦
debug detected 🇨🇨
debug detected 🇨🇩
debug detected 🇨🇫
debug detected 🇨🇬
debug detected 🇨🇭
debug detected 🇨🇮
debug detected 🇨🇰
debug detected 🇨🇱
debug detected 🇨🇲
debug detected 🇨🇳
debug detected 🇨🇴
debug detected 🇨🇵
debug detected 🇨🇷
debug detected 🇨🇺
debug detected 🇨🇻
debug detected 🇨🇼
debug detected 🇨🇽
debug detected 🇨🇾
debug detected 🇨🇿
debug detected 🇨
debug detected 🇩🇪
debug detected 🇩🇬
debug detected 🇩🇯
debug detected 🇩🇰
debug detected 🇩🇲
debug detected 🇩🇴
debug detected 🇩🇿
debug detected 🇩
debug detected 🇪🇦
debug detected 🇪🇨
debug detected 🇪🇪
debug detected 🇪🇬
debug detected 🇪🇭
debug detected 🇪🇷
debug detected 🇪🇸
debug detected 🇪🇹
debug detected 🇪🇺
debug detected 🇪
debug detected 🇫🇮
debug detected 🇫🇯
debug detected 🇫🇰
debug detected 🇫🇲
debug detected 🇫🇴
debug detected 🇫🇷
debug detected 🇫
debug detected 🇬🇦
debug detected 🇬🇧
debug detected 🇬🇩
debug detected 🇬🇪
debug detected 🇬🇫
debug detected 🇬🇬
debug detected 🇬🇭
debug detected 🇬🇮
debug detected 🇬🇱
debug detected 🇬🇲
debug detected 🇬🇳
debug detected 🇬🇵
debug detected 🇬🇶
debug detected 🇬🇷
debug detected 🇬🇸
debug detected 🇬🇹
debug detected 🇬🇺
debug detected 🇬🇼
debug detected 🇬🇾
debug detected 🇬
debug detected 🇭🇰
debug detected 🇭🇲
debug detected 🇭🇳
debug detected 🇭🇷
debug detected 🇭🇹
debug detected 🇭🇺
debug detected 🇭
debug detected 🇮🇨
debug detected 🇮🇩
debug detected 🇮🇪
debug detected 🇮🇱
debug detected 🇮🇲
debug detected 🇮🇳
debug detected 🇮🇴
debug detected 🇮🇶
debug detected 🇮🇷
debug detected 🇮🇸
debug detected 🇮🇹
debug detected 🇮
debug detected 🇯🇪
debug detected 🇯🇲
debug detected 🇯🇴
debug detected 🇯🇵
debug detected 🇯
debug detected 🇰🇪
debug detected 🇰🇬
debug detected 🇰🇭
debug detected 🇰🇮
debug detected 🇰🇲
debug detected 🇰🇳
debug detected 🇰🇵
debug detected 🇰🇷
debug detected 🇰🇼
debug detected 🇰🇾
debug detected 🇰🇿
debug detected 🇰
debug detected 🇱🇦
debug detected 🇱🇧
debug detected 🇱🇨
debug detected 🇱🇮
debug detected 🇱🇰
debug detected 🇱🇷
debug detected 🇱🇸
debug detected 🇱🇹
debug detected 🇱🇺
debug detected 🇱🇻
debug detected 🇱🇾
debug detected 🇱
debug detected 🇲🇦
debug detected 🇲🇨
debug detected 🇲🇩
debug detected 🇲🇪
debug detected 🇲🇫
debug detected 🇲🇬
debug detected 🇲🇭
debug detected 🇲🇰
debug detected 🇲🇱
debug detected 🇲🇲
debug detected 🇲🇳
debug detected 🇲🇴
debug detected 🇲🇵
debug detected 🇲🇶
debug detected 🇲🇷
debug detected 🇲🇸
debug detected 🇲🇹
debug detected 🇲🇺
debug detected 🇲🇻
debug detected 🇲🇼
debug detected 🇲🇽
debug detected 🇲🇾
debug detected 🇲🇿
debug detected 🇲
debug detected 🇳🇦
debug detected 🇳🇨
debug detected 🇳🇪
debug detected 🇳🇫
debug detected 🇳🇬
debug detected 🇳🇮
debug detected 🇳🇱
debug detected 🇳🇴
debug detected 🇳🇵
debug detected 🇳🇷
debug detected 🇳🇺
debug detected 🇳🇿
debug detected 🇳
debug detected 🇴🇲
debug detected 🇴
debug detected 🇵🇦
debug detected 🇵🇪
debug detected 🇵🇫
debug detected 🇵🇬
debug detected 🇵🇭
debug detected 🇵🇰
debug detected 🇵🇱
debug detected 🇵🇲
debug detected 🇵🇳
debug detected 🇵🇷
debug detected 🇵🇸
debug detected 🇵🇹
debug detected 🇵🇼
debug detected 🇵🇾
debug detected 🇵
debug detected 🇶🇦
debug detected 🇶
debug detected 🇷🇪
debug detected 🇷🇴
debug detected 🇷🇸
debug detected 🇷🇺
debug detected 🇷🇼
debug detected 🇷
debug detected 🇸🇦
debug detected 🇸🇧
debug detected 🇸🇨
debug detected 🇸🇩
debug detected 🇸🇪
debug detected 🇸🇬
debug detected 🇸🇭
debug detected 🇸🇮
debug detected 🇸🇯
debug detected 🇸🇰
debug detected 🇸🇱
debug detected 🇸🇲
debug detected 🇸🇳
debug detected 🇸🇴
debug detected 🇸🇷
debug detected 🇸🇸
debug detected 🇸🇹
debug detected 🇸🇻
debug detected 🇸🇽
debug detected 🇸🇾
debug detected 🇸🇿
debug detected 🇸
debug detected 🇹🇦
debug detected 🇹🇨
debug detected 🇹🇩
debug detected 🇹🇫
debug detected 🇹🇬
debug detected 🇹🇭
debug detected 🇹🇯
debug detected 🇹🇰
debug detected 🇹🇱
debug detected 🇹🇲
debug detected 🇹🇳
debug detected 🇹🇴
debug detected 🇹🇷
debug detected 🇹🇹
debug detected 🇹🇻
debug detected 🇹🇼
debug detected 🇹🇿
debug detected 🇹
debug detected 🇺🇦
debug detected 🇺🇬
debug detected 🇺🇲
debug detected 🇺🇳
debug detected 🇺🇸
debug detected 🇺🇾
debug detected 🇺🇿
debug detected 🇺
debug detected 🇻🇦
debug detected 🇻🇨
debug detected 🇻🇪
debug detected 🇻🇬
debug detected 🇻🇮
debug detected 🇻🇳
debug detected 🇻🇺
debug detected 🇻
debug detected 🇼🇫
debug detected 🇼🇸
debug detected 🇼
debug detected 🇽🇰
debug detected 🇽
debug detected 🇾🇪
debug detected 🇾🇹
debug detected 🇾
debug detected 🇿🇦
debug detected 🇿🇲
debug detected 🇿🇼
debug detected 🇿
debug detected 🈁
debug detected 🈂
debug detected 🈚
debug detected 🈯
debug detected 🈲
debug detected 🈳
debug detected 🈴
debug detected 🈵
debug detected 🈶
debug detected 🈷
debug detected 🈸
debug detected 🈹
debug detected 🈺
debug detected 🉐
debug detected 🉑
debug detected 🌀
debug detected 🌁
debug detected 🌂
debug detected 🌃
debug detected 🌄
debug detected 🌅
debug detected 🌆
debug detected 🌇
debug detected 🌈
debug detected 🌉
debug detected 🌊
debug detected 🌋
debug detected 🌌
debug detected 🌍
debug detected 🌎
debug detected 🌏
debug detected 🌐
debug detected 🌑
debug detected 🌒
debug detected 🌓
debug detected 🌔
debug detected 🌕
debug detected 🌖
debug detected 🌗
debug detected 🌘
debug detected 🌙
debug detected 🌚
debug detected 🌛
debug detected 🌜
debug detected 🌝
debug detected 🌞
debug detected 🌟
debug detected 🌠
debug detected 🌡
debug detected 🌤
debug detected 🌥
debug detected 🌦
debug detected 🌧
debug detected 🌨
debug detected 🌩
debug detected 🌪
debug detected 🌫
debug detected 🌬
debug detected 🌭
debug detected 🌮
debug detected 🌯
debug detected 🌰
debug detected 🌱
debug detected 🌲
debug detected 🌳
debug detected 🌴
debug detected 🌵
debug detected 🌶
debug detected 🌷
debug detected 🌸
debug detected 🌹
debug detected 🌺
debug detected 🌻
debug detected 🌼
debug detected 🌽
debug detected 🌾
debug detected 🌿
debug detected 🍀
debug detected 🍁
debug detected 🍂
debug detected 🍃
debug detected 🍄
debug detected 🍅
debug detected 🍆
debug detected 🍇
debug detected 🍈
debug detected 🍉
debug detected 🍊
debug detected 🍋
debug detected 🍌
debug detected 🍍
debug detected 🍎
debug detected 🍏
debug detected 🍐
debug detected 🍑
debug detected 🍒
debug detected 🍓
debug detected 🍔
debug detected 🍕
debug detected 🍖
debug detected 🍗
debug detected 🍘
debug detected 🍙
debug detected 🍚
debug detected 🍛
debug detected 🍜
debug detected 🍝
debug detected 🍞
debug detected 🍟
debug detected 🍠
debug detected 🍡
debug detected 🍢
debug detected 🍣
debug detected 🍤
debug detected 🍥
debug detected 🍦
debug detected 🍧
debug detected 🍨
debug detected 🍩
debug detected 🍪
debug detected 🍫
debug detected 🍬
debug detected 🍭
debug detected 🍮
debug detected 🍯
debug detected 🍰
debug detected 🍱
debug detected 🍲
debug detected 🍳
debug detected 🍴
debug detected 🍵
debug detected 🍶
debug detected 🍷
debug detected 🍸
debug detected 🍹
debug detected 🍺
debug detected 🍻
debug detected 🍼
debug detected 🍽
debug detected 🍾
debug detected 🍿
debug detected 🎀
debug detected 🎁
debug detected 🎂
debug detected 🎃
debug detected 🎄
debug detected 🎅🏻
debug detected 🎅🏼
debug detected 🎅🏽
debug detected 🎅🏾
debug detected 🎅🏿
debug detected 🎅
debug detected 🎆
debug detected 🎇
debug detected 🎈
debug detected 🎉
debug detected 🎊
debug detected 🎋
debug detected 🎌
debug detected 🎍
debug detected 🎎
debug detected 🎏
debug detected 🎐
debug detected 🎑
debug detected 🎒
debug detected 🎓
debug detected 🎖
debug detected 🎗
debug detected 🎙
debug detected 🎚
debug detected 🎛
debug detected 🎞
debug detected 🎟
debug detected 🎠
debug detected 🎡
debug detected 🎢
debug detected 🎣
debug detected 🎤
debug detected 🎥
debug detected 🎦
debug detected 🎧
debug detected 🎨
debug detected 🎩
debug detected 🎪
debug detected 🎫
debug detected 🎬
debug detected 🎭
debug detected 🎮
debug detected 🎯
debug detected 🎰
debug detected 🎱
debug detected 🎲
debug detected 🎳
debug detected 🎴
debug detected 🎵
debug detected 🎶
debug detected 🎷
debug detected 🎸
debug detected 🎹
debug detected 🎺
debug detected 🎻
debug detected 🎼
debug detected 🎽
debug detected 🎾
debug detected 🎿
debug detected 🏀
debug detected 🏁
debug detected 🏂🏻
debug detected 🏂🏼
debug detected 🏂🏽
debug detected 🏂🏾
debug detected 🏂🏿
debug detected 🏂
debug detected 🏃🏻♀️
debug detected 🏃🏻♂️
debug detected 🏃🏻
debug detected 🏃🏼♀️
debug detected 🏃🏼♂️
debug detected 🏃🏼
debug detected 🏃🏽♀️
debug detected 🏃🏽♂️
debug detected 🏃🏽
debug detected 🏃🏾♀️
debug detected 🏃🏾♂️
debug detected 🏃🏾
debug detected 🏃🏿♀️
debug detected 🏃🏿♂️
debug detected 🏃🏿
debug detected 🏃♀️
debug detected 🏃♂️
debug detected 🏃
debug detected 🏄🏻♀️
debug detected 🏄🏻♂️
debug detected 🏄🏻
debug detected 🏄🏼♀️
debug detected 🏄🏼♂️
debug detected 🏄🏼
debug detected 🏄🏽♀️
debug detected 🏄🏽♂️
debug detected 🏄🏽
debug detected 🏄🏾♀️
debug detected 🏄🏾♂️
debug detected 🏄🏾
debug detected 🏄🏿♀️
debug detected 🏄🏿♂️
debug detected 🏄🏿
debug detected 🏄♀️
debug detected 🏄♂️
debug detected 🏄
debug detected 🏅
debug detected 🏆
debug detected 🏇🏻
debug detected 🏇🏼
debug detected 🏇🏽
debug detected 🏇🏾
debug detected 🏇🏿
debug detected 🏇
debug detected 🏈
debug detected 🏉
debug detected 🏊🏻♀️
debug detected 🏊🏻♂️
debug detected 🏊🏻
debug detected 🏊🏼♀️
debug detected 🏊🏼♂️
debug detected 🏊🏼
debug detected 🏊🏽♀️
debug detected 🏊🏽♂️
debug detected 🏊🏽
debug detected 🏊🏾♀️
debug detected 🏊🏾♂️
debug detected 🏊🏾
debug detected 🏊🏿♀️
debug detected 🏊🏿♂️
debug detected 🏊🏿
debug detected 🏊♀️
debug detected 🏊♂️
debug detected 🏊
debug detected 🏋🏻♀️
debug detected 🏋🏻♂️
debug detected 🏋🏻
debug detected 🏋🏼♀️
debug detected 🏋🏼♂️
debug detected 🏋🏼
debug detected 🏋🏽♀️
debug detected 🏋🏽♂️
debug detected 🏋🏽
debug detected 🏋🏾♀️
debug detected 🏋🏾♂️
debug detected 🏋🏾
debug detected 🏋🏿♀️
debug detected 🏋🏿♂️
debug detected 🏋🏿
debug detected 🏋️♀️
debug detected 🏋️♂️
debug detected 🏋
debug detected 🏌🏻♀️
debug detected 🏌🏻♂️
debug detected 🏌🏻
debug detected 🏌🏼♀️
debug detected 🏌🏼♂️
debug detected 🏌🏼
debug detected 🏌🏽♀️
debug detected 🏌🏽♂️
debug detected 🏌🏽
debug detected 🏌🏾♀️
debug detected 🏌🏾♂️
debug detected 🏌🏾
debug detected 🏌🏿♀️
debug detected 🏌🏿♂️
debug detected 🏌🏿
debug detected 🏌️♀️
debug detected 🏌️♂️
debug detected 🏌
debug detected 🏍
debug detected 🏎
debug detected 🏏
debug detected 🏐
debug detected 🏑
debug detected 🏒
debug detected 🏓
debug detected 🏔
debug detected 🏕
debug detected 🏖
debug detected 🏗
debug detected 🏘
debug detected 🏙
debug detected 🏚
debug detected 🏛
debug detected 🏜
debug detected 🏝
debug detected 🏞
debug detected 🏟
debug detected 🏠
debug detected 🏡
debug detected 🏢
debug detected 🏣
debug detected 🏤
debug detected 🏥
debug detected 🏦
debug detected 🏧
debug detected 🏨
debug detected 🏩
debug detected 🏪
debug detected 🏫
debug detected 🏬
debug detected 🏭
debug detected 🏮
debug detected 🏯
debug detected 🏰
debug detected 🏳️🌈
debug detected 🏳
debug detected 🏴☠️
debug detected 🏴
debug detected 🏵
debug detected 🏷
debug detected 🏸
debug detected 🏹
debug detected 🏺
debug detected 🏻
debug detected 🏼
debug detected 🏽
debug detected 🏾
debug detected 🏿
debug detected 🐀
debug detected 🐁
debug detected 🐂
debug detected 🐃
debug detected 🐄
debug detected 🐅
debug detected 🐆
debug detected 🐇
debug detected 🐈
debug detected 🐉
debug detected 🐊
debug detected 🐋
debug detected 🐌
debug detected 🐍
debug detected 🐎
debug detected 🐏
debug detected 🐐
debug detected 🐑
debug detected 🐒
debug detected 🐓
debug detected 🐔
debug detected 🐕
debug detected 🐖
debug detected 🐗
debug detected 🐘
debug detected 🐙
debug detected 🐚
debug detected 🐛
debug detected 🐜
debug detected 🐝
debug detected 🐞
debug detected 🐟
debug detected 🐠
debug detected 🐡
debug detected 🐢
debug detected 🐣
debug detected 🐤
debug detected 🐥
debug detected 🐦
debug detected 🐧
debug detected 🐨
debug detected 🐩
debug detected 🐪
debug detected 🐫
debug detected 🐬
debug detected 🐭
debug detected 🐮
debug detected 🐯
debug detected 🐰
debug detected 🐱
debug detected 🐲
debug detected 🐳
debug detected 🐴
debug detected 🐵
debug detected 🐶
debug detected 🐷
debug detected 🐸
debug detected 🐹
debug detected 🐺
debug detected 🐻
debug detected 🐼
debug detected 🐽
debug detected 🐾
debug detected 🐿
debug detected 👀
debug detected 👁🗨
debug detected 👁
debug detected 👂🏻
debug detected 👂🏼
debug detected 👂🏽
debug detected 👂🏾
debug detected 👂🏿
debug detected 👂
debug detected 👃🏻
debug detected 👃🏼
debug detected 👃🏽
debug detected 👃🏾
debug detected 👃🏿
debug detected 👃
debug detected 👄
debug detected 👅
debug detected 👆🏻
debug detected 👆🏼
debug detected 👆🏽
debug detected 👆🏾
debug detected 👆🏿
debug detected 👆
debug detected 👇🏻
debug detected 👇🏼
debug detected 👇🏽
debug detected 👇🏾
debug detected 👇🏿
debug detected 👇
debug detected 👈🏻
debug detected 👈🏼
debug detected 👈🏽
debug detected 👈🏾
debug detected 👈🏿
debug detected 👈
debug detected 👉🏻
debug detected 👉🏼
debug detected 👉🏽
debug detected 👉🏾
debug detected 👉🏿
debug detected 👉
debug detected 👊🏻
debug detected 👊🏼
debug detected 👊🏽
debug detected 👊🏾
debug detected 👊🏿
debug detected 👊
debug detected 👋🏻
debug detected 👋🏼
debug detected 👋🏽
debug detected 👋🏾
debug detected 👋🏿
debug detected 👋
debug detected 👌🏻
debug detected 👌🏼
debug detected 👌🏽
debug detected 👌🏾
debug detected 👌🏿
debug detected 👌
debug detected 👍🏻
debug detected 👍🏼
debug detected 👍🏽
debug detected 👍🏾
debug detected 👍🏿
debug detected 👍
debug detected 👎🏻
debug detected 👎🏼
debug detected 👎🏽
debug detected 👎🏾
debug detected 👎🏿
debug detected 👎
debug detected 👏🏻
debug detected 👏🏼
debug detected 👏🏽
debug detected 👏🏾
debug detected 👏🏿
debug detected 👏
debug detected 👐🏻
debug detected 👐🏼
debug detected 👐🏽
debug detected 👐🏾
debug detected 👐🏿
debug detected 👐
debug detected 👑
debug detected 👒
debug detected 👓
debug detected 👔
debug detected 👕
debug detected 👖
debug detected 👗
debug detected 👘
debug detected 👙
debug detected 👚
debug detected 👛
debug detected 👜
debug detected 👝
debug detected 👞
debug detected 👟
debug detected 👠
debug detected 👡
debug detected 👢
debug detected 👣
debug detected 👤
debug detected 👥
debug detected 👦🏻
debug detected 👦🏼
debug detected 👦🏽
debug detected 👦🏾
debug detected 👦🏿
debug detected 👦
debug detected 👧🏻
debug detected 👧🏼
debug detected 👧🏽
debug detected 👧🏾
debug detected 👧🏿
debug detected 👧
debug detected 👨🏻🌾
debug detected 👨🏻🍳
debug detected 👨🏻🎓
debug detected 👨🏻🎤
debug detected 👨🏻🎨
debug detected 👨🏻🏫
debug detected 👨🏻🏭
debug detected 👨🏻💻
debug detected 👨🏻💼
debug detected 👨🏻🔧
debug detected 👨🏻🔬
debug detected 👨🏻🚀
debug detected 👨🏻🚒
debug detected 👨🏻⚕️
debug detected 👨🏻⚖️
debug detected 👨🏻✈️
debug detected 👨🏻
debug detected 👨🏼🌾
debug detected 👨🏼🍳
debug detected 👨🏼🎓
debug detected 👨🏼🎤
debug detected 👨🏼🎨
debug detected 👨🏼🏫
debug detected 👨🏼🏭
debug detected 👨🏼💻
debug detected 👨🏼💼
debug detected 👨🏼🔧
debug detected 👨🏼🔬
debug detected 👨🏼🚀
debug detected 👨🏼🚒
debug detected 👨🏼⚕️
debug detected 👨🏼⚖️
debug detected 👨🏼✈️
debug detected 👨🏼
debug detected 👨🏽🌾
debug detected 👨🏽🍳
debug detected 👨🏽🎓
debug detected 👨🏽🎤
debug detected 👨🏽🎨
debug detected 👨🏽🏫
debug detected 👨🏽🏭
debug detected 👨🏽💻
debug detected 👨🏽💼
debug detected 👨🏽🔧
debug detected 👨🏽🔬
debug detected 👨🏽🚀
debug detected 👨🏽🚒
debug detected 👨🏽⚕️
debug detected 👨🏽⚖️
debug detected 👨🏽✈️
debug detected 👨🏽
debug detected 👨🏾🌾
debug detected 👨🏾🍳
debug detected 👨🏾🎓
debug detected 👨🏾🎤
debug detected 👨🏾🎨
debug detected 👨🏾🏫
debug detected 👨🏾🏭
debug detected 👨🏾💻
debug detected 👨🏾💼
debug detected 👨🏾🔧
debug detected 👨🏾🔬
debug detected 👨🏾🚀
debug detected 👨🏾🚒
debug detected 👨🏾⚕️
debug detected 👨🏾⚖️
debug detected 👨🏾✈️
debug detected 👨🏾
debug detected 👨🏿🌾
debug detected 👨🏿🍳
debug detected 👨🏿🎓
debug detected 👨🏿🎤
debug detected 👨🏿🎨
debug detected 👨🏿🏫
debug detected 👨🏿🏭
debug detected 👨🏿💻
debug detected 👨🏿💼
debug detected 👨🏿🔧
debug detected 👨🏿🔬
debug detected 👨🏿🚀
debug detected 👨🏿🚒
debug detected 👨🏿⚕️
debug detected 👨🏿⚖️
debug detected 👨🏿✈️
debug detected 👨🏿
debug detected 👨🌾
debug detected 👨🍳
debug detected 👨🎓
debug detected 👨🎤
debug detected 👨🎨
debug detected 👨🏫
debug detected 👨🏭
debug detected 👨👦👦
debug detected 👨👦
debug detected 👨👧👦
debug detected 👨👧👧
debug detected 👨👧
debug detected 👨👨👦👦
debug detected 👨👨👦
debug detected 👨👨👧👦
debug detected 👨👨👧👧
debug detected 👨👨👧
debug detected 👨👩👦👦
debug detected 👨👩👦
debug detected 👨👩👧👦
debug detected 👨👩👧👧
debug detected 👨👩👧
debug detected 👨💻
debug detected 👨💼
debug detected 👨🔧
debug detected 👨🔬
debug detected 👨🚀
debug detected 👨🚒
debug detected 👨⚕️
debug detected 👨⚖️
debug detected 👨✈️
debug detected 👨❤️👨
debug detected 👨❤️💋👨
debug detected 👨
debug detected 👩🏻🌾
debug detected 👩🏻🍳
debug detected 👩🏻🎓
debug detected 👩🏻🎤
debug detected 👩🏻🎨
debug detected 👩🏻🏫
debug detected 👩🏻🏭
debug detected 👩🏻💻
debug detected 👩🏻💼
debug detected 👩🏻🔧
debug detected 👩🏻🔬
debug detected 👩🏻🚀
debug detected 👩🏻🚒
debug detected 👩🏻⚕️
debug detected 👩🏻⚖️
debug detected 👩🏻✈️
debug detected 👩🏻
debug detected 👩🏼🌾
debug detected 👩🏼🍳
debug detected 👩🏼🎓
debug detected 👩🏼🎤
debug detected 👩🏼🎨
debug detected 👩🏼🏫
debug detected 👩🏼🏭
debug detected 👩🏼💻
debug detected 👩🏼💼
debug detected 👩🏼🔧
debug detected 👩🏼🔬
debug detected 👩🏼🚀
debug detected 👩🏼🚒
debug detected 👩🏼⚕️
debug detected 👩🏼⚖️
debug detected 👩🏼✈️
debug detected 👩🏼
debug detected 👩🏽🌾
debug detected 👩🏽🍳
debug detected 👩🏽🎓
debug detected 👩🏽🎤
debug detected 👩🏽🎨
debug detected 👩🏽🏫
debug detected 👩🏽🏭
debug detected 👩🏽💻
debug detected 👩🏽💼
debug detected 👩🏽🔧
debug detected 👩🏽🔬
debug detected 👩🏽🚀
debug detected 👩🏽🚒
debug detected 👩🏽⚕️
debug detected 👩🏽⚖️
debug detected 👩🏽✈️
debug detected 👩🏽
debug detected 👩🏾🌾
debug detected 👩🏾🍳
debug detected 👩🏾🎓
debug detected 👩🏾🎤
debug detected 👩🏾🎨
debug detected 👩🏾🏫
debug detected 👩🏾🏭
debug detected 👩🏾💻
debug detected 👩🏾💼
debug detected 👩🏾🔧
debug detected 👩🏾🔬
debug detected 👩🏾🚀
debug detected 👩🏾🚒
debug detected 👩🏾⚕️
debug detected 👩🏾⚖️
debug detected 👩🏾✈️
debug detected 👩🏾
debug detected 👩🏿🌾
debug detected 👩🏿🍳
debug detected 👩🏿🎓
debug detected 👩🏿🎤
debug detected 👩🏿🎨
debug detected 👩🏿🏫
debug detected 👩🏿🏭
debug detected 👩🏿💻
debug detected 👩🏿💼
debug detected 👩🏿🔧
debug detected 👩🏿🔬
debug detected 👩🏿🚀
debug detected 👩🏿🚒
debug detected 👩🏿⚕️
debug detected 👩🏿⚖️
debug detected 👩🏿✈️
debug detected 👩🏿
debug detected 👩🌾
debug detected 👩🍳
debug detected 👩🎓
debug detected 👩🎤
debug detected 👩🎨
debug detected 👩🏫
debug detected 👩🏭
debug detected 👩👦👦
debug detected 👩👦
debug detected 👩👧👦
debug detected 👩👧👧
debug detected 👩👧
debug detected 👩👩👦👦
debug detected 👩👩👦
debug detected 👩👩👧👦
debug detected 👩👩👧👧
debug detected 👩👩👧
debug detected 👩💻
debug detected 👩💼
debug detected 👩🔧
debug detected 👩🔬
debug detected 👩🚀
debug detected 👩🚒
debug detected 👩⚕️
debug detected 👩⚖️
debug detected 👩✈️
debug detected 👩❤️👨
debug detected 👩❤️👩
debug detected 👩❤️💋👨
debug detected 👩❤️💋👩
debug detected 👩
debug detected 👪🏻
debug detected 👪🏼
debug detected 👪🏽
debug detected 👪🏾
debug detected 👪🏿
debug detected 👪
debug detected 👫🏻
debug detected 👫🏼
debug detected 👫🏽
debug detected 👫🏾
debug detected 👫🏿
debug detected 👫
debug detected 👬🏻
debug detected 👬🏼
debug detected 👬🏽
debug detected 👬🏾
debug detected 👬🏿
debug detected 👬
debug detected 👭🏻
debug detected 👭🏼
debug detected 👭🏽
debug detected 👭🏾
debug detected 👭🏿
debug detected 👭
debug detected 👮🏻♀️
debug detected 👮🏻♂️
debug detected 👮🏻
debug detected 👮🏼♀️
debug detected 👮🏼♂️
debug detected 👮🏼
debug detected 👮🏽♀️
debug detected 👮🏽♂️
debug detected 👮🏽
debug detected 👮🏾♀️
debug detected 👮🏾♂️
debug detected 👮🏾
debug detected 👮🏿♀️
debug detected 👮🏿♂️
debug detected 👮🏿
debug detected 👮♀️
debug detected 👮♂️
debug detected 👮
debug detected 👯🏻♀️
debug detected 👯🏻♂️
debug detected 👯🏻
debug detected 👯🏼♀️
debug detected 👯🏼♂️
debug detected 👯🏼
debug detected 👯🏽♀️
debug detected 👯🏽♂️
debug detected 👯🏽
debug detected 👯🏾♀️
debug detected 👯🏾♂️
debug detected 👯🏾
debug detected 👯🏿♀️
debug detected 👯🏿♂️
debug detected 👯🏿
debug detected 👯♀️
debug detected 👯♂️
debug detected 👯
debug detected 👰🏻
debug detected 👰🏼
debug detected 👰🏽
debug detected 👰🏾
debug detected 👰🏿
debug detected 👰
debug detected 👱🏻♀️
debug detected 👱🏻♂️
debug detected 👱🏻
debug detected 👱🏼♀️
debug detected 👱🏼♂️
debug detected 👱🏼
debug detected 👱🏽♀️
debug detected 👱🏽♂️
debug detected 👱🏽
debug detected 👱🏾♀️
debug detected 👱🏾♂️
debug detected 👱🏾
debug detected 👱🏿♀️
debug detected 👱🏿♂️
debug detected 👱🏿
debug detected 👱♀️
debug detected 👱♂️
debug detected 👱
debug detected 👲🏻
debug detected 👲🏼
debug detected 👲🏽
debug detected 👲🏾
debug detected 👲🏿
debug detected 👲
debug detected 👳🏻♀️
debug detected 👳🏻♂️
debug detected 👳🏻
debug detected 👳🏼♀️
debug detected 👳🏼♂️
debug detected 👳🏼
debug detected 👳🏽♀️
debug detected 👳🏽♂️
debug detected 👳🏽
debug detected 👳🏾♀️
debug detected 👳🏾♂️
debug detected 👳🏾
debug detected 👳🏿♀️
debug detected 👳🏿♂️
debug detected 👳🏿
debug detected 👳♀️
debug detected 👳♂️
debug detected 👳
debug detected 👴🏻
debug detected 👴🏼
debug detected 👴🏽
debug detected 👴🏾
debug detected 👴🏿
debug detected 👴
debug detected 👵🏻
debug detected 👵🏼
debug detected 👵🏽
debug detected 👵🏾
debug detected 👵🏿
debug detected 👵
debug detected 👶🏻
debug detected 👶🏼
debug detected 👶🏽
debug detected 👶🏾
debug detected 👶🏿
debug detected 👶
debug detected 👷🏻♀️
debug detected 👷🏻♂️
debug detected 👷🏻
debug detected 👷🏼♀️
debug detected 👷🏼♂️
debug detected 👷🏼
debug detected 👷🏽♀️
debug detected 👷🏽♂️
debug detected 👷🏽
debug detected 👷🏾♀️
debug detected 👷🏾♂️
debug detected 👷🏾
debug detected 👷🏿♀️
debug detected 👷🏿♂️
debug detected 👷🏿
debug detected 👷♀️
debug detected 👷♂️
debug detected 👷
debug detected 👸🏻
debug detected 👸🏼
debug detected 👸🏽
debug detected 👸🏾
debug detected 👸🏿
debug detected 👸
debug detected 👹
debug detected 👺
debug detected 👻
debug detected 👼🏻
debug detected 👼🏼
debug detected 👼🏽
debug detected 👼🏾
debug detected 👼🏿
debug detected 👼
debug detected 👽
debug detected 👾
debug detected 👿
debug detected 💀
debug detected 💁🏻♀️
debug detected 💁🏻♂️
debug detected 💁🏻
debug detected 💁🏼♀️
debug detected 💁🏼♂️
debug detected 💁🏼
debug detected 💁🏽♀️
debug detected 💁🏽♂️
debug detected 💁🏽
debug detected 💁🏾♀️
debug detected 💁🏾♂️
debug detected 💁🏾
debug detected 💁🏿♀️
debug detected 💁🏿♂️
debug detected 💁🏿
debug detected 💁♀️
debug detected 💁♂️
debug detected 💁
debug detected 💂🏻♀️
debug detected 💂🏻♂️
debug detected 💂🏻
debug detected 💂🏼♀️
debug detected 💂🏼♂️
debug detected 💂🏼
debug detected 💂🏽♀️
debug detected 💂🏽♂️
debug detected 💂🏽
debug detected 💂🏾♀️
debug detected 💂🏾♂️
debug detected 💂🏾
debug detected 💂🏿♀️
debug detected 💂🏿♂️
debug detected 💂🏿
debug detected 💂♀️
debug detected 💂♂️
debug detected 💂
debug detected 💃🏻
debug detected 💃🏼
debug detected 💃🏽
debug detected 💃🏾
debug detected 💃🏿
debug detected 💃
debug detected 💄
debug detected 💅🏻
debug detected 💅🏼
debug detected 💅🏽
debug detected 💅🏾
debug detected 💅🏿
debug detected 💅
debug detected 💆🏻♀️
debug detected 💆🏻♂️
debug detected 💆🏻
debug detected 💆🏼♀️
debug detected 💆🏼♂️
debug detected 💆🏼
debug detected 💆🏽♀️
debug detected 💆🏽♂️
debug detected 💆🏽
debug detected 💆🏾♀️
debug detected 💆🏾♂️
debug detected 💆🏾
debug detected 💆🏿♀️
debug detected 💆🏿♂️
debug detected 💆🏿
debug detected 💆♀️
debug detected 💆♂️
debug detected 💆
debug detected 💇🏻♀️
debug detected 💇🏻♂️
debug detected 💇🏻
debug detected 💇🏼♀️
debug detected 💇🏼♂️
debug detected 💇🏼
debug detected 💇🏽♀️
debug detected 💇🏽♂️
debug detected 💇🏽
debug detected 💇🏾♀️
debug detected 💇🏾♂️
debug detected 💇🏾
debug detected 💇🏿♀️
debug detected 💇🏿♂️
debug detected 💇🏿
debug detected 💇♀️
debug detected 💇♂️
debug detected 💇
debug detected 💈
debug detected 💉
debug detected 💊
debug detected 💋
debug detected 💌
debug detected 💍
debug detected 💎
debug detected 💏
debug detected 💐
debug detected 💑
debug detected 💒
debug detected 💓
debug detected 💔
debug detected 💕
debug detected 💖
debug detected 💗
debug detected 💘
debug detected 💙
debug detected 💚
debug detected 💛
debug detected 💜
debug detected 💝
debug detected 💞
debug detected 💟
debug detected 💠
debug detected 💡
debug detected 💢
debug detected 💣
debug detected 💤
debug detected 💥
debug detected 💦
debug detected 💧
debug detected 💨
debug detected 💩
debug detected 💪🏻
debug detected 💪🏼
debug detected 💪🏽
debug detected 💪🏾
debug detected 💪🏿
debug detected 💪
debug detected 💫
debug detected 💬
debug detected 💭
debug detected 💮
debug detected 💯
debug detected 💰
debug detected 💱
debug detected 💲
debug detected 💳
debug detected 💴
debug detected 💵
debug detected 💶
debug detected 💷
debug detected 💸
debug detected 💹
debug detected 💺
debug detected 💻
debug detected 💼
debug detected 💽
debug detected 💾
debug detected 💿
debug detected 📀
debug detected 📁
debug detected 📂
debug detected 📃
debug detected 📄
debug detected 📅
debug detected 📆
debug detected 📇
debug detected 📈
debug detected 📉
debug detected 📊
debug detected 📋
debug detected 📌
debug detected 📍
debug detected 📎
debug detected 📏
debug detected 📐
debug detected 📑
debug detected 📒
debug detected 📓
debug detected 📔
debug detected 📕
debug detected 📖
debug detected 📗
debug detected 📘
debug detected 📙
debug detected 📚
debug detected 📛
debug detected 📜
debug detected 📝
debug detected 📞
debug detected 📟
debug detected 📠
debug detected 📡
debug detected 📢
debug detected 📣
debug detected 📤
debug detected 📥
debug detected 📦
debug detected 📧
debug detected 📨
debug detected 📩
debug detected 📪
debug detected 📫
debug detected 📬
debug detected 📭
debug detected 📮
debug detected 📯
debug detected 📰
debug detected 📱
debug detected 📲
debug detected 📳
debug detected 📴
debug detected 📵
debug detected 📶
debug detected 📷
debug detected 📸
debug detected 📹
debug detected 📺
debug detected 📻
debug detected 📼
debug detected 📽
debug detected 📿
debug detected 🔀
debug detected 🔁
debug detected 🔂
debug detected 🔃
debug detected 🔄
debug detected 🔅
debug detected 🔆
debug detected 🔇
debug detected 🔈
debug detected 🔉
debug detected 🔊
debug detected 🔋
debug detected 🔌
debug detected 🔍
debug detected 🔎
debug detected 🔏
debug detected 🔐
debug detected 🔑
debug detected 🔒
debug detected 🔓
debug detected 🔔
debug detected 🔕
debug detected 🔖
debug detected 🔗
debug detected 🔘
debug detected 🔙
debug detected 🔚
debug detected 🔛
debug detected 🔜
debug detected 🔝
debug detected 🔞
debug detected 🔟
debug detected 🔠
debug detected 🔡
debug detected 🔢
debug detected 🔣
debug detected 🔤
debug detected 🔥
debug detected 🔦
debug detected 🔧
debug detected 🔨
debug detected 🔩
debug detected 🔪
debug detected 🔫
debug detected 🔬
debug detected 🔭
debug detected 🔮
debug detected 🔯
debug detected 🔰
debug detected 🔱
debug detected 🔲
debug detected 🔳
debug detected 🔴
debug detected 🔵
debug detected 🔶
debug detected 🔷
debug detected 🔸
debug detected 🔹
debug detected 🔺
debug detected 🔻
debug detected 🔼
debug detected 🔽
debug detected 🕉
debug detected 🕊
debug detected 🕋
debug detected 🕌
debug detected 🕍
debug detected 🕎
debug detected 🕐
debug detected 🕑
debug detected 🕒
debug detected 🕓
debug detected 🕔
debug detected 🕕
debug detected 🕖
debug detected 🕗
debug detected 🕘
debug detected 🕙
debug detected 🕚
debug detected 🕛
debug detected 🕜
debug detected 🕝
debug detected 🕞
debug detected 🕟
debug detected 🕠
debug detected 🕡
debug detected 🕢
debug detected 🕣
debug detected 🕤
debug detected 🕥
debug detected 🕦
debug detected 🕧
debug detected 🕯
debug detected 🕰
debug detected 🕳
debug detected 🕴🏻
debug detected 🕴🏼
debug detected 🕴🏽
debug detected 🕴🏾
debug detected 🕴🏿
debug detected 🕴
debug detected 🕵🏻♀️
debug detected 🕵🏻♂️
debug detected 🕵🏻
debug detected 🕵🏼♀️
debug detected 🕵🏼♂️
debug detected 🕵🏼
debug detected 🕵🏽♀️
debug detected 🕵🏽♂️
debug detected 🕵🏽
debug detected 🕵🏾♀️
debug detected 🕵🏾♂️
debug detected 🕵🏾
debug detected 🕵🏿♀️
debug detected 🕵🏿♂️
debug detected 🕵🏿
debug detected 🕵️♀️
debug detected 🕵️♂️
debug detected 🕵
debug detected 🕶
debug detected 🕷
debug detected 🕸
debug detected 🕹
debug detected 🕺🏻
debug detected 🕺🏼
debug detected 🕺🏽
debug detected 🕺🏾
debug detected 🕺🏿
debug detected 🕺
debug detected 🖇
debug detected 🖊
debug detected 🖋
debug detected 🖌
debug detected 🖍
debug detected 🖐🏻
debug detected 🖐🏼
debug detected 🖐🏽
debug detected 🖐🏾
debug detected 🖐🏿
debug detected 🖐
debug detected 🖕🏻
debug detected 🖕🏼
debug detected 🖕🏽
debug detected 🖕🏾
debug detected 🖕🏿
debug detected 🖕
debug detected 🖖🏻
debug detected 🖖🏼
debug detected 🖖🏽
debug detected 🖖🏾
debug detected 🖖🏿
debug detected 🖖
debug detected 🖤
debug detected 🖥
debug detected 🖨
debug detected 🖱
debug detected 🖲
debug detected 🖼
debug detected 🗂
debug detected 🗃
debug detected 🗄
debug detected 🗑
debug detected 🗒
debug detected 🗓
debug detected 🗜
debug detected 🗝
debug detected 🗞
debug detected 🗡
debug detected 🗣
debug detected 🗨
debug detected 🗯
debug detected 🗳
debug detected 🗺
debug detected 🗻
debug detected 🗼
debug detected 🗽
debug detected 🗾
debug detected 🗿
debug detected 😀
debug detected 😁
debug detected 😂
debug detected 😃
debug detected 😄
debug detected 😅
debug detected 😆
debug detected 😇
debug detected 😈
debug detected 😉
debug detected 😊
debug detected 😋
debug detected 😌
debug detected 😍
debug detected 😎
debug detected 😏
debug detected 😐
debug detected 😑
debug detected 😒
debug detected 😓
debug detected 😔
debug detected 😕
debug detected 😖
debug detected 😗
debug detected 😘
debug detected 😙
debug detected 😚
debug detected 😛
debug detected 😜
debug detected 😝
debug detected 😞
debug detected 😟
debug detected 😠
debug detected 😡
debug detected 😢
debug detected 😣
debug detected 😤
debug detected 😥
debug detected 😦
debug detected 😧
debug detected 😨
debug detected 😩
debug detected 😪
debug detected 😫
debug detected 😬
debug detected 😭
debug detected 😮
debug detected 😯
debug detected 😰
debug detected 😱
debug detected 😲
debug detected 😳
debug detected 😴
debug detected 😵
debug detected 😶
debug detected 😷
debug detected 😸
debug detected 😹
debug detected 😺
debug detected 😻
debug detected 😼
debug detected 😽
debug detected 😾
debug detected 😿
debug detected 🙀
debug detected 🙁
debug detected 🙂
debug detected 🙃
debug detected 🙄
debug detected 🙅🏻♀️
debug detected 🙅🏻♂️
debug detected 🙅🏻
debug detected 🙅🏼♀️
debug detected 🙅🏼♂️
debug detected 🙅🏼
debug detected 🙅🏽♀️
debug detected 🙅🏽♂️
debug detected 🙅🏽
debug detected 🙅🏾♀️
debug detected 🙅🏾♂️
debug detected 🙅🏾
debug detected 🙅🏿♀️
debug detected 🙅🏿♂️
debug detected 🙅🏿
debug detected 🙅♀️
debug detected 🙅♂️
debug detected 🙅
debug detected 🙆🏻♀️
debug detected 🙆🏻♂️
debug detected 🙆🏻
debug detected 🙆🏼♀️
debug detected 🙆🏼♂️
debug detected 🙆🏼
debug detected 🙆🏽♀️
debug detected 🙆🏽♂️
debug detected 🙆🏽
debug detected 🙆🏾♀️
debug detected 🙆🏾♂️
debug detected 🙆🏾
debug detected 🙆🏿♀️
debug detected 🙆🏿♂️
debug detected 🙆🏿
debug detected 🙆♀️
debug detected 🙆♂️
debug detected 🙆
debug detected 🙇🏻♀️
debug detected 🙇🏻♂️
debug detected 🙇🏻
debug detected 🙇🏼♀️
debug detected 🙇🏼♂️
debug detected 🙇🏼
debug detected 🙇🏽♀️
debug detected 🙇🏽♂️
debug detected 🙇🏽
debug detected 🙇🏾♀️
debug detected 🙇🏾♂️
debug detected 🙇🏾
debug detected 🙇🏿♀️
debug detected 🙇🏿♂️
debug detected 🙇🏿
debug detected 🙇♀️
debug detected 🙇♂️
debug detected 🙇
debug detected 🙈
debug detected 🙉
debug detected 🙊
debug detected 🙋🏻♀️
debug detected 🙋🏻♂️
debug detected 🙋🏻
debug detected 🙋🏼♀️
debug detected 🙋🏼♂️
debug detected 🙋🏼
debug detected 🙋🏽♀️
debug detected 🙋🏽♂️
debug detected 🙋🏽
debug detected 🙋🏾♀️
debug detected 🙋🏾♂️
debug detected 🙋🏾
debug detected 🙋🏿♀️
debug detected 🙋🏿♂️
debug detected 🙋🏿
debug detected 🙋♀️
debug detected 🙋♂️
debug detected 🙋
debug detected 🙌🏻
debug detected 🙌🏼
debug detected 🙌🏽
debug detected 🙌🏾
debug detected 🙌🏿
debug detected 🙌
debug detected 🙍🏻♀️
debug detected 🙍🏻♂️
debug detected 🙍🏻
debug detected 🙍🏼♀️
debug detected 🙍🏼♂️
debug detected 🙍🏼
debug detected 🙍🏽♀️
debug detected 🙍🏽♂️
debug detected 🙍🏽
debug detected 🙍🏾♀️
debug detected 🙍🏾♂️
debug detected 🙍🏾
debug detected 🙍🏿♀️
debug detected 🙍🏿♂️
debug detected 🙍🏿
debug detected 🙍♀️
debug detected 🙍♂️
debug detected 🙍
debug detected 🙎🏻♀️
debug detected 🙎🏻♂️
debug detected 🙎🏻
debug detected 🙎🏼♀️
debug detected 🙎🏼♂️
debug detected 🙎🏼
debug detected 🙎🏽♀️
debug detected 🙎🏽♂️
debug detected 🙎🏽
debug detected 🙎🏾♀️
debug detected 🙎🏾♂️
debug detected 🙎🏾
debug detected 🙎🏿♀️
debug detected 🙎🏿♂️
debug detected 🙎🏿
debug detected 🙎♀️
debug detected 🙎♂️
debug detected 🙎
debug detected 🙏🏻
debug detected 🙏🏼
debug detected 🙏🏽
debug detected 🙏🏾
debug detected 🙏🏿
debug detected 🙏
debug detected 🚀
debug detected 🚁
debug detected 🚂
debug detected 🚃
debug detected 🚄
debug detected 🚅
debug detected 🚆
debug detected 🚇
debug detected 🚈
debug detected 🚉
debug detected 🚊
debug detected 🚋
debug detected 🚌
debug detected 🚍
debug detected 🚎
debug detected 🚏
debug detected 🚐
debug detected 🚑
debug detected 🚒
debug detected 🚓
debug detected 🚔
debug detected 🚕
debug detected 🚖
debug detected 🚗
debug detected 🚘
debug detected 🚙
debug detected 🚚
debug detected 🚛
debug detected 🚜
debug detected 🚝
debug detected 🚞
debug detected 🚟
debug detected 🚠
debug detected 🚡
debug detected 🚢
debug detected 🚣🏻♀️
debug detected 🚣🏻♂️
debug detected 🚣🏻
debug detected 🚣🏼♀️
debug detected 🚣🏼♂️
debug detected 🚣🏼
debug detected 🚣🏽♀️
debug detected 🚣🏽♂️
debug detected 🚣🏽
debug detected 🚣🏾♀️
debug detected 🚣🏾♂️
debug detected 🚣🏾
debug detected 🚣🏿♀️
debug detected 🚣🏿♂️
debug detected 🚣🏿
debug detected 🚣♀️
debug detected 🚣♂️
debug detected 🚣
debug detected 🚤
debug detected 🚥
debug detected 🚦
debug detected 🚧
debug detected 🚨
debug detected 🚩
debug detected 🚪
debug detected 🚫
debug detected 🚬
debug detected 🚭
debug detected 🚮
debug detected 🚯
debug detected 🚰
debug detected 🚱
debug detected 🚲
debug detected 🚳
debug detected 🚴🏻♀️
debug detected 🚴🏻♂️
debug detected 🚴🏻
debug detected 🚴🏼♀️
debug detected 🚴🏼♂️
debug detected 🚴🏼
debug detected 🚴🏽♀️
debug detected 🚴🏽♂️
debug detected 🚴🏽
debug detected 🚴🏾♀️
debug detected 🚴🏾♂️
debug detected 🚴🏾
debug detected 🚴🏿♀️
debug detected 🚴🏿♂️
debug detected 🚴🏿
debug detected 🚴♀️
debug detected 🚴♂️
debug detected 🚴
debug detected 🚵🏻♀️
debug detected 🚵🏻♂️
debug detected 🚵🏻
debug detected 🚵🏼♀️
debug detected 🚵🏼♂️
debug detected 🚵🏼
debug detected 🚵🏽♀️
debug detected 🚵🏽♂️
debug detected 🚵🏽
debug detected 🚵🏾♀️
debug detected 🚵🏾♂️
debug detected 🚵🏾
debug detected 🚵🏿♀️
debug detected 🚵🏿♂️
debug detected 🚵🏿
debug detected 🚵♀️
debug detected 🚵♂️
debug detected 🚵
debug detected 🚶🏻♀️
debug detected 🚶🏻♂️
debug detected 🚶🏻
debug detected 🚶🏼♀️
debug detected 🚶🏼♂️
debug detected 🚶🏼
debug detected 🚶🏽♀️
debug detected 🚶🏽♂️
debug detected 🚶🏽
debug detected 🚶🏾♀️
debug detected 🚶🏾♂️
debug detected 🚶🏾
debug detected 🚶🏿♀️
debug detected 🚶🏿♂️
debug detected 🚶🏿
debug detected 🚶♀️
debug detected 🚶♂️
debug detected 🚶
debug detected 🚷
debug detected 🚸
debug detected 🚹
debug detected 🚺
debug detected 🚻
debug detected 🚼
debug detected 🚽
debug detected 🚾
debug detected 🚿
debug detected 🛀🏻
debug detected 🛀🏼
debug detected 🛀🏽
debug detected 🛀🏾
debug detected 🛀🏿
debug detected 🛀
debug detected 🛁
debug detected 🛂
debug detected 🛃
debug detected 🛄
debug detected 🛅
debug detected 🛋
debug detected 🛌🏻
debug detected 🛌🏼
debug detected 🛌🏽
debug detected 🛌🏾
debug detected 🛌🏿
debug detected 🛌
debug detected 🛍
debug detected 🛎
debug detected 🛏
debug detected 🛐
debug detected 🛑
debug detected 🛒
debug detected 🛠
debug detected 🛡
debug detected 🛢
debug detected 🛣
debug detected 🛤
debug detected 🛥
debug detected 🛩
debug detected 🛫
debug detected 🛬
debug detected 🛰
debug detected 🛳
debug detected 🛴
debug detected 🛵
debug detected 🛶
debug detected 🤐
debug detected 🤑
debug detected 🤒
debug detected 🤓
debug detected 🤔
debug detected 🤕
debug detected 🤖
debug detected 🤗
debug detected 🤘🏻
debug detected 🤘🏼
debug detected 🤘🏽
debug detected 🤘🏾
debug detected 🤘🏿
debug detected 🤘
debug detected 🤙🏻
debug detected 🤙🏼
debug detected 🤙🏽
debug detected 🤙🏾
debug detected 🤙🏿
debug detected 🤙
debug detected 🤚🏻
debug detected 🤚🏼
debug detected 🤚🏽
debug detected 🤚🏾
debug detected 🤚🏿
debug detected 🤚
debug detected 🤛🏻
debug detected 🤛🏼
debug detected 🤛🏽
debug detected 🤛🏾
debug detected 🤛🏿
debug detected 🤛
debug detected 🤜🏻
debug detected 🤜🏼
debug detected 🤜🏽
debug detected 🤜🏾
debug detected 🤜🏿
debug detected 🤜
debug detected 🤝🏻
debug detected 🤝🏼
debug detected 🤝🏽
debug detected 🤝🏾
debug detected 🤝🏿
debug detected 🤝
debug detected 🤞🏻
debug detected 🤞🏼
debug detected 🤞🏽
debug detected 🤞🏾
debug detected 🤞🏿
debug detected 🤞
debug detected 🤠
debug detected 🤡
debug detected 🤢
debug detected 🤣
debug detected 🤤
debug detected 🤥
debug detected 🤦🏻♀️
debug detected 🤦🏻♂️
debug detected 🤦🏻
debug detected 🤦🏼♀️
debug detected 🤦🏼♂️
debug detected 🤦🏼
debug detected 🤦🏽♀️
debug detected 🤦🏽♂️
debug detected 🤦🏽
debug detected 🤦🏾♀️
debug detected 🤦🏾♂️
debug detected 🤦🏾
debug detected 🤦🏿♀️
debug detected 🤦🏿♂️
debug detected 🤦🏿
debug detected 🤦♀️
debug detected 🤦♂️
debug detected 🤦
debug detected 🤧
debug detected 🤰🏻
debug detected 🤰🏼
debug detected 🤰🏽
debug detected 🤰🏾
debug detected 🤰🏿
debug detected 🤰
debug detected 🤳🏻
debug detected 🤳🏼
debug detected 🤳🏽
debug detected 🤳🏾
debug detected 🤳🏿
debug detected 🤳
debug detected 🤴🏻
debug detected 🤴🏼
debug detected 🤴🏽
debug detected 🤴🏾
debug detected 🤴🏿
debug detected 🤴
debug detected 🤵🏻
debug detected 🤵🏼
debug detected 🤵🏽
debug detected 🤵🏾
debug detected 🤵🏿
debug detected 🤵
debug detected 🤶🏻
debug detected 🤶🏼
debug detected 🤶🏽
debug detected 🤶🏾
debug detected 🤶🏿
debug detected 🤶
debug detected 🤷🏻♀️
debug detected 🤷🏻♂️
debug detected 🤷🏻
debug detected 🤷🏼♀️
debug detected 🤷🏼♂️
debug detected 🤷🏼
debug detected 🤷🏽♀️
debug detected 🤷🏽♂️
debug detected 🤷🏽
debug detected 🤷🏾♀️
debug detected 🤷🏾♂️
debug detected 🤷🏾
debug detected 🤷🏿♀️
debug detected 🤷🏿♂️
debug detected 🤷🏿
debug detected 🤷♀️
debug detected 🤷♂️
debug detected 🤷
debug detected 🤸🏻♀️
debug detected 🤸🏻♂️
debug detected 🤸🏻
debug detected 🤸🏼♀️
debug detected 🤸🏼♂️
debug detected 🤸🏼
debug detected 🤸🏽♀️
debug detected 🤸🏽♂️
debug detected 🤸🏽
debug detected 🤸🏾♀️
debug detected 🤸🏾♂️
debug detected 🤸🏾
debug detected 🤸🏿♀️
debug detected 🤸🏿♂️
debug detected 🤸🏿
debug detected 🤸♀️
debug detected 🤸♂️
debug detected 🤸
debug detected 🤹🏻♀️
debug detected 🤹🏻♂️
debug detected 🤹🏻
debug detected 🤹🏼♀️
debug detected 🤹🏼♂️
debug detected 🤹🏼
debug detected 🤹🏽♀️
debug detected 🤹🏽♂️
debug detected 🤹🏽
debug detected 🤹🏾♀️
debug detected 🤹🏾♂️
debug detected 🤹🏾
debug detected 🤹🏿♀️
debug detected 🤹🏿♂️
debug detected 🤹🏿
debug detected 🤹♀️
debug detected 🤹♂️
debug detected 🤹
debug detected 🤺
debug detected 🤼🏻♀️
debug detected 🤼🏻♂️
debug detected 🤼🏻
debug detected 🤼🏼♀️
debug detected 🤼🏼♂️
debug detected 🤼🏼
debug detected 🤼🏽♀️
debug detected 🤼🏽♂️
debug detected 🤼🏽
debug detected 🤼🏾♀️
debug detected 🤼🏾♂️
debug detected 🤼🏾
debug detected 🤼🏿♀️
debug detected 🤼🏿♂️
debug detected 🤼🏿
debug detected 🤼♀️
debug detected 🤼♂️
debug detected 🤼
debug detected 🤽🏻♀️
debug detected 🤽🏻♂️
debug detected 🤽🏻
debug detected 🤽🏼♀️
debug detected 🤽🏼♂️
debug detected 🤽🏼
debug detected 🤽🏽♀️
debug detected 🤽🏽♂️
debug detected 🤽🏽
debug detected 🤽🏾♀️
debug detected 🤽🏾♂️
debug detected 🤽🏾
debug detected 🤽🏿♀️
debug detected 🤽🏿♂️
debug detected 🤽🏿
debug detected 🤽♀️
debug detected 🤽♂️
debug detected 🤽
debug detected 🤾🏻♀️
debug detected 🤾🏻♂️
debug detected 🤾🏻
debug detected 🤾🏼♀️
debug detected 🤾🏼♂️
debug detected 🤾🏼
debug detected 🤾🏽♀️
debug detected 🤾🏽♂️
debug detected 🤾🏽
debug detected 🤾🏾♀️
debug detected 🤾🏾♂️
debug detected 🤾🏾
debug detected 🤾🏿♀️
debug detected 🤾🏿♂️
debug detected 🤾🏿
debug detected 🤾♀️
debug detected 🤾♂️
debug detected 🤾
debug detected 🥀
debug detected 🥁
debug detected 🥂
debug detected 🥃
debug detected 🥄
debug detected 🥅
debug detected 🥇
debug detected 🥈
debug detected 🥉
debug detected 🥊
debug detected 🥋
debug detected 🥐
debug detected 🥑
debug detected 🥒
debug detected 🥓
debug detected 🥔
debug detected 🥕
debug detected 🥖
debug detected 🥗
debug detected 🥘
debug detected 🥙
debug detected 🥚
debug detected 🥛
debug detected 🥜
debug detected 🥝
debug detected 🥞
debug detected 🦀
debug detected 🦁
debug detected 🦂
debug detected 🦃
debug detected 🦄
debug detected 🦅
debug detected 🦆
debug detected 🦇
debug detected 🦈
debug detected 🦉
debug detected 🦊
debug detected 🦋
debug detected 🦌
debug detected 🦍
debug detected 🦎
debug detected 🦏
debug detected 🦐
debug detected 🦑
debug detected 🧀
debug detected ‼
debug detected ⁉
debug detected ™
debug detected ℹ
debug detected ↔
debug detected ↕
debug detected ↖
debug detected ↗
debug detected ↘
debug detected ↙
debug detected ↩
debug detected ↪
debug detected #⃣
debug detected ⌚
debug detected ⌛
debug detected ⌨
debug detected ⏏
debug detected ⏩
debug detected ⏪
debug detected ⏫
debug detected ⏬
debug detected ⏭
debug detected ⏮
debug detected ⏯
debug detected ⏰
debug detected ⏱
debug detected ⏲
debug detected ⏳
debug detected ⏸
debug detected ⏹
debug detected ⏺
debug detected Ⓜ
debug detected ▪
debug detected ▫
debug detected ▶
debug detected ◀
debug detected ◻
debug detected ◼
debug detected ◽
debug detected ◾
debug detected ☀
debug detected ☁
debug detected ☂
debug detected ☃
debug detected ☄
debug detected ☎
debug detected ☑
debug detected ☔
debug detected ☕
debug detected ☘
debug detected ☝🏻
debug detected ☝🏼
debug detected ☝🏽
debug detected ☝🏾
debug detected ☝🏿
debug detected ☝
debug detected ☠
debug detected ☢
debug detected ☣
debug detected ☦
debug detected ☪
debug detected ☮
debug detected ☯
debug detected ☸
debug detected ☹
debug detected ☺
debug detected ♀
debug detected ♂
debug detected ♈
debug detected ♉
debug detected ♊
debug detected ♋
debug detected ♌
debug detected ♍
debug detected ♎
debug detected ♏
debug detected ♐
debug detected ♑
debug detected ♒
debug detected ♓
debug detected ♠
debug detected ♣
debug detected ♥
debug detected ♦
debug detected ♨
debug detected ♻
debug detected ♿
debug detected ⚒
debug detected ⚓
debug detected ⚔
debug detected ⚕
debug detected ⚖
debug detected ⚗
debug detected ⚙
debug detected ⚛
debug detected ⚜
debug detected ⚠
debug detected ⚡
debug detected ⚪
debug detected ⚫
debug detected ⚰
debug detected ⚱
debug detected ⚽
debug detected ⚾
debug detected ⛄
debug detected ⛅
debug detected ⛈
debug detected ⛎
debug detected ⛏
debug detected ⛑
debug detected ⛓
debug detected ⛔
debug detected ⛩
debug detected ⛪
debug detected ⛰
debug detected ⛱
debug detected ⛲
debug detected ⛳
debug detected ⛴
debug detected ⛵
debug detected ⛷🏻
debug detected ⛷🏼
debug detected ⛷🏽
debug detected ⛷🏾
debug detected ⛷🏿
debug detected ⛷
debug detected ⛸
debug detected ⛹🏻♀️
debug detected ⛹🏻♂️
debug detected ⛹🏻
debug detected ⛹🏼♀️
debug detected ⛹🏼♂️
debug detected ⛹🏼
debug detected ⛹🏽♀️
debug detected ⛹🏽♂️
debug detected ⛹🏽
debug detected ⛹🏾♀️
debug detected ⛹🏾♂️
debug detected ⛹🏾
debug detected ⛹🏿♀️
debug detected ⛹🏿♂️
debug detected ⛹🏿
debug detected ⛹️♀️
debug detected ⛹️♂️
debug detected ⛹
debug detected ⛺
debug detected ⛽
debug detected ✂
debug detected ✅
debug detected ✈
debug detected ✉
debug detected ✊🏻
debug detected ✊🏼
debug detected ✊🏽
debug detected ✊🏾
debug detected ✊🏿
debug detected ✊
debug detected ✋🏻
debug detected ✋🏼
debug detected ✋🏽
debug detected ✋🏾
debug detected ✋🏿
debug detected ✋
debug detected ✌🏻
debug detected ✌🏼
debug detected ✌🏽
debug detected ✌🏾
debug detected ✌🏿
debug detected ✌
debug detected ✍🏻
debug detected ✍🏼
debug detected ✍🏽
debug detected ✍🏾
debug detected ✍🏿
debug detected ✍
debug detected ✏
debug detected ✒
debug detected ✔
debug detected ✖
debug detected ✝
debug detected ✡
debug detected ✨
debug detected ✳
debug detected ✴
debug detected ❄
debug detected ❇
debug detected ❌
debug detected ❎
debug detected ❓
debug detected ❔
debug detected ❕
debug detected ❗
debug detected ❣
debug detected ❤
debug detected ➕
debug detected ➖
debug detected ➗
debug detected ➡
debug detected ➰
debug detected ➿
debug detected ⤴
debug detected ⤵
debug detected *⃣
debug detected ⬅
debug detected ⬆
debug detected ⬇
debug detected ⬛
debug detected ⬜
debug detected ⭐
debug detected ⭕
debug detected 0⃣
debug detected 〰
debug detected 〽
debug detected 1⃣
debug detected 2⃣
debug detected ㊗
debug detected ㊙
debug detected 3⃣
debug detected 4⃣
debug detected 5⃣
debug detected 6⃣
debug detected 7⃣
debug detected 8⃣
debug detected 9⃣
debug detected ©
debug detected ®
debug detected
info total: 2477
info saved at index.js
$ git diff index.js
warning: LF will be replaced by CRLF in index.js.
The file will have its original line endings in your working directory.
@bestmike007 you're right, thanks for that, need to be removed, it's unnecessary 😄 .
What about this: https://github.com/Kikobeats/emojis-list/blob/master/update.js#L29
| gharchive/pull-request | 2016-10-03T08:25:26 | 2025-04-01T04:32:42.004703 | {
"authors": [
"Kikobeats",
"bestmike007"
],
"repo": "Kikobeats/emojis-list",
"url": "https://github.com/Kikobeats/emojis-list/pull/11",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
217191810 | Yavorsky chrome to electron
Add a chromium-to-electron set of functions, continuing on from #6.
cc @yavorsky
@Kilian awesome, thanks!
| gharchive/pull-request | 2017-03-27T09:49:41 | 2025-04-01T04:32:42.020038 | {
"authors": [
"Kilian",
"yavorsky"
],
"repo": "Kilian/electron-to-chromium",
"url": "https://github.com/Kilian/electron-to-chromium/pull/8",
"license": "ISC",
"license_type": "permissive",
"license_source": "github-api"
} |
493029537 | Hot Reloading
🔥 Get the hot reloader working 🔥
Its implemented but not working so far 👎
due to Monday morning
Hot Reloading -> Done!
| gharchive/issue | 2019-09-12T21:05:28 | 2025-04-01T04:32:42.021200 | {
"authors": [
"Natia94"
],
"repo": "KillTheMessenger/Interspect",
"url": "https://github.com/KillTheMessenger/Interspect/issues/13",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
243287787 | Contribute to hnpwa and todomvc
Contribute to hnpwa.com and todomvc.com maybe? Most of JS View library listed there. Making moon more well known by community.
Yes, I've been thinking about making an hnpwa, and I'm currently working on a PR for todomvc, it is already available, just not official.
| gharchive/issue | 2017-07-17T03:02:36 | 2025-04-01T04:32:42.045463 | {
"authors": [
"KingPixil",
"muhajirframe"
],
"repo": "KingPixil/moon",
"url": "https://github.com/KingPixil/moon/issues/86",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
2131922463 | ✨ Add the ability to load sounds from streams
Description:
To allow this pull request to be merged, please make sure that the following items of this pull request are complete.
This pull request closes #158
✅The pull request head branch must be a feature branch with the syntax 'feature/-sync-testing'.
✅The pull request base branch must be a 'main' or 'preview' branch..
✅The pull request head branch contains a valid issue number.
✅The pull request title matches the linked issue title exactly.
✅The pull request assignees match the assignees of the issue.
✅The pull request labels match the labels of the issue.
✅The pull request organizational projects match the organizational projects of the issue.
✅The pull requests milestone matches the milestone of the issue.
Additional Info:
Pull requests are automatically synced with the associated issue upon creation by one of the KinsonDigital workflow bots.
The associated issue is the issue number that is embedded in the pull request head branch.
The list above will be automatically updated as the pull request's various settings match or do not match the associated issue.
To manually sync the pull request to the issue, create a comment with the [run-sync] command.
Note You must be an admin member of the organization to use this command.
[x] Sync with the issue. Use this to enable or disable this pull request from syncing with its associated issue.
[!Note]
Fixed the following https://github.com/KinsonDigital/CASL/labels/🐛bug 's
Fixed a bug where if the sound has never been played or was stopped in addition to the play speed being set to a value other than the default value, the sound would not retain its original play speed when switching audio devices.
[!Caution]
Introduced the following https://github.com/KinsonDigital/CASL/labels/🧨breaking changes
Refactored the name of the SoundDataException to AudioDataException
[!Note]
Add the following features
Added the ability for the Sound class, (now named Audio)` to stream it's audio from the audio source.
Added a new property to the Sound class, (now named Audio)namedBufferType` to see what type of buffer the audio was set to upon creation.
| gharchive/pull-request | 2024-02-13T09:57:13 | 2025-04-01T04:32:42.057499 | {
"authors": [
"CalvinWilkinson"
],
"repo": "KinsonDigital/CASL",
"url": "https://github.com/KinsonDigital/CASL/pull/338",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2253222808 | [REQUEST] Immersive Weathering support
https://modrinth.com/mod/immersive-weathering
This mod adds stages of rusting (exposed, weathered and rusted) to iron doors, as well as waxed variants. Please add short and tall variants of these doors to this mod!
Mod support implemented as of Dramatic Doors version 3.2.2 for MC 1.20.1! :)
| gharchive/issue | 2024-04-19T14:58:00 | 2025-04-01T04:32:42.082700 | {
"authors": [
"Abbie5",
"Kitteh6660"
],
"repo": "Kitteh6660/DramaticDoors",
"url": "https://github.com/Kitteh6660/DramaticDoors/issues/89",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
947110762 | Live reloading changes from a common directory
Just stumbled across this and I love the setup, thanks! I've used the create-app for react/ts/vite. I've added a src/common folder for shared code between main and renderer, but I've found that making changes to code in src/common doesn't trigger a reload of the main process.
I took a look through esbuilder package and I believe it may be these lines here that are only using src property from the config to determine a directory to watch. If I've understood correctly, I think we'd need another property to specify one or more "common" directories to additionally watch for.
Hey,
Thanks you for your comment!
I use electron-esbuild myself for a personal project (papyrus-compiler-app in my profile).
I have a common folder too. But I do not have this problem. Have you any repo with the same problem?
Here's what I've got: https://github.com/lewisandrew/Vite-Electron-Test
In which side the live reload does not refresh? In renderer?
If yes, this could be the vite server configuration that do not listen to common
It's working with renderer. It doesn't work with the main process. Starting dev you'll see the console log "hello main stuff..." that comes from the common function executed in main.ts. Editing the console log message and saving the file doesn't trigger a reload of the main process (the updated console log message doesn't get logged), but saving in the main.ts file does.
I think I found the problem. I tested with common/logger.
In your main.ts, if you change import logger from '@/common/logger.js' by import logger from '../common/logger.js' (note the tsconfig paths removed).
esbuild does not seem to know that the file as changed cause of the tsconfig paths. Maybe esbuild needs a plugin?
I think this is not related to electron-esbuild.
Thanks for looking into this. I also see it working if I use relative paths. I tried fooling around with an esbuild plugin that onResolve sets the new path correctly, however unfortunately that didn't work. It seems that whatever is causing it to work with relative paths is being determined separately (or maybe before) from how esbuild resolves it.
https://github.com/lewisandrew/Vite-Electron-Test/commit/a7807331b3613ceefbacf7a0c55b1cb56b01f154
Any ideas on what other configuration I may need to change?
The problem comes from the tool that looks for your sources dependencies (local files and node_modules).
It does not resolve paths aliases. I'm working on it. I'll maybe add a watchDirectories config options per environment
| gharchive/issue | 2021-07-18T20:21:26 | 2025-04-01T04:32:42.107772 | {
"authors": [
"Kiyozz",
"lewisandrew"
],
"repo": "Kiyozz/electron-esbuild",
"url": "https://github.com/Kiyozz/electron-esbuild/issues/26",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2247577287 | bad results
Hi, there might be some issues when translating tiny molecules. However, the model has almost 100% accuracy when translating molecules with SMILES representations 30-60 tokens long
Could you please provide a tutorial on how to fine-tune or train the model?
| gharchive/issue | 2024-04-17T07:25:44 | 2025-04-01T04:32:42.145155 | {
"authors": [
"BioMikeUkr",
"SnailWhb"
],
"repo": "Knowledgator/chemical-converters",
"url": "https://github.com/Knowledgator/chemical-converters/issues/2",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2316203975 | unzip: not found
Docker container for this build doesn't have unzip installed, so it fails when it tries to decompress the duckdb binary.
#17 doesn't work because the jenkinsuser isn't a sudoer.
Options:
Include it in the Docker container
Use gunzip instead since this is a single file archive
| gharchive/issue | 2024-05-24T20:23:11 | 2025-04-01T04:32:42.147129 | {
"authors": [
"caufieldjh"
],
"repo": "Knowledge-Graph-Hub/automate-pheno-comparisons",
"url": "https://github.com/Knowledge-Graph-Hub/automate-pheno-comparisons/issues/16",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
381948226 | [Vima Smart Lock] Key error events are not being converted
Current behavior
The xiaomi_lock_report converter is not currently converting Vima Smart Lock's key error events.
Expected behavior
Key error events should be converted and returned properly so that they can be consumed by upper layers (e.g.: in zigbee2mqtt).
Context
The key error event is supposed to be sent by this lock upon three different situations:
The key was not properly inserted or someone is trying to lock pick the cylinder.
The inserted key is not registered.
The inserted key is registered but disabled from the Mi Home app.
I've been doing some additional research on what my lock sends on each of the aforementioned cases:
The key was not properly inserted or someone is trying to lock pick the cylinder
I see no messages at all :open_mouth:
The inserted key is not registered
Message is 0x1101ffffffffffff, so:
state: '11' (17)
action: '01' (1)
keynum: 'ff' (255 / null)
This will of course not pass the current action assertion, which may be causing this issue in the first place:
https://github.com/Koenkk/zigbee-shepherd-converters/blob/ffb96bb165d6467ff49ab3d473242593951762fd/converters/fromZigbee.js#L640
The inserted key is registered but disabled from the Mi Home app
Haven't had the chance to try this yet, but I can speculate one of:
Coherent to current converter implementation, using action 07, like 0x1107ffffffffffff.
Similar to current converter implementation, but with the key number in place, like 0x110701ffffffffff.
Same as inserted key is not registered, but with the key number in place, like 0x110101ffffffffff.
If it actually matches case 2 or 3, there could be some additional issue in here: key numbers are not being taken into consideration for key error events.
In the other hand, case 1 is true, then it means that the lock is not reporting the key number at all under this situation, so there's nothing we can do. But honestly I don't think that's the case, because that's not coherent with the logs in Mi Home app, which afaik do actually give the key number for failed unlocks with disabled keys.
So, IMHO, xiaomi_lock_report should read:
if (state == 11) {
if (action == 1) {
// unknown key
return {keyerror: true};
}
if (action == 3) {
// explicitly disabled key (e.g.: reported lost)
return {keyerror: true, inserted: keynum}
}
}
I will make a PR. Seeing that @kirovilya originally added support for this lock, I suppose he should be able to review it and check if it works for him.
| gharchive/issue | 2018-11-18T10:38:49 | 2025-04-01T04:32:42.207914 | {
"authors": [
"aesedepece"
],
"repo": "Koenkk/zigbee-shepherd-converters",
"url": "https://github.com/Koenkk/zigbee-shepherd-converters/issues/135",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1160411059 | Provide method similiar to detect method that accepts e.g. bytes (List or Uint8List) as argument
I have to preprocess my images before doing interference. In order to apply transformations I read the image into an Image object with the flutter image plugin. I would really like to use ncnn_yolox_flutter, but if I wanted to I need to write my transformed image to the filesystem first so that ncnn_yolox_flutter can read it again for interference which is redundant.
Providing a detect method that accepts the bytes of a file would solve most of the problems, because I can encode the Image object as png which results in a List or Uint8List. Another approach would be to accept 3d arrays which contain the rgb values of the image, because then we can safe even more time, because we don't need to encode the raw data to a image file type first.
The flutter image plugin stores the data of the image as follows:
/// Pixels are encoded into 4-byte Uint32 integers in #AABBGGRR channel order.
final Uint32List data;
So providing a method that accepts something similar or something that does not need to much conversion would be appreciated a lot!
@leeflix
Thanks for the great request!
I have the same idea and am in the process of implementing a new detect method.
I hope to have an update in a few days.
@leeflix
Added Uint8List support in v0.1.0
The example app uses https://pub.dev/packages/image, which may be helpful.
Awesome, thank you!
| gharchive/issue | 2022-03-05T17:56:59 | 2025-04-01T04:32:42.233393 | {
"authors": [
"KoheiKanagu",
"leeflix"
],
"repo": "KoheiKanagu/ncnn_yolox_flutter",
"url": "https://github.com/KoheiKanagu/ncnn_yolox_flutter/issues/11",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
2355390513 | fix debug usage error
This PR addresses an issue occurring in debug mode when setting the threading start method using set_start_method fails. Previously, if an exception was raised during this process, the error handling code would incorrectly format the exception message, leading to a secondary exception of type TypeError with the message "not all arguments converted during string formatting."
Oops. Thank you!
| gharchive/pull-request | 2024-06-16T02:44:57 | 2025-04-01T04:32:42.241628 | {
"authors": [
"KoljaB",
"pia-ai"
],
"repo": "KoljaB/RealtimeSTT",
"url": "https://github.com/KoljaB/RealtimeSTT/pull/70",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
516659843 | Shyrma concat
provide deconv2d/3d (ff and bp) based on corresponding mkl dnn api
add possibility to pass axis as last input array in concat op
corrcect sumation in bias_add_bp op for NHWC case
thank for reasonable comments,
corrrected !
| gharchive/pull-request | 2019-11-02T17:10:34 | 2025-04-01T04:32:42.290689 | {
"authors": [
"shyrma"
],
"repo": "KonduitAI/deeplearning4j",
"url": "https://github.com/KonduitAI/deeplearning4j/pull/24",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
610988460 | Portal Application Registration Plugin Docs
Documentation for app registration plugin released as beta feature in 1.5.x.
https://konghq.atlassian.net/browse/DOCS-1013
Direct link to topic in progress:
https://deploy-preview-2005--kongdocs.netlify.app/hub/kong-inc/application-registration/
@Jlawlzz and @aaronhmiller what else do you think should go into the app registration plugin docs? Please review this draft PR at your earliest convenience. Thank you for your assistance.
This part confuses me I don't think we should be talking about declarative config here because this plugin does not support db-less.
This part confuses me I don't think we should be talking about declarative config here because this plugin does not support db-less.
Yes it confuses me as well and customers too but this is embedded in the plugin template, which seems too inflexible. I currently do not have control over the generated sections unfortunately. We really need to revisit these template because many of the default enable this plugin generated code examples create schema violations.
Yes it confuses me as well and customers too but this is embedded in the plugin template, which seems too inflexible. I currently do not have control over the generated sections unfortunately. We really need to revisit these template because many of the default enable this plugin generated code examples create schema violations.
I've got a list of plugin template improvements that we can easily make - this is one of them. Will make a ticket to keep track.
I've reviewed and the additional discussion and examples help a lot.
I've reviewed and the additional discussion and examples help a lot.
Thank you @aaronhmiller!
| gharchive/pull-request | 2020-05-01T21:58:45 | 2025-04-01T04:32:42.296091 | {
"authors": [
"HenriPro",
"aaronhmiller",
"lena-larionova",
"tlblessing"
],
"repo": "Kong/docs.konghq.com",
"url": "https://github.com/Kong/docs.konghq.com/pull/2005",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1523188103 | [DOCU-2838] Konnect System Accounts (GA)
Summary
Write docs for the following:
Make clear the difference between system account and a normal user
System account and PAT workflow entirely via API
Reason
DOCU-2838
Testing
/konnect/org-management/system-accounts/
Note: This ticket was moved to a different month, so per Amy: "Earliest I’d want to come back to [this] is second half of Feb (ie after 3.2 release)"
Closing this PR, it should be reopened when the work on this project resumes.
@lena-larionova Hi! When you have the time, could you review this? Thanks!
| gharchive/pull-request | 2023-01-06T21:24:08 | 2025-04-01T04:32:42.299405 | {
"authors": [
"Guaris",
"cloudjumpercat"
],
"repo": "Kong/docs.konghq.com",
"url": "https://github.com/Kong/docs.konghq.com/pull/4999",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1612973110 | Add Konnect signup CTA
Description
Jira ticket
Add Konnect Signup CTA to Docs and remove A/B test for "Personalized Demo".
Testing instructions
Netlify link:
Checklist
[ ] Review label added
[ ] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)
@acgoldsmith I added the change and it looks good, this is ready to be merged!
| gharchive/pull-request | 2023-03-07T08:38:16 | 2025-04-01T04:32:42.302261 | {
"authors": [
"fabianrbz"
],
"repo": "Kong/docs.konghq.com",
"url": "https://github.com/Kong/docs.konghq.com/pull/5260",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
841273733 | Add DevRole/RBAC pagination and ListAll; require the Portal for Portal tests
Carried on from #29. Includes the original change from that and changes to require the Portal for Portal feature tests, as it is not set up by default, and further requires admin API requests to make it available on a workspace.
Removes the RBAC requirement from Portal tests, since they don't actually require RBAC. The original merge from #26 passed CI once in main, which suggests there's maybe something going wrong with CI RBAC setup--while my local test environment didn't have RBAC on and the tests did not run at all, it looks like RBAC-only tests should run in CI, so the Portal tests should have failed earlier.
See https://github.com/Kong/go-kong/pull/29#issuecomment-807396216 for a bit more background.
The actual implementation of the List() changes and new ListAll() looks fine to me, as do the tests aside from the need to enable the Portal.
| gharchive/pull-request | 2021-03-25T20:14:59 | 2025-04-01T04:32:42.304755 | {
"authors": [
"rainest"
],
"repo": "Kong/go-kong",
"url": "https://github.com/Kong/go-kong/pull/30",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1414572988 | Cursor loss of focus when typing/edit JSON in Manage Environment menu
Expected Behavior
Cursor should not lose focus while typing
Actual Behavior
Cursor loss of focus when typing
Reproduction Steps
Go to menu Manage Environment
Create new environment
In text box, type a character
Wait for one second
Cursor will loss focus
Is there an existing issue for this?
[X] I have searched the issue tracker for this problem.
Additional Information
Version: Insomnia 2022.6.0
Build date: 9/27/2022
OS: Darwin x64 19.6.0
Electron: 19.0.3
Node: 16.14.2
V8: 10.2.154.4-electron.0
Architecture: x64
Insomnia Version
2022.6.0
What operating system are you using?
macOS
Operating System Version
macOS Catalina 10.15.7
Installation method
Insomnia
Last Known Working Insomnia version
No response
Hi @erlangparasu thanks for reporting this, this is a known issue, has been reported already in #5234.
We'll be fixing this as soon as possible in one of our upcoming beta releases.
| gharchive/issue | 2022-10-19T08:54:54 | 2025-04-01T04:32:42.310105 | {
"authors": [
"erlangparasu",
"filfreire"
],
"repo": "Kong/insomnia",
"url": "https://github.com/Kong/insomnia/issues/5303",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1918711434 | Issue when import from old version(unknown) exported insomnia json file to latest version 8.x.x
Expected Behavior
Import successful
Actual Behavior
Met this error:
Error: Project not found. at a2 (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-334620de.js:17:108051) at Module.l (file:///Applications/Insomnia.app/Contents/Resources/app.asar/import-9dfc1356.js:1:906) at async d8 (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-334620de.js:31:3691) at async Be (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-334620de.js:30:18468)
Reproduction Steps
No response
Is there an existing issue for this?
[X] I have searched the issue tracker for this problem.
Additional Information
No response
Insomnia Version
8.0.0
What operating system are you using?
macOS
Operating System Version
MacOS 13.5
Installation method
Homebrew
Last Known Working Insomnia version
Previous version of 8.0.0
Latest version 8.1.0 is working normally
| gharchive/issue | 2023-09-29T07:05:01 | 2025-04-01T04:32:42.314482 | {
"authors": [
"ittrongduc"
],
"repo": "Kong/insomnia",
"url": "https://github.com/Kong/insomnia/issues/6602",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1616928733 | KONG_DOCKER_VERSION not match kong version
https://github.com/Kong/kong/blob/c33859a83ea402e0b86460f8ea89f3997cc76b28/.requirements#L16
kong 3.2.1 is released in this repo,which does not match with the KONG_DOCKER_VERSION in .requirements?Can someone tell me is version 3.2.1 is not production-ready now?
besides,the latest docker image version is 3.1.1 in docker hub.
looks like 3.2.1 is WIP, see: https://github.com/Kong/docker-kong/pull/631
looks like 3.2.1 of docker-kong is WIP, see: Kong/docker-kong#631
yes,I think so.I have a comment on it as well.
3.2.2 has been released on Docker Hub now.
| gharchive/issue | 2023-03-09T10:43:22 | 2025-04-01T04:32:42.317495 | {
"authors": [
"chronolaw",
"sabertobihwy",
"zffocussss"
],
"repo": "Kong/kong",
"url": "https://github.com/Kong/kong/issues/10461",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2394882101 | feat(*): port several PDK and shared llm module from ai-proxy-advanced feature
Summary
This PR adds several PDK methods to allow ai-proxy-advanced plugin to do customized load balancing and failover.
It also moves the ai-proxy handler to a shared module so that both ai-proxy{,-advanced} plugins can reuse same codebase.
https://github.com/Kong/kong-ee/pull/9562
Checklist
[x] The Pull Request has tests
[na] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[na] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE
Issue reference
AG-12
Reviewers: please review https://github.com/Kong/kong-ee/pull/9562 first for a whole picture, I will then address comments there and port here.
ce-ee cherrypick not needed, it's part of the ai-proxy-advanced PR and is merged
| gharchive/pull-request | 2024-07-08T07:36:28 | 2025-04-01T04:32:42.321678 | {
"authors": [
"fffonion"
],
"repo": "Kong/kong",
"url": "https://github.com/Kong/kong/pull/13347",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1793230878 | [Pendulum] [USDT DOT] Add support for USDT, DOT on Pendulum
If you want to integrate an asset (fungible token/ NFT), you would need to provide
DOT
Origin: Polkadot
Is it available on other blockchains? yes
Metadata of the asset (symbol, decimals, smart contract address, on-chain metadata like assetId,...): XCM currency id: 0
Logo of the token
Is your asset transferable? yes
USDT
Origin: Statemint
Is it available on other blockchains? yes
Metadata of the asset (symbol, decimals, smart contract address, on-chain metadata like assetId,...): XCM currency id: 1
Logo of the token
Is your asset transferable? yes
Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-pr-1631-build-1.1.1-2023-07-12T05-14-36UTC.zip
Validation passed for cases:
Show balance
Send token (Approve step)
| gharchive/issue | 2023-07-07T10:08:05 | 2025-04-01T04:32:42.327934 | {
"authors": [
"NamPhamc99",
"Sokol142196"
],
"repo": "Koniverse/SubWallet-ChainList",
"url": "https://github.com/Koniverse/SubWallet-ChainList/issues/82",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2314746895 | [Issue-3108] Extension - Add highlight button Export multi account on Select account screen
Related issue: #3108
🚀 Deployed on https://pr-3113--sw-web-runner.netlify.app
| gharchive/pull-request | 2024-05-24T08:23:57 | 2025-04-01T04:32:42.329252 | {
"authors": [
"dungnguyen-art",
"saltict"
],
"repo": "Koniverse/SubWallet-Extension",
"url": "https://github.com/Koniverse/SubWallet-Extension/pull/3113",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2220247843 | Configura e adiciona CI de testes em PRs para a main
Adiciona configuração do Github Actions para executar os testes do site quando um novo PR para branch main é criado.
Exemplo da execução do Gihub Actions: https://github.com/diegosurita/visao-libertaria-site/actions/runs/8521760198
@KoreaComK o que você acha deste PR?
Vi que no site não tem nada relacionado a testes.
Não sei até que ponto os testes poderiam ajudar, a não ser que você pudesse escrevê-los, pois infelizmente não tenho o tempo necessário para conseguir montá-los. Se tiver tudo bem para você, eu faço o merge.
Os testes ajudariam pra dar mais segurança no momento for feito alguma alteração e é útil para validar se a funcionalidade está funcionando da maneira que deveria.
Posso fazer os testes sim, sem problemas.
| gharchive/pull-request | 2024-04-02T11:18:56 | 2025-04-01T04:32:42.334462 | {
"authors": [
"KoreaComK",
"diegosurita"
],
"repo": "KoreaComK/visao-libertaria-site",
"url": "https://github.com/KoreaComK/visao-libertaria-site/pull/119",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
181561293 | Supplies feature
I've Updated the Supplies Model, and the controller and view accordingly.
Derek Larson
fixes #1
fixes #2
| gharchive/pull-request | 2016-10-07T01:08:15 | 2025-04-01T04:32:42.335679 | {
"authors": [
"Derek03"
],
"repo": "KoreanDog/JappadogSecrets",
"url": "https://github.com/KoreanDog/JappadogSecrets/pull/13",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
2157953937 | [API] Skintight geckolib armor doesn't render right during animations
Describe the bug
When animating the player with a custom skintight geckolib armor model, the armor is rendered in the wrong place.
To Reproduce
Steps to reproduce the behavior:
Make a skintight geckolib armor model
Make a player animation
Perform animation in-game
See error
Expected behavior
The model stays skintight
Screenshots
Vanilla iron armor:
Custom armor:
Setup config (minecraft, modloader, libraries):
Minecraft version: 1.20.4
Mod loader: All
PlayerAnimator Library version 1.0.2-rc1+1.20
Other mods (If you use other mods, please specify! it might be an incompatibility):
Geckolib
model.zip
Here's the model I use
The pivot of your custom leggings is incorrect. Please match that to the vanilla model
Fixing the pivots of the groups and subgroups fixed it, thanks
| gharchive/issue | 2024-02-28T02:30:26 | 2025-04-01T04:32:42.369544 | {
"authors": [
"KosmX",
"thomasglasser"
],
"repo": "KosmX/minecraftPlayerAnimator",
"url": "https://github.com/KosmX/minecraftPlayerAnimator/issues/82",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1936718016 | When I want to print out the html file, I can only display the first page
Describe the bug
When I want to print out the exported html file, I can only display the first page
And I noticed that the Sliding block in the exported html file is different from other pages
Operating System
macOs Sonoma 14.0
To Reproduce
Steps to reproduce the behavior:
open the html file in browser
Click on print (command + p)
Screenshots
https://res.cloudinary.com/ds2agvour/image/upload/v1696994018/cak3jbp9lew0wnvoho7g.png
IMPORTANT: Error Log
Print in chrome so there is no log for Webpage-export
Thanks I am aware of this and it will be fixed in the next update
| gharchive/issue | 2023-10-11T03:16:29 | 2025-04-01T04:32:42.372721 | {
"authors": [
"KosmosisDire",
"veryqun"
],
"repo": "KosmosisDire/obsidian-webpage-export",
"url": "https://github.com/KosmosisDire/obsidian-webpage-export/issues/258",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1659980651 | Export current file + related notes (outgoing links)
Hi,
Here is a new idea. I is related to exporting multiple file like suggested here but is a different idea.
Describe the solution you'd like
I would like to be able to export on file with the notes related to the outoing links.
So I can share my note with someone who can then navigate on one level. For example my note could contain a concept (let's say the "halo effect" that is defined in another note.
Hmm I'm wondering if it is the same idea or not that this one.
It could be really cool. Thanks for this plugin. 🙏
Yes this has already been suggested and is planned. Thanks!
I will close this since it is a duplicate of #38
| gharchive/issue | 2023-04-09T19:37:47 | 2025-04-01T04:32:42.375318 | {
"authors": [
"KosmosisDire",
"Oskiator"
],
"repo": "KosmosisDire/obsidian-webpage-export",
"url": "https://github.com/KosmosisDire/obsidian-webpage-export/issues/59",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2554480656 | [Feature] Customizable Player/Target/Focus Colour options
Describe the feature
Currently the frames copies over from the Cell addon and colours it that way, but it would be great to have it separated!
Describe the implementation
An extra option under Colours perhaps would suffice.
Just for scoping sake, are you after individual options for each frame, or simply separate global options for the CUF frames?
Heya
Practically just as the picture depicts, where you can add an options to show absorbs alongside shields as an overlay bar.
And then add to that a text amount as well.
This picture is from my old elvui frames.
[cid:bb497ea2-2763-4507-99b1-d984ba0d20f1]
Fra: Vollmer @.>
Sendt: 30. september 2024 15:56
Til: Krealle/Cell_UnitFrames @.>
Cc: Neyebae @.>; Author @.>
Emne: Re: [Krealle/Cell_UnitFrames] [Feature] Customizable Player/Target/Focus Colour options (Issue #92)
Just for scoping sake, are you after individual options for each frame, or simply separate global options for the CUF frames?
—
Reply to this email directly, view it on GitHubhttps://github.com/Krealle/Cell_UnitFrames/issues/92#issuecomment-2383270384, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLWAHRZXKPFMITKXS7CUZKTZZFKBFAVCNFSM6AAAAABPA5BCBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBTGI3TAMZYGQ.
You are receiving this because you authored the thread.Message ID: @.***>
I don't see a picture.
Not sure why that didn't work in the first place.
But here it is!
Oh I think you you are referring to #95.
My question was about the frame colors :)
So sorry, it was what was on my mind at that moment :D
I personally prefer having separate colours on Raid frames to Player frames.
An example would be I use Class Colours for raid frames to easier distinct raiders for call outs.
Player frames I like them as in the picture above.
Makes it much easier peripherally to gauge my HP without looking.
| gharchive/issue | 2024-09-28T20:17:31 | 2025-04-01T04:32:42.462650 | {
"authors": [
"Krealle",
"Neyebae"
],
"repo": "Krealle/Cell_UnitFrames",
"url": "https://github.com/Krealle/Cell_UnitFrames/issues/92",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2608353873 | FormActionType - Confirmation does not work with Closure
Hey everyone !
The docs say that confirmation can be set to bool, array or callable.
But when i pass a Closure, i get an error rendering the datatable. It works for href etc. in the ButtonType.
->addRowAction('delete', FormActionType::class, [
'label' => 'Delete',
'button_attr' => [
'class' => 'btn btn-danger btn-sm',
],
'confirmation' => function(Entity $entity): array {
return [
'title' => 'Delete',
'message' => sprintf(
'Are you sure you want to delete Channel: [%s]?',
$entity->getChannel()->getName()
),
];
},
Is this a bug, wrong doc or am I doing something wrong ?
Thanks in advance !
Hey @jc-beyer-tqgg, thanks for the report. There was a bug and I just pushed a fix to version 0.24.3.
Please note that options allowed in the confirmation array (including array returned from callable) are:
translation_domain
label_title (you'll probably want to use this option instead of title)
label_description (you'll probably want to use this option instead of message)
label_confirm
label_cancel
type
@Kreyu Thanks for the super fast fix ! Really appriciate your work here
| gharchive/issue | 2024-10-23T12:04:15 | 2025-04-01T04:32:42.467105 | {
"authors": [
"Kreyu",
"jc-beyer-tqgg"
],
"repo": "Kreyu/data-table-bundle",
"url": "https://github.com/Kreyu/data-table-bundle/issues/139",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2551714503 | 🛑 💬 Sebastian Zitzmann is down
In 4d2a4b2, 💬 Sebastian Zitzmann (https://sebastian-zitzmann.de) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 💬 Sebastian Zitzmann is back up in c6e4353 after 1 hour, 24 minutes.
| gharchive/issue | 2024-09-27T00:00:11 | 2025-04-01T04:32:42.469647 | {
"authors": [
"KrisKodira"
],
"repo": "KrisKodira/uptime-monitor",
"url": "https://github.com/KrisKodira/uptime-monitor/issues/1395",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
224333202 | Installation Hangup
I've tried several times to install the elm extension with no success due to a hangup each time. Here is a Stack Overflow question representing what happens.
We don't control installation process - that's something handled by core VSCode editor.
| gharchive/issue | 2017-04-26T03:26:51 | 2025-04-01T04:32:42.583174 | {
"authors": [
"Krzysztof-Cieslak",
"afreymiller"
],
"repo": "Krzysztof-Cieslak/vscode-elm",
"url": "https://github.com/Krzysztof-Cieslak/vscode-elm/issues/111",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
664014798 | 可以实现文档流布局吗？
动态生成海报时，有多个 文字段落和图片 混排 且 每个文字段落里的文字长度无法固定，导致段落的高度不能定高。
请问用 Painter 可以自动撑开吗？可以实现类似html的文档流布局吗？
可以，文字限制宽度，图片可以动态获得文字高度来布局
同问。 有解决方案吗。 在仓库中没找到列子
| gharchive/issue | 2020-07-22T20:01:48 | 2025-04-01T04:32:42.585487 | {
"authors": [
"CPPAlien",
"Li-shiwei",
"zjydipingxian"
],
"repo": "Kujiale-Mobile/Painter",
"url": "https://github.com/Kujiale-Mobile/Painter/issues/267",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1425051049 | Dijkstra's Algorithm Completed
Completed in Python, Java, C++ and C
Closes #31
| gharchive/pull-request | 2022-10-27T05:23:02 | 2025-04-01T04:32:42.586370 | {
"authors": [
"Aniketgupta03",
"Kumar-laxmi"
],
"repo": "Kumar-laxmi/Algorithms",
"url": "https://github.com/Kumar-laxmi/Algorithms/pull/32",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
133269852 | fixed a bug where enable neovim would always be set to true
caught a bug :)
Oops!
Thanks!👍
| gharchive/pull-request | 2016-02-12T15:32:23 | 2025-04-01T04:32:42.590569 | {
"authors": [
"Kuniwak",
"RianFuro"
],
"repo": "Kuniwak/vint",
"url": "https://github.com/Kuniwak/vint/pull/161",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1109519290 | update optimistic kovan shorts subgraph api
Description
Just updating the subgraph API for ovm kovan shorts
EDIT:
This should fix: https://github.com/Kwenta/kwenta/issues/252
can you merge into dev first since not a hotfix
closed to fix branch name and prevent future confusion (mainnet kovan shorts NOT ovm kovan)
| gharchive/pull-request | 2022-01-20T16:33:20 | 2025-04-01T04:32:42.629245 | {
"authors": [
"JChiaramonte7",
"kmeraz"
],
"repo": "Kwenta/kwenta",
"url": "https://github.com/Kwenta/kwenta/pull/275",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
528777936 | fix fetch / deploy scripts for next network upgrade
script for fetch data should be added to web3Deployment folder.
fetched data should be printed out as json that will be stand alone json.
deploy Network Script should be re arranged and seperated to stages:
input files for deploy should be seperated to deployed contracts in first stage, permissions and misc data. and fetched data from above.
contract deployments should run separate stage. write output to json with new addresses.
each of the steps should be a separate:
list reserves
list tokens per reserve
list fee sharing wallets
transfer admins.
for each step. first function should verify the deploying address has required permissions on the contract it is interacting with.
Please open a folder in web3Deployment with all relevant stuff for network updgrade.
Including helper contract for checking if reserve points on correct network
done
| gharchive/issue | 2019-11-26T14:55:01 | 2025-04-01T04:32:42.633004 | {
"authors": [
"ilanDoron"
],
"repo": "KyberNetwork/smart-contracts",
"url": "https://github.com/KyberNetwork/smart-contracts/issues/507",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
771671125 | Use Keychain to store user access tokens securely
At the moment, user tokens are stored in the user's default database. While this is easy, it's not as secure as storing them in Keychain to meet expected requirements. This should be implemented before production reaches.
Documentation: https://developer.apple.com/documentation/security/keychain_services/keychain_items/using_the_keychain_to_manage_user_secrets
Merged as of fa1930f.
| gharchive/issue | 2020-12-20T19:21:03 | 2025-04-01T04:32:42.647901 | {
"authors": [
"KyleErhabor"
],
"repo": "KyleErhabor/clematis",
"url": "https://github.com/KyleErhabor/clematis/issues/4",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
829308457 | SSO Login fails due wrong params order
Description: The SSO Login on rpatchur makes the client crash, and it needs to be fixed and tested in newer clients to confirm if this still happens.
Client Version: 2015-09-16aRagexe
What rpatchur does: "-1rag1" "-t:password" "username" (results on a client crash)
What rpatchur should do -t:password username server -1rag1 (it works for me)
Additional Info: Where i found the correct param order
And is important to know that the commas are sent to the emulator too. So it fails because the server receives "username" and tries to find an account including the commas, tested on a 2018 hercules emulator.
Thanks for the report! I see @vstumpf has opened a PR so I'll review it and merge it.
| gharchive/issue | 2021-03-11T16:23:03 | 2025-04-01T04:32:42.657767 | {
"authors": [
"L1nkZ",
"waken22"
],
"repo": "L1nkZ/rpatchur",
"url": "https://github.com/L1nkZ/rpatchur/issues/21",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
637137211 | Fixes intermittent issues with Cypress tests
What
Fixes and workarounds for some intermittent problems with our Cypress tests. It is likely this is caused by the page being updated in the background and then the DOM element Cypress is referring to becoming detached from the document, since it has been replaced. There is a proposal to have Cypress requery in these cases over at https://github.com/cypress-io/cypress/issues/7306.
Why
So that we can have better confidence in our tests, and do not get into the habit of just re-running them when there is a failure.
Anything else?
We should follow progress of the linked GitHub issue and look to remove these workarounds once there is a better solution available.
Let's give it a go!
| gharchive/pull-request | 2020-06-11T15:55:17 | 2025-04-01T04:32:42.682308 | {
"authors": [
"mmmmillar",
"t-davies"
],
"repo": "LBHackney-IT/housing-needs-shared-plan",
"url": "https://github.com/LBHackney-IT/housing-needs-shared-plan/pull/68",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
737187751 | revise or retire original technical docs
documentation at https://ld4p.github.io/sinopia/ is out of date. either
remove, or
add text to say which parts are no longer accurate, or
revise so the docs reflect how Sinopia works now
@michelleif None of this is right or likely to be helpful. Can I remove?
please do
I turned off publication from GH pages. None of the content has been deleted.
Turns out this was also serving our help text, so turned back on.
add a note at top that these docs are out of date? except for the help? or move everything except https://ld4p.github.io/sinopia/help_and_resources/menu.html to a different folder so it doesn't get exposed anywhere?
I slimmed the page down to remove extraneous information.
| gharchive/issue | 2020-11-05T19:00:44 | 2025-04-01T04:32:42.700076 | {
"authors": [
"justinlittman",
"michelleif"
],
"repo": "LD4P/sinopia_editor",
"url": "https://github.com/LD4P/sinopia_editor/issues/2710",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2419712742 | 🛑 [Email] Fastmail (@rongyi.xyz) inbound is down
In 54b95e0, [Email] Fastmail (@rongyi.xyz) inbound (in1-smtp.messagingengine.com) was down:
HTTP code: 0
Response time: 0 ms
Resolved: [Email] Fastmail (@rongyi.xyz) inbound is back up in 051d9b1 after 6 minutes.
| gharchive/issue | 2024-07-19T19:41:20 | 2025-04-01T04:32:42.706194 | {
"authors": [
"LER0ever"
],
"repo": "LER0ever/Status",
"url": "https://github.com/LER0ever/Status/issues/235",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2720406546 | Update katex-header.html
PR updates katex-header.html file to be the same across all repos. Some of them were broken and caused double header menu displayed on docs.rs. I update all repos regardless of whether the katex header was broken, to sync all repos.
I'll fix CI issues in another PR. They are caused by CI using a new version of Rust compiler
| gharchive/pull-request | 2024-12-05T13:22:22 | 2025-04-01T04:32:42.714216 | {
"authors": [
"survived"
],
"repo": "LFDT-Lockness/cggmp21",
"url": "https://github.com/LFDT-Lockness/cggmp21/pull/121",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
552582773 | WatchDog Interrupt
The Watchdog Timer interrupt is used as the tick timer by freeRTOS but the LGT8F appears to have the WOTON fuse incorrectly set to allow this to happen..
Unfortunately this does not work... no interrupt happens....
I'm back on this issue and see from the LGT8F pdf that this chip has a 4th timer ( 16 bit ) which would allow me to modify freeRTOS to use this tmer as it's tick without bothering any of the "Arduino" functionality....
my problem is I don't seem to find any support for TIMER 3 in your board package...
specificaly how can I do ISR( TIMER3_OVF_vect ) or something equivalent... the LGT documentation seems to only show 1 interrupt vector for TIMER3 but that would be enough
for my purposes....
Any Ideas??
| gharchive/issue | 2020-01-21T01:56:38 | 2025-04-01T04:32:42.718644 | {
"authors": [
"ArduinoShop-ca",
"CanHobby"
],
"repo": "LGTMCU/Larduino_HSP",
"url": "https://github.com/LGTMCU/Larduino_HSP/issues/8",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
247098135 | Error: options.uri is a required argument
https://sentry.internal.kevinlin.info/sentry/linkr-demo/issues/82/
Error: options.uri is a required argument
at request (/:1046:5)
at request[func] (/:1324:5)
at check (/:8099:1)
at checkAuth (/:3517:9)
at componentDidMount (/:3510:9)
...
(8 additional frame(s) were not displayed)
If you're seeing this, please update your browser
| gharchive/issue | 2017-08-01T14:57:25 | 2025-04-01T04:32:42.751640 | {
"authors": [
"LINKIWI"
],
"repo": "LINKIWI/linkr",
"url": "https://github.com/LINKIWI/linkr/issues/12",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1408600550 | V0.7.2 release
patch release to allow 0.7.* series to build on nightly again
Closing -- just intended to use PR to check CI
| gharchive/pull-request | 2022-10-14T00:58:11 | 2025-04-01T04:32:42.756327 | {
"authors": [
"LLFourn"
],
"repo": "LLFourn/secp256kfun",
"url": "https://github.com/LLFourn/secp256kfun/pull/130",
"license": "0BSD",
"license_type": "permissive",
"license_source": "github-api"
} |
207995116 | Check boxes Don't Work
Expected Behavior
They should change from red to blue.
Actual Behavior
It does not and throws a js error:
Blockly.addClass_ is not a function
Steps to Reproduce
Open up playground and click checkbox.
Operating System and Browser
Windows 10 Chrome
Monitors (and the checkboxes that control them) have not yet been implemented. While they shouldn't throw an error, I'm going to backlog this for now.
This is just that we missed a spot when moving to Blockly.utils. It's
fixed in my merge pr.
On Thu, Feb 16, 2017 at 5:35 AM Andrew Sliwinski notifications@github.com
wrote:
Monitors (and the checkboxes that control them) have not yet been
implemented. While they shouldn't throw an error, I'm going to backlog this
for now.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/LLK/scratch-blocks/issues/794#issuecomment-280331584,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANDWfw5DkuyRl7pVM1I8KPMJ1X84eE5Oks5rdFCmgaJpZM4MCghe
.
| gharchive/issue | 2017-02-16T02:29:09 | 2025-04-01T04:32:42.760842 | {
"authors": [
"TheBrokenRail",
"rachel-fenichel",
"thisandagain"
],
"repo": "LLK/scratch-blocks",
"url": "https://github.com/LLK/scratch-blocks/issues/794",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
512655898 | Add power (exponentiation) operator
Proposed Changes
It adds power (exponentiation) operator to Scratch. It now supports an easy way to do exponentiations.
Reason for Changes
Scratch does not support exponentiation. Although there are some ways to "simulate" it, they are very hard to do, especially for young users.
This was also requested a long time ago on Scracth Forum and Scratch Wiki
Test Coverage
I didn't do any new "advanced" tests. I mostly copied things that are used for existing operator blocks to create a new block.
Related PRs
Other PRs that are needed for this implementation are:
LLK/scratch-vm#2296
LLK/scratch-blocks#2007
LLK/scratch-gui#5266
Hi @filips123. Thanks for the suggestion. As per our contributor guidelines, we ask that issues first be filed so that we can discuss contributions like this prior to submitting a PR. We carefully weigh every feature added to the Scratch editor before jumping into the code. Many thanks!
| gharchive/pull-request | 2019-10-25T18:28:11 | 2025-04-01T04:32:42.764237 | {
"authors": [
"filips123",
"thisandagain"
],
"repo": "LLK/scratch-blocks",
"url": "https://github.com/LLK/scratch-blocks/pull/2007",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
447405088 | Handle FindMPI 3.10+
CMake changed all of the output variable names from FindMPI.cmake. This PR handles this and no change is required on the users end. Yay for BLT. For example:
MPI_C_INCLUDE_PATH to MPI_C_INCLUDE_DIRS
MPI_C_COMPILE_FLAGS to MPI_C_COMPILE_OPTIONS
MPI_C_LIBRARIES to MPI_mpi_LIBRARY
On a side note, this exposed that list(REMOVE_DUPLICATES ...) errors on an empty list. So I added blt_list_remove_duplicates() which can.
Looks like cmake-3.11 was not happy:
https://travis-ci.org/LLNL/blt/jobs/536055889
-- CMake Version: 3.11.4
...
-- [mpi property] 'mpi' is a blt_registered target
-- [mpi property] BLT_MPI_INCLUDES: /usr/include/mpich
-- [mpi property] BLT_MPI_IS_OBJECT_LIBRARY: FALSE
-- [mpi property] BLT_MPI_IS_REGISTERED_LIBRARY: TRUE
-- [mpi property] BLT_MPI_LIBRARIES: BLT_NO_LIBRARIES
-- [mpi property] BLT_MPI_LINK_FLAGS: -Wl,-Bsymbolic-functions
-- [mpi property] BLT_MPI_TREAT_INCLUDES_AS_SYSTEM: TRUE
...
[ 63%] Linking CXX executable ../../../tests/blt_mpi_smoke
CMakeFiles/blt_mpi_smoke.dir/blt_mpi_smoke.cpp.o: In function `main':
/home/travis/build/LLNL/blt/tests/smoke/blt_mpi_smoke.cpp:21: undefined reference to `MPI_Init'
/home/travis/build/LLNL/blt/tests/smoke/blt_mpi_smoke.cpp:24: undefined reference to `MPI_Comm_rank'
/home/travis/build/LLNL/blt/tests/smoke/blt_mpi_smoke.cpp:26: undefined reference to `MPI_Comm_size'
/home/travis/build/LLNL/blt/tests/smoke/blt_mpi_smoke.cpp:31: undefined reference to `MPI_Reduce'
/home/travis/build/LLNL/blt/tests/smoke/blt_mpi_smoke.cpp:34: undefined reference to `MPI_Finalize'
collect2: error: ld returned 1 exit status
make[2]: *** [tests/blt_mpi_smoke] Error 1
make[1]: *** [blt/tests/smoke/CMakeFiles/blt_mpi_smoke.dir/all] Error 2
make: *** [all] Error 2
The command "make" exited with 2.
@white238 Just to double check, this is in addition to smoothing out the change from: MPIEXEC to MPIEXEC_EXECUTABLE which was already there?
@white238 ok, I see it know, I didn't expect it to show up in the diffs if it was already there -- but it did b/c you were making changes near by :-)
| gharchive/pull-request | 2019-05-23T01:08:05 | 2025-04-01T04:32:42.784714 | {
"authors": [
"cyrush",
"kennyweiss",
"white238"
],
"repo": "LLNL/blt",
"url": "https://github.com/LLNL/blt/pull/271",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
1971392973 | Test on Python 3.6
In GitLab by @wtbarnes on Oct 2, 2019, 11:25
The automated tests currently only test Python 3.7. We should add tests for Python 3.6 as well. We should also consider testing multiple versions of sunpy (e.g. the most current release as well as the master branch).
In GitLab by @wtbarnes on Oct 3, 2019, 13:58
closed via merge request !26
In GitLab by @wtbarnes on Oct 3, 2019, 13:58
mentioned in commit ef62f8e8504885fa54ad841245fd903c95b6bfcd
| gharchive/issue | 2019-10-02T18:25:23 | 2025-04-01T04:32:42.825664 | {
"authors": [
"nabobalis"
],
"repo": "LM-SAL/aiapy",
"url": "https://github.com/LM-SAL/aiapy/issues/22",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
502010010 | Sync Paymentrequest expiry with Desktop/iOS
Description
Currently the user can chose expiry rates for their requests from 10 minutes up to 24 hours.
On Desktop e.g. they can chose from 1 minute to 1 year.
Context
Current values on Desktop
Possible Implementation
Update the current values.
In our current codebase we already support one minute to a year. Actually we have all values plus "30 min" and "6 hours"
Nice, I already forgot about that one. Has been done with: #99
| gharchive/issue | 2019-10-03T11:32:01 | 2025-04-01T04:32:42.888098 | {
"authors": [
"maraph",
"michaelWuensch"
],
"repo": "LN-Zap/zap-android",
"url": "https://github.com/LN-Zap/zap-android/issues/116",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
455854041 | chore(deps): pin electron-builder to v20.41.0
Description:
Code signing in latest version of electron-builder has issues.
Motivation and Context:
Build broken.
See https://github.com/electron-userland/electron-builder/issues/3948
How Has This Been Tested?
yarn package --mac
Types of changes:
Build fix
Checklist:
[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.
Coverage remained the same at 19.848% when pulling 03b5e339541a6aed9a717c6cb570c93aab9dfc64 on mrfelton:fix/electron-build into b4a537d550e8214a2ba28f629367475049b189a9 on LN-Zap:next.
| gharchive/pull-request | 2019-06-13T17:05:48 | 2025-04-01T04:32:42.892684 | {
"authors": [
"coveralls",
"mrfelton"
],
"repo": "LN-Zap/zap-desktop",
"url": "https://github.com/LN-Zap/zap-desktop/pull/2421",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
2574340342 | No me salen los capítulos de la fuente "Tunovelaligera"
Source information
"Tunovelaligera"
Steps to reproduce
Expected behavior
Que me muestre los capítulos
Actual behavior
No se muestran los capítulos, aunque diga que esta completado me muestra 0
LNReader version
1.1.19
Android version
Android 14
Other details
No response
Acknowledgements
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.1.19.
[X] I have updated all installed extensions.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.
Hola sucede lo mismo en la version 2.0 beta
| gharchive/issue | 2024-10-08T22:34:45 | 2025-04-01T04:32:42.897422 | {
"authors": [
"Fruta999",
"hamunoz"
],
"repo": "LNReader/lnreader-plugins",
"url": "https://github.com/LNReader/lnreader-plugins/issues/1218",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
802645535 | Velocity Support
Velocity is a server proxy, similar to BungeeCord, if it wouldn't be too much of a hassle adding VelocityPowered would be preferred. Thank you.
I'll take a look at that when I have time :)
Just a update - this would work but I'm trying to use modern forwarding and such! I can't wait for this project to support Velocity!
| gharchive/issue | 2021-02-06T08:35:34 | 2025-04-01T04:32:42.905280 | {
"authors": [
"DBTDerpbox",
"LOOHP",
"Romvnly-Gaming"
],
"repo": "LOOHP/Limbo",
"url": "https://github.com/LOOHP/Limbo/issues/10",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
177573184 | Question about Django Integration
Hello,
I noticed the Django integration in the docs. Does this allow us to use mattermost to send a message to a Django app and get the result of a function back?
Yes, it is possible. Write your own management command, and run it on background.
| gharchive/issue | 2016-09-17T12:30:49 | 2025-04-01T04:32:42.929650 | {
"authors": [
"gotlium",
"mildlyill"
],
"repo": "LPgenerator/mattermost_bot",
"url": "https://github.com/LPgenerator/mattermost_bot/issues/23",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1806491640 | Add new models to convert_concentration
Add support for the Einasto and Hernquist profiles, although the Einasto profile uses the equation for NFW when getting the alpha parameter from cosmology. Now the function is in pure python, but it runs slower. For comparison, converting one concentration value takes 5 μs before vs 270 μs now and converting an array of 10 concentration values takes 6 μs before vs 600 μs now. I will close this PR if this is too slow or this PR is not necessary.
Still need to update the equations in the docstrings.
I cannot seem to fix the tests.
Pull Request Test Coverage Report for Build 5567748266
16 of 25 (64.0%) changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 97.281%
Changes Missing Coverage
Covered Lines
Changed/Added Lines
%
pyccl/halos/massdef.py
16
25
64.0%
Totals
Change from base Build 5553290862:
-0.1%
Covered Lines:
5653
Relevant Lines:
5811
💛 - Coveralls
Humm, although this is not something that is currently heavily used, I would rather not replace something in the code by a version that is so much slower. I can see two options:
Leave the existing NFW code in place for NFW, and use the method you implemented for the other two profiles.
Even better, implement the other two in C. A quick look at the code tells me it's just a matter of replacing the function whose root we need to find, so perhaps it's not so complicated.
Not planning on touching c-level files. Since CLMM already had this functionality, will close this PR.
| gharchive/pull-request | 2023-07-16T08:10:36 | 2025-04-01T04:32:42.957126 | {
"authors": [
"coveralls",
"damonge",
"hsinfan1996"
],
"repo": "LSSTDESC/CCL",
"url": "https://github.com/LSSTDESC/CCL/pull/1105",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
275795714 | Line numbers
I know we can splice in the lineno package, but it would be nice to have something easy built into start_paper since it's so important for the Pub. Policy review process. While there is an option for linenumbers in \documentclass for AASTeX, that implementation breaks a lot of other formatting (equations, itemized lists, etc.).
Can you provide an example of lineno (or some other solution)?
It's hard to see how we can provide a one-size-fits-all solution, given that under the hood many papers will be using one journal format or another, and some of them have their own options for line numbering. From the sound of it, the built-in solution for AASTeX is suboptimal, however.
This issue may be more at home in desc-tex, depending on what flavor the likely solution is.
To get it to work in the apj format, I had to modify the preamble as follows:
`
...
\RequirePackage[switch, columnwise, running, displaymath, mathlines]{lineno}
\newcommand*\patchAmsMathEnvironmentForLineno[1]{%
\expandafter\let\csname old#1\expandafter\endcsname\csname #1\endcsname
\expandafter\let\csname oldend#1\expandafter\endcsname\csname end#1\endcsname
\renewenvironment{#1}%
{\linenomath\csname old#1\endcsname}%
{\csname oldend#1\endcsname\endlinenomath}}%
\newcommand*\patchBothAmsMathEnvironmentsForLineno[1]{%
\patchAmsMathEnvironmentForLineno{#1}%
\patchAmsMathEnvironmentForLineno{#1*}}%
\AtBeginDocument{%
\patchBothAmsMathEnvironmentsForLineno{equation}%
\patchBothAmsMathEnvironmentsForLineno{align}%
\patchBothAmsMathEnvironmentsForLineno{flalign}%
\patchBothAmsMathEnvironmentsForLineno{alignat}%
\patchBothAmsMathEnvironmentsForLineno{gather}%
\patchBothAmsMathEnvironmentsForLineno{multline}%
}
...
\usepackage{enumitem}
...
\begin{document}
\linenumbers
...
`
That of course only covers fixes for screwed up formatting that came up in my document, and those who use other environments might discover other quirks. (I imagine tables could also be problematic)
Ideally the start_paper (or desc-tex) team would similarly fiddle with the docswitch-related preambles to get linenumbers working in all the supported formats and then just have an argument to \documentclass[\docopts]{\docclass} for turning it on and off. Perhaps this could be addressed at Sprint Week?
| gharchive/issue | 2017-11-21T17:22:26 | 2025-04-01T04:32:42.969493 | {
"authors": [
"abmantz",
"aimalz"
],
"repo": "LSSTDESC/start_paper",
"url": "https://github.com/LSSTDESC/start_paper/issues/70",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
1176588448 | 预训练模型文件损坏
您好，您发布的预训练模型100MB的压缩包是损坏的，我这尝试多次都没有成功
Tongbook你好，可以麻烦你提供一下你下载的预训练模型的名字和下载链接吗？或许你说的是MoCo或者wav2vec2的预训练模型？
我下载的mocov2预训练模型也是损坏的，请问哪里可以下载到正常的
| gharchive/issue | 2022-03-22T10:38:17 | 2025-04-01T04:32:42.981458 | {
"authors": [
"PeiyuChen1005",
"Tongbook",
"ouwen18"
],
"repo": "LUMIA-Group/Leveraging-Self-Supervised-Learning-for-AVSR",
"url": "https://github.com/LUMIA-Group/Leveraging-Self-Supervised-Learning-for-AVSR/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
246345656 | Error- " Unable to open object (Object '19' doesn't exist)"
Hello, after creating the .h5 file from training data, when I apply siterator, This error is coming - "Unable to open object (Object '19 doesn't exist)"
The image of hdf5 is attached with this.
I took only a small dataset to make sure first I learn what's happening in code. ( And to bring down computation complexity)
Hello, thanks for using our repository, and sorry for the late response. It looks like this error comes about because the key that you're looking at (speaker '19' in your case) is not in the *.h5 file that you had created. If you can show us the error with the trace as well as your input data, then perhaps that could illuminate your problem a bit more...
| gharchive/issue | 2017-07-28T13:21:33 | 2025-04-01T04:32:42.988956 | {
"authors": [
"karllab41",
"raikar008"
],
"repo": "Lab41/Magnolia",
"url": "https://github.com/Lab41/Magnolia/issues/89",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
953181674 | Drop support for SQLServer in Luminex module
Rationale
We don't have users for this module on SQL Server, and it's been causing test failures on TeamCity on SQL Server agents
Changes
Remove SQL Server script
Declare Postgres only in module and test code
@labkey-sweta we can drop this TeamCity project as part of this change:
https://teamcity.labkey.org/buildConfiguration/LabkeyTrunk_ModuleSuites_LuminexSqlserve?branch=&mode=builds
| gharchive/pull-request | 2021-07-26T18:41:54 | 2025-04-01T04:32:43.007556 | {
"authors": [
"labkey-jeckels"
],
"repo": "LabKey/commonAssays",
"url": "https://github.com/LabKey/commonAssays/pull/353",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1023005334 | CMake error: list sub-command FILTER requires list to be present
Using Visual Studio 2017 with CMake 3.12 gives the error
list sub-command FILTER requires list to be present
on the line
list(FILTER SOURCES EXCLUDE REGEX "${PROJECT_SOURCE_DIR}/vsg/.*" )
in the top level CMakeList.txt.
Fixed in PR #5.
| gharchive/issue | 2021-10-11T18:36:00 | 2025-04-01T04:32:43.022342 | {
"authors": [
"KnightTec"
],
"repo": "Lachei/VulkanPBRT",
"url": "https://github.com/Lachei/VulkanPBRT/issues/4",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2627667765 | [Social Media] More, but shorter, videos about Ladybird (I'll close this issue request, to avoid having too many open issues here)
Hey there folks,
This is just a small comment in regards to videos about ladybird.
I, and probably others, are interested in the news about ladybird, e. g. "is it ready yet?".
One way to keep up to date is via videos, such as:
https://www.youtube.com/watch?v=0aXSBCtELZ4
The video is fine, but as I have the attention span of a squirrel on a sugar nut rush, a length of 17 to 19 minutes is too long, IMO. I'd like to see more a range of, say, 4-8 minutes or so - just the primary gist, and showcasing a little bit of what is new. Ideally without too much audio, e. g. more eye candy than spoken text, though spoken text is also fine. For me I just want slightly shorter videos.
Anyway, that is the gist of it. Kind of a request to have more smaller videos about ladybird. This can be about singular features too, by the way, e. g. "this website now works, let me show you its features".
Thanks for reading!
You've opened and immediately closed several issues like this. The issue tracker is for technical issues, please refrain from opening these
| gharchive/issue | 2024-10-31T19:29:44 | 2025-04-01T04:32:43.025010 | {
"authors": [
"rubyFeedback",
"trflynn89"
],
"repo": "LadybirdBrowser/ladybird",
"url": "https://github.com/LadybirdBrowser/ladybird/issues/2092",
"license": "BSD-2-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
768382779 | refactor/file-restructure
created 'customers' and 'groomers' directories in 'components' directory; moved 'CustomerDashboard' and 'CustomerProfile' directories from 'components/pages' to 'components/customers'
Nice job-- that looks like it was tedious!
| gharchive/pull-request | 2020-12-16T02:10:44 | 2025-04-01T04:32:43.042833 | {
"authors": [
"KirstenS13",
"SRattacasa"
],
"repo": "Lambda-School-Labs/Express_Groomer-TeamC-FE",
"url": "https://github.com/Lambda-School-Labs/Express_Groomer-TeamC-FE/pull/45",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
630205892 | Removed parent from portfolio list, a few other QoL things
Description
Removed parent from portfolio list, a few other QoL things
Type of change
Please delete options that are not relevant.
[x] New feature (non-breaking change which adds functionality)
Change Status
[x] Complete, tested, ready to review and merge
Checklist
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts
the fast conflict resolution, poggers tbh desu
| gharchive/pull-request | 2020-06-03T18:00:21 | 2025-04-01T04:32:43.046583 | {
"authors": [
"michaelharms6010",
"reidysj"
],
"repo": "Lambda-School-Labs/My-School-FE",
"url": "https://github.com/Lambda-School-Labs/My-School-FE/pull/66",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
584112616 | auth tests
authRouter.spec.js
TESTING
| gharchive/issue | 2020-03-19T02:06:44 | 2025-04-01T04:32:43.047867 | {
"authors": [
"debauchery1st"
],
"repo": "Lambda-School-Labs/budget-blocks-be",
"url": "https://github.com/Lambda-School-Labs/budget-blocks-be/issues/42",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
945848250 | Problems with camera orientation
Debugging in Godot version 3.3. The same issue happened in Android and Xiaomi devices. The app camera does not understand the device sensor orientation, consequently, portrait images appears sideways on the screen, landscape images can be upright or upside down. I know nothing about XML and stuff, but the simpliest solution would be to make a viewport in godot, and create a new image with it, the image rotation would be set by the device orientation sensor. I think it could get similar to what WhatsApp does.
I've also had this issue and I think it stems for Godot not recognizing rotational metadata when importing external images. Personally, I think the issue really stems from hiding image's rotation in metadata, rather than just replacing the image with a rotated one.
I have looked in to this a while ago. The issue is with some devices have different camera rotation as default. It's also the issue if you take your photo in landscape or portrait mode.
There are some solutions we could implement into the plugin that may fix the issue for most of the devices but not 100%.
| gharchive/issue | 2021-07-16T00:42:02 | 2025-04-01T04:32:43.072649 | {
"authors": [
"Lamelynx",
"Pedro-Daniel",
"blurrred"
],
"repo": "Lamelynx/GodotGetImagePlugin-Android",
"url": "https://github.com/Lamelynx/GodotGetImagePlugin-Android/issues/8",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
353582047 | Migrate away from deprecated gulp-util dependency
I'm using this package in a project and noticed that one of its dependencies has been deprecated. According to this post from Gulp, gulp-util should be migrated as follows:
gutil.File => https://www.npmjs.com/package/vinyl
gutil.colors => https://www.npmjs.com/package/ansi-colors
gutil.log => https://www.npmjs.com/package/fancy-log
gutil.PluginError => https://www.npmjs.com/package/plugin-error
I can send a PR if you're interested.
Thanks!
Hi @thephilgray , thanks for the info!
Published gulp-file-assets@3.0.0 to solve this issue :)
| gharchive/issue | 2018-08-23T22:50:54 | 2025-04-01T04:32:43.079065 | {
"authors": [
"Lanfei",
"thephilgray"
],
"repo": "Lanfei/gulp-file-assets",
"url": "https://github.com/Lanfei/gulp-file-assets/issues/1",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1902394975 | [Bug] column 'row_number'
Bug report
What I did
$this->crud->addColumn( [ 'name' => 'row_number', 'type' => 'row_number', 'label' => '#', 'orderable' => false, 'priority' => 1, ]);
What I expected to happen
Adding a special column with numbers
What happened
The column is added but the first line breaks the standard layout for the list.blade.php template in the mobile version
What I've already tried to fix it
temporarily abandoned this column, better wait for corrections for styles
Is it a bug in the latest version of Backpack?
After I run composer update backpack/crud the bug... is it still there?
Yes
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 8.1.23 (cli) (built: Sep 1 2023 17:27:48) (NTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.1.23, Copyright (c) Zend Technologies
with Xdebug v3.2.2, Copyright (c) 2002-2023, by Derick Rethans
LARAVEL VERSION:
10.23.1.0
BACKPACK PACKAGE VERSIONS:
backpack/backupmanager: v5.0.0
backpack/basset: 1.2.0
backpack/crud: 6.2.0
backpack/generators: v4.0.2
backpack/langfilemanager: 5.0.0
backpack/logmanager: v5.0.0
backpack/permissionmanager: 7.0.1
backpack/pro: 2.0.11
backpack/settings: 3.1.0
backpack/theme-tabler: 1.1.0
Hey @smart4you
I'm also using row_number in a project. The following screenshot confirms it's not a bug.
CRUD::addColumn([
'name' => 'row_number',
'type' => 'row_number',
'label' => '#',
'orderable' => false,
])->makeFirstColumn();
LARAVEL VERSION:
10.23.1.0
BACKPACK PACKAGE VERSIONS:
backpack/backupmanager: v5.0.0
backpack/basset: 1.2.0
backpack/crud: 6.2.0
backpack/devtools: 2.0.3
backpack/editable-columns: 3.0.2
backpack/filemanager: 3.0.3
backpack/generators: v4.0.2
backpack/logmanager: v5.0.0
backpack/menucrud: v4.0.1
backpack/newscrud: v5.0.0
backpack/pagemanager: 3.2.0
backpack/permissionmanager: 7.0.1
backpack/pro: 2.0.11
backpack/settings: 3.1.0
backpack/theme-tabler: 1.1.0
Try
php artisan optimize:clear & php artisan basset:fresh
and Your other posted issue says you have overridden list.blade.php. Compare it with the CRUD package list.blade.php. See if you find something there.
and if you want to use a custom list view for a particular CRUD, use $this->crud->setListView('path.to.your.view');.
More info here
Thanks for the quick answer, today I will create a new and clean project to confirm that the problem is on my side
It looks like I broke something in my project that gives this effect((
Thanks for your time
| gharchive/issue | 2023-09-19T07:41:57 | 2025-04-01T04:32:43.195722 | {
"authors": [
"karandatwani92",
"smart4you"
],
"repo": "Laravel-Backpack/CRUD",
"url": "https://github.com/Laravel-Backpack/CRUD/issues/5319",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1966593478 | Fix issue #13
Fix para issue Configuración: Instalar Tailwind CSS en React y UI Framework #13
Descripción del Cambio:
Este pull request aborda la tarea de configurar e instalar Tailwind CSS en el proyecto React existente. Además, se detalla la documentación para la configuración y el uso de Tailwind CSS.
Cambios Realizados:
Configuración e instalación de Tailwind CSS en el proyecto Vite con TypeScript y React.
Documentación detallada en el archivo README.md sobre la configuración y el uso de Tailwind CSS.
Comentarios Adicionales:
La configuración del UI framework se ha dejado pendiente para futuras iteraciones. Esto permitirá una mejor planificación y selección de la biblioteca de UI framework más adecuada para el proyecto.
Checks:
[x] Se ha instalado y configurado Tailwind CSS en el proyecto React.
[x] La documentación sobre la configuración y el uso de Tailwind CSS se ha agregado al archivo README.md.
[ ] El UI framework se abordará en iteraciones futuras, una vez se haya seleccionado y planificado su incorporación.
Cierro el issue #13 parcialmente con este pull request.
¡Gracias por revisar mi contribución!
esto es React solamente? porque ya hay uno con NextJs
| gharchive/pull-request | 2023-10-28T13:20:30 | 2025-04-01T04:32:43.225004 | {
"authors": [
"FrancoCanzani",
"dody87"
],
"repo": "Las-Fuerzas-Del-Cielo/Sistema-Anti-Fraude-Electoral",
"url": "https://github.com/Las-Fuerzas-Del-Cielo/Sistema-Anti-Fraude-Electoral/pull/41",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2567525489 | 🐛 [ Bug ]: 获取封包数据失败
您使用的版本？
3.1.2
系统版本？
win10
您遇到了什么问题？
获取封包数据失败，重启后又好了
请提供错误截图？
请求过快，IP被封，请更换IP或者重启。
不是BUG，可能请求量过大导致数据拥堵
| gharchive/issue | 2024-10-04T23:21:28 | 2025-04-01T04:32:43.230151 | {
"authors": [
"ASCIIX",
"LauZzL",
"mortalref9527"
],
"repo": "LauZzL/leitingzhanji-ui",
"url": "https://github.com/LauZzL/leitingzhanji-ui/issues/91",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1581172103 | Diagrams
Diagram repair
seems to be an empty file
| gharchive/pull-request | 2023-02-12T08:34:27 | 2025-04-01T04:32:43.232683 | {
"authors": [
"Laura-Novich-OBW",
"delas6006"
],
"repo": "Laura-Novich-OBW/student-showcase",
"url": "https://github.com/Laura-Novich-OBW/student-showcase/pull/119",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
823956815 | tch::Cuda::is_available() returns false using local libtorch 1.8 for CUDA 11.1
I am on Arch Linux, Rust/cargo 1.50 and have set both LIBTORCH and LD_LIBRARY_PATH according to the README. tch-rs is on latest commit to master, commit 25ac21d. I am running the example with cargo run --example basics. I get false returned by both tch::Cuda::is_available() and tch::Cuda::cudnn_is_available().
I have triple checked that the path for LIBTORCH is correct, and it must be correct as everything builds fine and libtorch was not downloaded inside of tch-rs. I know that CUDA is installed correctly as well, because using the python-pytorch-cuda package from the Arch community repo (which is on PyTorch 1.8) I can use CUDA tensors just fine and torch.cuda.is_available() returns True.
I should note that my version of CUDA is 11.2, though I haven't seen that cause any issues with PyTorch 1.8 in Python (which apparently was built for CUDA 11.1).
Any suggestions? Are others having this issue? I saw #291, but I am not building in release, so I think this is a different problem.
Looks like if I unset LIBTORCH and build, it downloads libtorch (target directory is now 1.4 GB) and builds successfully, but I sitll get false for tch::Cuda::is_available() and tch::Cuda::cudnn_is_available(). So it definitely is not an issue with correctly setting environment variables.
Thanks for reporting this issue, I just pushed a (hacky) fix that should hopefully help with this.
The culprit here is that the C++ library is split in a cpu and a cuda version, and it's often the case for the cuda version not to be included by the linker as there is no "hard" dependency to it. We have a hack in place to get around this by forcing the dependency but this hack broke with the 1.8 release as the cuda library was split in multiple sub libraries and one of them (cuda_cu) was removed by the linker. I tweaked the hack to force this to be included.
Longer term, this will be tackled by passing -Wl,--no-as-needed via Cargo extra-link-args but this is only available since cargo 1.50 in nightly mode so we'll wait for this to reach stable until we push the fix.
Thanks for the quick reply and fix! Ah, I see - let's hope that makes it to cargo stable soon.
That fix seemed to do the trick! I am now getting true for both function calls. 😄 Thanks for your help!
With the latest change builds fail against the libtorch compiled against CUDA 10.2:
= note: /nix/store/cp1sa3xxvl71cypiinw2c62i5s33chlr-binutils-2.35.1/bin/ld: cannot find -ltorch_cuda_cu
/nix/store/cp1sa3xxvl71cypiinw2c62i5s33chlr-binutils-2.35.1/bin/ld: cannot find -ltorch_cuda_cpp
collect2: error: ld returned 1 exit status
because it doesn't have these libraries
❯ unzip -l libtorch-cxx11-abi-shared-with-deps-1.8.0.zip | grep libtorch_
352214112 02-27-2021 00:02 libtorch/lib/libtorch_cpu.so
1158264872 02-27-2021 00:02 libtorch/lib/libtorch_cuda.so
12640 02-27-2021 00:02 libtorch/lib/libtorch_global_deps.so
24837016 02-27-2021 00:02 libtorch/lib/libtorch_python.so
Ah it's a bummer that this depends on the cuda version. Anyway I just pushed a small tweak that will only trigger these libs to be linked if the files are present, hopefully this getting 10.2 to work.
Works like a charm, thanks!
So now I am not entirely sure that this is working. Running the basics example works just fine, but if I try to run the reinforcement learning example, I am getting a lot of linker errors.
BTW: I am still on the first commit where you first made the fix; I haven't pulled in the commit(s) after that.
➜ cargo run --example reinforcement-learning --features=python a2c2 > log.txt
Compiling tch v0.4.0 (/home/seth/school/adv_dl/project2/tch-rs)
error: linking with `cc` failed: exit code: 1
|
= note: "cc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-m64" "-Wl,--eh-frame-hdr" "-L" "/usr/lib64/rustlib/x86_64-unknown-linux-gnu/lib"
...
(then there is lots and lots of linker flags, I'll just share the first and last few of them)
"-Wl,-Bdynamic" "-lstdc++" "-ltorch_cuda" "-ltorch_cuda_cu" "-ltorch_cuda_cpp" "-ltorch" "-ltorch_cpu" "-lc10" "-lgomp" "-lbz2" "-lpython3.9" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc"
= note: /usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_rnn_executor'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `caffe2::TensorShape::TensorShape()'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `c10::C10FlagsRegistry[abi:cxx11]()'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `bool c10::C10FlagParser::Parse<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*)'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_force_shared_col_buffer'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `caffe2::OperatorDef::OperatorDef()'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_operator_throw_if_fp_exceptions'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `caffe2::BlobProto::BlobProto()'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_print_blob_sizes_at_exit'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cu.so: undefined reference to `c10::MessageLogger::~MessageLogger()'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `bool c10::C10FlagParser::Parse<int>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int*)'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_max_keep_on_shrink_memory'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_operator_throw_on_first_occurrence_if_fp_exceptions'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `caffe2::TensorProtos::TensorProtos()'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `caffe2::DeviceOption::DeviceOption()'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `caffe2::NetDef::NetDef()'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_operator_throw_if_fp_overflow_exceptions'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cu.so: undefined reference to `c10::MessageLogger::MessageLogger(char const*, int, int)'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_keep_on_shrink'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `FLAGS_caffe2_workspace_stack_debug'
/usr/bin/ld: /home/seth/packages/libtorch/lib/libtorch_cuda_cpp.so: undefined reference to `bool c10::C10FlagParser::Parse<bool>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool*)'
collect2: error: ld returned 1 exit status
error: aborting due to previous error
error: could not compile `tch`
To learn more, run the command again with --verbose.
Does this seem related, or should I make a separate issue?
I fixed it. There must have been some issue with trying to link with /usr/lib/libtorch_cuda.so (installed from the python-pytorch-cuda Arch package) vs. the locally downloaded libtorch, as uninstalling the python-pytorch-cuda package resulted in a successful build and run of the example program. It's also using Cuda(0) as the device, so everything looks good!
Sorry for the false alarm!
Glad that you got it to work, closing this issue for now but feel free to re-open if you notice more issues.
| gharchive/issue | 2021-03-07T16:27:22 | 2025-04-01T04:32:43.242831 | {
"authors": [
"LaurentMazare",
"danieldk",
"sethmnielsen"
],
"repo": "LaurentMazare/tch-rs",
"url": "https://github.com/LaurentMazare/tch-rs/issues/329",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2517537987 | [Enhancement]: Issues running Windows game on Linux with dotnet installed on Linux
Describe the new feature or enhancement
I followed the instructions for how to install MelonLoader v0.6.4 for a Windows game running under Steam Proton on Linux.
I had some problems, and would like to share my solution.
The main problem is that it failed to load hostfxr:
[ERROR] il2cpp_init detour failed: Failed to load hostfxr. Please make sure you have installed the .NET 6.0 runtime.
I definitely had the dotnetdesktop6 package installed per the instructions.
It turned out that it was failing because the Linux dotnet SDK was installed on the host, and it configures a system-wide environment variable, DOTNET_ROOT. This environment variable was being passed into the Proton Windows environment. The Windows dotnet host tool also uses this environment variable, and having it set, especially to a Linux host path, prevented it from finding its runtime.
In Steam, this environment variable can be cleared by setting launch options for the game:
DOTNET_ROOT= %command%
I don't think this should be fixed/enhanced in MelonLoader itself, but maybe it would help somebody else if it got into the instructions.
@samr7 Can you make a short step by step how to set the environment variable on Lutris or Bottles?
@ZanDev32 Are you also noticing this problem?
I am unfamiliar with Lutris.
I also don't know of a good way to do this using Wine built-in mechanisms or winetricks. It's possible to set environment variables in user.reg, but setting one to an empty string does not have the effect of removing or masking an existing environment variable.
Simply run the dotnet installer in wine tricks. Make sure you are using the x64 desktop runtime executable! And also add the version library in wine cfg under the libraries page in wine tricks to the prefix
| gharchive/issue | 2024-09-10T19:33:27 | 2025-04-01T04:32:43.260973 | {
"authors": [
"KibblesTheKitten",
"ZanDev32",
"samr7"
],
"repo": "LavaGang/MelonLoader",
"url": "https://github.com/LavaGang/MelonLoader/issues/740",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
139133521 | Can't set Host header via headers argument
Hi,
wanted to set the Host header so I can run locust against different endpoints.
WebSocketClient seems to accept custom headers, but there were a couple of surprises:
the headers argument is not a dict like in other frameworks, e.g. http://docs.python-requests.org/en/master/user/quickstart/#custom-headers
the headers list is appended - so you can't actually set the Host header
best regards,
Florian
This makes it work for me:
@property
def handshake_headers(self):
"""
List of headers appropriate for the upgrade
handshake.
"""
headers = [
('Host', self.host),
('Connection', 'Upgrade'),
('Upgrade', 'websocket'),
('Sec-WebSocket-Key', self.key.decode('utf-8')),
('Origin', self.url),
('Sec-WebSocket-Version', str(max(WS_VERSION)))
]
if self.protocols:
headers.append(('Sec-WebSocket-Protocol', ','.join(self.protocols)))
headers = OrderedDict(headers)
if self.extra_headers:
headers.update(self.extra_headers)
return headers.items()
| gharchive/issue | 2016-03-08T00:09:50 | 2025-04-01T04:32:43.271973 | {
"authors": [
"fpn"
],
"repo": "Lawouach/WebSocket-for-Python",
"url": "https://github.com/Lawouach/WebSocket-for-Python/issues/188",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
2622960596 | [Snyk] Security upgrade gatsby from 3.3.0 to 4.22.0
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
starter/package.json
starter/yarn.lock
Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
Issue
Score
Denial of Service (DoS) SNYK-JS-DATALOADER-8248488
641
[!IMPORTANT]
Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)
👷 Deploy Preview for taupe-cassata-172709 processing.
Name
Link
🔨 Latest commit
3a59f7d81a3b7e7407d9b6590b134c882c22c9cd
🔍 Latest deploy log
https://app.netlify.com/sites/taupe-cassata-172709/deploys/6721c52580709b000838e831
| gharchive/pull-request | 2024-10-30T05:33:23 | 2025-04-01T04:32:43.283655 | {
"authors": [
"LawrenceHecht"
],
"repo": "LawrenceHecht/strapi-starter-gatsby-blog",
"url": "https://github.com/LawrenceHecht/strapi-starter-gatsby-blog/pull/18",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1535954185 | help about configuration
Hello.
The following isn't an issues, just a help like on a forum. I could have posted on a forum (for example of my GNU/Linux distribution) or on Reddit Neovim, but if they don't use LazyVim it's time wasted.
I've just installed LazyNvim (good work, thank you, I really like it). I don't know Lua language, nor Neovim enough because I migrated from Vim a few days ago.
I have some file written in vimscript. Where can I put these files to be loaded from lazynvim? If I put a plugin file 'foo.vim' in the '.../lua/plugins' directory, it doesn't work.
I want to disable 'witch-key' plugin, so I added it to "disable_plugin" array within '.../lua/config/lazy.lua' file. How can I see all the plugins?
Sometimes, I got messages like:
- Failed (18)
cmp-buffer fetch failed
fatal: unable to access '.../cmp-buffer.git/': Could not resolve github.com
lualine.nvim fetch failed
[...]
How fix these manually?
I'm using:
NVIM v0.9.0-dev-710+gef89f9fd46
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Thank you.
Kind regards
For user questions, there's the discussions forum https://github.com/LazyVim/LazyVim/discussions
you can put vimscript files in ~/.config/nvim/plugin/
To disable a plugin, please see the examples in the docs.
Those errors are exactly what they say they are. You don't seem to be connected to the internet
| gharchive/issue | 2023-01-17T08:14:13 | 2025-04-01T04:32:43.292733 | {
"authors": [
"folke",
"gliom"
],
"repo": "LazyVim/LazyVim",
"url": "https://github.com/LazyVim/LazyVim/issues/72",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2342089021 | feat(util): add (git) blame-nvim
adding https://github.com/FabijanZulj/blame.nvim with default settings and overriding <leader>gb keymap
Also have you tried f-person/git-blame.nvim? That's what I'm using, but I'm interested if you've tried both and can do a comparison between them. This is not a suggestion to change the plugin, just a question from a user perspective if possible.
<leader>gb is a default keymap that shows a git history for the cursor location.
I also don't really see the point of this extra, since it's simply adding the plugin.
Users can easily do that themselves
Also have you tried f-person/git-blame.nvim? That's what I'm using, but I'm interested if you've tried both and can do a comparison between them. This is not a suggestion to change the plugin, just a question from a user perspective if possible.
I didn't know about this. I'll give it a try :)
<leader>gb is a default keymap that shows a git history for the cursor location.
it is labeled "Git Blame Line" so I thought it would make sense to "Git Blame File" instead :)
I also don't really see the point of this extra, since it's simply adding the plugin. Users can easily do that themselves
oops! I thought it would make a nice addition. closing :)
| gharchive/pull-request | 2024-06-09T08:06:00 | 2025-04-01T04:32:43.296631 | {
"authors": [
"dpetka2001",
"folke",
"gacallea"
],
"repo": "LazyVim/LazyVim",
"url": "https://github.com/LazyVim/LazyVim/pull/3552",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1960470415 | Save node button bug?
the save node button does not look as it is supposed to look(looks squished). A bug or because of the browser?
Just tried to add a new node and got the same issue (see screenshot). My window was using all the real estate of my computer, so it's probably something that other users will see as well
| gharchive/issue | 2023-10-25T03:42:00 | 2025-04-01T04:32:43.301374 | {
"authors": [
"ElmiraOn",
"biltzerpos"
],
"repo": "LePa-YU/Visualizer",
"url": "https://github.com/LePa-YU/Visualizer/issues/33",
"license": "CC0-1.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2396147226 | WebRTC documentations and GH repos
GH repo:
https://github.com/gurkanucar/spring-boot-webrtc-peer2peer
With Socket.io:
https://github.com/mrniko/netty-socketio
Chaim's repo for WebRTC
https://github.com/coding-with-chaim/toggle-cam-final
| gharchive/issue | 2024-07-08T17:11:01 | 2025-04-01T04:32:43.303483 | {
"authors": [
"LePhenix47"
],
"repo": "LePhenix47/Lahouiti_Younes_P13_21062024",
"url": "https://github.com/LePhenix47/Lahouiti_Younes_P13_21062024/issues/2",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
592367281 | New version of the kiosk system for nerve 1.6?
Tried to update to nerves 1.6 but I got this error
Failed to use "nerves" (versions 1.6.0 and 1.6.1) because
kiosk_system_rpi3 (version 1.9.1) requires ~> 1.5.0
mix.exs specifies ~> 1.6
** (Mix) Hex dependency resolution failed, change the version requirements of your dependencies or unlock them (by using mix deps.update or mix deps.unlock). If you are unable to resolve the conflicts you can try overriding with {:dependency, "~> 1.0", override: true}
my current env:
OSX 10.15.4
Elixir 1.10.2-otp-22
Erlang 22.1.8
See PR #53. I don't know who maintains this repository now, so I'm not sure when/if it will be merged.
In the mean time, I suspect that marking :nerves to be override: true will work so that you can use 1.6.1. That's pretty painful for me to type, so I hope that someone can make a new kiosk_system_rpi3 release. You could also force Nerves 1.5 and use Elixir 1.9.4.
This was pushed to hex in release v1.10.0
| gharchive/issue | 2020-04-02T05:26:19 | 2025-04-01T04:32:43.307073 | {
"authors": [
"epinault",
"fhunleth",
"mobileoverlord"
],
"repo": "LeToteTeam/kiosk_system_rpi3",
"url": "https://github.com/LeToteTeam/kiosk_system_rpi3/issues/55",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
137773268 | Can't install from bower - no tags found
On running bower install --save prefix-free:
Additional error details:
No tags found in git://github.com/LeaVerou/prefixfree.git
Available branches: gh-pages
:)
@tdmalone Did you see #173 ?
No I didn't, thanks! I downloaded it manually, but agree with the comment in that issue that 'While the fix worked, this should be resolved to allow easier uptake via bower.' =)
@tdmalone I have a PR with steps to tag :) Lets hope it gets tagged so this won't occur in the future :)
| gharchive/issue | 2016-03-02T04:56:28 | 2025-04-01T04:32:43.310815 | {
"authors": [
"TDA",
"tdmalone"
],
"repo": "LeaVerou/prefixfree",
"url": "https://github.com/LeaVerou/prefixfree/issues/6116",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
179655198 | Cannot drag panorama viewer inside popup
How to reproduce
Leaflet version I'm using: 1.0.0
Browser (with version) I'm using: Google Chrome 53.0.2785.116
OS/Platform (with version) I'm using: macOS Sierra
step 1: open http://playground-leaflet.rhcloud.com/yuq/edit?html,output
step 2: drag panorama image inside popup
What behaviour I'm expecting and which behaviour I'm seeing
Can drag panorama viewer. It works perfectly for leafletjs 0.7.7.
Minimal example reproducing the issue
http://playground-leaflet.rhcloud.com/yuq/edit?html,output
The linked playground example loads some resources (https://www.marzipano.net/demos/common/requestAnimationFrame.js, for example) with HTTPS/cert problems, so they refuse to load for me. This unfortunately makes it impossible to see the issue.
OK, after browsing to https://www.marzipano.net manually and temporarily accepting the cert (which applies to a different domain name), I can see the bug.
Apparently dragging on the <canvas> does not work, but dragging from the empty region of the popup container does. Weird.
This seems to be caused by calling L.DomEvent.disableClickPropagation() in L.Popup._initLayout().
Now we have to see why we did that, and why disabling click propagation from the popup container to the map pane also disables propagation from children elements under whatever circumstances.
We need to check that pointer interactions inside popups work well. A better/simpler test case than the panorama scenario might be setting up some dragula examples inside a popup.
Seems like duplicate of #6044.
| gharchive/issue | 2016-09-28T00:59:10 | 2025-04-01T04:32:43.318179 | {
"authors": [
"IvanSanchez",
"helmi03",
"johnd0e",
"perliedman"
],
"repo": "Leaflet/Leaflet",
"url": "https://github.com/Leaflet/Leaflet/issues/4960",
"license": "BSD-2-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
232759985 | Can I add shadows for leaflet polyline ?
How to reproduce
Leaflet version I'm using:
Browser (with version) I'm using:
OS/Platform (with version) I'm using:
step 1
step 2
What behaviour I'm expecting and which behaviour I'm seeing
Minimal example reproducing the issue
[ ] this example is as simple as possible
[ ] this example does not rely on any third party code
Using http://playground-leaflet.rhcloud.com/ or any other jsfiddle-like site.
Hi and thanks for using Leaflet!
Please note that this is our issue tracker, where bugs and feature requests and posted and discussed. For questions on how to use Leaflet and other support, you're better off using stackoverflow or gis.stackexchange.com.
You could possibly emulate shadows by adding multiple polyline's with the same coordinates but different styles. Also search for plugins that could help with this.
| gharchive/issue | 2017-06-01T04:02:20 | 2025-04-01T04:32:43.322474 | {
"authors": [
"chm74",
"perliedman"
],
"repo": "Leaflet/Leaflet",
"url": "https://github.com/Leaflet/Leaflet/issues/5543",
"license": "BSD-2-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
435857827 | Baselayer control doesn't select default baselayer if using more than one map
Hi,
here the example (leaflet V1.4.0):
https://aachen-hat-energie.de/test_ww/test_zukunft.htm
The baselayer-control is only activated on the third map, not on the first and second, as it should be. My Code:
<link rel="stylesheet" href="../js/Leaflet/leaflet.css" >
<script src="../js/Leaflet/leaflet.js" ></script>
<script src="../js/Leaflet/leaflet-bing-layer.min.js"></script>
<script>
'use strict';
var BING_KEY = "AplTrT4uzwlmfcERFFQu_NqDycERC_Er0qGYzZhIqrDfq-naYCsUr1kbbKRUqhq1";
var osmUrl = 'https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png';
function show_karte(div_id, mittelpunkt, zoom){
var bingLayer = L.tileLayer.bing({bingMapsKey: BING_KEY, maxZoom: 20, imagerySet: 'Aerial', attribution: '© 2019 Microsoft Corporation, Earthstar Geographics SIO'});
var bingLabelLayer = L.tileLayer.bing({bingMapsKey: BING_KEY, maxZoom: 20, imagerySet: 'AerialWithLabels', attribution: '© 2019 Microsoft Corporation, Earthstar Geographics SIO'});
var osmLayer = L.tileLayer(osmUrl, {maxZoom: 20, attribution: 'Map data © <a href="https://www.openstreetmap.org/">OpenStreetMap</a> contributors, <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>'});
var mittelpunkt = [mittelpunkt[1], mittelpunkt[0]]
var map = L.map(div_id,{layers: [bingLabelLayer]}).setView(mittelpunkt, zoom);
var baseLayers = {"Straßenkarte": osmLayer, "Luftbild mit Straßennamen": bingLabelLayer,"Luftbild": bingLayer};
var control = L.control.layers(baseLayers).addTo(map);
};
</script>
</head>
<body>
<div id="map" style="width:450px; height: 450px;">
<script type="text/javascript"> show_karte("map",[6.026173,50.816022],13); </script>
</div>
<div id="map1" style="width:550px; height: 450px;">
<script type="text/javascript"> show_karte("map1",[6.10428,50.76079],11); </script>
</div>
<div id="map2" style="width:650px; height:450px">
<script type="text/javascript">show_karte("map2",[6.10428,50.76079],12); </script>
</div>
</body>
I tried solutions as
https://aachen-hat-energie.de/test_ww/test_zukunft1.htm
https://aachen-hat-energie.de/test_ww/test_zukunft2.htm
which did not help. There seems to be only ONE control-object.
Sorry, I'm a dummy, but nobody on stackoverflow could help.
Plunkr here.
The word is not "activated", but rather "doesn't show any selected baselayer".
Can be due to https://github.com/Leaflet/Leaflet/commit/19d9e3bc93072bac655b9c6c28737442a6afe7fc . Should research whether several <section>s with radio buttons make exclusive groups of if they behave like one group of checkboxes.
I stumbled across this issue as well and thought I was doing something wrong, until I realized it might be a bug.
It seems their is no issue in Leaflet 0.7.2, while the issue is reproducible in Leaflet 1.4.0.
The following fiddles demonstrate the issue:
Leaflet 0.7.2 http://jsfiddle.net/sc28/fvy8aq37/2/ --> the base layers are correctly selected in both map controls
Leaflet 1.4.0 http://jsfiddle.net/sc28/9j3hstgx/ --> the base layers are only selected in the second map; when a base map is clicked in either map control, it gets deselected in the other.
Hm, on my PC the second example works well too.
@wowonk Which browser are you using? I tried on Firefox and Chrome and the issue is reproduced in both. Which browser are you using?
Hm, I tested on my tablett (MS Surface 3) with newest Fireforx, Win10, dirctX V12, Treiber WDDM 2.0: it works
I now tested on my PC with newest Firefox (Win8), dirctX V11, Treiber WDDM 1.3: I have the same errors as you
What now ???
Duplicate of #6482. It's already fixed by #6483
Wow, I forgot I approved such a PR :innocent:
Tested it locally, the issue is gone.
BTW @IvanSanchez, I'm going to release new Leaflet version this week.
Are there PRs that need to merged before the release?
| gharchive/issue | 2019-04-22T19:32:00 | 2025-04-01T04:32:43.331389 | {
"authors": [
"IvanSanchez",
"cherniavskii",
"sc28",
"wowonk"
],
"repo": "Leaflet/Leaflet",
"url": "https://github.com/Leaflet/Leaflet/issues/6618",
"license": "BSD-2-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
1369020330 | Get rid of "sl, sh, sa, dl, dh, da, pl, ph, pa", deliver the numbers programatically.
Each set provides low, high, and average, and we have a method (list_low_high_avg()) that can produce those numbers. We don't need a long dict for storing data.
Done as a part of issue_006.
| gharchive/issue | 2022-09-11T18:03:36 | 2025-04-01T04:32:43.332892 | {
"authors": [
"LeamHall"
],
"repo": "LeamHall/bp_tracker",
"url": "https://github.com/LeamHall/bp_tracker/issues/24",
"license": "Artistic-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1582069007 | fix: load envs at js boot
📝 Description
Problem: in some cases, Ledger Live Desktop don't properly set the env from process.env : when our JS code expected getEnv() value to be available and settled at boot time.
To fix this, we simply can load the module that do the setEnv (experimental.tsx in the current case of LLD) before the rest of our codebase (notably of coin implementations)
A way to reproduce the issue:
EXPERIMENTAL_EXECUTION_ON_RENDERER=1 API_STELLAR_HORIZON=https://stellar.coin.ledger-stg.com pnpm dev:lld
and when you sync a stellar account, it was still using the production one (see in Network panel) because the stellar impl have a getEnv() call at the module level: https://github.com/LedgerHQ/ledger-live/blob/develop/libs/ledger-live-common/src/families/stellar/api/horizon.ts#L26 (which makes it impossible to have an experimental settings for it btw, but at least we need to support its 'loads'. this isn't how getEnv is supposed to be used and i think it's noted as improvement on blockchain side but note it is just one example among possibly other cases)
❓ Context
Impacted projects: LLD
Linked resource(s): n/a
✅ Checklist
[ ] Test coverage uneasy to automate a test for this but i'm going to check later
[x] Atomic delivery
[x] No breaking changes
📸 Demo
🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.
ok i hate this XD
| gharchive/pull-request | 2023-02-13T10:25:28 | 2025-04-01T04:32:43.382114 | {
"authors": [
"gre"
],
"repo": "LedgerHQ/ledger-live",
"url": "https://github.com/LedgerHQ/ledger-live/pull/2601",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2007886623 | cx aes: fix some warnings for the OSU
Description
Fix some warnings needed for OSU build
Changes include
[X] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (e050ce5) 59.47% compared to head (ac046e0) 59.47%.
Additional details and impacted files
@@ Coverage Diff @@
## master #470 +/- ##
=======================================
Coverage 59.47% 59.47%
=======================================
Files 12 12
Lines 1683 1683
=======================================
Hits 1001 1001
Misses 682 682
Flag
Coverage Δ
unittests
59.47% <ø> (ø)
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
| gharchive/pull-request | 2023-11-23T10:15:25 | 2025-04-01T04:32:43.390012 | {
"authors": [
"codecov-commenter",
"jarevalo-ledger"
],
"repo": "LedgerHQ/ledger-secure-sdk",
"url": "https://github.com/LedgerHQ/ledger-secure-sdk/pull/470",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.