Components with containers

Loving the storybook! Great job, I already added it to several of my packages to showcase their interfaces.
I've bumped into an issue, when a component contains a container that snatches its own data. The data are taken reactively from Meteor source. What is the workflow to accomodat these types of components?
<Component>
   <ContainerOfAnother />
</Component>

That's the kind of thing I'm looking at. With React Komposer, I use a way to disable the container functionality at all.
See: https://github.com/mantrajs/mantra-sample-blog-app/blob/master/.storybook/config.js#L4
I hope we can do much better job as well.

Looking for some ideas.

One option that comes to mind is stub the context.
Something like a more function-complete version of meteor-stubs could be useful for this.
Another idea is providing a parameter to ComposeAll that will include metadata about the component being composed. This could be a string, for the requirements of this set of functionality.
When in test mode, the composer could take a "stub composer" provided by the test and ignore the one in the original container file.
original container:
export default composeAll(
  'myComponentKey'
  composeWithTracker(composer),
  useDeps(depsMapper)
)(Component);

story file:
// will cause composeAll in the original container file to ignore the composers
// provided to it and wrap the dumb component using testComposer
stubComposer('myComponentKey', composeWithTracker(testComposer));

I have implemented my last suggestion for react-komposer.
It works pretty well, as long as you don't need more than one composer type for the same component type (which seems to me like a reasonable expectation).
If I have a component that depends on a composition, I can enable the test mode and register a stub composer for it, which will override the original composer:
original component:
// components/my_component.js
import React from 'react';
import OtherComponet from '../containers/other_component';

class MyComponent extends React.Component {
  render() {
    return (<OtherComponet foo="bar" />);
  }
}

export default MyComponent;

If not stubbed, it may fail to get data, so let's create a stub:
// components/.stories/composer.js
import OtherComponet from '../other_component.jsx';
import {
  createStubComposers, setTestMode, compose
} from 'react-komposer';

const myStubComposer = (props, onData) => {
  // get data here
  onData(null, data);
};
setTestMode(true);
createStubComposers(OtherComponet, compose(myStubComposer));

and now we can use MyComponet in our story:
// components/.stories/my_component.js
import React from 'react';
import { storiesOf, action } from '@kadira/storybook';
import './composer'; // this is the file that registers the composer stub. import it before MyComponent
import MyComponent from '../my_component.jsx';

storiesOf('core.MyComponent', module)
  .add('default view', () => {
    return (<MyComponent />);
  });

@arunoda , any thoughts?

@MasterAM overall, this seems like a good idea.
Send a PR and let's discuss.

@arunoda, PR sent.
Currently I use some fixtures located in a file under .stories as the alternative data source for the composer stub. The composer stub itself is set up in another file inside the .stories directory.
In the stub setup file I import those fixtures and the base component, use the fixtures in the stub composer function and call createStubComposers with the base component and the stub.
It is also possible use a completely different composer with the same component later on (if another component is using a composition that includes it) by overriding the stub composer for it. It can by done by calling the createStubComposers again with the same component and a different composer.
It all depends on the identity of the composer at the moment of invoking the function returned from composeAll(). The invocation is usually done in the file in which the composition is defined, so the file that sets up the stub should be imported before the actual composition file is imported.

you might want to try https://github.com/gavriguy/react-indie which has some similar concepts to react-komposer but takes a different approach for handling data defaults, data loading and errors. it lets the component itself deal with the ui of all of the above making it a perfect fit.
it even uses storybook to showcase how the component works.
(note: im the creator of react-indie)

@gavriguy great. And you can publish your storybook to GitHub pages.
Checkout react-cdk for this. It has the sample code to do it.

@MasterAM Some of us are following the Mantra spec, which usually has 2 composer types for each component type, so I had to use a different approach.
@arunoda It doesn't look like https://github.com/gavriguy/react-indie would work well with mantra-core either.
I added a composeAllWithStub function on top of the setTestMode. Will submit PR shortly.

I run @MasterAM 's setTestMode(), then
export default composeAllWithStub([
  composeWithTracker(composer),
  useDeps(depsMapper)
],[
  compose(composerStub),
  useDeps(depsMapperStub)
])(Component);

Please check mantrajs/mantra-sample-blog-app#110 to see a working example.

@ihealthdavid
AFAICT, You can set the composers however you like for the original component, so you can use the Mantra spec (as I do, too). What prevents you from specifying as many composers as you like for a component? Can you show a simple example where it fails?
I created createStubComposers the way I did because I did not want to do "scaffolding" for tests in the application code.
@arunoda It does not look like PRs for ReactKomposer are getting much love. Any chance to change that?

@MasterAM I'm taking all of them in this week. Stay in touch.
Sorry about the delay.

Hi all, I've looked at all these options. They are great.
Anyway, I come up with something which looks like simple to me.
So, I implemented that. See: https://github.com/kadirahq/react-komposer#stubbing
I hope that's more than enough.

Thanks, @arunoda; this looks fairly elegant and useful. I will implement it soon in one of my apps which uses StoryBook and let you know how it went. :smile:

@MasterAM great.

Is there a way to deal with containers-in-component without react-komposer? We use Meteors createContainer and ran into the same problem ...

Yes. There is a way. Check Kadira Voice in few hours.

@sokki See: Stubbing React Containers for Testing

I think we could close this.

Add ref: https://github.com/kadirahq/getstorybook/issues/1

Guys, sorry for reviving this thread, but I am interested in your opinion. What really works for me for unit testing is to load all all components and containers as part of the module. Therefore module contains: { actions, components, modules }.
Then, in the component I load the components from the context from the given module. Such as:
const { Markdown } = context.modules.core.containers;

return <Markdown text="A" />

Do you see any issues with this approach? It makes unit testing a breeze.


github-workflows: Disable running functional tests jobs for now

These still require some tools to be installed.
Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

:+1:


Check composer.json autoloader

Your composer.json autoloads the folder /folderindex mapping it to the App\ namespace, however there are just classes namespaced under Kraftausdruck\Extensions in that folder. I wonder if the composer.json would be more correct by putting Kraftausdruck\ as a PSR-4 autoloading namespace or if everything is right and I didn't get how that works (very possible, indeed, and in that case, that would be an educative moment for me).

Ohh good catch! This really is wrong. Definitely a copy/past leftover - Silverstripes autoloader prevents bubbling up. It’s more of an optimization with Silverstripe not required.


Enhancement: Improve the README for Better Clarity and Usability

Hello,
I recently came across the DataverseSQL repository and found the concept intriguing. However, I noticed that the README could be more informative and user-friendly. A well-structured and detailed README is crucial for understanding the purpose, usage, and technology stack of a project, especially for first-time visitors or potential contributors.
Suggested enhancements:

Project Overview: A brief summary of the project's purpose and its significance in relation to Power Platform, Dataverse and SQL and analytics.
Technology Stack: Details about the technologies and tools used in the project.
How to Use: Step-by-step instructions or examples on how to use the repository, ideally with usage scenarios or case studies.
Contribution Guidelines: If open to contributions, guidelines on how others can contribute effectively.

An improved README would not only make the DataverseSQL project more accessible but also potentially attract more users and contributors.
Thank you for considering this suggestion.
Best regards,
Maks

@maksii
Thank you for your interest in this repository and correct comments!
I have made changes to the Readme document.


The tokio-tar dependency seems unmaintained, and it is broken on PowerPC

The current version of uv depends on the tokio-tar crate:
https://github.com/astral-sh/uv/blob/8e86cd0c7385643b9c017bb25adbd4f5ca895b37/Cargo.toml#L132
However, the upstream repository has not seen any activity for 10 months now, and the project seems dead. It is currently broken on PowerPC, and I've filed a pull request to fix it. However, I don't hold my hopes high and in general, the repository has a feeling of a fork of async-tar that wasn't really meant to be maintained (note that it doesn't even have a bug tracker).
That said, krata-tokio-tar seems to be a fork of the fork that has had some recent activity, so I've filed my pull request there as well.
Perhaps a better option would be not to rely on tokio-tar (or async-tar) at all.

Thanks for raising this issue. I’m working on packaging uv for Fedora, and tokio-tar is one of a handful of dependencies I hadn’t gotten around to investigating yet. Even if the dependency stays, your PR will be helpful as a downstream patch.

Seems reasonable, cc @BurntSushi

For the record, I've gotten an initial response on the krata-tokio-tar fork but they haven't found time to review the PR yet.

I’m trying to build a Fedora package rust-tokio-tar using https://github.com/edera-dev/tokio-tar/pull/1, and it’s working on x86_64, aarch64, and ppc64le, but still failing on i686:
test src/builder.rs - builder::Builder<W>::append_dir_all (line 390) ... FAILED
failures:
---- src/builder.rs - builder::Builder<W>::append_dir_all (line 390) stdout ----
Test executable failed (signal: 6 (SIGABRT) (core dumped)).
stderr:
memory allocation of<PHONE_NUMBER> bytes failed
failures:
    src/builder.rs - builder::Builder<W>::append_dir_all (line 390)
test result: FAILED. 9 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 5.01s

…and on s390x:
test header::set_metadata_deterministic ... ok
failures:
---- insert_local_file_different_name stdout ----
thread 'insert_local_file_different_name' panicked at tests/all.rs:1103:5:
assertion failed: entries.next().await.is_none()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
    insert_local_file_different_name
test result: FAILED. 50 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.05s

At a glance, the allocation on i686 is suspiciously large, and endianness issues are always prime suspects for s390x-specific problems, but I haven’t tried to investigate these in detail yet.

It looks like the insert_local_file_different_name is flaky, roughly less than 20% of the time, on s390x, but it also occurs (more frequently) on aarch64. I have also observed flaky failures in other tests on aarch64 – at least large_filename and writing_files, and my notes indicate that I saw path_separators panic in a previous attempt.
I think a reasonable conclusion here is that tokio-tar has significant race conditions, at least on some architectures, and should have engaged in much more fearful concurrency.

That said, krata-tokio-tar seems to be a fork of the fork that has had some recent activity, so I've filed my pull request there as well.

I tested krata-tokio-tar, and in ten attempts I observed flaky test failures on at least x86_64, ppc64le, aarch64, and s390x, so it looks like it also suffers from similar problems.

