Is there a way to make this script start automatically when starting any video?

First of all thank you very much for this script I use Anime4k in a standard way so it works great for me to load the necessary scripts depending on the resolution of the video, only that I would like this script to always start in each video since I have to copy the file "Anime4K_jbgyampcwu" each anime folder or type the command to activate since I watch a lot of anime broadcast with Streamlink. thank you

The script is designed to "Non-invasive" at the beginning (only work when user request), so it does can be annoying for people who indeed have vast amount of anime.
You can use text editor supports "UTF-8 no BOM" format to open AnimeAnyK.lua,
for example, notepad.exe after Windows 10 22H2, almost any Linux text editor, notepad++, Visual Studio Code.
In text editor, search function Core_jbgyampcwu.GetIndicatorFileStatus(),
between local indicatorFileFullPath... and -- Try indicator file exist,
insert a new line return true, indicatorFileFullPath,
delete all line until keyword end
It will look like this:
... (other code)

function Core_jbgyampcwu.GetIndicatorFileStatus()
    ... (other code)
    -- Fill parent folder
    local indicatorFileFullPath = mpUtils.join_path(fileParentFolder, indicatorFileName)
    return true, indicatorFileFullPath
end

...(other code)

Then the script should enable on any video you've opened.
When you press script bind key, you can clear your GLSL, but not able to use it to enable again.
In this case, close video player and open again to get GLSL enabled.

thank you very much, it works quite well :)

Hi, 1.2 was released, so you don't need to hack the script anymore.
Download directly from master branch or look at Release page.
Go to line 25, change from AlwaysOn = false, to AlwaysOn = true,.


Typescript Typings

@uqee - just wanted to give you a heads up I have submitted a PR to add typings to definitively typed to help out folks using Typescript - https://github.com/DefinitelyTyped/DefinitelyTyped/pull/21750
Would you mind glancing at the test I wrote and confirm it looks consistent with how your library should be used?  I looked ad your index.js and it seemed fairly simple in the way things were initialized, so I am hoping I got it right.
Thanks
Test for typings
example of typescript compiling without type errors using typings
import * as stickyCluster from 'sticky-cluster';
import * as express from 'express';
import * as http from 'http';

/** test with all params */
stickyCluster(
    (callback) => {
        const app = express();
        const server = http.createServer(app);

        // don't do server.listen(), just pass the server instance into the callback
        callback(server);
    },
    {
        prefix: 'sticky-cluster:',
        concurrency: 10,
        port: 3000,
        debug: true,
        hardShutdownDelay: 60 * 1000,
        env: (index) => ({ stickycluster_worker_index: index }),
        errorHandler: (err) => { console.log(err); process.exit(1); }
    }
);

/** test with no params */
stickyCluster(
    (callback) => {
        const app = express();
        const server = http.createServer(app);

        // don't do server.listen(), just pass the server instance into the callback
        callback(server);
    }
);

Type Definition
// Type definitions for sticky-cluster 0.3
// Project: https://github.com/uqee/sticky-cluster
// Definitions by: Austin Turner <https://github.com/paustint>
// Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped

/// <reference types="node"/>
import * as http from 'http';

declare namespace stickyCluster {
    type InitializeFn = (callback: Callback) => void;
    type Callback = (server: http.Server) => void;
    interface Options {
        concurrency?: number;
        port?: number;
        debug?: boolean;
        prefix?: string;
        env?: (index: number) => { stickycluster_worker_index: number };
        hardShutdownDelay?: number;
        errorHandler?: (err: any) => void;
    }
}

declare function stickyCluster(callback: stickyCluster.InitializeFn, options?: stickyCluster.Options): void;
export = stickyCluster;

Thanks! Looks good )


Create Pattern36.c

PATTERN
Write a C program to print the below pattern.

@20a31a05e8 thanks for your contribution but currently I will not be able to merge this as It is already assigned to someone else. But you can show you interest for the issue #58.

ok @Vishal21121


avoid naming files as "aux.S"

See https://github.com/mupq/pqm3/issues/13 and https://github.com/mupq/pqm4/issues/216.

resolved by commit 23a3fe87efe6594cac0cfaee55ef8a86896f6f65.


Added check for any invalid objects present in the database

Insert a check for invalid objects that can fail at build time to prevent deployment of invalid objects to upstream environments

The two most recent commits have switched to treating the file as binary rather than text. This needs to be resolved before merging (not by Chris Unwin, but one of the reviewers should be able to do this).

Superseded by #6


How do we access the input values?

Hey there - awesome plugin!
How can we access the input values after the user submits - so that we are able to evaluate the entered credentials?
Thanks again!

You should be able to access the user's input data  from within the callback. Examples for each of the dialog types are provided in the readme.
For example:
var options = {
    title: "Change Password",
    message: "Please change your password.",
    minLength: 8
};

PasswordDialogPlugin.showChangePassword(options,
    function(result) {
        if (result.cancel) {
            console.log("User cancelled the change password dialog.");
        }
        else {
            console.log("User completed the change password dialog.", result.currentPassword, result.newPassword);
        }
    },
    function(err) {
        console.log("Change password dialog error.", err);
    });

@Justin-Credible I actually just saw that - so for the username, is it just result.userName?
Thank you again!

Yep, you can see the types here:
https://github.com/Justin-Credible/cordova-plugin-password-dialog/blob/master/typings/cordova-plugin-password-dialog.d.ts#L93

Thank you again, have a great holiday!


Toolbar icons not resized horizontically

When resizing the tool bar with fb_toolbar_size:x, the icons are resized vertically but not horizontically.

Fixed with https://github.com/alex0809/netsurf-base-reMarkable/commit/134cd55cbf4d69d4fc6fb656f5b789b8623c80e7


Feat(grid): horizontal scroll

Todo:

[x] fix/add tests
[x] disable strategy if virtualScroll is enabled
[x] fix unsynchronized animation  action buttons & hover background
[x] hover on resizing handle should have a less contrasting color

To be addressed in a future PR

[ ] fix frozen-boundary, sometimes it vanishes on resize
[ ] resizing handler should cover row borders

Tracking the remaining work in Jira

don't forget to 🍒 to master


How can I open the website?

Hello, you have built a really nice site! I want to run it on my own pc to modify it, but I can't find the index.html file. I am really new to web dev, so could you please tell me how to run the side locally?

Hello, you have built a really nice site! I want to run it on my own pc to modify it, but I can't find the index.html file. I am really new to web dev, so could you please tell me how to run the side locally?

You can refer this video: https://youtu.be/EdlGgn9uhPU

Hello, you have built a really nice site! I want to run it on my own pc to modify it, but I can't find the index.html file. I am really new to web dev, so could you please tell me how to run the side locally?

She has mentioned everything, and web development completly based on javascript.....  simply install npm,nodejs,gatsby plugins, and build the static ..... one thing gatsby, nodejs higher than 10v


Update settings.py

Dummy keys are added for testing

Oh they're dummy! Lol ok

is there any chance that you could merge this? The keys are dummy not real ones. Thank you

Well, I don't really want to be the gatekeeper for this going forward, but since you're asking me to, no, I won't merge this. Here's why:

if you define the keys here, how would the try ever fail?
if you define the keys here, you need to manually exclude these lines in git to avoid committing keys every single time you commit
The API keys are defined in local_settings.py, which is imported after this. I can add a dummy file, and then it will be ignored by git as it's included in .gitignore.


Make accessibility optional and return iOS errors

Hi @laszloblum,
I stumbled upon your fork and I think you made some great additions to the original plugin. I just have two small suggestions to make:

As with the original plugin, errors on iOS just return the string 'error' which is not useful if they occur in production. I'm not really familiar with Swift but I assume what I added should include the original error message.
The accessibility parameter has a default value in your implementation so I also marked it that way in the interface. This makes the method a bit more convenient to use.

Please let me know what you think of these changes.

Hi @mfrey43
I am happy that you like the plugin. Your suggestions are great.
Unfortunately, this work is a contract work with my client (atroo).
So, I don't really want to interfere with them since it is their repo.
I hope they can see your comment and accept your PR.

Hi @laszloblum,
I stumbled upon your fork and I think you made some great additions to the original plugin. I just have two small suggestions to make:

As with the original plugin, errors on iOS just return the string 'error' which is not useful if they occur in production. I'm not really familiar with Swift but I assume what I added should include the original error message.
The accessibility parameter has a default value in your implementation so I also marked it that way in the interface. This makes the method a bit more convenient to use.

Please let me know what you think of these changes.


[Executing] /usr/local/bin/bower install

I am using windows and getting this error when I try to run command.
I have node and bower installed
If this is a BUG REPORT:
$ php bin/console avanzu:admin:fetch-vendor
[Executing] /usr/local/bin/bower install
[Error] The system cannot find the path specified.
If this is a FEATURE REQUEST:

Describe the new feature briefly.
If you consider or have knowledge submit a Pull Request.

Debug info

Component
Version

Symfony version
Your current symfony version

AdminThemeBundle
1.3.5/dev-master/specific-commit/tag

Operating System
Windows or GNU/Linux or other

add configure in comfig.yml
avanzu_admin_theme:
bower_bin: 'your bower bin path'

As described by @englenshan you need define the bower_bin path in config if you are using other than default path. Closing as solved


skip empty string for start position

Hi,
I found out that scanLine() in models/points.go doesn't filter empty string (uint8 = 0) for start position.
This will introduce some weird issues if the input is made from a large buffer, the Key() from first point gonna be a very large string with all the empty string due to the invalid start position.
One of the obvious example is, if you change the value from uswest10 to uswest1 in https://github.com/influxdb/influxdb/blob/master/tsdb/engine/wal/wal_test.go#L327, the test will be failed due to this issue (only uswest1 will fail, uswest2 until uswest100 working fine). The reason is the first key is a large string (350000*uint8 + "cpu,host=A,region=uswest1"), it return no result when we pass in the valid key "cpu,host=A,region=uswest1" to lookup value from map (string comparison failed).

uswest10 (or uswest2 until uswest99) have no issue is because it is not the first point.

I have also created a test for points_test.go, this test gonna be failed without the new changes.
Sorry if my explanation is not clear enough.

