From 1-to-100: Growth Hacking For Established Projects

Who Can Enter:
Anyone who is in the process of starting a web3 company that is pre-funding can participate.
Prize
$500 in ETH (2 prizes for less than 10 submissions, 4 prizes awarded if more than 10 submissions received).
Challenge
Have you been working on a blockchain or Web3 startup in your spare time?  Do you need an excuse to take a break from coding and ruthlessly focus on traction? If so, this hackathon is for you!
Over the next 15 days, drive as much viral growth for your startup as you possibly can. This is something you need to do anyways; let us pay you to do it! At the end of the hackathon, prove to us that you’ve made major positive impact in your metrics by showing us significant improvement in:

Beta signups or emails collected
Medium post shares or claps
Existing Web3 players talking about your idea publicly (e.g. on Twitter or in publications)
Industry SME endorsements (recorded, written, or published)
Members in your WhatsApp or Telegram group
Participation in your Slack or Discord space
Other (tell us how you measure virality!)

The only metric we will not accept is Twitter metrics, as they can be easily tampered with.
Deliverables Due Upon Completion
We expect to see the following upon completion of the hackathon:

A link to your product webpage or existing product materials
A benchmark of metrics as of January 29, 2020
Quantifiable proof of traction both upon completion and over time. Show us your numbers!
An open-source playbook on how you achieved success, written and published as an article, a deck, a PDF, etc. This should be at least 700 words in length.

How We Score Your Entries
Quantitative: Link to score-card with weighted scores and how it will be calculated for each.
Qualitative: 40% of the score will be based on the playbook; the creativity and ingenuity shown in finding potential users for your next project and building a community around it.
Rules
The following rules will be strictly enforced by judges, at their discretion:

Any cheating will result in immediate disqualification (no bots!)
Each applicant must meet minimum scoring requirements
Applicants must be able to showcase benchmark numbers as of January 29, 2020 for comparison to post-hackathon numbers.

Resources:
Feel free to consult the following resources about growth hacking and lean experimentation:

Fake door: https://hackernoon.com/fake-door-the-mvp-before-the-mvp-61197ed264a3
Lean UX: https://www.uxmatters.com/mt/archives/2016/02/validating-product-ideas-through-lean-user-research.php
Cold calling for introverts: https://www.youtube.com/watch?v=3tcVZtgUWYk&t=0s
How to Launch Your Blockchain Startup (Without Writing a Single Line of Code)
https://media.consensys.net/how-to-launch-your-blockchain-startup-without-writing-a-single-line-of-code-9c6970b0e43d

Is it restricted to Ethereum ecosystem ? Or it can be any public web3 stack ?

Is it restricted to Ethereum ecosystem ? Or it can be any public web3 stack ?

@aj07 Not restricted to Ethereum, any Web3 project qualifies!

@gitcoinbot & @zherring  I have filled the form and put the link during submission. Here it says missing link...
Any idea ?

I thought there would be 2 winners based on the description.  Did the rest of us not meet qualifications?


Some response headers are stripped off when you sign in

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to Graph Explorer while not signed in, and run a query
See the list of response headers listed on the response headers tab
Now sign in and run the same query, see the response headers list is shorter
that's the error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
AB#9911

@thewahome
Can you please share the response with the headers that you are getting when you make a request to the Graph API  through the JS SDK?

@nikithauc

Can you please share the response with the headers that you are getting when you make a request to the Graph API through the JS SDK?

The headers available are: cache-control, client-request-id, content-type, request-id. But I have investigated and found that this is by design.

According to this article on Access-Control-Expose-Headers, there are headers that are exposed to the browser by default. They are listed in this article about CORS-safelisted response header

The Access-Control-Expose-Headers response header allows a server to indicate which response headers should be made available to scripts running in the browser, in response to a cross-origin request.

A CORS-safelisted response header is an HTTP header in a CORS response that it is considered safe to expose to client scripts. Only safelisted response headers are made available to web pages.

The Graph API exposes less headers than the API we hit to get the demo data. This is the reason the headers are less when a user is logged in.

Graph API exposed headers:
Access-Control-Expose-Headers: ETag, Location, Preference-Applied, Content-Range, request-id, client-request-id, ReadWriteConsistencyToken, SdkVersion, WWW-Authenticate

Proxy API exposed headers:
Access-Control-Expose-Headers: Cache-Control, Content-Type, Content-Encoding, Vary, Access-Control-Allow-Origin, Access-Control-Expose-Headers, Strict-Transport-Security, request-id, client-request-id, x-ms-ags-diagnostic, x-ms-resource-unit, OData-Version, X-FE-DATA

This means it would be possible to get all the response headers through an application that is not running in a browser


Resizing the window breaks the glare

When the windows is resized the glare height & width need to be recalculated.

@timothyachumba I totally forgot that, should be fixed now!

Wow @gijsroge! Really fast!
Great work by the way!
Take a look https://timothyachumba.com


How to handle accessibility issues for videos?

Currently the streaming video component isn't optimal for screenreaders.
Ref. Slack discussion https://app.slack.com/client/T02JL00JU/C01MU3H6G0Y/thread/C01MU3H6G0Y-1689857111.343759
and
https://app.zenhub.com/workspaces/energy-vision-5fb6386c578f1200222dd6c2/issues/gh/equinor/energyvision/1638
For discussion:

title - invisible on page, for accessibility
caption or not - visible or not?
description/alt text?
mark as decorative?
same options as for iFrame component?

setup a meeting with siteimprove clarifying how to handle these

suggestion from siteimprove is adding a simple caption:
  Captions: This is a beautiful video showcasing our products.

Thanks @padms - Let's give this a try :smile: Could the explanation be changed to "Use the alt text below to describe the video content (for screenreaders)."

@meols I have changed the description.


Lower the version requirement for the symfony/cache-contracts package

While investigating #545, I noticed that we are requiring symfony/cache-contracts:^2.4 while symfony/symfony:^4.4 requires symfony/cache-contracts:^1.1 (actually it replaces that package with symfony/contracts:^1.1). This makes it impossible to install sentry/sentry-symfony:^4.2 on a plain Symfony 4.4 installation (no Flex). ~However, I cannot understand why it works with sentry/sentry-symfony:4.1.3 though, since that version is the one where the composer.json requirement actually got changed~

thanks guys :+1:


Is there any way of disabling the creation of a new crop area?

Hello,
I want the user to just be able to move and resive the CropBox but not to be able to click and drag outside the initial CropBox and in this way to destroy the previous CropBox and create a new one.
I hope I explained it well.
Thanks for the awesome plugin!

Just set the dragMode option to 'move'.

I guess I scrolled past that. Thanks. Awesome plugin!


Temporary solution to remove failed fixup tasks from the fixup view

Solves https://github.com/sourcegraph/cody/issues/1088
Before(Turn on voice)
https://github.com/sourcegraph/cody/assets/11155207/81810737-31a5-424e-b654-c6278f13e76d
After(Turn on voice)
https://github.com/sourcegraph/cody/assets/11155207/a0e73968-fcd5-445a-80a7-431e23c95bfb
Answering followup questions
From @abeatrix
> IIRC FixupTask has a method for displaying error, or somewhere in fixupController 😀
That's true and the error is still gonna be displayed with this fix

IS this the perfect way to solve the problem?
I think a more broader solution which has full blown error handling scenarios with a lot of different forms of failure would be a much nicer solution but for now this solution works and handles the error pretty well. As folks build more the understanding of the error handling scenarios would be better and maybe then that can be pursued but this seems okay for now.
Test plan
Just do what the video says

CC @abeatrix @jdorfman

@arafatkatze approved to run, @abeatrix will have to do the rest. :)


How do you adjust lr and wd?

Hi,
Thanks so much for your great work!
I am confused about how you adjust the lr and weight_decay. In pretrain/utils/lr_control.py/lr_wd_annealing, I think lr and wd are only acquired and not changed.
Thank you!

in that function we modify the lr and weight_decay inoptimizer.param_groups, so it will acquire and change lr/wd in the same time.


Add Pipeliner.Do

Fixes https://github.com/go-redis/redis/issues/962#issuecomment-462442503

Maybe Do should be placed into Cmdable interface?


Better Layout quick switch

Description of the new feature / enhancement
Per monitor based control over the layout hotkeys. Using a hot key assigned a certain layout currently switches to said layout on all monitors. New fucntion would instead be able to both assign a certain hotkey for only a specific monitor, or if chosen so, switch all layouts.
Scenario when this would be used?
When wanting to switch the layout on only one of the multiple displays possibly plugged in.
Supporting information
No response

Hi @THEwabbit212, did I get it right that the layouts were changed on all monitors after you press a quick switch hotkey?

I see. That makes sense, on my home pc it did however change on both monitors, while on my laptop here it behaved like you said.
Thank you for the answer

I see. That makes sense, on my home pc it did however change on both monitors, while on my laptop here it behaved like you said.

Looks like a bug then. Could you please attach here a bug report from your home PC to help us investigate it?
You can generate it by the Report Bug tool in the systray.

/needinfo

actually, /reportbug


Added separate functions for query in create.go , update.go , delete.go

Modified create.go , delete.go , update.go . Added separate functions for query (GenerateCreateQuery , GenerateUpdateQuery, GenrateDeleteQuery ) .

@Jayesh333 you should've asked @atharva29 to squash all the commits into one.


Adding cognalys.com

I've added cognalys.com provides a new method of Mobile number verification / Two factor authentication for free

this is the logo
https://www.cognalys.com/static/logo/favi.png

Closing in favor of #947


fix typo in index page for zh-tw

Fix some Chinese typos in index.zh-tw.md

LGTM

LGTM

Please back port to v1.0


Remove nest_asyncio from 002_ApacheKafkaBroker and 003_LocalRedpandaBroker notebooks

We need to remove nest_asyncio.apply logig when starting the brokers in notebooks: ApacheKafkaBroker and LocalRedPandaBroker
After that, failing tests should show where we need to apply the nest_asyncio manually and not automatically in the broker


Droptimes are incorrect

Droptimes are either improperly calculated or are getting bad information from API.
To reproduce the issue:

Add an upcoming username to name_queue
Load the sniper
Compare time to snipe between NameMC and buckshot.

Names that are upcoming to claim on NameMC (few hours to drop) are already 'claimed' when attempting to setup buckshot.

Initialising...
Enter your gift code (press ENTER if you have already redeemed your gift code):
Measuring offset...
Your offset is: -18 ms.
Sniping Purpel in ~-26982 seconds | sniping at 2021-07-17 08:56:11 (utc).
Signed in to<EMAIL_ADDRESS>successfully.
Error: [SnipeGc] The name Purpel has already dropped.
Error: [SnipeGc] The name Purpel has already dropped.
Error: [SnipeGc] The name Purpel has already dropped.
Error: [SnipeGc] The name Purpel has already dropped.
Error: [SnipeGc] The name Purpel has already dropped.
Error: [SnipeGc] The name Purpel has already dropped.
Moving on to next name...