It turns out that flaky test failures, particularly insert_local_file_different_name, may occur on any architecture, including x86_64. I was able to reproduce this with just
$ gh repo clone vorot93/tokio-tar
$ cd tokio-tar
$ for i in $(seq 1 1000); do cargo test || (echo "FAILED ON ITERATION $i"; sleep 3600); done

This failed on iteration 82. When I tried cargo test --release, it failed on iteration 25.

Could you perhaps also try async-tar? Apparently tokio-tar was forked from that but it had a few changes since, and I don't know if they were forward-ported to tokio-tar.

We can't really use async-tar because it's built on async-std and we're using tokio.

I haven’t attempted to build an RPM package for async-tar or test it on architectures other than x86_64 (especially in light of @charliermarsh’s comment), but I did try repeatedly running cargo test, with and without --release, as in https://github.com/astral-sh/uv/issues/3423#issuecomment-2124671700, and I haven’t managed to get it to fail so far.


[AIRFLOW-2533] Fix path to DAG's on kubernetes executor workers

Make sure you have checked all steps below.
JIRA

[X] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2533

Description

[X] Here are some details about my PR, including screenshots of any UI changes:
When triggering a DAG using the kubernetes executor, the path to the DAG on the worker node is not properly set due to the modification of the command that is sent to the pod for the worker node to perform.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Prior to removing airflow command modification:

After removal of modification:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[X] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

LGTM, less is more. Lets see what Jenkins will tell us.

Thanks @Fokko , looks like one of tests failed because of
KIP: Failure: SkipTest (Kubernetes integration tests require a minikube cluster;Skipping tests [Errno 2] No such file or directory)
----------------------------------------------------------------------
   No Traceback
   SkipTest: Kubernetes integration tests require a minikube cluster;Skipping tests [Errno 2] No such file or directory

Have you seen this before?  Weirdly did not that experience that here https://travis-ci.com/bnutt/incubator-airflow/builds/74708974 with this change https://github.com/bnutt/incubator-airflow/compare/432ac718b14e...3a3227856aa6.

Codecov Report

Merging #3470 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #3470      +/-   ##
=========================================
- Coverage    76.9%   76.9%   -0.01%
=========================================
  Files         203     203
  Lines       15119   15119
=========================================
- Hits        11628   11627       -1
- Misses       3491    3492       +1

Impacted Files
Coverage Δ

airflow/models.py
87.32% <0%> (-0.05%)
:arrow_down:

Continue to review full report at Codecov.

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

👍 This PR fixed my problem, why not been merged yet? we need it !


Tooltips on flex full-height containers glitch and appear off-center on IE11

Hi,
I stumbled upon a browser-specific bug with tooltips today. So far I've been able to reproduce it with:

Windows 7 + IE11
Windows 10 + IE11

The problem appears when the document body is set as a flex container and forced to span the full height of the viewport. This is usual when using footers that stick to the bottom of the page.
The main content then is set as flex: 1 0 auto; and the footer and header stick then to its respective positions.
On IE11, when using this kind of configuration, tooltips will glitch the page for a moment, as they make the scrollbar appear and disappear quickly, and then will be positioned off-center as a result of that glitch (the scrollbar will move the components and Popper.js will calculate the position with the scrollbar, then the scrollbar disappears and the tooltip is no longer in the right place).
This is the end result:

Attaching an absolutely positioned element on the document body when it is a flex container as I've described, will cause the scrollbar to appear on IE11. This is the root of the problem.
I've fixed this at work with a pretty simple addition to the .tooltip class. If the position is set to top left by default, attaching it will not cause the scrollbar to appear. So this would fix the problem (with no side effects for other browsers that I've tested):
.tooltip {   left: 0;   top: 0; }
A minimal example of the issue that I'm mentioning is availible here (browse with IE11): https://codepen.io/ReyJamonico/pen/PQOoQo
The fix is commented out as well.
I would be open to creating a PR for this fix if it saves time.

Had the same issue. Quickly flashing the scrollbar due to content added to body in IE11 on Windows 10. Your solution fixed it.

Given the age of the issue and v5 dropping IE11, I'm inclined to call this one a stale won't fix. I do wonder if changing the container option for the tooltip would solve these issues vs custom CSS, which we can't unilaterally add as far as I can tell.

Given the age of the issue and v5 dropping IE11, I'm inclined to call this one a stale won't fix. I do wonder if changing the container option for the tooltip would solve these issues vs custom CSS, which we can't unilaterally add as far as I can tell.


Update billing-spending-limit.md

@jlian,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Add React Router

Fixes #94
Describe your changes
Describe here
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added thorough tests

Codecov Report

Merging #102 (ae332a1) into dev (26b67f1) will decrease coverage by 0.43%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #102      +/-   ##
==========================================
- Coverage   60.20%   59.77%   -0.44%
==========================================
  Files          42       42
  Lines        1626     1626
  Branches      179      179
==========================================
- Hits          979      972       -7
- Misses        629      637       +8
+ Partials       18       17       -1

Flag
Coverage Δ

backend
61.96% <ø> (ø)

dev
59.77% <ø> (?)

frontend
43.52% <ø> (-3.63%)
:arrow_down:

staging
?

