Session store not set on request

Hi,
I'm receiving the bellow error messagem when trying to load : php artisan ide-helper:generate
[RuntimeException]
Session store not set on request.

I'm having the same issue when I try to login or to make an AJAX request. I think it's not 'ide-helper' related problem, but it is the Session configuration itself. However, I'm not able to solve it.

@icemanblas hi, thank for the feedback. Yes, maybe its not about ide-helper. I'll look for Session problems.

Did you find a solution?

Also having the same issue (just upgraded to Laravel 5.2) and can't seem to find a solution.

In my case, I simply created fresh project and imported all custom files manually. This is not of any help, but that's just what i did. That was a few months ago.
Recently, while browsing, I came across some article which said the problem is related to the routes.php file and the way middleware is used within some routes (Laravel 5.1). Sorry, can not provide link or details, just a guidance where the problem lays.
While this is not a good answer or solution, it might be of some help.

I narrowed it down to having Request::session() in app/Providers/AppServiceProvider. Still not sure how to fix it though. It should be using the normal global middleware defined inapp/Http/Kernal.php -> $middleware right?

I don't think this is related to the ide-helper at all

Yep, i think your right. I remember getting the error on other artisan commands as well. Still not sure what's causing this though.

Any solution on this issue ?

I also don't think it's related to ide-helper.
Can someone put a public repo which reproduces the problem?


fuzzing: run latest fuzzers in OSS-Fuzz

Signed-off-by: AdamKorcz<EMAIL_ADDRESS>Builds the recently added fuzzers in OSS-Fuzz.
Run latest fuzzers in OSS-Fuzz

Friendly ping :wave:


We lost our website footers

Current it is:

What it should be:

We need to find out which part was wrong (and introduced from which PR) so that we could be able to fix it.

before this issue timestamp，everything is fine

Thank you @qhduan for fixing this problem!
We now have our footer again, cheers!


Update cosmos to latest version

High Level Description
Include recent changes made to cosmos:

