Cannot find relative main module using remote in renderer

Describe the issue / bug.
As per the Electron documentation of the remote module: "Modules specified by their relative path will resolve relative to the entrypoint of the main process." But when trying const foo = require('electron').remote.require('./foo'); in the renderer process it throws Error: Cannot find module './foo'. This might be related to the webpack config as discussed in #42.
How can I reproduce this problem?
project/
├── main
│   ├── foo.js
│   └── index.js
└── renderer
    └── main.js

// some relative module: main/foo.js
module.exports = 'bar';

// renderer process: renderer/main.js
import Vue from 'vue';

const foo = require('electron').remote.require('./foo');

Tell me about your development environment.

Node version: 8.1.2
NPM version: 5.0.3
vue-cli version: 2.8.2
Operating System: macOS Sierra

This is expected behavior with the presence of webpack, as it will bundle all main process code (within the dependency tree) into one single file. So the remote.require methods will not work with the initial setup as foo.js will never make it to production.
It might be worth updating the webpack configuration to support this in the future, but for the time being this will be on the back burner.

Going to close for now, but will keep this in mind. Feel free to comment back any further questions.

Hi @SimulatedGREG!
I was on holidays but just came back and found what I believe to be a good solution by editing the webpack.main.config.js and manually adding every relative module as new entries.
let mainConfig = {
  entry: {
    main: path.join(__dirname, '../src/main/index.js'),
    foo: path.join(__dirname, '../src/main/foo.js')
  },
}

I recommend you to not use this approach if you want to enjoy all webpack features, especially HMR. Please see https://medium.com/@develar/electron-very-fast-developer-workflow-with-webpack-hmr-e2a2e23590ad
If you want to transfer data between renderer and main — consider to use IPC. You can see HMR ready IPC in the https://github.com/electron-userland/electrify (will be published as separate module soon).

If you want share code between processes — you can simply put code not in the sry/main, but in the src.


Publish metadata that describes the dependencies of a C++ library