(The username is not claimable for another 3.25 hours, according to NameMC at time of posting)

After some investigation, it appears droptimes from https://drops.peet.ws (found in constants for the NameMC_API) are incorrect, which matches the data found in the log.
From https://drops.peet.ws/droptime?name=Purpel -
{"name":"Purpel","UNIX":1626512171,"searches":163,"updated":1626171432,"message":"'PiratSnipe on top!' -everyone"}
1626512171 converts to 2021-07-17 08:56:11 UTC, which matches buckshot.
NameMC says the name is available at<PHONE_NUMBER> which is 2021-07-17 19:50:57 UTC.
So, unfortunately the API currently used is providing incorrect information and the bot will not be able to make snipes.

Ah, I see. Well thanks for the testing, I'll try to ask peet bout that.

Changed api to one that mcsniperpy uses. Issue should be fixed.


Number of views is not correct

Thanks for the great library. Nevertheless when I do a search on: "Madonna Hung Up" I get these results:
{'channel': 'Madonna',
 'duration': '5:27',
 'id': 'EDwb9jOVRtU',
 'index': 0,
 'link': 'https://www.youtube.com/watch?v=EDwb9jOVRtU',
 'thumbnails': ['https://img.youtube.com/vi/EDwb9jOVRtU/default.jpg',
                'https://img.youtube.com/vi/EDwb9jOVRtU/hqdefault.jpg',
                'https://img.youtube.com/vi/EDwb9jOVRtU/mqdefault.jpg',
                'https://img.youtube.com/vi/EDwb9jOVRtU/sddefault.jpg',
                'https://img.youtube.com/vi/EDwb9jOVRtU/maxresdefault.jpg'],
 'title': 'Madonna - Hung Up (Official Music Video)',
 'views': 268}

It seems like the number of views (269 036 248) isn't parsed correctly. Seems like this line could be the culprit:
https://github.com/alexmercerind/youtube-search-python/blob/cdfd4ff16ef45a00c448983586b4fcc7cd8ef123/youtubesearchpython/videos__scripthandler.py
for character in self.pageSource[index+2].split()[0]:

@saturnus-ringar,
Okay... Let me see. I'll give you update soon.
Thanks for your feedback.

Hi @saturnus-ringar,
I'm unable to reproduce the issue you mentioned.
However, I might be able to help you, if you provide me a .txt document with string stored in self.page.
You can generate one with the following script:
search = SearchVideos("Madonna Hung Up", offset = 1, mode = "json", max_results = 20)
with open('log.txt', 'w', encoding = 'utf_8') as log:
    log.write(search.page)
print(search.result())