unit
59.77% <ø> (-0.44%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

frontend/src/components/App.tsx
54.54% <ø> (ø)

frontend/src/components/AdminView.tsx
10.52% <0.00%> (-42.11%)
:arrow_down:

frontend/src/components/PollAnsweringPage.tsx
50.00% <0.00%> (+50.00%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update README.md

Thanks for the submission 👍

Cool!
On Mon, Nov 20, 2017, 21:06 Marco Stadler<EMAIL_ADDRESS>wrote:

Merged #1 https://github.com/thesplunker/Splunkenizer/pull/1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thesplunker/Splunkenizer/pull/1#event-1350637572, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AgNWvHHXNRDJJ-hdenKcrSvatjTLzby2ks5s4dungaJpZM4Qj34Y
.


Preview doesn't open in default browser

I'm using Windows XP SP2 and have Chrome as my default browser. Issuing the command always opens the preview in IE, even if IE is not currently running.
I've had a look in MarkdownPreview.py but there's no explicit mentioning of the browser used to preview the file.

humpf. yes, looks like theres something missing on windows and webbrowser.py :/
http://hg.python.org/cpython/file/5661480f7763/Lib/webbrowser.py#l522
ill try to find a workaround. if i cant ill setup a settings where you can tweak the default browser. oki ?

Great find! Yes, a setting for the preview browser would be nice.

could you please try with the last commit ? i just forced the default browser for windows.
look likes it works on my VM (xp)
tell me thanks

Thanks for the quick response.
Now it doesn't open any browser window at all. There's no error in the console either. I thought about adding Chrome's browser string in webbrowser.get() by hand, but according to the docs there isn't any.
The code looks like it should work, but it doesn't. It could be a bug with the webbrowser library. Maybe the last resort should be to have a user setting where you can define, manually, the browser you want to use.

yes i played with webbrowser.py, trying to add chrome, but without luck.
i reverted my last change and i'll add a settings asap
strangely it works nice on my VM with or without that change...

The only way to open in Chromium (in my case on ArchLinux) is to hardcode it, because there isn't any browser string in webbrowser library. Following replacement in MarkdownPreview.py:47 works for me:
webbrowser.get('/usr/bin/chromium %s').open(tmp_html.name)
Chromium is already default browser but webbrowser just recognize an instance of BackgroundBrowser.

this webbrowser.py definitely sucks :/
ill try to find a workaround with a list of default locations and a setting to hardcode the path.

On Linux you may could rely on the fact that all (important) executables are inside the $PATH variable. In that fact a simple call of chromium/chromium-browser or google-chrome should work. Otherwise you could previously check the existance with which chromium etc.
Good luck!

I have same problem on KDE (ubuntu 11.10). Here default browser opened by plugin is Konqueror.
I guess that default 'open' action for html files of desktop should be used instead force to open in a browser, so I used desktop module [1] instead webbrowser module.
I added desktop module to repo since I don't know how make Sublime install packages in it python environ and this is a fast fix. The patch [2] add desktop module and change MarkdownPreview.py to use desktop module.
I don't know if works on Windows, don't have windows to test. If someone can test should be good.
I can do a pull request if change is good :).
[1] http://pypi.python.org/pypi/desktop
[2] https://github.com/chronossc/sublimetext-markdown-preview/commit/39bbd2a0ecb2a1f97663a5e8ebb2eeac9f8f2d86


Grok exporter returns single output for multiple same log lines

Hi Fstab,
My Log file has many log lines which is exactly same and i want them to all the log lines as output of the grok exporter( i.e in /metrics page). But it seems the grok Exporter returns only one line for those multiple log lines.
Example;
Log lines...................................................................................................................
172.xx.xx.xx - - [22/feb/2021:01:09:50 -0800 - "POST /fstab/grok_exporter/issue HTTP/1.1"<PHONE_NUMBER>32  172.xx.xx.xx - - [22/feb/2021:01:09:50 -0800 - "POST /fstab/grok_exporter/issue HTTP/1.1"<PHONE_NUMBER>32
The output i  want in grok page......................................
log_monitoring{code="200",date="22/feb/2021:01:09:50 -0800",load="681",method="POST",path="/fstab/grok_exporter/issue"} 323232
log_monitoring{code="200",date="22/feb/2021:01:09:50 -0800",load="681",method="POST",path="/fstab/grok_exporter/issue"} 323232
But the orginal output is:
log_monitoring{code="200",date="22/feb/2021:01:09:50 -0800",load="681",method="POST",path="/fstab/grok_exporter/issue"} 323232
Is there a way to get both the log line in the ouput.
thanks

It looks like you are using a gauge metric with 323232 as a value. You could use a counter metric and 323232 as a label. For example, if you call the label n you would get:
log_monitoring{code="200",date="22/feb/2021:01:09:50 -0800",load="681",method="POST",path="/fstab/grok_exporter/issue" n="323232"} 2

The metric counts the number of occurrences, and 2 means that this exact combination of label values was observed twice.


GS watcher error in test_layernorm_sharded.py::test_layernorm_sharded_rm

This was working early January, but recent changes lead to PCC errors when watcher is enabled on Grayskull. To reproduce:
TT_METAL_WATCHER=30 pytest tests/tt_eager/python_api_testing/sweep_tests/pytests/tt_dnn/test_layernorm_sharded.py::test_layernorm_sharded_rm -xv
        ref_lnorm = ref_fn(in0 + in1, in0.shape[-1:], gamma.flatten(), beta.flatten(), epsf)

        passing, output = comp_pcc(tt_got_back, ref_lnorm, 0.999)
        logger.info(output)
>       assert passing
E       assert False

tests/tt_eager/python_api_testing/sweep_tests/pytests/tt_dnn/test_layernorm_sharded.py:184: AssertionError

@tt-aho @yugaoTT please have a look as only you two have touched this file

I'm not seeing any errors locally, running TT_METAL_WATCHER=30 pytest tests/tt_eager/python_api_testing/sweep_tests/pytests/tt_dnn/test_layernorm_sharded.py::test_layernorm_sharded_rm -xv

@TT-billteng can we close it if this is no longer in CI?

sweep test added back and merged, I'll close


paragraphs getting removed in reading mode

can you add an option for them to stay? i have some chat history like documents where the lack of paragraphs looks really confusing in this theme, otherwise i'm a quite big fan of it. am i missing an option somewhere which does that? i honestly have no idea and i'm also not sure what CSS element does this, i'd prefer it as a toggleable option

Thanks! This was just a bug in my view: it doesn't need an option it should just keep paragraphs in reading mode.
I'm not sure when this happened, as I seldom use reading mode myself, but try version 3.0.7 and let me know if it's working for you. It should behave similarly to the default theme: paragraph breaks keep their spacing, but multiple breaks following each other collapse into a single break in reading mode.

just updated, paragraphs are there now!
what do you mean with the last sentence though? i never observed such behaviour of paragraphs....  do you mean like if i press enter multiple times in a row?

i actually liked how narrow the editor content was in the previous version in reading mode, can you restore that while keeping the paragraphs? i feel like it was part of this themes unique character

It's always interesting which parts appeal to people! Do you like it narrower just in reading more, or in both reading mdoe and live preview?
I've been trying to keep reading mode and live preview as similar as I can make them, but since I don't use reading mode much anyway, and there are limitations preventing them from being perfectly identical, perhaps I should understand more about what people want from reading mode.

it seems to add additional paragraphs in editing mode now

The difference in behaviour comes if you have two consecutive empty lines. In editing modes (live preview mode or source mode) these will appear as two separate lines, but in reading mode they'll be collapsed into a single empty line. This derives from the underlying behaviour of Markdown: reading mode is equivalent to rendering Markdown as HTML, and collapsing empty whitespace is standard HTML behaviour.

hmm, i liked the narrowness in reading mode specifically. but i actually wouldn't mind if it would be narrow in editing mode as well. you could also make it a toggle in case not everyone likes it? i always think that's a good idea for such specific style stuff, not everyone likes everything, but i'm not sure to which extent a toggle is possible.

i always think that's a good idea for such specific style stuff, not everyone likes everything

I agree, but also not everyone wants to spend their time customising every detail. I do, but I'm writing a whole theme anyway! I'd like Kakano to have a default appearance that has a good default appearance for people who don't care to tinker with the details, with settings for things that genuinely make a difference.
Based on this thread, it seems like line width in Reading View is one of those things! I've added a separate setting for it in version 4.1.0, so it can be different from Live Preview.
I'll add a credit to you in the README, with a link. I can use your Github profile, unless there's some other URL you'd prefer.

Sometimes editing themes can get a bit tedious, yeah...
Thank you, the github profile is fine.


ResourceYAMLEditor: onChange doesn't fire any event when typing the the yaml document

Hello
In our project we're using the ResourceYAMLEditor to perform updates on our CRs.
I have a callback configured to listen to all the changes:
            <ResourceYAMLEditor
              initialResource={YAML.stringify(fromState.cr, null, '  ')}
              onSave={updateModel}
              onChange={() => {
                console.log('Event fired!');
                dispatch({
                  operation: ArtemisReducerOperations.setYamlHasUnsavedChanges,
                });
              }}
            />
          </Suspense>

Unfortunately when I'm executing this, there's no log in my console indicating changes:

Sorry I opened this issue in wrong project


Added support for indicating directionality on Graphs

Adds support for arrows on Graph edges to allow indicating directionality of graphs. uses same trick as VectorField to render the arrows.

[x] Closes https://github.com/ioam/holoviews/issues/2521
[x] Add gallery example
[x] Add section to networks user guide

Simple example:

Real data example:

Done the requested renaming so I'll go ahead and merge.


mbed-edge-examples: use bitbake gitsm fetcher

@esajaa can I get admin rights to merge this

@x85446 Esa might be on summer holiday still. I've added edge-gw-austin team with write access to the repository.

Hi, sorry for the late reply, I was on summer holiday as suspected. I upgraded the access for the edge-gw-austin to admin level.


migration problems...

While CI run i get a migration error, related to djangocms-blog and cmsplugin_filer_image:
$ pip freeze
...
cmsplugin-filer==1.1.1
Django==1.8.13
django-cms==3.3.0
django-filer==1.2.2
djangocms-blog==0.8.5
...
Creating test database for alias 'default'...

Traceback (most recent call last):
...
django.db.migrations.graph.NodeNotFoundError: Migration djangocms_blog.0007_auto_20150719_0933 dependencies reference nonexistent parent node ('cmsplugin_filer_image', '0003_mv_thumbnail_option_to_filer_20160119_1720')

Full CI output: https://travis-ci.org/jedie/PyLucid/jobs/140795585
Any idea, why this happen?!?

@jedie did you removed cmsplugin filer custom migration path from MIGRATION_MODULES?

Yes, that was the problem and fixed with: https://github.com/jedie/PyLucid/commit/6aeb88a0802e090e7c332ca4b928e24421ea40b5
Thanks!


Add Balanced Classification Data Splitter

fix #973
Perf test results here
Summary:

The data sampler performs slightly worse (in holdout log loss, holdout f1, and time to fit) compared to the original StratifiedKfold
This performance might be due to our default values for min_samples/min_percentage, so might be useful to do tuning.

@bchen1116 I left a few comments on the perf test doc, feel free to send me an invite if you wanna chat about any of that! Will review code shortly


[Bug]: Invite process fails when DMs turned off

What happened?
A person with DMs turned off in their discord settings cannot go through the accept invite process.
The person will be unable to see pending invites or accept invites for pairing since the process requires DMs to work. It is common for people in many NFT servers to turn off DMs due to the vast number of spam DMs. An error will be thrown when the bot attempts to send a DM. In this case one option would be to have a channel with pairing requests where people are tagged via <@discord_id_here> so that they get a red indicator by the channel and can choose to see why they have been tagged (to have a pairing session).
I am happy to work on this and will add it to the Project board if you want to give me perms @mbuxmann.
How to reproduce the bug?
Go to User Settings in Discord.
Make sure the following setting is toggle off as shown here:

Have someone send you an invite for pairing. You will never get the DM.
Additional information
My proposed solution above is, send a fallback message to a pairing channel where someone will be tagged with a message that gives them the command to execute if they accept the pairing invitation, something like /accept-invitation invitation {id_here}

Screenshot of what the proposed solution looks like in a log channel.

n

HI @jimthedev,
This is much needed and I really appreciate it, thank you very much! I've given you write permissions so you should be able to add/edit things on the project board now.

Great, thanks @mbuxmann!


[BUG] - Problem with app

Describe the bug
Won't update / install
Smartphone (please complete the following information):

Device: Xiaomi Mi9lite
Android Version: Android 10
App Version: 3.4.8

To Reproduce
Install, @90% error: not installed
Expected behavior
Install complete
Screenshots (Only if necessary)
Additional context
App Version 3.4.7 installs fine
No logs

Hello! Thanks for reporting this. I found the issue with the app signature and rebuilt the latest release. It should now be fixed here.


Implement F5 "class" command

I've partially implemented the "class" command (https://devcentral.f5.com/wiki/irules.class.ashx). Our iRules use it quite a bit, and trying to handle it with mocks was becoming painful.

Looks great @jamespic ! I think it would make sense to add some documentation to the readme too - could you do that, please?

Any chance of this being merged in? We might use testcl, but we depend on class matching a lot.

Sorry, this is my bad. @landro asked me to add some documentation, and it kind of fell off my radar. There's some basic documentation now, so it's hopefully closer to being mergable.

Hi there! I'll see if I can get the merge in tonight. Stay tuned.


Why Plugin name is Github3 instead of Github only ?

It is more of a discussion question. We couldn’t we change plugin name ?

The light theme code comes from https://plugins.jetbrains.com/plugin/12271-github-3-color-scheme, I made few changes to the color. I don't understand why he called this github3, I think he is at least professional. I guess this is the third edition theme color of github. We can change the name of the theme, but I’m not sure if it’s a good experience for existing users.

Okay, So we could rename it right ?
but before that, Will it effect people like us who have installed this plugin already with Github3 name ?

Yes, I think we can. You know the result after you do it, don’t you? Ha ha! Even if there is a problem, the worst case is just to change back to the original name.

I think its not super important now, we keep it on hold.
I am actually waiting for v1.1.0 but seems like it will not have Github3 Light theme, Could you please take a look at https://github.com/jiyuan0125/Github3/issues/22
Also when I will get Latest version from Jetbrains Store ? I am eager to try it out.

https://github.com/jiyuan0125/Github3/commit/cb2b2277ab86d3665b9fc1892c4a3f70f0ec4ef1 fixes this issues, only project ID is kept with github3 as it will be linked with Jetbrains Store


Feat: adv_core/adv_dhcp_server - Add multiple features

Add multiple features. See CHANGELOG.
Also greatly improve role rendering time.

Note: CHANGELOG will be sorted at merge, since it was sorted in another PR.


__('Validation') returns an array instead of a a string

Laravel Version
11.22.0
PHP Version
8.3.10
Database Driver & Version
No response
Description
Translation of the word Validation does not work:
in tinker, try this:
echo __('Validation');
and you will get this result:
 WARNING  Array to string conversion.

Steps To Reproduce
new clean laravel app, open artisan tinker and execute this command:
echo __('Validation');

The limitations has been described in the documentation: https://laravel.com/docs/11.x/localization#using-translation-strings-as-keys

Please see many previous issues about this.


Domino elements injected into CDI beans are retained across requests

This seems to be a generalized version of https://github.com/OpenNTF/org.openntf.xsp.jakartaee/issues/61 , but occurs even when a bean is @RequestScoped or @Dependent.

What if we make those CDI beans @RequestScoped ? I think your CDI bean provider can be configured so that those injections are request scoped. Is this an option you are valuating ?

I originally figured that was the problem, but doing that didn't fix it - it seems that the proxies are actually retained and not replaced with new values even when marked as @RequestScoped, and I'm not sure why. I had some success in MVC with marking the bean being injected into as @Dependent, but that's not consistent: https://github.com/OpenNTF/org.openntf.xsp.jakartaee/issues/61

Got, it


update README

The only example command of the readme fails...
import mistune
mistune.__version__
'0.8.4'
mistune.html('test.md')
AttributeError: module 'mistune' has no attribute 'html'

NOTE: This is the re-designed v2 of mistune. Check v1 branch for earlier code.

v2 is not released yet. But, what you are looking for is v1 branch code.

I'm just saying, that could be made clearer in the README. Just as a feedback from a first-time user.

I understand, going specifically to v0.8.4 readme got me the right readme. Confusing was that the pip version is very recent yet the master's readme already further. But fine, my mistake. Thanks for the work.


Use server side in node.js?

Was thinking to use this in node.js server side when generating email and adding the .ics as an attachment.  Would that work?

While browsing the source of this project, I discovered a similar project which is targeting node first:
https://github.com/adamgibbons/ics
Maybe it will suit your needs.


Rewrites the ensure_text implementation

Borrows the ensure_text_type function's implementation from Zarr and uses it to rewrite the ensure_text function. Basically it makes sure any bytes-like data can be encoded as text with zero-copy. Also avoids getting muddled in Python 2/3 details as well, which should make it easier to maintain.
TODO:

[ ] Unit tests and/or doctests in docstrings
[ ] tox -e py37 passes locally
[ ] tox -e py27 passes locally
[ ] Docstrings and API docs for any new/modified user-facing classes and functions
[ ] Changes documented in docs/release.rst
[ ] tox -e docs passes locally
[ ] AppVeyor and Travis CI passes
[ ] Test coverage to 100% (Coveralls passes)

Hello @jakirkham! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file numcodecs/compat.py:

Line 32:9: E741 ambiguous variable name 'l'
Line 33:9: E741 ambiguous variable name 'l'

Not sure what is up with the coverage report. When drilling down into it, am seeing 100% on the individual files.


Fix spelling

Description
Minor update to fix spelling in a few comments
Motivation and Context

Clean up spelling errors reported by https://goreportcard.com/report/github.com/hyperledger/fabric#misspell
How Has This Been Tested?

Ran make checks. No new tests as this PR only updates comments.
Checklist:

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

Signed-off-by: Sheehan Anderson<EMAIL_ADDRESS>

LGTM
Reviewed-by: Greg Haskins<EMAIL_ADDRESS>


Attempted import error: 'Provider' is not exported from 'react-redux'.

What version of React, ReactDOM/React Native, Redux, and React Redux are you using?
"react": "^17.0.2",
"react-dom": "^17.0.2",
"react-redux": "^7.2.5",
"react-router-dom": "^5.3.0",
"react-scripts": "4.0.3",
"redux": "^4.1.1",
What is the current behavior?
import { Provider } from 'react-redux';
i have imported provider from react-redux but it is showing error not exported from react-redux
What is the expected behavior?
it should work
Did this work in previous versions of React Redux?

[X] Dont know using this first time

We definitely do<EMAIL_ADDRESS>Something is wrong with your build tooling. This isn't a bug on our end.

let me re build and run the project

I faced this problem because I wrote {provider} with small case of "p" but when I wrote
import { Provider} from "react-redux" it works fine !


Constant RuntimeException Folder.php line 393 while updating plugins

After an upgrade from 1.6.0-rc.4 to the latest Grav version (releases: testing), I tried to update plugins :
01. Admin Panel     [v1.9.7 -> v1.10.0-beta.4]
02. Form            [v3.0.0-rc.4 -> v3.0.7]
03. Login           [v3.0.0-rc.4 -> v3.0.3]
04. Pagination      [v1.4.1 -> v1.4.2]
05. Problems        [v2.0.2 -> v2.0.3]
06. Widget          [v1.3.0 -> v1.3.2]

but if failed at one moment :
Preparing to install Admin Panel [v1.10.0-beta.4]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...    ok
  '- Success!

Preparing to install Form [v3.0.7]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...    ok
  '- Success!

Preparing to install Login [v3.0.3]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...
In Folder.php line 393:

  [RuntimeException]

Then, when I retried, it said :
01. Pagination      [v1.4.1 -> v1.4.2]
02. Problems        [v2.0.2 -> v2.0.3]
03. Widget          [v1.3.0 -> v1.3.2]

and it failed again :
Preparing to install Pagination [v1.4.2]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...    ok
  '- Success!

Preparing to install Problems [v2.0.3]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...
In Folder.php line 393:

  [RuntimeException]

Maybe one important information
When I first tried to update the plugins, I previously reset the global system.yaml gpm release field to "stable", because I saw that it was on "testing" (wich was used for the self-upgrade), and I would like to set it to "stable" for production environment (while I did let it to "testing" on local).
So, the local CLI self-upgrade of my Grav project was made under "testing", but then, the first attempt of plugins update was made under "stable". Then, when it failed, I reset back the global system.yaml channel to "testing", and the above code excerpts are coming from that second and third attempt. ;)

After investigation, it may be due to files permissions. But I never changed anything under Windows 7, neither on my Xampp config (not mentioning that some of the plugins succeed in updating).
I re-tested to install one missing plugin (the problems plugin) with the CLI :
Preparing to install Login [v3.0.3]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...
In Folder.php line 393:

  [RuntimeException]

So I tried to install it directly from the admin panel. It said it succeed, but in fact the plugin isn't installed, and an alert is showing an error message :

So, I check the user/plugins/problems folder's permissions.
Here's the owner (me) :
dir /Q plugins\problems
 Répertoire de D:\Travail\Programmation\Web\Projets_pro\Resonnances\www\user\plugins\problems
12/07/2019  14:32    <REP>          DEV\Romarain           .
12/07/2019  14:32    <REP>          DEV\Romarain           ..
               0 fichier(s)                0 octets
               2 Rép(s)  67 727 667 200 octets libres

Here's my account permissions :
Belong to local groups          *Administrateurs
                                *HomeUsers
Belong to global groups         *None

Here's the problems folder's permissions :
icacls plugins\problems
                             BUILTIN\Administrateurs:(I)(F)
                             BUILTIN\Administrateurs:(I)(OI)(CI)(IO)(F)
                             AUTORITE NT\Système:(I)(F)
                             AUTORITE NT\Système:(I)(OI)(CI)(IO)(F)
                             AUTORITE NT\Utilisateurs authentifiés:(I)(M)
                             AUTORITE NT\Utilisateurs authentifiés:(I)(OI)(CI)(IO)(M)
                             BUILTIN\Utilisateurs:(I)(RX)
                             BUILTIN\Utilisateurs:(I)(OI)(CI)(IO)(GR,GE)

(F) means "total control".
(M) means "modification" (R+W+X).
(RX) means "read and write" (R+W).
So as you can see, the SYSTEM (Système) and ADMINISTRATORS (Administrateurs) are in (F).

It does look like some wonky permissions.  Not sure how it got to that point.  But it might just be simpler to reinstall and copy your user folder back over.

If I really can't solve the problem, I'm going to do that.
But before, I'm trying to investigate on a possible issue with PHP and the folder deletion process under the management of the GPM and/or plugin installation internals.
Here what I found on the rmdir page of PHP : https://www.php.net/manual/en/function.rmdir.php
In case you're trying to rmdir() and you keep getting 'Permission denied' errors, make sure you don't have the directory still open after using opendir(). Especially when writing recursive functions for deleting directories, make sure you have closedir() BEFORE rmdir().

Also :
Say, you're working on Windows and continue to get a permission's error without a reason. Then it may be that a different Windows program is working on the folder (see earlier notes also). In the case that you can't find that program, the line

<?php closedir(opendir($dirname)); ?>

may solve the problem!
Make sure to write this before rmdir($dirname);.

I'm going to watch the error plugin files (it's one of the plugin that fails installing on my machine) to find some opendir() uses that wouldn't have been closed correctly.

I found nothing in the PHP files. So I decided to use the technic of the manual deletion.
Workaround for fixing the RuntimeException

Try to manually delete the remaining folder of the plugin that is failing during installation or update or reinstallation (go in the plugins/ folder, and directly delete the desired folder). Note : the folder should be empty if a previous installation failed (the folder had been emptied, but its own deletion failed).
If a permission elevation prevent you to delete, change the security rights in order to give "total control" on the Authentified Users (Windows), or create an entry for your specific user (add an entity).
Retry the plugin installation. It should succeed.

Thanks for the message anyway, @rhukster ! ;)
This topic can be closed (if an explanation comes later about those random permission problems, I will surely edit my message to share it).