Again not sure why ci/circleci test -- TestServer_Query_Aggregates_FloatMany failed as below:
--- FAIL: TestServer_Query_Aggregates_FloatMany (9.65s)
	server_test.go:2499: median - odd count - float: unexpected results
		query:  SELECT MEDIAN(value) FROM floatmany where time < '2000-01-01T00:01:10Z'
		exp:    {"results":[{"series":[{"name":"floatmany","columns":["time","median"],"values":[["1970-01-01T00:00:00Z",4]]}]}]}
		actual: {"results":[{"series":[{"name":"floatmany","columns":["time","median"],"values":[["1970-01-01T00:00:00Z",null]]}]}]}

I have tried to execute test locally as well as docker, success without errors...
I will check if the test fail again...

check this function skipWhitespace at  https://github.com/influxdb/influxdb/blob/master/models/points.go#L723

@oiooj yup I'm doing similar checking, but there is some minor different:
skipWhitespace is skipping for:

' ': uint = 32
'\t': uint = 9

and I'm trying to skip for uint = 0

Thanks @ch33hau.  The fix for this is in the wrong place though.   It should be:
diff --git a/models/points.go b/models/points.go
index 6a2fdad..5fa8021 100644
--- a/models/points.go
+++ b/models/points.go
@@ -731,7 +731,7 @@ func skipWhitespace(buf []byte, i int) int {
                        return i
                }