Update documentation (https://github.com/dcos/cosmos/pull/633)
Add describe response v3 (https://github.com/dcos/cosmos/pull/636)
Update README (https://github.com/dcos/cosmos/pull/638)
Bug fixes and improvements for uninstall (https://github.com/dcos/cosmos/pull/637)

Related Issues

DCOS-15881 Update cosmos and cosmos-ee documentation
DCOS-15084 Update DescribeResponse to be a PackageDefinition
INFINITY-1686 Rapid, concurrent uninstalls fail
INFINITY-1691 Force Marathon update for uninstall

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: tests are in the cosmos repo
[X] Read the DC/OS contributing guidelines
[X] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[X] Change log from the last version integrated (this should be a link to commits for easy verification and review): changelog
[X] Test Results: link to CI job test results for component
[X] Code Coverage (if available): link to code coverage report

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot label Ready For Review

@jsancio @spahl please review!


Ixia-Chassis-Shell 1.2.0-PREVIEW release is not working

The ixia_chassis_shell.zip for the Ixia-Chassis-Shell 1.2.0-PREVIEW release contains a bad driver that has:
def initialize(self, context):
    """
    :type context: cloudshell.shell.core.driver_context.InitCommandContext
    """

    self.logger = tg_helper.get_logger()
    self.handler.initialize(context, self.logger)

It is missing the context parameter in the get_logger() call.

The driver also contains the .idea directory and .pyc files.

Hi @shmir ,
I think we can close this issue since there are a lot of packages that were released later, with a fix.
Also, we might need to hide Ixia-Chassis-Shell 1.2.0-PREVIEW release.
What do you think?
Thank you,
Costya

Ixia-Chassis-Shell 1.2.0-PREVIEW release removed


API server hostname in kubeconfig contains a trailing dot

The server URL in the kubeconfig we generate for admins contains a trailing dot:
- name: johannes-test-cluster
  cluster:
    server: https://johannes-test.<redacted>.net.:6443

This is due to the fact that we use the same Terraform variable for creating Route 53 records (in which case the trailing dot does make sense) and for generating the kubeconfig file.
This doesn't seem to affect things technically, but we may want to fix this nonetheless.

Fixed in https://github.com/kinvolk/lokomotive/pull/422.


allow for configurable openstack storage class

Template the openstack storage class so that it allows configuration of multiple storage classes that can be mapped to different cinder volume types.

I have signed the CLA.

Have also verified my github email.

I have tested this PR on a test cluster it worked as expected.
The following group_vars:
persistent_volumes_enabled: true
storage_classes:
  - name: hdd
    is_default: true
    parameters:
      availability: nova
      type: HDD
  - name: ssd
    parameters:
      availability: nova
      type: SSD

resulted in:
kubectl describe storageclasses
Name:            hdd
IsDefaultClass:  Yes
Annotations:     storageclass.kubernetes.io/is-default-class=true
Provisioner:    kubernetes.io/cinder
Parameters:     availability=nova,type=HDD
ReclaimPolicy:  Delete
Events:         <none>

Name:            ssd
IsDefaultClass:  No
Annotations:    storageclass.kubernetes.io/is-default-class=false
Provisioner:    kubernetes.io/cinder
Parameters:     availability=nova,type=SSD
ReclaimPolicy:  Delete
Events:         <none>

Looks good to me.

ci check this

I don't understand why GitLab CI says
$ /bin/sh scripts/premoderator.sh
User does not have permissions to start CI run

@woopstar please consider to merge this

Is there something stopping this from being merged?

Maybe @riverzhang can help us get the CI job running


Amend pre-script sequence titles

The pre-script sequence titles looked a bit incorrect, so I've neatened them
up a bit here. There are no content changes, only aesthetic/grammar ones.

Thank you for contributing to openstack/packstack!
openstack/packstack uses Gerrit for code review.
Please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


IBM Sterling Configure Price Quote Software v<IP_ADDRESS>

Chart ibm-cpq-prod-4.0.1.tgz added. This is our Continuous Delivery release for Chart version 4.0.1 for product CPQ.
Please go ahead and merge ASAP.
Once merged we would be re-testing and send notification.
Thank you

<EMAIL_ADDRESS>Please address checks failed issue ASAP.
Thanks


NonlinearSolvers: self.F.owned_local ValueError->AttributeError

mini PR, following #771:
ValueError changed to AttributeError (otherwise error message does not show up)

Merging as only 2 lines were changed and it should be harmless changes, the Travis check error is due to failure at cloning air-water-vv:
$ cd erdc/proteus
$ git checkout -qf b0c4270dd24b350469cf2c587cd4b098778a95bf
$ git submodule update --init --recursive
Submodule 'air-water-vv' (https://github.com/erdc/air-water-vv.git) registered for path 'air-water-vv'
Cloning into '/home/travis/build/erdc/proteus/air-water-vv'...
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated


No option for unlimited time control

Just wondering if an unlimited time control when creating challenges is going to be implemented in the future? Unless it already has been and I've missed something.

I don't think it is possible to create an unlimited time control game with the Lichess API,
so unless Lichess adds an option to do that it won't be possible to add it to any of the client libraries (such as berserk and chariot etc).
The currently slowest time control which the Lichess API (and chariot) allows to set when creating a challenge is 14 days per move.
(I think the "unlimited" time control which is available only on the web site, i.e not via API, is actually implemented as 21 moves per day, but I might be misremembering)

Ah I see
I had been making unlimited time control games vs the AI with the API just by omitting all of the time control fields and I thought it'd be the same for seeks and challenges, though that doesn't seem to be the case
Thanks for letting me know!


Git master branch and PyPi Inconsistent

I tried installing metric-learn package via pip install metric-learn.
This seems to install an inconsistent version with what I see on Git.
Some examples of the differences is that the PyPi version of BaseMetricLearner class
doesn't inherit from the 'TransformerMixin' class.
Also, the PyPi version of BaseMetricLearner's 'transformer' method transforms by the inverse of the cholesky decomp of matrix M vs. the Git version shows it without the inverse.
Am I installing this the wrong way? It seems that running with the git version gives me more intuitive results/use of methods.

We've been making a lot of progress on the library and plan to push a new point release soon (gh-71), but we haven't gotten there yet.
For now, installing from the master branch is a good idea.

Thank you very much this is really helpful - would you have a rough estimated timeline of the new release?


DNS errors when using cradle with both hostname and IP address

Having a problem when using cradle with any hostname or IP address. Oddly enough, the errors are always DNS related, which doesn't make a whole lot of sense.
When using a hostname (including localhost), the following error occurs:
events:12
        throw arguments[1];
                       ^
Error: ECONNREFUSED, Could not contact DNS servers
    at IOWatcher.callback (dns:52:15)
    at node.js:773:9

When using an IP address (including <IP_ADDRESS>), the following error occurs:
events:12
        throw arguments[1];
                       ^
Error: ENOTFOUND, Domain name not found
    at IOWatcher.callback (dns:52:15)
    at node.js:773:9

At first I thought that the errors might be with the CouchDB installations so I tried two different ones (local and remote) and cradle fails with both of them. Cradle has been run from both a Mac and Linux box and same failures occur. Additionally, I have tested with save operations, as well as info() requests on both the db and server objects. This has been confirmed with dbs both requiring and not requiring authentication. Node is able to make HTTP requests using the regular HTTP libraries without an error.
The following code demonstrates usage (just replace localhost with any ip or remote hostname):
var cradle = require('cradle');

var couch = new(cradle.Connection)('http://localhost', 5984, {
    cache: true,
    raw: false,

});

var db = couch.database('scratch');

setInterval( function () {
    console.log(db.info());
    console.log(couch.info());
}, 1500);

Since these errors don't make a whole lot of sense, it's tough for me to figure out what the issue is. If there is any additional information with which I might provide you, please let me know. Thanks!

I'm getting similar issues using<EMAIL_ADDRESS>ECONNREFUSED when using a domain name.

I'm getting similar issues using<EMAIL_ADDRESS>ECONNREFUSED when using a domain name.


Update community-plugins.json

Added a plugin!
lfg

Had to revert this for now, Please follow instructions here, happy to accept a pull request with revised the version @Marvy101

why was this reversed? what part of the instructions did I not follow?
Best,
Dada
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
06/03/24,
03:11:37 AM
On Mon, Jun 3, 2024 at 3:07 AM Akshay Narisetti @.***>
wrote:

Had to revert this for now, Please follow instructions here
https://docs.basedhardware.com/developer/Plugins, happy to accept a
pull request with revised the version @Marvy101
https://github.com/Marvy101
—
Reply to this email directly, view it on GitHub
https://github.com/BasedHardware/Friend/pull/202#issuecomment-2144801586,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV3DYC4TNF35TJ6Q3FNTR3TZFQ543AVCNFSM6AAAAABIUVDR62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBUHAYDCNJYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Your prompt contains "asking questions about their day", which implies back and forth communication. Have a look at https://docs.basedhardware.com/developer/Plugins/#bad-prompt-example for more info.

updated it!
Best,
Dada
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
06/03/24,
11:48:40 AM
On Mon, Jun 3, 2024 at 3:33 AM Akshay Narisetti @.***>
wrote:

Your prompt contains "asking questions about their day", which implies
back and forth communication. Have a look at
https://docs.basedhardware.com/developer/Plugins/#bad-prompt-example for
more info.
—
Reply to this email directly, view it on GitHub
https://github.com/BasedHardware/Friend/pull/202#issuecomment-2144854512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV3DYC7STXRSS2ZDW5C57MDZFRBAFAVCNFSM6AAAAABIUVDR62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBUHA2TINJRGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

You should open a new pull request, thanks!


Empty content while using whatsapp single share.

Hi
This is how I am trying to use single share for whatsapp.
whatsappInvite(){
  let shareOptions = {
	title: "YO",
	message: "Join me in this game",
	url: "www.google.com",
	subject: "Join me in this game" //  for email
  };
    setTimeout(() => {
      Share.shareSingle(Object.assign(shareOptions, {
        "social": "whatsapp"
      }));
    },300);
}

This successfully opens the whatsapp app to select the people i want this to send to. But when i select the person I want the content send to in the next screen the content is null. There is absolutely nothing.
General Share works fine though,
Look at the picture below for the result of above code.

In RNShare/social/WhatsAppShare.m file
Replace the below code and see if this works.
NSString *text = [RCTConvert NSString:options[@"message"]];
text = [text stringByReplacingOccurrencesOfString:@":" withString:@"%3A"];
text = [text stringByReplacingOccurrencesOfString:@"/" withString:@"%2F"];
text = [text stringByReplacingOccurrencesOfString:@"?" withString:@"%3F"];
text = [text stringByReplacingOccurrencesOfString:@"," withString:@"%2C"];
text = [text stringByReplacingOccurrencesOfString:@"=" withString:@"%3D"];
text = [text stringByReplacingOccurrencesOfString:@"&" withString:@"%26"];
NSString * urlWhats = [NSString stringWithFormat:@"whatsapp://send?text=%@", text];
NSURL * whatsappURL = [NSURL URLWithString:urlWhats];

Please append option url string with the text string if needed.


RT2.7 isis_interface_passive_test.go

Initial commit for RT2.7
It resolves #1615

Pull Request Functional Test Report for #1807 / ada5daf71c8f14422d87923db1cfca34e8e3189c
No tests identified for validation.
Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
111 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.9%) to 46.627%

Files with Coverage Reduction
New Missed Lines
%

topologies/binding/binding.go
44
39.56%

topologies/binding/options.go
67
33.99%

Totals

Change from base Build<PHONE_NUMBER>:
-0.9%

Covered Lines:
1341

Relevant Lines:
2876

💛  - Coveralls


Add probuilds.net

I'm a bit lost of what information people would find useful in this. I've had probuilds requested many times but am I just to bring in the last played items? Show the most popular?

I'm not entirely sure myself. I think you could just scrape the 6 most popular items along with the most popular boots. However, one of the big selling points of probuildes (IMO) is that it shows you the order in which items were built. However, this is something that is more difficult to showcase for several reasons
For starters, you don't know which lane the champion was in. With the ever increasing amount of flex picks, it's very important to figure out who goes where. If a team has Naut, Graves, and Trundle, who is going where? The items built will be different.
Secondly, it's very much dependent on the player shown. Look at Graves. The three player this week with completed item builds are Kirei, Spirit, and Dardoch. Each of them got a different jungle item. This is very context dependent due to the play style of the player and the team that they had. Also, the item path would change based on how your team is doing.
Personally, I don't think probuilds is that useful because it's too context dependent. There's not a large enough data set with aggregated info to make it worth using - especially for something like championify. If probuilds did something where it kept track of a player over a long period of time and gave all the champions he played with data on item builds and such, then it would be more helpful (and also less helpful ~ think about how many pros there are). Just my thoughts.

I would really love some probuilds to be added to this. Even if it's context based it would still be nice to be able to quickly see what popular items are on the champion you're playing. You can also attempt to assume what lane they went based on the team comp.
Show most popular items, and most recent highest KDR final build.
I will probably be able to code something for this in javascript/nodejs/python/php (maybe). But sadly I don't recognize the structure you're using.

@LuaTenshi If people feel just the popular items would be useful, then I'll gladly implement it. :)

How about showing the most recent highest KDR final build as well?
I (mostly) made a script that will do the above as well as get the most popular items. The only problem is that it doesn't really output stuff in the correct LoL build format so it's not a simple copy+paste or download into folder thing. That and it uses JQuery because plain Javascript is painful.

I've already integrated probuilds and it'll be out in the next release. I can look into adding KDR too.

Hi, Currently for probuilds.net the program show this:

Popular Items ----> (Core Items)
Popular Boots ----> (Boots)
KDA               ----> (Top KDA Items)

because the most important data on probuilds.net web site is Recent Final Builds for every champion,
my suggestion is:

show 6 Recent Final Builds because this is the most important data and builds that any player could have from this site.

calculating KDA from Live Feed section of the web site, isn't the best method because sometimes game take only 10/15 min and program select 2/0/3 compare to 5/2/5. I think its better to
A) select best KDA from Recent Final Builds
B) select another calculation method for KDA from live feed
C) completely remove KDA and change it with Recent Final Builds

Thanks, You are the BEST 💯 🥇

@Firefoxin Feel free to open a new issue for better tracking.


Add an integration test setup

We should be able to test udfs using integration test setup.
Possible requirements:

Setup automated Exasol docker that upload jar to bucketFs
Setup s3 (gcs, azure) docker instances
Perform write <-> read operations

Too much effort.


Avoids emitting the same output from multiple processes of the same process pool

It uses a shared set of (line: [u8], occurences: u32) to avoid emitting lines that has been emitted by other processes already.
It still supports emitting the same line multiple times from one process.
The shared data might be later used for showing logging from a worker pool. It contains the merged output of all processes.
Fixes WEB-489

Why did you merge this with 0 approvals and 1 request for change?


HHH-10795 StatefulPersistenceContext.entityEntryContext does not work properly for ManagedEntity associated with a different StatefulPersistenceContext

In particular it:

reverts the fix for HHH-10251 so that the ImmutableEntityEntry provides the PersistenceContext;
adds a test case that reproduces some of these issues;
properly checks (within the constraints of the SPI) if the ManagedEntity is associated with the expected PersistenceContext, and responds appropriately;
removes support for reference caching for enhanced immutable entities.

I'm closing this since we need to support reference caching ManagedEntity objects.


prevent raw SQL usage in API

Is your feature request related to a problem? Please describe.
currently It is possible to run raw SQL queries in an External API Connection or a Custom Action.
https://stackoverflow.com/questions/14824453/rails-raw-sql-example
Describe the solution you'd like
in app/models/concerns/safe_executable_validator.rb prevent usage of:

Activerecord::Base
*.find_by_sql
Rails

to be clear, raw SQL means complete SQL statements not fragments like this: https://guides.rubyonrails.org/active_record_querying.html#array-conditions


Toogle

Toggle Not Working Properly , How To Solve It.

Toggle Not Working Properly , How To Solve It.

You could start by providing an adequate bug report: https://github.com/twbs/bootstrap/blob/v4-dev/CONTRIBUTING.md#bug-reports

Closing until we hear back with a more specific question.


Remove deprecated code

Remove deprecated code, those who still use it have had ample opportunity to switch to the newer implementation, and if they have not done so yet, they will do it only when removed.

Resolved by 5eebfbe7ea365d40322589c7b1fedf16e6618663


Mobile player

Deployed to: http://dev.quranicaudio.com:33152

Deployed to: http://dev.quranicaudio.com:33153

Deployed to: http://dev.quranicaudio.com:33154


How many iterations of questions will it ask?

I am wondering where the setting which simulates a conversation between a Wikipedia writer with a specific persona and an expert ? How many iterations of questions will it ask ? Where is that setting in the code?
In practice, we limit the conversation to at most M rounds
Is this the one?
max_conv_turn: int = field(
default=3,
metadata={"help": "Maximum number of questions in conversational question asking."},
)

Your understanding is correct.
We control the STORMWikiRunner with STORMWikiRunnerArguments. You can find more information there.

Thank you, another question, how does the relevant question is generated as I am unfamiliar with dspy?

Could you clarify on "relevant question"? Do you mean how the question is generated for perspective guided QA?

Thats correct, is it defined in dspy.dsp.HFModel?

@ferrygun It is defined by max_conv_turn in STORMWikiRunnerArguments. Each conv turn contains one question been asked by "Wiki writer" role and one corresponding answer by "expert" role.


How did GoLang rewrite work for you?

How long did your rewrite take.  How much faster is it now?
Just curious if I should learn Go ;)

This project is pretty simple so it only took an hour, it doesn't do any intensive work so the speed doesn't matter now, the Node version is also fast cause it doesn't use any dependencies, but when the project gets bigger, the difference will show.
Overall Go is a nice replacement for building CLIs, GoReleaser makes it trivial to distribute Go binaries on GitHub releases or Homebrew, that's one reason I didn't go for Rust. Another reason is the Go compiler is so fast, it makes writing code a joy 🥶

that's one reason I didn't go for Rust