Source map gets broken after entry name change and rebuild

Bug report

What is the current behavior?
There is no problem when the project is built initially. Then if the entry name changes and the project gets rebuilt again — the source map gets broken, it doesn't work properly in chrome dev tools and sources property doesn't contain actual sources, but instead the bundle filename from the previous build.
If you delete node_modules folder, reinstall dependencies and build project again — generated source map starts to work properly.
If the current behavior is a bug, please provide the steps to reproduce.

clone the test repo, run npm i and npm run build inside it;
open ./dist/index.html in the browser — source map is working correctly;
open webpack.config.js, change entry name, run npm run build again;
open ./dist/index.html in the browser — source map doesn't work. Check the source map itself — the sources property contains wrong info;
delete node_modules, reinstall dependencies, build project again — source map starts to work correctly.

What is the expected behavior?
The source map should work correctly after entry name change and rebuild. The sources property should contain proper information.

Other relevant information:
webpack version:  4.41.0
Node.js version: 11.6.0
Operating System: OS X 10.11.6 (15G22010)
Additional tools:

This is a bug in the cache of terser-webpack-plugin.
Deleting node_modules/.cache/terser-webpack-plugin restores the good behavior.
@evilebottnawi

Investigate

@webpack-bot move to webpack-contrib/terser-webpack-plugin


Loading nn.Module from checkpoint doc fix

