Bypass CORS via Flash

On your demo page you say:
"Some ad's will throw "VAST Error: on VASTClient.requestVastXML, HTTP request error with status '-1'", because that adServer is not setting the http access control header, the reason why some video player's are able to play the ad's in firefox because they do the request by flash bypassing the browser".
I was wondering if you're working on adding this, or if you possibly know how it's being done (or have a link to a resource of how it can be done).
Looking at actionscript docs for "security.allowDomain"...
http://help.adobe.com/en_US/AS2LCR/Flash_10.0/help.html?content=00001490.html
..it says (regarding SWF versions):
Version 5. No cross-domain scripting restrictions.
Version 6. Cross-domain scripting security is introduced.
So I'm guessing I need to build a Version 5 or lower SWF? I'm new to Flash/Actionscript.
Thanks

Hi @gordonglas, no we are not working on this because the server should serve the VAST response with the correct CORS headers see http://www.iab.net/media/file/VASTv3.0.pdf, page 16 (<IP_ADDRESS> Cross Origin Resource Sharing (CORS) for JavaScript).
This happens in some servers because they only are expecting that the VAST response to be loaded by Flash, and Flash use a different way to handle CORS source 1, source 2 than the browsers source.
Now regarding your other question:
No I don't think you need to use a old version of flash, because I expecting them to serve the ad's with the cross-domain.xml (Flash CORS). So if you having a lot of issues and with CORS and your adservers are not friendly to start serving the correct headers you could do the following:
If you get that error message when loading the VAST response then using the ExternalInterface you can request some flash to load that XML and retrieve to the JS the result.

Thank you so much! I was able to get XML back via Flash, since our ad-tag provider has implemented a crossdomain.xml whitelist (just not the CORS headers for Javascript).


Credits

We need to write up some credits - this will appear when users look at the "about" menu.

Hi @antiboredom, if you want, I work on this feature.

@nucliweb that would be great - thank you!

@antiboredom do you like the system of Brackets for show credits?

@nucliweb I hadn't seen this before, but yeah I really like it!

Ok, I will work in this concept for the credits section ;)


Create reverse-bits.md

📥 Pull Request
Description
I've added the detailed description about reverse Bits problem. And I used java for implement the problem into code.
The Reverse Bits problem asks you to reverse the bits of a given 32-bit unsigned integer. Essentially, you need to flip the binary representation of the number so that the least significant bit (LSB) becomes the most significant bit (MSB) and vice versa.
Fixes #1198
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Thank you [@ajay-dhangar] for merging these changes.


Some confusion in your decisions documents organisation

Hello there,
I was reading through your decision documents and I found the following mistake:
ADR 10 has a note "Amended by 13. Terraform Data Structure". The actual document is in fact ADR 15. The text and the link aren't correct.
Also you seem to have two documents ADR 15:

ADR 15 DNS Infrastructure, the title is currently "14. DNS Infrastructure", that's confusing because the ADR 14 is another document 😬.
ADR 15 Terraform Data Structure that I mentioned before.

Btw, thank you for sharing publicly those documents 👍

Good spot @dgellow, hopefully #95 should sort this out.


Add a retry mechanism

Add retry parameters so the web requests call can be more robust.
I set up them up to do 5 retries with 10 seconds of interval as a baseline, so I'm open to discuss it.
Add the timeout parameter (as 30 seconds) to prevent the request from waiting for a long time.

I'm a bit out of touch with this code, so I'm not sure how valuable my review would be. One thing I remember from previous failures was that sometimes the exit code was not properly propagated during failure conditions and then the next step in the workflow executed. This usually lead to very long-running test suites because all the tests that rely on RavenDB to be available timeout. As long as this change addresses it in some way or another (I assume you have tested it with for example, an invalid license?) I'm :+1:


Bug report: reporting do not return a properly formatted JSON

Description
I just noticed that all the reporting commands that derive from the same baseclass are not properly formatting a JSON output. Even if you specify the -o json the items are returned in a CSV format
Steps to reproduce
Execute the m365 tenant report activeuserdetail -period D7 -o json or any other report command.
Expected result
A properly formatted Json Array
Actual result
A text output

That is by design, because the generated reports are CSV rather than data structures that we can return as JSON. I agree that it's suboptimal though. As changing it would introduce a breaking change, let's consider this for v4.

Looking at this issue it seems that the only thing that was wrong is that the JSON string was encoded twice. I'm not seeing a CSV string with JSON output and I can't trace it back to our code.
@appieschot has fixed the double encoding bug in #2534 which we have just shipped. With that, I think we can close this issue, correct?

Yes. I am closing it


Nostalgic Tweaks [1.20.1-Forge-2.0.0-Beta-8.4.1]

Mod Name
Nostalgic Tweaks
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/nostalgic-tweaks
Describe the bug
Nostalgia Tweaks causes a crash before title screen
Steps to reproduce
No response
Logs
https://gist.github.com/Its-Just-Luci/2c88f7184446360f6fe18e0804f8f196
Additional context
Despite having it's API mod installed and verified to be working, Nostalgia tweaks still causes an issue at startup. Sinytra has been giving me inconsistencies when trying to patch mods, but seems to stay fixed once I make it to the main menu, I've tried booting up with NT 3 or 4 times to no avail, so I assume I can safely say it's a 'proper' case of incompatibility

Cause of this error is rubidium, though both mods are compatible with Sinytra, when combined they cause a crash. Providing this info as @Su5eD had asked for it in a different issue report, so hopefully this helps

issue seems to be resolved when installing a newer version of Rubidium


Template Format update for New-EPACPolicyDefinition.ps1

I was using the script provided and wanted to provide enhancement to keep the format and order the same as defined in the StarterKit with the name at the top along with the properties defined in a specific order
Below are the changes suggested to this file to achieve this ordering
if ($PolicyDefinitionId -match "Microsoft.Authorization/policyDefinitions") {
    $policyDefinition = Get-AzPolicyDefinition -Id $PolicyDefinitionId
    $baseTemplate = [ordered]@{
        name       = $PolicyDefinition.name
        properties = $policyDefinition.Properties | Select-Object DisplayName, Description, Mode, @{n = "Metadata"; e = { $_.Metadata | Select-Object Version, Category } }, Parameters, PolicyRule
    }
    if ($OutputFolder) {
        $baseTemplate | ConvertTo-Json -Depth 50 | Out-File "$OutputFolder\$($policyDefinition.Name).json"
    }
    else {
        $baseTemplate | ConvertTo-Json -Depth 50
    }
}

if ($PolicyDefinitionId -match "Microsoft.Authorization/policySetDefinitions") {
    $policyDefinition = Get-AzPolicySetDefinition -Id $PolicyDefinitionId
    $baseTemplate = [ordered]@{
        name       = $PolicyDefinition.Name
        properties = $policyDefinition.Properties | Select-Object DisplayName, Description, Mode, @{n = "Metadata"; e = { $_.Metadata | Select-Object Version, Category } }, PolicyDefinitionGroups, Parameters, PolicyDefinitions
    }
    $baseTemplate.properties.PolicyDefinitions | Foreach-Object {
        $_ | Add-Member -Type NoteProperty -Name policyDefinitionName -Value $_.policyDefinitionId.Split("/")[-1]
        $_.psObject.Properties.Remove('policyDefinitionId')
    }
    if ($OutputFolder) {
        $baseTemplate | ConvertTo-Json -Depth 50 | Out-File "$OutputFolder\$($policyDefinition.Name).json"
    }
    else {
        $baseTemplate | ConvertTo-Json -Depth 50
    }
}

@martyh888 : If you like connect to me on my linkedin (see my profile)

Since I haven't heard from you. I will put the change in tonight

Cant direct connect to you but this is my linkedin. https://www.linkedin.com/in/martinhillman/
I am based in Perth Australia hence the time difference but I will fork and do a PR


Write a R program to find the eigenvalues of a matrix

Description
Write a R program to find the eigenvalues of a matrix
The eigenvalues and eigenvectors of a linear transformation are the values and vectors that determine the transformation. The eigenvalues of a matrix A are the values λ for which the matrix equation Av = λv has a non-trivial solution.
Input  :
1 2 3
4 5 6
7 8 9

Output :
16.116843969807043
-1.1168439698070427
0.9999999999999998

How to contribute

Save the solution in find_the_eigenvalues_of_a_matrix.r file
Add find_the_eigenvalues_of_a_matrix.r file in program/find-the-eigenvalues-of-a-matrix folder

Assign me.

!assign


Document gate layouts

Document wire, constant and constraint layouts for every gate.

Hello!
This PR has been open for a long time, please review and update as following:

If this PR is no l longer relevant, close it.
If this PR is relevant but not read, mark it as Draft and make a comment of what else needs to be done.
Fix any issues and get it merged / reviewed by 10/27/2023.

If there's no update by 10/27/2023 this PR will be closed.

Done in #692.


Evaluate the support for sharding/composition deployment topology and serving flow

Today, the K/V service has the following constraints:

Loads all data into the server RAM
Request flow is a single roundtrip to the server. The server does not communicate to anything outside the TEE when serving requests

As a result, there is limitation on the supported scale of the system. This is a known issue and the team is taking an incremental approach to build the foundations before solving this.
More sophisticated deployment topology and serving flow are being evaluated to support better horizontal scaling:

Server composition. Instead of a single deployment of a K/V server instance, if a K/V server process can talk to another trusted K/V server process using secure and privacy-preserving protocol, such as the same protocol used by external callers calling the K/V server, the K/V server deployment topology can become a graph of nodes instead of a single node. And each node system can decide to load different dataset.
Server sharding. Built on top of but not the same as server composition. Instead of loading all data into the server RAM, each server process may only load a subset. During serving, relevant subsets are queried by another intermediate server process that presents the final response to the external caller. There are multiple options to achieve the exact flow. This ticket is not going to prescribe any specific design.

This github issue is used to announce any updates relevant to this and if you have any suggestions/feedback please also comment here.

Sharding is available now
https://github.com/privacysandbox/fledge-key-value-service/blob/release-0.13/docs/sharding.md