You read my mind for my next question. ;)
Good point about GoReleaser; was thinking of making small utilities in [Vlang}(https://vlang.io/).
Thank you for responce!


SAP Business One Hardware Requirements Guide Link broken

Link is broken for "SAP Business One Hardware Requirements Guide."

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

ID: c88fe88b-64af-eafa-60fa-4bdce1a47f9a
Version Independent ID: c2ae11b3-fdbe-5e9b-b439-ab5006653000
Content: SAP Business One on Azure Virtual Machines
Content Source: articles/virtual-machines/workloads/sap/business-one-azure.md
Service: virtual-machines-linux
GitHub Login: @msjuergent
Microsoft Alias: juergent

@win2000b
Thanks for bringing this to our attention. We are working towards fixing this and will get back on this.

I corrected the link. PR is merged already

@msjuergent Thanks for updating the doc for fixing the link.

@win2000b The doc is updated now, I am proceeding to close this issue.
Hope the provided information is helpful.
If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.


WIP: Re-gen of visrec to automate post-gen updates

Summary
This is a partial re-gen of the visrec service using the latest apex generator which includes the new "visrec" feature.   This should avoid the need for the manual post-gen changes for the visrec service in the future.
This PR is not intended to be merged into the master branch.  Instead, we can just use this PR as a way to verify the changes to the generated code.

Closing as this has been added to the latest release


Using FormKit from a CDN

Reproduction
https://gist.github.com/mdixon4/b6a4f50844660374f90186d43deef88e
Describe the bug
When attempting to use formkit via CDN esm build, the error Unknown input type "text" is thrown.
It is not just text types, choosing a different type (e.g. textarea or even form) gives the same error (e.g. Unknown input type "form")
A full stack trace is below:
Uncaught Error: Unknown input type "text" ("name")
    at v (+esm:7:1134)
    at ve (+esm:7:8634)
    at setup (+esm:7:6811)
    at callWithErrorHandling (vue.esm-browser.js:1682:22)
    at setupStatefulComponent (vue.esm-browser.js:8486:29)
    at setupComponent (vue.esm-browser.js:8442:11)
    at mountComponent (vue.esm-browser.js:6364:13)
    at processComponent (vue.esm-browser.js:6339:17)
    at patch (vue.esm-browser.js:5942:21)
    at ReactiveEffect.componentUpdateFn [as fn] (vue.esm-browser.js:6479:21)

Environment
• OS: Windows
• Browser: tested on edge and firefox
• Version: same behavior in 1.0.0-beta.4 and 1.0.0-beta.5-bd20073 (@next)

@mdixon4 this is a super annoying issue with browser-based ESMs right now. I'll do my best to explain since it can be a real gotchya in general:
Basically, what is going on is @formkit/vue requires vue — pretty self explanatory, but there are some places where id does things like import { inject } from 'vue'. In a build environment, your build tool knows to use the version of vue that is part of the project in node_modules (as long as it is within version constraints) — but when loading in the browser from an ESM how does it know how to resolve "vue"?
Well — they try to "guess" basically, but if they guess a version that is not the exact version of vue you are using in your project — then you have 2 instances of the Vue module. So in your case the createApp() you called was done on a different instance of the Vue module than @formkit/vue imported. So when it tries to use your plugin configuration (include inputs) it finds none, because the plugin was registered on a different module — thus you get errors like "Unknown input".
If you take a look at @formkit/vue ESM that JSDelivr created: https://cdn.jsdelivr.net/npm/@formkit/vue/+esm you'll find this line jammed into the minified code:
import{defineComponent as b,getCurrentInstance as g,watch as h,watchEffect as k,reactive as j,h as $,inject as S,provide as O,onUnmounted as x,ref as A,markRaw as C,computed as w,createTextVNode as V,resolveComponent as<EMAIL_ADDRESS>
So there is the culprit — your code is loading a different version of vue than JSDeliver's version. Now here's where things get really crappy — JSDelivr's (or unpkg etc) version Vue as an +esm doesn't work because it doesn't know to use the browser-based version of vue 😔
There really seems to be no great way to do full esm's in the browser if they have peerDependencies — except for using an import map which is not supported in any browser except chrome. Fortunately Guy Bedford wrote a polyfill for import maps.
Here's your gist forked with a working version:
https://gist.github.com/justin-schroeder/e7540c3bbc76526695d90b49f0c6c01e
Frankly — I'm not entirely sure how we can improve this 🤔 but open to suggestion. One thing we can definitely do is ship a browser-friendly version of FormKit minified into a single ESM, but that doesn't solve the peerDependency issue

Hi @justin-schroeder, thanks for taking the time to explain so clearly. I can see it's a tricky problem. The import map solution works well. ✅
I can't figure out how to make it work using esm.sh though. I get a 500 error with the second URL here, but not sure what's wrong. But anyway, that's outside the scope of this project - but I'd mention it here in case anyone comes along with a working esm.sh setup.
import { createApp, reactive } from<EMAIL_ADDRESS>// This URL gives a 500 error:
import { plugin, defaultConfig } from 'https://esm.sh/@formkit/vue?alias=vue:vue@3/dist/vue.esm-browser.js&deps=vue@3'

Thanks again for your help!

There's still not a great way to do ESM imports, but this gist can serve as a helpful guide for future explorers: https://gist.github.com/justin-schroeder/e7540c3bbc76526695d90b49f0c6c01e


Fix: JS tree shaking

Description
This PR aims to solve tree shaking issues as described in #37575 issue.
Motivation & Context
I created a little demo here with a detailed README to show the problem I'm experiencing with the current version of Bootstrap and a possible solution using a patched version of the library. Basically I can't get tree shake working on my project unless I change the way you create the esm file (single index.esm.js and then a single file for each component, e.g. src/alert.js, src/tooltip.js)
Type of changes

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

Checklist

[X] I have read the contributing guidelines
[X] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-{your_pr_number}--twbs-bootstrap.netlify.app/

Related issues
Fixes #37575

Thanks for this PR @astagi. We haven't looked at it yet but could you please remove the modifications in dist/js? It's going to be generated/built when we'll make the release.

Chances are this is not needed at all. We ship index.esm.js after 5.3.0
alpha 1, doesn't this work for you?
On Tue, Dec 27, 2022, 19:18 Julien Déramond @.***>
wrote:

Thanks for this PR @astagi https://github.com/astagi. We haven't looked
at it yet but could you please remove the modifications in dist/js? It's
going to be generated/built when we'll make the release.
—
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/pull/37733#issuecomment-1366056649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVLNJ7TV5T4AWH3KMXFO3WPMQE3ANCNFSM6AAAAAATKSRPXA
.
You are receiving this because your review was requested.Message ID:
@.***>

Thanks for this PR @astagi. We haven't looked at it yet but could you please remove the modifications in dist/js? It's going to be generated/built when we'll make the release.

Sure @julien-deramond just removed and forced update.
@XhmikosR do you mean bootstrap.esm.js? I don't think is needed, that's why I removed it from build scripts. The remaining structure will be
dist
- js
-- index.esm.js
--src
---- alert.js
---- tooltip.js

I don't think we need another JS dist file. For package users, using src/index.esm.js should be enough. Have you tried it with specify bootstrap/js/src/index.esm.js?
When the ESM files were introduced, we only targeted browser users and we shouldn't introduce any breaking changes.

I don't think we need another JS dist file. For package users, using src/index.esm.js should be enough. Have you tried it with specify bootstrap/js/src/index.esm.js?
When the ESM files were introduced, we only targeted browser users and we shouldn't introduce any breaking changes.

@XhmikosR haven't tried using src/index.esm.js directly, I usually compile everything using Rollup and its plugins and put generated files and maps in the dist folder. I agree with you, in this case it's the same files structure you have in src.. I don't know if using src/index.esm.js directly is the correct way, in that case src/index.esm.js file should be referenced in package.json as module alongside the sideEffects (this property actually activates tree shaking).
I'm curious to try modules in browsers, I usually bundle everything in a single js files using modules from packages, anyway I don't think things would change: imho using a single esm file with class declarations and code to initialize components can't be optimized in any way.

@XhmikosR another thing that concerns me: using src/index.esm.js directly as a module would skip all the Rollup plugins chain such as Babel.. any idea on this?

@XhmikosR @julien-deramond I made some tests (here with my version supporting tree shaking and here with the current Bootstrap version) and yes, the old bootstrap.esm.js file looks to be optimized for browsers! I will restore it alongside index.esm.js file that should correctly be referenced in package.json alongside sideEffects to make tree shaking work using Webpack or Rollup. The only thing I needed to do is using an import map for Popper.js
<script type="importmap">
    {
        "imports": {
            "@popperjs/core": <EMAIL_ADDRESS>        }
    }
</script>

Do you know why I get this different behavior? There are some optimization made by browser that bundler like Webpack or Rollup can't do by default?
By my side I'll restore old ESM build asap and use a different variable to build modules for tree shaking.

@XhmikosR @julien-deramond I've just force updated this branch, I made some tests and as @XhmikosR suggested, using only "js/index.esm.js" as module everything works as expected (Luxon library uses this approach as well). Now we have

dist/bootstrap.esm.js (and minified version) for browser usage.
js/index.esm.js as module for Webpack, Rollup etc.. with sideEffect set to false to enable tree shaking.

Here you can find my demo updated with this configuration to see things in action! Same results, no breaking changes, no file touched/added in dist folder.

Unfortunately, it is still a breaking change because the now referenced file is not passed through babel.
That's why I only decided to include the js/index.esm.js for people to manually reference it when they build Bootstrap. For browser-ready builds only the dist file can be used like before.
We need to revisit our bundles in v6 and see what we are shipping. And also, remove the dist files from the repo and later see if we can split our CSS and JS into separate packages.

Unfortunately, it is still a breaking change because the now referenced file is not passed through babel.
That's why I only decided to include the js/index.esm.js for people to manually reference it when they build Bootstrap. For browser-ready builds only the dist file can be used like before.
We need to revisit our bundles in v6 and see what we are shipping. And also, remove the dist files from the repo and later see if we can split our CSS and JS into separate packages.

Sorry @XhmikosR what do you mean with "the now referenced file"? Index.esm.js? It doesn't need to be passed through Babel, is something that should be used with bundlers like Rollup or Webpack and is up to users to make it pass through Babel for the final bundle in their project configuration.. this is the same approach used by Luxon and it's the correct way.. the old bootstrap.esm.js that passes through Babel is the file that can be used in browsers, if you reference this file inside module it won't be tree shaked and this will impact on the final bundle size..
Let me also add that I don't know how many users are using that module directly in browsers, I followed the documentation to use Bootstrap with Rollup.js using import syntax, that's the only thing I found about modules and following the documentation I discovered that tree shaking was missing.

@XhmikosR I can confirm that I don't have any breaking with my modification. I tried using the module in a html page
    <script async type="module">
        import { Alert, Tooltip } from 'bootstrap'

        const alert = new Alert(document.getElementsByClassName('alert')[0])

        setTimeout(() => {
            alert.close()
        }, 5000);

        document.querySelectorAll('.ttp').forEach(el => {
            new Tooltip(el);
        });
    </script>

I'm forced to use an importmap to make it working and here I can reference bootstrap.esm.js
    <script type="importmap">
       {
           "imports": {
               "@popperjs/core": <EMAIL_ADDRESS>               "bootstrap": "/bootstrap/dist/js/bootstrap.esm.js"
           }
       }
   </script>

Please see the example here. js/index.esm.js referenced in package.json is only used by bundlers.

The change in package.json is the breaking change. Before the file was passed through Babel, now it isn't.

The change in package.json is the breaking change. Before the file was passed through Babel, now it isn't.

@XhmikosR Yes I know. With my modification index.esm.js is not passed through Babel because it's intended to be used as module by users.. users can do *import {Button} from "bootstrap" * in their projects and then use it as a module (parsing with Babel using their specific configuration, bundle it and minify). The module section in package.json is not intended to be used by browsers but by Node.js, imho there's no need to make it pass through Babel (it will be done later by the user in their projects if they need).
On the other side bootstrap.esm.js (that is still present and not touched by this modification) is intended to be used by browsers, and people must define a pathmap or include it directly to use it inside browsers (and this happened before my modification as well) despite the file defined in package.json.
Please see Luxon source code linked above. Sorry for these long posts and thanks for your patience and your replies, but I don't understand what's wrong with this PR. I'd like to understand to improve bootstrap-italia project as well.


jQuery.fn.resize() event shorthand is deprecated

Not up to date with the newest version of jQuery 3.5.1

Where do you see this shorthand version used?

It happens in our code when what I assume is the constructor gets called $.slidebars(). Let me check with the uncompressed version.

Very sorry for the false alarm. Our version is clearly slidebars 0.10.3. I'll have to figure out how to migrate.


add-gasCost-reputationOracle-bulkpayout

@foufrix how was this tested. Can we add a test?

End 2 end testing flow is already implemented and the code I added is tested through that (tests > e2e-backend > fixtures.js > sendFortune() )
I did not write new functions, just using the one from web3.js, which I suppose those methods are already tested in the web3 repo. estimateGas() is callable from any smart contract methods and web3.eth.getGasPrice() is a general function from web3.js.


Add option for custom ACME CA

Is your feature request related to a problem? Please describe.
I would like this tool to be used with a self signed CA in an internal environment that has an acme compliant server. I'm currently using Step CA for my acme compliant server. I currently don't have the option to use my own acme server without a ton of involved reconfiguration.
Describe the solution you'd like
An advanced configuration option where you can upload a self signed CA and give a custom acme compliant url to be used with a given host.
Describe alternatives you've considered
I am currently using a combination of jwilder/nginx-proxy and the encrypt companion to accomplish the same task with a custom acme CA, but it would be ideal to have a graphical frontend for a reverse proxy that can pull a valid internal cert, route traffic to separate physical hosts as needed and also the underlying containers running on the same machine.
Additional context

Are there any plans to integrate this feature? I'm having the exact same requirement.

I'm using NPM both for intranet traffic and for traffic coming from outside. For the latter, it works amazingly as it is, for the internal, would be nice if it could work with Smallstep CA (ACME and compatible with certbot) and avoid the manual certificate renewal every year for each service!

+1

Would love it if this feature was added!

+1

+1

So, this is my temporary solution:
I create my own container with this Dockerfile for each new version of NPM:
FROM docker.io/jc21/nginx-proxy-manager:2.11.1

RUN curl http://<internal_http_server>.lan/rootca.crt -o rootca.crt \
    && mv rootca.crt /usr/local/share/ca-certificates/rootca.crt \
    && update-ca-certificates

RUN echo -e "\nserver=https://labca.lan/directory\n" >> /etc/letsencrypt.ini

RUN sed -i "s\Let's Encrypt\LabCa\g" /app/frontend/js/*.js

This custom container can only work with the internal CA instance and not with Let's Encrypt. You can't have both. If you need also external domain you must run a second instance of NPM.
After this, I run the container in the same way I did before with the original NPM container, but I'm able to create and renew internal certificates with LabCA:

FROM docker.io/jc21/nginx-proxy-manager:2.11.1
RUN curl http://<internal_http_server>.lan/rootca.crt -o rootca.crt
&& mv rootca.crt /usr/local/share/ca-certificates/rootca.crt
&& update-ca-certificates
RUN echo -e "\nserver=https://labca.lan/directory\n" >> /etc/letsencrypt.ini
RUN sed -i "s\Let's Encrypt\LabCa\g" /app/frontend/js/*.js

Hmm. I tried using your solution @francescocaponio but whenever I try to issue a new certificate I get:
Certificate is not valid (Cannot read properties of null (reading '1'))
I'm using stepca as the bases for my ACME server. According to the logs from stepca the certificate gets issued but it seems that nginxproxymanager UI doesn't know what to do with it. Don't suppose you have any ideas?
From the logs it looks like it does indeed get issued...
app_1  | Successfully received certificate.
app_1  | Certificate is saved at: /etc/letsencrypt/live/npm-9/fullchain.pem
app_1  | Key is saved at:         /etc/letsencrypt/live/npm-9/privkey.pem
app_1  | This certificate expires on 2024-03-09.
app_1  | These files will be updated when the certificate renews.

Hi,
I also have the same log
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/npm-15/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/npm-15/privkey.pem
This certificate expires on 2024-06-04.
These files will be updated when the certificate renews.
NEXT STEPS:
...

try to analyze the content of the file /tmp/letsencrypt-log/letsencrypt.log of the npm container for a DEBUG level log of certbot, and check also the stepca logs to understand better where the problem could be.

@accessiblepixel

Hmm. I tried using your solution @francescocaponio but whenever I try to issue a new certificate I get: Certificate is not valid (Cannot read properties of null (reading '1'))
I'm using stepca as the bases for my ACME server. According to the logs from stepca the certificate gets issued but it seems that nginxproxymanager UI doesn't know what to do with it. Don't suppose you have any ideas?

The problem is caused by npm certbot, which after spending some hours I've just discovered that it removes the subject in the CSR. Also the default Step CA ACME provisioner configuration is not adding a CN/subject, when the CSR has none and this is what the problem is.
To solve you need to add
  "forceCN": true,

in your step-ca config ca.json.
Mine looks now like this and certificates are issued without issues.
                        {
                                "type": "ACME",
                                "name": "acme",
                                "forceCN": true
                        }

Hope this helps you.

@francescocaponio thank you for your cool solution, the workaround is working like a charm 🖖
PS: it cost me some time, till I realized your sed had a small typo. You used \ instead of / for the regex.

No disrespect to the project, but if you're facing these kinds of challenges, you might be starting to outgrow nginx-proxy-manager! It might be much easier in this scenario to just switch to plain old nginx, or another reverse proxy (eg: caddy). I just switched to caddy a few days ago for the better custom ACME provider support (and several other more advanced features). What you're trying to achieve here can be done in a few lines in a caddyfile:
my.domain.com {
    tls {
        issuer acme {
            dir https://ca.domain.com:8443/acme/acme/directory
	    trusted_roots /data/caddy/custom-certs/step-ca/step-ca.pem
        }
    }
    reverse_proxy * http://myappserver.local:8080
}

That's it! The whole configuration!

No disrespect to the project, but if you're facing these kinds of challenges, you might be starting to outgrow nginx-proxy-manager! It might be much easier in this scenario to just switch to plain old nginx, or another reverse proxy (eg: caddy). I just switched to caddy a few days ago for the better custom ACME provider support (and several other more advanced features). What you're trying to achieve here can be done in a few lines in a caddyfile:

@lriley2020 you are absolutely right, I had same thoughts too. I will probably switch myself to Caddy, but at least for NPM I wanted to see if there is a chance to get ACME working with another RA/CA, since it looked that, not much was missing. And in my case, the package was already there and was convenient to just use it.

+1


Add node ping command

Ping provides the ability to determine if a node is reachable or not. It can help revive failed nodes, or put to sleep nodes that zwave-js thinks are still awake.
Waiting for upstream PR for doc update.
Test Results
Ping listening node
Command and response
{ "command": "node.ping", "nodeId": 7, "messageId": 99 }
{"type":"result","success":true,"messageId":99,"result":{"responded":true}}

zwave-js logs
21:47:54.140 CNTRLR » [Node 007] pinging the node...
21:47:54.151 SERIAL » 0x010800130701002507c0                                              (10 bytes)
21:47:54.152 DRIVER » [Node 007] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      7
                      └─[NoOperationCC]
21:47:54.178 SERIAL « [ACK]                                                                   (0x06)
21:47:54.186 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:47:54.186 SERIAL » [ACK]                                                                   (0x06)
21:47:54.188 DRIVER « [RES] [SendData]
                        was sent: true
21:47:55.408 SERIAL « 0x011800130700007900bc7f7f7f7f010103000000004204000073              (26 bytes)
21:47:55.409 SERIAL » [ACK]                                                                   (0x06)
21:47:55.414 DRIVER « [REQ] [SendData]
                        callback id:     7
                        transmit status: OK
21:47:55.420 CNTRLR « [Node 007] ping successful

Ping sleeping node
Command and response
{ "command": "node.ping", "nodeId": 2, "messageId": 100 }
{"type":"result","success":true,"messageId":100,"result":{"responded":false}}

zwave-js logs
21:48:01.022 CNTRLR » [Node 002] pinging the node...
21:48:01.029 SERIAL » 0x010800130201002508ca                                              (10 bytes)
21:48:01.030 DRIVER » [Node 002] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      8
                      └─[NoOperationCC]
21:48:01.051 SERIAL « [ACK]                                                                   (0x06)
21:48:01.061 SERIAL « 0x0104011301e8                                                       (6 bytes)
21:48:01.062 SERIAL » [ACK]                                                                   (0x06)
21:48:01.063 DRIVER « [RES] [SendData]
                        was sent: true
21:48:05.350 SERIAL « 0x01180013080101ac007f7f7f7f7f01010700000000020700002d              (26 bytes)
21:48:05.351 SERIAL » [ACK]                                                                   (0x06)
21:48:05.355 DRIVER « [REQ] [SendData]
                        callback id:     8
                        transmit status: NoAck
21:48:05.360 CNTRLR   [Node 002] The node did not respond after 1 attempts.
                      It is probably asleep, moving its messages to the wakeup queue.
21:48:05.361 CNTRLR   [Node 002] ping failed: The node is asleep

@kpine your call but FWIW I don't think we need to wait for the docs update to merge this, I checked the zwave-js code and everything looks good


Hyper-V in environments throwing error

Dev Home version
0.1501.547.0
Windows build number
10.0.22631.3874
Other software
OS Build Version: 10.0.22631.3874.amd64fre.ni_release.220506-1250
.NET Version: .NET 8.0.6
Steps to reproduce the bug

Updated Dev Home to latest
Click environment
Get hyper-v error

Expected result
Just works cause Hyper-V Manager just works.
Actual result
hyper-v manager works yet dev home doesn't
Included System Information
CPU: Intel(R) Core(TM) Ultra 7 165H
Physical Memory: 31.64GB (12.65GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHomeGitHubExtension.Canary_0.1500.530.0_x64__8wekyb3d8bbwe (Dev Home GitHub Extension (Canary))
Microsoft.Windows.DevHomeAzureExtension.Canary_0.1000.530.0_x64__8wekyb3d8bbwe (Dev Home Azure Extension (Canary))
Microsoft.Windows.DevHome_0.1501.533.0_x64__8wekyb3d8bbwe (Core Widget Extension)
Microsoft.Windows.DevHome_0.1501.533.0_x64__8wekyb3d8bbwe (Hyper-V Extension)
Microsoft.Windows.DevHomeGitHubExtension_0.1500.533.0_x64__8wekyb3d8bbwe (Dev Home GitHub Extension (Preview))
Microsoft.Windows.DevHome.Canary_0.1501.547.0_x64__8wekyb3d8bbwe (Core Widget Extension)
Microsoft.Windows.DevHome.Canary_0.1501.547.0_x64__8wekyb3d8bbwe (Hyper-V Extension)
Widget Service:
MicrosoftWindows.Client.WebExperience_524.18000.0.0_x64__cw5n1h2txyewy

Hey @crutkas, Which error are you talking about exactly?

Sorry looks like the screenshot didn’t paste in.
This is adding user to hyper-v group
If hyperv manager lets me create / launch / delete without this, dev home should too

We can talk offline about it but we actually can't as the Hyper-V extension would need to run elevated in order to do that. The comment I linked above explains it. But under the hood Hyper-V manager is elevating (without a UAC prompt), by means we can't use in Dev Home. The only other way to allow users to interact with Hyper-V is if they are in the Hyper-V admin group. Once added to this group the users would need to log off/on again or reboot. It's a local users and groups account which is a bit of a special case, as even after being added/removed from the group the users access token that was given to them at logon, does not get updated. The Hyper-v apis are checking the users access token to confirm if they're in the group, which is why we can't just add them and have it all just work as they still won't be able to see/interact with their VMs until they've logged off/rebooted unfortunately:
Heres an excerp from a MS learn doc: How Access Tokens Work | Microsoft Learn  which states

If you add a user to a group after the user’s access token has been issued, or modify privileges assigned to the user account, the user must log off and then log on again before the access token will be updated.


Submit solution for 3Sum

I want to work on this. Could you assign it to me?

I want to write a solution in java. would you assign it to me?


Discuss indentation of configuration files in debugging docs

While building my BinderHub, most of my problems came from not indenting keys correctly in config.yaml and secret.yaml. I've updated the Debugging BinderHub docs to discuss different types of nested charts and suggest some tools to help with this issue based on discussions in #845 and this Discourse thread.

This is excellent!

Thank you, I had excellent source material to work from!


Hello, I edited your project and placed the AutoCompleteEntry element in my own ContentViews to add my properties (HeaderProperty, ListOfItemsProperty, TxtProperty). Unfortunately, I am solving a problem with the TextProperty property binding.

Hello, I edited Your project and placed the AutoCompleteEntry element in my own ContentViews to add my properties (HeaderProperty, ListOfItemsProperty, TxtProperty). Unfortunately, I am solving a problem with the TextProperty property binding.
NewPage1ViewModel is used on the NewPage1.xaml page, where in the constructor I set the default value this.Text01 = "The default value of the Text01 property when the VM is initialized";, unfortunately, this value is not written when the application starts in the required <controls:AutoCompleteEntryContentView Header="Vehicle brand:" Txt="{Binding Text01, Mode=TwoWay}" ListOfItems="{Binding ListItemText01, Mode=TwoWay}" ></controls:AutoCompleteEntryContentView>.
Unfortunately, binding to the Txt item is broken. The txt entry is set 2x when the project is started, the first time with the correct text from the VM and the second time as an empty string.
Can someone help me with this problem?
(google translator)
MauiAppAutoCompeteEntry.zip
https://drive.google.com/file/d/14APs_dURRwzPWWUnmTjUGzOQiAC_1O9w/view?usp=sharing
.Net 7
Tested on Samsung Xcover6 pro (Android 13) and Windows 11 (22H2)

Hello.
I've just updated the repo with a sample of a binding to Text, where the initial value is set in the VM constructor.
Could you check if this issue is still ongoing?

I'm closing this issue, due to lack of activity and because I cannot reproduce it.
Thanks!


documentation: new version timeouts

Updating docs to modified version of timeouts from the api and command line options
addressing issue #291

@sadath-12 It woudl be good if you can update the blog too.
check here :
https://github.com/kyverno/chainsaw/tree/main/website/docs/blog/posts

@eddycharly suggested me to back the change to blog since explanation is required there


Atom beautify introduces syntax error

Description
Beautification losing code which causing syntax error. I am using atom-beautify 0.29.23
Input Before Beautification
This is what the code looked like before:
const wWidth = document.body.offsetWidth;
const style = {
      weekHeader: {
        width: wWidth*7+8
      }
  };
export default style;

Expected Output
The beautified code should have looked like this:
const wWidth = document.body.offsetWidth;
const style = {
    weekHeader: {
        width: wWidth*7 + 8
    }
};
export default style;

Actual Output
The beautified code actually looked like this:
const wWidth = document.body.offsetWidth;
const style = {
    weekHeader: {
        width: *7 + 8
    }
};
export default style;

We are loosing variable wWidth
Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/vanng822/90d5088ac55baab8a9aac682af584772

I opened an issue on this.

Thank you @prettydiff

Yep, I am trying to get the latest version of Pretty Diff into Atom Beautify today.


Curation Stage Feature

Add a column to the data table showing the curation stage for each dataset. For admin use only.

I'll expose the curation status in the basic EE VO. Eventually, we will add support for secured fields in VO with so we can control who sees what.


fix(ClassObserver): split classes by any ASCII whitespace. fixes #257

@Gheoan thanks! Can you make the corresponding changes to the ClassObserver tests- as well as add a test for the new-line scenario?
https://github.com/aurelia/binding/blob/master/test/class-observer.spec.js
Please sign the CLA if you haven't done so already.

@jdanyow I made the first test to check for every possible ASCII whitespace. Are you ok with modifying the test or you want a new one?

thanks @Gheoan will review and merge asap- did you sign the CLA? (required for legal reasons)

@jdanyow I already signed the CLA

@jdanyow Should we merge and add this to the forthcoming release?

CLA confirmed.

Not yet- I need to fix the tests.  We can put it in the next release.


remove downstream listeners from Envoy Mobile build

based on a hacked up prototype looks like ~1M savings

@jpsim next step is y'all experimenting with the use_api_listener runtime guard.

That'd be setRuntimeGuard("use_api_listener", true / false) right? Is there a way we can observe if it's being applied correctly?

I'm comfortable removing the listeners completely. It looks like all our unit and integration tests pass with listeners disabled and I don't think we need to run a production experiment for this.


Adding data for es-Co 'Colombia' in the provider database

There was no data for Colombia 'es-CO' in the provider database.
I added some of the basics by now and I am preparing the rest that is under my knowledge.
I read the contributor guidelines and used the files of other countries as reference for structure, styling and information contained. If I am missing something, I'm sorry, its my first time on here. Let me know and I'll gladly fix it.

Pull canceled.
I will make a new attempt after the corrections needed are made


Make test amounts BigNumbers

Multiple tests use bare JS numbers as amounts, we should migrate them all to our bignumber library of choice to prevent floating point errors (and for consistency).

Duplicate of #204?

Hmm, true. Closing.


refactor: add methods and implement traits for FilePath and SafeFilePath

closes #1726

waiting on https://github.com/tauri-apps/tauri/pull/10884 to be released


Pytorch

In this PR, we switch the learning part to PyTorch and support Logistic Regression and LSTM.
One thing to be addressed here is the input of training/prediction function needs to be (candidates, features) instead of features.

I'm also seeing this error when running make docs
WARNING: autodoc: failed to import module 'fonduer.learning'; the following exception was raised:
Traceback (most recent call last):
  File "/home/lwhsiao/repos/fonduer/.venv/lib/python3.6/site-packages/sphinx/ext/autodoc/importer.py", line 152, in import_module
    __import__(modname)
  File "/home/lwhsiao/repos/fonduer/fonduer/learning/__init__.py", line 1, in <module>
    from fonduer.learning.disc_models.logistic_regression import LogisticRegression
  File "/home/lwhsiao/repos/fonduer/fonduer/learning/disc_models/logistic_regression.py", line 8, in <module>
    from fonduer.learning.disc_learning import NoiseAwareModel
  File "/home/lwhsiao/repos/fonduer/fonduer/learning/disc_learning.py", line 26, in <module>
    class NoiseAwareModel(Classifier, nn.Module):
TypeError: metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases


C# beta features and cleanup

This PR is based on #2643, which needs to be merged first.
This PR bring some small features towards beta and also does some cleanup:
-- exposes peer info in serverside call handlers (fixes #2543)
-- adds option to authenticate client using root cert chain (fixes #2588)
-- fix all VS project to target AnyCPU and not x86
-- upgraded to latest version of Google.Apis.Auth that has been released recently.

The C# windows tests seem to be consistently failing.

Updated this to include PR #2654, which should fix the tests.

Jenkins is green enough.


slog kvs are missing in CaseTraceLogger

Bug Report
What did you do?
make trace_test
What did you expect to see?
2019/03/12 13:51:49.548 node.rs:203: [INFO] alloc store id
2019/03/12 13:51:49.565 node.rs:218: [INFO] alloc first region id
2019/03/12 13:51:49.565 node.rs:225: [INFO] alloc first peer id for first region
2019/03/12 13:51:49.614 node.rs:136: [INFO] try bootstrap cluster
2019/03/12 13:51:49.771 node.rs:203: [INFO] alloc store id
2019/03/12 13:51:49.790 node.rs:326: [INFO] start raft store thread

The log is not complete, miss important info, eg, cluster id/store id/region id
What did you see instead?
All slog kvs are retained.

For contributors who want to fix this:
Currently CaseTraceLogger does not output kv pairs:
https://github.com/tikv/tikv/blob/192cd352667fa52fb0f205a0ad517b12ae9f150e/components/test_util/src/logging.rs#L33
We can just refer to slog-term's implementation to output kv pairs:
https://github.com/slog-rs/term/blob/e5518f68b00f088c19aaa8238a23dac3a7aa8843/src/lib.rs#L394


OLS-559: Use AnyHttpUrl instead of bare string

Description
OLS-559: Use AnyHttpUrl instead of bare string
Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #OLS-559
Closes #

/lgtm

/approve

@tisnik what does this have to do with OLS-559?


Use https://wiki.geysermc.org/ instead of the old GitHub wiki

This only applies to the Wiki command now

Removed command in https://github.com/GeyserMC/GeyserDiscordBot/commit/2dedff39f148506462f6a75e0b22d0f01770be67


Updating to work with Angular 11

Makes this work with Angular 11, plus resolves #70.
I was getting the same issues as described in #70 and this link helped: https://github.com/angular/angular/issues/15763

Please disregard - did not solve the problem.

did you get this working for angular 11?


BP.TF Classifieds are not being relisted after a failure

Describe the bug
BP.tf classifieds are not being relistead after some failure with it's (BP.TF) API.

To Reproduce
Steps to reproduce the behavior:

Let bot do usual scheduled tasks
Let BP.TF API request fail
Classifieds are not restored after hiding.

Expected behavior
There should be retriable task for that.

Screenshots and logs

2021-01-05 13:23:19 ESC[34mdebugESC[39m: Removing all listings
2021-01-05 13:23:19 ESC[34mdebugESC[39m: Checking listings...
2021-01-05 13:23:26 ESC[34mdebugESC[39m: Count didn't change
2021-01-05 13:23:26 ESC[34mdebugESC[39m: Removing all listings...
2021-01-05 13:23:26 ESC[34mdebugESC[39m: Disconnected from socket server {"reason":"io server disconnect"}
2021-01-05 13:23:26 ESC[34mdebugESC[39m: Disconnected from socket server {"reason":"forced close"}
2021-01-05 13:23:34 ESC[34mdebugESC[39m: Connected to socket server
2021-01-05 13:23:34 ESC[34mdebugESC[39m: Checking listings...
2021-01-05 13:23:44 ESC[34mdebugESC[39m: Disconnected from socket server {"reason":"ping timeout"}
2021-01-05 13:23:50 ESC[34mdebugESC[39m: Checking account info
2021-01-05 13:23:58 ESC[34mdebugESC[39m: Connected to socket server
2021-01-05 13:24:08 ESC[34mdebugESC[39m: Disconnected from socket server {"reason":"ping timeout"}
2021-01-05 13:24:27 ESC[34mdebugESC[39m: Connected to socket server
2021-01-05 13:24:37 ESC[34mdebugESC[39m: Disconnected from socket server {"reason":"ping timeout"}
2021-01-05 13:24:56 ESC[36mverboseESC[39m: 0 incoming offers (0 on hold), 0 outgoing offers (0 on hold)
2021-01-05 13:25:10 ESC[34mdebugESC[39m: Connected to socket server
2021-01-05 13:25:20 ESC[34mdebugESC[39m: Disconnected from socket server {"reason":"ping timeout"}
2021-01-05 13:25:21 ESC[33mwarnESC[39m: Failed to check for updates:  ETIMEDOUT {"code":"ETIMEDOUT","connect":true,"attempts":6}
2021-01-05 13:25:25 ESC[33mwarnESC[39m: Failed to get account info from backpack.tf:  ETIMEDOUT {"code":"ETIMEDOUT","connect":true,"attempts":6}

Additional context

I had to use !refreshlistings to fix this.
Version: 2.3.5

known problem and I already fed up to find the fix.

known problem and I already fed up to find the fix.

Thanks, I've seen this remark. To my understanding deprecation just means a feature which could be removed in future releases, it doesn't explicitly tell us it's broken. If that's the case, would you mind if I submit a PR fixing the wiki to address this issue?
I'm not familiar with bot's codebase, but, what's wrong with catching an exception and unhiding classifieds back and/or implementing a retriable?

Thanks, I've seen this remark. To my understanding deprecation just means a feature which could be removed in future releases, it doesn't explicitly tell us it's broken. If that's the case, would you mind if I submit a PR fixing the wiki to address this issue?
I'm not familiar with bot's codebase, but, what's wrong with catching an exception and unhiding classifieds back and/or implementing a retriable?

ok. You can't submit a PR for editing the wiki. Just send your suggestion here. Thanks.

ok. You can't submit a PR for editing the wiki. Just send your suggestion here. Thanks.

Hm, thought that's possible on github for some reason, lol.
I suppose we just state that this feature is broken.

Hm, thought that's possible on github for some reason, lol.
I suppose we just state that this feature is broken.

Nah not really broken. Only broke when backpack.tf dead

Nah not really broken. Only broke when backpack.tf dead

@idinium96 aight, but bot doesn't recover when bp gets back online, classifieds are still stuck hidden unless restarted.

@idinium96 aight, but bot doesn't recover when bp gets back online, classifieds are still stuck hidden unless restarted.

Currently being tested in 00a9f6f commit (development branch, #278)

Currently being tested in 00a9f6f commit (development branch, #278)

Is this still a thing in the latest version?

Unfortunately, I can't nor confirm nor deny, due to bptf premium. I guess we have to ask around people who use this feature.


Support Python 3.9

We have to wait pytd dependencies Python 3.9 support, especially for

PySpark
td-spark
pyarrow

As of Jan 12th 2021, the dependencies status are:

td-spark v20.10.0 supports Spark 3.0.1
Spark 3.0.2 will support Python 3.9 https://issues.apache.org/jira/browse/SPARK-33371
pyarrow 3.0.0, planned to be released this January, will support Python 3.9 https://issues.apache.org/jira/browse/ARROW-10905?src=confmacro

pyarrow 3.0.0 has been released https://pypi.org/project/pyarrow/3.0.0/

pyarrow 3.0.0 has been released https://pypi.org/project/pyarrow/3.0.0/

Note: we dropped Python 3.9 support as of 1.4.2.
We're planning to support 3.9 once td-spark and PySpark support 3.9 and Python packages are released on PyPI.

@chezou Do we have any plans to resume 3.9 (and 3.10?) support ?

@robinbowes I'm no longer with maintaining pytd anymore. It's up to @treasure-data/integrations team's decision now.

@chezou Thanks for confirmation.


Unable to use some keys of the iPad smart keyboard on lessons

Describe your problem and - if possible - how to reproduce it
When using the site on Safari and Chrome on an iPad pro, I am no longer able to use some keys like arrow keys to navigate the lesson pane, which means I am stuck touching the screen to position my cursor, which isn't incredibly accurate. I also cannot use the 'press to move the cursor' action on the lesson pane so can't place my cursor where needed, so it depends on having to touch the screen on the exact place I need to place the cursor. I also can no longer use ctrl + enter to submit the lesson. I used to be able to use the arrow keys and the ctrl + enter to submit previously.
Add a Link to the page with the problem
Tell us about your browser and operating system

Browser Name: Chrome and checked on Safari
Browser Version:
Operating System: iPad OS 11.4

If possible, add a screenshot here

Hi @seekingcat
Thanks a lot for the issue report, and we are sorry to hear about the bad UX.
We currently have almost no support for Mobile devices other than those with standard Keyboard, Mouse/Touchpad
I understand this is an annoyance. But there might be a while before we can support our platform on all devices. Until then I would recommend you to be using the platform on a desk device.
I am tagging this as help wanted for further investigation and fix.

Hi, thank you for your response. It really was just a curiosity as the keyboard arrow keys worked in the previous platform. I asked Quincy on Twitter and he said to raise it as an issue. Hopefully this will get a look in, but I appreciate there are other more urgent issues. Thanks again.

Additional info
On mobile devices, the keyboard does not show up when the code editor is clicked
This is an issue on both .org and .rocks
To Reproduce
Steps to reproduce the behavior on mobile phone:

Go to https://learn.freecodecamp.org/javascript-algorithms-and-data-structures/regular-expressions/using-the-test-method
Click on the code editor to enter the the answer to the challenge.

Expected behavior
The keyboard should pop up when user clicks on the code editor on mobile.
Screenshots

Smartphone (please complete the following information):

Device: iphone 5S

@emmawinston I don't think we are using p5. however, I believe a similar solution to trigger the keyboard could work. I was wondering if you are still interested in this issue?

@ahmadabdolsaheb even if they're no longer interested, it still is a bug which needs fixing

@ahmadabdolsaheb even if they're no longer interested, it still is a bug which needs fixing

Hello, yes, I am still interested! I'm also pretty swamped with work hence the very slow response, sorry. If nobody else wants to take a look I will add it to my to do list, but it might be a while before I get to it! :)

Any update on this? @raisedadead

Any update on this?

A pull request is welcome if you are interested.

Hi @raisedadead,
I am not aware of the codebase and how much effort it would take to submit PR
I am interested if someone could guide me on how to fix this


Use representative point for markers in cohort maps

In the map on the home page and the maps in the country pages, use the representative points for plotting markers, which should then bring together all cohorts which share a common admin2 unit.
I.e., there should be exactly one marker for each admin2 unit.

E.g., this should be just one marker...

And make it easy to differentiate between individual markers on the cohort pages and cohort markers on the home page / country page


Update index.html

added my profile..

hi! why this repo is shown as "excluded project" in hacktoberfest

Hi! why is repo is shown as "excluded project" in Hacktoberfest


Derive decode for struct with fields with different endianness

For below struct:
#[drive(Decode)]
struct Foo {
    identifier: u32,     // big endian, fixed size.
    flags: u32,          // native endian, fixed size.
}

How could this work with bincode-2? Asking this question for serveral reasons:

There's a Config argument indecode_from_reader, it can be configured to either big endian or little endian, but neither would work for above struct?
Would it make sense to add endianness annotations for some field, like binread crate?
With a combination of both 1) and 2), when there're enough annotations to tell how to deserialize the data, why a Config argument is needed at all (at least wrt endianness)?

It sounds like you're trying to use bincode to interface with a foreign format. Is that correct? Bincode does not support compatibility with formats other than bincode. The endianness config was designed purely to improve speed on systems with different endianness.


pubsub: fire simultaneous pull requests

Fixes #1974
To Dos

[ ] Unit tests

Closed for now, as the Pub/Sub team's feedback could squash the need for this / force big API changes that would be too tiring to keep this PR up to date with. We can use this as a reference if we need to re-implement after the API makeover.


Middle ware to parse application/json http requests

Rack Middleware to handle different content for the http routes
API communication with mobile applications uses various formats specified by their 'Content-type' header, including JSON, and XML.  This PR adds support for JSON, and makes other parsers pluggable.  The parsers are needed to transform the body of POST requests into params attributes that can be consumed by the Volt controllers.
About

Handles 'application/json' by default
enables Volt.config.http_content_types setting to add additional parsers
handles nested attributes gracefully

Great work on this.  Thanks!


Handle overload for HttpStatus codes and exception handling for large json payloads

Method added to ErrorHandler for receiving a status code and map of log messages instead of an exception and map of log messages.
Method should help streamline providing more accurate status codes in our microservices.
mongodb-driver added to pom for BsonSerializationException.
BsonSerializationException check added to the original handle method to properly return 413 instead of 400 when json payload is too large.

ObjectHelper search function modified to use GET instead of POST. Resolved 415 error.

LGTM. Merging


provide definition for 'data item from reasonable extrapolation'

definition provided in the 2016-02-04 version of the OWL file.


added engine=openpyxl in read excel and correct bug with value_counts

In order to run on my computer I had to add the following changes:

engine="openpyxl" to the read_excel pandas method;
Also df.value_counts("NOC") did not work for me (which probably is a matter of the pandas version - I changed to df["NOC"],value_counts().

Solved by specifying the environment in 13b4ada1 instead. In particular, pandas==1.2.4 is expected.


minor change to notebook

Why are these changes needed?
Fix an indent and version number in the openai notebook.
Related issue number

Checks

[x] I've used pre-commit to lint the changes in this PR, or I've made sure lint with flake8 output is two 0s.
[ ] I've included any doc changes needed for https://microsoft.github.io/FLAML/. See https://microsoft.github.io/FLAML/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Looks good to me. Just wondering why do we need to fix the version?

Version 1.1.3 updated the price from v1.1.2. The notebook's results will be quite different when using these two different versions, including how long it takes to finish.

Looks good to me. Just wondering why do we need to fix the version?

Version 1.1.3 updated the price from v1.1.2. The notebook's results will be quite different when using these two different versions, including how long it takes to finish.

pip install will always install the latest version by default. To avoid installing the eariler version, maybe better use >=1.1.3.

Looks good to me. Just wondering why do we need to fix the version?

Version 1.1.3 updated the price from v1.1.2. The notebook's results will be quite different when using these two different versions, including how long it takes to finish.

pip install will always install the latest version by default. To avoid installing the eariler version, maybe better use >=1.1.3.

After we release a new version and before we update the notebook, if a user executes pip install flaml>=1.1.3, they will see an inconsistent result. That's why I fixed the version number here.


WIP: Jordan/1626 update sentry

Closes #1626
Description:

removed raven JS
added sentry/browser

❤ Thank you!

[ ] Added entries in CHANGELOG.md with issue # and GitHub username
[ ] Reviewed Files changed in the github PR explorer

so it seems that the new sentry SDK has improved support for source maps - having a hard time understanding this documentation tbh.

That looks awesome!


grpc_server: fix tokenizer group usage

Without this fix, the grpc server won't start:
ERROR:    Traceback (most recent call last):
  File "/opt/vllm/lib64/python3.11/site-packages/starlette/routing.py", line 732, in lifespan
    async with self.lifespan_context(app) as maybe_state:
  File "/usr/lib64/python3.11/contextlib.py", line 210, in __aenter__
    return await anext(self.gen)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/vllm/lib64/python3.11/site-packages/vllm/entrypoints/openai/api_server.py", line 60, in lifespan
    grpc_server = await start_grpc_server(async_llm_engine, args)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/vllm/lib64/python3.11/site-packages/vllm/entrypoints/grpc/grpc_server.py", line 600, in start_grpc_server
    await service._post_init()
  File "/opt/vllm/lib64/python3.11/site-packages/vllm/entrypoints/grpc/grpc_server.py", line 121, in _post_init
    self.tokenizer_group = await self.engine.get_tokenizer_group()
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'AsyncLLMEngine' object has no attribute 'get_tokenizer_group'

See smoke test logs at https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_release/52005/rehearse-52005-pull-ci-opendatahub-io-vllm-ibm_main-smoke-test/1793932779138846720/artifacts/test/build-log.txt

Note: this is not required on release, as 78a8dfe5 takes care of that


anchors not working on lbry.io

Noticed this while browsing https://lbry.io/faq/contributing - clicking the bookmarks doesn't take you to the correct section.
The anchors in  https://github.com/lbryio/lbry.io/blob/master/content/faq/contributing.md seem to work fine.

So, this is annoying. Two different kind of Markdown syntaxes for anchors.
Our PHP uses: https://michelf.ca/projects/php-markdown/extra/#spe-attr
GitHub uses: https://gist.github.com/asabaylus/3071099
I suppose since this is the website file, we ought to use the PHP syntax documented above (I haven't confirmed this works, btw).

I was wrong, our PHP uses: https://github.com/erusev/parsedown-extra

@tzarebczan you can likely fix this by changing the anchor syntax to match that specified in the first/third link.

Yup, was going to look into it this week. Thanks for the initial legwork.

Fixed the contributing doc: https://lbry.io/faq/contributing#designing
Will check if we are doing this elsewhere - definitely on the learn page.

The learn page is not rendered via Markdown
On Mon, Sep 25, 2017 at 12:19 PM, Thomas Zarebczan<EMAIL_ADDRESS>
wrote:

Fixed the contributing doc: https://lbry.io/faq/contributing#designing
Will check if we are doing this elsewhere - definitely on the learn page.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry.io/issues/222#issuecomment-331934313, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgZVkEdMibS9dpIapoRBrEkm-kiBRAEks5sl9KagaJpZM4PW2cz
.

--
Jeremy Kauffman, Founder, LBRY http://lbry.io/
(267) 210-4292
Build LBRY: get https://lbry.io/get, follow https://twitter.com/lbryio,
like https://facebook.com/lbryio

I meant the what page, oops. I see its in PHP, and they already work: https://lbry.io/what#combatting-the-ugly (I was using the wrong URL in the past which I why I didn't think it was working)


Scroll Offset is not retained/restore when moving around a TabBarView

If you add a scrollable widget (ListView, etc) to a TabBarView and swap to another index and then back again the scroll offset is not restored. The offset will be reset to zero.

/cc @Hixie

Yeah we should probably restore the page storage logic.

Dupe of https://github.com/flutter/flutter/issues/8101


[WIP] Parse value alias

This is a WIP PR, making this for some feedback about whether the general direction is correct.
Things that still need to be done:

Tests to ensure parsing value aliases work;
Verification that repeated value aliasing statements are aliasing to the same value;
Rewriting aliased values as they are defined in the source code

Fixes #23.

Whew! Sorry it took so long. I've incorporated feedback from your comments into my code. Now what's left is adding a unit test and a file test... will get to that soon.

Hmm... so I'm running into issues about type inference. Consider the example code you gave in the linked issue:
function qux() {
ebb0:
  v4 = iconst.i8 6
  vx3 -> v4
  v1 = iadd_imm vx3, 17
}

The iadd_imm instruction needs to know what the type of vx3 is, but since we parse instructions during recursive descent and resolve source-to-IR mappings at a later pass, we do not have enough information about what the type of vx3 is during instruction parsing.
I think rustc has the same problem and they use the concept of type variables to represent an unknown type, which would be resolved at a later pass. In other words, we'll need to have another pass that specifically resolves type variables, if we are to follow and copy what rustc does.

Good to have you back!
About the issues with type inference. I wrote some more about it in #63.
In general, the Cretonne parser doesn't try to be too fancy about type inference. It's a language for writing test cases, so it is usually best to be as explicit as possible. In practice, the parser can only infer types from values that it has already seen defined earlier in the text.
I think this principle can be extended to aliases too:
  v4 = iconst.i8 6
  vx3 -> v4
  v1 = iadd_imm vx3, 17

When looking for the type of vx3, infer_typevar() finds that it is not present in the source map and fails. This check could be extended to alternatively check if the source value is an alias, and then check if the aliased value has a known type. If the aliased value has not been defined yet, just fail the same way.
The idea is "best effort, not too fancy".

About the Travis CI failure: Cretonne is currently checking against rustfmt 0.7.1. I see that 0.8.0 is out, so I'll upgrade it now.

Alright! This should be ready to go. I'm not sure if it needs a file test though...

Awesome, thanks!
For the parser, it is usually easier to write file tests than unit tests when testing more complicated things. You can't test parser errors that way, though.


Error step-04 folder

I have read and done all chapters without any problems. But I get an error while doing: "7. Set up a signaling service to exchange messages". I use git clone to get the code on my localhost. I delete the work directory and rename the step-04 folder to work. I go inside the work folder. I do a npm install. Then node index.js. It's running without a response, so that's fine. From my browser, I open localhost:8080 (like it is said). The browser gives error: ERR_CONNECTION_REFUSED. In the node console I get the following error message:
/Users/My_Name/Localhost/webrtc-googlecodelabs/work/node_modules/node-static/lib/node-static.js:348
                      mime.lookup(files[0]) ||
                           ^
TypeError: mime.lookup is not a function
    at Server.respond (/Users/My_Name/Localhost/webrtc-googlecodelabs/work/node_modules/node-static/lib/node-static.js:348:28)
    at /Users/My_Name/Localhost/webrtc-googlecodelabs/work/node_modules/node-static/lib/node-static.js:64:22
    at FSReqWrap.oncomplete (fs.js:123:15)

The same error I get with step-05 and step-06.
I have Node v6.10.2 and Chrome 62.
What am I doing wrong?

I found a solution myself. I edited the index.js like this:
'use strict';
var os = require('os');
var app = require('express');
var http = require('http').Server(app);
var io = require('socket.io')(http);
var port = process.env.Port || 3000;
io.sockets.on('connection', function(socket) {
  // no changes, same as original
});
http.listen(port, function(){
  console.log('listening on *:' + port);
})

Install express with the command npm install express --save
And in the index.html change the line:
<script src="https://cdn.socket.io/socket.io-1.2.0.js"></script>
Since index.html is not served anymore by the node app 'index.js(by the changes I made), I have  installed the 'Webserver for Chrome' that is a webserver now forindex.html`.

I cannot get it work, and same issue! I tried with @hermanfransen suggest, but not help at all.

I can reproduce the error. It seems that updating node-static dependency makes it work.
Credit: https://stackoverflow.com/a/46622619/7684576
Submitting PR.

Problem seems to be reproducible in steps 5 and 6 too. Submitting PR for them too.

Thanks @hermanfransen and @quangtrung89 !
Apologies for the delay in responding.
Should be fixed as @nitobuendia describes.


Fix digest resolution for GCR

Removes additional (for GCR unacceptable) parts from Accept header
Adds tests for official docker.io and gcr.io registry

fixes #134

Awesome thanks!


Update the add device modal screenshots

Change-type: minor
See: https://github.com/balena-io/balena-ui/issues/4710
Signed-off-by: Thodoris Greasidis<EMAIL_ADDRESS>

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

No @vipulgupta2048 there are a few really outdated cases of that button showing in some of the device guides.
I'm planning to fix those in a second pass. Making those images is not fun :(

@balena-ci rebase

I'm planning to fix those in a second pass. Making those images is not fun :(

Welcome to a documentarian's world ❤


⚠ Bofrost.at has degraded performance

In 55a91e6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1422 ms

Resolved: Bofrost.at performance has improved in 8f1ac24 after 27 minutes.


⬆ upgrade substrate to polkadot-v0.9.43

Upgrade substrate version to polkadot-v0.9.43.
Co-authored-by: @abdelhamidbakhta

Breaking change from Substrate, no more ws options on the cli
https://github.com/paritytech/substrate/pull/13384

I fixed all ws occurrences for the tests
This PR also introduces a condition where the out-peers can't be set to 0
https://github.com/keep-starknet-strange/madara/blob/c49f2c8bc7c3668ec3ccfac1db454b7c5cbff62a/tests/util/dev-node.ts#L93
I commented that line in the tests, but would like some feedback on how you want to handle that. The error that it appears is not friendly at all


docs(all): remove example of mdx follow on designer advice

Checklist

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information

:tada: This PR is included in version 1.0.0-alpha.50 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


$http no longer accepts "string-like" URLs

Since Angular 1.4.9, the $http service only accepts pure strings as URLs.  If I pass in an object that has a toString() method, $http raises an exception:
var url = {
   toString: function() {
        return 'http://www.example.com';
   }
};

$http.get(url); // Throws "Error: [$http:badreq] Http request configuration url must be a string."

This is a departure from Angular's pre-1.4.9 behavior, jQuery, and XMLHttpRequest; all of which accept (and correctly interpret) the url object described above.  This behavior was introduced in 6628b4f1e5835d997290881c6ba394547883a516 to fix #12925, and merged in #13444.
I would recommend relaxing this restriction slightly, and allow objects with a toString() method to be used as URLs.

The relevant portion of $http's source currently looks like:
if (!isString(requestConfig.url)) {
      throw minErr('$http')('badreq', 'Http request configuration url must be a string.  Received: {0}', requestConfig.url);
}

I would recommend changing it to something like this:
var isStringlike = function(val) {
    return isString(val) || (isObject(val) && isFunction(val.toString));
};
if (!isStringlike(requestConfig.url)) {
      throw minErr('$http')('badreq', 'Http request configuration url must be a string.  Received: {0}', requestConfig.url);
}

While this would result in a less-satisfactory fix for #12925 (we might throw a less descriptive error in some cases), the behavior would also be more correct.
If this looks good, I can write up a PR.

Some downsides to the above approach:

Even currently, we do not reject empty strings
Some objects (ie. []) serialize to an empty string
Object.prototype.toString does not serialize objects in a way that could ever be useful.

It's documented that http only accepts strings in the url. So I don't think we should now start to support objects with toString functions.

Agree with @Narretz the change that you point to only enforces something as it is specified in the documentation.

I disagree.  Given that JavaScript is a dynamically-typed language, when an API document states that a method accepts a string, a developer can typically expect that the method can safely accept a string, or any other value that can be safely coerced to a string, unless the documentation specifically notes that the library performs an explicit type-check.
To pick one very obvious example, most of Angular's API methods that accept boolean values will happily accept any truthy or falsy values.  Very few other string parameters are type-checked, and Angular generally performs very little type-checking at all; only performing such checks when the coercion would be invalid, nonsensical, or unsafe.
By introducing this change, Angular broke a contract about how developers expect a dynamically-typed language to work.  While the change is technically consistent with the existing documentation, it is not consistent with how similarly-documented functions in Angular behave.
Finally, I would argue that the rationale for introducing this change (displaying a helpful error message when a developer passes in an obviously-invalid URL) does not appear to have been actually satisfied by the changes that were introduced, nor is the stated rationale sufficient for breaking existing usages of the library (without explicitly noting it as a breaking change).

Workaround for anybody stumbling across this page:
$provide.decorator('$http', function($delegate){
    var newHttp = function(cfg){
        if(cfg.url instanceof Object){
            cfg.url = cfg.url.toString();
        }
        return $delegate(cfg);
    };

    angular.extend(newHttp, $delegate);

    angular.forEach(['get', 'delete', 'head', 'jsonp'], function(method){
        newHttp[method] = function(url, cfg){
            return newHttp(angular.extend({}, cfg || {}, {
                method: method,
                url: url
            }));
        };
    });

    return newHttp;
});


SR300 is not detected in realsense-viewer

Required Info

Camera Model
SR300

Firmware Version

Operating System & Version
Ubuntu 16.04 LTS

Kernel Version (Linux Only)
4.10.0-38-generic

Hardware
Surface Book performance base

I followed this link, but realsense-viewer says please connect device. The camera itself works fine, it worked on an other Ubuntu machine.
The result from
modinfo uvcvideo | grep "version:"
is
version:        1.1.1.realsense-4.4.0 srcversion:     F394CA611A53D8EEC317046
and  sudo dmesg | tail -n 50
is
[  664.005629] usb 2-<IP_ADDRESS>: New USB device found, idVendor=8086, idProduct=0aa5 [  664.005633] usb 2-<IP_ADDRESS>: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [  664.005636] usb 2-<IP_ADDRESS>: Product: Intel(R) RealSense(TM) Camera SR300 [  664.005639] usb 2-<IP_ADDRESS>: Manufacturer: Intel(R) RealSense(TM) Camera SR300 [  664.005641] usb 2-<IP_ADDRESS>: SerialNumber:<PHONE_NUMBER>8
also lsusb shows
Bus 001 Device 010: ID 041e:4099 Creative Technology, Ltd

Do you see the camera using lsusb?

@dorodnic  with lsusb, yes, Creatie Technology is SR300 camera. The other laptop, which is working with librealsense v1, returns the same. So at least camera is recognized.

Hi @hironoriyh , what is the output for "rs-enumerate devices" demo (from librealsense2-utils package)?
Additionally, please log disconnect/reconnect flow and provide the full log with "dmesg -wT"

@hironoriyh , do you still need assistance with the topic ?

@dorodnic  sry for the late response. we use sr300 on another machine now.

Hi @hironoriyh , I'm closing this it seem you have the device running properly on another PC.
Feel free to reopen this in the future.


More clarity on scaling

in this article
https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-hubs-trigger?tabs=csharp#scaling
what happens when the scaleout setting of app service plan is set to 1?
are we still going to get Function_0 to Function_n as per function scaling logic upto the total consumption of app service plan resources or one app service plan unit(per scaleout) means always only Function_0?
can I get more clarity on this?

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

ID: a109c38e-b241-c9a2-7ef8-2e828659191c
Version Independent ID: 69842b0f-607f-5cf5-6e1a-4d312c98100c
Content: Azure Event Hubs trigger for Azure Functions
Content Source: articles/azure-functions/functions-bindings-event-hubs-trigger.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

Hello @mganeshphani, Thank you for your question! We will review and update as appropriate.

Hello @mganeshphani
Thank you for reaching out. When you manually set the scale-out setting to “1” this means only single instance of your function app will be running at any given time. As mentioned in the document each instance of an event triggered function is backed by a single EventProcessorHost instance, so the Function_0 instance will be the only instance running. You can find more information here regarding scaling for App service plan.
Please let me know if there are any additional concerns.


reorder to speed up ui rendering, and bypass wintun uninstall errors

Things start to get more interesting.

When I tried to move app.run() above, the systray will just not show up at all. Looks like some error happening again. Maybe the app.run() is trying to access something, for example device and driver, that will be later initiated?
Just as I was about to trouble shoot the issue above, I reran and got a whole new error:
preflight device failed. error message: Error creating interface: Cannot create a file when that file already exists.

Windows interface and tun creating/uninstall is so messed up. Continuing the investigation.

Restarting the app and manually exiting the app solved the 2nd issue, since it helps dispose these stuff. Now focusing on 1st issue


Prototype kit: Improve guidance around sharing prototypes, and using Github

What
We need to improve our guidance around how to use Github and why it is important.
Why
Some users don't feel confident using Github as a way to save and share their work with others. There are indicators from user research that this is a mix of confidence and knowledge.
Done when

[x] We've researched the type of users that we have and where people might sit on a scale (beginner to expert)
[ ] We've researched the involvement journey that Github requires
[ ] We've explored the reasons that people don't feel confident
[ ] New guidance around using github (and it's benefits) is proposed

Started to look at the involvement that Github requires people to have to use it: https://app.mural.co/t/nhsdigital8118/m/nhsdigital8118/1631008407533/64487a92c5c94fb6afca78533431aa36704fc175?sender=karlgoldstraw0227