Add information about the dependencies of a C++ library to the module metadata file that is published to a Maven repository with the library binaries (added in #143).
Currently, the dependency information is taken from the POM. This has several implications:

The module metadata file can only be used when a POM or some other metadata file is available to describe the dependencies.
It is not possible for each variant of a library to have different dependencies, for example selecting api dependencies for linking and all dependencies for runtime for those tool chains that support this.

Consume this information during dependency resolution, using it in preference to the information in the POM.
Implementation:

[x] Include dependencies in generated metadata
[x] Use dependencies during resolution.
[x] Change C++ plugins to use this.

Test coverage:

[x] public headers are published, implementation headers are not
[x] uses base name of library to generate names of modules and artifacts
[x] headers for implementation dependencies are not visible to consumers

This is done enough.


Add client only DB columns to Postgres DB tables (MP Beta Release)

Need to add the following client columns to each of the tables listed to address the differences between the Check Engine SQL Server client DB tables and the host tables.
CAMD Schema

UNIT_PROGRAM (need to remove from C# generated classes or use a view)

nox_group

CAMDMD Schema

PROGRAM_CODE

rue_ind
so2_cert_ind
nox_cert_ind
noxc_cert_ind
notes

EXEMPTION_TYPE_CODE (use unit_exemption to create a view)

prg_code

CAMDECMPSMD Schema

PROCESS_CODE

process_cd_name
parameter_group_override_cd
process_group_cd

CAMDECMPSAUX Schema

PROGRAM_PARAMETER (if needed use a view to create using PROGRAM and PROGRAM_CODE)

os_ind

CHECK_SESSION (create workspace table for this)

updated_status_flg (existing data needs to be set to Y)
last_updated

Jason, I believe that we verbally talked about scripts for this ticket,  I believed that we were discussing data scripts, but believe the ticket is for structure changes.
Should I produce alter table scripts, or just change the tables directly?

Added additional PROGRAM_CODE columns and updated the CAMPD Release #1 before-load & after-load scripts


Add merge method constants

Fixes https://github.com/xanzy/go-gitlab/issues/409

LGTM! Thanks @bzon! 👍


Userguide section and whitepaper on user change management.

Suggestions for clarifying change management from the user POV
= releases + versions, deprecations, iris.FUTURE
This is mostly for discussion at this point.
It is now pretty much complete + correct to my original conception.
However, @rhattersley already suggested that this information might with advantage be a bit "generalised" and then "pushed back" onto the SemVer project https://github.com/mojombo/semver.
As I was most of the way toward providing this a standalone Iris docs, I've just carried on with that for this first draft.
This issue is mentioned as a possible for 1.10, #1948
which would be nice as we are targetting a lot of deprecations in 1.10.
While may be relevant there, it certainly isn't essential.

if I import iris and look for names without a single leading underscore ... iris sub-packages ...

It's surely ok to exclude local imports, though it certainly is an annoying glitch and a backwards incompatibility if code fails because we removed an automatic submodule import
E.G. what if importing iris did not result in importing iris.cube ?
I think @rhattersley already suggested that all internal imports could be given private internal names, to avoid this kind of problem.
Changing that now will doubtless upset lots of existing user code, but it we want it we should get on right now and introduce a deprecation for it in 1.10
I've put a note in the 1.10 ticket #1948 for now
However, I'm not sure if this is actually  feasible as it stands ...
>>> import iris
>>> hasattr(iris, 'proxy')
False
>>> from iris import proxy as _proxy
/home/h05/itpp/git/iris/iris_main/lib/iris/proxy.py:34: UserWarning: iris.proxy is deprecated in Iris v1.9. Please use lazy imports instead.
  warnings.warn('iris.proxy is deprecated in Iris v1.9. Please use lazy '
>>> hasattr(iris, 'proxy')
True
>>>

I think @rhattersley already suggested that all internal imports could be given private internal names, to avoid this kind of problem.

I'm now :-1: on this. I mentioned the idea yesterday offline, but it doesn't address the whole problem. Instead I think it'd be better to use the existing __all__ convention.

Thanks @rhattersley
This is a jolly useful discussion (for me, anyway)

But they also state:

If __all__ is not defined, the set of public names includes all names found in the module’s namespace which do not begin with an underscore character ('_').

So we'd need to start being a bit more thorough with our __all__ definitions.

All true, but for now all that really matters is what we include in our definition of "public"
- and I now think this is a good candidate to include.
Given that, I think I should enhance the formal definition in the Developer's Guide, and just reference  that here rather than repeating all the gory details :  Applies also to the point you already made about experimental.

However, I'm not sure if this is actually feasible as it stands ...

>>> import iris
>>> hasattr(iris, 'proxy')
>>> from iris import proxy as _proxy

To be clear, this example really isn't quite the point...
Though you can't avoid (e.g.) iris having a 'proxy' property if it has ever been imported,
the real problem is more like this one :
>>> import iris.cube
>>> iris.cube.datetime.MIN_YEAR
1

I.E. 'datetime' appears as a public property of iris.cube.
That we can avoid.

Note: I'm going to let this stew a bit longer before doing any more, in case there are further comments.

@QuLogic thanks, not much to say : all your comments were true !

@rhattersley suggested I could consider pushing some of this content back into the SemVer document.
So I thought about what here is SemVer and what not.
My conclusions are...
The SemVer provisions:

backwards-incompatible changes can only occur at major releases
deprecations can only be introduced at a minor release (not bugfix)
API additions and changes can only be introduced at a minor release (not bugfix)
API means "public"
there are no definitions of certain terms used :
API
public
behavior / functionality
deprecation (what "marking API functionality as deprecated" exactly means)

Additional provisions from Iris (as I'm attempting to rationalise them):

key certainties we are adding:

only deprecated features may be changed at a major release
deprecated functionality will always emit runtime deprecation warnings

( for user code that 'could' invoke deprecated functionality, e.g. with different data )

("therefore":) code that ran in the version preceding a major release, without deprecation warnings, will continue to function unchanged

deprecations

will always involve documentation
will always raise runtime warnings for code where it 'could' make a difference

( though it still isn't clear to me whether we can always deliver this )

iris.FUTURE : central control for compatibility-breaking modal changes
terms we are trying to define more precisely :

what public API means
'backwards compatible' means any conceivable existing code should behave as before
what 'behaviour' means

( return values and side effects, but somewhat limited : excluding warnings and printed output, possibly ? )

This is a fallacy. It is not possible to change anything without breaking something else. https://xkcd.com/1172/

Classik ! :grinning:
But Seriously..
I had a good chat with @rhattersley yesterday about what it would mean to separate iris.fileformats.grib off into a separate package/project, and that provided an interesting example.
This makes very clear a point which I had not properly considered :  That any "behaviour" as I've tried to define it here (aka all outcomes of some code) potentially changes with all dependencies, including upgrades non.
It means :

anything we claim to be "exactly the same" only applies to changing (upgrading) Iris and nothing else (unless explicit dependencies changed.

This is a fallacy. It is not possible to change anything without breaking something else. https://xkcd.com/1172/

Classik ! :grinning:
But Seriously..
I had a good chat with @rhattersley yesterday about what it would mean to separate iris.fileformats.grib off into a separate package/project, as you suggested :  so that we can release Iris 1.10 without needing to first resolve all the ongoing efforts to deprecate parts of it and provide alternatives for everything.

( The idea would be to spinoff "iris_grib", initially equivalent to the current "iris.fileformats.grib", but then evolving seperately.
In particular, we can then deprecate and remove the "old" loader without requiring an Iris major version release. )

This example makes clear a point which I had not properly considered in the proposals here :
Any "behaviour" (as here, i.e. all outcomes of any code) can potentially change when any dependency is changed (e.g. upgraded), to the point of breaking (e.g. dependency major version change).
That means we can only completely fossilize behaviour by pinning the version of all dependencies (that is, at least their major versions, where the concept applies).
Which seems pretty crazy and meaningless.
Instead, I guess the correct approach is to redefine "behaviour" in terms of the calls on component dependencies, not total results ??
Any ideas how best to state this ?
I think we should still accept that if a version upgrade in a dependency actually breaks something, then that is a bug and we need to limit that version until we fix it.
This is currently true for matplotlib and numpy : we aren't fully compatible with latest versions.

@marqh what are your thoughts on this ?
I'd like us to firm up on it, but this may be altogether too wordy

Latest revisions...

I have attempted to respond to all the simple improvement suggestions already posted
I have attempted to define more precisely what we mean by "public"
I have attempted to define more vaguely (!) what we mean by "same behaviour"
I haven't yet taken any position on the PEP440 / SemVer version string formatting issue.

Other issues mentioned in discussion above, but still not addressed in the text :

imported modules-within-modules (as excluded from "public" API)
segregated description of SemVer principles, and where we add to them

ping @marqh

i think it is worth considering keeping this to the white paper, and not adding a section to the user guide
how much benefit do we get from the extra user guide section as well?

not adding a section to the user guide

I agree the userguide is rather bloated now.
My concern is that this topic should definitely be on a list of "things the user should know, that they may not know they need to know".
Can you suggest a better approach that satisfies that need ?
The userguide contents listing was just the only existing place I could think of that performs that function.  Obviously, though, it does include a good few chapters that are firmly in the "specialist interest : come back later" category.
Right now, we don't have a clear 'read this first' section at present, and perhaps we should...

ok, I'm sold; let's accept this now.  Any reworking of the docs can include a review of

Right now, we don't have a clear 'read this first' section at present, and perhaps we should...


CSS stylesheet

Says "css stylesheet is missing" when I try to upload to Wordpress any solutions?

You should use wp_enqueue_style to add the css file.

This isn't a problem related to the framework.


Is it support recurring payments?

Is it support recurring payments?

@biapar you can create your own payment provider that handles this. By default there are non available 'out of the box'.


Implicit Kustomization support

Currently flux-local does not work like flux to generate a synthetic Kustomization if none is present on disk. This is not supported by kustomize build natively, as it prefers to have everything explicit.
Today flux works by actually writing to disk, which is not appropriate for a library/tool to update someones repo. Another option is to use some kind of overlay, which may be too heavy weight. Another option is to try to make a worktree we can write to which also seems too heavyweight for a readonly view (though seems appropriate for diff)
I actually did solve this in https://github.com/allenporter/flux-diff by making an in memory overlay to generate files in while runnign the go program. One option may be that the CLI needs to be entirely converted to golang.

As an example of the gap, take this cluster: https://github.com/allenporter/flux-local/tree/main/tests/testdata/cluster2
In the apps Kustomization I had to add https://github.com/allenporter/flux-local/blob/main/tests/testdata/cluster2/apps/kustomization.yaml to make it work, but it should ideally work implicitly.


Fix Metaquantome Viz (v2.0.0) Heatmap Clustering

metaQuantome: visualize
Issue
The metaQuantome: visualize (version 2.0.0-0) tool does not run correctly when using the heatmap plotting type.

Error message: Name 'feature_cluster_size' is not defined when running
Discovered by @subinamehta
Reason
An undefined variable (https://github.com/galaxyproteomics/tools-galaxyp/blob/master/tools/metaquantome/metaquantome_viz.xml#L120) from the 758f945 commit.
Fix
Prepend '$mode_args.plot' to unknown variables.
To do:

[x] Add/edit tests to define expected heatmap clustering behavior file outputs.

@jraysajulga would be good to have a test for this option. Thanks.

changes looks good, but tests are failing infortunately :(

changes looks good, but tests are failing infortunately :(

Okay. Do you have any tips for using planemo? I'm trying to planemo test and planemo serve but they both get stuck while running the tool.

Okay. Do you have any tips for using planemo? I'm trying to planemo test and planemo serve but they both get stuck while running the tool.

Which tests are failing?

Which tests are failing?

Go here: https://github.com/galaxyproteomics/tools-galaxyp/pull/504/checks?check_run_id=1766314904
Click on "artifacts" and download the "All tool tests results"

Go here: https://github.com/galaxyproteomics/tools-galaxyp/pull/504/checks?check_run_id=1766314904
Click on "artifacts" and download the "All tool tests results"

Okay. Thanks! That's quite helpful. Seems like the last error is during the lint:
.. ERROR: Invalid XML found in file: tmps78h8uak. Errors [/tmp/tmps78h8uak:398:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1: Element 'test', attribute 'expect_num_output': The attribute 'expect_num_output' is not allowed.]

Okay. Thanks! That's quite helpful. Seems like the last error is during the lint:
.. ERROR: Invalid XML found in file: tmps78h8uak. Errors [/tmp/tmps78h8uak:398:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1: Element 'test', attribute 'expect_num_output': The attribute 'expect_num_output' is not allowed.]

expect_num_outputs plese see here: https://docs.galaxyproject.org/en/latest/dev/schema.html#id80

expect_num_outputs plese see here: https://docs.galaxyproject.org/en/latest/dev/schema.html#id80


WIP: test fixes

This gets the tests to pass! Although it would be nice to not need to commit the 1.4MB PLT file to the repository, but if it's the specific PLT for the tests than maybe that's fine.
Although it would be nice to host this PLT and other PLT's in a GitHub release so that they can be dynamically downloaded on startup. Although there's a very large number of potential combinations so I'm not sure it's feasible to build them all.


Params Named '_' in Array Move Themselves

It appears that rspec (or perhaps rails) is doing something very strange with '_' keys in a hash ordering.
app/controllers/demos_controller.rb:
class DemosController < ApplicationController
  def update
    raise params.inspect
  end
end

spec/controllers/demos_controller_spec.rb:
require 'rails_helper'

RSpec.describe DemosController, type: :controller do
  describe 'PATCH #update' do
    it '...' do
      patch :update, params: {
        bulk: [
          { id: 'A' },
          { id: 'B', _destroy: true }
        ]
      }
    end
  end
end

Result:
RuntimeError: [<ActionController::Parameters {"id"=>"A", "_destroy"=>"true"} permitted: false>, <ActionController::Parameters {"id"=>"B"} permitted: false>]

(notice A gets the '_destroy' instead of B:)
Tested:
rails: '5.1.2'
rspec-rails: '3.6.0'
The identical code test written in minitest:
require 'test_helper'

class DemosControllerTest < ActionDispatch::IntegrationTest
  test 'updating' do
    patch demo_path, params: {
      bulk: [
        { id: 'A' },
        { id: 'B', _destroy: true }
      ]
    }
  end
end

RuntimeError: [<ActionController::Parameters {"id"=>"A"} permitted: false>, <ActionController::Parameters {"id"=>"B", "_destroy"=>"true"} permitted: false>]

(notice B correctly gets the '_destroy' instead of A:)

sample project that has this issue: demo.zip

@ksylvest Rack has a hard time with deep structures of hashes and arrays like that. See https://github.com/rack/rack/pull/1058 for instance.

Closing as this is unlikely to be an rspec-rails issue, we pass them through to Rails / Capybara etc and don't modify them in anyway I can think of that would cause this.


Serve content with support for HTTP conditionals and range requests

This PR introduces new utilities to serve content with support for HTTP conditionals as defined in RFC7232. It will allow to return 304 Not Modified (for instance) and handle HTTP Range requests (RFC7233) transparently.
Motivation and Context

Implementing RFC7232 and RFC7233 is not trivial: I believe it should be implemented at Tide level instead of leaving the users implementing it themselves. At the time I checked a few weeks ago Rocket, warp and actix all had limited (if any) support for such conditional requests (this might have changed). Support for conditional requests is provided by Go's standard http library.
This will help closing #63. Also the current implementation of tide::Route::serve_dir could benefit from it to handle last modification date and range requests.
I am already running a full implementation in production to serve a bunch of video files for internal use (building a media center for home).
This draft PR depends on changes that are not yet released (some not even merged) in http-types, see dependencies section below. I will update this PR as much as the situation evolves on http-types side. I will then commit the implementation, testing and more documentation.
Finally i will move out of draft status once everything is released on http-types side and implementation, tests and docs completed.
For now I am requesting comments for interest in such feature within Tide or if you prefer that I release this in an external crate. Also I would like you comments on the API, please.
Thanks in advance !
Cheers.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Dependencies:

[x] http-rs/http-types#211 to be released
[x] http-rs/http-types#222 to be merged
[x] http-rs/http-types#224 to be merged
[ ] http-rs/http-types#180 to be merged

I think if we have this, then ModState probablly belongs in htpp-types?
I am not sure if that would be confusing or not, given most of the other things there represent http headers directly, but it feels like the correct place.

I think if we have this, then ModState probably belongs in http-types?
I am not sure if that would be confusing or not, given most of the other things there represent http headers directly, but it feels like the correct place.

This is indeed an open question. It could be renamed in something like http_types::conditional::CondState, or a better name that suite more HTTP wording. But personally I am more on the it would be confusing side: I believe the ModState is closer to the application logic, than HTTP logic (the border is thin). It is just a convenient utility provided to the user to pass either a time or a version string associated to its resource.
Looking at what Go does they just allow a time in their serve_content function, and they force users to set the ETag if any at the response header level. This is where Rust enums are superior and allow to do more for the user.
Otherwise I have no strong opinion about it.

This is indeed an open question. It could be renamed in something like http_types::conditional::CondState, or a better name that suite more HTTP wording. But personally I am more on the it would be confusing side: I believe the ModState is closer to the application logic, than HTTP logic (the border is thin). It is just a convenient utility provided to the user to pass either a time or a version string associated to its resource.

I might change my opinion here. When you look at the If-Range header implementation I have submitted in http-rs/http-types#180 it has exactly the same need. Having a shared type to handle both cases might be interesting, and in such case it would belong to http-types utils.

@Fishrock123 @ririsoft
Hi, I’m interested that conditional headers in tide framework. I tried to implements the  middleware which can only verify about If-None-Match and content ETag. if they match, it return the 304 NotModified.
https://github.com/u5surf/tide-condition
serve_file directive must know about file modified information through from_file_with_path of http-types
(see also
https://github.com/http-rs/http-types/blob/main/src/body.rs#L429
Fortunately, async_std::fs::Metadata has file modification time.
https://docs.rs/async-std/0.99.12/async_std/fs/struct.Metadata.html#method.modified
It is possible to be use this. Although, it has not implemented about this yet.
So now, it is hard to use modified information to serve the static file.
Moreover, how can be treated in case of dynamic generated contents?
That’s why I gave up implements the period verification such as using If-Modified-Since and Last-Modified

I am closing this PR as I am not using/working on tide anymore and will thus not be able to work on this further on.


Bump & release for #108

Any chance we could bump to v1.3.1 to release #108?

Hey I'm closing this PR but I cherry-picked your commit and amended it with an update sync'ing de TS optionality with the JSDocs

Thank you so much @webketje!


Typo in quote

https://github.com/webpod/zurk/blob/04301a699a9031f30d24e33178662901f2b3308a/src/main/ts/x.ts#L59
qoute should be quote here :smile:

@caleblloyd,
Thanks for the report. Fixed.


This is the worst slider ever, why the source is not public so we can fix it ourselves?

It just breaks and breaks and breaks!

Please let us know the issue. Thanks in advance!

@jssor please can you explain why there is no source code? appreciate it.


issue related to folder names with "space"

reported issue:
https://sourceforge.net/p/spinalcordtoolbox/discussion/help/thread/842a6926/
solution is to use relative path.

configure the Travis testing with the toolbox installed in a folder with spaces, and use absolute names whan calling functions

We should test with quotes and with "\ "


[B2C] Server side block: username and realm is not returned in the response

Duplicate, tracked here:
https://github.com/AzureAD/microsoft-authentication-library-for-android/issues/437


Timeout not working

First of all, thank you for the amazing work.
Even if set to 1(ms), the getFingerprintPerformance never times out, returning an object with elapsed keys in the tenths of ms, and a total time of +100ms:
import { setOption, getFingerprintPerformance } from '@thumbmarkjs/thumbmarkjs';

setOption('timeout', 1);
console.log(getFingerprintPerformance());

{
  "elapsed": {
    "audio": 42.80000019073486,
    "canvas": 9.5,
    "fonts": 9.399999618530273,
    "hardware": 9.399999618530273,
    "locales": 9.399999618530273,
    "permissions":<PHONE_NUMBER>0463257,
    "plugins": 9.299999713897705,
    "screen": 9.299999713897705,
    "system": 9.199999809265137,
    "webgl": 9.099999904632568,
    "math": 9.099999904632568
  },
  ...
}
Time elapsed:<PHONE_NUMBER>0463257

I know for a fact that the setOption('timeout') is working, because if I use setOption('foo') it will raise as foo not being a valid option.

After further testing, it was a false alert; a simple component that just returns this promise was used as proof of concept:

function proofOfConcept() {
  return new Promise(resolve => setTimeout(() => {
    resolve('Promise 1 resolved');
  }, 1000))
}

includeComponent('proofOfConcept', proofOfConcept);

{
  "elapsed": {
    "proofOfConcept": 42.40000009536743
  },
  "proofOfConcept": {
    "timeout": "true"
  }
}

In this case, the timeout correctly happens, but it does so within 42ms, which I'm crediting to the overhead of the rest of the library.


Render Error

Steps to reproduce
Use Tab Bar and display list veiw in each Tab
suddenly renddered error occurred
Expected results
No Error should display list with out error
Actual results
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
 [
                  //         Center(
                  //           child: Text("No Report Yet"),
                  //         )
                  //       ]
                  //     : reports
                  //         .map(
                  //           (e) => ReportCard(
                  //             report: e,
                  //             onClick: () => selectReport(e),
                  //           ),
                  //         )
                  //         .toList(),
                ),
          (reports2.length < 1)
              ? const Center(
                  child: Text("No Report Yet"),
                )
              : ListView.builder(
                  itemBuilder: (BuildContext context, int index) {
                    return ReportCard(
                      report: reports2[index],
                      onClick: () => selectReport(reports2[index]),
                    );
                  },
                  itemCount: reports2.length,
                ),
        ],
      ),
    ],

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Can any one help


Does the en_coref_lg model work with the spacy's "en_vectors_web_lg" or only with " en_core_web_lg"?

Only this question. Thanks

The new release (NeuralCoref 4.0) is now independent of SpaCy models and can be integrated in any SpaCy (English) pipeline. Please check the README for the new usage instructions and details.


Class 'App\Http\Controllers\DownstreamResponse' not found

Trying to send a Notification and I got the above error, how do I fix this?

Hi
I think it Missing an import of Laravel-FCM\Response\DownstreamResponse somewhere in the code.
Can you give me more informations about this error.
Maybe with a part of your code that thrown the exception.
Thanks

$downstreamResponse = FCM::sendTo($tokens, $option, $notification);
$downstreamResponse->numberSuccess();
$downstreamResponse->numberFailure();
$downstreamResponse->numberModification();
//return Array - you must remove all this tokens in your database
$downstreamResponse->tokensToDelete();
//return Array (key : oldToken, value : new token - you must change the token in your database )
$downstreamResponse->tokensToModify();
//return Array - you should try to resend the message to the tokens in the array
$downstreamResponse->tokensToRetry();
// return Array (key:token, value:errror) - in production you should remove from your database the tokens present in this array
$downstreamResponse->tokensWithError();

I commented out those lines apart from the first one and it worked.

I am unable to reproduce your problem
Do you use Laravel or Lumen?
Can you give me all the content of the error message?

This is related to not having the use statement for DownstreamResponse (as you said, not imported).
The readme is missing them in some of the other examples, I only updated one.

I am using Laravel 5.2
Notifications are sent but it produce errors on my laravel.log and I found these lines of codes are the ones causing it:
		$downstreamResponse = new DownstreamResponse($response, $tokens);
		$downstreamResponse->numberSuccess();
		$downstreamResponse->numberFailure();
		$downstreamResponse->numberModification();

		//return Array - you must remove all this tokens in your database
		$downstreamResponse->tokensToDelete();

		//return Array (key : oldToken, value : new token - you must change the token in your database )
		$downstreamResponse->tokensToModify();

		//return Array - you should try to resend the message to the tokens in the array
		$downstreamResponse->tokensToRetry();

This was the error:
[2016-07-22 09:10:28] local.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Class 'App\Api\V1\Controllers\DownstreamResponse' not found' in C:\wamp\www\MyApp\app\Api\V1\Controllers\PushNotificationController.php:42
After I did what @gcphost recommended (use LaravelFCM\Response\DownstreamResponse;), I got the following error:
[2016-07-22 09:11:39] local.ERROR: exception 'ErrorException' with message 'Undefined variable: response' in C:\wamp\www\MyApp\app\Api\V1\Controllers\PushNotificationController.php:42
Sorry, what does those lines of code do, I mean what are their functions.

Hi,
I think that your error is thrown by the following line:
$downstreamResponse = new DownstreamResponse($response, $tokens);

You shouldn't instantiate DownstreamReponse in your controller.
DownstreamResponse is constructed by the package and  is returned by the method: FCM::sendTo($tokens, $option, $notification);
Like in the following line:
$downstreamResponse = FCM::sendTo($tokens, $option, $notification);

In summary,

You send a notification with the method FCM::sendTo($tokens, $option, $notification);.
The package is sending the notification and constructs a DownstreamResponse with the response returned by fcm.
In your controller, you can check if the notification was send with success or if some error appeared during the process, with the following methods:
$downstreamResponse->numberSuccess(),  $downstreamResponse->numberFailure(); and $downstreamResponse->numberModification();
You can get all tokens that you must to remove in your database with the method: $downstreamResponse->tokensToDelete();
You can get all tokens that you must to modify in your database with the method:  $downstreamResponse->tokensToModify();
You can all tokens that you should resend with this method: $downstreamResponse->tokensToRetry();

Please can you give me a feedback if this solution is working for you.
Best Regards

Thanks for the detailed explanation, it works well now. Thanks

ErrorException in Manager.php line 77: Missing argument 1 for Illuminate\Support\Manager::createDriver(), called in /home/kaptastech/public_html/application/API/events/vendor/illuminate/support/Manager.php on line 87 and defined
I am receiving following issue with lumen when trying send notification message.
Here is my code :
`$notificationBuilder = new PayloadNotificationBuilder('my title');
$notificationBuilder->setBody('body')
->setSound('default');
    $notification = $notificationBuilder->build();

    $optionBuilder = new OptionsBuilder();

    $token = "token_here";
    $deviceResponse = FCM::sendTo($token, $optionBuilder->build(), $notification);
    `

Thanks


Chat between users has been removed for content policy reasons.

Hi there I'm SimSimi!
It's removed policy is application chat. Well that's good.

The released iOS: 8.7.9


Please add Academic theme

Hi,
I have created a new theme for academic staff/student websites and would be grateful if you could consider adding it to the official theme collection. If accepted, it would appear to be the first academic theme in the collection.
Theme repo: https://github.com/gcushen/hugo-academic
Thanks!

Hi @gcushen,
thank you for sharing your theme with the community. To take the last mile please add a static folder to the exampleSite directory. It's required by the build script of https://themes.gohugo.io even if you don't use it.

Thank you very much @digitalcraftsman , I have updated the theme and believe it should meet the requirements now.

LGTM. I've added your theme in cb8284a2f346a442c9fd43a8bfe739d3392ee05e.

Sorry @digitalcraftsman , after you added the theme, I noticed a few very minor differences between the dev and production environments (causing incorrect rendering of README.md and an invalid CSS image path that needed fixing). Please could you kindly update to the latest https://github.com/gcushen/hugo-academic ? Cheers :)


fix: dropdown radio padding for item indicator

What kind of change does this PR introduce?

Ensure that dropdown radio items have consistent spacing (basically emulated how radix UI implemented it)

@joshenlim looks good
I think you might need to isolate the padding to just checkbox and radio items though

Ahh okay gotcha on this! Will push a fix today

just pushed a quick fix for this, also eyeballed the other dropdown components to make sure they look fine
quick question as well, how do i get my storybook styling to look like yours haha, the black background, font family etc

@joshenlim looks like something is wrong. lets screenshare later and debug

Looks related, got a similar screenshot here https://github.com/supabase/ui/pull/207

LGTM 🔥

:tada: This PR is included in version 0.26.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@joshenlim ahhh
see this screenshot on this PR.
I think your using the wrong toggle for dark mode.
https://github.com/supabase/ui/pull/207#issuecomment-852287632

ahh gotcha on this ^ yeah i was using the sun/moon icon for the toggle, but oddly the font seems weird on my storybook - is there supposed to be a font loaded?


dynamically allocate threads

Implement dynamic thread allocation similar to libFuse.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

We ended up pulling the multi-threaded FUSE support into mountpoint rather than fuser (#135), so this is stale now. We might revisit in the future, but closing for now.


search_by_coordinates only returns food results

I have been trying to use search_by_coordinates to find POI around me but it seems that it only returns the same food results no matter what I put in as term. See below
Inputs:
params = {
'term': 'superstore',
'limit': '40',
'radius_filter': '10000'
}
response = client.search_by_coordinates( lat, lng, params )
url generated under sign_request
https://api.yelp.com/v2/search/?ll=51.0454027%2C-114.0565189%2C{'term'%3A+'superstore'%2C+'limit'%3A+'40'%2C+'radius_filter'%3A+'10000'}&oauth_token=XXXXXXXXXXXXXXXXX&oauth_consumer_key=XXXXXXXXXXXXXXXXXX&oauth_nonce=84599947&oauth_timestamp=1457744867
i'm not sure if term=superstore should go right after search/? and this is not happening here. I'm wondering if API is treating it as empty search term.

parameters are passed wrong in here.

Alright, it turns out you need to do it this way

But this won't work. Guess what, lat and lng needs to be at end of url!!!!
So you get something like this

and the API complains about InvalidParameter
But if you get rid of limit and radius_filter and leaving only term

you can get a url with 'll' at the end

and the API will give you some good results....

So when we generate the url. maybe find a way to leave lat and lng terms at the end?

Hm, I know some OAuth libraries want query-string args to be in alphabetical order, I wonder if that's what we're hitting here.

ya i think so... looks like it's in reverse alphabetical order. "term", "ll", "limit"

Digging in, trying to reproduce locally.

@FiniteElementries : What version of the oauth2 library are you using?  pip freeze | grep oauth will get the answer I'm looking for.

Hi @mittonk , oauth2==1.9.0.post1 is what I have got. Thanks for looking into this. Cheers~

OK, reproduced problem.

One layer of the onion: in your first attempt,

response = client.search_by_coordinates( lat, lng, params )

the params dict is getting passed in as the accuracy argument, and leaving term, limit, and radius_filter empty.  Using the Python **kwargs feature (https://docs.python.org/2/tutorial/controlflow.html#keyword-arguments) gets us further:
response = client.search_by_coordinates(lat, lng, **params)

That's basically equivalent to
response = client.search_by_coordinates(lat, lng, term='superstore', limit=40, radius_filter=4000)

That gets us to a fairly unhelpful
InvalidParameter:

error

Next layer of the onion:  Adding some ipdb.set_trace() diagnostics to the error-printing code, I find the actual error from the API is:

ipdb> response
{u'error': {u'field': u'limit', u'text': u'One or more parameters are invalid in request', u'description': u'Limit maximum is 20', u'id': u'INVALID_PARAMETER'}}

That's much clearer.  (The clientlib should print that whole error, would have saved us a bunch of time: issue TODO).

Dropping limit to 20 as allowed by the API gives our expected result:

response = client.search_by_coordinates(lat, lng, **params)
print response.businesses[0].name

Real Canadian Superstore

So, there's nothing about alphabetical order (so we can ignore that), just Python keyword ordering, an illegal input, and a woefully inadequate error message.
@FiniteElementries : Is that enough to get you rolling again?
Thanks for the nice adventure, we'll work on improving the error messages!

@mittonk  lol that's a tricky one. Thanks man. It works!

Awesome.


Add test suite to test browser compatibility

So far, I have been developing primarily in Firefox 61, which will remain our only officially supported platform for a while. The Curation Tool has been used in Google Chrome without any severe bugs. However, we should write an in-browser test suite that tests whether user interface features display and operate correctly on different browsers.

You might find this article useful. And check out Selenium if you haven't yet.

We should also choose our target browsers in Vue CLI so we generate the right polyfills and transpline the JavaScript code correctly. We're currently using the Vue defaults, which is currently "last two versions of browsers with global usage > 1%, but not IE <= 8".

It looks like Vue now recommends using Cypress for both end-to-end testing as well as component testing (see blog post on setting this up) and Vitest for unit tests (see browser-specific testing).
Cypress looks like it will meet the needs of this issue. This isn't a priority for v1.0, but I wanted to add this comment to remind myself to do this at some point.


Object scale affects TF values.

For the same reasons as in https://github.com/Field-Robotics-Japan/UnitySensors/issues/55
https://github.com/Field-Robotics-Japan/UnitySensors/blob/master/Assets/UnitySensors/Runtime/Scripts/Sensors/TF/TF.cs

#140 にて修正完了


Semaglutide injection measure definition including tablets

@andrewbarron85 has drawn my attention to the fact that the semaglutide measure is now including tablets (NLP STP example)
A quick review looks like we did not foresee release of tablet preps when we wrote the measure. The very quick fix is to include bnf name NOT LIKE tab. Other fixes include using dmd.formroute or curation of bnf codes.

We thought #2940  fixed this issue but tablets are still being reported on the measure.

You're missing a \n from this line.
Because it's missing, the generated SQL is:
SELECT
     CAST(month AS DATE) AS month,
     practice AS practice_id,
     SUM(total_quantity) AS numerator
 FROM hscic.raw_prescribing_normalised
 WHERE quantity_per_item>3 AND bnf_code LIKE '0601023AW%' --Semaglutide AND bnf_name  LIKE '%inj%'
 GROUP BY month, practice_id

and not:
SELECT
     CAST(month AS DATE) AS month,
     practice AS practice_id,
     SUM(total_quantity) AS numerator
 FROM hscic.raw_prescribing_normalised
 WHERE quantity_per_item>3 AND bnf_code LIKE '0601023AW%' --Semaglutide
       AND bnf_name  LIKE '%inj%'
 GROUP BY month, practice_id

That is, everything after the comment is erroneously included in the comment.
See lpneedles.json for where this is done correctly.
I'm going to check all other measures to see whether we hit this elsewhere.
If we get more funding, reworking measure definitions is top of my wishlist.

Thanks @inglesp: hopefully fixed and PR created.

This is the only measure affected.
# check_comments.py
import glob, json

for path in glob.glob("*.json"):
    with open(path) as f:
        measure_def = json.load(f)

    for key in "numerator_where", "denominator_where":
        if key in measure_def:
            for row in measure_def[key ][:-1]:
                if "--" in row and row[-1] != "\n":
                    print("-" * 80)
                    print(path)
                    print(row)

$ python check_comments.py
--------------------------------------------------------------------------------
semagglutidequantity.json
bnf_code LIKE '0601023AW%' --Semaglutide
--------------------------------------------------------------------------------
semagglutidequantity.json
bnf_code LIKE '0601023AW%' --Semaglutide

this is now fixed.


Grafana dashboard - Github actions postcommit workflows mapping

The following dashboard maps every post-commit workflows in Grafana Dashboard according to the following states:

Success
Fail
Pending
Time-out
None

The dashboard depends on PR-24073

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

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

R: @damccorm

@MarcoRob were you able to validate that this correctly creates the dashboard locally? If so, would you mind commenting with a screenshot of the rendered dashboard? Grafana changes are pretty hard to review without that context

Sure!
The data is being retrieved from sync script, I will share with you directly via email a test instance where we were testing the dashboard and validating

#24073 was merged so this should be good to go


Adding Readme

Creating a juicy readme for this project
What should the readme contain?

A few words about the dependencies what the project includes, also list them on top of the readme (badges)
h2 heading title of the project name ( ZOCS )
Pronunciation of the project name (The same as socks)
A slogan along the logo or banner of the project (this will be included in this ticket further on)
The main purpose of the project, the idea in the background
A link to the demo page what actually will be the documentation on this project
A Roadmap to see what happens in the next releases
About contribution
List of contributors

Slogan should look like the following in the readme

Zocs to keep your docs warm

Logos Banners
A Sock where a documentation icon lives
Imagine a house cut half in middle
Like this just instead of a house imagine with a sock

List of contributors like

Details
onnaiwd


Writing unit tests for Login component

I'm submitting a
Unable to write unit test case with the given example on the repo
Current behavior
Latest version from master branch. mount expects some structure on the component causing type not defined error
Expected behavior
Documentation or sample code would be helpful
Minimal reproduction of the problem with instructions
import { mount, createLocalVue, shallowMount } from '@vue/test-utils'
import Login from<EMAIL_ADDRESS>import VueRouter from 'vue-router'
import ElementUI from 'element-ui'
//import i18n from '@/lang'
const localVue = createLocalVue()
localVue.use(VueRouter)
localVue.use(ElementUI, {
i18n: (key:string, value:string) => i18n.t(key, value)
})
const routes = [
{
path: '/',
name: 'home',
children: [{
path: 'dashboard',
name: 'dashboard'
}]
}]
const router = new VueRouter({
routes
})
describe('Login.vue', () => {
it('toggle click', () => {
//const wrapper = shallowMount(Login,{localvue})
const wrapper = mount(Login, {localVue,router})
})
})
What is the motivation / use case for changing the behavior
Will be able to contribute or develop more test cases for the project
Environment

默认的色彩好难受，朦朦胧胧的感觉


Company Ticket in the planning stage

When a company ticket is selected to be used in a showing in the planning stage it should not show up in the dropdown menu when signing up for another showing.

It shouldn't after a hard refresh. The state isn't updated in the frontend

Okay I signed up again and they were marked as pending, maybe I did something wrong the first time 👇

@Edholm This might be an outdated issue in that case, a fix for this should be in master.

hehe might be but not verified though

This problem exists in the current master branch as well.

This should be resolved in #149


Switch to using asyncio.timeout instead of asyncio.wait_for

asyncio.wait_for creates a task whereas asyncio.timeout avoids doing this which decreases latency.
Fallback to using async_timeout when the python version is too old (<3.11)
asyncio.timeout will become the underlying implementation for async.wait_for in cpython 3.12
https://github.com/python/cpython/pull/98518

Thank you for the suggestion! I think it's a good idea. Let's do it.
Until now, websockets has no dependencies. This removes an entire category of concerns like managing versions that, as a single maintainer, I don't want to deal with. I understand that this may not look like a big benefit but it is valuable to me.
In order to keep this benefit, I am tempted to do one of the following:

create a small compatibility layer to use asyncio.wait_for on Python < 3.11 and asyncio.timeout on Python ≥ 3.12
vendor CPython's or  async-timeout's implementation — they're probably identical if async-timeout was merged into CPython.

Option 1 could be as simple as:
if sys.version_info[:2] >= (3, 12):

    async def asyncio_wait_for(coro, timeout):
        async with asyncio.timeout(timeout):
            await coro

else:

    asyncio_wait_for = asyncio.wait_for

In all cases, version compatibility code should go in websockets.legacy.compatibility rather than a new module.

I'm aware that my option 1 doesn't yield performance benefits on Python < 3.12 while your version does. IMO those who care about performance optimizations available in Python 3.12 should upgrade to Python 3.12. It isn't my job to fake that for them.

I'll work on option 2 since the races in async.wait_for and the issue tickets they generated for cpython were part of the motivation for cpython switching out the implementation.  It think it would be best if everything behaved the same regardless of the python version.
ex:
https://github.com/python/cpython/issues/86296
https://github.com/python/cpython/issues/81839
https://github.com/python/cpython/issues/96764

Its passing locally now. Hopefully it should be good to go now

Also, It would be great if you could rebase and squash into a final commit to clean up the PR.

Late here.  I'll take a look in the morning if the Home Assistant beta isn't too busy.

I squashed your commits and I'm finalizing the changes here: #1325.

I filed https://github.com/nedbat/coveragepy/issues/1598 for the coverage problem.
Thank you for your contribution!

I had this on my followup list and just returned to it and found you already got it over the finish line.  Many thanks 👍 🐬 🥇

This caused https://github.com/encode/uvicorn/issues/1927.

Looks like you have already determined whats going on in https://github.com/encode/uvicorn/issues/1927#issuecomment-1656580406
Let me know if I can help in any way.
Cheers


Reduce FBH5 output volume

Reduce FBH5 output volume by generating this diagnostic output only once every ten scans.

Added in 4f6ac37, will close when tested live.

Working in production at MeerKAT.


Notes section error

In the notes section discussing the difference between ALLUSERS=1 and ALLUSER=1 the last sentence is confusing:
"...and the ALLUSER=1 parameter is used only in VDI environments to specify a per-machine installation". Generally VDI is used in the context of a persistent "Personal Desktop" and without this reference the sentence is misleading. The per-machine based installed refers to RDSH/Pooled WVD images. Can this be updated to clarify?

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

ID: 17880b9d-6b98-3194-cc33-fe8067ce241e
Version Independent ID: 643bcf2f-507b-e449-73db-923d8a368ad9
Content: Teams for Virtualized Desktop Infrastructure - Microsoft Teams
Content Source: Teams/teams-for-vdi.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@wcvanzyl  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@wcvanzyl Do you think adding the below sentence to the note would help? If not, what exact wording would you like to see?
ALLUSER=1 parameter is used only in VDI environments to specify a per-machine installation, which implies a shared environment subject to change (RDS/Pooled WVD) and not a persistent, dedicated one.

That would make sense, thank you
Werner
On Tue, 2 Jun 2020 at 03:27, VLG17<EMAIL_ADDRESS>wrote:

@wcvanzyl https://github.com/wcvanzyl Do you think adding the below
sentence to the note would help? If not, what exact wording would you like
to see?
ALLUSER=1 parameter is used only in VDI environments to specify a
per-machine installation, which implies a shared environment subject to
change (RDS/Pooled WVD) and not a persistent, dedicated one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/4508#issuecomment-637378791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMI36D7LOIZFWXO6KIQK66TRUSZV5ANCNFSM4MFTXEIA
.

--
Werner

@LanaChin

I've pinged the PMs on this. Thanks.

Thanks for your feedback. Per the product team, the ALLUSER=1 parameter (setting per-machine installation mode for VDI) is not just for a shared environment. It can be used for both shared and dedicated VDI scenarios.


Ollama load balancing doesn't supprot different model names with the same ID.

Bug Report
Probably also related to https://github.com/open-webui/open-webui/issues/1081
Installation Method
docker-compose.
Environment

Open WebUI Version: v0.3.33

Ollama (if applicable): 0.3.6

Operating System:  Arch linux

Browser (if applicable): Brave

Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[x] I have included the browser console logs.
[x] I have included the Docker container logs.
[x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
I expect different model names to appear as different models in the openwebui dropdown.
Actual Behavior:
OpenWeb UI is seeing these as the same model (because they are, just aliased). I htink this is becuase the ID numbers are the  same.  Openwebui is ignoring the model names and combining the two. however this results in a 404 because it's only associating one model name with the index.  When openwebui load blances to the other model, it can't find it as the call to ollama uses the model name not the ID.
Description
Bug Summary:
Custom Model Names do not work correctly with loadbalancing in openwebui.
Reproduction Details
Steps to Reproduce:
I have two machines that run Ollama servers - epyc 16 core based that only has CPU, and a desktop with a 3090 in it.  I used ollama cp to rename the models so that if the desktop was on i could choose the fast option.
Epyc:
NAME                                                ID          	SIZE
codestral:22b-v0.1-q8_0-cpu-16  	8dde0029a91f	23 GB
Desktop:
codestral:22b-v0.1-q8_0-desktop  	8dde0029a91f	23 GB
Logs and Screenshots
Screenshots/Screen Recordings (if applicable):

Additional Information
The only reason i'm using custom model names is  because there's no ollama server load balancing where it allows you to prefer one server over the other (or routes to the more performant server).
My needs are simple so I'd be happy with "if desktop is offline then use server cpu"

Ollama load balancing will be deprecated in favour of #5680 in the near future! Stay tuned!


Add new masternode

<IP_ADDRESS>

<IP_ADDRESS>

Addet

You didn't add the one I put in the pull <IP_ADDRESS> but did add the ones that replied to my pull (sigh). Was there an issue with it?


Revert "Roll Plugins from a9f34a1d528c to 1e2ffdb006e6 (1 revision)"

Reverts flutter/flutter#94313
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux flutter_plugins/4133/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac plugin_lint_mac/4793/overview

I doubt this will re-open the tree, the failing test doesn't use the plugin roll SHA.

Oh, actually it will help Linux flutter_plugins but not Mac plugin_lint_mac.
info - example/lib/web_view.dart:550:37 - Prefer const with constant constructors. - prefer_const_constructors

@bparrishMines plugins sheriff

@mvanbeusekom re: lint error https://github.com/flutter/plugins/pull/4553

The Mac plugin_lint_mac failure is due to url_plugin being federated.  I'll get a fix out.
https://github.com/flutter/plugins/commit/a456f6343840eba0d0b4de27e215f210bf4dbcc4

The Mac plugin_lint_mac failure is due to url_plugin being federated. I'll get a fix out. flutter/plugins@a456f63

https://github.com/flutter/flutter/issues/94372

Hm, this roll revert didn't fix Linux flutter_plugins
   info - example/lib/web_view.dart:550:37 - Prefer const with constant constructors. - prefer_const_constructors

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8829201417244925441/+/u/run_test.dart_for_flutter_plugins_shard_and_subshard_analyze/test_stdout

I think it needs to be rolled to https://github.com/flutter/plugins/commit/6bc9a2bd62e5ac9ff36b0fddf77ece6fdddaeef6. We should instead merge https://github.com/flutter/flutter/pull/94352/.

@jmagman To clarify, are you saying that we should abandon this PR, and instead merge https://github.com/flutter/flutter/pull/94352?

@jmagman To clarify, are you saying that we should abandon this PR, and instead merge #94352?

Yes, this isn't the right SHA to roll to, it didn't fix Linux flutter_plugins .  Actually #94352 had a failing ci.yaml roll test and all the tests were queued, and I don't know how to kick the tests.  I created an identical manual roll at https://github.com/flutter/flutter/pull/94375


Default sidebar links broken

Issue:
The links in a newly generated "default sidebar" point to <notebook_name>.html
Since "pretty links" are the default for the jekyll page generation, this does not work (404 on following the link from the index page).
Steps to reproduce:

Generate a new project via the template, enable github pages
Build lib, build docs, push to github
Access the generated documentation on github, try to click the link to the core notebook

Possible fixes:
The breaking commit seems to be da400c3572a944e23d569a6017bc0884335e1d36 (20.08.). It replaced "f.stem" by "f.name", therefore making it "core.html" instead of "core". I don't know why this change was made, so one fix would be to:

Undo this particular change (not sure what this would break further down the line)
or
Turn of jekyll "pretty links" in the _config.yml.

UPDATE:
I just realized that in the same commit Jeremy changed the _config.yml for the nbdev documentation to essentially implement solution 2 from above. If this is intended to be the solution then we should adjust the nbdev template to generate such a _config.yml by default. I would prefer this solution, as it allows to have the documentation generated in a static way that doesn't require a running jekyll server to view it.

I think I have a similar issue. I have a repo called "integrators" and a nb that exports to basic.py. My navigation has an item called "title" and when I click it, it says: `/integratorsbasic.html' not found.

Thanks, your suggestion "2. Turn of jekyll "pretty links" in the _config.yml." worked for me!

It works for me either!
please erase out if there is "pretty links" in the _config.yml file.

that does not solve it for me. I am using the gitlab template from https://gitlab.com/thomas.capelle/nbdev_template/. By "pretty links" you mean the "permalink: pretty" line?

If I am manually chaning that f.name to f.stem, I am still missing the slash. Any idea where that should be added?

If I am manually chaning that f.name to f.stem, I am still missing the slash. Any idea where that should be added?

Without looking at your config I don't know what's causing this.

My config looks like this
repository: https://gitlab.memri.io/memri/pyintegrators
output: web
topnav_title: integrators
site_title: memri integrators
company_name: memri
description: memri integrators, integrating your information
# Set to false to disable KaTeX math
use_math: true
# Add Google analytics id if you have one and want to use it here
google_analytics:
# See http://nbdev.fast.ai/search for help with adding Search
google_search:

host: <IP_ADDRESS>
# the preview server used. Leave as is.
port: 4000
# the port where the preview is rendered.

exclude:
  - .idea/
  - .gitignore
  - vendor

exclude: [vendor]

highlighter: rouge
markdown: kramdown
kramdown:
 input: GFM
 auto_ids: true
 hard_wrap: false
 syntax_highlighter: rouge

collections:
  tooltips:
    output: false

defaults:
  -
    scope:
      path: ""
      type: "pages"
    values:
      layout: "page"
      comments: true
      search: true
      sidebar: home_sidebar
      topnav: topnav
  -
    scope:
      path: ""
      type: "tooltips"
    values:
      layout: "page"
      comments: true
      search: true
      tooltip: true

sidebars:
- home_sidebar

theme: jekyll-theme-cayman
baseurl: /integrators
permalink: pretty

My config looks like this
repository: https://gitlab.memri.io/memri/pyintegrators
output: web
topnav_title: integrators
site_title: memri integrators
company_name: memri
description: memri integrators, integrating your information
# Set to false to disable KaTeX math
use_math: true
# Add Google analytics id if you have one and want to use it here
google_analytics:
# See http://nbdev.fast.ai/search for help with adding Search
google_search:

host: <IP_ADDRESS>
# the preview server used. Leave as is.
port: 4000
# the port where the preview is rendered.

exclude:
  - .idea/
  - .gitignore
  - vendor

exclude: [vendor]

highlighter: rouge
markdown: kramdown
kramdown:
 input: GFM
 auto_ids: true
 hard_wrap: false
 syntax_highlighter: rouge

collections:
  tooltips:
    output: false

defaults:
  -
    scope:
      path: ""
      type: "pages"
    values:
      layout: "page"
      comments: true
      search: true
      sidebar: home_sidebar
      topnav: topnav
  -
    scope:
      path: ""
      type: "tooltips"
    values:
      layout: "page"
      comments: true
      search: true
      tooltip: true

sidebars:
- home_sidebar

theme: jekyll-theme-cayman
baseurl: /integrators
permalink: pretty

Have you tried adding the slash to the end of your base URL? Making it "/integrators/"?
At this point I have no clue if this is the intended way to use nbdev though. GitHub issues are not really the place to discuss this, you might want to try the fast.ai forums for that (I'm on there too)

Yeah could be a stop gap solution for now. Thanks for looking into it. Will make a post on the forum.

Yeah I'll take out pretty' in the yaml. And IIRC you do want a /` at the end of your baseurl.

Thanks, the extra slash + removing the pretty line fixed it. It does result in a "//" ending of my url on the landing page

I actually solved this problem for myself a different way: Before running it through Jekyll, I remove the .html from both docs/sidebar.json and docs/_data/sidebars/home_sidebar.yml like so (in my Makefile):
	perl -pi -e 's/\.html//g' docs/sidebar.json
	perl -pi -e 's/\.html//g' docs/_data/sidebars/home_sidebar.yml

Not recommending this exactly, but it does let you keep pretty urls.


Price-feeder: Add FTX Provider

Summary
We should add the FTX websocket API to the price feeder for additional support of our stablecoin conversions: https://docs.ftx.com/#overview

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Looks like the websocket API might only give us tickers.
Let's rate limit to be sub-30 requests per second and hit their rest endpoint to get candles.
Candles requires Price, Volume, and Timestamp, whereas Tickers require only last trade Price & Volume.


docs: updating path for JS

It seems the develop branch is gone, so the link references.

Thanks for spotting this. The merge request will need rebasing before it can be merged.
As you realise the develop branch is gone. There are multiple references the develop branch which are broken, in docs/js-api.md docs/developes.md and docs/deploy.md.

Closing for: https://github.com/hyperledger/burrow/pull/1303


zip-all does 9e9 iterations on empty list

The min-length gets 9e9 if the the args is empty (seems that there may be other corner cases too).
Actually could work just with min-length = undefined instead of min-length = 9e9.

The documented function signature is

([a], [b], [c], ...) → [[a, b, c, ...]]

so passing undefined is undefined (heh) behaviour to begin with. Other functions also behave nonsensically when passed unexpected arguments.
The current consensus seems to be not to clutter the code with argument-sanity checks.

Shouldn't the signature be (a, [b], [c], ...) → [[a, b, c, ...]] in that case?
And in general, I have to say I'm totally disagreeing with such consensus. Especially in a "prelude" library I think undefined behavior, and especially ones DoSsing the interpreter, is unacceptable.
If this really is the consensus, I think I'll go for something like rambda instead.

To reproduce: empty=[]; zipAll ...empty


litelemnt lifecycle issue

in the litelemnt all the function could be call outside before shadowroot is implement
new= new element
new.call()      // in call you could not query any node in shadowroot!

If you want to access elements inside render method in a lifecycle method like connectedCallback, you just need add a setTimeout and the elements will be accessibles.
Example:
connectedCallback() {
	super.connectedCallback()

	this.initializeRippleEffect()
}

initializeRippleEffect() {
	/**
	 * This function need to be inside a setTimeout
	 * function to access elements after render flow.
	 */
	setTimeout(() => {
		const rippleElements = this.shadowRoot.querySelectorAll('.ripple')

		if (rippleElements.length > 0) {
			rippleElements.forEach(element => {

				/**
				 * Add Ripple effect to selected element.
				 * If the element have `ripple-color` attribute,
				 * the ripple color effect will receive the color
				 * of the attribute.
				 */
				element.onclick = (event) => {
					let X = event.pageX - element.offsetLeft
					let Y = event.pageY - element.offsetTop
					let rippleDiv = document.createElement('div')

					rippleDiv.classList.add('ripple-effect')

					/**
					 * Create style
					 */
					const style =  {
						top: `${Y}px`,
						left: `${X}px`,
					}

					/**
					 * Add created style to rippleDiv
					 */
					Object.assign(rippleDiv.style, style)

					let customColor = element.getAttribute('ripple-color')

					if (customColor) {
						rippleDiv.style.background = customColor
					}

					element.appendChild(rippleDiv)

					/**
					 * Remove the created div
					 * after the effect finish (.88 sec)
					 */
					setTimeout(() => {
						rippleDiv.parentElement.removeChild(rippleDiv)
					}, 900)
				}
			})
		}
	})
}

@danielbarion  it could not change the order call() will before all the lifecycle func
#1 new= new element
#2 new.call() // in call you could not query any node in shadow root!

lifecycle having problem i think.
normal when the element
#1  constructor
..... during this time parent node could not found this element. but it did!....
#2  connectedCallback()
normal order is below
#1  constructor
... any other lifecycle funcs
#2  ready()
#3 call()
but actually is #1 > #3 > #2 !!!

Oh, i got it now, my bad.. sorry for my answer.

For efficiency, LitElement renders its DOM asynchronously. You can use the updateComplete Promise to know when the element has updated and rendered its DOM.
For example:
const el  = new MyEl();
el.updateComplete.then(() => {
  // act on element after it's been updated / rendered.
});

but did the bug solve? the order still not correct!


mapIterable to turn into a normal generator

Current mapIterable
const mapIterable = (fn, x) => (function*() {
  for (const xi of x) yield fn(xi)
})()

This is me not knowing how to use generator syntax. I would like to convert this to function*(fn, x) {...}

I've done this.


Update blaze-http to 0.14.10

Updates org.http4s:blaze-http from 0.14.9 to 0.14.10.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s", artifactId = "blaze-http" } ]

labels: semver-patch

There's about to be an 0.14.11, which we'll want on series/0.20.


Support alternative Emblem.js file extensions

We currently only look for .emblem, but .embl and .em also seem to be used in some projects.

or maaaaybe we should deprecate our Emblem support 😅


https://www.hackerrank.com/challenges/caesar-cipher-1/problem

Closing Issue/Referencing Issue
issue reference (#)
Changes Made In Pull Request

Thanks Mr. Bot


fix(curriculum): Typo in Links and Images lessons

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #54214

Hi @omair-muhammad. Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝


Specify types directive in package.json for TypeScript

This allows the TS language service to automatically pull in types for Preact. This benefits non-TypeScript users as well. If you're using VSCode and just plain vanilla JS, it will pickup Preact's types automatically after installing and provide autocompletion

Beauty! I thought that was already in there.


Fix DDC test html/js_dispatch_property_test Times Out.

Fix test from timing out.

this doesn't run because it's a custom HTML test. See https://github.com/dart-lang/sdk/issues/31577


Sinuous Daggerplay

How this ability work? Is it suppose to be additional tail attack or do I need equip dagger like for Kasatha?


ActiveField::$inputOptions override default widget options

Before 2.0.17 you could set default options for input widget. So if there were no options in config, the options that set in widget by default were used instead. Now, there are always options in config, because inputOptions are added to it. In the inputOptions there is class 'form-control' by default, so in widget config options there is always class 'form-control' too. So now it's not possible to know if the config was empty from the very beginning, because it comes to widget prefilled already.
For example we have widget:
class Datepicker extends InputWidget{
    public function init(){
        parent::init();

        $this->options += [
            'class' => 'datepicker',
        ];
    }
}

We set default options class 'datepicker', so if we call our widget like this:
$form->field($model, 'date')->widget(Datepicker::class);
our widget options property will have class 'datepicker'. But after 2.0.17 the only way to set class 'datepicker' is to call widget like this:
$form->field($model, 'date')->widget(Datepicker::class, ['options' => ['class' => 'datepicker']]);
| Yii version      | 2.0.17
| PHP version      |  7.1

Yii 2.0.17
PHP 7.2.10
I use
<?= $form->field($model, 'date')->widget(DatePicker::class, [
	'type' => DatePicker::TYPE_COMPONENT_PREPEND,
        'options' => ['class' => 'form-date-picker'],
	'pluginOptions' => [
		'autoclose' => true,
		'format' => 'yyyy-mm-dd',
		'language' => 'ru-RU'
	]
]); ?>

and
<?= $form->field($model, 'date')->widget(DatePicker::class); ?>

there is a difference. @posterx #17220

I found a similar problem which I think correlates to this. After upgrading to 2.0.17 or later the "options" property in my DI container definitions are no longer being applied properly. I made a comment in what I realize was the wrong spot here (https://github.com/yiisoft/yii2-framework/commit/9726b1a1a32c12f4629cdfeb2ce5f71c263b14ef#diff-3389dc9760ea4e01ebe04aaa7e9283f3) and I believe this commit (https://github.com/yiisoft/yii2/commit/a8d4f8538e6996a5b1153e714bb7b14e210b30cd#diff-afe28192283fbfadaf6145620191c339) was when the issue began.

@BrianVB  Please show the code of your widget?

The widget I am using is Kartik's Select2 widget (https://github.com/kartik-v/yii2-widget-select2).
The code I am using to call the widget:
echo $form->field($model, 'category_ids')->widget(Select2::className(), [     'data' => $categories_list,     'pluginOptions' => [         'allowClear' => true,         'tags' => true,         'tokenSeparators' => [','],     ] ]);
I am setting the configuration for this widget in a container configuration file I have created.  Using the advanced application template, in common/config/main.php I have:
'
// --- Container definitions for global defaults
$config['container'] = require(DIR . '/container.php');
'
And in container.php I have:
`
 [
       ...
        // --- Default desired configuration for Select2 widget
        'kartik\select2\Select2' => [
            'options' => [
                'placeholder' => 'Select one or more..',
                'encode' => false,
                'multiple' => true
            ],
            'pluginOptions' => [
                'allowClear' => true,
                'tags' => true,
                'closeOnSelect' => false
            ]
        ],
       ...
];
`

The values of the 'options' array are being overridden from my container config. There is more code but this should give you the general idea of what I mean. If there's any other information I can provide please let me know.

workaround
https://gist.github.com/bscheshirwork/36a3aec9a4d66106e6cd4a65eaf6c5ab

I confirm this behavior with Yii 2.0.40, got it noticeable after upgrading from <IP_ADDRESS>.
PHP 7.4.14.
How to reproduce:

Use clean yii2 install
Add MyCaptcha:

class MyCaptcha extends \yii\captcha\Captcha
{
    public $options = [
        'class' => 'form-control',
        'style' => 'background:green'
    ];
}

In contact.php use MyCaptcha in place of Captcha

 <?= $form->field($model, 'verifyCode')->widget(MyCaptcha::className(), [
                        'template' => '

{image}

{input}

',
                    ]) ?>

Results in:
Yii 2.0.16 renders
<input type="text" id="contactform-verifycode" class="form-control" name="ContactForm[verifyCode]" style="background:green">

Yii 2.0.17 and 2.0.40 render
<input type="text" id="contactform-verifycode" class="form-control" name="ContactForm[verifyCode]">

I confirm this behavior with Yii 2.0.40, got it noticeable after upgrading from <IP_ADDRESS>.
PHP 7.4.14.
How to reproduce:

Use clean yii2 install
Add MyCaptcha:

class MyCaptcha extends \yii\captcha\Captcha
{
    public $options = [
        'class' => 'form-control',
        'style' => 'background:green'
    ];
}

In contact.php use MyCaptcha in place of Captcha

 <?= $form->field($model, 'verifyCode')->widget(MyCaptcha::className(), [
                        'template' => '

{image}

{input}

',
                    ]) ?>

Results in:
Yii 2.0.16 renders
<input type="text" id="contactform-verifycode" class="form-control" name="ContactForm[verifyCode]" style="background:green">

Yii 2.0.17 and 2.0.40 render
<input type="text" id="contactform-verifycode" class="form-control" name="ContactForm[verifyCode]">

@yugaego would you be able to prepare a PR for this?

@yugaego would you be able to prepare a PR for this?

I'm working towards the PR.

I'm working towards the PR.


Can't create a SaaS app with oidc inbound protocol config in a sub org

Description:
Create an enterprise login idp in a sub org.
Create a SaaS app as given below. For the user, I have given the org creator of the sub org (user is outside the org). This user has the required permissions to invoke the request in the sub org.
curl --location --request POST 'https://localhost:9443/o/<sub org id>/api/server/v1/applications' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --header 'Authorization: Basic YWRtaW46YWRtaW4=' \ --data-raw '{     "name": "B2B SaaS",     "isManagementApp": true,     "authenticationSequence": {         "type": "USER_DEFINED",         "steps": [             {                 "id": 1,                 "options": [                     {                         "idp": "EnterpriseIDP",                         "authenticator": "EnterpriseIDPAuthenticator"                     },                     {                         "idp": "LOCAL",                         "authenticator": "BasicAuthenticator"                     }                 ]             }         ],         "script": "var onLoginRequest = function(context) {\n   executeStep(1,\n       {\n           authenticationOptions: [{\n               idp: (context.request.params.org && !context.steps[1].idp) ? \"EnterpriseIDP\" : context.steps[1].idp\n           }],\n           authenticatorParams : {\n               common : {\n                   skipIdentifierPreProcess : \"true\"\n               }\n           }\n       },\n       {\n           onSuccess: function (context) {\n               Log.info(\"User successfully completed initial with IDP : \" + context.steps[1].idp);\n               if (context.steps[1].idp === \"EnterpriseIDP\") {\n                   return;\n               }\n           }\n       });\n};\n",         "subjectStepId": 1,         "attributeStepId": 1     },     "inboundProtocolConfiguration": {         "oidc": {             "grantTypes": [                 "authorization_code"             ],             "callbackURLs": [                 "http://localhost:8080/pickup-dispatch/oauth2client"             ]         }     } }'
Got the following 401 unauthorized error.
{     "code": "OAUTH-60003",     "message": "Invalid Request.",     "description": "Error while updating OpenIDConnect configuration. No authenticated user found. Failed to register OAuth App.",     "traceId": "876b48db-7dba-4f59-9dff-4b25ddf9ccda" }
The error seems to be due to the validation at https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/ccc2e5775aba025e9b68970484ba8203b5bef7fd/components/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth/OAuthAdminServiceImpl.java#L240-L242 where the username is not set due to https://github.com/wso2-extensions/identity-carbon-auth-rest/blob/c49eed43fa4ef833b68a4d24979dda22d2fdfb79/components/org.wso2.carbon.identity.auth.service/src/main/java/org/wso2/carbon/identity/auth/service/handler/AuthenticationHandler.java#L102-L109

fixed with https://github.com/wso2/carbon-identity-framework/pull/4117


Update Concept06_saving_variables.ipynb

savers is never defined

Are tutorials restricted to specific version of tf and python?

Python 3 for most of it unless specified otherwise. And, TensorFlow 1.0 or above.

I will double check my code why I had to update from 'saver' to 'savers'


lib/io: set gpio and pwm config api version on usage

They were set to 0 instead of current version.
Signed-off-by: Bruno Dilly<EMAIL_ADDRESS>

+2

merged


Add conditions to transactions

Some of TODOs and missing tests here, but ready for a concept review.

Codecov Report

Merging #56 into master will decrease coverage by 8.37%.
The diff coverage is 31.42%.

@@            Coverage Diff             @@
##           master      #56      +/-   ##
==========================================
- Coverage    94.7%   86.33%   -8.38%
==========================================
  Files          12       12
  Lines         548      622      +74
==========================================
+ Hits          519      537      +18
- Misses         29       85      +56

Impacted Files
Coverage Δ

src/lib.rs
100% <ø> (ø)
:arrow_up:

src/event.rs
54.54% <0%> (-45.46%)
:arrow_down:

src/accountant.rs
78.67% <12%> (-15.82%)
:arrow_down:

src/transaction.rs
76.85% <54.28%> (-20.41%)
:arrow_down:

src/logger.rs
96.87% <0%> (-3.13%)
:arrow_down:

src/accountant_stub.rs
90.58% <0%> (+1.17%)
:arrow_up:

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 dba6d7a...e759bd1. Read the comment docs.


Support NetworkAccessPolicy as part of OSDisk struct

Feature Request

OS disk struct here doesn't contain NetworkAccessPolicy flag which is present part of managed_disk_properties.
Without this, our disks are open to internet with NetworkAccessPolicyAllowAll (applied by default). Though a disk attached to a running VM can't have an export SAS URL. We would like to have an argument which enables us to explicitly apply NetworkAccessPolicyDenyAll/NetworkAccessPolicyAllowPrivate flag to avoid exposure to internet.
In the end, we would need something like below to be added to OSDisk struct::
type OSDisk struct {
  // existing arguments as-is
  // NetworkAccessPolicy - Possible values include: 'NetworkAccessPolicyAllowAll', 'NetworkAccessPolicyAllowPrivate',
  //'NetworkAccessPolicyDenyAll'
  NetworkAccessPolicy NetworkAccessPolicy `json:"networkAccessPolicy,omitempty"`
}

This isn't just for a VM but also for VMSS resources. I'm new to this repo, hence not aware of contributing.
Shall you need more details, please revert to me.
Thanks,
Harsha

@harshavmb Thanks for your feedback. Our SDK is auto-generated by service swagger definition. From computer spec, it seems no related model with your feature. I think it should be a feature request. Could you please open an issue here that our service team could jump to help?

@tadelesh
As asked, I opened an issue here.

Close as it is swagger issue.


How to handle the page "Your connection isn't private" in taiko

To Reproduce
Steps (or project) to reproduce the behavior:

when we open the URL we see the page as Your connection isn't private
So while running the scripts in jenkins we see an issue.

while opening browser also i used:
await openBrowser({ headless: headlessChrome, ignoreCertificateErrors: true, args: ['--no-sandbox', '--start-fullscreen', '--disable-web-security', '--disable-RendererCodeIntegrity'] })

Any suggestions would be an great help?

@saikrishna321 @sriv  Any insight on this Please

Are you able to open this page in chrome? taiko has an option for openBrowser to options.ignoreCertificateErrors which is true by default, but I suspect this error is not related to this setting

yeah @sriv  Earlier the jenkin setup was headless chrome is true when i am unable to handle this certificate. and also i am running my scripts in jenkins
So Now I am trying to run the scripts with headless mode is false,here is my output on jenkins
[runner: 1]   ## TC2 - Book Train & Non D & C EHI Car Rental
Failed to capture screenshot on failure.
Error: Browser or page not initialized. Call openBrowser() before using this API
WARNING: Browser or page not initialized. Call openBrowser() before using this API
[runner: 1]     Error Message: Error: Failed to launch browser!
[0203/045120.618627:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0203/045120.618696:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
Stacktrace:
Error: Failed to launch browser!
[0203/045120.618627:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0203/045120.618696:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)

    at onClose (node_modules/taiko/lib/browserFetcher.js:262:11)
    at ChildProcess.<anonymous> (node_modules/taiko/lib/browserFetcher.js:251:63)
    at ChildProcess.emit (events.js:326:22)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)

@sriv  headless_chrome = false is working fine on my local system.

Sorry, I meant to ask what happens if you open the page outside the script (manually opening the webpage in chrome)?
Make sure you try the same url that your CI is using, some people use different URLs for every environment.
If the webpage's certificate has an issue, there is nothing taiko can do, so I suggest we rule that out first.
On jenkins, to run headless_chrome=false you may need to run it using xvfb.

Some hints on the error are mentioned in Google Chrome's documentation - https://support.google.com/chrome/answer/6098869?hl=en#zippy=%2Cyour-connection-is-not-private-neterr-cert-authority-invalid-err-cert-common-name-invalid-neterr-cert-weak-signature-algorithm-err-certificate-transparency-required-or-ssl-certificate-error

On jenkins, to run headless_chrome=false you may need to run it using xvfb.
What it meant @sriv ? I am not sure about this

xvfb is a virtual frame buffer for the X server. The error you see is because the OS does not have a physical display and the process cannot render any content.
xvfb-run is a utility that can run commands in a virtual display, allowing you to run processes on cloud VMs/containers that do not have a display manager.
See https://github.com/getgauge/taiko/blob/master/.github/workflows/taiko.yml#L108-L114
for an example on how we do this to run taiko's functional tests

I still recommend that you check that your test environment is setup and working properly, I suspect that the original certificate issue is likely an environment issue rather than a problem in your test code or taiko.

Sure @sriv I will check with my team and get back to you


PythonEnvsReducer.resolveEnv() should fall back to wrapped locator.

Current PythonEnvsReducer.resolveEnv() returns undefined if the requested environment is not one provided by iterEnvs().  That means the wrapped locator never gets a chance to resolve the environment.  Instead PythonEnvsReducer.resolveEnv() should fall back to the wrapped locator in that situation.

@int19h

@int19h


A few touchups to 'Adding' hardware

[x] Include an image for the 'Add Board' card
[x] Set the warning hints as alert boxes
[x] Style the schematics a little for appearance

@ganicke, @Jaqster wants to know if we can remove the "add board" image

Sorry, I just don't think that image looks very polished...  Why do we even need an image here?

We don't. I'll take it out.


Fix gp/bo tutorials

This fixes item list rendering of gp/bo tutorials.

@fehiepsi is it OK if i rework the bo tutorial similar to the way i reworked the gp tutorial?

Sure @martinjankowiak, It would be great to me!


[TB] Add focus blur doesn't seem to work

Problem/Concern
If I go to set the Focus State settings and enable "Add focus blur", I would expect to see a blurred box shadow on the textfield when I focus it.  But I don't notice it.
Proposed Solution

The css variable --focusBlur is being set and updated correctly, so it appears to be an issue with the css for the input.

Looked at this some.  The style that is being affected by --focusBlur here is:
"& .MuiInputBase-root.Mui-focused .MuiOutlinedInput-notchedOutline": {
                            border: '1px auto var(--button)',
                            boxShadow: '0 0 var(--focusBlur) 1px var(--button-half)',
 }

The problem I'm seeing here is that "auto" for border is incorrect.  Should probably be "solid".  That is why the border isn't changing color when focused.  The value of var(--focusBlur) is also "4" and not "4px" which is causing the blur not to happen.

The value of "4" for --focusBlur is being set in TB.css.

The border is now correct after adding px unit to --focusBlur.
However, the blur isn't showing for dark mode.

These are the changes that still need to be made, I believe.  Note that the darkmode rule needs to be more specific than what is there otherwise the lightmode rule will trump it.  It is also very hard to see the blur in darkmode unless you make it white.  But I'll leave it up to Lise to determine what the issue is there.  Not enough contrast in dm-button?  Or is that not the correct CSS variable to use now?  Dunno.
diff --git a/code/src/ui/src/mui-a11y-tb/themes/Theme.css b/code/src/ui/src/mui-a11y-tb/themes/Theme.css
index ee73f32..dd3d885 100644
--- a/code/src/ui/src/mui-a11y-tb/themes/Theme.css
+++ b/code/src/ui/src/mui-a11y-tb/themes/Theme.css
@@ -2096,8 +2096,8 @@ button.MuiPaginationItem-root:hover {
   background: var(--dm-surface);
   color: var(--dm-on-surface);
 }
-.darkmode .MuiOutlinedInput-notchedOutline fieldset::focus {
-  border: 1px auto var(--dm-button);
+.darkmode .MuiInputBase-root.Mui-focused fieldset.MuiOutlinedInput-notchedOutline {
+  border: 10px solid var(--dm-button);
   box-shadow: 0 0 var(--focusBlur) 1px var(--dm-button-half);
 }

diff --git a/code/src/ui/src/mui-a11y-tb/themes/Theme.jsx b/code/src/ui/src/mui-a11y-tb/themes/Theme.jsx
index c444d00..1615b5c 100644
--- a/code/src/ui/src/mui-a11y-tb/themes/Theme.jsx
+++ b/code/src/ui/src/mui-a11y-tb/themes/Theme.jsx
@@ -313,7 +313,7 @@ try {
                           },
                         },
                         "&.Mui-focused .MuiOutlinedInput-notchedOutline": {
-                            border: '1px auto var(--button)',
+                            border: '1px solid var(--button)',
                             boxShadow: '0 0 var(--focusBlur) 1px var(--button-half)',
                         },
                         "& fieldset": {
@@ -522,7 +522,7 @@ try {
                             color: "var(--on-input-disabled)",
                         },
                         "& .MuiInputBase-root.Mui-focused .MuiOutlinedInput-notchedOutline": {
-                            border: '1px auto var(--button)',
+                            border: '1px solid var(--button)',
                             boxShadow: '0 0 var(--focusBlur) 1px var(--button-half)',
                         },
                     }


Updated node versions on travis and changed some package versions

Enables build for newer node versions

thanks @lordnox


update rust toolchain file

update the stable Rust version to a recent version

I've been keeping this synced with smoldot https://github.com/ermalkaleci/smoldot/blob/2a9dc99e65f3c47d950c50ca0fbe052bb463ca67/.github/workflows/ci.yml#L42


Code refactoring according to 2023 Anonymous Types video

Contributes to: #296

@szylviaaa: it is done - thanks for your contribution,


nodes that start and end in a single block

eg : <link href='http://fonts.googleapis.com/css?family=VT323' rel='stylesheet' type='text/css' />

@agarwalayush dekh liyo be yeh bhi

solved


Updating dependencies to React v15

This updates react, react-dom, and react-addons-test-utils dependencies to 15.0.0.
It also changes line 21 in the README to indicate that 0.2.x works with both React 0.14.x and React 15.0.x.
No console warnings, and all tests pass:

Slight update to widen peerDependency support. Could we get this merged in soon?

Thanks @thathenderson. I'll take a look right now.

:rocket:


Does not show up after install on Windows 10?

Hi Greg! I followed the steps to install on Windows 10, but I don't see anything when I "Refresh plugins" in KiCad.
The menu is just blank there.
Here you can see where it is installed. Are there any other steps to get it to appear?

Thanks,
George

It should be inside the scripting directory. Also best way to make sure plugins are reloaded is to close KiCad and start it again, and not just eeschema or pcbnew, the main KiCad window.

Great - that works perfectly now!


[feature suggest] add a function goquery.NewDocumentFromString

i notice that there are function NewDocumentFromResponse, function NewDocument, function NewDocumentFromReader, function NewDocumentFromNode. I think they are well designed.
i hope to discuss whether it is good to add a function NewDocumentFromString(str []byte) goquery.Document, this function can transfrom the []byte to a Document object.

i find some problem is same with me, sorry to disturb.


interpreting coord checks

Hi there, I'm working on a flax port of this and I'm trying to use the coord check scripts on a variant of your MLP example to see if I've done it right. I'm struggling to interpret the results though:

The point I'm confused on is the green line in the muP graph step 1: if I understood your paper correctly, this should be a flat line right?
Looking through my code, i can't spot the mistake though, so I must ask, is my assumption about step 1 of the coord check wrong?

Hi! Does the green curve correspond to the last layer? If so, this is expected. It is for a related reason that we recommend initializing the last layer weights to zero.

Aah I see. Yes it is for the last layer. Thanks


Web Developement Project

Creating a Local Gym Page using HTML and CSS

I have Created one Landing Page of a Local gym using basic developement languages like HTML and CSS

@MOUSAM-AGARWAL while creating PR please follow all the Contribution Rules which are mentioned in the issue #43 .