Changes for trello linking and putting alpha banner on all page whils…

…t some titles and some spelling

Looks good.


Add a Write-Up for April 2018 - Tatu

Team members will produce a write-up of the most important things they have worked on since last Community Meeting, the problems they have found and what they plan to do in the next weeks (that can be a bit blurry, and that's fine). These write-ups will be published as a blog post for the community to review on Monday before the Community Meeting.
Create your own Write-Up for Community Meeting 10 using the same structure as https://raw.githubusercontent.com/aragon/aragon-wiki/master/docs/meetings/community/write-ups/cm06/tatu.md
Must be submitted by end of day, Tuesday 1st of May 2018!

Aragon write-up April
### Chris - Product Manager

#### Attend Offsite
- Lead product development process definition workshop
- Lead product roadmap development workshop
- Lead sprint planning workshop
- Lead 0.5 sanity check workshop

#### Implement Product Management Process
- Update product management process and documentation, based on team feedback
- Structure first development sprints and release cycle in Flow PM tool
- Track first development sprints and release cycle in Flow PM tool
- Implement daily written stand-up update process
- Lead weekly dev meetings
- Begin restructuring Github repositories

#### Hold regular 1on1 Conversations w/Product Team Members
- Jorge
- Bingen
- Brett
- Jouni
- Oliver
- Pierre

#### Support Audit
- Assume non-tech audit responsibilities
- Coordinate audit logistics

### Developed 0.5 Feedback Collection Process
- Determined how to collect feedback from internal and external channels
- Determined how to process feedback for input into dev process

### Next

#### Coordinate, Track and Report on Sprints and Releases
- Track in Flow PM tool to provide higher-level internal team visibility
- Track in Github/Zenhub to provide issue-level visibility

#### Continue Refining Product Development Process
- Incorporate community product feedback
- Streamline tracking and reporting activities
- Increase accountability and visibility into process

#### Continue Supoorting Audit
- Coordinate responses to audit findings
- Guide audit toward successful conclusion

#### Assume DevOps Responsibility

#### Continue Regular 1on1 Conversations with Dev and Design Teams

#### Support Product Team Hiring Process
- Take part in interview as needed
- Take part in trial weeks as needed


Re-organize documentation to list features independently of data objects

Ongoing
TO-DO before merging:

[ ] Add footprint attribute (#563),
[ ] Introduce to_area_or_point? (#564),
[ ] Add densify_points in config? (#530)
[ ] Add setter for metadata set_crs and set_transform? (#567)
[ ] Re-organize "Fundamentals" to be generic to all objects and add missing aspects (#568)
[ ] Do not forget to add to_pointcloud in "Interface" page.

I'm just thinking. I'm not sure how well nodata are discussed in the current documentation. Maybe we could have a subsection explaining nodata, when and how they are used, and how to handle the mask and update it (with set_mask). Sometimes people get confused on how to handle it.


Implement Package family

Feature
We need to create family Package that would hold just information about various subset grouping them together. This would be useful then for bundling things together for exports, filtering in UI, and so on. It should be just simple list of subset versions that could be created directly from tools without publishing, but versioned.
[cuID:25xp1b6]

This shouldn't just depend on the artist. Produciton could put together things from different assets, for exports, and so on. Put together stuff like geo, looks, clothes, grooms, ...

Kinda similar to the projection workflow we have experimented with; https://github.com/pypeclub/OpenPype/pull/1110

Produciton could put together things from different assets, for exports, and so on. Put together stuff like geo, looks, clothes, grooms, ...

But who or where defines what goes together? That's mostly what I'm asking. Just to figure out the approach to implementation here.

But who or where defines what goes together? That's mostly what I'm asking. Just to figure out the approach to implementation here.

we thought about actually using Loader (or something very similar to it). Maybe even action of ftrack. So you wouldn't need to go through publishing process

I've been doing a some brainstorming on this front a multiple question have arisen. To avoid ambiguity I will use the term package in completely generic way, but would like to define two distinct approaches that need to be supported that I will name assembly and bundle for not, just to have some differentiation. Names are not important at this point.

usecase one is where we have multiple subsets relate to each other in a very simplistic way without any special relationships. Example would be

a set of renderlayers (not know how they should be connected)
characters that always tend to appear together in the shot
a collection of trees that we grouped together to make it easier to load them into a scene when building a forest, etc.
All of these just need information that they belong together and I will call them bundles for now.

usecase two is multiple subsets that not only belong together, but should be connected (assembled) in a particular way.

A look and groom applied to an alembic cache. Can give you a render ready assembly of a character
A proxy look applied to a rig can give you animation ready assembly of a character
Cutlery and plates placed on a table and published together gives you an assembly that you can use for set dressing.
All of these need extra information about how things are connected, what their transforms might be and so on. I will call these assemblies for now.

My feeling is that these can and should be two separate families.

Bundle lets you group things together and then load them into your DCC in bulk, but that's about it. Considering they only contain metadata, these could technically be purely database based subsets not actually pointing to any files on disk and could be trivial to generate from practically anywhere. Loader, Scene, you name it.
Assembly requires to be published from a dcc, because it requires the artist o create all these relationships and then serialize them the same way as the assembly attempted to do it now. Here, we hit a problem with the massive scope of the options and it is precisely what USD is good at, even if we can't neccessarilly load USD directly everywhere, it could still be parsed in unsupported hosts and the assembly would be re-created on the fly from host native data.

For example. I could choose to load Assembly (USD representation) to maya as USD stage, or as native data, which could just get the relationships and transforms of all the references, load their maya native representations and connect accordingly.
Now the main question I think is. Is it worth having these families split, or is bundle just and extremely simple case of assembly and could be represented by a USD file, that literally just points to the required references?

Bundle lets you group things together and then load them into your DCC in bulk, but that's about it. Considering they only contain metadata, these could technically be purely database based subsets not actually pointing to any files on disk and could be trivial to generate from practically anywhere. Loader, Scene, you name it.

This seems to be like groups in OP?
Just need support for loading in groups and defining them.

his seems to be like groups in OP?
Just need support for loading in groups and defining them.

That is actually true and might be enough for the simple variation. In v4 I would love to replace groups with something more flexible. So one subset could be part of multiple groups.

That is actually true and might be enough for the simple variation. In v4 I would love to replace groups with something more flexible. So one subset could be part of multiple groups.

What's the state of design ideas on this Issue and potentially that grouping restructure?


not working on custom network

Hi,
To be honest, it's super sad that this even needs to exist. Which i can only blame docker for as their ipv6 support is so horrendously crappy...
Which makes me very happy that this project is there to help people like me :)
I followed your guide and a command like this works:
docker run --rm -t busybox ping6 -c 4 google.com
But if i create a custom network:
docker network create --ipv6 --subnet fd00:dead:beef::/48 test
And then run a container in that network:
docker run --network test --rm -t busybox ping6 -c 4 google.com
It doesn't ping.
I might very well be missing something but i have no clue what that might be?
Or am i trying something that is unsupported?
Best regards,
Mark

Hi Mark, thanks for trying it out. It's not unsupported, that should work. In the custom network case, did you start the ipv6nat container in the same way? It still needs to have --network host.

Could you share the command you're using to start the ipv6nat container? Also, output of ip6tables-save (after you've started all containers) might be useful.

Hi Robbert,
Sure thing!
The command to start ipv6nat is:
docker run -d --name ipv6nat --privileged --network host --restart unless-stopped -v /var/run/docker.sock:/var/run/docker.sock:ro -v /lib/modules:/lib/modules:ro robbertkl/ipv6nat
As per your description on the main page of this project.
The iptables output (note, this is a vultr node, spun up for this test purpose):
# Generated by ip6tables-save v1.8.4 on Mon Jul 27 16:03:35 2020
*nat
:PREROUTING ACCEPT [3:228]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:DOCKER - [0:0]
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT ! -d ::1/128 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -o br-2a4cee23ef2e -m addrtype --dst-type LOCAL -j MASQUERADE
-A POSTROUTING -s fd00:dead:beef::/48 ! -o br-2a4cee23ef2e -j MASQUERADE
-A POSTROUTING -o docker0 -m addrtype --dst-type LOCAL -j MASQUERADE
-A POSTROUTING -s fd00::/80 ! -o docker0 -j MASQUERADE
-A DOCKER -i br-2a4cee23ef2e -j RETURN
-A DOCKER -i docker0 -j RETURN
COMMIT
# Completed on Mon Jul 27 16:03:35 2020
# Generated by ip6tables-save v1.8.4 on Mon Jul 27 16:03:35 2020
*mangle
:PREROUTING ACCEPT [101:8272]
:INPUT ACCEPT [48:3552]
:FORWARD ACCEPT [32:2992]
:OUTPUT ACCEPT [165:17064]
:POSTROUTING ACCEPT [186:19192]
COMMIT
# Completed on Mon Jul 27 16:03:35 2020
# Generated by ip6tables-save v1.8.4 on Mon Jul 27 16:03:35 2020
*raw
:PREROUTING ACCEPT [116:9572]
:OUTPUT ACCEPT [165:17064]
COMMIT
# Completed on Mon Jul 27 16:03:35 2020
# Generated by ip6tables-save v1.8.4 on Mon Jul 27 16:03:35 2020
*security
:INPUT ACCEPT [48:3552]
:FORWARD ACCEPT [20:2080]
:OUTPUT ACCEPT [165:17064]
COMMIT
# Completed on Mon Jul 27 16:03:35 2020
# Generated by ip6tables-save v1.8.4 on Mon Jul 27 16:03:35 2020
*filter
:INPUT ACCEPT [8:688]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [27:2932]
:DOCKER - [0:0]
:DOCKER-ISOLATION-STAGE-1 - [0:0]
:DOCKER-ISOLATION-STAGE-2 - [0:0]
:DOCKER-USER - [0:0]
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A FORWARD -o br-2a4cee23ef2e -j DOCKER
-A FORWARD -o br-2a4cee23ef2e -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -i br-2a4cee23ef2e ! -o br-2a4cee23ef2e -j ACCEPT
-A FORWARD -i br-2a4cee23ef2e -o br-2a4cee23ef2e -j ACCEPT
-A DOCKER-ISOLATION-STAGE-1 -i br-2a4cee23ef2e ! -o br-2a4cee23ef2e -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o br-2a4cee23ef2e -j DROP
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN
COMMIT
# Completed on Mon Jul 27 16:03:35 2020

I did try adding the ipv6nat node to the test network, but that didn't seem to make any difference. The ping still wouldn't work for a container in that same network.

@markg85 Can you restart docker, try to ping and post the output of ip6tables -nvL which may provide additional information about package stats?
The current configuration seems fine:

-A FORWARD -i br-2a4cee23ef2e ! -o br-2a4cee23ef2e -j ACCEPT should (finally) ACCEPT your traffic to the destination server.
-A POSTROUTING -s fd00:dead:beef::/48 ! -o br-2a4cee23ef2e -j MASQUERADE should (finally) masquerade your traffic.

That second line fails for me.
❯ ip6tables -A POSTROUTING -s fd00:dead:beef::/48 ! -o br-2a4cee23ef2e -j MASQUERADE
ip6tables: No chain/target/match by that name.

This is the output you requested:
❯ ip6tables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
   36  3176 DOCKER-USER  all      *      *       ::/0                 ::/0
   36  3176 DOCKER-ISOLATION-STAGE-1  all      *      *       ::/0                 ::/0
    8   832 DOCKER     all      *      docker0  ::/0                 ::/0
    8   832 ACCEPT     all      *      docker0  ::/0                 ::/0                 ctstate RELATED,ESTABLISHED
    8   832 ACCEPT     all      docker0 !docker0  ::/0                 ::/0
    0     0 ACCEPT     all      docker0 docker0  ::/0                 ::/0
    2   144 DOCKER     all      *      br-2a4cee23ef2e  ::/0                 ::/0
    0     0 ACCEPT     all      *      br-2a4cee23ef2e  ::/0                 ::/0                 ctstate RELATED,ESTABLISHED
    9   684 ACCEPT     all      br-2a4cee23ef2e !br-2a4cee23ef2e  ::/0                 ::/0
    2   144 ACCEPT     all      br-2a4cee23ef2e br-2a4cee23ef2e  ::/0                 ::/0
    0     0 ACCEPT     all      br-2a4cee23ef2e !br-2a4cee23ef2e  ::/0                 ::/0
    0     0 ACCEPT     all      br-2a4cee23ef2e !br-2a4cee23ef2e  ::/0                 ::/0

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
 pkts bytes target     prot opt in     out     source               destination
    9   684 DOCKER-ISOLATION-STAGE-2  all      br-2a4cee23ef2e !br-2a4cee23ef2e  ::/0                 ::/0
    8   832 DOCKER-ISOLATION-STAGE-2  all      docker0 !docker0  ::/0                 ::/0
   36  3176 RETURN     all      *      *       ::/0                 ::/0

Chain DOCKER-ISOLATION-STAGE-2 (2 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DROP       all      *      br-2a4cee23ef2e  ::/0                 ::/0
    0     0 DROP       all      *      docker0  ::/0                 ::/0
   26  2200 RETURN     all      *      *       ::/0                 ::/0

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination
   36  3176 RETURN     all      *      *       ::/0                 ::/0

IPv6 is such a.... thorough piece of crap to get working. I honestly can't wrap my head around how people could invent something so super vague. And that comes from me as software developer. Imagine how totally "out of this world" ipv6 must feel to less technical educated people.

@markg85 Masquerade Rules can only be used in the NAT Table. You might want to check the output of ip6tables -t nat -nvL. :+1:

@markg85 Masquerade Rules can only be used in the NAT Table. You might want to check the output of ip6tables -t nat -nvL.

I think you're assuming i know what that output means and how to interpret that? ;)
I have no clue!
❯ ip6tables -t nat -nvL
Chain PREROUTING (policy ACCEPT 9 packets, 684 bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER     all      *      *       ::/0                 ::/0                 ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 78 packets, 6237 bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER     all      *      *       ::/0                !::1                  ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT 78 packets, 6237 bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 MASQUERADE  all      *      br-2a4cee23ef2e  ::/0                 ::/0                 ADDRTYPE match dst-type LOCAL
    0     0 MASQUERADE  all      *      !br-2a4cee23ef2e  fd00:dead:beef::/48  ::/0
    0     0 MASQUERADE  all      *      docker0  ::/0                 ::/0                 ADDRTYPE match dst-type LOCAL
    2   208 MASQUERADE  all      *      !docker0  fd00::/80            ::/0

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 RETURN     all      br-2a4cee23ef2e *       ::/0                 ::/0
    0     0 RETURN     all      docker0 *       ::/0                 ::/0

But to remind you. This is still just plain vultr with a fedora node.

If you can give me your public key for ssh's authorized_keys file and you can play with it.
I can also spin up a new node with only that node + docker installed, nothing more (and cgroups set to v1 for docker). So that you begin with a clean slate.

@markg85 As you can see, the corresponding NAT rule is not matched by your packages:
0     0 MASQUERADE  all      *      !br-2a4cee23ef2e  fd00:dead:beef::/48  ::/0

If you are able to create a clean system, you should check if it works on this machine.

@markg85 As you can see, the corresponding NAT rule is not matched by your packages:
0     0 MASQUERADE  all      *      !br-2a4cee23ef2e  fd00:dead:beef::/48  ::/0

If you are able to create a clean system, you should check if it works on this machine.

I'm totally lost.
I'm following the exact lines on the main page which apparently gives me that.
I can't make things up as i simply can't think of what to type in or what means what.
Lets bisect what you say first, as that sounds alien to me too.
the corresponding NAT rule is not matched by your packages
NAT rule (network address translation), i know the abbreviation. I "kinda" know what nat does.
packages ... What packages? We're not talking about fedora distribution packages i assume. I'm guessing "network packages" but that too doesn't make much sense to me as this seems to apply to the whole "adapter". I'm lost, what do you mean?
you should check if it works on this machine ... That's exactly what i'm doing and why i'm ending here. I can't. And i can't "guess" the correct commands as ipv6 made any guess work require scientific papers and many decades of research before one gets it concepts.
Lastly, can i have your public ssh key? I'll spin up a new node and do absolutely nothing on it besides installing docker + adding you to the `authorized_keys" file. Hopefully you can try out the case i have here.

@markg85

I'm totally lost.

Okay, let's break it down to a few essential points.
All your docker containers will get a private IPv4 address, which is used for internal communication. As your docker host (very likely) does not have enough public IPv4 addresses for each container, outgoing packets (destination outside your docker network or docker host) have to use NAT (Network Address Translation) which will basically provide a way to communicate with services outside your docker host with the public IPv4 address of your docker host.
IPv6 provides a huge space of addresses, so you (might) be able to directly assign public IPv6 addresses to your container so you do not need NAT. As this is a completely different solution comparing to Docker's IPv4 handling, Docker-IPv6-NAT will simply do exactly the same as docker already does for IPv4: NAT for IPv6.
So if you ping Google, your ICMPv6 Echo Request packets will leave the docker network and the docker host. As a result of this, the following rule should be applied:
Chain POSTROUTING
    0     0 MASQUERADE  all      *      !br-2a4cee23ef2e  fd00:dead:beef::/48  ::/0

"Please MASQUERADE (which you want for your IPv6 NAT setup) all packets which leaves the docker network (you created) and are sent from containers attached to this network."
As you can see, it works for the default bridge docker0:
    2   208 MASQUERADE  all      *      !docker0  fd00::/80            ::/0

This might be a misconfiguration of your docker network, a routing issue or a DNS issue as I cannot see any IPTables rules, which might drops your outgoing packets.
Can you please provide the output from your docker host for:

docker network inspect test
ip -6 route

And from a docker container spawned with docker run --network test --rm -it debian:stable bash:

ip addr
cat /etc/resolv.conf
ip -4 route
ip -6 route

Lastly, can i have your public ssh key?

Short answer: no. Long answer: I do not prefer to log into other peoples machines.
But with the requested output (see above), we might be able to solve your problem. :wink:

@bephinix Thank you for that elaborate explanation! Really awesome!
I think i'm at to point to know enough about it to know that i know no shit about it :) (if that makes sense, hehe)
The way you describe it sounds logical to me and how i would want to have it to work. I don't want to manage every individual container by it's own to have it's firewall in order. I want my containers to all be private unless i expose ports to the outside world (which docker conceptually allows just fine). So i think, conceptually, NAT is a fitting solution. In fact, i'd argue that configuring each instance (if each had a public ipv6 ip) is much more of a hassle and performance overhead that is just not needed. The nodes i have now all have their own ipv4 local address and that's perfectly fine. I don't need or even want them to be public.
Here's a lot of information you requested :)
❯ docker network inspect test
[
    {
        "Name": "test",
        "Id": "2a4cee23ef2ed89554c9a36f0b79ff1ccfc7f5ee0c2ccd571b4081fcb7233aa8",
        "Created": "2020-07-27T15:38:16.964289023Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": true,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/16",
                    "Gateway": "<IP_ADDRESS>"
                },
                {
                    "Subnet": "fd00:dead:beef::/48"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {},
        "Labels": {}
    }
]

❯ ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:19f0:5001:1d26::/64 dev ens3 proto ra metric 100 pref medium
fd00::/80 dev docker0 proto kernel metric 256 linkdown pref medium
fd00::/80 dev docker0 metric 1024 linkdown pref medium
fd00:dead:beef::/48 dev br-2a4cee23ef2e proto kernel metric 256 linkdown pref medium
fe80::/64 dev ens3 proto kernel metric 100 pref medium
fe80::/64 dev docker0 proto kernel metric 256 linkdown pref medium
fe80::/64 dev br-2a4cee23ef2e proto kernel metric 256 linkdown pref medium
default via fe80::fc00:2ff:fee8:c673 dev ens3 proto ra metric 100 pref medium

And here are the outputs from within the container (docker run --network test --rm -it debian:stable bash)
root@1258d023b558:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
44: eth0@if45: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:ac:16:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fd00:dead:beef::2/48 scope global nodad
       valid_lft forever preferred_lft forever
    inet6 fe80::42:acff:fe16:2/64 scope link
       valid_lft forever preferred_lft forever

root@1258d023b558:/# cat /etc/resolv.conf
nameserver <IP_ADDRESS>
nameserver 2001:19f0:300:1704::6
options ndots:0

root@1258d023b558:/# ip -4 route
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/16 dev eth0 proto kernel scope link src <IP_ADDRESS>

root@1258d023b558:/# ip -6 route
fd00:dead:beef::/48 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fd00:dead:beef::1 dev eth0 metric 1024 pref medium

Note that if you don't trust my box, that's fine :) You can spin up a vultr node too, hehe. Tell me if you want to go that route as i can give you the exact commands i used to get it up and running.

@markg85 Okay, I would guess that the cause of the broken IPv6 ping are misconfigured devices, routes or addresses.
As you see, the docker network you created does not have a gateway set for IPv6; it should look like this:
"Config": [
                {
                    "Subnet": "<IP_ADDRESS>/16",
                    "Gateway": "<IP_ADDRESS>"
                },
                {
                    "Subnet": "fd00:dead:beef::/48",
                    "Gateway": "fd00:dead:beef::1"  ## This line is missing! ##
                }
            ]

Can you check which IPv6 addresses are configured for your docker host by using ip addr? (You may want to mask your public IPs.)

Tell me if you want to go that route as i can give you the exact commands i used to get it up and running.

This might be useful. Please also add your Linux Kernel version and the name and version of the OS you are using.

There must be more wrong.
The help on this page does not mention that the gateway needs to be added.
I removed the network and recreated it:
docker network create --ipv6 --subnet fd00:dead:beef::/48 --gateway fd00:dead:beef::1 test
And ran: docker run --network test --rm -it debian:stable bash
Now we're even further gone.
ping6 google.nl <-- no result
ping google.nl <-- no result
The network looks like this now:
❯ docker network inspect test
[
    {
        "Name": "test",
        "Id": "bae07ad09bdc83a5422fcef0f51f141b9d6f7894b4803ea2d8d5812480b8ba94",
        "Created": "2020-08-02T15:49:24.476825663Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": true,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/16",
                    "Gateway": "<IP_ADDRESS>"
                },
                {
                    "Subnet": "fd00:dead:beef::/48",
                    "Gateway": "fd00:dead:beef::1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {},
        "Labels": {}
    }
]

To be fair, i think we do keep doing this all next week and still get no further.
I really think it would be best if you could either spin up a vultr node or me spinning one up and giving you access to it.
 You can test things much faster if you don't have the hours of latency between your question and my answers :)

@markg85 Okay, let's start with how you created your VM/Node. Can you post the steps and the OS and kernel version you are running on your node?

Vultr: i took Fedora 32 x64 (32 is the version, don't be fooled by that number)
Logon to your node.
Note: everything written in these blocks are the commands i'm executing.
Updating everything:
dnf update -y and reboot
Go back to cgroups v1 as docker doesn't like v1 yet
And i'm not willing to use "podman".
grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0" and reboot
Install docker (moby)
dnf install moby-engine -y
And enable/start it
systemctl enable docker --now
Test if it works
docker run --rm -t busybox ping -c 4 google.com <-- gives 4 ping results
docker run --rm -t busybox ping6 -c 4 google.com <-- fails (unsurprisingly, i did nothing with ipv6 here in this case)
And done :)
From this moment on you have a working docker environment.
Next is getting the NAT + IPv6 stuff working.
Right now on that particular node my kernel is: Linux ipv6-test 5.7.11-200.fc32.x86_64 #1 SMP Wed Jul 29 17:15:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux but you might very well have a different one. Also, i don't think the kernel version matters. Assumption... sometimes dangerous :P but hey, IPv6... it's "alive" for so many years already. I sure as hell are not running a 2.0 kernel or something ancient like it.
Good luck!

@markg85 Thx, I will check it out.

@markg85 Can you test the following command: docker run --network test --rm -t busybox ping6 -c 4 2001:4860:4860::8888 ?

@markg85 Can you test the following command: docker run --network test --rm -t busybox ping6 -c 4 2001:4860:4860::8888 ?

Yes.
That works! Why? lol

@markg85 I think I found your error. Well, it is not your error.
It was the DNS.
Docker itself and Docker-IPv6-NAT uses IPTables/IP6Tables for setting up firewall rules to isolate networks and containers and managing NAT. There are (at least) two kernel subsystems, which will handle the "filter operations": nf_tables (new) and x_tables (legacy).
As Docker currently does not support nf_tables, it uses x_tables as the IPTables backend (so does Docker-IPv6-NAT). Fedora 32 uses nf_tables for its firewall, which breaks Docker Networking; I was not able to resolve hostnamens on IPv4-only bridges either.
If you use a custom bridge network (not docker0), Docker will configure its own DNS resolver to be able to resolve container hostnames. If you using nf_tables, the forwarded DNS queries will not succeed.
It might work with docker0, as this default bridge is not a normal birdge network.
This nf_tables/x_tables issue is also present in Debian 10 (or was).
It took me some hours to find the underlying cause and I wrote a Tutorial for a Hosting Provider which contains some information about it and a workaround; you might want to check it out.
How to Fix
Edit /etc/firewalld/firewalld.conf and set FirewallBackend=nftables to FirewallBackend=iptables and reboot.
It should work now! :tada:

Ahh, so that's why you kept asking for the kernel ;)
See, this is going a lot faster!
So weirdly enough, this didn't work right away after applying your fix.
I undid it to just figure out that nothing worked anymore (any ping, ipv4 and v6).
I redid your fix and now for whatever creepy magical mystical reason it all of a sudden does work...
For now, it works :cake:
But i'm really expecting this to fail for whatever reason.
Also, the guide on the main page doesn't tell me to add the ipv6 gateway in the network create line. Could you fix that up?
And perhaps mention this whole bla_tables shebang in there too ;)

@markg85 Great it works now! You should an OS which is officially supported by Docker; e.g. Fedora 31. :+1:

Also, the guide on the main page doesn't tell me to add the ipv6 gateway in the network create line.
Well you do not have to. I am using Debian 10 and ArchLInux and the Gateway is set correctly. There is also a bug for docker network inspect which does not show the gateway although it is set.

And perhaps mention this whole bla_tables shebang in there too ;)

Yes, I will create a PR.

@robbertkl This should be solved.

Thanks!

@markg85 Great it works now! You should an OS which is officially supported by Docker; e.g. Fedora 31.

Also, the guide on the main page doesn't tell me to add the ipv6 gateway in the network create line.

Well you do not have to. I am using Debian 10 and ArchLInux and the Gateway is set correctly. There is also a bug for docker network inspect which does not show the gateway although it is set.

And perhaps mention this whole bla_tables shebang in there too ;)

Yes, I will create a PR.

Perhaps choosing Fedora 32 added to the difficulties.
Do know that i start a node with the intention to keep it running for quite a while (years sometimes) so i prefer choosing the latest version.
Thank you very much for all your help!
 It's not blocking anything. Just a warning in the log that i want to get rid of which triggered this endeavor.


add link(s) to external visualizations of MBON data?

Should we include links to other summaries of MBON datasets?
This map should be the all-encompassing map and could link out to other views like the occurrence data only.
Example links that could be added:

for MBON occurrence data in OBIS: https://obis.org/institute/23070
others?

Maybe update the readme to include the information from the first cell of https://github.com/marinebon/map-of-activities/blob/main/map-of-activities.ipynb?
The way the map is created, it's tricky to add in links on the webpage. Right now I'm using attr in cell[6] to include additional links in the footer.


Add a speak(string id, string text) method to TTSQueue that calls the Dart API to speak if no speak is enqueued, otherwise enqueue it for after the utterance

Completed https://github.com/muxable/rtchat/commit/4d709ace1491356f2e4cad232aeca23c3d086138


git config

Add additional optional git config arguments for nix shell
git config --global user.name "Your Name"
git config --global user.email<EMAIL_ADDRESS>

GIT_AUTHOR_NAME is the human-readable name in the “author” field.
GIT_AUTHOR_EMAIL is the email for the “author” field.
GIT_AUTHOR_DATE is the timestamp used for the “author” field.
GIT_COMMITTER_NAME sets the human name for the “committer” field.
GIT_COMMITTER_EMAIL is the email address for the “committer” field.
GIT_COMMITTER_DATE is used for the timestamp in the “committer” field.
EMAIL is the fallback email address in case the user.email configuration value isn’t set. If this isn’t set, Git falls back to the system user and host names.

fixed in
https://github.com/tkachuk-labs/stack-templates/commit/4c026e7667390c77be68e43e0d67df15204697d2


Bug Fixes -

#266 - Create RBD Wizard - View Task Progress page/screen shows extra information
#260 - During RBD creation (wizard), if you create a new pool vs. use an existing pool, the left pane overwrites part of the wizard steps on top
#252 - status inconsistent in top level list views vs. cluster object details > host list view
#246 - Admin > Tasks: I can see a Task List, but there’s no timestamp (just date) and by who on the Submitted column
#244 - RBD resizing let’s user specify unrealistic values (beyond what you actually have) without any warning message
#253 - charts look decent but would be better if text should be left justified per design
#256 - RBD List view: RBD name should be left justified
#258 - RBD List view: RBD name should be left justified, and there shouldn’t be so many spaces to say “ RBDName in MyCluster”

@cloudbehl Please review.


Update mongeez version.

Thanks for your contribution! I am going to update the README as soon as I publish a new release that will actually support Mongeez 0.9.6.

Obsolete due to #6.


Feature request -- disable range of the dates in the picker

Currently in the picker sap.m.DatePicker we can select all the dates but there must be some option which helps to disable dates atleast range of dates that would be helpful instead of validating after the change in the calender

Hi,
thanks for the suggestion! I'll pass this on to the responsible developers and we'll let you know if and when it is implemented.
Kind regards
Christiane

Hi @kartheekgj ,
Sorry for the delay.
Do you still want this feature?
Thanks and Kind Regards,
Diana, openui5 dispatcher

Nope we have found a work around solution for using date picker range

@kartheekgj, thank you for the answer.
Therefore I'm closing this one.
Thanks and Kind Regards,
Diana


Where is file font-awesome.css?

In documentation you refer to link to file font-awesome.css
Where is that file?
I mean, I did exactly as you stated in documentation, and that's what I get:

thank you

Thanks to the file shared by @mspanish I go it :)
You should add such file in the repository

I cannot add font-awesome to the repo since this is an external project, and in fact js-socials can work perfectly with any other icon library. It's only defaults that are bound to font-awesome (as a most widely used lib).
I guess the solution would be to more precisely explain that font-awesome should be downloaded separately and probably provide a link to it.
What you think?

I think it is a perfect idea. But it would also be preferable to add to the repository by default, the files provided by @mspanish. Her files set seem to be lighter than the font-awesome.min.css

Yes, this file set is great, we really appreciate @mspanish efforts.
The thing is including it in the repo directly would not be ideal, since component is not hardly dependent on any of these iconsets. So I do believe it should be described better on the website of the project.
@jfoclpf, thank you for the feedback, it will be considered.


question on syntax highlighting request initiated by user's javascript

Thanks for this great software, I have been using it in my blog and really like it.
The following html code is meant to do syntax highlight on a chunk of code pasted in the textarea. However, it's strange that when the page initially load, the part in div was syntax-highlighted, however, when I click "Format" button, it doesn't do syntax-highlighting. I guess something basic must be wrong with my javascript.
Thanks in advance.

	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
	<title>Hello SyntaxHighlighter</title>

	<link type="text/css" rel="stylesheet" href="styles/shCoreDefault.css"/>

<textarea id="src" rows="7" cols="80"> </textarea>
<button onclick="render()"/>Format</button>

a = "hello world";
if (a > 10) {
	console.log("done");
}

v3 unfortunately wasn't meant to ran multiple times. I'll implement this for v4. https://github.com/syntaxhighlighter/syntaxhighlighter/issues/375


Remove input data folder from SpeedyWeather.jl

This PR removes the input_data folder from SpeedyWeather.jl and adds functions to check and download input data at the first run of  SpeedyWeather.jl. As more input data are likely to be added soon (e.g. surface fluxes param), I thought this is a good time to add something like this before this repo gets too bloated. For now, I use the same licence as in SpeedyWeather.jl  but we should eventually correct the copyright and licencing information to that of the data. For now, and for simplicity,  the input_data archive is stored on GitHub at https://github.com/dmey/speedy-weather-input-data but we should eventually move it onto HTTP storage. @milankl more immediately, if you like the sound of this, I would like to move the input_data repo under your username or on org for SpeedyWeather.jl.

Just set up github.com/SpeedyWeather and therein a repository called SpeedyWeatherInputData

I think we should agree on an interface between SpeedyWeather.jl and SpeedyWeatherInputData.jl, because this might be also the time to think about what to do if someone wants to use their own orography for example. One way could be do officially register SpeedyWeatherInputData.jl and then have as a default
run_speedy(input_data=SpeedyWeatherInputData)

but someone could just load another module
import MyInputData
using SpeedyWeather
run_speedy(input_data=MyInputData)

For orography for example we need just an array on a grid that is supported by the spectral transform in SpeedyWeather.jl, so SpeedyWeatherInputData could provide a function like get_orography and the transform is then done in SpeedyWeather.jl. What do you think?

Regarding orga see #182

I'm honestly thinking to postpone this idea. While I agree with it in general, moving the data somewhere else and finding a good interface should probably only be done once we've had the chance to play around with it more. This is to understand what we would want from such a code/input data separation and what interface would make most sense. At the moment, I wanted to have primitive equations (but not necessarily all the parameterizations) for v0.5 and only if the surface parameterizations are implemented we will know better how to structure this separation.
Does that make sense?

Another point is reproducibility. If we turn some SpeedyWeather.jl release into a doi (say with zenodo) in the future then we would have a dependency on another repository which should be clearly tagged with a version number. What I like about having the smallest default data set within the repository itself is that we don't have to deal with that.

Alright, I give this PR a v0.6 milestone for now and we can pick that up again once the primitive equation model is up and running and we actually use all that input data.


Code=-1007 "too many HTTP redirects"

I have been using your library from long time and it's working pretty good. But all of the sudden I am facing an issue Code=-1007 "too many HTTP redirects"
I am just passing URL and when I debug it is giving this error for that URL. That URL loads the image when I check in browser. Also When I manually load that image using the below code it's working.
NSURL *url = [[NSURL alloc] initWithString:urlString];
NSData *data = [[NSData alloc] initWithContentsOfURL:url];
UIImage *result = [[UIImage alloc] initWithData:data];
cell.brandImageView.image = result;
But SDWebImage is failing in this case.
Any help would be appreciated.

please share the image url

It's
https://lorealusa.app.box.com/representation/file_version_76631532073/image_2048_jpg/1.jpg?shared_name=minpjkejz8ogyd3ie9m06340dye94f6d
On Mon, 19 Jun 2017 at 3:39 PM, Konstantinos K<EMAIL_ADDRESS>wrote:

please share the image url
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rs/SDWebImage/issues/1935#issuecomment-309396780, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AESjlfjvd-L7s4_Uw_nXFDumP3atVUduks5sFki5gaJpZM4N9-CF
.

--
Thanks & Regards
Ram

you are right, i just replicated that in the demo project. really weird.

Yeah.. All I can do is to keep a check condition in error care as mentioned below and download the image manually and send it through completion block.
if (error.code == NSURLErrorHTTPTooManyRedirects) {                         dispatch_queue_t queue = dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_HIGH, 0ul);                         dispatch_async(queue, ^{                             NSError * error = nil;                             NSData * imageData = [NSData dataWithContentsOfURL:url options:0 error:&error];                             if (error)                                 NSLog(@"error is %@",error);                             dispatch_async(dispatch_get_main_queue(), ^{                                 UIImage *image = [UIImage imageWithData:imageData];                                 completedBlock(image, nil, cacheType, YES, url);                             });                         });                     }
But I need to update this logic so that Image cache is also handled in this case.