📚 Documentation
https://lightning.ai/docs/pytorch/stable/common/checkpointing_basic.html#nn-module-from-checkpoint shows the ability to directly retrieve nn.Module weights from a checkpoint if the module is given as an argument in the  LightningModule constructor. For example, it shows the following code for encoder and decoder as arguments:
checkpoint = torch.load(CKPT_PATH)
encoder_weights = checkpoint["encoder"]
decoder_weights = checkpoint["decoder"]

However, when I try to reproduce this I get the following error:
Traceback (most recent call last):
  File "C:\Users\monte\code\scratch\lightning_example.py", line 63, in <module>
    encoder_weights = checkpoint["encoder"]
KeyError: 'encoder'

It runs correctly if I add self.save_hyperparameters() to the constructor and update the checkpoint loading to be:
checkpoint = torch.load(CKPT_PATH)
encoder_weights = checkpoint["hyper_parameters"]["encoder"]
decoder_weights = checkpoint["hyper_parameters"]["decoder"]

Should the documentation be updated?
Also, if there is documentation giving advice on the simplest way to take a pure Pytorch model, train it using Lightning, and get weights back for use in pure Pytorch I'd be interested in it. Thanks!
cc @borda

@montehoover I linked a pull request that fixes this example. The code should be:
encoder_weights = {k: v for k, v in checkpoint["state_dict"] if k.startswith("encoder.")}
decoder_weights = {k: v for k, v in checkpoint["state_dict"] if k.startswith("decoder.")}

if we want to achieve what is described in the text.

Thanks!


Development

Hello. Did you open the PR by mistake? I've seen a list of commits in e-mails and just managed to actually open github

Yes, I was in a hurry and GitHub keeps defaulting to this master branch instead of the master branch of my own fork, so I accidentally opened the pull request to the wrong branch.
I don't plan on merging my fork into this repository, so you can safely ignore it.
Apologies for the confusion :)


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3727

Questions ?
Please refer to the Backport tool documentation


a better dogehouse logo

1

https://benawad.gay/ for new favico?

+1

Yes, I agree.

+1

+1

Urgent issue regarding UI design. Current logo is gay

http://benawad.gay

@ax20 nice design

Thanks it was curated by my frontend team, They thought it would be the best class of action for the company. Would you be intrested in a collabration?

hey refresh

@benawad they forced me

New twitter  banner?

https://www.change.org/p/ben-awad-petition-to-change-dogehouse-tv-logo-to-fck-sh?recruiter=1200944809&utm_source=share_petition&utm_medium=copylink&utm_campaign=share_petition

no body can surpass this

no body can beat this masterpiece

Why angular is the best framework
https://www.digitaldoughnut.com/articles/2018/december/why-angular-is-the-best-framework

@KristofKekesi  i angree

LOL you guys

@benawad

you can't even crop

an array of memes😂

Going to close this just so I can get 20 dislikes, which are a lot on GitHub

tygngf


Docker environment to run licensed from command line: "pip.rb:48: syntax error, unexpected '.' (SyntaxError)"

Hi,
I've been asked to evaluate this tool in a POC for an internal application. Licensed; looks nice and interesting. I'm not a ruby developer/user, more someone from the CI/CD team, and our app is not written in ruby but uses npm as package manager. I plan to integrate a licensed check step into our Jenkins pipeline and instead of installing licensed in our CI nodes, I choose to build a docker image so I can mount our code and run licensed into a docker container.
I first start with creating a Docker image from the official ruby image (as licensed was written in ruby); here is my Dockerfile:
FROM ruby:2.3.7-jessie
RUN echo deb http://ftp.debian.org/debian jessie-backports main >> /etc/apt/sources.list
RUN apt-get update && \
    apt-get install -y cmake pkg-config npm nodejs
RUN gem install licensed
RUN useradd --no-log-init --create-home -r -u 1000 -g users test
RUN mkdir /app && \
    chown test:users /app
USER test
WORKDIR /app

Build the image:
docker build --rm -t licensed:ruby-2.3.7  .
Here is my licensed app config: .licensed.yaml
name: 'placement-back'
cache_path: '/app/test1/.licenses'
source_path: '/app/test1'
sources:
  npm: true
allowed:
  - mit

... and my package.json:
{
  "name": "placement-back",
  "version": "0.0.0",
  "dependencies": {
    "async": "^2.6.0",
    "atomic": "0.0.2"
  }
}

Then I can mount the app and run licensed; here is a simple example:
docker run -it --rm --network="host" -v /home/chris/workspace/app:/app licensed:ruby-2.3.7 bash
$ cd /app/test1
$ npm update
<EMAIL_ADDRESS>node_modules/atomic
<EMAIL_ADDRESS>node_modules/async
└──<EMAIL_ADDRESS>$ licensed cache
Caching licenses for placement-back:
  npm dependencies:
    Caching async (2.6.1)
    Caching lodash (4.17.10)
    Caching atomic (0.0.2)
License caching complete!
* placement-back npm dependencies: 3
$ licensed status
Checking licenses for placement-back: 3 dependencies
...
3 dependencies checked, 0 warnings found.

$ uname -a
Linux localhost.localdomain 4.15.14-1.el7.elrepo.x86_64 #1 SMP Wed Mar 28 14:16:59 EDT 2018 x86_64 GNU/Linux
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian

This worked fine with this simple test1 example. Great!
My problems comes when I tried to use the real package.json from my app, having something 40+ main dependencies (approx 500 dependencies in total after running npm). When I run npm update with this json file; npm returns errors. I asked the developers for help and they told me that the npm engine that I used was too old; they requires a npm 8.9.3 version. This first docker image have a npm 1.4.21 version.
Instead of creating the docker image from ruby; I thought that it should be easier to start with a nodejs image to avoid having the npm issue.
Here is my second Docker image from node:
FROM node:8.11.1
RUN echo deb http://ftp.debian.org/debian jessie-backports main >> /etc/apt/sources.list
RUN apt-get update && \
    apt-get install -y cmake pkg-config ruby ruby-dev python-pip
RUN gem install licensed
RUN mkdir /app && \
    chown node:users /app
USER node
WORKDIR /app

Build the image:
docker build -f Dockerfile.node --rm -t licensed:node-8.11 .
Then I run the same test with this new image:
docker run -it --rm --network="host" -v /home/chris/workspace/licensed:/app licensed:node-8.11 bash
$ cd /app/test1
$ npm update
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.