-               if buf[i] == ' ' || buf[i] == '\t' {
+               if buf[i] == ' ' || buf[i] == '\t' || buf[i] == 0 {
                        i += 1
                        continue

Because https://github.com/influxdb/influxdb/blob/master/models/points.go#L139 is where the start position within the line is determined.

Thanks @jwilder ( and @oiooj too )!
I got hinted earlier but just got it now, yes skipWhitespace is the right method to be modified, I will update it

+1, makes sense to me, but waiting for confirmation from @jwilder

Thanks @ch33hau!

Thanks @otoolep and @jwilder =)


consider a more structured code layout

From my very harsh/critical perspective, go-langserver is rapidly becoming a giant glob of code living in a single directory. This is bad because our code documentation can rapidly become out of date or interconnected pieces can be altered affecting other things unintentionally.
This is less of a "I have a concrete plan" and more of a "let's chat about how we can improve this" issue. Ideally we have a top-down polytree structure without any cyclic dependencies etc.
One good example is how langserver/internal/refs is totally separate from the main package. Granted, more of the external references code in workspace_refs.go can and should be moved away from the main langserver package -- but it's a good reference idea here.
Take this as a plea from me to find and place code that is sufficiently independent and factor it out into smaller separate internal subpackages @keegancsmith :) (I'll be trying to do this actively, too, obviously)

I agree, its organic growth has led to code that could be better structured, so we should do some improvements. I'm not sure if subpackages (excluding for larger bits of code such as refs or symbols) would actually make life easier though. I think the bigger win would be better thought put into how all the shared state is accessed/separated out. Right now we have stuff split out over files in a haphazard way, but it is all essentially doing things to LangHandler. So that seems like a good win rather than just moving code around.
BTW I don't see our code layout as a bad thing. I'm glad we got to this point of confusing code! Because now I think it is more obvious how we can improve the codebase, than if we designed it upfront when all we supported was hover, ref and j2d. But yes, prioritizing some refactoring/cleanup work is super important, especially if we want more outside contributors to not just run away when they open up this codebase.

I'm going to try ship a few small changes this week which should start shaping us to a codebase that makes more sense. The mini-goal I set this week is making https://godoc.org/github.com/sourcegraph/go-langserver/langserver look reasonable. The first PR is here https://github.com/sourcegraph/go-langserver/pull/87


Ability to add the authors for each line of code

Ability to add the authors for each line of code from GIT.

Hi @230116885230116885,
You mean a git blame view similar to the github one?
This is something that an extension (such as the great brackets-git) should handle instead of Brackets core. I suggest you repost your feature request to brackets-git 👍

Yes. Thank you.
https://github.com/zaggino/brackets-git/issues/1310


Add Search Algorithm implementation in C/C++

Could you be more specific?

@BrunoTissei A binary sort and a ternary sort could be starting points.

@erilyth Ok, in progress.

Any search algorithm in c/c++?

@TuhinKundu Anything that hasn't been implemented and is related to search algorithms. (Preferably with a README file explaining the algorithm)


WIP: Add HAProxy monitoring

This is abusing host-api a bit.  The change makes it such that if you run -haproxy-monitor it will run in a different mode in which it just monitors the haproxy socket and reports the status to cattle.
The host-api will run in the network agent in this mode, not in the rancher-agent container.

@cjellick This is mostly done, if you could review

Posthumous LGTM.
...Pretty cool


Rebuild button for write-access members?

According to (my understanding of ) the commit.html file people that have repo.role.write permissions should be able to see and activate rebuilds of failures. However, the people in my organization do not seem to be able to see the rebuild button.
According to the perms table they user_id does have repo_write permission, so I'm not sure where the problem lies.

we can close, merged a PR a while back


Adding a warning when soundcloud track is a demo from SoundCloud GO+

This PR is related to #67
When a SoundCloud track has the property "monetization_model":"SUB_HIGH_TIER" means its a 30 second demo from the full track, this PR just adds a isDemo property on a SoundCloudAudioTrackInfo class and sets the duration of the track to 30 seconds.
Example usage:
if(track.getSourceManager() instanceof SoundCloudAudioSourceManager) {
  SoundCloudAudioTrackInfo info = (SoundCloudAudioTrackInfo) track.getInfo();
  if(info.isDemo)
    System.out.println("The track is a 30 second demo")
}

Closed as it looks like its not going to get merged


Coded UI Testing in not working Properly on this UI

on user controls it works good but when we come to Message Dialog (Coded UI is unable to record the Dialog windows)
Any Alternate solution for this

MahApps.Metro v2.0.0
Windows  7 ultimate
Visual Studio 2015
.NET Framework  4.5.2

Coded UI is unable to record Mahapps Flyout on its latest version


Unable to load in Wowreeb

I have updated the config but keep getting an error.

<Exe Path="D:\Turtle WoW\WoW.exe" />
<AuthServer Host="logon.turtle-wow.org" />

<DLL Path="D:\Turtle WoW\VfPatcher.dll" Method="Load" />
<DLL Path="D:\Turtle WoW\nampower.dll" Method="Load" />

I tried the same yesterday because i wanted to use Vanillafixes + ReShade and tried to prelaunch the VfPatcher.dll in WoWReeb

The Method field should be omitted for VanillaFixes:
<DLL Path="D:\Turtle WoW\VfPatcher.dll" />
<DLL Path="D:\Turtle WoW\nampower.dll" Method="Load" />

(That should probably be documented somewhere...)

After i removed the Method field i get this

VanillaFixes should definitely work with wowreeb since version 3.5 (https://github.com/namreeb/wowreeb/issues/20#issuecomment-1366997088). An error code of 5 means ERROR_ACCESS_DENIED, does it work if you try to inject any other DLL like nampower.dll?

Yes, i was using nampower.dll only and that one was working (or at least didnt throw an error)
 <DLL Path="d:\<wow path>\VfPatcher.dll" />
 <DLL Path="d:\<wow path>\nampower-2.2\nampower.dll" Method="Load" />

 anonymized

Closing since I tested this again and it still works with the latest version.


⚠ Bofrost.lu has degraded performance

In 875b986, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 985 ms

Resolved: Bofrost.lu performance has improved in 9d7cd26 after 6 minutes.


chore: add refl etc annotations

I don't get what the build problem in "Post PR summary content" is here; comments are appreciated

I don't get what the build problem in "Post PR summary content" is here; comments are appreciated

I had the same problem in #18926 and solved it by merging the current master, as suggested in this Zulip thread.


Adjust the priority of the configs

Close #302
config with profiles should have higher priority than others.

@ryanjbaxter this PR does the same thing as https://github.com/spring-cloud/spring-cloud-config/pull/2207
spring-cloud-zookeeper also has the same issue as spring-cloud-config JDBC backend that we discussed yesterday.

We can't do this as easily as config server since. While config server jdbc needed to match git, this has always functioned this way and may break users. It needs to be behind a flag and users must opt in. The default can be changed in 4.0.x

I think it's a bug. the zookeeper config didn't use the same config order in import and bootstrap mode.

Documentation added.

@spencergibb a new flag is introduced as requested.


Responsiveness on mobile, tablets, rotated mobile and machine

@Landos007  there is a displacement issue in  a small laptop display
here is the screenshot showing the issue : http://prnt.sc/s4kvrz

pop up issue

I left the comment it these screenshots

@Landos007  iPad landscape fix the home page


Add additional fields & Update CHANGELOG

@cjds I think this will mean we need to recompile and re-release the fetch_binary_drivers


MINOR: Fix binary compatibility break in KafkaClientSupplier.getAdminClient

Changing the return type in an interface is a binary incompatible change.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

2 jenkins jobs passed, 1 failed with 2 unrelated flaky tests:

org.apache.kafka.connect.integration.RebalanceSourceConnectorsIntegrationTest.testReconfigConnector
kafka.server.DescribeLogDirsRequestTest.testDescribeLogDirsRequest


[flash_ctrl] Adding Interface at Environment,fix analog inputs

…ls + fix analog inputs
Signed-off-by: Nikola Miladinovic<EMAIL_ADDRESS>

lgtm at a glance, however there are several CI issues that need to be addressed.
seems one of the files was marked executable.

@nikola-miladinovic, please add @matutem as reviewer on all of your PRs.


Don't download completed or locked exercises by default

fixes #318

Coverage decreased (-0.4%) to 74.401% when pulling 45eb8bf586c4c208b5ec6c041f2f0b5fbd2d1347 on update-dont-dl-completed-juha into 21c020ba872ef1468e43f0b239862877f65fce9e on master.

Coverage decreased (-0.4%) to 74.401% when pulling 45eb8bf586c4c208b5ec6c041f2f0b5fbd2d1347 on update-dont-dl-completed-juha into 21c020ba872ef1468e43f0b239862877f65fce9e on master.

:+1:


Update README.md to reflect Python runtime version changes.

Update the documentation to show that AWS Lambda now supports Python 3.6, and bless runs on that runtime.
In addition, make it clear that the bless_client runs on Python 2.7

Coverage remained the same at 95.015% when pulling a781517231279228383708e6909a726c36995505 on tanishq-dubey:master into f82e2a95d4c3734221eeeca45359ac80cbc5292b on Netflix:master.


Fix urls fixer wrong import rewrite

My attempt to fix #250.
I noticed that the underlying issue is that some noop tests are actually doing rewrites.
For exemple, the following is actually triggering an erase/rewrite of the import node but since it rewrites the same thing we don't notice it:
def test_fake_noop():
    check_noop(
        """\
        from django.urls import re_path

        re_path('whatever')
        """,
        settings,
    )

I added a state_added_names variable to keep track of names that will need to be imported. Then I can only add an import with these names (minus the ones initially imported).
PS: Last commit replace the state_used_names variable with state_re_path_used because it was only needed to determine if the re_path import can be removed.
I'm unsure if it's the best way to deal with this so I'm happy to take any feed back. At least maybe this will give you some food for thoughts on your attempt.
Cheers

Thank you. I will review this properly in the next few days, then hopefully do a django-upgrade release with all the built-up stuff!

PS: Last commit replace the state_used_names variable with state_re_path_used because it was only needed to determine if the re_path import can be removed.
I'm unsure if it's the best way to deal with this so I'm happy to take any feed back. At least maybe this will give you some food for thoughts on your attempt.

This seems like a good approach to me!

Woops, forgot about the release note, my bad. Anyway, thanks for the review and the few tweaks !

Thank you! Release coming shortly, writing a blog post for it...

Awesome! I saw that you have been very productive lately with the blog posts. Really nice! Keep up the good work 😃

Thank you @adamchainz and @UnknownPlatypus for fixing it in a short period of time 🎉


Update parse_grpc_uri docs with keep-alive params

I guess we can do a quick v0.8.1 release with this.


test: add os dep lib to globalconfig of a test addon

@sgoral-splunk do you want this to be merged?


Update docs to include replacement note

Add warning note about packaged being replaced by http-client

Thanks!


OpenPilot Tools Does Not Work Following the readme

Describe the bug
I've been trying to get the joystick example under tools to work for about a week now. I feel like there are things missing from the readme, it definitely doesn't work right out of the box.
After following all the steps, Running Boardd without sudo gives me Permission Denied for one
Then running it with sudo does show that the panda is found and the correct panda with gps is detected, but it's aborted right after
Aborted (core dumped)

This is all with the car on and my paw plugged into the panda. I tried the paw switched to both off and PWR
If the car is off (on idle) it does seem to show it on, but since the car is off I wouldn't be able to do anything
Shows
Panda GPS on

debug_controls.py doesn't seem to start either. It throws this error
Could not open /dev/shm/can
I'm not sure what to do at this point, but I feel like i've tried everything.
Beforehand I did run the udev tools
How to reproduce or log data
Follow the readme for tools on a fresh install of Ubuntu 16.04 with a grey panda
Expected behavior
Joystickd to work after following the readme with a Panda Paw
Additional context
I use a Panda Paw, I tried using the paw with both the Pwr switch on and off, but neither worked
Operating system: Ubuntu 16.04

I agree, the readme should mention things like udev rules for panda, flashing the panda on a PC and not using the eon panda firmware, safety modes, controls allowed, switches on giraffe hardware (even though most of us have harness now), and other gotchas that come up during the process. It is not as easy as running the three commands in the readme at all. I have been trying to get it to work for a few months now off and on with no luck.

I have noticed that with the /dev/shm/can and /dev/shm/sendcan, if you do sudo rm -rf /dev/shm/can && rm -rf /dev/shm/sendcan it can latch onto those files

Made a new issue to track this #1799.


change default install location for apps to /Applications

Closes #2534.
Pending agreement.

Please excuse me if I'm mistaken, but lines 185-186 of USAGE.md state:
This is commonly used to create the links in the _root_ Applications directory instead of the _home_ Applications directory by specifying...
Shouldn't _root_ and _home_ be swapped here?

You are very right. Thank you. Fixed.

While I am loathe to change the defaults, I am generally swayed by the number of requests.
However, let's analyze this a bit first for unexpected effects:

The assumptions behind #8819 may become incorrect, and there may be other similar code.
brew cask info may show incorrect info, as the existing symlink is in an unexpected place.
Uninstalling an app would leave behind the broken symlink in the old default location.
Using the system-wide dir for Apps, and keeping the user dir for ~/Library artifacts is inconsistent and extremely confusing.

There may be more issues, as I haven't thought deeply.  Any change would have to be done carefully.

brew cask info may show incorrect info, as the existing symlink is in an unexpected place.

Uninstalling an app would leave behind the broken symlink in the old default location.

This can be remedied by exposing more information about cask installations in the .metadata directory. Perhaps a simple JSON file:
{
  "appdir": "~/Applications",
  ...
}

Using the system-wide dir for Apps, and keeping the user dir for ~/Library artifacts is inconsistent and extremely confusing.

I disagree, as this recommended change is due to a matter of expectations. Users expect apps to be global (/Applications) and other things to be local (~) because instructions for things other than apps (unless they come in a pkg) usually tell you to install in the user directories.
Inconsistent? Perhaps. Confusing? Quite the contrary. We’ve seen many users (not just in that issue) question the choice of ~/Applications but never the other directories. The current setup is the confusing one, which is why most change it.
With all the other points I mostly agree — we should take some care to not break things too much. My primary concern was making a decision, whichever it is, and close the issue (we have too many under consideration that we should just pick something).
However, I don’t really think issues like orphaned links on uninstall are a problem; especially if we consider most users are indeed already picking /Applications as the links directory. I say that because they’re at worst a minor annoyance. I also agree with @jawshooah with exposing more information in .metadata, though that should be discussed in depth in another issue.
I also appreciate all the care we always take with user installs and transitions, and we should indeed be careful considering the considerable user-base we have, but we’re admittedly pre-alpha: things are expected to and should break; now is the only time we get to not be shy about that.

we’re admittedly pre-alpha: things are expected to and should break; now is the only time we get to not be shy about that.
I keep forgetting about this. Most things work very nicely, so it's easy to forget that this project is still in its relative infancy.

@vitorgalvao beautifully argued as always, and you have me convinced in principle about making an incompatible change.
In practice, we are in heavy use.  In practice, we also have to respond to issues.  There are likely near 100 duplicate reports regarding the recent incompatible change with Homebrew.
That bug was fully addressed within a few hours.  Every user who upgraded outside that small time window never saw the bug, and never filed an issue.
But the appdir change is different: instead of affecting a subset, it will affect every single user going forward.  And there is no "notice of incompatible" change when people upgrade at the CLI.  Thus it has the potential to generate truly enormous numbers of duplicate issues.
And that must be reckoned with, regardless of what version number we assign to ourselves.

Great discussion here so far. I'm +1 for changing the default, but I'd like to continue to discuss options for smoothing out the transition a bit more before we just decide to do a "damn the torpedoes" merge.

And there is no "notice of incompatible" change when people upgrade at the CLI.

We could special case this with a message printed to users that do not have the appdir explicitly configured (or even just throw in a notice to everybody, billboard style). We'd just have to decide on how to approach the messaging.
Besides the details, are we mostly agreed that messaging to the user base for this change is worth pursuing?

@rolandwalker Well, you do tend to be able to make me take a step back and see what I missed in these major decisions.
I do stand by the point that this change (as opposed to the incompatibility one) would be “at worst a minor annoyance”. The former broke the complete experience, while the latter might cause slight confusion (annoyance, perhaps?). The number of users it’ll affect may also be extremely reduced, if we assume most are using /Applications as the linking directory anyway (which we can’t say for sure).
However,

Thus it has the potential to generate truly enormous numbers of duplicate issues.

And that must be reckoned with (…)

This possibility is certainly not something that can be ignored, I agree.

Besides the details, are we mostly agreed that messaging to the user base for this change is worth pursuing?

@phinze Yes.
Would it be worth considering an abstraction of such a system? Something that we could use in the future when making breaking changes. Could we in theory perhaps take more control over homebrew-cask upgrades, so that upgrading normally from a pre-break version to the new one would be stopped until the user is aware of the modifications? I’m guessing not currently, as long as brew upgrade brew-cask works.

Could we in theory perhaps take more control over homebrew-cask upgrades

No, that's the problem.  The moment that the upgrade happens is out of our control.  We'll have to look at the first execution after the upgrade.
Messaging is good, and we should do it, but it's not sufficient.  Some people will be running the command from a script.
Some finesse may be in order.  After all, we managed #4688 with very few hitches.  The key was to overlap functionality for a while and sweep up afterwards.
What about:

implement brew cask activate <cask> to help people control the switchover
at install time

check whether --appdir was set explicitly
check for symlinks in ~/Applications
if there are symlinks that belong to us in ~/Applications, and --appdir was not set

create the new symlink in both places
emit a warning that explains how to complete a clean switchover

Another possibility would be to grab any symlinks that belong to us and re-create them in both locations.  Then the user would only need to rm them from ~/Applications to make the warning go away.

Both options seem acceptable to me. The second one could mean a faster transition, though. I don't understand what brew cask activate <cask> is supposed to be doing, though.

Sorry: the activate verb is meant to be like brew link, only generalized for copying, linking or shimming.
For this case it would just mean "regenerate the symlinks for my staged Cask".

As original promoter of the pesky #2534, I am unsurprisingly in favor.
However, @rolandwalker is right in recommending to approach sweeping changes with caution (and a beekeeping suit). Perhaps reformed defaults would be best postponed to an official beta release, where users may be more tolerant of incompatible behavior.

Cross-posting from https://github.com/caskroom/homebrew-cask/issues/2534#issuecomment-78128288:

Another :+1: for /Applications as default.  It looks like Apple is trying to phase out support for ~/Applications, and cask should follow Apple's lead.

I just want all of my installed applications to show up in the Applications stack in the dock.  I don't care about the rest.  For now, I'm accomplishing that using the line in .bashrc mentioned above:

export HOMEBREW_CASK_OPTS="--appdir=/Applications"`

> I shouldn't have to worry about things like that, **it should just work** ;)

Can we go ahead and merge @vitorgalvao commit? What's the hold up?

What's the hold up?

We need a strategy for a smooth transition.

Any updates on this?

Same issue.

You linked this issue?

I linked my previous response to that same question.

Redundant due to the news on #13201.


Fix #72 - Refactor message transformation page

Purpose
Moved the ballerina and java interceptors in tow two separate pages
Issues

Fixes #72

Maintainers: Check before merge

[x] Manual verification

@Rajith90 , please move this content to the APIM 4.0.0 docs if it is applicable.


ConfigMap doesn't allow the value 'Yes' in config values

The following config map
apiVersion: v1
kind: ConfigMap
metadata:
  name: foo
data:
  bar: 'Yes'

has a linting error on the 'Yes' value, saying Incorrect type. Expected "string". I'm assuming it sees the string yes and tries to interpret the value as a boolean, but what if I want to interpret it as a string? How do I make that not an error?

Thanks for flagging this.  We lean on the RedHat YAML extension for schema validation, so this may be out of our control.  Let me investigate further and raise it with the RH YAML folks if need be.

Yeah, I figured it might be so, but wasn't sure where to file the issue. Was in a bit of a hurry, so figured better pick one and get it written down :)
But feel free to move it and/or file a referencing issue there instead of this one.

fwiw, looking at the spec, Yes is actually interpretted by YAML as a Boolean.
I think most parsers are a little flexible so it works, but the YAML schema validator is actually being true to the spec:
http://yaml.org/type/bool.html
I'm going to close this since I don't think we're going to do anything further on this issue....

@brendandburns IIUC, foo: Yes should unambiguously be interpreted as a boolean, but foo: 'Yes' probably not?

@brendandburns That Yes is interpreted as a boolean is only for YAML 1.1, in the YAML 1.2 specification the examples with Yes, No, On, Off (in the various casings combinations) were removed, although there still is a link in that document to the 1.1 list of types.
An up-to-date YAML parser (i.e. one updated after the release in 2009 of the 1.2 spec) should not interpret Yes as a boolean.


Can't create an automated Docker Registry build without access to the github Ceph org

I was going to set up the Docker Registry automated builds for these Dockerfiles, but I cannot do so without access to the Github Ceph org.  (I do have access to the Docker Registry Ceph org.)

Relatedly, there is currently no ceph/ceph-base:latest tag, which makes it impossible to simply do a docker pull ceph/ceph-docker.

Sorry for the delay @Ulexus, can you tell me what you need and I'll make you have it.
Thanks!

Thanks, I'm now a member, so I can get this done.  I'll add the automated builds as soon as PR #9 is merged (so we don't have to rename again)

Apparently, I still don't have sufficient access to bind the Docker hooks on this repository (necessary for the automated build).  I don't know what access level that requires, but it may be easier for someone else with access to set up the automated builds.

It does let me generate an "automated build" without the build trigger, though.  That's good enough, I think.

Looks like the build fails:
Specified Dockerfile was not found. (/tmp/build_bczahbt4xwimbssvauckpd8/Dockerfile)
I guess the dockerfile path is wrong.

Hum looks like the build is looking for a Dockerfile at the root but since we have multiple Dockerfile, I'm not sure how this should work for us. Perhaps we will have to split everything into individual repos... not sure.
@Ulexus if you have an idea :), you seem to know better than I do these automated builds.

Yeah, I see.  I've actually set up each of the automated builds; you don't need to add another repo for it.  All you have to do is setup the webhooks on Github to send to each of the Docker repositories.
The documentation is here (skip down to the Github Service Hooks section)

Putting this here as a reminder for me to setup: http://docs.docker.com/docker-hub/builds/#webhooks

The service hooks appear to be in place; commits are triggering builds.


Allow Refresh Token revocation without Access Token revocation (according to RFC 7009)

First of all thanks for this awesome library!
We are using it in combination with Micro Focus Access Manager 5.0. The product is very special in a way that it seems to implement only the MUSTs from the RFCs. Which works fine with this library up to the moment when the user wants to log out and we call the revokeTokenAndLogout(); method.
Now, the thing is that Access Manager won't allow the revocation of an access token and thus the whole function call fails. Moreover, it seems that there is no way to prevent the library from revoking solely the refresh token. I first thought that this is an issue of the Access Manager, but if one examines RFC 7009 then it actually describes this as a valid approach:

Token Revocation

Implementations MUST support the revocation of refresh tokens and
SHOULD support the revocation of access tokens (see Implementation
Note).

According to the Access Manager Documentation revoking the refresh token will also automatically revoke all the corresponding access tokens, so that should be fine and better than revoking only the latest access token.
Now my feature request is to adapt the revokeTokenAndLogout(); method to accept a parameter that will disable access token revocation and thus only revoke the refresh token.

Ooh interesting. Just as a gut feeling (no evidence) I think that this would have potentially many weird side effects in the library. Adding the flag (or similar feature, as I don't think boolean parameters are a good plan) should be doable, but fear that with proper intensive testing other areas of the library would not be ready to cope with having a working access token but invalid refresh token.
Either way, seems like a proper feature-request to me.

Examining the revokeTokenAndLogout(); method makes me believe that this might actually not be that hard to implement since right now after successful revocation of both tokens it calls the logout(); method that clears the storage of any tokens.
At the start of revokeTokenAndLogout(); there is this check which might not be necessary and might resolve this issue when removed:
if (!accessToken) {
      return;
}


API support

You have done really fantastic work! But it seems that currently there are no APIs offered for developers.
Coverage is critical in coverage-guided fuzzing, but there is limited work because it's challenging to obtain the coverage in Python apps in a cost-effective manner.
Hence, I think It would be more convenient if I could obtain the coverage information during my custom apps and do some further jobs based on it.

There's been (some) API support, but no documentation...  I did a proof of concept integration with a Hypothesis-based "fuzzer", really a TPBT system, many moons ago, but that project has yet to become public.

There's been (some) API support, but no documentation... I did a proof of concept integration with a Hypothesis-based "fuzzer", really a TPBT system, many moons ago, but that project has yet to become public.

thanks for your reply. I've already made it myself. Thanks for your awesome code!


feat: Add access token type of machine user

Description
Close #60

Upgrade zitadel-go from v2.0.2 to v2.0.10
Add access_token_type argument in machine user
Modify TosConfirmAnd to TosConfim due to the changes in zitadel-go

Note
I'm not sure whether TosConfim is the right variable instead of TosConfirmAnd in this case. Please correct me if I'm wrong. This change is caused from https://github.com/zitadel/zitadel-go/commit/056cbc9968f9b7715a34745279502754b14056c0#diff-5b93f5db7a37d745ed8a700162aa0d8f266ab509f163d686b6a3265ed4d36c64

Close with #71


Fix ambassador script

based on SvenDowideit/dockerfiles#37
Requires that to be merged first, and the image on the docker hub needs to be updated. @SvenDowideit

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "aphs-fix-ambassador-multi-port" git@github.com:aidanhs/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

ping @SvenDowideit, I'll assign this to you :smile:

Ping @SvenDowideit

merged upstream,  LGTM - @moxiegirl @thaJeztah

cool, thanks!
LGTM


Closes #2591 Add User-Agent Header in two network requests

Description

Send User-Agent Header OpenFoodFacts Official Android App 3.2.2 in the /tagline-xx.json and /1.json?fields=null GET requests.
add import openfoodfacts.github.scrachx.openfood.BuildConfig; to Utils.java to use the correct BuildConfig, currently it was using the package com.firebase.jobdispatcher which was not desired and returned incorrect VersionName

Related issues and discussion
fixes #2591
Screen-shots, if any

Checklist
Make sure you've done all the following (You can delete the checklist before submitting)

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.
[x] Code is well documented
[x] Include unit tests for new functionality
[x] All user-visible strings are made translatable
[x] Code passes Travis builds in your branch
[x] If you have multiple commits please combine them into one commit by squashing them.
[x] Read and understood the contribution guidelines.

Updated User-Agent
The User-Agent would be uniform through the app now. TYPE is made optional now. Currently, we only have Scan and Search as TYPE, we can think of adding more if required later on.


feat(ix-player): auto-retry on 423 response

Description
Before this PR

Some docs links were broken
Some type import paths were incorrect
Video playback would not retry automatically on a 423 response code.

After this PR

Documentation links are fixed
Video playback retires automatically on a 423 response code.

Todo

[x] Retry on 423 errors
[x] Create the 423 MD file explaining the error

Oh I just realized is the react package different? Do we need additional support?

Oh I just realized is the react package different? Do we need additional support?

Not sure what additional support means in this context, but for the react package to consume this change, the only thing that should need to happen is a dependency version change.
Since we're changing the behavior of properties that are not defined by a consumer, ie  not src, poster etc, there shouldn't be any changes needed inside the React package.
  "dependencies": {
    "@imgix/ix-player": "1.0.0-beta.2", <--- this
    "@mux/playback-core": "0.15.0",
    "prop-types": "^15.7.2"
  },
  "devDependencies":

If you:

bump that dep locally (both in ix-player package json and ix-player-react package json)
delete the node_modules in the example react app you'd like to run
run yarn dev from the root
and run yarn dev in the react project

You'll be using @imgix/ix-player-react with @imgix/ix-player's latest changes. You can see the retry behavior kick in.
The reason this isn't being done as part of this PR is to be able to release the two packages independently. If we bump the player version in the react package as part of the same release, folks can refer to the releases tab for each package in isolation.
The contributing docs should probably include a more detailed explanation of this 🤔 .
If you want, we can sync up on the repo setup. There are some things that are easier to explain outside of a PR discussion.


Build issues using Bun

The build breaks when using bun, due to the sharp dependancy that is used by jampack.

I had similar issue on my project and I found a consistent solution:

Delete any old node_modules and bun.lockb folders
Add sharp as a trusted dependency in your package.json:

  "trustedDependencies": [
     "sharp"
  ]

Run bun install and then bun build it should work now.

Oh man, thanks for that info. I'll have to try that.

@ottodevs Bro that works like a charm, thanks!

resovled with 27d353f40950ac3a71a29b44fe07598bd9299b9b


Map Image PDF Export

Sorry but I don't understand the goal of this pull request ...

Can this be merged?


Error running home-manager switch

I'm not sure if this is a user error or not, but I installed home-manager on NixOS by adding the home-manager package to my system configuration.nix script.
I'm still new to NixOS, so I'm not sure what information you would need to debug this issue, but I'm running NixOS 18.03.
tim@nixos ~> uname -a
Linux nixos 4.14.39 #1-NixOS SMP Tue May 1 19:58:27 UTC 2018 x86_64 GNU/Linux

When I try to run home-manager switch, I get the following error:
tim@nixos ~> home-manager switch
error: file 'home-manager/home-manager/home-manager.nix' was not found in the Nix search path (add it using $NIX_PATH or -I)

Now, I understand that home-manager.nix is not in my path, but when I do a global search for that file from the root directory, I can find the file, but in the directory home-manager/home-manager. Is there something I am fundamentally doing wrong or is this a bug?

Hmm, I'm guessing you're using the home-manager package from Nixpkgs? If so I would recommend skipping that and instead following the installation instructions from the README.
If you did following the readme and still got this error I suspect you might have an incorrectly set programs.home-manager.path option. Would you mind pasting your Home Manager configuration?

I did install the package from nixpkgs. I updated my nix configuration to remove the home-manager nixpkg. I then switched to my new nix configuration and installed nix via the README using the version for NixOS 18.03.
Now let me get this out of the way:
I am using the fish shell which isn't POSIX compliant. I have bash installed though. That being said, I get the following error when trying the default home.nix that the README suggests:
tim@nixos ~> nix-shell $HM_PATH -A install

Creating initial Home Manager generation...

error: syntax error, unexpected $undefined, at /home/tim/.config/nixpkgs/home.nix:3:32
(use '--show-trace' to show detailed location information)

Uh oh, the installation failed! Please create an issue at

    https://github.com/rycee/home-manager/issues

if the error seems to be the fault of Home Manager.

I'm assuming that setting the HM_PATH variable isn't working because when I set it in fish, whatever environment home-manager relies on doesn't pick up on it. I thought that it was enough to have a POSIX compliant shell installed to use this tool. If that's not the case, feel free to close this issue, because that's where my problems lie.

{
  programs.home-manager.enable = true;
  programs.home-manager.path = $HM_PATH;
}

You'll need to replace $HM_PATH with the actual path to the Home Manager project root. For example,
{
  programs.home-manager.enable = true;
  programs.home-manager.path = https://github.com/rycee/home-manager/archive/release-18.03.tar.gz;
}

After that nix-shell https://github.com/rycee/home-manager/archive/release-18.03.tar.gz -A install should work fine.


Inbound NAT rules vs. load-balancing rules

The section titled "How are inbound NAT rules different from load-balancing rules?" could cover not only differences, but also equivalence scenarios. For example, will a load balancer with only one VM behind it, and with appropriate NAT rules to the this target VM, work in an equivalent way (thanks to the NAT rules) even if there is not a single load-balancing rule set?

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

ID: 26f2ee4c-633b-8579-47e1-1543db5acaeb
Version Independent ID: 0baa18b9-14ca-1703-ba64-f036ec39b639
Content: Frequently asked questions - Azure Load Balancer
Content Source: articles/load-balancer/load-balancer-faqs.yml
Service: load-balancer
GitHub Login: @mbender-ms
Microsoft Alias: mbender

@MikeLabatt - Azure LB with one VM instance in the backend is not a recommended configuration. Our Standard LB SLA also doesnt cover this scenario. Putting it in the docs will send a confusing message to customers. We want to be consistent that this is  not a pattern we recommend.

@MikeLabatt
Load Balancing Rule and Inbound NAT Rules are two entirely different concepts. They differ greatly be behavior.

The primary example is that a NAT Rule does not have a health probe, meaning it cannot check the backend's health and will just route the traffic according to the rule configured.
Where as a Load Balancer rule will only route traffic to healthy instances.


Spaces in the user agent field are being reported as errors.

E.G.
"Mozilla/5.0 (cloud; like Mac OS X; en-us) AppleWebKit/537.36.0 (KHTML, like Gecko) Version/4.0.4 Mobile/7B334b Safari/537.36.0"

Completely rewrote how the records are split, implementing my own splitting algorithm using a state machine.  Made it much easier to account for differing field formats.


Don't bypass cache in lfs_cache_prog() and lfs_cache_read()

In some cases specific alignment of buffer passed to underlying device
is required. For example SDMMC in STM32F7 (when used with DMA) requires
the buffers to be aligned to 16 bytes. If you enable data cache in
STM32F7, the alignment of buffer passed to any driver which uses DMA
should generally be at least 32 bytes.
While it is possible to provide sufficiently aligned "read", "prog" and
per-file caches to littlefs, the cases where caches are bypassed are
hard to control when littlefs is hidden under some additional layers.
For example if you couple littlefs with stdio and use it via FILE*,
then littlefs functions will operate on internal FIlE* buffer, usually
allocated dynamically, so in these specific cases - with insufficient
alignment (8 bytes on ARM Cortex-M).
The easy path was taken - remove all cases of cache bypassing.
Fixes #158

Another approach is possible, but it is considerably harder, uses more code and RAM.
lfs_config could be extended with additional field to specify required alignment. If these value is greater than __BIGGEST_ALIGNMENT__ (in case of gcc this is the alignment of memory provided by malloc()) additional code would have to be executed to manually align dynamically allocated buffers. This would also require extra fields for storing the unaligned pointers (to pass it to free()). User provided buffers should be checked for proper alignment with assertions. With all this in place, the condition for bypassing cache could be extended with test for sufficient alignment.
Please let me know if you would prefer this path - I will implement an alternative pull request in that case.
Important note - similar fix will be required for v2 branch too.

I've tried to understand why the assertion in lfs_cache_prog() fails now for read size == prog size == 1, but I really have no idea, maybe the test scenario needs some adjustments now or maybe there is some underlying problem which was hidden before or maybe my change is completely wrong... Any pointers appreciated.

Hmm, lets rebase and see. Sorry if this messes with your branch.

Well, I guess the problem went away. Unrelated question, do you think this sort of change should be on a minor release?

Unrelated question, do you think this sort of change should be on a minor release?

What do you mean exactly? Are you're asking whether you should do a new minor release right after this is merged? Or maybe you cannot decide between a minor and patch release? Or something else? (; As long as this gets released sooner than later I don't have any strong preferences (;

Or maybe you cannot decide between a minor and patch release? Or something else? (; As long as this gets released sooner than later I don't have any strong preferences (;

Right now, every PR that lands on master is treated as either a patch, minor or major release. Minor releases are used to indicate new features. This PR is a bit ambiguous, but lets go with a patch release for now.

Thanks for the pr!

Right now, every PR that lands on master is treated as either a patch, minor or major release.

Please take a look at how the description of the patch releases are generated. I assume this PR went into https://github.com/ARMmbed/littlefs/releases/tag/v2.0.3 , but there is actually no mention about it, just the most recent commit which deals with travis-ci related issues.

So I played around with it a bit, but unfortunately as soon as you add text to tags in GitHub, they become big release notices which makes it hard to find the releases for the major/minor releases. IMO these are more important to find as they contain human written release notes. They also contain a list of all commits since the last minor release, so when we make a minor release this commit will be found there.

@FreddieChopin, after uses this process a bit longer, I see your point. It is very difficult to find which version a commit went into. I'm changing this here: https://github.com/ARMmbed/littlefs/pull/261

BTW after some more time I'm ready to admit that bypassing the cache should be reverted. It is actually not really a viable solution to expect every external library to deal with alignment or other low-level stuff like that.
Please revert yourself or I can prepare a pull-request - whatever is more convenient.

That sounds like a plan. If you're able to create a PR that would help, otherwise I can revert it next minor release.
There's a number of performance issues that people have identified around the metadata fetching. The cache bypassing may help a little bit, but I think it still warrants more investigation.
https://github.com/ARMmbed/littlefs/issues/203#issuecomment-519022104
Sorry I still haven't been able to get to the performance issues at all.
I'm planning on taking care of porting documentation next, but hopefully after that everything will be more or less settled and I'll finally be able to look into all of the performance issues.


Do not package travis-phantomjs (reduce installed size more than 1000 times)

Disclaimer: I am not a user of this package, this was found during mass npm package downloading.
Atm, your npm package ember-bootstrap-datetimepicker 0.6.0 has packaged size 37 MiB, and installed size 70.55 MiB.
70.50 MiB of that is inside the ./travis-phantomjs dir. 17 MiB of that is the file ./travis-phantomjs/phantomjs-2.0.0-ubuntu-12.04.tar.bz2.
I suspect that those files were accidently packaged.

There is one dep and it's needed (babel).  Also not sure why your bot is flagging phantomjs in travis ci builds.

phantomjs-2.0.0-ubuntu-12.04.tar.bz2 is needed?

mkdir test
cd test
wget https://registry.npmjs.org/ember-bootstrap-datetimepicker/-/ember-bootstrap-datetimepicker-0.6.0.tgz
tar -xf ember-bootstrap-datetimepicker-0.6.0.tgz
du -hs package/*

12K     package/addon
24K     package/app
12K     package/blueprints
4,0K    package/CHANGELOG.md
12K     package/config
4,0K    package/index.js
4,0K    package/LICENSE.md
4,0K    package/package.json
4,0K    package/publishToGHPages.sh
4,0K    package/README.md
71M     package/travis-phantomjs

@claudiocro

Oh, looks like @claudiocro does deployments directly from the CI box.  He'll need to modify the the travis.yml to remove travis-phantom before deployment.
Reopening.


Return heatmaps instead of color-mapped results

Is there a particular reason why visualize_saliency_with_losses and visualize_cam_with_losses returns a color-mapped result instead of the heatmap/grads?
I would suggest returning the result before mapping to a specific colormap like "jet".
See
https://github.com/raghakot/keras-vis/blob/master/vis/visualization/saliency.py#L83
https://github.com/raghakot/keras-vis/blob/master/vis/visualization/saliency.py#L196

That's a good point. Will change it.

@raghakot could you please make a new release and push it to PyPI? Would be great to have this fix when using pip. Thanks!

@raghakot, I'd just like you to know that I spent 2 days of work to find out that release 0.4.1 from github is different from release 0.4.1 from PyPI. Thanks @LennartPiro for pointing that out.


Built-in support for Ethernet via USB?

Hello,
would it be possible to support USB-to-Ethernet adapters out of the box for users who want to have an additional ethernet device on their Raspberry Pi? We could of course create a customized version of kiosk_system_rpi3 just to set CONFIG_USB_NET_AX88179_178A=y, but it seems inefficient.
Greetings,
Nils Moskopp

We try to keep the common systems to a minimum amount of extra configs. Since the raspberry pi already has an ethernet port and I don't own one of the adapters you mentioned, its hard to test that between updates we don't break the other configs that were enabled. The strategy for now is to have users with custom modifications fork the system and tune it to their needs.


update memcache populate script

update memcache populate script to improve test cause of memcached for get and set operations

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


[feat] Add per-tag scheme rules

This change allows scheme rules on a per-tag basis, in case you
want to limit the schemes that a certain tag can have, while not
enforcing the same restriction on another.
Closes #50

This looks much better. What's your use case for it?

Sorry, you already said.
I think it's reasonable. I'm going to review a little and merge it.

No problem! We are really looking at the use case where we want users to be able to only have data: scheme's for  tags, but still allow http and https links for  tags. Just provides a bit more configuration if needed.


gpu/cpu time performance

Click to expand!
Issue Type
Performance
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
2.10
Custom Code
No
OS Platform and Distribution
Windows 10
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
cuDNN = <IP_ADDRESS>
GPU model and memory
nVidia GTX 1050, 4GB GRAM
Current Behaviour?
I have noticed that training on cpu faster than gpu. Note that I have tried same on RTX 3090 TI and got similar results

GPU performance:

2023-03-12 13:45:41.870315: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-03-12 13:45:42.381082: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1616] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 2787 MB memory:  -> device: 0, name: NVIDIA GeForce GTX 1050, pci bus id: 0000:01:00.0, compute capability: 6.1
WARNING:tensorflow:Please add `keras.layers.InputLayer` instead of `keras.Input` to Sequential model. `keras.Input` is intended to be used by Functional model.
Epoch 1/100
3125/3125 [==============================] - 10s 3ms/step - loss: 0.0495
Epoch 2/100
3125/3125 [==============================] - 10s 3ms/step - loss: 0.0014
Epoch 3/100
3125/3125 [==============================] - 10s 3ms/step - loss: 0.0013
Epoch 4/100
3125/3125 [==============================] - 11s 4ms/step - loss: 0.0013
Epoch 5/100
3125/3125 [==============================] - 11s 4ms/step - loss: 0.0012
Epoch 6/100
3125/3125 [==============================] - 11s 4ms/step - loss: 0.0011

CPU performance:
2023-03-12 13:48:54.873454: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
WARNING:tensorflow:Please add `keras.layers.InputLayer` instead of `keras.Input` to Sequential model. `keras.Input` is intended to be used by Functional model.
Epoch 1/100
3125/3125 [==============================] - 4s 1ms/step - loss: 0.0511
Epoch 2/100
3125/3125 [==============================] - 4s 1ms/step - loss: 0.0019
Epoch 3/100
3125/3125 [==============================] - 4s 1ms/step - loss: 0.0013
Epoch 4/100
3125/3125 [==============================] - 4s 1ms/step - loss: 0.0013
Epoch 5/100
3125/3125 [==============================] - 4s 1ms/step - loss: 0.0013
Epoch 6/100
3125/3125 [==============================] - 4s 1ms/step - loss: 0.0012

Standalone code to reproduce the issue
import numpy as np
from tensorflow.keras.utils import to_categorical
from tensorflow.python.keras.layers import Dense, Input
from tensorflow.python.keras.models import Model, Sequential

def build_std_func_model(n_inputs):
    inp = Input(n_inputs)
    h = Dense(100, activation="relu")(inp)
    h = Dense(100, activation="relu")(h)
    h = Dense(100, activation="relu")(h)
    h = Dense(100, activation="relu")(h)
    output = Dense(n_inputs, activation="linear")(h)
    return Model(inputs=inp, outputs=output)

def build_std_seq_model(n_inputs):
    model = Sequential()

    model.add(Input(n_inputs))
    model.add(Dense(100, activation="relu"))
    model.add(Dense(100, activation="relu"))
    model.add(Dense(100, activation="relu"))
    model.add(Dense(100, activation="relu"))
    model.add(Dense(n_inputs, activation="linear"))
    return model

def make_func_dataset(n_examples=30000, n_linears=15, n_categorical=4):
    linear = np.random.randn(n_examples, n_linears)
    categorical = [np.random.choice([0, 1, 2], size=n_examples) for _ in range(n_categorical)]
    categorical = [to_categorical(item) for item in categorical]
    return [linear, *categorical]

def run_simplest():
    X = make_func_dataset(n_examples=10**5, n_linears=30, n_categorical=0)[0]
    # model = build_std_func_model(30)
    model = build_std_seq_model(30)
    model.compile(optimizer="adam", loss="mean_squared_error")
    model.fit(X, X, epochs=100)

if __name__ == '__main__':
    # tf.config.set_visible_devices([], 'GPU')
    # run_functional()
    run_simplest()

Relevant log output
No response

@RinnetenseiQ,
May i know how many CPU cores you have? The following are the reasons why the CPU performance is higher than the GPU  in some of the model training cases.

For small models there will be no performance improvements when using GPU and you are going to benefit from GPU only when you have large weight matrices.

For small matrices it will be faster on CPU because it has higher frequency and this overhead of invoking kernels and copying is only worsens the situation. Try multiplying matrices of these shapes (10000, 10000)x(10000x10000). You will see that the GPU is much faster.

Try increasing number of parameters in your model. There is an overhead when invoking GPU kernels and copying data to/from GPU.

Also the overhead of invoking GPU kernels, and copying data to and from GPU, is very high. For operations on models with very little parameters it is not worth using GPU since frequency of CPU cores is much higher. If you compare matrix multiplication, you will see that for large matrices GPU outperforms CPU significantly. Reference. Thank you!


Update python package on PIP

Hi authors,
Thanks very much for your good algorithm to detect rare cells!
But it seems that your public pip version is not compatible with your repository. Besides, python package doesn't include those plotting functions in R packages which are crucial for people to recognize rare cells. It would be very nice if you can incorporate these functions into the python package.
Thanks again for your algorithms!
Yanshuo

Hi @poseidonchan,
Thank you for the hint!
Indeed, the readme file on PyPI was an older version and I fixed it in the lastest version 1.0.4.
Regarding the plotting functions, we are working on implementing them in the python package at the moment. For now, the standard scanpy plotting can be used to e.g. visualize the location of the top markers in the UMAP as seen in the tutorial, but the same easy-to-use plotting functions from the R package will be introduced as well!
Glad that you like the algorithm!
Greetings from Munich, Germany
Marco

Thanks!


Unbound Compile Failed on "linux/386" Platform

Describe the bug
Whenever I try to compile unbound inside linux/386 platform Dockers container it fails. But it compiles fine on other platforms. I can't find any solution.
#0 285.2 /usr/bin/ld: /tmp/unbound.acbOZI.ltrans7.ltrans.o: in function `tls_session_ticket_key_cb':
#0 285.2 /tmp/workdir/unbound/util/net_help.c:1550: undefined reference to `EVP_CIPHER_get_iv_length'
#0 285.3 /usr/bin/ld: /tmp/unbound.acbOZI.ltrans17.ltrans.o: in function `secalgo_hash_final.constprop.0':
#0 285.3 /tmp/workdir/unbound/validator/val_secalgo.c:208: undefined reference to `EVP_MD_CTX_get0_md'
#0 285.3 /usr/bin/ld: /tmp/workdir/unbound/validator/val_secalgo.c:208: undefined reference to `EVP_MD_get_size'
#0 285.3 /usr/bin/ld: /tmp/workdir/unbound/validator/val_secalgo.c:213: undefined reference to `EVP_MD_CTX_get0_md'
#0 285.3 /usr/bin/ld: /tmp/unbound.acbOZI.ltrans17.ltrans.o:/tmp/workdir/unbound/validator/val_secalgo.c:213: undefined reference to `EVP_MD_get_size'
#0 285.3 /usr/bin/ld: /tmp/unbound.acbOZI.ltrans1.ltrans.o: in function `remote_control_callback':
#0 285.3 /tmp/workdir/unbound/daemon/remote.c:3345: undefined reference to `SSL_get1_peer_certificate'
#0 285.3 /usr/bin/ld: /tmp/unbound.acbOZI.ltrans12.ltrans.o: in function `dtio_ssl_handshake':
#0 285.4 /tmp/workdir/unbound/dnstap/dtstream.c:1325: undefined reference to `SSL_get1_peer_certificate'
#0 285.4 /usr/bin/ld: /tmp/unbound.acbOZI.ltrans12.ltrans.o:/tmp/workdir/unbound/dnstap/dtstream.c:1350: undefined reference to `SSL_get1_peer_certificate'
#0 285.4 /usr/bin/ld: /tmp/unbound.acbOZI.ltrans13.ltrans.o: in function `ssl_handshake.part.0':
#0 285.4 /tmp/workdir/unbound/util/netevent.c:1436: undefined reference to `SSL_get1_peer_certificate'
#0 285.4 /usr/bin/ld: /tmp/workdir/unbound/util/netevent.c:1466: undefined reference to `SSL_get1_peer_certificate'
#0 285.5 collect2: error: ld returned 1 exit status
#0 285.5 make: *** [Makefile:369: unbound] Error 1

To reproduce
Steps to reproduce the behavior:
    git clone https://github.com/NLnetLabs/unbound.git && \
    cd unbound && \
    groupadd _unbound && \
    useradd -g _unbound -s /dev/null -d /etc _unbound && \
    ./configure \
        --disable-dependency-tracking \
        --prefix=/opt/unbound \
        --with-pthreads \
        --with-username=_unbound \
        --with-ssl=/opt/openssl \
        --with-libevent \
        --with-libnghttp2 \
        --enable-dnstap \
        --enable-tfo-server \
        --enable-tfo-client \
        --enable-event-api \
        --enable-subnet && \
    make install

Expected behavior
It should compile just like other platforms.
System:

Unbound version: latest
OS: bullseye-slim

Additional information
The Dockerfile I'm using to compile:
https://github.com/origamiofficial/docker-pihole-unbound/blob/main/latest/Dockerfile
Full Output
unbound log.txt

Unbound do not support i386 platform that's why it's happening. If you have a i386 platform I would suggest you to use my Bind9 image.


ft(cyctl): Delete modules functionality

closes #239
📑 Description

Implements module deletion functionality via cyctl command.

cyctl delete module <MODULE_NAME>

Added minimum spacing when no modules are present.

✅ Checks

[ ] I have updated the documentation as required
[ ] I have performed a self-review of my code

ℹ Additional context
Suggestion:

I believe, we need to added additionally functionality of deleting multiple modules

cyctl delete module MODULE_1 MODULE_2 MODULE_3 ...

Hey @siddhantprateek thanks for the PR, I think you should make some changes here:

Modify the Delete function something like this (it will help to delete multiple modules at once):

func DeleteModules(clientset *client.CyclopsV1Alpha1Client, moduleName []string) { //rest of code }

You can use something like this to get the input Module name in an array format:

Args:  cobra.MinimumNArgs(2)

and
deleteCommand, resourceNames := args[0], args[1:]

And also make changes in the DeleteModule function:
if len(moduleName) > 0 {}
else { // return error }

Other than this I think it works good !

Hey @siddhantprateek thanks for the PR. Will review it today.
I'd say we can have this solution that deletes a single module and then implement it for multiple modules in a different PR.

I've also added bit of error handling to DeleteModules, i'll create separate PR for multiple modules


[BEAM-13712][Playground] Add graph for python

[BEAM-13712] Add preparer to get and store graph for Python SDK

moved some from utils package to avoid cyclic dependencies

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM


Support SAML encrypted tokens

While testing fediz tomcat plugin with Sign&go IDP, I was facing issues as SAML Encrypted token are not supported.
The first commit is adding support for Encrypted assertion.
Then I was still facing issues, as encrypted assertion remove the necessity to sign the assertion.
The second commit proposes a way to disable assertions signature validation
The last issue I noticed was about an attribute statement with a space inside the name. The fix for that is the 3rd commit (I am not 100 % sure having space in attribute name is valid so I separate the commit)

@amergey Thanks for the PR. Could you separate all three issues into separate PRs please to make it easier to review them?

Encrypted assertion part is in https://github.com/apache/cxf-fediz/pull/55
Usigned assertion is in https://github.com/apache/cxf-fediz/pull/54
Attribute Name parsing fix is in https://github.com/apache/cxf-fediz/pull/56

Thanks! Please close this PR then if no longer needed.


Serialization errors with export on Databricks

A workaround was applied to solve issue #1847 using init scripts.
However new errors arose when calling the export:
It seems that Databricks use a custom HadoopConfiguration GlobalHadoopConfiguration that isn't serializable. We use SerializableWritable to pass the configuration to the workers for the FS discovery and copy.
Caused by: NotSerializableException: org.apache.spark.util.GlobalHadoopConfiguration
Serialization stack:
	- object not serializable class: org.apache.spark.util.GlobalHadoopConfiguration
	- object (class $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw$$iw$$iw, $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw$$iw$$iw@58ef2bea)
	- field (class: $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw$$iw, name: $iw, type: class $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw$$iw$$iw)
	- object (class $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw$$iw, $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw$$iw@68305186)
	- field (class: $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw, name: $iw, type: class $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw$$iw)
	- object (class $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw, $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw@2ff5b5ed)
	- field (class: $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw, name: $iw, type: class $line1866b642d1ac4207a239f3c39765385627.$read$$iw$$iw$$iw$$iw)
	- object

We use SerializableWritable to pass the configuration to the workers for the FS discovery and copy.

Hmmm... but why do we need to do this?  Could we "just" extract the necessary parameters from hadoopConfiguration into our operators?  Because it seems truly strange that we need the entire configuration to perform some operation, it should either already be on every worker or we should care about only a few fields from it.
@johnnyaug and/or @guy-har do you have more info?

We use SerializableWritable to pass the configuration to the workers for the FS discovery and copy.

Hmmm... but why do we need to do this?  So I had a look, and this is in order to create a FileSystem (which needs a configuration).  This is obviously problematic.
@johnnyaug and/or @guy-har do you have more info?

Not reproducible


IsPixelStage json value crash

Describe your bug here.
I wanna make a pixel stage but it make me crash with a strange message. Who can help me?
crash_2024-10-21_11'53'22.txt
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Neko, HashLink, or other build system
Did you edit anything in this build? If so, mention or summarize your changes.
No

How does your stage json look like?

It looks like you manually edited your stage JSON and forgot some letter, which makes it crash


Implement floor function.

This PR implements floor function with covering test for input of dtype float16, float32 and float64.

Thank you for a patch. It looks good except comments.

Please fix docs/source/reference/functions.rst.

Thank you checking my PR.
I fixed it.

Thank you! Great!!


Testing Challenge Branch

There is not good documentation or a good tutorial/branch around testing. It would be very valuable to have a good challenge around testing in order to tech the common experienced with smart contracts.

I can do that, I've already fully covered challenge1 and challenge2 with full test coverage. Do we want to use those challenges or do we want to create a new one?

These are the tests for challenge1: https://github.com/StErMi/scaffold-eth-challenge-1-decentralized-staking/blob/main/packages/hardhat/test/staker.js
These are the tests for challenge2: https://github.com/StErMi/scaffold-eth-challenge-2-token-vendor/blob/main/packages/hardhat/test/vendor.js

Awesome! I think using a challenge that someone has already completed could be helpful. We just want to have them walk through the full process of setting up and writing tests. Right now there isn't a robust way to learn or great documentation. The most important things to cover would be instantiating and interacting with contracts, making sure they are correctly implementing the async/await calls for chain data etc.
Is that helpful?

@captnseagraves In my blog post I explain how to do that
Go to https://stermi.medium.com/how-to-write-your-first-decentralized-app-scaffold-eth-challenge-1-staking-dapp-b0b6a6f4d242 and find the section  Exercise Part 3: Test Coverage
Would that be a good fit to integrate it into the challenge documentation? I know that I'm asking a lot but maybe reviewing my blog post (that is more a longer explanation of the challenge and how to do that) would be good to understand if that it's a good blue-print to use when we want to create a challenge explanation

@codenamejason would the issue be closed when I updated the second challenge with the updated readme (that cover test)?

@codenamejason I think that at this point we should think to add a meaningful contract to the master and add tests directly to the master. The master branch should be something people take inspiration from and use as the kickstart of the next project for both react/solidity.
what do you think? I've released a new blog post that takes the example of a "world purpose", could that be an example to use?
Here's the GitHub repo https://github.com/StErMi/solidity-template

@StErMi the mainnet-starter branch is the one to focus on for using for a production app.

move to challenges repo


Detect the CPU, install the same Bazel version

Motivation

Using x86_64 Bazel on Apple Silicon Mac's happens to work right now, but
when we want to start building arm64 binaries directly, that'll need to
change. This should preserve the current state of things while also
allowing for experimentation with only small changes.
Test plan

[x] Linux Buildkite CI
[x] Linux personal PC
[ ] Linux Stripe devbox
[ ] Linux Stripe CI
[x] macOS Buildkite CI
[x] macOS Stripe laptop
[x] macOS personal laptop
[ ] macOS Stripe arm64 laptop

I can't even get master to build on arm64, so I don't think I'm going to block this PR on it.

(this is ready for review now)


fix(oidc): store requested response_mode

Which Problems Are Solved
Zitadel never stored or returned the requested response_mode in oidc Auth Requests. This caused the oidc library to fallback to the default based on the response_type.
How the Problems Are Solved

Store the response_mode in the Auth request repo
Store the response_mode in the Auth request v2 events
Return the resonse_mode from the Auth Request v1 and v2 ResponseMode() methods. (Was hard-coded to an empty string)

Additional Changes

Populate the response_modes_supported to the oidc Discovery Configuration. When it was empty, the standard specifies the default of query and fragment. However, our oidc library also supports form_post and by this fix, zitadel now also supports this.

Additional Context

Closes #6586
Reported https://discord.com/channels/927474939156643850/1151508313717084220

Regarding tests:

Query mode is the default and already covered by current tests
Fragments are never send over HTTP, therefore can't be tested automatically.
Form_post needs a user agent that executed the returned JavaScript snippet, therefore can be tested automatically.

I've manually tested the 3 modes using the v1 login. :ok_hand:


Text color

Text color
In dark mode, when there is a lot of text, the text color will be blinding, perhaps the following colors can be adopted
.theme-dark {
    --text-normal: #93a1a1;
    --text-faint: #93a1a1;
    --text-muted: #93a1a1;

 }

.markdown-preview-view blockquote {
    color: #93a1a1 !important ;
}

before

after

Reducing contrast might cause problems for other users though. Have you tried lowering your moniter's contrast/ brightness?

Reducing contrast might cause problems for other users though. Have you tried lowering your moniter's contrast/ brightness?

I have a screen hang light, so lowering the brightness of the monitor doesn't work for me.
Adjusting the screen contrast might be a way to do it, I'm not sure how to adjust it on a Mac.

I'm sticking with the color palate of the Nord theme. If you'd like to use a darker font then definitely having your own custom CSS overrides is the solution.


Bad WebGL detection when Chrome disable "Use hardware acceleration when available"

Expected Behavior
Support WebGL.
Current Behavior
The browser support WebGL but not work when disable hardware acceleration.
from 5.0.0-rc3 ~ Now
Possible Solution
N/A
Steps to Reproduce

chrome://settings/system set "Use hardware acceleration when available" to disable
Open Example
throw exception and the PIXI.utils.isWebGLSupported will return false

WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support.

Environment

pixi.js version: 5.0.0-rc3 - ~
Browser & Version: _e.g. Chrome65 - ~
OS & Version: _e.g. Windows 10
Running Example: https://www.pixiplayground.com/#/edit/iYVa93CevZ3vAfQpvhNw1

Set
PIXI.settings.FAIL_IF_MAJOR_PERFORMANCE_CAVEAT = false;
before creating your renderer.
Since hardware acceleration is disabled, you're going to get terrible WebGL performance, and Chrome can report that to us. By default, if the browser itself says performance is going to be terrible, then we'll fail the WebGL check.
But you can set that flag to false to ignore the browsers recommendation and use WebGL anyway

PS. You'll need 5.1.0 or above of PIXI for this settings to exist


Add link to consultancies.

I feel semi-okayish to this.  I prefer just having companies in the CONTRIBUTORS file instead.   If there's a clear wayfor people to get on this list then it's okay.

LGTM.
@arianvp: I think, the consultancies list should be distinct from the contributors list. Someone can of course offer to work as a consultant without having contributed and vice versa. Of course, there's some overlap.
The way to get on this list is to create a PR, as stated in the comment above the list. @arianvp: How can we make this clearer?

@soenkehahn I somehow missed that line.

LGTM. I'll probably add myself there soonish =)

Not sure what the build failures are about...

@jkarni: CI in this repo is broken, unfortunately. Feel free to merge. Or fix the CI. :(


Remove old "require" statement from README

Does exactly what the title says. There was still a very old require statement in the Log only in development part of the README docs. This PR changes that for an ES6 Import statement.
I've also added a note that NODE_ENV can only be test. This is interesting to note for end-users since (probably among others) React-Scripts from Create-React-App sets NODE_ENV to test when running their test script.

Awesome


Can you  share the evalution metric code?  include PSNR, MSSIM, MSE, FID ,T-R ,T-P,T-H.

hello, Chongyu Liu, can you  share the evalution metric code?   thank you.

you can refer to the erasenet repo.
Guangtao Lyu @.***> 于2022年10月23日周日 16:46写道：

hello, Chongyu Liu, can you share the evalution metric code? thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/lcy0604/CTRNet/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ7RD3VDQWTMEWIBCLZB5XTWET3N3ANCNFSM6AAAAAARMGKFN4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

you can refer to the erasenet repo. Guangtao Lyu @.> 于2022年10月23日周日 16:46写道：
…
hello, Chongyu Liu, can you share the evalution metric code? thank you. — Reply to this email directly, view it on GitHub <#5>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ7RD3VDQWTMEWIBCLZB5XTWET3N3ANCNFSM6AAAAAARMGKFN4 . You are receiving this because you are subscribed to this thread.Message ID: @.>

that repo doesn't include FID.


UI improvements for the edit mode

:nut_and_bolt: Description: What code changed, and why?
UX identified some design issues in edit mode, this PR covered some of UX improvement changes.

:chains: Related Resources
https://github.com/chef/automate/issues/4808
:+1: Definition of Done
I have covered UX improvements which are mentioned below

Delete Data Bag - Button text: “Delete” ->  change to delete
Create/Remove Chef Server - The button on modal dialogue says “Delete” where on the drop down it says “Remove” we should make these the same. -  changed to delete
When you hover policy files, details page- the hover effect has some glitch. it not coverup the beta tag.
Client list page - Create client button misaligned
Delete popup modal width issue
Roles list page is misaligned when there is no data.
FIx pagination issue for the clients

:athletic_shoe: How to Build and Test the Change
Go to the `infrastructure tab` from the top navigation bar then you can see the `Chef Server`
If you have data then you can see the list of servers --> then you can check all the mentioned points.

:white_check_mark: Checklist

[ ] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[ ] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable

Great job on these fixes - all are working well for me 🎉
I noticed that on many of the delete modals, I'm seeing the content break out of the container when the browser is collapsed. Would be ideal to be fixed here but could also be addressed elsewhere.

I have added some more changes for the modals, when you get the chance please check it once.

Great job on these fixes - all are working well for me 🎉
I noticed that on many of the delete modals, I'm seeing the content break out of the container when the browser is collapsed. Would be ideal to be fixed here but could also be addressed elsewhere.

I have added some more changes for the modals, when you get the chance please check it once.

Thanks for the update Vinay - Ideally, the modal should still be flexible like before and the content inside is adjusted to fit as it shrinks.  I understand that the modal content designs are new and in flux right now, so I think this solves the issue for the time being 👍


[ci] stop using path resolve for all testcase

Works great, the post CI action require 37 secs instead of 58 mins now.


Only $populate if it's whitelisted

Summary
(If you have not already please refer to the contributing guideline as described
here)

[ ] Tell us about the problem your pull request is solving.
[ ] Are there any open issues that are related to this?
[ ] Is this PR dependent on PRs in other repos?

If so, please mention them to keep the conversations linked together.
Other Information
If there's anything else that's important and relevant to your pull
request, mention that information here. This could include
benchmarks, or other information.
Your PR will be reviewed by a core team member and they will work with you to get your changes merged in a timely manner. If merged your PR will automatically be added to the changelog in the next release.
If your changes involve documentation updates please mention that and link the appropriate PR in feathers-docs.
Thanks for contributing to Feathers! :heart:

Published as latest. Thank you!

Such a breaking change will destroy many online services. $populate should set in default whitelist.


Create Cart Page

Display all items
Display total number of items
Option to remove an item and add more of the same item
Button to back to shopping page
Button to the checkout page

Hello, I tried to solve the issue.
This is what I did:
Added a new Cart component to display all items, total number of items, options to remove or add items, and buttons to navigate back to shopping and to checkout.
You can review changes in this commit: https://github.com/lattaai13/JoseChaconUrias-GroceryStore-23/commit/ffa87949c00d56f9879d24c8f4c99c844077476b.

[!CAUTION]
Disclaimer: The commit was created by Latta AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

This issue was tried to solve for free by Latta AI - https://latta.ai/ourmission
If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.


Added Megamenu v4

Relates to #1188

Adds the new megamenu (v4.0.0) from NPM

Hey @Harry-Ross ,
It seems like the dropdown will be hidden by our new megamenu once we log in
1. Please fix this UI issue

Please action @Aibono1225 comment

Done - Updated the style 🙂:


Allow consumers to define tags

Allow users to define framework/app... specific tags.

@bensigelman @yurishkuro @michaelsembwever could you please review?


Add Jooan A6M variant

Just a different Wifi chip

please sync your fork, it does not let me merge the pr saying the head repo is out of date.


How to resolve INCOMPATIBLE_EXTENSIONS error

✅ Prerequisites

[ * ] Did you perform a cursory search of open issues? Is this question already asked elsewhere?
[ * ] Are you reporting to the correct repository (magic-sdk)?

❓ Question
I'm using magic-sdk 4.4.2 and @magic-ext/oauth 0.9.0. When trying loginWithRedirect as described here, I',m receiving this error:
Uncaught Error: Magic SDK Error: [INCOMPATIBLE_EXTENSIONS] Some extensions are incompatible with<EMAIL_ADDRESS>  - Extension `oauth` supports version(s) `>=2.4.6`
    at new MagicSDKError (sdk-exceptions.js:17)
    at Object.exports.createIncompatibleExtensionsError (sdk-exceptions.js:138)
    at SDKBase.prepareExtensions (sdk.js:83)
    at new SDKBase (sdk.js:107)

I've tried to downgrade to magic-sdk 4.0.0 and oauth extension version to 0.7.0 (got the instructions from support), but id did not resolve the issue. I've also tried other versions.
🌎 Environment

Software
Version(s)

magic-sdk
4.4.2

Browser
Brave Version 1.26.74 Chromium: 91.0.4472.124 (Official Build) (64-bit)

yarn
v1.21.1

Operating System
Ubuntu 18.04.5 LTS

Can you provide a reproduction of the issue in CodeSandbox? I'm using this to quickly test the problem but cannot reproduce: https://codesandbox.io/s/condescending-star-nvnlm?file=/index.html

Can you provide a reproduction of the issue in CodeSandbox? I'm using this to quickly test the problem but cannot reproduce: https://codesandbox.io/s/condescending-star-nvnlm?file=/index.html

I see you're using extensions: [new MagicOAuthExtension()] and the docs say: extensions: [new OAuthExtension()]. I'm using ClojureScript, I'll try to put it in sandbox.

I see you're using extensions: [new MagicOAuthExtension()] and the docs say: extensions: [new OAuthExtension()]. I'm using ClojureScript, I'll try to put it in sandbox.

Syntax differs slightly depending on whether you're consuming the SDK via CDN or NPM. When using our CDN, the extension class is prefixed with Magic* because it exists in the global namespace and we are aiming to prevent conflicts.

Took a deep dive into this issue and I believe it's related to an old cyclic dependency within the semver package. Apparently there's a known issue with bundling semver using Rollup that creates an unexpected behavior where semver.satisfies returns false always.
Related issues:

https://github.com/rollup/plugins/issues/879
https://github.com/npm/node-semver/issues/318

We are in the midst of a refactor that will bundle all Magic SDK dependencies together before publishing to NPM. I have run into this bug myself while implementing that change. I will try to resolve it for you from our side and ping this issue when the fix goes out (should be in v6.0.0).

Please give this a try with<EMAIL_ADDRESS>and let me know how it works for you. If the issue remains unresolved please feel free to ping this thread and I'll re-open the issue.


Performance

Ok this is getting ridiculous, why does showing the scroll down button lag the frames, why does loading older messages lag everything...

i think we're going to need to evaluate all the re-build scenarios. And figure out which widgets are rebuilding the most, and which can we avoid

Messages view is one that I'd love to avoid, but I'll probably have to modify the flutter framework to get some more performance. Been trying to fix that for ages but flutter has shitty bug in it

Messages view is one that I'd love to avoid, but I'll probably have to modify the flutter framework to get some more performance. Been trying to fix that for ages but flutter has shitty bug in it

And you're sure it's not fixed in later versions?

It is not, it's a root level issue with flutter. It's not really a bug persay, but it's just how it works. It's okay though because I've found a better solution which will fix a lot of issues

I think I've mostly fixed the performance issues, if there are more I'll fix them as I go but rn the app feels super snappy