@RamChandraReddy are you interested in creating a PR?

Closing due to lack of response


Set Payment Pending status when redirecting to payment

Abandoned payments were left hanging as pending orders in Magento, this happens when customers goes to payment portal and then close the browser window without confirming or cancelling payment. This change sets the order to Pending Payment before redirecting customer to payment portal which means Magento will automatically cancel the order if payment is not completed within a store set timeout.

Needs some more rework


Powertoy Run Consuming 100% of Disk After Startup

Microsoft PowerToys version
v0.77.0
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
Whenever the system is restarted the powertoy run is consuming 100% of the disk usage making the system unusable for atleast 5 minutes.
✔ Expected Behavior
It should not consume 100% of the disk resource. For the initial indexing it's okay to to it once but not everytime I restart my system.,every time
❌ Actual Behavior
Whenever the system is restarted the powertoy run is consuming 100% of the disk usage making the system unusable for atleast 5 minutes.
Other Software
No response

/bugreport

Here is the bug report generated by the method mentioned above.
Uploading PowerToysReport_2024-01-23-19-06-32.zip…

@anirban12d looks like that just links to this issue, I am unable to download the bug report.


Joins with sql_query where column names conflict

The root of my issue is Diesel's inability to perform multiple joins on the same table in a single query (due to the lack of aliasing). My attempt at a workaround is to construct a raw query using sql_query. However, when there are columns of the same name across multiple tables in the query, the deserialization results in column values being overwritten by the values of that column from the other table. What is the suggested approach?