+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>added 3 packages in 4.474s
$ licensed cache
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': /var/lib/gems/2.1.0/gems/licensed-1.1.0/lib/licensed/source/pip.rb:48: syntax error, unexpected '.' (SyntaxError)
          a[k.strip] = v&.strip
                          ^
	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.1.0/gems/licensed-1.1.0/lib/licensed.rb:14:in `<top (required)>'
	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.1.0/gems/licensed-1.1.0/lib/licensed/cli.rb:2:in `<top (required)>'
	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.1.0/gems/licensed-1.1.0/exe/licensed:4:in `<top (required)>'
	from /usr/local/bin/licensed:23:in `load'
	from /usr/local/bin/licensed:23:in `<main>'

Licensed failed (even a licensed help command fails).
Here are some additional information regarding config & installed gems:
$ uname -a
Linux localhost.localdomain 4.15.14-1.el7.elrepo.x86_64 #1 SMP Wed Mar 28 14:16:59 EDT 2018 x86_64 GNU/Linux
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
$ gem list --local

*** LOCAL GEMS ***

addressable (2.5.2)
bigdecimal (1.2.4)
faraday (0.15.2)
io-console (0.4.2)
json (1.8.1)
licensed (1.1.0)
licensee (9.6.0)
minitest (4.7.5)
multipart-post (2.0.0)
octokit (4.9.0)
pathname-common_prefix (0.0.1)
psych (2.0.5)
public_suffix (3.0.2)
rake (10.1.0)
rdoc (4.1.0)
rugged (0.27.1)
sawyer (0.8.1)
test-unit (<IP_ADDRESS>)
thor (0.20.0)
tomlrb (1.2.7)

I don't know what exactly is missing in this docker image to run licensed. I've tried install python-pip and pip gem; and start building licensed from source but it does not fix this and it was not part of the 1st ruby image... still the same error.
Help/idea appreciated ^^
Regards,
Chris

@cnaslain 👋  sorry for the difficulties.
The issue with your second docker image is that the version of ruby is a bit old and doesn't support the & operator, causing the syntax error.
There are two ways to fix this.
If you want to use a ruby base docker image, you can install different versions of nodejs in your docker image by following https://github.com/nodesource/distributions#installation-instructions.  It looks like you'd want the 8.x installer.
If you want to use a node base docker image, you can install more recent versions of ruby installing and using ruby-install.  You'll need Ruby >= 2.3.0 I think.
Let me know if you have any other questions 🙇

Should licensed.gemspec include https://guides.rubygems.org/specification-reference/#required_ruby_version so that gem install licensed would fail and say why?

@jonabc I've tried the official ruby image + custom setup for nodejs; works like a charm. Thanks!
PS: I also tried the nodejs + manually install ruby; it works too but the docker image is much bigger and more complicated to build; so starting by ruby is the best choice.
For those who are interested in using docker:
FROM ruby:2.4.4-jessie
RUN echo deb http://ftp.debian.org/debian jessie-backports main >> /etc/apt/sources.list
RUN apt-get update &&
apt-get install -y cmake pkg-config
RUN gem install licensed
RUN curl -sL https://deb.nodesource.com/setup_10.x | bash - &&
apt-get install -y nodejs
RUN useradd --no-log-init --create-home -r -u 1000 -g users test
RUN mkdir /app &&
chown test:users /app
USER test
WORKDIR /app

@cnaslain if you're still evaluating licensed, this scenario should be a bit simpler.  licensed executables for darwin/mac and linux are shipped as of the 1.2.0 release.
You should be able to curl the executable directly into a docker container set up for your project - no need to use a base ruby docker image or install ruby just to use licensed.


recognize_google should have pfilter = 0 by default but it's censoring words as if it's running pfilter = 1

Steps to reproduce
def speech_to_text(self):
        recognizer = sr.Recognizer()
        with sr.Microphone() as mic:
            print("listening...")
            recognizer.adjust_for_ambient_noise(mic,duration=2)
            audio = recognizer.listen(mic)
        try:
            self.text = recognizer.recognize_google(audio, language = "en-US")
            print(text)

"what the shit"
"what the s***" -> This is what is recorded, and in theory the correct result of pfitler = 1, But even in the source code it looks like it's running pfilter = 0.
Expected behaviour
I would expect this to return without the censorship and if i provide pfitler = 1 then I should get the above result. Or if you are really lazy until a real fix comes out, a quick update to say the default is returning the results of pfitler = 1
System information
(Delete all the statements that don't apply.)
My system is macOS Monterey
My Python version is 3.9.12
My Pip version is 22.0.4
My SpeechRecognition library version is 3.7.1
My PyAudio library version is 0.2.11

I have this problem. Can somebody help?

        if key is None: key = "AIzaSyBOti4mM-6x9WDnZIjIeyEU21OpBXqWBgw"
        url = "http://www.google.com/speech-api/v2/recognize?{}".format(urlencode({
            "client": "chromium",
            "lang": language,
            "key": key,
            "pFilter": pfilter
        }))

Looks like this is handled on the server side.  This should be reported to Google.

I have just reported to Google that this repository, in my opinion, is exposing this fraudulent API key


我使用一键部署提示“Disabling patch for /home/user/.wine/drive_c/users/user/AppData/Roaming/Tencent/WeChat ...”

我使用一键部署提示“Disabling patch for /home/user/.wine/drive_c/users/user/AppData/Roaming/Tencent/WeChat ...”
我的操作系统为fedora39
gx@fedora:/$ curl -sL https://gitee.com/mirrors/dochat/raw/main/dochat.sh | bash

       ____         ____ _           _
      |  _ \  ___  / ___| |__   __ _| |_
      | | | |/ _ \| |   | '_ \ / _` | __|
      | |_| | (_) | |___| | | | (_| | |_
      |____/ \___/ \____|_| |_|\__,_|\__|

      https://github.com/huan/docker-wechat

                +--------------+
               /|             /|
              / |            / |
             *--+-----------*  |
             |  |           |  |
             |  |   盒装    |  |
             |  |   微信    |  |
             |  +-----------+--+
             | /            | /
             |/             |/
             *--------------*

      DoChat /dɑɑˈtʃæt/ (Docker-weChat) is:

      📦 a Docker image
      🤐 for running PC Windows WeChat
      💻 on your Linux desktop
      💖 by one-line of command

🚀 Pulling the docker image...

<IP_ADDRESS>: Pulling from zixia/wechat
Digest: sha256:69411b334353b0993e3a8affc59eab888338275b086444f61e396046cf767cf5
Status: Image is up to date for zixia/wechat:<IP_ADDRESS>
docker.io/zixia/wechat:<IP_ADDRESS>

🚀 Pulling the docker image done.
🚀 Starting DoChat /dɑɑˈtʃæt/ ...

[DoChat] 盒装微信 v0.15.1
Disabling patch for /home/user/.wine/drive_c/users/user/AppData/Roaming/Tencent/WeChat ...
Disabling patch for /home/user/.wine/drive_c/users/user/Application Data/Tencent/WeChat ...
[DoChat] WeChat <IP_ADDRESS>
[DoChat] Starting...
[DoChat] WeChat.exe exit with code 0
[DoChat] Found new version?
[DoChat] WeChat.exe exited

📦 DoChat Exited with code [0]

🐞 Bug Report: https://github.com/huan/docker-wechat/issues

我在Fedora 38 上遇到了和你一样的问题。你可以设置DOCHAT_DEBUG环境变量来查看具体的报错信息，我这里的报错信息是:
I encountered the same issue on Fedora 38. You can set the DOCHAT_DEBUG environment variable to view the specific error messages. The error message I received here is:

看起来像是与窗口显示有关的问题，我从wayland切换到x11就可以正常使用。或者参考 #214 ，执行：
It seems to be a window display-related issue. I switched from Wayland to X11, and it resolved the issue for me. Alternatively, you can refer to issue #214 and execute: [执行的命令].
xhost +


Update recurly config

After updating our app to Ember v3.6, the getter and setter for recurly.config.fields was no longer working as expected. This PR simplifies the recurly config access. Now, to change the style for recurly fields for example, just get the config object and modify it:
const config = this.get('recurly.config');
config.fields.all.style = { color: 'red' };

Whoops


RON should be available for all positions

Seems like EUSA requires that RON be an option for all votes, including those for President, Secretary and Treasurer.
https://www.eusa.ed.ac.uk/pageassets/activities/societies/runasociety/Elections-and-AGMs(2).pdf

Unless there's a contradiction elsewhere, https://github.com/compsoc-edinburgh/constitution/blob/master/compsoc-constitution.tex#L310 means that RON would always e called including for the executive positions

https://github.com/compsoc-edinburgh/constitution/blob/master/compsoc-constitution.tex#L313-L315 says that RON will not be available for the positions of President, Secretary and Treasurer.

Whups, maybe I should have read a bit further... Yep, RON should be available for all roles


When editing displayId, make sure object does not exist

When you edit the displayId and try to save the object, should first check if object exists.  If it does, should give the user the option to "Overwrite" or "New Version".
Note this could work for all edits of a part.  Namely, first edit could save with no prompt, since will not exist, but subsequent ones could give the option to overwrite or new version.

Done.  I also added a settings tab in preferences that controls the default behavior (ask the user, overwrite, or new version).


Some features

Hi @rubensousa ,
It would be possible to add the following features:

In addItem, besides the title, it would be possible to add another parameter, this parameter, but it should be possible that it can be changed.
Example considering Youtube app:
Icon "Playback speed •"  Normal / 0.75x / 1.25 ....

The possibility to change color to:
a) ripple effect
b) Color of the item when it is selected

The ability to reduce the size of the container, not to take up all the space of the device.
Example, here it is performed on a tablet, but the same for a mobile device:
https://raw.githubusercontent.com/rubensousa/BottomSheetBuilder/master/screens/tablet_grid.png

Connected to 3), the possibility of having rounded corners at the top of the container.

@rubensousa : are there any news?


Render only approved experiences in the View Experiences page

Summary
The goal of this issue is to render only the experiences approved by the moderators on the view experiences page.
This issue is part of  issue #157
What needs to be done?

[ ]  Implement review status property for approved experiences
[ ]  Add (uncomment) the filter for approved experiences in the list_public_experiences view

Who can help?
The dev team.

@jhlink Is there anything else to be added?

Nope, this is great!! Thanks @anoura12 !


Feature/details

Summary
(select one:)

Breaking change
Addition
Patch for #
New provider

[ +] Tested

[ +] Unit tests
[ +] Style

[ +] Documentation (PR # )

Goal
Details functional in nominatim
Description
Add details by placeid
Add details by osmtype and osmid

Thanks @ReBlack for your contribution 🍻

Please see #12

I'm also thinking about removing the generated phpdoc, I'm not sure this is useful and the annotation should be sufficient

I agree


Add WEBP support in GDAL

See https://github.com/mapbox/rasterio/issues/1285.

Somewhat complicated. WEBP requires libtiff (see https://developers.google.com/speed/webp/docs/compiling#compiling_on_unix-like_platforms) and we're currently using the libtiff that ships with GDAL.


How should I disable caching for testing?

Hi,
I've a base class that inherits from requests_cache.CacheMixin and requests.Session and sets a default cache lifetime expire_after=NEVER_EXPIRE.
Then I have another class that inherits from this base client. One method sets expire_after=598 explicitly for a request.
For testing I want to disable caching, but passing expire_after=NEVER_EXPIRE to my test client instance does not work, because the per-request option has precedence.
So how am I supposed to:

Set a default cache lifetime for my class that is used 99% of the time.
Use a different cache lifetime for some requests.
Then disable caching for my tests.

The easiest way to disable caching is by mocking the CacheMixin class and replacing it with a regular requests.Session (or if you want, another custom subclass of Session to use for testing). There's an example of doing that here: https://requests-cache.readthedocs.io/en/stable/user_guide/compatibility.html#disabling-requests-cache
Let me know if that accomplishes what you want.

Hi. This does work for me:
@pytest.fixture(scope='function')
def requests_cache_mock(requests_mock):
    with requests_cache.disabled():
        yield requests_mock

But now I have the problem that my logger tries to access response.from_cache and response.expires which don't exist in this case. The cleanest solution would be if I could just pass a expire_after=DO_NOT_CACHE, but I guess that's not possible.
Anyway, thanks for your help! :)

Nope, I was wrong. This does not work. It still writes to cache.
The other solution from the documentation doesn't work either.
My class is inheriting from CacheMixin. So I tried the following without success:
@pytest.fixture(scope='function', autouse=True)
def disable_requests_cache():
    with mock.patch('requests_cache.CacheMixin'):
        yield

Could I just clear the cache before each test? I guess that would work for my current situation.

Seems like replacing the SQLite backend with memory did work for me...

Sure, using the memory backend is a valid option too.
If patching the session class or mixin didn't work, post your custom session class definition and I can help debug.


too many values to unpack (expected 2)

Te = 1
G = tf(1,[1,1,0])
Gz = c2d(G, Te, 'zoh')
C1z = tf([1],[1,-1],Te)
C2z = (1/b1)tf([1,-a],[1,-b0/b1],Te)
C3z = tf([0.2488,-0.2134],[1],Te)
Cz = C1zC2z*C3z
sys1 = CzGz/(1+CzGz)
dts = 1
u1ds = np.zeros(tempsSimulation.shape);
u1ds[0] = 1/dts
ctrl.forced_response(sys1, tempsSimulation, u1ds, 0)
Hello, there is my code, and i'm getting the error : too many values to unpack (expected 2)
Can you help me please, also, i have to print with matplotlib the curves from a parabol input, that's why i am using forced_response, can you help me with it too please ?
Thanks a lot !

Hello. The code is incomplete and not oconsistent with your error message.

a, b0, b1, tempsSimulation are not defined. (Also ctrl, np, tf, c2d)
Please use markdown code tags so that the * does not get swallowed
You most likeley want to do something with the response. Assign the return values of forced_response to T, yout, xout. These are 3 values in a tuple. "expected 2" indicates, that you actually want to assign to only 2 variables.  But that does not fit your posted code.

`
import control as ctrl
import numpy as np
from control.matlab import *
import matplotlib.pyplot as plt
Te = 1
tau = 1
a = np.exp(-Te/tau)
b1 = Te - tau * (1 - a)
b0 = a*Te - tau * (1-a)
G = tf(1,[1,1,0])
Gz = c2d(G, Te, 'zoh')
C1z = tf([1],[1,-1],Te)
C2z = (1/b1)*tf([1,-a],[1,-b0/b1],Te)
C3z = tf([0.2488,-0.2134],[1],Te)
Cz = C1zC2zC3z
TempsDeReponseEstime = 30
tempsSimulation = np.arange(0,TempsDeReponseEstime,Te)
sys1 = CzGz/(1+CzGz)
dts = 1
u1ds = np.zeros(tempsSimulation.shape);
u1ds[0] = 1/dts
ctrl.forced_response(sys1, tempsSimulation, u1ds, 0)
`
There it is, hoping everything you need to help me is there :)