My search result is giving correct response, as follows:
{
    "search_result": [
        {
            "index": 0,
            "id": "EDwb9jOVRtU",
            "link": "https://www.youtube.com/watch?v=EDwb9jOVRtU",
            "title": "Madonna - Hung Up (Official Music Video)",
            "channel": "Madonna",
            "duration": "5:27",
            "views": 268876210,
            "thumbnails": [
                "https://img.youtube.com/vi/EDwb9jOVRtU/default.jpg",
                "https://img.youtube.com/vi/EDwb9jOVRtU/hqdefault.jpg",
                "https://img.youtube.com/vi/EDwb9jOVRtU/mqdefault.jpg",
                "https://img.youtube.com/vi/EDwb9jOVRtU/sddefault.jpg",
                "https://img.youtube.com/vi/EDwb9jOVRtU/maxresdefault.jpg"
            ]
        },
...

Give me some feedback according to the comment above. ❎ I'm closing this for now.
Feel free to reopen 😃!

Thanks for looking into this. Here is the txt-results:
https://pastebin.com/V3hkakK4
... I'm using Python 3.8.5.

Hi @saturnus-ringar,
Thanks for your information. Expect the issue to be fixed quickly.
Thankyou.

🎉 @saturnus-ringar,
Please try out the library from master of the repo.
Let me know if your issue gets resolved.

Yes, it works. The number of views is now 269103180. Thanks for the fix!

I've encountered an issue with the number of views. views end up as "LIVE". Here's how to reproduce the issue:
for result in json.loads(SearchVideos("Generation Underground Shooken to the Core", offset=1, mode="json", max_results=1).result())["search_result"]:             print(result["views"])


Securely erasing memory

Currently, there are a few aspects of this crate that can't be easily erased from memory:

temporary values and other stack-based values containing key material when creating private keys may be copied at will by the compiler
hkdf might use some temporary values as well

This library doesn't perform some of the more large operations to be able to sufficiently implement "stack bleaching", such as signing data with private keys. This library merely generates the key, so a library that uses this library might be more suited for stack bleaching.
My question is: is it even worth it to eliminate all temporary variables, or should people try to use stack bleaching until there is a new development with Rust and/or the LLVM that allows for the developer to indicate that the compiler should not make certain stack data persist longer than required?

There is more trouble in this regard in the initialization methods for the key_generator. It is also leaving some memory behind, but besides stack bleaching, I could add some members on the key_generator that contain the MAC key and the HKDF key and RNG seed, but I would also want to add something for the symmetric resource encryption key, which would mean that I would need to add the ResourceEncryptor as a generic parameter for the key_manager

It seems like the only way to do this without stack bleaching would involve having several members of the structs as Option<T>, and perhaps making a separate struct to simplify any sort of .unwrap() and .is_some() shenanigans. I wouldn't mind (much) doing this, but there are still some underlying crates that do not buffer their intermediate outputs... likely for a good reason, because it seems pretty tedious and imperfect. There's a lot of meticulous aspects of this, such as initialization. Calling Box::new(SomeStruct::new(...)) seems to only allocate the struct to the heap once the struct is returned from the new method. So to take that into account, the code might look something like this (kind of nasty):
#[cfg(feature = "boxed")]
type Boxed<T> = Box<T>;
#[cfg(not(feature = "boxed"))]
type Boxed<T> = T;

pub fn new(arr: &[u8]) -> Boxed<Self> {
    let mut s: Boxed<Self> = Boxed::new(Self {
        hkdf: Hkdf::from_prk(arr).expect("should be long enough"),
        hkdf_2: None,
        kdf_key: Default::default(),
    });
    s.hkdf.expand(b"level 2 kdf", &mut s.kdf_key);
    s.hkdf_2 = Some(Hkdf::from_prk(&s.kdf_key).expect("long enough"));
    s
}

Keep in mind that there would likely need to be a trait called Boxed that has a new method, or maybe a macro. Not entirely sure, but this seems like it would be nasty enough to consider stack bleaching instead. I tried to store intermediate values in a previous, unreleased version of this crate, and it got extremely hectic, especially once I had to start dealing with the Option<T> types.


[Doc Source]: how to delete volumes from a pool

Are you proposing new content, or a change to the existing documentation layout or structure?
I would like to propose you may add to the documentation how to delete volumes from a pool. I apologize in advance if this is already explained somewhere, but obviously I could not find it.
The reason for that is because the current supported provisioning is only thick, the available pool space could run out in some situations, and therefore it could be needed to remove some volumes that are not needed anymore.
What I just did is to delete the corresponding PVC and the PV using the regular kubectl, but when I checkout the volumes with the mayastor plugin (kubectl mayastor get volumes) the volumes are still there wasting space from the pool.
Thank you.

I have the same problem and no understanding of how to cleanup the orphan volumes.  In the process of deleting all resources in the mayastor namespace and detaching and wiping the disks!

Try to use mayastor-client in the pod. With that binary you are able to list all nexus and all children and that can be used for rebuilding degraded volumes as well.
/bin # ./mayastor-client  -b <IP_ADDRESS> pool list
NAME                        STATE       CAPACITY         USED DISKS
pool-on-openebs-test-02-san online<PHONE_NUMBER>48<PHONE_NUMBER> aio:///dev/vdd?uuid=ae169e36-2c3c-4559-bb8a-3785bcb2c7b4
pool-on-openebs-test-02     online<PHONE_NUMBER>416<PHONE_NUMBER>32 aio:///dev/vdc?uuid=768c1f01-4bfd-4618-a4cf-921a751a7116
/bin # ./mayastor-client  -b <IP_ADDRESS> nexus list
NAME                                         SIZE STATE  REBUILDS PATH
774ba995-9521-45dd-ae61-de188ee4e9dc<PHONE_NUMBER>0 online        0 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:nexus-774ba995-9521-45dd-ae61-de188ee4e9dc
49216324-cd59-4afd-9a93-3e16f1a2b70d<PHONE_NUMBER>0 online        0 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:nexus-49216324-cd59-4afd-9a93-3e16f1a2b70d
b9fee01a-7309-4e04-ba0f-861ea228aa08<PHONE_NUMBER>0 online        0 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:nexus-b9fee01a-7309-4e04-ba0f-861ea228aa08
70a57e2f-4a42-4461-9e44-a4e9a4002f6b<PHONE_NUMBER>0 online        0 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:nexus-70a57e2f-4a42-4461-9e44-a4e9a4002f6b
f690b066-6809-498d-808c-9d428c1ee09e<PHONE_NUMBER>0 online        0 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:nexus-f690b066-6809-498d-808c-9d428c1ee09e
68057349-a5ad-4c43-adb5-a1402dab9042<PHONE_NUMBER>00 online        0 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:nexus-68057349-a5ad-4c43-adb5-a1402dab9042
0807a310-a00d-4d3a-9a2f-8a4456927a45     52428800 online        0 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:nexus-0807a310-a00d-4d3a-9a2f-8a4456927a45
/bin # ./mayastor-client  -b <IP_ADDRESS> replica list
POOL                        NAME                                  THIN SHARE         SIZE URI
pool-on-openebs-test-03-san 0807a310-a00d-4d3a-9a2f-8a4456927a45 false  none     54525952 bdev:///0807a310-a00d-4d3a-9a2f-8a4456927a45?uuid=72a895eb-4925-4ec8-ae94-abe67bf746df
pool-on-openebs-test-03-san 30ab9ef3-f787-410b-a38a-1d828600ddc6 false  nvmf<PHONE_NUMBER>0 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=cf3bd1f9-2272-4819-9c1d-1ba238670190
pool-on-openebs-test-03-san f690b066-6809-498d-808c-9d428c1ee09e false  none<PHONE_NUMBER>0 bdev:///f690b066-6809-498d-808c-9d428c1ee09e?uuid=43320b71-83c1-4662-aea0-90938351d2f2
pool-on-openebs-test-03-san 176d5553-b525-4a46-989f-6b62d9af1483 false  none<PHONE_NUMBER>0 bdev:///176d5553-b525-4a46-989f-6b62d9af1483?uuid=5a49e2ee-7589-4648-92e2-372f76bdd8c6
pool-on-openebs-test-03-san 82f10ebd-6177-4e6f-ae1c-a393755f96dd false  none<PHONE_NUMBER>0 bdev:///82f10ebd-6177-4e6f-ae1c-a393755f96dd?uuid=db2e9bdd-6838-40fd-89e2-f9a59b1a5cb0
pool-on-openebs-test-03     b9fee01a-7309-4e04-ba0f-861ea228aa08 false  none<PHONE_NUMBER>0 bdev:///b9fee01a-7309-4e04-ba0f-861ea228aa08?uuid=f5cfe4f0-9cad-4f7b-97f4-9d982844cd94
pool-on-openebs-test-03     49216324-cd59-4afd-9a93-3e16f1a2b70d false  none<PHONE_NUMBER>0 bdev:///49216324-cd59-4afd-9a93-3e16f1a2b70d?uuid=ce09fdf8-7dde-4bca-b3f1-be4248eb7e1e
pool-on-openebs-test-03     70a57e2f-4a42-4461-9e44-a4e9a4002f6b false  none<PHONE_NUMBER>0 bdev:///70a57e2f-4a42-4461-9e44-a4e9a4002f6b?uuid=177c511c-1000-4cd9-ac18-19df73a11a5c
pool-on-openebs-test-03     774ba995-9521-45dd-ae61-de188ee4e9dc false  none<PHONE_NUMBER>0 bdev:///774ba995-9521-45dd-ae61-de188ee4e9dc?uuid=8c9607fd-1763-4778-bf98-43b2b6fdbe00
pool-on-openebs-test-03     68057349-a5ad-4c43-adb5-a1402dab9042 false  none<PHONE_NUMBER>00 bdev:///68057349-a5ad-4c43-adb5-a1402dab9042?uuid=fd08ebc9-d7be-4c71-9013-2dd6b398eac1
on node <IP_ADDRESS>
/bin # ./mayastor-client -b <IP_ADDRESS>  nexus children 30ab9ef3-f787-410b-a38a-1d828600ddc6
NAME                                                                                STATE
bdev:///30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=ad02bcea-b171-41d4-98c7-9d8b48469432                                        online
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=cf3bd1f9-2272-4819-9c1d-1ba238670190 faulted
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=bac9cc57-943a-47cb-a029-0a8aa0ac95ae faulted
/bin # ./mayastor-client -b <IP_ADDRESS>  nexus remove 30ab9ef3-f787-410b-a38a-1d828600ddc6 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=bac9cc57-9
43a-47cb-a029-0a8aa0ac95ae
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=bac9cc57-943a-47cb-a029-0a8aa0ac95ae
/bin # ./mayastor-client -b <IP_ADDRESS>  nexus children 30ab9ef3-f787-410b-a38a-1d828600ddc6
NAME                                                                                STATE
bdev:///30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=ad02bcea-b171-41d4-98c7-9d8b48469432                                        online
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=cf3bd1f9-2272-4819-9c1d-1ba238670190 faulted
/bin #
/bin # ./mayastor-client  -b <IP_ADDRESS>  nexus children 30ab9ef3-f787-410b-a38a-1d828600ddc6
NAME                                                                                STATE
bdev:///30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=ad02bcea-b171-41d4-98c7-9d8b48469432                                        online
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=cf3bd1f9-2272-4819-9c1d-1ba238670190 faulted
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=4225a123-10aa-445c-9d36-f6c5a13237e9 degraded
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=5fad4b54-aa95-4796-9d79-c815f7ef8ff1 degraded
/bin # ./mayastor-client -b <IP_ADDRESS>  nexus remove 30ab9ef3-f787-410b-a38a-1d828600ddc6 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=cf3bd1f9-2
272-4819-9c1d-1ba238670190
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=cf3bd1f9-2272-4819-9c1d-1ba238670190
/bin # ./mayastor-client  -b <IP_ADDRESS>  nexus children 30ab9ef3-f787-410b-a38a-1d828600ddc6
NAME                                                                                STATE
bdev:///30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=ad02bcea-b171-41d4-98c7-9d8b48469432                                        online
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=4225a123-10aa-445c-9d36-f6c5a13237e9 online
nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=5fad4b54-aa95-4796-9d79-c815f7ef8ff1 degraded
/bin #
/bin # ./mayastor-client  -b <IP_ADDRESS> rebuild state 30ab9ef3-f787-410b-a38a-1d828600ddc6 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=5fad4b54-
aa95-4796-9d79-c815f7ef8ff1
state
running
/bin # ./mayastor-client  -b <IP_ADDRESS> rebuild progress 30ab9ef3-f787-410b-a38a-1d828600ddc6 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=5fad4b
54-aa95-4796-9d79-c815f7ef8ff1
progress (%)
23
/bin # ./mayastor-client  -b <IP_ADDRESS> rebuild progress 30ab9ef3-f787-410b-a38a-1d828600ddc6 nvmf://<IP_ADDRESS>:8420/nqn.2019-05.io.openebs:30ab9ef3-f787-410b-a38a-1d828600ddc6?uuid=5fad4b
54-aa95-4796-9d79-c815f7ef8ff1
progress (%)
24
I was experimenting this in version 0.8.0, and it was working in that. However this is totally undocumented unfortunately, although this is a very important part of the system I believe.

We're seeing the same issue. Removing a PV via kubectl appears to not remove the underlying storage allocation based on what we're seeing in mayastor get volumes. This is all fine and well for a very short time, but after putting CI/CD processes into the cluster, things can get out of hand pretty quickly. There definitely needs to be some cleanup. I'm sure it can be done manually as mentioned above. However, manually interaction should not be required as the destruction of the data was already ordered via kubectl.

A question to those experiencing this issue - is the reclaimPolicy of the corresponding StorageClass set to Delete?
If so, then the PV created during dynamic provisioning should also carry the Delete policy, and that being the case, Mayastor assets (i.e. replicas) should be deleted automatically when the PVC (and hence PV) is deleted.  If that is not the case, then this is a bug that we should look into but it isn't behaviour which is currently seen during system testing of the current release.
As has been noted, setting the reclaimPolicy to anything other than Delete will lead to orphaned assets.  There is currently no benefit in setting this policy to Retain, since once the corresponding PVC and/or PV have been deleted there is no way to restore access to the volume from the underlying, orphaned replicas.  This is by design - Mayastor is currently predicated on dynamic provisioning and doesn't support static.
A later version of Mayastor (expected Q4 2022) will likely feature automated garbage collection of orphaned volumes (i.e. set to Retain when the PVC has been deleted).

Indeed the reclaimPolicy is set to "Retain". Thanks for the info

It's worth mentioning that mayastor was not removing the underlying volumes after the PV was deleted, not the PVC. So, sure, setting the reclaim policy to Retain is expected to keep the PV around after the PVC is removed. The expectation is that after deleting the PV (in this case, manually), the underlying volume would be destroyed. It is not.
Setting the reclaimPolicy to Delete does in fact fix the problem, but dynamic provisioning doesn't necessitate automatic deletion of underlying PVs. I don't understand how/why this would be a design feature as it results in a broken cluster state. I managed to clean it up manually by using the mayastor CLI and then going into the etcd cluster and deleting references and then restarting some of the mayastor pods (don't remember which ones).
Basically, it was a manual cleanup process that was fairly dangerous I'm sure. Just wanted to put my thoughts here for a future person that finds themselves in this same situation. Looking forward to support for Retained volumes. I don't want some SRE to accidentally delete a PVC for a major database and then have to go into a disaster recovery panic. There are a lot of places where running kubectl delete -f some-spec-that-was-previously-applied.yml may contain a PVC. For mission critical stuff, we would use a different class that requires an additional step to destroy the underlying PV. We can't do this with mayastor currently.

Looks like this is a known k8s bug:
https://github.com/kubernetes-csi/external-provisioner/issues/546
https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/2644-honor-pv-reclaim-policy/README.md
We've added Automatic GC on orphan volumes: https://github.com/openebs/mayastor-control-plane/pull/724
WA on current release, please restart the csi-controller pod


Doesn't <Appwrite {...config}> expose secrets?

Hey👋,
Just started using Appwrite recently. Nice project, by the way.
I might be wrong, but doesn't using the config in client side expose Appwrite secrets (like the project id)?
<Appwrite {...config}>

Would really appreciate a good response.
Thanks.

@Codes-Wizard good question. This config is intended to be used on client side, similar to Firebase. Hers's some documentation. If you want more security you can create an API key for server side usage inside your Appwrite console and use it inside .server.ts/js files in SvelteKit.

@Codes-Wizard good question. This config is intended to be used on client side, similar to Firebase. Hers's some documentation. If you want more security you can create an API key for server side usage inside your Appwrite console and use it inside .server.ts/js files in SvelteKit.

Ok. Thanks, by the way


Using Opacity in Tokens Creates Blank Variable [2]

Describe the bug
This is a recurring bug that has been reported previously in:

#2549
#2015

When you create a variable of a token that's using the alpha operation as a color modifier, it creates a blank #ffffff variable.
To Reproduce
Steps to reproduce the behavior:

Create a color token also using an opacity token as reference
Create variables
See error
Go back to the the token
Edit token
Click on Save
Error is resolved - variable is updated

Expected behavior
The user should not have to edit the token and then save it for it to update the variable to its correct value
Screenshots or Screencasts
Recording
JSON (optional)
Reach out to me for token-set

@keeganedwin Any update on this bug? it's giving me some grief, and I'm blocked on a major multi-brand (Pizza Hut, KFC and TacoBell) theming project

@tokendan will look into it and get back to you!

@six7 thinking this could be related to my comment in https://github.com/tokens-studio/figma-plugin/issues/1822. If we don't mix the opacity tokens with color tokens, we seem to have more consistent results.

@tokendan I have a feeling this is because our Opacity tokens are connected to Figma's layer opacity/transparency and not intended to be a part of a color variable which needs to be resolved.
A workaround could be to convert the tokens you are using in color tokens to a number token and see if that resolves the problem.

Thanks both, at least for now the bug has been broadly addressed with the rc9 release. My opacities aren't showing as white anymore.

Closing this ticket as it's fixed.


Add Proxy Support to Etcd & Kubernetes Quoin

Issue to remain open until we fix all the environment differences for running under a Proxy.

Issue moved to scipian/community #36 via ZenHub

Re-opening to track the PR's that were required for this work.

Tasks:

[ ]  Add environment variables for system, docker, and user #34
[ ]  Feed etcd module environment variables #39
[ ]  Add proxy and env file for Docker in bootstrap #41


Code Release

Hi,
This work is very interesting!
Are you planning to release the code? If yes, what is the approximate timeline for that?
Additionally, what is the maximum allowed video length for this method？
Thanks a lot!

Thanks!
There is no limit in video length.
We're working on the release, stay tuned :)

Quick question @omerbt - how can i set the video lenght to more than 200 frames though? i created a snippet with 300 frames (10 sec) and cant seem to set it higher than 200.... any help would be greatly appreciated! :) THANKS FOR YOUR HARD WORK!!!!

Thanks! There is no limit in video length. We're working on the release, stay tuned :)

any way to set more than 200 frames? possible on 3090? whats the max lenght on 24gb of vram in general?

Thanks! There is no limit in video length. We're working on the release, stay tuned :)

about  long video,The video reconstruction  Very poor, how should it be improved


Support for custom HTTP methods

HTTP is an open protocol that gets augmented by several extension
specifications. One of them, for example, is WebDAV, which brings new methods
like PROPFIND and SEARCH.

To be able to use REST-assured with any HTTP-based protocol (not only with the
base protocol's methods), it would be best to have an ".invoke(String)" method
added to com.jayway.restassured.specification.RequestSende (and an
implementation of that in RequestSpecificationImpl):

/**
 * Perform a custom request to a path. Normally the path doesn't have to be fully-qualified e.g. you don't need to
 * specify the path as <tt>http://localhost:8080/path</tt>. In this case it's enough to use <tt>/path</tt>.
 *
 * @param methodName The name of the custom HTTP method to invoke.
 * @param path The path to send the request to.
 * @param pathParams The path parameters.
 * @return The response of the request.
 */
Response invoke(String methodName, String path, Map<String, ?> pathParams);

Original issue reported on code.google.com by headcrashing on 10 Aug 2012 at 9:45

It's fine by me. If someone has the time to implement it I'll include it in the
next release.

Original comment by<EMAIL_ADDRESS>on 3 Sep 2012 at 9:36

Changed state: Accepted

Was already reported: http://code.google.com/p/rest-assured/issues/detail?id=184

Not yet fixed. Please do so, custom extensibility this is an essential HTTP
feature.

Original comment by<EMAIL_ADDRESS>on 3 Sep 2012 at 9:31

Original comment by<EMAIL_ADDRESS>on 3 Sep 2012 at 9:36

Added labels: Type-Enhancement
Removed labels: Type-Defect

Was this issue fixed? The main readme says that the supported methods are POST, GET, PUT, DELETE, OPTIONS, PATCH and HEAD. I would like to test a WebDAV server which uses methods such as PROPDIND, MKCOL, etc.

No this is not fixed yet. Feel free to help out and provide a pull request.


[FR] Ignore extraneous "entity" option

Checklist

[ x] I am running the latest version of the card
[ x] I checked if there isn't another feature request opened with the same request
[ x] I checked that the feature is not already available in the dev branch

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When trying to use the card with auto-entities card I see an error.
Here is the card:
type: custom:auto-entities
card:
  type: vertical-stack
unique: true
show_empty: true
card_param: cards
filter:
  include:
    - entity_id: sensor.cleargrass_1_*
      options:
        type: custom:apexcharts-card
        series:
          - entity: this.entity_id
        graph_span: 1h

First I talked with Thomas (https://github.com/thomasloven/lovelace-auto-entities/issues/234) and he proposed this FR.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Ignore extraneous "entity" option.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@RomRider could you have a look at this? I need this too.

You can disable configuration checks until I fix that with:
experimental:
  disable_config_validation: true

Thank you! This worked out great.


make dagger run use a random path for DAGGER_SESSION_URL

Signed-off-by: Marcos Lilljedahl<EMAIL_ADDRESS>

fixing lint errors :grimacing:


[Bug]: Error: At least one chain must be set before attempting to connect a wallet

Current Behavior
getting this on hot reload in a react app
Error: At least one chain must be set before attempting to connect a wallet
It works when I reload the page ok, just hot reload fails
Expected Behavior
shouldn't happen
Steps To Reproduce
use a react app and change code and save to hotreload
What package is effected by this issue?
@web3-onboard/core
Is this a build or a runtime issue?
Runtime
Package Version
2.6.0
Node Version
16
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Anything else?
No response
Sanity Check

[X] If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.

@sgehrman can you share your code base so we can reproduce?

@sgehrman would also be good to note, if you are using within a react project we have a React Hooks package that would make your implementation and usage more simple - https://www.npmjs.com/package/@web3-onboard/react

I'm using the react hooks.  I'm also on NextJS if that matters.
Can't easily share the code.

on hot reload, chains is [], on a normal load it has chains

hot reload calls init again with the same params, but the result has [] for chains
export const init = (options) => {
web3Onboard = Web3Onboard(options);
web3Onboard.state.get().chains == [] second call on hot reload.

return web3Onboard;

Looking at your code now, but it's so hipster and cool, I can't make any sense of it.
dispatch, svelte, actions, rxjs?  Too much complexity. It's probably failing in there somewhere.  Why not write normal code that works rather than this hipster fad overly engineered code?

Also, I'm unable to step though your code in Chrome.  No idea why, it won't auto format and it's all one line.  Build you code so ti's normal code that is debuggable.

trying this:
export const setupOnboard = () => {
// hack for hot reload
const existing = web3Onboard?.state.get();
if (existing && existing?.chains?.length > 0) {
console.log('init bypassed');
return;
}
init({ params... })
}
but that has a sideeffect:

MetaMask - RPC Error: The method "eth_selectAccounts" does not exist / is not available. {code: -32601, message: 'The method "eth_selectAccounts" does not exist / is not available.', data: {…}}
So, it almost works.  Let me know if that gives you a clue.

@sgehrman There's a lot here, let's focus this issue a little bit. To restate: The issue is with hot reloading and seeing the "At least one chain..." message?
If that is the case I have seen this behaviour before however, it seems like with the latest versions of the packages it has been resolved.
Can you try reproducing the issue using this demo?

As a side note: Let's make sure comments about the code are constructive. Comments like  "so hipster and cool" or "Build you code so it's normal code that is debuggable" are very vague. Let's practice good OSS etiquette and if you see where there could be an improvement please let us know but using more helpful comments, thank you!

We have the same problem in a Next.js/React app.
Onboard is initialized in a useEffect (because we load chain configs async).

@aaronbarnardsound this is not really solved, it is directly related with my comment in https://github.com/blocknative/web3-onboard/issues/888
I am using VUE and the hot reload (due to reactivity changes) is a big issue. I keep getting the same annoying popup and message:

What I should do to just remove this? I am trying to have persistence on refresh

Also seeing this issue

We will take a look into this issue and reopen if necessary. We will update here regardless. Thanks for raising


Mesh tiling and combining utilities

Describe the problem
Many projects require meshes be combined or split up (into tiles) for performance reasons. Writing code to do this can be a burden for developers.
Describe the solution you'd like
Provide scripts and processes to combine meshes (and materials) as well as split up large meshes into tiles which can be shown/hidden based on viewing perspective.
Describe alternatives you've considered
Don't provide these tools.
Additional context
See @Cameron-Micka for MeshTiler and MeshCombiner examples.

Issue found with submeshes to fix.


fix: WARN  [vite:css] start value has mixed support, consider using flex-start instead

🐛 The bug
WARN  [vite:css] start value has mixed support, consider using flex-start instead
replace justify-content: start; to justify-content: flex-start; in view/Main.vue
🛠 To reproduce
add Nuxt Devtools
🌈 Expected behavior
This error takes up a lot of space in the console
[1]  WARN  [vite:css] start value has mixed support, consider using flex-start instead
[1] 61 |    transform: translate(-50%, -50%);
[1] 62 |    display: flex;
[1] 63 |    justify-content: start;
[1]    |     ^
[1] 64 |    overflow: hidden;
[1] 65 |    align-items: center;

ℹ Additional context
No response

Resolved via https://github.com/nuxt/devtools/pull/369


glTexBuffer not implemented?

I need glTexBuffer.
Should I implement it in GL.Objects.Buffers  as:
procedure Texture_Buffer (Target : Buffer_Target; Format : GL.Pixels.Internal_Format;
                          Object : Buffer'Class);

glTexBuffer only works with GL_TEXTURE_BUFFER, so I would implement it something like this:
type Texture_Buffer_Target (<>) is limited new Buffer_Target with private;

--  ...

procedure Attach (Target : Texture_Buffer_Target; Format : GL.Pixels.Internal_Format; Object : Buffer'Class);

--  ...

Texture_Buffer            : constant Texture_Buffer_Target; --  changed type


Upgrade projects to GAX v3 and fix breakages

This now builds until it hits Google.Cloud.Logging.Log4Net. I don't expect that to be hard to fix, but I've run out of time for now (and the PR's getting big!)
If you'd prefer me to split this into multiple PRs, I'm happy to do so - suggestions for the coarseness would be welcome. (Likewise, if you're happy to review this as-is, are you happy for me to keep working on extra APIs and add more commits to the PR, or create a new PR?)

I've just realized this will all fail until I've created another PR for GAX, mind you - I'll do that first thing on Monday.

This now builds and all unit tests pass. I'll run all the integration tests when I can.

Added a final commit addressing review comments - PTAL.

Final commit LGTM


Images on "The Doki Theme Update" tab do not appear to be scaled correctly

Describe the bug
It appears that the images shown on the Update tab of the theme (automatically opened when you install or update the theme) do not correctly scale to the width of the tab
To Reproduce

Open the Update tab on a resolution lower than 1080p.

Expected Behavior
The image is scaled to the width of the tab, so you don't have to use the scroll bar at the bottom to see the image.
Environment
JetBrains Rider 2021.2.2
Build #RD-212.5284.64, built on October 8, 2021
Licensed to Rider Evaluator
Expiration date: January 7, 2022
Runtime version: 11.0.12+7-b1504.28 amd64
VM: Dynamic Code Evolution 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
.NET Framework 4.0.30319.42000
GC: G1 Young Generation, G1 Old Generation
Memory: 1500M
Cores: 4
Registry: debugger.new.debug.tool.window.view=TRUE, ide.tree.horizontal.default.autoscrolling=FALSE, ide.tooltip.showAllSeverities=TRUE, ide.mac.bigsur.alerts.enabled=TRUE, show.diff.preview.as.editor.tab.with.single.click=TRUE, ea.enable.developers.list=FALSE, parameter.info.max.visible.rows=10, ide.win.file.chooser.native=TRUE, ide.mac.file.chooser.native=TRUE, search.everywhere.pattern.checking=FALSE, performance.watcher.sampling.interval.ms=200, ide.borderless.tab.caption.in.title=FALSE, awt.file.dialog.enable.filter=FALSE, debugger.show.values.use.inlays=TRUE, performance.watcher.unresponsive.interval.ms=1000, vcs.enable.add.ignored.directories.to.exclude=FALSE, ide.allow.merge.buttons=TRUE, use.winp.for.graceful.process.termination=FALSE, ide.tooltip.initialDelay=0, ide.require.transaction.for.model.changes=FALSE, ide.debug.in.title=TRUE, rdclient.asyncActions=false
Non-Bundled Plugins: com.intellij.resharper.HeapAllocationsViewer (2021.2.0), com.jetbrains.rider.android (212.5284.64), io.acari.DDLCTheme (21.0.0)
Screenshots

Ahh man, that's what it looks like for other people.......dang it.
It's supposed to look like this 😭

Does https://doki-theme.unthrottled.io/ not resolve for you, or take a really long time to load?

The page works as expected.
TBH the only thing I did was install Rider (cuz doki-theme/doki-theme-visualstudio#31, ha!), install The Doki Theme and press the Restart button for the extension to install and apply. Then I just changed the theme to Cinnamon and that was it.

By the way, how can I open the tab manually?

By the way, how can I open the tab manually?

Help -> Find Action
Enter Show Update Notification

The page works as expected.

Okay, well I'd like to know why the fancy page is not working, but I also should fix the plain page. Could you search through the logs (or provide the logs for me, Help -> Show Log in Explorer), looking to see if there is any Timeout stuff in there.

I don't see an option called "Show Log in Explorer" in the Help menu. Maybe you are talking about "Collect Logs"?

Lol, wups.  I normally do:
Help -> Find Action
Enter Show Log in Explorer
I thought there was that option in the dropdown.

Open Log in Editor will open the containing folder for you, as well.
If you don't want to provided the log (cause of privacy stuff) I'm looking for things related to timeouts.

I don't have that option:

How about trying:
Help -> Find Action...
Enter Show Log in Explorer ?

Okay, so I spent a bunch of time refactoring the website to be smaller and load quicker. I've done everything up to the point of server side rendering to get the best user experience. I am going to update the fallback page (the original one in this issue) but I'd like to know if my outside fix worked.
@justalemon and/or @Dragon-0609 could you do me a favor and:

Go to Help -> Find Action
Enter Show Update Notification

And tell me if you get a page that looks like this 👇

Please and thank you!

Works well.


Allow for a Global to be accessed from generateTitle or generateDescription [SEO Plugin]

Link to reproduction
No response
Payload Version
n/a
Node Version
n/a
Next.js Version
n/a
Describe the Bug
It would be great if it was possible to access data from a Global via the generateTitle or generateDescription functions when using the SEO Plugin.
doc and locale are currently available, having access to a global (or payload in general?), where information such as a company name or tagline may be included would be helpful as part of automatically generated titles/descriptions.
cc @paulpopus
Reproduction Steps
n/a
Adapters and Plugins
No response

After this PR is released you'll be able to use the req.payload local API to fetch whatever you need https://github.com/payloadcms/payload/pull/7711

Appreciate you @paulpopus!


Nodes delete resources should use /v2 resources not /v1

When deleting nodes currently it uses direct ssh connection to stop, should use /v2 .
Possible duplication of resources. Need to check.

Fixed in issue #171


Google tag manager module script on head

What problem does this feature solve?
Hello, i really appreciate what it does google-tag-manager package and i have a question and feature request about it.
Does it have an option to put the gtm script in body (body: true) or we have to modify the package on node_modules directly?
// Add google tag manager script to head  @nuxtjs/google-tag-manager/index.js line 47   this.options.head.script.push({     src: (options.scriptURL || '//www.googletagmanager.com/gtm.js') + '?' + queryString,     async: true,     body: true   })
It will be nice to add this as an option if it does not exist.
I have another question about script, when I add (body: true) in @ nuxtjs / google-tag-manager / index.js line 47. the script is added at the end of the body scope but the script https: // www. google-analytics.com/analytics.js appears in the head, how can i move it to the body?

This feature request is available on Nuxt community (#c9297)

Please open an issue in https://github.com/nuxt-community/modules/ :relaxed:


Release 2.0.0-rc.2

What's Changed
Fix issue with npm release
Full Changelog: https://github.com/connectrpc/connect-query-es/compare/v2.0.0-rc.1...v2.0.0-rc.2

The original release somehow missed changes to peer dependencies. The code is there, just need to do another release.


Add a How To Contribute section in README.md

As a beginner with perl myself I struggled a little bit on how to set up this project for development from the source. Took me a while to figure what some files were there for and how to install and run the tests. I think it is a good a idea to have a How To Contribute section on open sources projects which makes outsiders to the project start contributing easily.

Thanks your PR.
I added "without installing section", and added to POD in Slack/RTM/Bot.pm because I'm using Minila authoring tool (which automatically generate README.md from POD).

Oh I see. Cool, didn't know about Minila. Thank you very much! :-)


Feature: Scheduling system

Rework is needed in regards to the last editions scheduling system in the management view.
Requirements: In a way something like a teams/outlook calendar

Closed in #435


ServicesAllowedList Supported Versions

The document does not clearly state what versions of Windows 10 support the ServicesAllowedList feature.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9596a57e-365e-2809-1f8d-8aebbda5bc36
Version Independent ID: 4a287709-2466-93eb-cc2f-9f7566277abb
Content: Policy CSP - Bluetooth
Content Source: windows/client-management/mdm/policy-csp-bluetooth.md
Product: w10
Technology: windows
GitHub Login: @ManikaDhiman
Microsoft Alias: dansimp

@officedocsbot assign

I seen Bluetooth group policy settings in windows 10 pro 1809 or later editions.
normally specified article csp , will support server 2012 or sever 2016 or sever 2019.
for client Windows10 pro or enterprise or education

Hi @terickson81 we appreciate your feedback. Thank you.
@ManikaDhiman is this something that you can add to the documentation? Can you please confirm that ServicesAllowedList supports Windows 10 Home, Pro, Enterprise, and Education for desktop as well as Windows 10 Mobile? Kindly let us know. I can also request one of the freelance tech writers to check and create a pull request, but you're the expert here, so I've opted to ask you first. Thank you.

Thanks @jvsam,
It would be helpful to know the editions (Home, Pro, Enterprise) as well as the build releases (1709, 1803, 1809, 1903) that supports the feature.

Hi @jvsam, product team confirmed that the SKU table under Bluetooth/ServicesAllowedList policy description provides the correct SKU info. And, this policy was added in Windows 10, version 1511. Hope this answers all your questions. Thanks!

Thanks @ManikaDhiman and @jvsam! We've been trying to disable the Bluetooth file transfer service for a long time, and hoping this feature will provide that option.

Hi again @terickson81, this documentation has been updated (Refer: commit 829aac7 added by @ManikaDhiman), and it now includes Windows 10, version 1511. See https://docs.microsoft.com/windows/client-management/mdm/policy-csp-bluetooth, Bluetooth/ServicesAllowedList section. As confirmed, the SKU information is also accurate. We will now close this issue. Thank you for your feedback to help improve the contents of this documentation and for being part of the Microsoft Docs community!
Hi @ManikaDhiman your assistance is appreciated. Thank you.

@officedocsbot close


Bug

I have among us v2020.10.22s, but i can't open the injector. Every time I open, it just closes right away.

Because you are not supposed to open the injector but the AmongUsCheatClient.exe and if it’s not there check your antivirus

Could u send me the exact link to the AmongUsCheatClient.exe cause there are several

There is not link just download in the release page

0.0.3-beta2 this?

Sorry I didn’t see but you have 10.22s so you can’t use the client yet

When are you working on an update? @Escartem

When I have time but it will come out as soon as possible


Seems like the quay oauth token is not referenced or injected correctly

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What happened:
In the periodic https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/logs/periodic-containerdisks-push-nightly/1522033424607481856 I see:
CSRF token was invalid or missing.

As a consequence repo descriptions will not be uploaded (but publishing images continues to work).
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
common-templates version:
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/kind bug

The injected quay auth token was no longer valid.
It will be fixed by this PR https://github.com/kubevirt/secrets/pull/54.

/cc @dominikholler

@0xFelix Looks like it still failing: https://prow.ci.kubevirt.io/?job=periodic-containerdisks-push-nightly

@enp0s3 It is fixed now
https://prow.ci.kubevirt.io/job-history/gs/kubevirt-prow/logs/periodic-containerdisks-push-nightly

@davidvossel do you have the permissions to close this issue?

/close


Create init.py

closes #7

I'm going to test this later to see if the problem is fixed.

ok

i already fixed the problem??????

No this pull request has the code in it to fix the repo.  When someone wants to add code to your repo they will open a PR.  You can look through their code and if you like it you can press the merge button to add it to your repository.

The code seems to be fixed now and the imports work.

alright


Spot Exchange: Error handling

Spot Exchange should improve error handling (or at least a friendly error view) for failed transactions. For example, at times swapping USDC to sUSD results in the following error:

Deliverables

Make sure common exchange errors are displayed in a human-readable format

related: https://github.com/Kwenta/kwenta/issues/1298


SPARQL query does not show editions

The bug
The Query Browser with SPARQL does not show any changes in the editor after typing.
Affects Nexus Fusion
To Reproduce

Go to 'https://bbp.epfl.ch/nexus/web/'
Click on 'Admin'
Select an Organization, for example 'bbp'
Select a project, for example 'neocurator'
Click on 'Query'
Select 'SPARLQ' from the options displayed on the left
Try editing the query
See the error

Expected behavior
Trying to edit the query, the editor for the query does not change, it seems like nothing was added, but all the changes appear only when the Execute SPARQL query bottom is used.

Fixed in https://github.com/BlueBrain/nexus-web/pull/1125


Validation - ford over intermittent stream

https://github.com/openstreetmap/iD/issues/6213
Here is an example where the ford exists but the validation still shows an error - lots of them in Timor Leste
https://www.openstreetmap.org/edit?editor=id#map=18/-8.22725/125.60061

Sneaky missing ford just out of view....


[sw/tests] Mark pwrmgr_random_sleep_all_reset_reqs_test broken in sival ROM_EXT

This test also seems to be part of issue #21706, so this commit marks it as broken in sival ROM_EXT.
This should fix the currently failing CI checks on master.
Examples of this test failing in CI:

https://dev.azure.com/lowrisc/opentitan/_build/results?buildId=143751&view=logs&jobId=6d7ef521-d3a1-575b-de1b-a7342dcf1a8e&j=6d7ef521-d3a1-575b-de1b-a7342dcf1a8e&t=5fbf7d75-9dee-5f42-7084-95893df8eb52
https://dev.azure.com/lowrisc/opentitan/_build/results?buildId=143812&view=logs&jobId=6d7ef521-d3a1-575b-de1b-a7342dcf1a8e&j=6d7ef521-d3a1-575b-de1b-a7342dcf1a8e&t=5fbf7d75-9dee-5f42-7084-95893df8eb52

TODO (post merge, if this gets merged)

[ ] Add pwrmgr_random_sleep_all_reset_reqs_test to the list in #21706.

A slightly different, but very similar test pwrmgr_sleep_all_reset_reqs_test is failing for my PR.
The log shows very similar symptom to the ones you posted, i.e. it stuck in a reset loop forever.
Perhaps it makes sense to update both tests to be broken?

SGTM, though I think @pamaury  and @jwnrt should chime in as well.
Also, in this PR the non-(SiVal ROM_EXT) test aon_timer_wdog_lc_escalate_test_fpga_cw310_rom_with_fake_keys fails with apparently the same symptoms -- why could that be?

If we've seen it fail in at least one CI run for an unrelated PR then I think we should disable it. Given it's sharing code with another test we're marking as broken, this seems appropriate. The original author can fix them up and re-enable them once ready.

//sw/device/silicon_creator/manuf/skus/earlgrey_a0/sival_bringup:cp_provision_fpga_cw310_sival and //sw/device/silicon_creator/manuf/skus/earlgrey_a0/sival_bringup:ft_provision_fpga_cw310_sival seem to suffer from the same problem, see https://dev.azure.com/lowrisc/opentitan/_build/results?buildId=143850&view=logs&jobId=5011a995-22d7-5073-e1ce-26fc382a8885&j=5011a995-22d7-5073-e1ce-26fc382a8885&t=875997a6-7e2b-594d-05e6-ce6a085f3383. I'm adding them as well

Actually these are non-ROM_EXT SiVal tests, so potentially a separate issue? Not adding them to this PR for now.

//sw/device/tests:aon_timer_wdog_lc_escalate_test_fpga_cw310_rom_with_fake_keys in CW310 ROM Tests fails consistently but that's also the case in other PRs. I'm proceeding with the merge since this PR should improve CI state on master.


[SPARK-28459][SQL] Add make_timestamp function

What changes were proposed in this pull request?
New function make_timestamp() takes 6 columns year, month, day, hour, min, sec + optionally timezone, and makes new column of the TIMESTAMP type. If values in the input columns are null or out of valid ranges, the function returns null. Valid ranges are:

year - [1, 9999]
month - [1, 12]
day - [1, 31]
hour - [0, 23]
min - [0, 59]
sec - [0, 60]. If the seconds argument equals to 60, the seconds field is set to 0 and 1 minute is added to the final timestamp.
timezone - an identifier of timezone. Actual database of timezones can be found there: https://www.iana.org/time-zones.

Also constructed timestamp must be valid otherwise make_timestamp returns null.
The function is implemented similarly to make_timestamp in PostgreSQL: https://www.postgresql.org/docs/11/functions-datetime.html to maintain feature parity with it.
Here is an example:
select make_timestamp(2014, 12, 28, 6, 30, 45.887);
  2014-12-28 06:30:45.887
select make_timestamp(2014, 12, 28, 6, 30, 45.887, 'CET');
  2014-12-28 10:30:45.887
select make_timestamp(2019, 6, 30, 23, 59, 60.5)
  2019-07-01 00:00:00.5

Returned value has Spark Catalyst type TIMESTAMP which is similar to Oracle's TIMESTAMP WITH LOCAL TIME ZONE (see https://docs.oracle.com/cd/B28359_01/server.111/b28298/ch4datetime.htm#i1006169) where data is stored in the session time zone, and the time zone offset is not stored as part of the column data. When users retrieve the data, Spark returns it in the session time zone specified by the SQL config spark.sql.session.timeZone.
How was this patch tested?
Added new tests to DateExpressionsSuite, and uncommented a test for make_timestamp in pgSQL/timestamp.sql.

Test build #107970 has started for PR 25220 at commit 020eb71.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13078/
Test PASSed.

Great! Thank you, @MaxGekk !

Test build #107970 has finished for PR 25220 at commit 020eb71.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Test build #107995 has started for PR 25220 at commit f526b6e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13104/
Test PASSed.

Test build #107995 has finished for PR 25220 at commit f526b6e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Could you rebase this PR, @MaxGekk ? Thanks!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13150/
Test PASSed.

Test build #108042 has started for PR 25220 at commit 7350951.

@dongjoon-hyun Thank you for your review. Just in case, I have implemented make_timestamp without explicit time zone as it is required by the JIRA ticket. To support passing time zones to the functions, need to add 7th parameter to the expression. I am traveling now, will come back to the PR shortly.

Test build #108042 has finished for PR 25220 at commit 7350951.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Thank you for informing that. Have a safe travel!

Do we need to support this case?
postgres=# select make_timestamp(2014, 12, 28, 06, 59, 60);
   make_timestamp
---------------------
 2014-12-28 07:00:00
(1 row)

Test build #108097 has started for PR 25220 at commit 4b93ad1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13205/
Test PASSed.

Test build #108097 has finished for PR 25220 at commit 4b93ad1.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class SeptenaryExpression extends Expression

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13262/
Test PASSed.

Test build #108160 has started for PR 25220 at commit c7cdf11.

Test build #108160 has finished for PR 25220 at commit c7cdf11.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

@dongjoon-hyun @wangyum Please, take a look at the PR one more time.

Sure, @MaxGekk !

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13364/
Test PASSed.

Test build #108262 has started for PR 25220 at commit c7cdf11.

Test build #108262 has finished for PR 25220 at commit c7cdf11.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Test build #108280 has started for PR 25220 at commit 68dafdd.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13380/
Test PASSed.

Test build #108280 has finished for PR 25220 at commit 68dafdd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13396/
Test PASSed.

Test build #108298 has started for PR 25220 at commit cfb8ce1.

Test build #108298 has finished for PR 25220 at commit cfb8ce1.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108298/
Test FAILed.

jenkins, retest this, please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13410/
Test PASSed.

Test build #108313 has started for PR 25220 at commit cfb8ce1.

Test build #108313 has finished for PR 25220 at commit cfb8ce1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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


Handle NewsFeedView networking errors

Call LDTMessage for any HTTP / no connection errors.

This is definitely lower priority, as React doesn't output errors in production mode -- so nothing really breaks, it just looks like there are no updates. (In development mode, you get a red screen of death).


Add option for requirejs global option

I am using jshint with my requirejs application. Everytime, I parse my code it gives me error that "require" and "define" are not defined. One way to overcome this is to add "/*global define:false */" at the top of every module which is cumbersome. Therefore, would be great to add an option in jshint so that it could be set to true or false to overcome this error.

Since there are already several library-specific configuration options for JSHint that add predefined variables, how about one for AMD that adds 'define' and 'require'?

Technically speaking, an environment option for AMD would only add define (require being a RequireJS-specific extension). In that case, there isn't really much saved from a dedicated option. There may be slightly more benefit to a "requirejs" environment option, but we're discouraging library-specific extensions and really only maintaining the current ones for backwards compatibility.

(require being a RequireJS-specific extension).

The require global variable is part of the AMD spec:

This specification reserves the global variable "require" for use by module loaders. Module loaders are free to use this global variable as they see fit. They may use the variable and add any properties or functions to it as desired for module loader specific functionality. They can also choose not to use "require" as well.

It's certainly mentioned there, but that's about as non-committal as spec language can get. Because a loader might not define require globally (as is the case with curl.js, for example), it would be inappropriate for JSHint to insert require into the list of pre-defined globals for such cases.

It's certainly mentioned there, but that's about as non-committal as spec language can get.

This should not be about one's opinion on the commitment of the AMD spec. Your defense of not adding an amd option seems to be based on an incorrect understanding of which globals the AMD spec reserves:

Technically speaking, an environment option for AMD would only add define (require being a RequireJS-specific extension). In that case, there isn't really much saved from a dedicated option.

It would beneficial for JSHint to have a standard that one can consult in order to evaluate future decisions against. For example: "Must reserve more than 2 globals" is a requirement that could be used.


double-beep: Watch ^today\W*offer

double-beep requests the watch of the watch_keyword ^today\W*offer. See the MS search here and the Stack Exchange search here.

^today\W*offer has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


675: Return raw response if the parsing fails

This commit includes:

Fix for #675
Test to verify the code change.

@reinaldo13 this looks good on the client side. Could you add another commit making the corresponding change to the server side code with a test as well?

@focusaurus: sure! Not a problem. I can get this done within the next couple of days.

@focusaurus: i just added the corresponding change to the server side code + test. Feel free to review when you get a chance. Thanks!

Well done. Thank you.


Ensure null, defaults and references are used on alter table

For @elixir-lang/ecto-adapters,

[x] MySQL
[x] PostgreSQL
[ ] MSSQL
[x] SQLite
[x] MongoDB

There were some bugs when generating modify clauses in migrations for PostgreSQL and MySQL so you may have inherited those too. To improve this, I have added integration tests and I have added some unit tests too.  All you need to do is to update those 3 tests in your suites and pass the integration tests and you should be good to go:

https://github.com/elixir-lang/ecto/blob/f8f8b875fb6e4d353d8f3890f35787c5f206bb50/test/ecto/adapters/mysql_test.exs#L437

https://github.com/elixir-lang/ecto/blob/f8f8b875fb6e4d353d8f3890f35787c5f206bb50/test/ecto/adapters/mysql_test.exs#L459

https://github.com/elixir-lang/ecto/blob/f8f8b875fb6e4d353d8f3890f35787c5f206bb50/test/ecto/adapters/mysql_test.exs#L504

MongoDB does not support null constraints, defaults, or references

SQLite: https://github.com/jazzyb/sqlite_ecto/commit/4361e211c4e30eea768d53d35bcd253dde9183dc

This has been handled along side the constraints for me.
MSSQL: livehelpnow/tds_ecto@5bd6b2a97e20fd5627d139d268e37eb4f6434a48


F2P-47: cypress e2e test template and docker compose update.

What
Added cypress as part of docker-compose. At the moment there are a few blank tests.

new job in docker/docker-compose.yaml
a few tests to confirm that each react service is available and placeholders
updated .gitignore

TODO

[ ] - update start.sh to stop if cypress fails or notify

The README could have a small section on cypress


optional referrer

Coverage increased (+0.3%) to 92.523% when pulling f91f579fccec2401676308e3aac95b6305178809 on optionalReferrer into 6caa0d7883cfb463b63605ba7827316c6dd20c0f on master.

Coverage increased (+0.3%) to 92.523% when pulling f91f579fccec2401676308e3aac95b6305178809 on optionalReferrer into 6caa0d7883cfb463b63605ba7827316c6dd20c0f on master.


fix(sec): upgrade org.springframework.boot:spring-boot-autoconfigure to 3.0.7

What happened？
There are 1 security vulnerabilities found in org.springframework.boot:spring-boot-autoconfigure 2.5.7

CVE-2023-20883

What did I do？
Upgrade org.springframework.boot:spring-boot-autoconfigure from 2.5.7 to 3.0.7 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
How can we automate the detection of these types of issues?
By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.
The specification of the pull request
PR Specification from OSCS

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Resolved at : https://github.com/pinpoint-apm/pinpoint/issues/10092


fix: extract transtion manager to fix some bug

Summary

fix different connections that affect each other.
only save when clicking the button. (it's saved when inputting)
Fix the cursor will jump to the end of the text when inputting

@likyh Thanks for the PR, as we discussed there are some very valuable changes proposed here, I especially like the addition of the Transformation Manager Hook, that will be useful in the future for better encapsulation and reduce the coupling concerns you raised earlier. Since my last service pack 1.0 PR for UI has resolved a few of the key issues that this ticket originally aimed to fix, we'll hold on merging for now.
We will collaborate on incorporating some of these ideas in a future ticket when the transformation logic is extracted.


fix Package.activateConfig is deprecated

This PR will fix the deprecation warning Package.activateConfig is deprecated

add new version and require atom >= 1.0.0
change the way the config is set
Update .travis.yml
add sudo required
add config schema
fix naming bug

This closes #66

I have added travis ci. You might want to do this also in your repo

Thanks for your contribution! Not sure if we want to add travis right now, would it be too much work to split that into a separate PR?

erm ... does it hurt just to leave it inside? I mean it's just the .travis.yml file - if you really don't want it I will simply remove it in this PR

the .travis.yml file is now in .gitignore. Feel free to add a .travis.yml file if you wish and remove the entry in .gitignore

just realised, that the version in atom is 0.3.2, I made a 0.3.3 but the releases here do not have these versions. Imho this should be fixed also ... simply create a tag 0.3.3 before you make a new release ;-)

The thing with the version is that the tool used to push a package to the atom repo (apm) automatically increases the version number + tag with that version.

ah ok I understand. Funny ;-). Anything left to do here for me with the PR?


PowerShell module doesn't cancel download & installation with Ctrl-C

Brief description of your issue
When I press Ctrl + C, I expect that the package download & installation would be cancelled by PowerShell module. That is not the case as both continue silently in the background without user's knowledge. The svchost process continues to download the file and the module initiates the usual installation flow after the download finishes. Observe in the short 40sec video below (the video is sped up):
https://github.com/user-attachments/assets/945a8231-8851-4da3-8f07-34f043a65758
Steps to reproduce
Try an Upgrade-WinGetPackage command and press Ctrl + C when the package is being downloaded
Expected behavior
Package download and installation to be cancelled
Actual behavior
Download and installation continues as normal
Environment
~ Get-Module Microsoft.WinGet.Client | Select Version
Version
-------
1.9.25190

[Policy] Issue-Bug
[Policy] PowerShell

Same here.


Fix compile_live when no flags are specified & add option to specify default flags"

I'm getting the following error when using the compile_live without specifying any flag, so this PR fixes it.
Error detected while processing BufWritePost Autocommands for "<buffer=1>":
Error executing lua callback: ...rt/compiler-explorer.nvim/lua/compiler-explorer/init.lua:146: attempt to concatenate upvalue 'flags' (a nil value)
stack traceback:
        ...rt/compiler-explorer.nvim/lua/compiler-explorer/init.lua:146: in function <...rt/compiler-explorer.nvim/lua/compiler-explorer/init.lua:142>

Another thing it does is adding an option to specify default compiler flags, I use a few flags by default and it would be nice to have them show up by default rather than typing them continuously, let me know if you want me to revert it if you don't like it

Thanks for opening this PR. I am fine with adding the compiler_flags option. I was also thinking about  adding an option for changing the event on which a new compile is triggered after :CECompileLive (ex: TextChanged instead of BufWritePost). Would you like something like that?

Yeah, that could be an option, the only problem I see is setting the event TextChangedI which will print alert.error("Could not compile code with compiler id %s", args.compiler) until we finish writing a correct expression, the BufWritePost seems to work pretty well for my usage
Thanks again for the plugin!


Error while setting up network

I'm trying to set up the network part.
I ran docker-compose -f docker-compose-e2e-template.yaml up but I receive the following errors:
ca_peerImporterOrg              | Error: File specified by 'tls.keyfile' do
t exist: /etc/hyperledger/fabric-ca-server-config/IMPORTER_CA_PRIVATE_KEY
ca_peerExporterOrg              | Error: File specified by 'tls.keyfile' do
t exist: /etc/hyperledger/fabric-ca-server-config/EXPORTER_CA_PRIVATE_KEY
ca_peerRegulatorOrg             | Error: File specified by 'tls.keyfile' do
t exist: /etc/hyperledger/fabric-ca-server-config/REGULATOR_CA_PRIVATE_KEY
Did anyone have the same issue? How to solve this?
I just need to get the app running without any modification.
Thanks in advance!

What platform are you running this on? (The default code and instructions are for Linux Bash, though there are instructions given in the book for Macs too.)  If you are running on a bash shell in Linux, you should not get the above error. If it's a Mac, change the code based on what's in the book. If it's anything else, you'll just have to figure out how to make the substitutions. See (and adapt) the code in network/trade.sh.

Should be fixed with https://github.com/HyperledgerHandsOn/trade-finance-logistics/commit/da0d715c9c22b989a0e5da20da496068652b92f7


Request: add subject CN for client certificates

For server authentication, SAN DNS is what is required. However, many TLS servers that perform client authentication (mutual TLS) use the subject CN in the client certificate as the identity. An example is Mosquitto (see https://mosquitto.org/man/mosquitto-conf-5.html and use_identity_as_username).
I read the discussion in #205. However, I would argue that the situation is different for client certificates. There are common servers and configurations that do not work without the CN in client certificates. Also, TLS clients do not necessarily correspond to DNS names in the way TLS servers do, but may be apps or people (for a person the email address is already supported).

Hi.
This is a must for me. As it is now, I can't seem to be able to generate a client cert that would actually be usable with PgSQL, as PgSQL uses CN to identify users. mkcert certs don't have a CN...

I understand that this is a real need, but I think part of mkcert's role in the ecosystem is to encourage movement towards modern usage. Applications should use DNS, IP, URL, or email SANs on client certificates as well, rather than rely on completely unstructured CNs.
It's very easy to fork mkcert for custom needs, and we'll make it even easier to build derived tools by making the root installation into a library, but the core tool will keep encouraging best practices.

I understand and agree. Thank you!

Tell that to our company who's OK with using a 20-year-old procedure :D

https://github.com/txthinking/mad can custom the cert O OU and CN


Performance degradation  after deleting all vertices

I develop a small application to insert 500K nodes to OrientDB (using version 1.7-rc2) It take around 47.3 seconds.  From the studio i run query "delete from Person", then i run the application again, but in this time it takes 501.6 seconds !!
Here is the code:
public class PerformanceTest {
TransactionalGraph g;
public PerformanceTest() {
	connect();
}

public void connect() {
	String dbURI = "remote:localhost/peopleGraph";
	OrientGraphFactory factory = null;
	factory = new OrientGraphFactory(dbURI).setupPool(1, 10);
	g = factory.getTx();
}

public void add() {
	long tOut, tIn = System.currentTimeMillis();
	for (long i = 0; i < 500000; i++) {
		Vertex v = g.addVertex("class:Person");
		v.setProperty("ID", i);
		v.setProperty("name", String.format("name-%06d", i));
                    // commit EVERY 100 records
		if (i % 100 == 0) g.commit();
	}

	g.commit();

	tOut = System.currentTimeMillis();
	System.out.println(String.format("Procesing time %f",
			(tOut - tIn) / 1000.0));
}
private void close() {
	g.shutdown();
}
public static void main(String[] args) {
	PerformanceTest t = new PerformanceTest();
	t.add();
	t.close();
}

}

Hi, I wonder if this issue was resolved?

Hi,
This issue will be resolved with new cluster design .
On May 7, 2015 9:56 AM, "Andrey Verbin"<EMAIL_ADDRESS>wrote:

Hi, I wonder if this issue was resolved?
—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/2244#issuecomment-99748795
.

Hi @laa , thank you for quick reply! It is being a year since this issue first created and 2.0 already out (I guess). Can you share some specifics on what is causing this issue and how new cluster design resolve it?
I have very limited knowledge of OrientDB but what I learned lead me to think that OrientDB record ID point to physical location of data on disk. This is why it is blazing fast at traversing rows - conventional database has to lookup physical locations in indexes while OrientDB just read data right away.
If my assumption is correct then you cannot move records inside database file which means that over time something like 'memory fragmentation' will happen and this will slow down not only 'deletes' but all 'updates'.
I was puzzled with above question when I found this issue in google and  I wonder if this issue has anything to do with my question.
Thank you very much!

Duplication of https://github.com/orientechnologies/orientdb/issues/5267


getBounds returns null on Text when text is integer of 0

The following code will create a text display, but is unable to return the bounds of it:
var val = 0;
var testText = new createjs.Text(val);
console.log(testText.getBounds());

A simple workaround is to ensure the text value is a string by adding a blank string to the end, like so:
var testText = new createjs.Text(val+"");

I just pushed a fix for this, based on @noobiept's pull request.


update .net docker images to latest version 3.1.2

Hi,
I have updated 3 dockerfiles to use latest version(3.1.2) of available .NET Core images. Those latest images include security fixes.
Release notes for 3.1.1
Release notes for 3.1.2
Thank you

Hi @b0
thanks for this PR.


Fix working with nested schemas for databases

[x] tests and linter show no problems (npm t)
[x] code is properly formatted (npm run fmt)
[x] description of changes is added in CHANGELOG.md

Landed in https://github.com/metarhia/metasql/commit/1ffc3df870500772adc63d0091595228a85db4c3


dockerBuild fails if node host user UID is not 1000

In trying to create a dockerBuild node, discovered having created a jenkins user with uid=1001 that dockerBuild fails with ```
10:33:18   > git checkout -f ac64818c12047d4da21c4f7e833f5deff1a4101c # timeout=10
10:33:19  sh<EMAIL_ADDRESS>Permission denied
10:33:19  sh<EMAIL_ADDRESS>Permission denied
10:33:19  mv: accessing<EMAIL_ADDRESS>Permission denied
The reason being because the adoptopenjdk docker images have the jenkins user set to uid=1000, which happens to match the adoptopenjdk Azure cloud uid of 1000.
It would be good to match the image to the host environment, or make the built image handle this dynamically?

Could someone summarize what is the status of this issue?
Have we solved it, or only had a workaround on jenkins agents? and if it is only for openj9 build. but not temurin's

From Semeru/OpenJ9 perspective it is not solved. I don't believe it is specific to OpenJ9. The workaround is you must run docker compiles on a machine where the host's user id (number) matches the user id in the container. This is due to host folders being mounted and written to from in the container during a build.

if you are runing  docker.image('adoptopenjdk/centos7_build_image').inside(){...} on a machine which jenkins user is not set to e 1000:1000, cannot use --user flag?
e.g  docker.image('adoptopenjdk/centos7_build_image').inside("-u jenkins:jenkins"){...}
we have dockerArgs  to config docker run parameter and pass into the pipeline

I got curious.
Looks like dockerArgs got overloaded when this was added (cc @gdams )
https://github.com/adoptium/ci-jenkins-pipelines/pull/350
So it is now used for the pull command as well as when starting the container. If I hack out the pull usage to test it, it still hangs on the checkout. I assume because the plugin adds the uid still.
docker run -t -d -u 1001:1001 -u jenkins:jenkins .....


Add badges

This PR is adding badges to docs.rs.
Example badges for mio crate:

URL
Badge

Latest version: https://docs.rs/mio/badge.svg

Version 0.4.4: https://docs.rs/mio/badge.svg?version=0.4.4

Version 0.1.0: https://docs.rs/mio/badge.svg?version=0.1.0

Version 666: https://docs.rs/mio/badge.svg?version=666

I decided to write my own badge generator instead of using services like shields.io but I have no idea how does it look like on other screens.
What do you think?

They look pretty good on my screen, on par with badges from shields.io, etc.


Add an asyncio version of the HttpApi class

This adds a Python 3.5+ async def / await version of the MatrixHttpAPI class. It also adds an import shim to give a nice (i.e. not syntax) error if a user tries to import it on <3.5.
I have asked a couple of people knowledgeable in such things and I expect no issues with having sections of the package to have different Python version requirements than others, as long as it is not imported there will be no trouble.

I need some tests on this code before I can merge it. I know that's a
complicated request because of how this only works with some versions, but I
don't want to signup to support code so abstracted away from the core of the
library if I won't at least get some sort of warning when I break it by changing
something in the main library.

@Zil0 @non-Jedi I have updated this, added tests and cleaned it up. I think it is good to go, if either of you have time to look it over :)

I am a little confused by the coveralls setup, it seems we are running it on all the jobs, but coveralls only takes the first report? Anyway the coverage will be screwy on anything <3.5

If the new asyncio tests were included in the coveralls report it would be green.


LEAN-3321:TNM-090 - Delete General table notes

The implementation of https://jira.atypon.com/browse/LEAN-3321. Refer to the Figma design at https://www.figma.com/file/vspHhzKTbwSkZWQWOcmIw2/LW---Editor-%26-Roles?node-id=25316%3A373326&mode=dev for visual details. It's important to highlight that the deletion icon won't be visible when the node is empty and this aspect will be addressed in the corresponding story ticket.

@IslamJMomani I believe I accidentally deleted this comment while attempting to remove one of my own comments:
Are you suggesting making the entire message a variable, not just the footnote type? I'm currently using the footnote type as a variable to also utilize it for reference  footnotes.

@IslamJMomani I believe I accidentally deleted this comment while attempting to remove one of my own comments: Are you suggesting making the entire message a variable, not just the footnote type? I'm currently using the footnote type as a variable to also utilize it for reference footnotes.

Yes, that was my suggestion. However, if necessary, the person responsible for implementing the regular footnote deletion can handle it when the time comes.

@nghazzawi-atypon,

The current PR state is different from what was previously approved, so it's useful to request another round of review in such cases.
Given that we have 2 tickets to cover the delete cases, I was expecting this PR to only handle deleting the general note. However, I see it covers both. Let's avoid this in the future, as it makes the review and cleanup process more challenging.
I believe we can further clean the code, but I recall you mentioning that Mohammad wanted this to be merged anyway, without major refactoring. Am I right?

@nghazzawi-atypon,

The current PR state is different from what was previously approved, so it's useful to request another round of review in such cases.
Given that we have 2 tickets to cover the delete cases, I was expecting this PR to only handle deleting the general note. However, I see it covers both. Let's avoid this in the future, as it makes the review and cleanup process more challenging.
I believe we can further clean the code, but I recall you mentioning that Mohammad wanted this to be merged anyway, without major refactoring. Am I right?

@IslamJMomani  Actually, I believe pursuing further cleanup or major changes at this stage carries considerable risk. With each delay in merging and the subsequent need to rebase to the master branch, new issues arise due to changes in the transformer, track changes plugin, and other elements, which in turn impact our ongoing work. Additionally, implementing both node types appears to be stuck in a loop. Even minor adjustments result in unexpected side effects, making deletion implementation in this context particularly challenging and causing more headache.  Considering the discussions we've had on https://jira.atypon.com/browse/LEAN-3321, it's clear that all of this should be revisited and re-implemented in our next plan, ensuring we can execute the changes correctly in their appropriate contexts.


Test coverage for custom events

We are currently lacking test coverage for emitted events, as I am currently unsure how to do this with Jest.
I assume that I need to listed to window events using Jest's bundled jsDom but have not been able to find a happy path for this.
Further notes in Satchel.events.test.js

Resolved by #10


Specify IP to set for zoneedit

Documentation of the zoneedit dynamic DNS change API:
https://support.zoneedit.com/Knowledgebase/Article/View/4/1/changes-to-dynamic-dns
Format is:
https://dynamic.zoneedit.com/auth/dynamic.html?host=<your_hostname>&dnsto=<your_ip>
The dyndns.class code for "zoneedit" does not specify "dnsto" at all. So I guess Zoneedit will be assuming the IP address that the request came from, which will be whatever is the current default gateway of pfSense - which probably works OK for ordinary failover of a primary to secondary, but not when the user wants the dynamic DNS name to point to something else.
This is a possible fix for Redmine 6992. It needs testing by someone with the relevant configuration and Zoneedit account, e.g. the OP of the issue.
https://redmine.pfsense.org/issues/6992

@rbgarga Did you manage to test it?
I actually do not know if it really works, I just followed the Zoneedit FAQ doc.

No, I don't have an account to validate it, what is a common situation when we deal to dyndns. But I've checked recommended clients source code and they all use this parameter.
https://sourceforge.net/projects/zoneclient/files/
https://github.com/egiles/dns-zoneedit/blob/master/lib/DNS/ZoneEdit.pm#L71
Now I've updated the ticket and submitter will be able to help us testing it


register fails with ReferenceError: regeneratorRuntime is not defined

Calling Pushy.register with this code:
const deviceToken = await Pushy.register({
          appId: '[my-app-id]',
        })

results in the following error:
Uncaught (in promise) ReferenceError: regeneratorRuntime is not defined
    at pushy-sdk-npm.js:1:1
    at f (pushy-sdk-npm.js:1:1)
    at new i (pushy-sdk-npm.js:1:1)
    at Object.register (pushy-sdk-npm.js:1:1)
    at _callee$ (EnableNotificationsStep.tsx:28:1)

Closing due to lack of activity.

This appears to still be an issue.
While the suggested solution* works, I don't think it should be the consumer's concern to install packages that are required to make Pushy work.
*npm i regenerator-runtime followed by import 'regenerator-runtime/runtime' at the top of the file that uses Pushy

Hi @jgarplind,
Thanks for reaching out and for confirming you're still facing this issue.
We've just released version 1.0.15 of the Pushy Web SDK which now includes babel-polyfill as a dependency of the npm package. This should effectively resolve the issue you encountered.
Please install version 1.0.15 of the Pushy Web SDK from npm using the following command:
npm install pushy-sdk-web@latest --save

Please give it a try, and let us know if there's anything else we can help with.

Hi @noe-david,
We'd be glad to further assist.
Can you please advise what kind of web framework you're using? Is it React/Angular/Vue or something else?

Hi @noe-david,
Thanks for letting us know! We've been able to reproduce and fix the issue in commit https://github.com/pushy/pushy-sdk-web/commit/b0bff868dd93bbb5170ed51a5f87f7ae908a2f45.
We've just released version 1.0.16 of the Pushy Web SDK which directly consumes the Pushy JS module.
Please install version 1.0.16 of the Pushy Web SDK from npm using the following command:
npm install pushy-sdk-web@latest --save

Please give it a try, and let us know if there's anything else we can help with.

Hey again! Thanks for being on this!
I installed the patch and ran the dev server and got this:
✘ [ERROR] Could not resolve "promise-polyfill"

    ../node_modules/.pnpm/pushy-sdk-web@1.0.16/node_modules/pushy-sdk-web/src/lib/pushy.js:7:20:
      7 │ import Promise from 'promise-polyfill';
        ╵                     ~~~~~~~~~~~~~~~~~~

  You can mark the path "promise-polyfill" as external to exclude it from the bundle, which will
  remove this error and leave the unresolved path in the bundle.

✘ [ERROR] Could not resolve "whatwg-fetch"

    ../node_modules/.pnpm/pushy-sdk-web@1.0.16/node_modules/pushy-sdk-web/src/util/api.js:1:7:
      1 │ import 'whatwg-fetch';
        ╵        ~~~~~~~~~~~~~~

  You can mark the path "whatwg-fetch" as external to exclude it from the bundle, which will remove
  this error and leave the unresolved path in the bundle.

Perfect! That solved it 👍
Thanks for your commitment @pushy team!


Command to generate Android NDK symbols.zip file

Hi! Is there any reason why appcenter-cli doesn't contain a simple command to do the building of symbols.zip automatically, c.f the complex steps described here...:
https://docs.microsoft.com/en-us/appcenter/diagnostics/android-ndk
Suggestion: create symbols.zip that covers all the so files in the distribution:
appcenter crashes make-ndk-symbols-zip

Hi @sseyod,
There is a reason indeed, and it is because the tool used to extract the symbols only works on Linux. As you already know, I prepared a Docker-based tool to do the job, available at https://github.com/microsoft/appcenter-cli/issues/618.
I marked this as a feature-request as we could integrate a solution within the CLI.

As we do not have plans to add support for this feature in the next year, I'm closing the issue


Won't Accept My Token

I just signed up and tried to use the eclipse plugin but I get the following pop-up error but with nothing in Eclipse error log:
We couldn't authenticate you. Please verify your token and try again

The token worked just fine on my vs-code and chrome plugins so I at least know the toke is correct.
My Env:
Eclipse SlimRel
Java 9.0.1
On another note . . .
Is this project dead? I see no activity since 2016? Any chance there will be any updates?

Please, create a support ticket here: http://feedback.codealike.com/forums/156227-general-ideas-and-feedback-for-codealike