You need to indroduce unique names via expr as some_name for each column in your select clause.
As you already know joining a table more that once is currently not easily possible via the diesel dsl, as this would require support for aliasing. There is #2254 for that. Something like that can be adjusted to work to work in third party crates.


feat(test): Add --config-file flag option to ng test command

Allow for users to optionally specify a path to a karma config file on the ng test command which
will allow for the usage of a karma config file different from that set as the default in the
angular-cli.json file
Fixes: #976

I don't feel this is the correct approach to handle this scenario... I think the option to define the location of a default config file should be set within the angular-cli.json file so devs won't have to pass in a path on every run of ng test

I agree with you on that, and that behavior will remain the same for identifying the default path for the karma config file. This optional flag will give the developer the option to specify a path for different karma config file when using npm test.

Having an option in angular-cli.json is right.
Flag for ng-test is also usable.
For example, I want to run tests with chrome and firefox launchers and only with phantomjs.
Of course, it can be done by looking to process.args in karma.config...

Please update this PR after rebasing on latest master

@Brocco for this feature merge, are you expecting for the dev to define for example a staging environment test file and they could then define that in their project config file as follows: test.karma.staging which would then define the path to their staging configuration file for Karma? This would then eliminate the need for them to pass the path each time and the flag could be used as --config staging