I see no unpack error with this code. The last line returns a tuple for the following plot:
T, yout, xout = _

plt.subplot(2,1,1)
plt.plot(T, yout)
plt.subplot(2,1,2)
plt.plot(T, xout.T)

Could you please post your backtrace?

Hello, it seems to work when adding xout, i'm verry sorry about it, thanks a lot for your help !


[WIP] Change tab defaults

The state of a user's filtering is currently shared between all three tabs of the Audit Tool, which is done by persisting the query string when changing tabs.
However, we now want to change the filters in each view, tailoring them to the task that is to be performed on that tab. As such, we want different default values when loading each tab, and we should stop sharing the filter state when switching tabs.
In order to do this, this change removes all notion of defaults and blank values from the filter class, and moves the defaults up into the controllers.
The sidebar filter values are also driven by the filter object, rather than the query parameters, which are not indicative of the current state of the filter (since they may be blank, but a default filter will apply).

 Create a default filter for 'Audit content' and 'assign content' tabs

 List view should reflect the default option of "Me" being pre-selected in "Allocated to" filter.

 List view should reflect the default option of "Me" being pre-selected in "Allocated to" filter.

Superceded by https://github.com/alphagov/content-performance-manager/pull/345

Superseded by https://github.com/alphagov/content-performance-manager/pull/345


Freeze when processing large quantity of "skipping unchanged chapter"

Actually making edits is fine, but if it's skipping a bunch of chapters that don't need changes it'll freeze up entirely while it checks.

Pretty sure this is just kivy being laggy when there is a lot of shit in the text box to render. One possible solution is to limit the maximum number of lines in the log to 50 or so, tho that means you won't by able scroll all the way up to see old errors.

fixed in 2.5.2 probably


Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:1024/eiemy-q0vh0=/

Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:1024/eiemy-q0vh0=/
After upgrade to lastes Flutter version.
Flutter always show this error after install and launching.
it currently not working and i can not continue to develop at present.
Steps to Reproduce
After upgrade to lastes Flutter version.
Flutter always show this error after install and launching.
it currently not working and i can not continue to develop at present.
Running Xcode build...

 ├─Assembling Flutter resources...                          14.1s
 └─Compiling, linking and signing...                        10.2s
Xcode build done.                                           39.2s
Installing and launching...                                        29.2s
Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:1025/jFpDvAxfurw=/

Target Platform:
Target OS version/browser:
Devices:

[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.2 19C57, locale zh-Hans)
    • Flutter version 1.12.13+hotfix.5 at /Users/virs/flutter
    • Framework revision 27321ebbad (6 天前), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/virs/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.1, Build version 11A1027
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 41.0.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[!] IntelliJ IDEA Ultimate Edition (version 2019.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[✓] VS Code (version 1.41.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.7.1

[✓] Connected device (1 available)
    • “wei zhang”的 iPhone • 029252aa59e25c34188ac565344af93858a917b1 • ios • iOS 13.1.3

! Doctor found issues in 1 category.

tried restart system, and reinstall Flutter

i am not using proxy or vpn

repeat it after switch to master channel enable macOS development.

Hi @virskor
are you experiencing this issue with stable or master channel (or both)?
Are you located in China?

@iapicca yes, i am in China. i found this problem still existing, and i just reopen this issue. these problem exits on both stable/master channel. Thanks

i just upgrade to 1.12.13(hotfix5) but this problem still trouble me.

Having the same problem.
Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:50365/UGuZ7dchAl0=/
[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.18363.535], locale bs-Latn-BA)
    • Flutter version 1.12.13+hotfix.5 at C:\Programs\Flutter
    • Framework revision 27321ebbad (6 days ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\Anis\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 40.1.2
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] IntelliJ IDEA Community Edition (version 2018.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2018.2.2
    • Flutter plugin version 28.0.4
    • Dart plugin version 182.4323.44

[√] IntelliJ IDEA Community Edition (version 2019.3)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2018.3
    • Flutter plugin version 42.1.4
    • Dart plugin version 193.5731

[√] VS Code, 64-bit edition (version 1.38.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.6.0

[√] Connected device (1 available)
    • ANE LX1 • 9WV4C19131006232 • android-arm64 • Android 9 (API 28)

• No issues found!

same. stable, Russia

Same, stable, Canada.

I forgot to connect the ios application in firebase and add google json in runner)

It works fine when you are using flutter run --release. But using flutter run will lose connection when process to installing and launching step. And this problem seems not frequently happens on wired connection. Try to open connection via network on xcode,This problem comes to trouble. But connections works well on Xcode. And flutter run --release also work well via network connection

Same, Hong Kong and Oslo.

Finally what can i do. Because i have same problem

same here on stable latest.

For those experiencing this issue, please post full logs from flutter run --verbose in a gist. Thanks!

I just ran into this tonight after working with Flutter for a week. Was working on a new app and trying to run on my USB-connected iOS device, but this issue began — trying to rerun older apps (ones I'd been able to run yesterday) also failed with the same error.

I'm on a mac, OS version 10.15.1
Restarting my computer doesn't seem to have an effect.
I've attempted to run the same app on the iOS Simulator, an Android Emulator, and a USB-connected iOS device. So far, the USB-connected iOS device is the only one affected by this issue.
I haven't tried uninstalling/reinstalling Flutter yet, or switching to a different version.

I've pasted my flutter doctor and flutter run output here: https://gist.github.com/averyvery/173ac2df50449cb2356ed91165da7140
The final lines are:
[+1008 ms] Forwarded port ForwardedPort HOST:1026 to DEVICE:50123
[   +5 ms] Installing and launching... (completed in 25.2s)
[   +7 ms] Connecting to service protocol: http://<IP_ADDRESS>:1026/LWSLWJ2x_Ds=/
[ +126 ms] Fail to connect to service protocol: http://<IP_ADDRESS>:1026/LWSLWJ2x_Ds=/: HttpException: , uri = http://<IP_ADDRESS>:1026/LWSLWJ2x_Ds=/ws
[   +1 ms] Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:1026/LWSLWJ2x_Ds=/
[   +2 ms] "flutter run" took 53,306ms.

After some googling, I was able to resolve by going into Xcode:

Go to Window > Devices and Simulators
Uncheck "Connect via network"

Apologies if this is unrelated, or is a known issue. I got the solution from https://github.com/flutter/flutter/issues/13747#issuecomment-369322275

I'm having the same issue @zanderso please refer to my error here
https://gist.github.com/beingentangled/2ac66cceb429e408763c6e8b3be77631

I've got the same issue. And the weirdest thing is that downgrading is not helping at all.

Here is the log including the error:
`+1006 ms] Forwarded port ForwardedPort HOST:1024 to DEVICE:49395
[   +4 ms] Installing and launching... (completed in 25.8s)
[  +10 ms] Connecting to service protocol: http://<IP_ADDRESS>:1024/VbX8F-ZI1YQ=/
[  +46 ms] Fail to connect to service protocol: http://<IP_ADDRESS>:1024/VbX8F-ZI1YQ=/: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:1024/VbX8F-ZI1YQ=/ws
[        ] Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:1024/VbX8F-ZI1YQ=/
[   +2 ms] "flutter run" took 66,348ms.
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:509:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:615:18)

#3      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:515:33)

#4      AppContext.run. (package:flutter_tools/src/base/context.dart:146:29)
#5      _rootRun (dart:async/zone.dart:1126:13)
#6      _CustomZone.run (dart:async/zone.dart:1023:19)
#7      _runZoned (dart:async/zone.dart:1518:10)
#8      runZoned (dart:async/zone.dart:1465:12)
#9      AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#10     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:505:20)
#11     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#12     FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:413:21)

#13     AppContext.run. (package:flutter_tools/src/base/context.dart:146:29)
#14     _rootRun (dart:async/zone.dart:1126:13)
#15     _CustomZone.run (dart:async/zone.dart:1023:19)
#16     _runZoned (dart:async/zone.dart:1518:10)
#17     runZoned (dart:async/zone.dart:1465:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#19     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:364:19)
#20     CommandRunner.run. (package:args/command_runner.dart:112:25)
#21     new Future.sync (dart:async/future.dart:224:31)
#22     CommandRunner.run (package:args/command_runner.dart:112:14)
#23     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:250:18)
#24     run.. (package:flutter_tools/runner.dart:63:22)
#25     _rootRun (dart:async/zone.dart:1126:13)
#26     _CustomZone.run (dart:async/zone.dart:1023:19)
#27     _runZoned (dart:async/zone.dart:1518:10)
#28     runZoned (dart:async/zone.dart:1502:12)
#29     run. (package:flutter_tools/runner.dart:61:18)

#30     AppContext.run. (package:flutter_tools/src/base/context.dart:146:29)
#31     _rootRun (dart:async/zone.dart:1126:13)
#32     _CustomZone.run (dart:async/zone.dart:1023:19)
#33     _runZoned (dart:async/zone.dart:1518:10)
#34     runZoned (dart:async/zone.dart:1465:12)
#35     AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#36     runInContext (package:flutter_tools/src/context_runner.dart:64:24)
#37     run (package:flutter_tools/runner.dart:50:10)
#38     main (package:flutter_tools/executable.dart:65:9)
#39     main (file:///Users/user/Library/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#40     _startIsolate. (dart:isolate-patch/isolate_patch.dart:305:32)
#41     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)
`

I got this too

my error was disappeared after some edits. still not sure what was the fix.
you can try to edit android/build.gradle especially dowgrading your gradle version.
also i have removed preferences package from pubspec it is using old version of shared_preferences.
my versions.
classpath 'com.android.tools.build:gradle:3.3.2'
 classpath 'com.google.gms:google-services:4.3.3'

I am having this issue, followed these proposed solutions but didn't fix the issue:

Downgrading from SDK 29 to 28
Flutter clean
Use a physical device.

The weirdest thing is that if I use an IOS emulator, it works fine, the issue only affects an android device (virtual or physical)
Here is the android gist (Have the error):

https://gist.github.com/ortizen/c8d17f85034252ecd3728393cd746665

And the IOS run (Runs OK)

https://gist.github.com/ortizen/d08ec9ab64c0f4feeddb1e731a1cbc29

I am suing macOs Catalina 10.15.2 and Android Studio 3.5.3

How many with this problem using this package?
dependencies:
flutter_clean_architecture: ^2.0.1

Same issue here under iOS ? (iOS10.15.2) Any solution yet ?

Same issue here under iOS ? (iOS10.15.2, Xcode11.3, Flutterv1.12.13+hotfix.5) Any solution yet ?

is it working in Android for you?

I've got a solution to my problem.
Please check the following:
If the app has any permissions, make sure to give it in both Android Manifest and Info.plist.
In my case, I was requesting a location at the start of the application whose permission was not defined for IOS in Info.plist which when requested at the starting will result in a crash and will not allow to connect the observatory throwing the error:
Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:1024
Please make sure to give the necessary permissions in both IOS and Android.
Thanks.

resolved by disabling personal hotspot on device

I copied all my plugins to a new project and narrowed it down to flutter_facebook_plugin giving the error, once removed it started to run on device again. Hope this helps!

I copied all my plugins to a new project and narrowed it down to flutter_facebook_plugin giving the error, once removed it started to run on device again. Hope this helps!
Yeap, I tried @DerSIlent  solution to nuke facebook plug in and solve the problem.

I had the same issue (iOS on iPad).For me it seems that it had to do with DNS settings (I had <IP_ADDRESS> set up as my DNS, overriding my router's default DHCP settings).
After setting DNS in system settings it to "Automatic" apparently solved the problem for me.

Also had the same issue, solved it by removing the package barcode_scan

I also had the same issue, and solved it by using FlutterActivity instead of FlutterFragmentActivity.

I finally found that flutter upgrade and a flutter clean did help.

For me it was wrongly configured facebook login. Precisely missing string.xml and AndroidManifest.xml data:
/android/app/src/main/res/values/strings.xml
`

Your App Name here.
<!-- Replace "000000000000" with your Facebook App ID here. -->
<string name="facebook_app_id">000000000000</string>

<!--
  Replace "000000000000" with your Facebook App ID here.
  **NOTE**: The scheme needs to start with `fb` and then your ID.
-->
<string name="fb_login_protocol_scheme">fb000000000000</string>

`
/android/app/src/main/AndroidManifest.xml
`

`

I was having this issue. I uninstalled the app from my device, opened the project in xcode, ran some build cleaning thing that appeared in the yellow triangle warning area, then built the app via xcode. Then uninstalled the app from device again. Then ran via android studio and it worked.

Incredible, @mdrideout, your workaround helped indeed ! The cleaning in Xcode and uninstall/install trick did help. Thank you very much.

Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:65426/FiX7i0GaT6Y=/
Same issue
channel stable and location india

Same here, worked once after that service protocol error, Cambodia, Stable

I copied all my plugins to a new project and narrowed it down to flutter_facebook_plugin giving the error, once removed it started to run on device again. Hope this helps!

this one worked. Crazy.

Same problem here, using adb connected over WiFi.

 It started working again when I clicked the power button on the side of emulator.

/cc @blasten to try to reproduce this.

I was able to reproduce this issue by using an emulator running Android 10.

[        ] Forwarded host port 61900 to device port 38717 for Observatory
[  +18 ms] Connecting to service protocol: http://<IP_ADDRESS>:61900/Zjn5H-sLOgo=/
[  +98 ms] Fail to connect to service protocol: http://<IP_ADDRESS>:61900/Zjn5H-sLOgo=/: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:61900/Zjn5H-sLOgo=/ws
[        ] Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:61900/Zjn5H-sLOgo=/
[   +5 ms] "flutter run" took 4,699ms.

Duplicate of https://github.com/flutter/flutter/issues/33050

I was able to fix the issue by updating system image to revision 8. This can be done by going to Preferences -> System Settings -> Android SDK -> SDK Platforms.

If you hitting this issue, it's likely that you are using an older system image and facing  https://issuetracker.google.com/issues/132325318. Please provide more details otherwise.

I'm closing this issue since the solution is to update the system image. Please reopen and provide more details if you experiment the same issue.

I'm closing this issue since the solution is to update the system image. Please reopen and provide more details if you experiment the same issue.

That wouldn't solve it on iOS though.

@indigothm This scope of this issue has crept a bit. I think we should leave this one closed, and if folks are still seeing this, please open new separate Android and/or iOS issues. Thanks!

I do have the same problem on IOS, not sure if it's related to changes in any of my plugins. However, I can run app perfectly from Xcode, with all the logs being available.

I had the same issue, I remove the flutter_facebook_login from my pubspec and the app works fine.
Regards


Large numbers library

Description of Change

New

library for arbitrarily large integer numbers
use of it to compute large Fibonacci numbers

Checklist

[x] Added description of change
[x] Added file name matches File name guidelines
[x] Added tests and example, test must pass
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] Sort by alphabetical order
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:

The problem in this pull is with the operator overloading function + in large_number.h. Any thoughts and suggestions are appreciated.

note: CPPLINT passes. the error referred to has been fixed in another pull-request #795

@ayaankhan98

Already included in #805


[release-1.3] Get rid of demo-auth

This is an automated cherry-pick of #17043

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio_release-1.3
cc3b77d039c930d0e86a2a618395a82ce1de8638
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

Because this PR can be merged:

Merge a doc PR into istio/istio.io:master to fix all references in the docs to the files you delete here.
Backport that doc PR into istio/istio.io:release-1.3. Make sure that the new docs will work for both 1.3.0 and for the changes in this PR.
Make sure that the release-1.3 branch is pushed live to reflect those changes for the 1.3 release branch.

Because this PR can be merged:
1. Merge a doc PR into `istio/istio.io:master` to fix all references in the docs to the files you delete here.

2. Backport that doc PR into `istio/istio.io:release-1.3`. Make sure that the new docs will work for both 1.3.0 and for the changes in this PR.

3. Make sure that the release-1.3 branch is pushed live to reflect those changes for the 1.3 release branch.

I am working on the document update to reflect this change. Thanks.

I am working on the document update to reflect this change. Thanks.

Thanks! Please comment here again when that is done.

not stale

not stale

I dont think we should backport this. It is not a backwards compatible change to remove.. we can always just not document it in the 1.3 istio.io docs, but removing it is harmful to users using it, since they will not be able to upgrade from 1.3.3 -> 1.3.4, and there is not a clear benefit to doing this


Fix module code prefix

Codecov Report

Merging #281 (b42c7f4) into master (8818ec1) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #281   +/-   ##
=========================================
  Coverage     52.71%   52.71%
  Complexity      749      749
=========================================
  Files           141      141
  Lines          3460     3460
  Branches        484      484
=========================================
  Hits           1824     1824
  Misses         1499     1499
  Partials        137      137

Impacted Files
Coverage Δ

...ain/java/seedu/address/logic/parser/CliSyntax.java
94.11% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


fix(default-theme): hide language switcher when only one language ava…

closes #1206
Changes
Language switcher only visible if more than one language exist

Checklist

[*] I followed contributing guidelines

 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.

@mkucmus thank you for approving this PR. The conflicts are resolved, but can you give me please a hit, what is wrong with the PR tittle? I tried to fix it without success :disappointed:

@mkucmus thank you for approving this PR. The conflicts are resolved, but can you give me please a hit, what is wrong with the PR tittle? I tried to fix it without success

I think you did everything right, but there are some limitations of the gh action for forked PRs :/ It's worth checking it out


[otbn,dv,doc] Handle bad CSRs properly in ISS and docs

The first commit is just a minor clean-up. The interesting commit in the PR has the following message:

This is (sadly) playing catch-up with the RTL, which implemented its
current behaviour a while ago. Document what happens on bad CSRs, then
implement it properly in the ISS. Note that the ISS behaviour has
changed for writes to RND.
The result now matches both the existing spec and RTL.

Hi @imphil! Thanks for the review. These changes alter the ISS to match the spec that was already committed to the repository. May I suggest that we take them, and then follow up with a change to the spec, ISS and RTL to implement the error on writes to RND (opening an issue to track)? Otherwise, we're going to be in an awkward situation where the model and RTL don't agree and I have to update the RIG not to trigger the mismatches.


V0.1.0

Increment version number and begin tracking changes in CHANGELOG.md

Hello @emanuega! Thanks for opening this PR.

In the file merlin/__init__.py:

Line 96:1: W391 blank line at end of file


Batch adding of tags

I thought about it, should be simple.

batch editing mode toggled with a button

=> opens thumbnails view
=> opens the manual tag tray
=> tray shows message "select as many videos as you'd like and click on a tag to add the tag to all of them"

clicking on any video adds a large checkmark ✅ to indicate "selected"

=> adds selected: true to ImageElement

clicking on any tag in the video tray adds the tag to all those videos

🤷 some users have been insisting that batch adding of tags is important to them. Seems like an easy-enough implementation as described above 🤞
I'll implement it unless someone wants dibs 🤝

Oh that would actually be very helpful. I'm going to use VHA for organising films for a film festival. Making it possible to quickly tag multiple video's this way would make tags a lot more useful!

I'll try to finish the feature today -- it's functionally 90% there, just need to make the UI (user interface) intuitive / self-explanatory 😊
Thank you for words of encouragement (knowing a feature is useful to others is motivating) 🤝

You're welcome Whyboris. The whole app makes life a lot more easy for film festivals, especially during selection with this tagging functionality.
I'm a bit of a lurker around here but if you like it I'll make a new feature request here instead of adding it to other posts haha. At least if that's something useful for the development.


Rustdoc from forward_to_deserialize is nasty

All the type parameters are __V and all the argument names are _.

Instead I would prefer to see this:

Fixed in #853.