Made the requested changes and committed
On Wed, Nov 23, 2016 at 9:12 PM, Mike Brocchi<EMAIL_ADDRESS>wrote:

@Brocco requested changes on this pull request.
Please make the suggested change and appropriate e2e tests.
In packages/angular-cli/tasks/test.ts
https://github.com/angular/angular-cli/pull/1102#pullrequestreview-9971984
:

@@ -13,7 +13,8 @@ export default Task.extend({
const projectRoot = this.project.root;
return new Promise((resolve) => {
const karma = requireDependency(projectRoot, 'karma');

 const karmaConfig = path.join(projectRoot, this.project.ngConfig.config.test.karma.config);

 const karmaConfigFile = this.project.ngConfig.config.test.karma[options.config];

I don't think this should be looking the path up in the config file. The
default file location will suffice, just need to update the content of that
file if different configuration is needed. If an alternative (read:
secondary) config file is needed, for whatever reason than the path to the
new config file is what should be supplied with the --config option.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/pull/1102#pullrequestreview-9971984,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ9WvTMxaYTsJOfmBHBaC_qXwOsguMx0ks5rBPKmgaJpZM4I282C
.

--
Marc Sensenich
email<EMAIL_ADDRESS>

https://github.com/angular/angular-cli/pull/4564 got merged meanwhile. Sorry it wasn't your PR instead, which was much older :/

As per CLI help, *ng test --karma-config=karma.conf.js
CLI Help screenshot:


HTTPResponseError code in "Handling client and server errors" section is incorrect.

Sample code provided for "Handling client and server errors" section on main page is invalid. See: https://github.com/node-fetch/node-fetch#handling-client-and-server-errors
class HTTPResponseError extends Error {
	constructor(response, ...args) {
		this.response = response;
		super(`HTTP Error Response: ${response.status} ${response.statusText}`, ...args);
	}
}

trying to use code will fail with runtime exception. WebStorm shows problem: 'this' is not allowed before superclass constructor invocation.
..args should be removed, node Error constructor only supports a single string argument. See: https://nodejs.org/docs/latest-v10.x/api/errors.html#errors_new_error_message

Reproduction
Steps to reproduce the behavior:

Copy and use sample code from "Handling client and server errors" section.

Expected behavior
Modified code that works should be like:
class HTTPResponseError extends Error {
	constructor(response) {
		super(`HTTP Error Response: ${response.status} ${response.statusText}`);
		this.response = response;
	}
}

Screenshots

Your Environment

software
version

node-fetch
2.6.1

node
14.15.4

npm
6.14.11

Operating System
Windows 10

Additional context

looking into this issue

PR created - https://github.com/node-fetch/node-fetch/pull/1666


Unable to customize elfeed-use-curl?

Hi Chris,
I just noticed a strange problem:

customize-group elfeed
Scroll down to Elfeed Use Curl.
Click the arrow to expand it.
Error (used kill-rectangle because the whole backtrace is too long to paste here):

Debugger entered--Lisp error: (void-fu
  nil((bool) t)
  widget-apply((bool) :match t)
  custom-variable-value-create((custom
  widget-apply((custom-variable :group
  widget-default-create((custom-variab
  widget-apply((custom-variable :group
  widget-default-value-set((custom-var
  widget-apply((custom-variable :group
  widget-value-set((custom-variable :g
  custom-redraw((custom-variable :grou
  custom-toggle-hide-variable((custom-
  widget-apply((custom-visibility :arg
  widget-apply-action((custom-visibili
  widget-button-click((down-mouse-1 (#
  funcall-interactively(widget-button-
  call-interactively(widget-button-cli
  command-execute(widget-button-click)

I reproduced it in emacs -q by:
(require 'package)
(setq package-archives '(("gnu" . "https://elpa.gnu.org/packages/")
                         ("melpa" . "https://melpa.org/packages/")))
(package-initialize)
(require 'elfeed)

Am I doing something wrong?  :)
Thanks.

It just had the wrong customization type name for elfeed-use-curl. The
stack trace you provided made this trivial to sort out, thanks!


TFS113219 Need to document IPv6 address support of URI constructor ap…

TFS113219 Need to document IPv6 address support of URI constructor appropriately
Adding the necessary info that an IPv6 address in string form must be enclosed in brackets.
Updated System.Uri constructor topic
Describing and illustrating the correct string format for an IPv6 address.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks for adding this detail, @stevewhims. LGTM.

Thanks, Ron! :)


set authenticate to false on currencyDAO

need the currencydao to not be authenticated for ratediscovery model's currency selection

@noodlemoodle are we hitting the currencydao directly, or are we looking up currencies which have been provided based on paymentprovidercorridors and such?
It's

to/from country list based on payment providers in system
for a country corridor, a set of to/from currencies are available.

@jlhughes we need it filtered by eligible payment providers for the spid. @noodlemoodle so yes, my understanding is..  instead of hitting currency dao specifically we need to hit available corridors, and return all "from" currencies. then when one is selected, on the "to" field we again hit corridors, and then get all "to" currencies, and filter by the matching ones with the from selection.


getVersion is not defined

🐛 Bug Report
Jest v24 crashes with "getVersion" is not defined.
To Reproduce
See source code.
Expected behavior
Jest does not crash.
Issue in source
This line requires cli.
But cli itself requires jest here. Clearly, getVersion is not exported at this point.
Run npx envinfo --preset jest
Paste the results here:
System:
    OS: Windows 10
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Yarn: 1.10.1 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

I had the same experience as @bricss. require('jest-cli/build/cli'); did not work for me, but require('jest/node_modules/jest-cli/build/cli'); did. Former CRA app, latest version, ejected quite recently.

To break the dependency cycle, we can delete the module cache and require it again
in scripts/test.js:
delete require.cache[require.resolve('jest-cli/build/cli/index.js')];
const cli = require('jest-cli/build/cli/index.js');

24.1.0 is released


Shaders timer; toggle on port 2 digital output

@bruno-f-cruz Hi Bruno,

I manually merged your recent pull request related to the digital input parsing using the updated API as there is a conflict with the current main branch.

The following are just some illustrations of the problem we need to solve.

Shader timers. Currently, my workflow is stuck on shader timer nodes.
Should I still use Behavior.TimestampedOutputToggle to toggle the port 2 digital output? I can't receive the timestamp.

I dont have an board with me at the moment, but your problem might be the "DistinctUntilChanged". Can you plot the values that arrive at "Value" and "BitWiseAnd" and "DistinctUntilChanged" node simultaneously? Disabling the node will probably be enough to make it work.

Check  #4 for a try at solving the first problem

Hi Bruno,
Both of these issues were solved.

I manually merged your pull request related to the shaders timer. It works. I am running some sessions to see how accurate of the shaders timer and will keep you posted.

Disabling the "DistinctUntilChanged" node works.

closed by #4


Improve ping functionality related UI

Summary
Currently, UI related to check connection for specific controller is a little bit confusing. It should be enhanced so that user understand what issues is he facing of.
Details
Check connection button should be visible for every controller definition - it should be enabled/disabled depending on the canPing method result.
Additionaly message which is now displayed for every controller when Check connection button is unavailable shoud be moved from the top of the page next to the button (warning icon displaying the details of the problem when clicked).
Messages related to Check Connection button result should stay in the top part of the page.
Acceptance criteria

No error message related to checking connection possibility in the top of the page.
Check Connection button displayed (enabled/disabled) for every controller configuration.
In case of button is disabled, warning icon displayed next to it - clicking on warning icon should open the popup with detailed message describing the issue

Additional context
Exemplary screen:

Ok, but instead of disabled buttons and warning icons just put a label here "Not configured.".

@GoebelL But what if controllers is configured, but exception will be thrown during checking the settings? Should it also display this 'Not configured' label in this case?

Closed with #245


Support for http.ClientRequest#setHeader, #getHeader, #removeHeader

I'm developing a library to consume an HTTP API. I'm seeing the following error since adding an edge case that requires the usage of http.ClientRequest#setHeader:
     TypeError: Object #<EventEmitter> has no method 'setHeader'
      at [object Object].apiCall (/Users/james/Projects/urban-airship/lib/reques
t.js:112:9)      at [object Object].get (/Users/james/Projects/urban-airship/lib/request.js
:129:15)

The lines in question:
  if (typeof data !== 'undefined') {
    encodedData = JSON.stringify(data);

    // THE NEXT TWO ARE THE OFFENDING LINES
    req.setHeader('content-type', 'application/json');
    req.setHeader('content-length', encodedData.length);

    req.end(encodedData, 'utf8');
  } else {
    req.setHeader('content-length', 0);
    req.end();
  }

Where req is an instance of http.ClientRequest.

I found it. Check out how requests are intercepted and then the mock request is returned. In the linked bit of code, a new EventEmitter is instantiated and then ultimately returned. An EventEmitter doesn't quack like an http.ClientRequest completely, ergo problems like this will show up. IMHO a neutered version of http.ClientRequest should be returned instead.

I have a solution, but it may not be ideal. Is there a reason we're not returning a new OverriddenClientRequest this already, or were we just assuming that was the case?

Thanks for the contribution!
nock v0.10.4 released.


Update openstack environment builder

Updating the Openstack environment builder to handle projects/tenants and create all test objects in that context

@Fryguy Please review
cc @jvlcek @blomquisg

@brandondunne LGTM, I only had 1 question, on 2 locations, for you to confirm.

Thanks @jvlcek I addressed your concerns

Thanks @brandondunne LGTM :+1:

Updated for both Havana and Grizzly


haruna: 0.8.0 -> 0.9.1

Description of changes
Upstream update and patch in list to yt-dlp so it is actually found.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Replaces #187628

Result of nixpkgs-review pr 188348 run on x86_64-linux 1

1 package built:

haruna


My settings to exclude folders don't work

I add the configuration but it does not respect it when generating the structure

Hey my friend!
If you are trying to avoid showing the objets folder, delete the last ‘/’ and try again. Like this "**/objects".
If it doesn't work let me know!

If you want to match node_modules directories regardless of depth, you could use a pattern like '**/node_modules'.
example :
"draw.folder.structure.exclude": [
"/node_modules",
"/.git",
"/dist",
"/out"
]

f you want to match node_modules directories regardless of depth, you could use a pattern like '**/node_modules'


wip: arc-theme: 20210127 -> 20210412, switch to meson

Motivation for this change
It looks like it needs an update for GNOME 40.
doesn't build yet = draft
now it builds, but I haven't tested it yet.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Doesn't build currently due to the treewide gnome3 -> gnome rename.

I can confirm that the commit that I linked works for me.

I also tested this on nixos-unstable and it worked great. Just needed to s/gnome3/gnome/.

Result of nixpkgs-review pr 122086 run on x86_64-linux 1

1 package built:

arc-theme


[new product] chef-client.md

add new product chef-client

update eol and support date

Seems good to me

Glad to see someone adding this project. As a past Chef developer and later the PM for the client I would call out that the project name hasn't been Chef Client for a number of years. This should be updated to be Chef Infra Client, which is the name of the project currently. Other than that it looks great.

@tas50 thanks for your feedback, I updated the PR

Still draft or ready for review ?

@marcwrobel, I am waiting to have some time to work on #4425
I will put this PR in ready for review when I find a solution for the other one

There's a lot of release dates here that still need to get updated. I think some of this is confusion on how Chef's version numbers work. When I used to do these releases we would cutover master/main to the new version sometime in January to start prepping things for our yearly April release. The first commit afer this bump will become say 17.0.0 and every release after this continues to bump the minor version. This was done as each commit builds a package that users can download from the current build repo. When we were happy with things and wanted to do the release we'd just tag a build "stable" and ship it. That means for something like 16.0 the first released version is actually 16.0.275 in May when the 16.0.0 tag is all the way back in Jan. TLDR: Don't trust the github tags.

@marcwrobel is everthing ok for this PR ? is it ready to land or not ?

@nperez60 I updated the latest release version. This should be good to go @marcwrobel

@nperez60 can you pull in the latest version here?

@tas50 done! sorry 😅


Showing the UI is to slow and tedious

Extension Version: 0.4.5
VS Code Version:  1.45.0
OS Version: 10.11.6 osx

Using that alt + c + p is to tedious, after that I need to click again before it shows. WHy not s single shortcut. Another issue, why does it take so long to show?

Hi @schroef, thank you for the comment.
The performance of the UI that based on Electron depends on environment.
Only first starting might be time consuming work for your computer.
Could you make new issue for another topic after close this issue if it was solved?

I'll check it again and will update t
With different post

Maybe, you had better to use internal Color Picker of VS Code instead of the extension because the Electron seems to be high-load for your computer.

Hello, I have a problem with Color Picker, it doesn't work with Alt + C + P or Ctrl + Shift + P and I write Pick Color.
This is my information:
VSC Version: 1.45.1
OS: Linux Ubuntu 20.04lts x64 5.4.0-29-generic snap
Color Picker: Version: 0.4.5

Hi @danilogonzalez-mcs, thank you for the comment.
Could you make new issue for another topic?

Hi @danilogonzalez-mcs, thank you for the comment.
Could you make new issue for another topic?

Ok sorry

No reply came, then this abandoned issue is closed.


Updating primitives names for 'pnp' bjt devices in lvs gds files

Fixes https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/issues/1

Renaming pnp bjt devices with its new name in the gds files used in LVS testing under the following directory:

globalfoundries-pdk-libs-gf180mcu_fd_pr/rules/klayout/lvs/testing/testcases/

@mithro Changes is completed including cap_mim as you agreed with @atorkmabrains


Include new pages under "who am i"

popup for about me section with minimal intro about the person

I want to work on it, assign this to me

update me when you are done with the pages done

hey can u assign this issue?

Yes @Vipul-Ydv, you are also assigned to this issue

please let me know if people are still working on this feature, react to this message


The plugins firebase_auth use a deprecated version of the Android embedding.

I have a problem downloading the plugin. I use flutter version 3.3.8. The message that I get when I run flutter pub get is this:
The plugins "firebase_auth" use a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if these plugins support the Android V2 embedding. Otherwise, consider removing them since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.

Hi @thaliachitziou99, firebase_auth is a third-party plugin. Any issues you face using it should be reported on their repo.
I'll be closing this as this issue is not related directly to the flutter repo.
Kindly make sure you're using the latest version of the plugin because as far as I understand, they have migrated to from the v1 embedding for quite some time now.


GovLens Logo!

We need a logo for the project. Should gather some feedback here on what kind of messaging the logo should represent, as well as making sure it follows accessibility best practices.

Ehhh it's a transparent ping so doesn't look great in preview but it's done!


Some of the enemies are not spawning.. (maybe outside of the screen?)

Describe the bug
Sometimes the spawner chooses a location outside of the play area
To Reproduce
Steps to reproduce the behavior:

open game
wait for new spawn time
count the enemies.
4 sometimes there will be fewer enemies than what it should be

Expected behavior
There should be a set number of enemies at this state in the game. per each 600 ticks.
Screenshots
If applicable, add screenshots to help explain your problem.
nah
Desktop (please complete the following information):

Windows 10
commit https://github.com/datWaffle21/MyFirstGameRemastered/commit/2689a88adc08f25e925ed90f525fbf7153e2771b

Smartphone (please complete the following information):

nope

Additional context
Add any other context about the problem here.
not a huge issue but kinda annoying and a potentially easy fix

Fixed with latest Commit! https://github.com/datWaffle21/MyFirstGameRemastered/commit/ae149806216e8e2a09998995eb60da650e8d6d97


Co-exist with starlight documentation

Is your feature request related to a problem?
I have starlight docs page that lives at /docs on my website. I'd love to also have a /blog route that uses this package but I wasn't able to get the two to co-exist.
Describe the solution you'd like
Do you know if it's possible or how difficult this would be to support?
Describe alternatives you've considered
No response
Additional Context
No response

Thanks for your feedback.
Are you using something like the "Use Starlight at a subpath" guide (and your docs are in a src/content/docs/docs/ directory? Or some other setup?

Yes that's correct. I tried adding the blog to src/content/docs/blog as well as src/content/blog/blog and had issues with both. I didn't expect it to work since starlight-blog overrides some components so I figured it would mess with the docs.

I setup a repro in a StackBlitz using the following steps:

Start from a fresh Astro installation
 Add Starlight to an existing Astro site
Setup Starlight at a docs subpath
Install starlight-blog

And everything worked out of the box for me. Here is the link to the StackBlitz.

/ is a classic Astro page in src/pages/index.astro
/docs is a Starlight documentation in src/content/docs/docs
/blog is a blog using starlight-blog in src/content/docs/blog

Maybe the StackBlitz can help you figure out if this is a configuration issue on your end or if you are still encountering issues, would you mind providing a repro?

Thanks so much! I'll check it out and report back

It worked! I think what I did before was injecting a step that wasn't necessary and broke it. Amazing! Thanks @HiDeoo

Thanks for taking the time to check it out, really appreciate it!


chore(build): Refactor codegen traits

Signed-off-by: Lucio Franco<EMAIL_ADDRESS>

I don't mean to intrude here, but why was build.rs code changed back from tonic_build::prost::compile_protos to tonic_build::compile_protos? That is what the file originally was...

We just re-export the prost version, since that is the default we want users to use. If you disable the feature you need to go through lower-level functions to get the functionality.

Right now, we don't have fbs support yet but that has not been mapped out yet! Likely, for the first phase of fbs we will expose a fbs compile_protos and still leave the prost one as a default until we find a more ergonomic method.
The plan though is to still keep prost as the main proto spec.

Right now, we don't have fbs support yet but that has not been mapped out yet! Likely, for the first phase of fbs we will expose a fbs compile_protos and still leave the prost one as a default until we find a more ergonomic method.
The plan though is to still keep prost as the main proto spec.

Since it has been a few months, I wanted to stay up-to date. Is the flatbuffers support out yet, or would it be in the near future?

@msinojia doesn't seem like the work has been completed on the fbs implementation and some of this work has stalled. I don't think we currently have a clear plan for it until someone is ready to drive it. I likely won't have time since there are some other priorities for tokio that need to be done and we don't require fbs at work.


update dependencies to support latest Gren version(0.4.4)

To support the latest version of Gren(0.4.4), the dependencies in this package were updated.
Let me know ifd there's anything else that would need to be done.

@ajstrand Thanks for reminding me this needs to be done! There are a few errors that I noticed when building the package - I had enough time tonight to fix up the mimeTypes issues. There's some refactoring that needs to be done given the file system part of the node package changed quite substantially in the latest version. I'll try to get to it later this week, but would welcome any progress towards the required changes!

@joeybright thanks for the comment! Im new to gren/elm.
I can take a look at file system API refactoring and see if im able to help at all there.
Is building the package with gren/node enough to spit out errors that i can work on fixing?
Or are there more steps to test the package?

@ajstrand You should be able to clone the package locally, run gren make in the project root, and it'll spit out any errors. I don't have a test suite for this package (the built-in gren testing doesn't support testing Task type for good reasons, which this package mainly uses and returns), but I do have some private codebases that leverage the package. So, when gren make runs without error, I can test the updates on those!

@ajstrand I got some time and was able to get rewrite the package to get it compiling with 0.4.4! I have yet to do any testing, though, and won't be able to get to it for a bit. So, if you're still interested in contributing, writing a test app would be a great help. Otherwise, I'll do some testing when I have the time. If you need any help or have any questions, let me know!

@blaix Thanks for looking into this a bit more! I spent some time earlier this morning testing. I rewrote a large portion of the logic so that everything works as expected. I'd like to do a bit more testing tonight before committing the code, though. If you have the bandwidth, after I commit my updates, it'd be helpful if you could make sure they work for you. Having another pair of eyes is always good!

@joeybright The changes are working great for me, thanks!


fix: UI bug debug tab : System Information

This is a fix for #749

Br,
Stijnus

works on windows, thanks @Stijnus


MViTv2 on UCF101 and HMDB51

Thanks for your outstanding work! Both Mvit (with pooling) and Swin (with window) reduce Network complexity, giving me hope to implement it with my machine. Even if I prefer Mvit with its simpleness, I meet great difficulty with limited GPUs. So could you pls assist in :

efficient speedup strategy. (MViTv2_S is still enormous for me, and I mean some efficient video strategy. if have)
config and models on UCF101 and HMDB51. (Perhaps transformer and new architecture donnot work on these tiny datasets, but these are my last hope. BTW, both fine-tune and scratch are crucial for me
I just wanna cry for low accuracy on UCF, but it's much better for  the long wait for several months on k400
UCF and HMDB dataloader. (I define the ucf.py and hmdb.py by employing almost the same code in kinetics.py, and more advanced implementation of dataloader is also essential.

There seem to be many issues, and addressing them maybe needs many resources. However, if you have any ideas about any of them, pls contact me at<EMAIL_ADDRESS>Looking forward to your reply. LOL @lyttonhao @haooooooqi

Hi,

We have the smaller model MViTv2_T in the model zoo.  You could also explore different network designs (e.g. reducing network depth/width and increase pooling size)
We don't run experiments for UCF101 and HMDB51 datasets, so we don't have the dataloaders.


Adds more content to index.html and creates 3 new html files

The 3 new html files are tennis.html, travel.html, and personalblog.html.

The title / desc look good!


Error?

What does that mean?
It lauched perfectly without error (so it showed me settings, like 2 sec delay, whitelist etc in cmd). Next it spams only this text...
It doesnt catch me pokemon.
I put channel id in whitelist. This also not worked, so I inserted my channel id into pokeball.py. Still no catching.
What do I miss?

Hmm, this happens when you get DMs but not sure why this error is popping up for you.
Technically, message.guild should return None instead of an AttributeError.
Possibly a change in discord.py. Well, I'll send a fix for it soon along with other fixes.


Issue of after the match ended and in lobby

Description

Screenshots

Additional context

edit the issue or open a new issue with information please


Global Reader Role Limitation for Intune Portal

Global Reader role does not have the capability to view the in-depth settings for Windows Information Protection within Intune portal > app protection policies.

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

ID: 0767aac4-fcd9-eaac-2c30-8f17d8eadd92
Version Independent ID: a380a828-03f9-e037-3a62-e4165fda7cb6
Content: Azure AD built-in roles - Microsoft Entra
Content Source: articles/active-directory/roles/permissions-reference.md
Service: active-directory
Sub-service: roles
GitHub Login: @rolyon
Microsoft Alias: rolyon

@the-cory-smith
Based on the document you followed, the Global Reader role does not have the capability to view the in-depth settings for Windows Information Protection within Intune portal > app protection policies. This is because the Global Reader role is a read-only role that allows users to view resources but not make any changes to them.
If you need to view the in-depth settings for Windows Information Protection within Intune portal > app protection policies, you will need to have a role with higher permissions, such as the Intune Administrator or Intune Service Administrator role. These roles have the necessary permissions to view and modify app protection policies in Intune.


[Feature] - Verified Plugin icon for installed plugins

Before Requesting

[X] I found no existing issue matching my feature request

Describe the feature you'd like!
Display a verified symbol/icon next to installed plugins that came from betterdiscord.app, making sure that the files are unmodified from the currently verified version on the website.
This will help quickly knowing which installed plugins are verified to be safe, allowing users to easier find plugins that were manually installed from unverified sources.
Anything else?
No response

This is the same concept as #1391 going to condense them


feat(design): form component

Description

Fixes #141
Fixes #140 too
Check this out for more info:
https://slime-gouda-96f.notion.site/Form-Component-7c971d27708b41709cdc8d483dc1d9c5?pvs=25
Checklist

[ ] My code follows the contributing guidelines of this project.
[ ] I am aware that all my commits will be squashed into a single commit, using the PR title as the commit message.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code in hard-to-understand areas.
[ ] I have updated the user-facing documentation to describe any new or changed behavior.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have not reduced the existing code coverage.

Comments

Hey guys @SalihuDickson @JaeAeich, this is ready to be merged so that @JaeAeich or @SalihuDickson can start the work on the migration of the TES create to lit with the design package. Note that the CSS part functionality is not implemented but will be done soon! This merge is to unblock the migration as it will help define the design package APIs better (so that migration can start for other packages too).
Note: There is a new package here by the name of lit-tes you can use that for the migration design package & all other templating is already handled in this PR.

Is is rendering anything? Mine is throwing some errors and and blank screen on run dev.

Is is rendering anything? Mine is throwing some errors and and blank screen on run dev.

Yes lit-tes package is working fine on my end! What is the error it is throwing?


Code Insights for Apache StreamPipes

Body
Apache StreamPipes
Apache StreamPipes (incubating) is a self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore IoT data streams. StreamPipes offers several modules including StreamPipes Connect to easily connect data from industrial IoT sources, the Pipeline Editor to quickly create processing pipelines and several visualization modules for live and historic data exploration. Under the hood, StreamPipes utilizes an event-driven microservice paradigm of standalone, so-called analytics microservices making the system easy to extend for individual needs.
Background
StreamPipes is grown significantly throughout recent years. We were able to introduce a lot of new features and attracted both users and contributors. Putting the cherry on the cake, we were graduated as an Apache top level project in December 2022. We will of course continue developing new features and never rest to make StreamPipes even more amazing. Although, since we are approaching with full stream towards our 1.0 release, we want to project also to get more mature. Therefore, we want to address one of our Achilles' heels: our test coverage.
Don't worry, this issue is not about implementing myriads of tests for our code base. As a first step, we would like to make the status quo transparent. That means we want to measure our code coverage consistently across the whole codebase (Backend, UI, Python library) and report the coverage to codecov. Furthermore, to benchmark ourselves and motivate us to provide tests with every contributing, we would like to lock the current test coverage as an lower threshold that we always want to achieve (meaning in case we drop CI builds fail etc). With time we then can increase the required coverage lever step to step.
More than monitoring our test coverage, we also want to invest in better and more clean code. Therefore, we would like to adopt sonarcloud for our repository.
Tasks

[ ] calculate test coverage for all main parts of the repo
[ ] send coverage to codeCov
[ ] determine coverage threshold and let CI fail if below
[ ] include sonarcloud in CI setup
[ ] include automatic coverage report in PR validation (see an example here) -> optional
[ ] include automatic sonarcloud report in PR validation -> optional
[ ] what ever comes in your mind 💡 further ideas are always welcome

❗ Important Note ❗
Do not create any account in behalf of Apache StreamPipes in Sonarcloud or in CodeCov or using the name of Apache StreamPipes for any account creation. Your mentor will take care of it.
Relevant Skills

basic knowledge about GitHub worfklows

Learning Material

GitHub workflow docs
Apache StreamPipes workflows
Sonarcloud for Monorepos
Using code cov for a monorepo: https://www.curtiscode.dev/post/tools/codecov-monorepo/ & https://docs.codecov.com/docs/flags

Mentor

Tim Bossenmaier (bossenti[at]apache.org).

StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.

This issue is intended to be a suggestion for this year's GSOC.
If you are interested in taking part at GSOC via the ASF, please have a look on this guide: https://community.apache.org/gsoc.html
In case there are any questions related to the GSOC process or this issue in particular, feel free to reach out to us 🤝

PS: If not already done, it would be great if you could subscribe to our mailing list<EMAIL_ADDRESS>

@Kshitiz-Mhto if you are still interested in working on this topic as part of this year's GSOC, I would like to kindly remind you to write your project proposal and submit it by 2023/04/04 (https://summerofcode.withgoogle.com/programs/2023).
Here is more information on how to write a proposal: https://google.github.io/gsocguides/student/writing-a-proposal
In case there any open questions, feel free to reach out
Good luck 🙂

hello @bossenti
would you provide your feedback on my proposal demo link: PROPOSAL-5.pdf
Schedule  of Delivery hasnot be fixed yet, i m working on it., Thank you

Hi @Kshitiz-Mhto I've read your proposal
Thanks for putting that much effort into it.
As of now I'm not sure if I'm allowed go provide you with feedback policy-wise (both Google and ASF)
I'll add some comments in the Google doc if it's possible
Otherwise I would strongly encourage you to submit your proposal as it is before the deadline passes 🙂

Hi @Kshitiz-Mhto I've read your proposal Thanks for putting that much effort into it. ....

Thank you! some comments in the google docs would be wonderful. I would really appreciate your feedback and will make changes according to your feedback. Thank you.

@Kshitiz-Mhto can you provide me with a link that allows me to add comments to your GDoc? 🙂

@Kshitiz-Mhto can you provide me with a link that allows me to add comments to your GDoc? slightly_smiling_face

here it is @bossenti  https://docs.google.com/document/d/1Prp3sv5IVTnNNliwr58FOcvAUwqjyuhc7qaqLy3vYrg/edit?usp=sharing

hello @bossenti ,  unfortunately i didnt get selected this year but can i still work on this issues ?

Hey @Kshitiz-Mhto that's sad to hear, but really great that you are still motivated to take on this task.
We would really appreciate any contribution here though 🚀
With which part of the whole aspect would like to start?
I would suppose to define some dab tasks for this quite large topic. For example, we could start with the Python part, try everything out and then adopting for the UI and the backend.

@Kshitiz-Mhto since I didn't hear from you again, I'm assuming you are no longer willing to support here, right?


pull request template updated for title standardization

Description
Suggestion - The PR title can be standardized to include the issue id and type to get a better context of the PR ex: [FIX/FEATURE - #ISSUEID]
Fixes # (issue)

not yet created

Type of change

New feature

How Has This Been Tested?

None required - making template changes

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Will this work?

/ok-to-test sha=45cda3b


Adds command to generate a varied trigger history for manual testing

Codecov Report

Merging #191 into master will decrease coverage by 1.20%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #191      +/-   ##
==========================================
- Coverage   89.26%   88.05%   -1.21%
==========================================
  Files         114      115       +1
  Lines        2404     2437      +33
  Branches      430      436       +6
==========================================
  Hits         2146     2146
- Misses        256      289      +33
  Partials        2        2

Impacted Files
Coverage Δ

src/cli/pushhost.ts
0.00% <0.00%> (ø)


Suggestions - Add additional configurations, add CI, add integration tests

Hey!
I had a ton of ideas that I wanted to put into the project. I have been thinking about it all day.
I figured that users may want to change the threshold of the backlights. Also, I thought it would be great to allow users to change the backlight max and min values so they can adjust what intensity they prefer.
While I had some of those configurations taken care of, I needed to make sure that I wouldn't get anything funky as input so I decided to use one of my good old tools, Cerberus, to validate a schema.
It doesn't take care of everything, so I had to make sure that the backlight_min_value is lower than backlight_max_value. The same goes for red_threshold and yellow_threshold.
Since I added some dependencies, I wanted to make sure that they stay up-to-date, so I added dependabot to open PRs for us when an update of our dependencies is available.
I created a few tests as well, so I created a CI to run them and added the status in the README.md.
If you have any questions, don't be shy to ask me.

Starting to make me feel obsolete, looks awesome!