Publishing to IIS doc does not cover how to ACL the directory containing your site

It would be great if https://docs.microsoft.com/en-us/aspnet/core/publishing/iis referenced https://docs.microsoft.com/en-us/aspnet/core/hosting/apppool#securing-resources this somewhere as that information is otherwise difficult to discover.
Linked issue https://github.com/aspnet/Hosting/issues/914

@shirhatti @tdykstra Do you want me float some language in there for this?

@GuardRex Yes, that would be great.  How about incorporating the App Pool doc content into publishing/iis and retire the separate app pool doc?

Sure ... I can handle that.
There's a few things to consider ...

In the Add Website dialog, IIS fills the "Site name" text over to the "Application pool" textbox and creates a new AppPool for each new site created unless you click Select to use an existing AppPool. @shirhatti, your opening paragraph might be misinterpreted by a reader that they will need to explicitly setup a new AppPool for each app separately after the site is created (outside of the Add Website dialog). If it's ok, I'd like to refactor that language a hair.
We don't want to make anyone think that merely running a site requires an AppPool identity other than ApplicationPoolIdentity. It comes up when the process needs other permissions. I'm concerned about the "To grant the IIS worker process access to your application, you will need to ..." language. The "access" could be misinterpreted as "to even load the site" and the "you will need to" implies that it must be done for every app. If it's ok, I'd like to work on that text just a bit.

... and I'll update the images to WS2016.
Finally, there's that open PR at https://github.com/aspnet/Docs/pull/2488, which I don't think would result in a merge conflict if I update that branch after a PR for this issue. Otherwise, it might be safer if that other PR gets merged first. Why do I feel a big 'ole GH :bomb: about to go off? :boom: :smile:


python311Packages.python-engineio: 4.6.1 -> 4.7.1

Diff: https://github.com/miguelgrinberg/python-engineio/compare/refs/tags/v4.6.1...v4.7.1
Changelog: https://github.com/miguelgrinberg/python-engineio/blob/v4.7.1/CHANGES.md
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

14 packages failed to build:

gdbgui
gdbgui.dist
onionshare
onionshare-gui
onionshare-gui.dist
onionshare.dist
pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
python310Packages.flask-socketio
python310Packages.flask-socketio.dist
python311Packages.flask-socketio
python311Packages.flask-socketio.dist

42 packages built:

appdaemon
appdaemon.dist
home-assistant-component-tests.ambient_station
home-assistant-component-tests.control4
python310Packages.aioambient
python310Packages.aioambient.dist
python310Packages.pycontrol4
python310Packages.pycontrol4.dist
python310Packages.python-engineio
python310Packages.python-engineio.dist
python310Packages.python-socketio
python310Packages.python-socketio.dist
python310Packages.ripe-atlas-cousteau
python310Packages.ripe-atlas-cousteau.dist
python310Packages.sisyphus-control
python310Packages.sisyphus-control.dist
python310Packages.tago
python310Packages.tago.dist
python310Packages.tagoio-sdk
python310Packages.tagoio-sdk.dist
python310Packages.uptime-kuma-api
python310Packages.uptime-kuma-api.dist
python311Packages.aioambient
python311Packages.aioambient.dist
python311Packages.pycontrol4
python311Packages.pycontrol4.dist
python311Packages.python-engineio
python311Packages.python-engineio.dist
python311Packages.python-socketio
python311Packages.python-socketio.dist
python311Packages.ripe-atlas-cousteau
python311Packages.ripe-atlas-cousteau.dist
python311Packages.sisyphus-control
python311Packages.sisyphus-control.dist
python311Packages.tago
python311Packages.tago.dist
python311Packages.tagoio-sdk
python311Packages.tagoio-sdk.dist
python311Packages.uptime-kuma-api
python311Packages.uptime-kuma-api.dist
ripe-atlas-tools
ripe-atlas-tools.dist

Looks like this breaks flask-socketio?
flake-socketio.txt

Looks like this breaks flask-socketio?

Yes, it does.
I guess that I have to do some work on the inputs first, like https://github.com/NixOS/nixpkgs/pull/255732

Already on master.


Cli can't register first master, because no current master can be found

With empty configuration, trying to register my first master, I get a complaint that no current master can be found, followed by instructions to try to register to a master.
> % kontena master login http://X.X.X.X
Running #<Kontena::MainCommand:0x0056302f3ed720> -- callback matcher = 'nil'
Running #<Kontena::Cli::MasterCommand:0x0056302f3d2a38> -- callback matcher = 'nil'
Running #<Kontena::Cli::Master::LoginCommand:0x0056302f41bf30> -- callback matcher = 'master login'
D, [2016-10-27T10:28:47.938554 #1] DEBUG -- CONFIG: Configuration file not found, using default settings.
D, [2016-10-27T10:28:47.938729 #1] DEBUG -- CONFIG: Configuration loaded with 0 servers.
D, [2016-10-27T10:28:47.938753 #1] DEBUG -- CONFIG: Current master: default
D, [2016-10-27T10:28:47.938788 #1] DEBUG -- CONFIG: Current grid: (not selected)
/usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/config.rb:313:in `require_current_master': You are not logged into a Kontena Master. Use: kontena master login (ArgumentError)

-> % kontena version
cli: 0.16.0

Full error stack:
/usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/config.rb:313:in `require_current_master': You are not logged into a Kontena Master. Use: kontena master login (ArgumentError)
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/common.rb:139:in `require_current_master'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/common.rb:179:in `client'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/master/login_command.rb:170:in `block in get_authorization_url'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/common.rb:80:in `vspinner'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/master/login_command.rb:169:in `get_authorization_url'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/master/login_command.rb:212:in `response_from_web_flow'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/cli/master/login_command.rb:55:in `execute'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/command.rb:181:in `run'
	from /usr/lib/ruby/gems/2.3.0/gems/clamp-1.1.1/lib/clamp/subcommand/execution.rb:11:in `execute'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/command.rb:181:in `run'
	from /usr/lib/ruby/gems/2.3.0/gems/clamp-1.1.1/lib/clamp/subcommand/execution.rb:11:in `execute'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/lib/kontena/command.rb:181:in `run'
	from /usr/lib/ruby/gems/2.3.0/gems/clamp-1.1.1/lib/clamp/command.rb:132:in `run'
	from /usr/lib/ruby/gems/2.3.0/gems/kontena-cli-0.16.0/bin/kontena:16:in `<top (required)>'
	from /usr/bin/kontena:23:in `load'
	from /usr/bin/kontena:23:in `<main>'

this occurs even when starting with no .kontena_client.json in use, but it is using the kontena cli docker image.

will test again if made avialable in the kontena cli image.

@james-nesbitt can you try like this: kontena master login --name master http://X.X.X.X

will do.

james@redrum [05:22:30 PM] [~/.local/share]
-> % kontena master login --name kontena-testing http://<IP_ADDRESS>
Running #<Kontena::MainCommand:0x0055bfa9cddf20> -- callback matcher = 'nil'
Running #<Kontena::Cli::MasterCommand:0x0055bfa9cc7158> -- callback matcher = 'nil'
Running #<Kontena::Cli::Master::LoginCommand:0x0055bfa9cc40e8> -- callback matcher = 'master login'
D, [2016-10-27T14:24:16.723411 #1] DEBUG -- CONFIG: Configuration file not found, using default settings.
D, [2016-10-27T14:24:16.723567 #1] DEBUG -- CONFIG: Configuration loaded with 0 servers.
D, [2016-10-27T14:24:16.723591 #1] DEBUG -- CONFIG: Current master: default
D, [2016-10-27T14:24:16.723624 #1] DEBUG -- CONFIG: Current grid: (not selected)
Opening browser to https://cloud.kontena.io

If you are running this command over an ssh connection or it's
otherwise not possible to open a browser from this terminal
then you must use the --remote flag or use a pregenerated
access token using the --token option.

Once the authentication is complete you can close the browser
window or tab and return to this window to continue.

If the browser does not open, try visiting this URL manually:
                                                             https://cloud.kontena.io/login/oauth/authorize?response_type=code&client_id=8da2d19131b340e188d5b8f64adfb3d3&scope=user&state=ba136cb94c771270cf6f9d4be0483300d77cbf20e4e8c6f67cdd50fc09819d21&redirect_uri=http%3A%2F%2F<IP_ADDRESS>%2Fcb

      Waiting for connection on port 42219..

OK I think that I managed to get the login to work.
First I had to also add the --remote,
then the code that was given to me from the kontena web UI was incorrect:
 kontena master login --code {code{&server_name={name}

Should have been:
 kontena master login --code={code} name={name http://X.X.X.X

feel free to mark the issue as closed, if you think that having a --name as required is expected behaviour.

No, the issue  is real and fixed now in the referenced PR.


Disable load of pervious months

I do not want the user to be able to scroll to the pervious months - just the current and/or future months.
Current behavior:

A User can view pervious as well as future months

Expected behavior:

A User can only view current month with future months

You didn't read the README or test the example project: https://github.com/jonathantribouharet/JTCalendar#questions
You just have to implement canDisplayPageWithDate method.
https://github.com/jonathantribouharet/JTCalendar#pagination


Feature/acollow/#11 initialedits

This PR contains initial edits that we needed to get QFEDv3 to run properly and closes #11 . The emission factors for trace gases were also updated, closing #14.

@acollow please make a PR to develop, not main.


Add Learn Git Branching

On the Learn Git Branching repo, they briefly talked about how the website work including levels and sandbox mode. Furthermore, Learn Git Branching is an open source project, if students are interested that can contribute to it.
I will also update the README.md file with the new topic. Question: Should git branching be put as a subtopic of gitflow?

Add Git branching as a sub-branch on Git Flow under readme.md
Add reasons why I provided Learn Git Branching Github repo under development_process.md

Add git commands

According to A3,

Contributors: You can sign up to contribute to one or two topics related to software engineering. These contributions can be a Pull Request for any of the following:
a. Creating new entries, pages, links and address a new topic
b. Editing existing entries
c. Reorganizing to clarify, simplify, or break down topics

FAQ
1b. Do I have to write the contribution all myself?
No. You can link to an external source and write a few sentences summarizing how it helps a CSC301 student. As long as it’s clear that you’re not claiming to have done someone else’s work, you are fine.

Our contribution can be any of the following, including links, and it does not require an expansion on the topic. As expansion on the topic can be contributed by other students. In my pull request, I have explained why the link I provided can help CSC301 students, therefore, going over the concepts covered in the site will not be necessary.
Please feel free to let me know if my understanding for the assignment is incorrect.

According to the lecture and the assignment handout, the topic should be first come first serve. I am the earliest person in the whole class to signup, create pr and made changes right after a request is issued. Therefore, whoever that come after me should be responsible for contributing something different. Therefore, it would not be fair for me to change my topic.
I am willing to resolve repeated topic with people that sign up later than I am and even suggest other topics for them to contribute. However, I will not change my topic as the responsibility should not be on my end.


App Service: Domain CRUD

Known issue: javadocs missing
Justification: generated code is failing checkstyle. Will fix after AutoRest refactoring is done.

Can we merge this yet? The country codes are useful for CDN too.


[Feature] Documentation Feature

Summary
Enabling component states to all have their individual documentation. This will most likely be through markdown and the markdown_widget package.

https://github.com/GetDutchie/flutterbook/pull/4 check this out

Addressed this on #12


fix theme

anchor looks awful

tailwind is paid more or less
tried vuetify 3 again. it works. just need to redo the pnpm update
their create didnt work properly. plus package.json type:module


merge /source into /od and /software-service

/source was where OD and OSSD files where, but they now mostly duplicate what is under /od and /software-service. Seems /source should go away, and /od where versions, tranaslations etc should be committed to minimize barrier to deployment.

Seems a good idea. @mlinksva are you happy to implement?


css class au-animate breaks repeat.for re-rendering

See this plunker for css class au-animate breaking repeat.for re-rendering.
http://plnkr.co/edit/F65cUaS7qFxgETSf5Wjn

@zewa666 @martingust Can you guys look into this?

This will get fixed with https://github.com/aurelia/templating-resources/issues/112


Don't need to lock in initialization

This was meant to go into a previous commit (thanks @jparise).

:+1:


vutur更新后 总是停止工作

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T08:03:11.395Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author
Version

stylus
Alan
0.0.4

|project-manager|alefragnani|0.15.0|
|vue-snippets|hollowtree|0.1.1|

|vscode-lebab|jeremyrajan|1.0.1|
|vscode-JS-CSS-HTML-formatter|lonefy|0.2.3|
|vetur|octref|0.6.1|
|vscode-docker|PeterJausovec|0.0.13|;

Steps to Reproduce:

This issue should be filed against Vutur @octref

@18267372741
Try 0.6.2 first. There are still one server crash issue that hasn't been resolved yet https://github.com/octref/vetur/issues/131
@rebornix You can close this I think.


.java and .class file showing same icon

Hi,
Since .java and .class showing same icon, it is little confusing while opening the file. Please add the different icon for .class file.
would be great if the icon for .class file similar to link below
http://fileinfo.com/img/icons/files/128/class-737.png

I think we should consider having diff icons for .java, .class and .jar.

Do you have a idea for the color combos? I don't have any idea...

In matter of fact, I do. Will provide samples, as I'll work on them on the weekend.

So here is my proposal for the Java related files.
jar
java
class

I'm fine with it.

I really like it 💯 👍 😁

Perfect.

I agree just perfect.


erf implementation (numba/nopython compatible)

Error function which jit compiles and accepts an np.array input, with tests.

Awesome, thanks!
Do you want to remove erf from the todo.md and add a bullet under New Features in the releases.md? Would be good to add GH#2 to that bullet as well.

Don't worry about the test failures, i've added scipy support in #3 which we'll merge afterwards

Looks good, thanks very much!
A couple of minor tweaks, then definitely good to merge.

Cheers, have committed a couple of tweaks & apols for busting tests with the scipy dependency - start as you mean to go on... :)

Merged, nice one!


Create Test to replicate Developer requesting access to published service

Description
Tests whether developer is able to create an access request to a published service.
Prerequisites

Service must already be created
Application must already be created

Test Steps

Developer navigates to home page, then logs in
Click API Directory
Select a listed API (TODO get test API name)
Click Request Access
Select Application from the dropdown list
Select environment (TODO get env name; should just be dev)
Fill in some text in the comment section (can just be lorem ipsum, or some other random text)
Click submit

** Test Data**

apiowner.json fixture: contains login username and password

Expected Results

Access request successfully created. (TODO add in more details; what is shown when an access request is completed?)

Test case has (mostly) been implemented. Need to finish API owner approving the access request which can be found in 03-api-owner-access-rqst.spec.ts. Need to resolve #227 before continuing.

To raise the request to access the API and to approve the request by Access manger is divided into 2 spec files.Details are as below:
03-rqst-access.spec.ts

authenticates developer
1.1 Developer sign in to application
creates an application
2.1 Developer click on 'Create Application' button
2.2 Enter application name as 'Auto Test App', enter the description and click on Create button
creates an access request
3.1 The user navigate to API Directory page and select 'Auto Test Product' API
3.2 Click on Request Access button
3.3 On New Access Request Page, select 'Auto Test App' as application, select the environment, check the term and condition check box and click on Submit button
3.4 Store the API key to store.json file

04-approve-pending-rqst.spec.ts

approves an access request
1.1 Access Mamager (Mark) sign in the Application
1.2 Switch to 'platform' namespace
1.3 Navigate to Consumers Page under Namespace
1.4 Click on the Application ID
1.5 The user can see the request raised by the Developer
1.6 Approves the Request
1.7 Verify that the status of the application is changed to 'Completed'
Verify that API is accessible with the generated API Key
2.1  Verify that the API returns 200 stats code when call the API with the API Key


added consul -pid-file startup flag

Hi, I added the startup command to create a pid file. Also updated the readme and added a server spec test, hope I didn't miss anything. Cheers

Coverage remained the same at 100.0% when pulling edb4826294c78f198a6ad258d1624ca4e0e292ed on hprotzek:master into 8a66a9f815ac7f1fb6e3e35ed71dce71f3b3c8d1 on johnbellone:master.

Please rebase!

I am closing this out because of impeding #126 landing on master. The pid-file is handled by manager of your choice. Please see poise-service.


Remove mkl depth causing error on creation of conda environment

@srajotte could I ask you to quickly test something for me? It's related to this issue here: https://github.com/joelmoniz/DepthNets/issues/8
If you create a conda environment like: conda env create -f=environment.yml -n depthnet,
does it work for you?
It works on my end on a fresh Ubuntu install, but I just want to double-check with someone else.
Cheers!

Hi Chris,
The fix removes the MKL error on my test system (Ubuntu 18.04 VM). I get an error about a "psi4" package, but it doesn't seem to be related with the fix.


Support enabling color despite output not being a TTY

Please consider supporting FORCE_COLOR: https://force-color.org/ and/or enabling color programmatically.
Use case is some tool that runs in a daemon mode, but the output gets copied to a tty in a roundabout way.

Bump. I bet this would make it work in xcode controlled terminals


Issues with Source maps

I don't have a good repro of this yet (everything seems ok in a small project), but source maps are behaving strangely in our main project.
Example, check out this code:

Line 78 and 79 are "disabled" for breakpoints, even though 76 and 77 are enabled. Trying to add breakpoints by clicking on the line numbers has strange behaviour:

Clicking line 67 puts a breakpoint on line 67
Clicking line 68 puts a breakpoint on line 69
Clicking line 70 puts a breakpoint on line 71
Clicking line 72 puts a breakpoint on line 82
Breaking on line 67 and then pressing Step jumps to labelText on line 82

Additionally, I think that the source maps aren't working for related projects (even when sourcemap is enabled both on the referencing and referenced project), since I only see the .cs files from the main "app" and not our components.
I'll keep trying to get a small repro I can share, but if you have any tips for helping track it down in the meantime, let me know. If I can't get a repro I can share publicly, I might be able to share something privately for you to investigate.

Additionally, I think that the source maps aren't working for related projects (even when sourcemap is enabled both on the referencing and referenced project), since I only see the .cs files from the main "app" and not our components.

Yup, same here.

Here's a (relatively small) repro:
SourceMapsIssues.zip
Build this and open Index.html in your browser. Open the dev tools and open DatePickersPageContainer.cs. Note that some of the lines in the ReactStyle section are disabled while others not and adding brekpoints in this method to various lines results in them jumping to other lines. Stepping through the coed shows similarly confusing behaviour.

We believe this result of clicking on one line and the browser tools setting a debugger on another line is just a quirk of Chrome developer tools. Source Map support is still not perfect.
Firefox seems to handle setting breakpoints better.
We are unaware of a way to fix the Chrome Developer Tools breakpoint setting issue.
Closing this issue, but we can always re-open.


Do not attempt to collapse broken encodings in fields

Without this strings with broken encodings will raise an exception in Encodings.collapse_adjacent_encodings: NoMethodError: undefined method+' for nil:NilClass`

Fixed by #789


126 us change channel create form to socket instead of http

Description
Please provide a detailed description of what was done in this PR.
Precise the issue that you are resolving.
Changes include

[X] New feature (non-breaking change that adds functionality)
[ ] Bugfix (non-breaking change that solves an issue)

Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it.
Checklist

[X] I have assigned this PR to myself
[X] I have added at least 1 reviewer
[X] I have added the needed labels
[X] I have linked this PR to an issue
[X] I have linked this PR to a milestone
[X] I have linked this PR to a project
[X] I have tested this code
[ ] I have added / updated tests (unit / functionals / end-to-end / ...)
[ ] I have updated the README and other relevant documents (guides...)
[ ] I have added sufficient documentation both in code, as well as in the READMEs

Additional comments
Please post additional comments in this section if you have them, otherwise delete it.

Cannot enter password for protected channels


still possible to create copies of pages that exceed their models' max_count

Issue Summary
In Wagtail admin, it's possible to select a page type that has hit its max_count limit (introduced in Wagtail 2.4) and then use the "copy" action in the dropdown menu to create another copy, even though no new pages of the type should be allowed to be created.
Steps to Reproduce

Create a new model derived from wagtail.core.models.Page
Add a max_count = 1 property
In Wagtail Admin, create a page of this type and publish it
In Admin, select the page's More > Copy action, choose a new slug for it
Publish the copy - a new page is created, no error is thrown
Expected behavior: because the existing page meets the max_count limit, an error should be thrown alerting the user that further copies cannot be created

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: no

Technical details

Python version: Python 3.7.2
Django version: 2.1.5
Wagtail version: 2.4
Browser version: Chrome 72

There's no check against max_count in the Page model's copy method, only in can_create_at.

Thanks @phette23 for the really helpful steps to reproduce and investigation.
Fixed with #5115
Merged in https://github.com/wagtail/wagtail/commit/77a8e3b7c08dafa5e18a57ce5e1d8f6ac7d54e1a


Pass status code, headers, from onResourceReceived to page.property('content').then(function(content)

Hello,
with phantom 1.x, i could set a global variable to pass statusCode and headers from
onResourceReceived
Then in the callback of page.content, i could handle error 404, or a redirection.
Now with phantom 2.x, It seems impossible. A variable set in onResourceReceived (even a global), is not available in :
page.property('content').then(function(content){

if(GLOBALVARSTATUS == 200){
  res.send(content);
}else if(GLOBALVARSTATUS == 301){
 ....
}
}

What is the current solution to handle 404, 301 redirect with phantom node 2.x ?

Can you show me the code for 1.x? I don't get how something GLOBALVARSTATUS in the callback would have worked because that's executed in node not phantomjs. Maybe seeing how you were doing it in 1.x could help me.

Here is my full code 1.x :
http://pastebin.com/LbL1UzqD
I am using phantom to render my single page application for Google ... But now that you're telling me it's impossible to share value between onResourceReceived & evaluate , maybe my hack has never worked :s

I took a look. I am not sure that ever did work. :) RESPONSE is executed in the context of phantomjs and the callback for evaluate is executed in the context of nodejs. Those are two different processes. So I doubt it worked.
Back to the real question, what are you trying to do?

PAGE.property('content').then(function(content) {

Here inside I would like to know if it was a HTTP code 200 / 404 / (301 with access to the headers of the request to know to which url it want to be redirected)

});

:)

By it you mean all the resources, right?

The first ressource is enough

I did a quick test and I was able to get it working with this pull request.
However, as you can see, I use eval to evaluate global space. It is really hacky. I am not sure how I feel about it.
See the test case at the bottom to see how to use it. I am not convinced that this is something that should be added :(

See #378. I added new functionality to get back global space properties. I struggle if I want to document this because it really is a hack and I don't think it makes sense for it to be public.

@laurentdebricon any update to this? Does the new pull request work for you?

Hello,
Great ! it's working :
page.property('content').then(function(content) {
       ph.windowProperty('lastResponse').then(function(lastResponse) {
                  // here i have access to lastResponse that I set in page.property('onResourceReceived',

      });
});

package.json devDependencies misses babel-register.
npm install babel-register solve the problem, then npm install build the project (it took me some times :p )
Thank you

What does Babel register do? I have never used it.
Sent via my iPhone

On Feb 23, 2016, at 8:07 AM, Laurent Debricon<EMAIL_ADDRESS>wrote:
Hello,
Great ! it's working :
page.property('content').then(function(content) {
ph.windowProperty('lastResponse').then(function(lastResponse) {
// here i have access to lastResponse that I set in page.property('onResourceReceived',
  });

});
package.json devDependencies misses babel-register.
npm install babel-register solve the problem, then npm install build the project (it took me some times :p )
Thank you
—
Reply to this email directly or view it on GitHub.

I released 2.0.1 so you shouldn't need to build locally anymore.

Great ! Thank you for your work !


PROD SUPPORT: Case name and E-Filing id should have space between

Describe the bug
A minor correction required... there is no space between the case title and filing number. There should be a blank space after the comma (before the filing number).

Hi @rajeshcherukumalli , @Susmitabe , @Ramu-kandimalla
Working fine in UAT
Refer screenshot

signed off

Working as expected
screenshot for ref


New version: NirSoft.Volumouse version 2.15

Pull request has been created with komac v2.8.0 :rocket:

Resolves #201827

Microsoft Reviewers: Open in CodeFlow

cc @ItzLevvie


Unable to run App From Source

Hi,
I'm trying to run the app from the source but not able to run successfully. I followed all the instructions mentioned on GitHub. It doesn't do anything after the below line for a long time:

Any help is appreciated.

Hello,
have you try to open the internet browser and navigate to the page https://localhost:5001 ?
Michal

Thanks @hradilm for your reply. Yes did that already browser opens automatically but nothing happens for a long time. Any other thoughts?

This issue has seemed to have rectified itself & i can get to home screen. When logging in i get the forge authorize application & then login failed image. any suggestions would be appreciated

Hello,
you just modify the value inside the config, see https://github.com/Autodesk-Forge/forge-configurator-inventor/blob/master/WebApplication/appsettings.json#L36
You can change Enable: true to Enable: false
You can do it directly in appsettings.json file, or you can do override in your appsetting.Local.json

@mivasi @hradilm Thanks for your help! greatly appreciated


enhancement on Dark mode

This a fix of the issue #65

please solve the conflict

I have resolved the conflict and made a new pull request.


Make Bytes/Messages Sent/Received public on data channels

Description
BytesReceived, BytesSent, MessagesReceived and MessagesSent are all used to create stats but sometimes you don't want to go through all the stats...
This makes those methods available directly on a data channel
I'm not sure we need to add any tests... they're already tested in datachannel module

Actually, I don't think this is necessary, I've just got this info via GetStats() and it worked well. Let me know what you think

Thanks for the PR @danjenkins!
I don't see these in the W3C docs, so my gut says we probably should not do it. I am afraid if we have inconsistent APIs between implementations that it will frustrate users :(
If the GetStats API doesn't have something you need tell me and I would love to implement it!

I don't see these in the W3C docs, so my gut says we probably should not do it. I am afraid if we have inconsistent APIs between implementations that it will frustrate users :(
If the GetStats API doesn't have something you need tell me and I would love to implement it!
https://www.w3.org/TR/webrtc/#webidl-1143016005

Completely agree. Once I'd realised how to go grab these stats then things fell into place


Add theme switching

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


fix user migration specs

This PR fixes failing tests in CI + some minor fixes in the MFA user export.
@javitonino would you mind doing a quick review?

:heavy_check_mark: Acceptance OK
Tested the user migration with MFA configuration.


CC2652RB: does not work with CC2652RB_coordinator_20220103 or CC2652RB_coordinator_20211217

Hi there,
i've tried updating my slaesh CC2652RB stick from 20210708 to 20211217 or 20220103 but with 20220103 it does not even see any devices - with 20211217 it seems to see the devices but none reacts...
Stefan

Hi @disaster123,
i have updated my slaesh CC2652RB to 20211217 and it is working fine. If the devices (routers) do not respond, remove them from mains power for a few seconds as stated in the FAQ https://www.zigbee2mqtt.io/guide/faq/#what-does-and-does-not-require-repairing-of-all-devices. That workes for me.
Jost

mhm OK - might be an option but a bit strange... will try it in a few minutes... restoring old FW i got alle devices working again immediatly.
Might this be missing nvbackup or something like this?
I used:
c2538-bsl/cc2538-bsl.py -p /dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_23_93_25_A0-if00-port0 -evw CC2652RB_coordinator_20211217.hex

for update.

Log says:
zigbee.1 | 2022-01-18 19:15:46.202 | warn | (813) DeviceAvailability:Failed to ping 0x00124b0022612054 GL-C-006
-- | -- | -- | --
zigbee.1 | 2022-01-18 19:15:46.118 | warn | (813) DeviceAvailability:Failed to ping 0x60a423fffeff1c35 TS011F
zigbee.1 | 2022-01-18 19:15:45.729 | warn | (813) DeviceAvailability:Failed to ping 0x84fd27fffe865141 TS0001
zigbee.1 | 2022-01-18 19:15:45.524 | warn | (813) DeviceAvailability:Failed to ping 0x84fd27fffe812d46 GL-C-006P
zigbee.1 | 2022-01-18 19:15:45.487 | warn | (813) DeviceAvailability:Failed to ping 0x84fd27fffe68e20b TS0001
zigbee.1 | 2022-01-18 19:15:45.369 | warn | (813) DeviceAvailability:Failed to ping 0x842e14fffe15d05e TS011F
zigbee.1 | 2022-01-18 19:15:45.228 | warn | (813) DeviceAvailability:Failed to ping 0x804b50fffe6b6c0b TRADFRI control outlet
zigbee.1 | 2022-01-18 19:15:45.115 | warn | (813) DeviceAvailability:Failed to ping 0xcc86ecfffe8db464 TRADFRI control outlet

OK it really fixes itself after 30 min.... i didn't expect to have to wait so long...


Subcriptions not working

Thanks for creating Jackalope. We try to use it to connect to AWS IOT.
We got it running, but it seems the subscriptions we pass in are not properly passed to Tortoise311
our configuration
  Supervisor.child_spec(
        {
          Jackalope,
          subscriptions: [{"cm/v1/device/+/data", 0}]
          client_id: "cm-mqtt",
          handler: Processor.Handler,
          server: server_opts
        },
        id: Tortoise311.Connection.Parametric,
        restart: :permanent
      )

only after manually subscribing we receive data
Tortoise311.Connection.subscribe_sync("cm-mqtt", [{"cm/v1/device/+/data", 0}])

Just realized going through the code that subscriptions is not supported and that initial_topics needs to be used, which doesn't allow to set QOS level, so a binary array needs to be passed instead of a tuple array like in tortoise.


Vim -> Vim not working in MSYS2 and Cygwin

The tmux plugin doesn't work for systems like MSYS2 and Cygwin because the ps command is much simpler and hasn't got the format options required for the Tmux plug in.
The original line:
is_vim="ps -o state= -o comm= -t '#{pane_tty}' \
    | grep -iqE '^[^TXZ ]+ +(\\S+\\/)?g?(view|n?vim?x?)(diff)?$'"

fails in MSYS2 and Cygwin because the native ps command does no support -o or -t.
I have fixed it with the following line:
is_vim="ps -a |grep -q '.*''#{s|/dev/||:pane_tty}'' .*vim$'"

which works on both MSYS2 and on my Ubuntu systems. The command relies on the tmux variable substitution to remove the /dev/ from the pane tty name and then greps for a tty name and vim from the ps output. It doesn't do the same process state filtering that the original does but that info is not available in the MSYS2 and Cygwin ps command.
It might be worth considering if this is a more generic cross platform solution.

Here's the extended is_vim line with the regex to cover the variants of the vim name as per the original:
is_vim="ps -a |grep -qE '.*''#{s|/dev/||:pane_tty}'' .*+(\\S+\\/)?g?(view|n?vim?x?)(diff)?$'"

Hey @pnetherwood, thanks for the detailed notes and the suggestion. I'm generally very conservative with changes to the core vim matching logic, but this seems straightforward enough and should improve portability, so I think it sounds like a worthwhile change.
Would you mind turning this into a PR, updating the reference to the snippet in both the README and the tmux plugin manager version?

Hmm, so I'm running with this update locally and it doesn't seem to work, specifically the Vim detection portion. I'm running nvim, so I'm guessing it has to do with the grep pattern, but this gives me a bit more pause in moving to this. Any thoughts?

What platform are you on? Does the output of ps -a include the tty?
Since there is no -t for the ps command on MSYS2 I just add the pane tty to the grep but strip out the /dev/ part using tmux variable substitution. Try this in a shell inside tmux to test:
tmux run-shell "echo '#{s|/dev/||:pane_tty}'"

You should see a tty name that should in the the ps -a list. We can grep out the current pane's tty from the list using.
tmux run-shell "ps -a |grep -E '#{s|/dev/||:pane_tty}'"

The grep pattern is then extended to have the second part of the original grep.
Try running this from nvim inside tmux from the nvim command line:
!tmux run-shell "ps -a|grep -E '.*''\#{s|/dev/||:pane_tty}'' .*+(\\S+\\/)?g?(view|n?vim?x?)(diff)?$'"

(Note I've escaped the # so it can run from vim).
You should see the output from the ps command for the nvim session that you are running if it succeeds.
This is what I used to debug it but I've only tried it in MSYS2 and on Ubuntu.

I've figured out the issue with this. It relies on tmux substitution format which needs to be in this form: s|/dev/|| to avoid conflicts with /. This appears to be only available in later versions of tmux and I'm using version 3 on MSYS2 and Ubuntu.
So if you run
tmux run-shell "echo '#{s|/dev/||:pane_tty}'"

on tmux 3 you get the tty without the /dev/. On other earlier versions you get no output.
So minimum requirement for this PR is Tmux 3.0 so should not be merged unless a work around can be found perhaps using sed.
You could point people to this PR if they are trying to get it to work on MSYS2.
It works fine on WSL as its ps command supports -t.


Highlight node more explicitly when selected

This just changes the color when you select a node either through click or search. Before it wasn't as obvious. Now it's a brilliant shade of green!

+1


record xds send time

Added stat for recording xds send time
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
d9ce755555ff1c2387748dc8b49454f7949e0b09
link
/test unit-tests_istio

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

/test unit-tests_istio


Update test to accommodate new text change in "minishift delete"

Looks like there is change of text in minishift delete src:
$ minishift delete
Currently no Minishift VM defined.

Previously it was "Does Not Exist".

So, it seems that the status command still have message "Does Not Exist".
Hence, this issue is not required.


rustic crashes with misaligned pointer dereference: address must be a multiple of 0x8

[00:00:00] backing up...                  █████████████████████░░░░░░░░░░░░░░░░░░░ 326.07 MiB/592.87 MiB 1.76 GiB/s   (ETA 0s)                                                              The application panicked (crashed).
Message:  misaligned pointer dereference: address must be a multiple of 0x8 but is 0x7fb16201f40d
Location: /Users/kptsky/.cargo/registry/src/index.crates.io-6f17d22bba15001f/nix-0.27.1/src/unistd.rs:3794

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
thread caused non-unwinding panic. aborting.

already fixed upstream: https://github.com/nix-rust/nix/pull/2311
We are waiting for the fix in the nix crate to be published...

We are waiting for the fix in the nix crate to be published...

Nix 0.28.0 released

Tested and indeed the issue is gone. Thank you!


Reduce boilerplate from test fixtures

Use list comprehensions in tests to make them more succinct.

@briantkennedy I only cleaned up a few, but assuming this pattern looks good to you I'll role it out to the other tests. Should reduce repetition in tests substantially and make them more readable.


Fix mistyped GameStepTimer_NoSlowTime offset

In 9d3a598 the NoSlowTime offset is changed from 0x02f6b94c to 0x02F6894C, which seems like a mistake (B -> 8).
Even though NoSlowTime isn't used anywhere, I figured it's still good to fix it.

Yeah that was actually a typo. I've removed that offset now since its unused. Thanks though.


RSA key size not used when selecting shared signature algorithms

If a TLS 1.2/1.3 client sigalgs lists sha512_rsa_pss before sha384_rsa_pss and sha256_rsa_pss then the OpenSSL server will select sha512_rsa_pss even if the RSA key in the X.509 certificate is only 1024-bit.  The server aborts the session with an "internal_error" alert (80) and dumps the following error:
140217200965440:error:0409806E:rsa routines:RSA_padding_add_PKCS1_PSS_mgf1:data too large for key size:crypto/rsa/rsa_pss.c:192:
140217200965440:error:141EC044:SSL routines:tls_construct_server_key_exchange:internal error:ssl/statem/statem_srvr.c:2473:

that's probably because you should use 2048 bit keys nowadays.


Wrong emit on complex LuaTuple $dbg

Basing off of the example in the readme:
function test() {
	return 10;
}
const value = $dbg(test());

local function test()
	return 10
end
local value = (function(value)
	print("[source.ts:4] test() =", value)
	return value
end)(test())

will be wrong if test returns a LuaTuple, only catching the first element of it. This should be easy to change, albeit with a performance hit, by using ...values.

Could also have a check for that particular macro symbol and adjust the emit accordingly :?
Not sure how tough that'd be from a transformer perspective, but yeah.


Fix compile error when LNW_VERSION=2

Do the included files change based on the version? I dont see any #ifdef wrapped around for different versions - can you clarify

I see that the changes only go into the lnw-v2 directory of relevant files.

Do the included files change based on the version?

LNW_VERSION causes both a cmake conditional and a C conditional to be defined (LNW_V2 or LNW_V3).
It is applied by means of:

#ifdefs in the C/C++ source files,
Selecting the version-specific subdirectory in switchapi/es2k/CMakeLists.txt.


Always shut down the tokio runtime before exiting zebra

Scheduling
If #3133 removes all the calls to app_writer().shutdown(), then we don't need to do this task until the lightwalletd work.
Motivation
After we fix #3133, we might need to shut down the tokio run time before the Zebra abscissa application shuts down. This avoids a potential security issue where the tokio runtime threads are forced to shut down without cleaning up properly.
APIs
https://docs.rs/abscissa_core/0.5.2/abscissa_core/component/trait.Component.html#method.before_shutdown
https://docs.rs/abscissa_core/0.5.2/abscissa_core/application/trait.Application.html#method.shutdown

This seems to be covered by PR #3133. If we find this kind of bug in other code that shuts down Zebra, we should open a specific ticket for it.


$firebaseStorage and fir-storage-src proposal

@jwngr @katowulf @abehaskins
This issue addresses two features

$firebaseStorage() service
fir-storage-src directive

$firebaseStorage
Here is my proposal for the $firebaseStorage() API, written in TypeScript:
You'll notice that is follows the same binding convention as $firebaseObject(), and $firebaseArray(), as both of those services take a database reference. $firebaseStorage() is similar but it takes a storage reference.
The piece of feedback I'm most looking for is surrounding the events for the $put() method. I've currently wrapped each function of the state_change event into a method, $progress, $error, and $completed.
interface $firebaseStorage {
  (ref: firebase.storage.Reference): FirebaseStorage;
}

interface FirebaseStorage {
  new (storageRef: firebase.storage.Reference);
  $put(File): UploadTask;
  $getDownloadURL(): Promise<string>;
  $getMetadata(): Promise<Object>;
  $updateMetadata(): Promise<Object>;
}

interface UploadTask {
  $progress: (Object) => (); // Can't be a promise
  $error: (Error) => (); // Should this be a promise?
  $complete: (Object) => (); // Should this be a promise?
}

Here it is in action:
function MyCtrl($firebaseStorage) {
  // Create a reference (possible create a provider)
  const storageRef = firebase.storage().ref('user/1.png');
  // Create the storage binding
  const storageFire = $firebaseStorage(storageRef);

  // Get the possible download URL
  storageFire.$getDownloadURL().then(url => {

  });

  const file = // get a file;
  // upload the file
  const task = userImage.$put(file);
  // monitor progress state
  task.$progress(metadata => console.log(metadata));
  // log a possible error
  task.$error(error => console.error(error));
  // log when the upload completes
  task.$completed(metadata => console.log(metadata.downloadURL));

  // meta data
  storageFire.$getMetadata(metadata => console.log(metadata));
  storageFire.$uploadMetadata({
    cacheControl: 'public,max-age=300',
    contentType: 'image/jpeg'
  });
}

fir-storage-src
To make displaying images from Firebase Storage simple and adhere to the security model I recommend we develop a directive that retrieve's the download url and set's the src attribute of the image:

If you're interested in seeing this in action, I've written a demo app here.

Hi David, could it be possible to upload flexchat src into github? Kind of fans have human rights?

No problem @davidrensh! I've been developing it on github since the beginning.
https://github.com/davideast/flex-chat

Can you expand a bit on how you would const file = // get a file; in angular? If this is complex we might consider including this as part of the service or as a directive somehow.

@abehaskins Yes, this is not trivial. I think we could include a small FileUploadDirective. Which would work like this:
<file-upload on-change="$ctrl.myChangeCallback">
    My Upload Label
</file-upload>

And the code works a bit like this:
function FileUploadDirective() {
  return {
    restrict: 'E',
    transclude: true,
    scope: {
      onChange: '='
    },
    template: `
      <input type="file" name="file" id="firebase-storage-file-upload" class="inputfile" />
      <ng-transclude></ng-transclude>
    `,
    link: function (scope, element, attrs) {
      element.bind('change', function () {
        scope.onChange(Array.from(element.children().files));
      });
    }
  }
}

const app = angular.module('app');
app.directive('file-upload', FileUploadDirective);

Sorry this isn't as nice as David's proposal.
What if we also made a FirebaseStorageFile directive and a $firebaseStorageFile service  (not convinced this is idiomatic, but just an idea)
It might look like...
<input
  type="file"
  firebase-storage-file="/photos/goat.png"
  ng-model="fileRef"  />

<button
  ng-click="fileRef.$put()">
  Upload
</button>

I imagine  $firebaseStorageFile to be a lot like $firebaseStorage except...
It is initialized with a storage ref or a $firebaseStorage instance. At initialization it fetches the blob data from the URL and makes it accessible via $getData().
var fileRef = new $firebaseStorageFile(storageRef.child("photos/goat.png"));

// Pass fileRef.$getData() around for raw data
// ...or use fileRef.$getDownloadUrl() for img tags

Local data can be changed via $setData()  (this is what our FirebaseFile directive will call) which influences $getData() and $getDownloadUrl() but does not upload to Firebase Storage until $put() is called.
var fileRef = new $firebaseStorageFile(storageRef.child("photos/goat.png"));
var url;

// Initial load of URL uses Firebase Storage public URL
url = $fileRef.$getDownloadUrl();

// User selects new file
$fileRef.$setData(NEW_FILE)

// Gets reader.readAsUrl() i.e. base64 version for local previews and such
url = $fileRef.$getDownloadUrl();

// Save to Firebase Storage
$fileRef.$put();

// Gets public Firebase Storage URL
url = $fileRef.$getDownloadUrl();

If put() is called without arguments it uploaded the data from $setData() if it's called with with a new file it will act the same as the underlying Storage ref and call $setData() locally.
We can easily do things like loaded() with a $firebaseStorageFile() since we'll be loading it on init then all future loads will likely be cached we can help users display loading prompts and such.
I think adding this would give developers a lot of power to interact directly with files with minimal code. It's definitely a simpler path for them with the underlying services still exposed if they need more control.
Thoughts?

any ETA if this will be added  to the angularfire ?

@CyrusZei Still hashing out a good solution.
I'm starting to wonder if even AngularFire is the best spot for Firebase Storage. Should this functionality live as it's own module? Not everyone will need storage support and you can build the Firebase SDK without storage included to save kbs.
Thoughts?

well, my thoughts I think that it would be great if there was one module that had all the functions that firebase offers instead of adding more modules and keep track of two modules.

While one module is easy, it adds extra and possibly unneeded size to the library. This size is an extra burden over the networks making the page load of a site slower. Using a standard convention it should be easy to include the needed modules.
const app = angular.module('app', ['firebase' ,'firebase.storage']);
``

yes, I was more thinking about version control ?, but I understand what you mean

I think I have a solution that makes everyone happy. We need to start breaking out functionality into specific modules for library size, but we could still expose the "firebase" module for convenience.
If you want individual modules:
const app = angular.module('app', ['angularfire.auth', 'angularfire.database', 'angularfire.storage']);

If you want everything
const app = angular.module('app', ['firebase']);

Thoughts?

that is really great thought! I like that alot

The determining factors for whether they share a repo or get their own should be:

Do they have a lot of overlapping code? Will splitting them result in redundancy? (maybe, see below)
Are they always used together, such that separating them simply means two install steps? (maybe, see below)
Are they logically the same thing? (not really)
Is the project of sufficient scope and size to bother splitting them because of testing or code management? (not really)
Are they likely to diverge in the future? (not really)

Client library size could be managed by simply creating optimized releases as part of a build process. This shouldn't really a big factor in whether they are included together.
One thing to consider is that Auth is needed by both Storage and Database. Storage also has an optional dependency on Database (It's likely meta data would be stored in the database since Storage can't list, track, categorize, or store meta in any way itself.).
We could also argue that Auth indirectly needs Database, since we have the same issue as Storage--it can't independently store meta data, lists, or any useful organization of users.
So the logical dependency arrangement in my mind looks something like this:

Given this, my though is that would should ideally include them together. If that seems impractical because of difficulty managing them as one entity, or because of testing or other real-world constraints, then Auth and Database should remain AngularFire and Storage should be considered as a "pluggable module" for the lib and maintained separately.

@davideast at the Angular/module level, yes, definitely do this.

@katowulf Agreed. They still belong in the same repository, but different modules are now needed with the 3.0 SDK changes.
I opened up an issue to address this specifically as to not detract from the Storage spec discussion.
#799

when is AngularFire 3.0.0 being released? can I surely expect storage referece wrapped in it?

+1

?
2016-08-21 4:59 GMT-03:00 Juan David Nicholls Cardona <
<EMAIL_ADDRESS>
+1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/angularfire/issues/785#issuecomment-241244246,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUAsAJ_2d-GoqCGkoJJQVI0A_gzBFAY3ks5qiAVOgaJpZM4I02I4
.

I ported firebase storage upload example(https://firebase.google.com/docs/storage/web/upload-files) to a factory:
https://gist.github.com/tianweiliu/6594f6cc09d0e5a3ef6c704db6d2f97a

Just as a note to those following along on this thread: @davideast is going to be putting together docs for the new Storage features and, once those are ready, we will cut a 2.3.0 release. Give us a little bit more time before we can get this into your hands.

I ported other example of the firebase storage upload https://gist.github.com/jdnichollsc/5ddc40c1c482e6209a8f4d634fd11d1e
Regards, Nicholls

AngularFire 2.3.0 has now been released, which includes $firebaseStorage:
https://github.com/firebase/angularfire/blob/master/docs/reference.md#firebasestorage


Implement a unary operation helper to apply unary operation on Money's generic type

added unary operation helper to check whether the unary operations can be performed on a specific type.


QMSI v1.1.0  ALPHA  drop

This pull request brings QMSI v1.1.0 ALPHA code drop and updates the README file.
What is pending after this:

Update the Known Issues section
Link to new toolchain release and also to new ISSM when they go out
Update flashing instructions for Quark SE Devboard

THIS IS AN ALPHA RELEASE!

you should remove all those whitespaces in the license headers   :)

Will do.
From: Anas Nashif<EMAIL_ADDRESS>Sent: Wednesday, May 11, 2016 12:55 PM
To: 01org/qmsi<EMAIL_ADDRESS>Subject: Re: [01org/qmsi] QMSI v1.1.0 ALPHA drop (#6)
you should remove all those whitespaces in the license headers :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com/01org/qmsi/pull/6#issuecomment-218437702
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.

Can we squash all README changes together?
Also I think we should be inline with the release notes released with ISSM.

@nashif @plmorale I think the white spaces were inserted by the pack_bsp.py script . I will have a look.
@plmorale I can squash the README changes if you want. I was just making it easier for you to reviews the changes. :)  I used the release notes from ISSM and basically copied what we needed from there into our README.md . It's a very manual process. Actually, ideally we would have one being generated from the other or we could just have our README.md linking to some online documentation somewhere. I just don't think a .docx file is the best media for that, to be honest.

You have files from 1.0.1 that are not part of 1.1 anymore still in the tree, for example: qm_scss.c. this file was removed in 1.1

@nashif @plmorale  I just fixed it now. Can you please have another look?
The commits for the README file were squashed as requested.

For the sake of documentation, this Pull Request is currently pending on a newer toolchain release.
@plmorale should I just merge it ?


Review dependantRoot usage

Motivation
General clean-up, drop the need to have an intermediary event and re-use code from findAttesterDependentRoot
Description

Generalize findAttesterDependentRoot to support previous epoch and current epoch
Use getDependantRoot to compute the head event dependant roots
Cache shuffling dependant root and re-use in API
Make dependantRoot hex in API to prevent unnecessary type conversions

@tuyennhv testing this branch with
lodestar.js dev --startValidators 0..7 --api.rest.enabled --api.rest.api '*'

I get a lot of logs for re-orgs so some logic must be wrong somewhere between the validator consumer or beacon node producer. For every slot after epoch > 0
Eph 1/0 0.061[]                 warn: Potential next epoch attester duties reorg slot=8, dutyEpoch=2, priorDependentRoot=0xdca272c39cb493f10e3c400af6267632a78172f6636894d0e6166d25d8cca104, newDependentRoot=0x8649261fe405bcf7672e12d1b1a3e29aae3be28d228204d108af49c42bc6d87f

and for every slot after epoch > 1
Eph 2/0 0.046[]                 warn: Potential current epoch attester duties reorg slot=16, dutyEpoch=2, priorDependentRoot=0xdca272c39cb493f10e3c400af6267632a78172f6636894d0e6166d25d8cca104, newDependentRoot=0x8649261fe405bcf7672e12d1b1a3e29aae3be28d228204d108af49c42bc6d87f

would you mind taking a look? I don't want to create a regression for the issue at https://github.com/ChainSafe/lodestar/issues/3211

Closing for separate PRs

https://github.com/ChainSafe/lodestar/pull/4556
https://github.com/ChainSafe/lodestar/pull/4555
https://github.com/ChainSafe/lodestar/pull/4554
https://github.com/ChainSafe/lodestar/pull/4553


Incomplete

{{Fill in the Synopsis}}

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

ID: d3fcee46-c430-0e9d-25a5-5020313a5e98
Version Independent ID: 315379f1-45a4-b0fe-f40d-abeb927df059
Content: Remove-SPAccessServicesDatabaseServer (sharepoint-server)
Content Source: sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAccessServicesDatabaseServer.md
Product: sharepoint-powershell
GitHub Login: @techwriter40
Microsoft Alias: kirks

@officedocsbot assign @yogkumgit

Thanks for reporting!

@get-itips  Thank you very much for the contribution and updating the documentation with PR. @hwkwicre Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Chart reordering

in the user performance chart this week is towards left, it should be to the right ideally

Yes, it should have been in increasing fashion


Manually update version number to test autodeploy to dev instance

Change Description:
see above and attached GH ticket
Closes GH(s):
GH-159
UW-Directory Pull Request checklist

[x] I have run poetry run tox
[x] I have selected a semver-guidance: label for this pull request (under labels,
to the right of the screen)

deleting because I need to set a version in pyproject.tom AND set semver guidance to minor.


Reqs data

Summary
Added requirements data to all colleges and an additional 7 majors.
Requires testing to make sure no errors from DB changes and incorrect requirements.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: einc:x: bhong0423You have signed the CLA already but the status is still pending? Let us recheck it.


controller node create

Opening this issue to discuss if is it right to create the entity and the node in the same node controller call.
I see some better solutions:

The web interface call the entity api and the node api
Create a new route, like diagramOperation and implement the calls for the controllers

This is resolved since the frontend call two apis:

Create the entity
Create the node


wpa_cli does not work out of the box with live CDs

Getting the network working when installing NixOS is very important.
However when booting from at least the minimal ISO you cannot configure the wireless network from wpa_cli.  Instead you are greeted with the error:
Could not connect to wpa_supplicant: (null) - re-trying.
One work around is to add the following line to the /etc/wpa_supplicant.conf file:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
And then do
systemctl restart wpa_supplicant.
It would be good if the /etc/wpa_supplicant.conf file on the live CD already contained this stanza, or better yet, if wpa_supplciant was compiled to include ctrl_interface support even without a wpa_supplicant.conf file.

I tested this a few months ago and it works. Reopen if the problem persists.

I hit this problem with the image I just pulled downloaded from the the official website. Editing the wpa_supplicant.conf hasn't solved this for me yet.

I worked around this problem by using a different wi-fi network. The one I was using has one of those web interface sign-in's after you attach to the network to actually gain access to the internet at large.

@ajl-ewp wpa_supplicant are only used to connect to a wireless network. Any sign-in page is used only once you are connection to the wireless.


Add ignore capabilities for creating indexes and helper functions

This PR responds to issue #39 with support for ignoring sources and/or releases based on the presence of an .aresIndexIgnore file in the respective folder.
Additionally, there are two helper functions getIgnoredSources and getIgnoredReleases that will allow a user to display the list of sources and releases that will be ignored when creating the various indexes.

Closing to merge onto develop branch.


Can't sync column from source on complex queries

I can't use "sync column from source" on virtual datasets whose query doesn't start with SELECT.
Expected results
Whatever my query is, I should be able to sync column from source for my virtual datasets.
Actual results
When my query starts with SELECT, there's no problem.
When my query start with "WITH" statements :

I can create a virtual dataset using the "EXPLORE" feature in SQL Lab
I can't update it and sync columns from source : I get the "ONLY SELECT STATEMENTS ARE ALLOWED" error

I'm forced to re-run the query in SQL Lab, and save is over the previous virtual dataset
What's more, contrary to the previous version of superset (0.x.x), the time columns are not detected, but this seems to be a different issue.
Screenshots

How to reproduce the bug

Run a query in SQL Lab starting with a "WITH" statement
Click on Explore and create a virtual dataset
Go to dataset, update the query (you can add/remove/modify a column, anything works, even a mere filter)
Save
Click on 'Sync Columns from source' (it should get your new column list)
See error

Environment
(please complete the following information):

superset version: 1.0.1
python version: 3.7.9
node.js version: doesn't apply, I run on Kubernetes, using gunicorn as server
source : Athena

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Nothing to report

Taking a look.

I tested with a simple query and it worked:
WITH RAW AS (SELECT name, color FROM bart_lines)
SELECT * FROM RAW

We've had problems in the past with our SQL parser not being able to identify CTEs as SELECT statements correctly, and I fixed a few of them lately:

https://github.com/apache/superset/pull/16769
https://github.com/apache/superset/pull/17654
https://github.com/apache/superset/pull/17329

I suspect the original SQL that triggered this problem fell into this category.
@ValentinC-BR I'm going to close the ticket, but feel free to reopen if you can still repro it — if I have the SQL of the virtual dataset I can fix it.

My bad, it didn't come from queries that don't start with SELECT, but with queries with comments.
.
It seems that the comments (-- MY COMMENT HERE) are not well supported.

The title of this issue could be changed, as it is not related to complex queries.

No worries, sorry for the delay, this ticket fell under my radar.
If the problem was comments then https://github.com/apache/superset/pull/16769 should fix it. :)


rules_oci support

Description of the problem / feature request:
support rules_oci images substituting images into a k8s_deploy.
Feature requests: what underlying problem are you trying to solve with this feature?
rules_docker is deprecated and in minimal maintenance mode. rules_oci appears to be its successor. It would be great if we could support rules_oci.
While rules_oci is the successor to rules_docker, it's not a drop in replacement, so it will be a non-trivial and breaking change.
It's unclear whether a fork is the right answer in the short term until all the users of rules_gitops move away from rules_docker and move to rules_oci.
Let me know if this is something people are thinking about.

Hi @DolceTriade !  This is definitely something we are thinking about -- we've started https://github.com/fasterci/rules_gitops
as the successor to the current iteration of rules_gitops and are planning support for rules_oci there (https://github.com/fasterci/rules_gitops/pull/1).  Contributions are welcome so please join us there if you want to participate

Great, will do!


fix daemon bug

Fix It
https://github.com/alipay/sofa-tracer/issues/26

Pull Request Test Coverage Report for Build 33

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 46.85%

Totals

Change from base Build 29:
0.09%

Covered Lines:
2060

Relevant Lines:
4397

💛  - Coveralls


changing height after element was out-of-screen

I have a vertical-collection where the hight of the items can change between two states with different hights.
I use alwaysRemeasure=true and defaultHeight=50, which is the smaller height.
Now when I change an item to the tall state and scroll it off-screen SAM sets min-height: 200px;. The tall state actually is 200px tall. But when I scroll the item back into the viewport the min-height remains 200px, and I can't change the state back to the small state.
So basically the items can only get larger and larger. 😢
I think SAM should set the min-height back to the defaultHeight when an items gets back into the viewport, and then again remeasure when it leaves the viewport again.

I just ran across the same scenario - 👍 for a fix on this.  I'd be happy to submit a PR given some direction toward the right area of the code to look at.

I'm pretty sure we just have to insert something like this.element.style.minHeight  = this.get('defaultHeight') in the right place in the vertical-item component. But this needs further investigation.
@runspired would you accept a PR? Then I could maybe spend some time investigating this.

Should be fixed by updating to @html-next/vertical-collection (now re-exported by this lib)


bumb go version on waldo CLI

custom request

we use your CLI to upload builds, and it seems its using an old go version that has known vulnerabilities. Are there any plans to update the CLI?


Fix: conman - force conman user gid and uid

Force conman user uid and gid, to prevent read/write issues in active passive HA context.

Since @neilmunday is working on Suse for next release, you should drop OpenSuse test for now.


Merge 0.5.9

support starRocks Transformer

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

approve


[Bug] Cannot fetch IMAP messages

Hi, I use IMAP to test one email account. After setting the configuration and solving the tls problem. Finally, envelope list only work for 1 mail which send/receieve by my self.
you can see from the output: 1
2024-12-10T09:44:07.320899Z DEBUG email::email::envelope::list::imap: found 1 imap envelopes

| ID               | FLAGS             | SUBJECT            | FROM                      | DATE                              |
|------------------|-------------------|--------------------|---------------------------|-----------------------------------|
| 1242             |                   | Hihi               | Chuannan Zhang            | 2024-12-10 17:26+08:00            |

Bug
Next I send a test email (with only 'test' body) from gmail/output. And himalaya return error. Seems it successfully links to the INBOX and finds exists(2) with the incoming mail. But it cant resolve the IMAP task.
2024-12-10T09:39:22.663292Z DEBUG keyring::service: define global service name name="himalaya-cli"
2024-12-10T09:39:22.670467Z  INFO himalaya::email::envelope::command::list: executing list envelopes command
2024-12-10T09:39:22.672094Z DEBUG email::imap: building 1 IMAP clients
2024-12-10T09:39:22.680882Z DEBUG client::build: rustls::client::hs: No cached session for DnsName("imap.qq.com")
2024-12-10T09:39:22.681651Z DEBUG client::build: rustls::client::hs: Not resuming any session
2024-12-10T09:39:22.736403Z DEBUG client::build: rustls::client::hs: ALPN protocol is None
2024-12-10T09:39:22.736420Z DEBUG client::build: rustls::client::hs: Using ciphersuite TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
2024-12-10T09:39:22.736720Z DEBUG client::build: rustls::client::tls12: ECDHE curve is EcParameters { curve_type: NamedCurve, named_group: secp256r1 }
2024-12-10T09:39:22.736729Z DEBUG client::build: rustls::client::tls12: Server DNS name is DnsName("imap.qq.com")
2024-12-10T09:39:23.102235Z DEBUG client::build: email::imap: using password authentication
2024-12-10T09:39:23.102304Z  INFO client::build: process::command: run shell command cmd="pass show qqmail"
2024-12-10T09:39:23.102314Z DEBUG client::build: process::command: inherit stdin from parent
2024-12-10T09:39:23.102320Z DEBUG client::build: process::command: stdout piped
2024-12-10T09:39:23.102324Z DEBUG client::build: process::command: stderr piped
2024-12-10T09:39:23.342150Z DEBUG client::build: process::command: shell command gracefully exited code=0
2024-12-10T09:39:23.342386Z DEBUG client::build: email::imap: supported auth mechanisms mechanisms=[Plain, Login, XOAuth2]
2024-12-10T09:39:23.342401Z DEBUG client::build: email::imap: trying auth mechanism… mechanism=Plain
2024-12-10T09:39:23.589632Z DEBUG client::build: email::imap: authentication succeeded! mechanism=Plain
2024-12-10T09:39:23.591261Z  INFO email::email::envelope::list::imap: listing IMAP envelopes from mailbox INBOX
2024-12-10T09:39:23.591714Z DEBUG email::imap: client 1/1 is free, locking it
2024-12-10T09:39:23.592300Z DEBUG email::email::envelope::list::imap: UTF7-encoded mailbox name="INBOX"
2024-12-10T09:39:23.713906Z  WARN select_mailbox{client=1}: imap_codec::response: Rectified missing `text` to "..."
2024-12-10T09:39:23.713993Z DEBUG email::email::envelope::list::imap: mailbox selected name="INBOX" data=SelectDataUnvalidated { flags: Some([Answered, Flagged, Deleted, Draft, Seen]), exists: Some(2), recent: Some(0), unseen: Some(1), permanent_flags: Some([Asterisk, Flag(Answered), Flag(Flagged), Flag(Deleted), Flag(Draft), Flag(Seen)]), uid_next: Some(1247), uid_validity: Some(1517461405) }
Error:
   0: cannot fetch IMAP messages
   1: cannot resolve IMAP task
   2: unexpected BAD response: Sequence set is inavlid!

Location:
   /Users/edwardzcn-mini/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pimalaya-tui-0.2.1/src/himalaya/backend.rs:513

It does work with --page-size 0 param. Here is the result:

But why I need this param. I find the explanation in the samle toml config that customize the number of envelopes to show by page.

Would it be possible for you to create us a fake account there, so I could debug? You can send me credentials either as a private message on the Matrix chat, or by email at: clement.douin at posteo.net

Sry that I could not provide you a fake account to test. In short, the qq.com mail service asks for phone number registered with ID card :( However, is it possible to hypothesize the path (e.g., whether it lies in the client or the core dependency) based on the trace information in the first paragraph? I will continue conducting some tests in this area.
BTW, I use Gmail  in my daily workflow. However, as I mentioned in the core repository issue, this requires proxy feature support in advance.

But why I need this param. I find the explanation in the sample config that customize the number of envelopes to show by page.

When using --page-size 0 you disable the pagination, therefore the IMAP sequence sent is not the same (1:*). I don't get why the server sends an error on the sequence set received. Unfortunately the sequence is not logged. I will add a log soon, then you can either wait for the next patch release or build from sources (using Cargo directly).

I also have this problem, but I can use imap.qq.com mailbox in aerc.

2024-12-29T00:00:29.554522Z DEBUG list_envelopes{folder="INBOX" opts=ListEnvelopesOptions { page_size: 10, page: 0, query: None }}: email::email::envelope::list::imap: UTF7-encoded mailbox name="INBOX"
2024-12-29T00:00:29.554631Z TRACE list_envelopes{folder="INBOX" opts=ListEnvelopesOptions { page_size: 10, page: 0, query: None }}:select_mailbox{client=1}: imap_client::stream: wrote 27/27 bytes
2024-12-29T00:00:29.625562Z TRACE list_envelopes{folder="INBOX" opts=ListEnvelopesOptions { page_size: 10, page: 0, query: None }}:select_mailbox{client=1}: imap_client::stream: read 298/1024 bytes
2024-12-29T00:00:29.625686Z  WARN list_envelopes{folder="INBOX" opts=ListEnvelopesOptions { page_size: 10, page: 0, query: None }}:select_mailbox{client=1}: imap_client::tasks::tasks::select: missing required UNSEEN OK untagged response
2024-12-29T00:00:29.625719Z DEBUG list_envelopes{folder="INBOX" opts=ListEnvelopesOptions { page_size: 10, page: 0, query: None }}: email::email::envelope::list::imap: mailbox selected name="INBOX" data=SelectDataUnvalidated { flags: Some([Answered, Flagged, Deleted, Draft, Seen]), exists: Some(7), recent: Some(0), unseen: None, permanent_flags: Some([Asterisk, Flag(Answered), Flag(Flagged), Flag(Deleted), Flag(Draft), Flag(Seen)]), uid_next: Some(3693), uid_validity: Some(1415888772) }
2024-12-29T00:00:29.625882Z TRACE list_envelopes{folder="INBOX" opts=ListEnvelopesOptions { page_size: 10, page: 0, query: None }}:fetch_envelopes_by_sequence{client=1}: imap_client::stream: wrote 59/59 bytes
2024-12-29T00:00:29.685929Z TRACE list_envelopes{folder="INBOX" opts=ListEnvelopesOptions { page_size: 10, page: 0, query: None }}:fetch_envelopes_by_sequence{client=1}: imap_client::stream: read 43/1024 bytes
Error:
   0: cannot fetch IMAP messages
   1: cannot resolve IMAP task
   2: unexpected BAD response: Sequence set is inavlid!


[google_maps_flutter] API for setting GMSServices.provideAPIKey

Can we get an API for setting GMSServices.provideAPIKey so that we can avoid baking hard-coded values in AppDelegate (as described here)?
Use case
Avoid hard-coding sensitive API keys in AppDelegate (as described here).
Proposal
If there was an API exposed to Dart, one could get the API key from the database after authentication or Firebase Remote Config, and then pass it to Google Maps before instantiating a widget.
Will this approach work for Android too?  (Obviously, a uniform solution is ideal.)

It is possible to restrict usage of API keys to specific Android app, iOS App, HTTP Referer, or IP addresses.
https://console.cloud.google.com/apis/credentials
I believe authenticating with Firebase Remote Config itself will require API key, because your app will need to initialize Firebase clients with certain key. (usually available in GoogleService-Info.plist)
So I am unsure if putting Google Maps API key (which will likely be same as the Firebase API key if you are using One API key for the iOS app) in firebase will make this safer, unless you restrict app key itself.
By the way, it is recommended not to store any sensitive credential value in Firebase remote config.

By the way, it is recommended not to store any sensitive credential value in Firebase remote config.

It is also not advisable to store API Keys in source code.  So, if you can't store them in source code, and you can't use a service like Firebase Remote Config, what is one supposed to do?

By the way, it is recommended not to store any sensitive credential value in Firebase remote config.

It is also not advisable to store API Keys in source code. So, if you can't store them in source code, and you can't use a service like Firebase Remote Config, what is one supposed to do?

As I have said before,

It is possible to restrict usage of API keys to specific Android app, iOS App, HTTP Referer, or IP addresses.
https://console.cloud.google.com/apis/credentials

So your Google Cloud API key can be put into configuration file in app package (e.g. .plist file in iOS). Even if someone steals it, they won't be able to use it because API key will only work under given app, and Google Cloud services will reject requests not coming from your app.
The link that you are referring to is talking about private key or API key which cannot be restricted by client type, id.
There is no point in persisting sensitive information in RemoteConfig, as anyone can see the full config value.

Thank you @cielo, I am reverting to hard-coding the API Key in AppDelegate.swift, following the instructions.
My reservations were driven by the documentation I cited, as well comments from #51267 that literally said, "API key in your source code is only meant for testing purpose in documentation not for production release."

That should be fine. The same doc that you linked has this information.

Restrict your API keys. You can best protect your API key by restricting it to specific IP addresses, referrer URLs or mobile apps, and specific APIs, as this significantly reduces the impact of a key compromise.
You can specify application and API restrictions for a key from the console by opening the Credentials page and then either creating a new API key with the settings you want, or editing the settings of an API key. See section Restricting API keys for full details.

So if you are hard coding google maps key, make sure it is only useable in your iOS app bundle id. By default, they don't impose limits and anyone who obtains your key can abuse it.

@cielo What about service accounts? I need to integrate Dialogflow with my Flutter app, and would really prefer not to have a streaming backend server just to protect my credentials... especially when the rest of my app is using Firebase.  As it stands, I have to include a JSON file for my service account in my app bundle.  If I could restrict the usage of the service account similar to how you can restrict API keys, it would help alleviate this concern.  Currently, there is no suitable way to securely provide this data in Flutter for a production application.  Many people are asking these types of questions without a suitable answer.

@AlexHartford If you are talking about private credential JSON file that is generated for service account, you should never put that in your app package. Those private keys are meant for secure environments, such as your own server environments, and that is just how those keys work. You shouldn't embed service account key in website or in app.

Currently, there is no suitable way to securely provide this data in Flutter for a production application.

There is no way to securely store credential data in ANY of the Flutter/Android/iOS/Web/Xarmin application. Any savvy individual will be able to extract credential file from the app package if they want to. I am unsure why anyone would think there is such a way. And above is the reason why anyone won't be able to find an answer like you said.

Many people are asking these types of questions without a suitable answer.

Even the Dialogflow asks you to store private key in a safe place.

You can only download this JSON file once, so make sure to save the file and keep it somewhere safe. If you lose this key or it becomes compromised, you can use the same process to create another.

So, you would never put those private key in an app package which will be distributed to tens of thousands of users.
So what would you have to do? You must setup server environment which keeps track of service account keys (if you use GCE, this step may be a lot simpler) and authenticate requests. You cannot just say 'I prefer not to have a streaming backend server just to protect my credentials'., as that is a necessary step to protect your information.

@cielo I appreciate the quick reply.  I do believe there should be a more elegant solution to this problem though.  Why even bother providing https://pub.dev/packages/googleapis (with no mention that including service accounts in-code is not suitable for production)?
Yes, most developers understand this is wrong - but the package linked above, provided by dart.dev, breaks this rule fundamentally.  And I can tell from the usage of this package and its derivatives (e.g. https://pub.dev/packages/flutter_dialogflow) many people are just letting this security gap slide.  There are 2 medium articles (1, 2) that have gained exponentially more traction than the project I linked in my previous comment that are making use of this flutter_dialogflow package.  So clearly, people want this to be easier.
Having to set up a server for no value-added other than hiding my credentials? Trust me, I understand that credentials being private is fundamentally important. Yes, it is a necessary step to protect my information, currently.
Why can't service accounts be restricted in the same way that API keys are?  Can I use an API key instead of a service account for accessing Dialogflow?  I don't have answers to these questions because documentation does not exist on these topics.
TL;DR: Why have https://pub.dev/packages/googleapis at all if you can't utilize it without breaking security constraints?

I will avoid lengthy discussion after this last comment as we are talking about topic that is barely related to what the original requestor of this issue initially asked about.
@AlexHartford
Service account is not the only way to use https://pub.dev/packages/googleapis. It works well with API keys & credentials method for many of services that it supports.
From GitHub repo

In addition, based on the API being used, you need either an API key or a Client ID. And finally, depending on what kind of application is being used, you might need a Service Account.

Do keep in mind that pub.dev is a repo for Dart, not just for Flutter.
So it is not right to say

Why even bother providing https://pub.dev/packages/googleapis

Again, it is incorrect to say

including service accounts in-code is not suitable for production.

because service accounts can be included in-code in a server environment in production.
Also for the examples which need service account private key (e.g. google storage bucket, DialogFlow, etc), the package doesn't mention anything about embedding the key in mobile app.
The example shows you how to use the package in dart lang, which does not necessarily mean it is used in flutter. Dart files can run standalone in server environments, and if you have dart server, it should be fine to use that package for DialogFlow. If you want to use googleapis dart package in your app, you probably only want to use features that require API key credentials which can be access controlled by bundle id, or app id.
Likewise, there is probably an example out there in Java library that uses DialogFlow private key directly, but that does not mean it is expected to have that same setup in Android. (because Java can run as standalone server, and the library/example was probably meant for java server).
Just because there is a package for something does not mean that it is okay to use it. There are probably hundreds of packages listed in other package repo such as Maven(Java) or NPM(JavaScript) that do not follow valid security protocols. That does not mean that users are okay to use them, which is what you are saying here.
Same concerns can be applied to medium articles (1, 2) that you are talking about. They are probably written by someone who do not have deep understanding of what it means to embed private key to your app package, or they wrote with an intention that the app will be used by trusted in-network users, or etc. They both received few comments and some reactions, and that is just it. Not sure how that can be interpreted as 'exponentially more people want this feature'. I do see people interested in DialogFlow, which they can do whenever they want since there is a way to do it with a server.
On contrary, the medium article that you mention, which also happens to be written by Google Engineer, correctly shows how architecture should look like, and it uses NodeJS server to relay and authenticate between web app and Dialog APIs.
It is very misleading to say

Having to set up a server for no value-added other than hiding my credentials?

Because with server, you get security, control and gain more access to wide variety of APIs (including DialogFlow).
None of official DialogFlow setup instruction or GCP instruction ask you to embed private key in your mobile app (other than those 2 misleading blog articles), but you are insisting on it because you don't want to setup a server. That is only issue here and nothing else.
e.g. Firebase Admin API which has more powerful features than Firebase Client SDK requires service account key because Admin API is expected to be run in a server environment. Of course, you CAN embed private key in your app and let your app use Firebase Admin API key directly (similar to what you are trying to do with DialogFlow), but that is just poorly designed architecture that poses security risk.
I used Firebase Admin API as example, but there are tens of thousands of APIs (AWS, GCP, Azure, etc) out there that requires API calls to be made in safe server environments, because they rely on private key.
Lastly, do note that flutter_dialogflow was not developed or released by google, and it is a third party package developed by another developer. It might be fine to use that package, if your intention is distributing app to trusted small set of users, such as your teammates/coworkers (which I still see as security risk), but if you are thinking about releasing it on App Store or play store, you should never use it unless you want to freely distribute your private keys in the wild.
Not to mention, when you have to rotate your private keys because of security compromise or for quarterly/annual security review, all users who have old version of app & old private keys will just simply won't be able to use the service.
I see a lot of misinterpretation from your comments as I have pointed them out above. I understand that not everyone is savvy enough, but if you are a developer whose intention is using DialogFlow, one of the core services provided by GCP, and not simple HTML/JS, then you shouldn't be fixated with one path with dead-end. e.g. You will need to understand basics of how private/public crypto key works because service account key that you are keep mentioning is a private key, and you are trying to distribute that key to untrusted users (in a mobile app). You likely need to learn about server programming with whatever language you are familiar with to make this work.

I apologize for going quite off-topic but this is ultimately the issue that all the related-but-closed issues led, and you seemed like my best shot at getting some answers.  Thank you for being candid with me.
@cielo I appreciate your detailed response.  You have made a few things clear to me that I was admittedly overlooking because I have only used Dart for Flutter development.
I have a good amount of experience working with server programming using various languages but was hoping I would be able to avoid it in this case as none of my other functionality requires a server (and I am in a prototyping stage, but still want to follow best-practice where it is logical).
The main point around the articles I brought up was just that Flutter, being relatively young, has some questionable implementations for various things out there.  As I gain more experience with these tools I hope to make positive contributions to the community.
Thanks for addressing me in a straightforward manner.  Keep up the good work.

So your Google Cloud API key can be put into configuration file in app package (e.g. .plist file in iOS).

Not so for the GoogleMap widget -- the values have to be stored in AppManifest.xml on Android, and AppDelegate.swift on iOS. Storing an API key in a properties file only works for other Maps APIs, such as Places / Timezone.
There are some fundamental problems with the current approach:

Currently there is no way for Flutter code to get access to the Google Maps API key, if you want to reuse that key for calling other Maps APIs. That means you need to define your API key in at least three places, to use both GoogleMap and other APIs: AppManifest, AppDelegate, and your Dart code.
The GoogleMap widget cannot be configured programmatically from Dart, sourcing the API key from Dart code, the way other Maps APIs can be. The GoogleMap widget can only be configured in the respective native environments.

We need either the ability to read the Maps API key from the AppManifest/AppDelegate, or to configure the GoogleMap widget from an API key provided by the Dart API.
I personally prefer the latter (which would require the key to be configured in only one place, in Dart code), but the former would be an improvement (it would require the key to be configured in two places, for an Android+iOS Flutter app). (Yes, even with the pure Dart solution, there should probably be separate keys for Android and iOS, but they can be switched using if (Platform.isAndroid) etc.)


Trying to remove sidebar gives an error in 1.8

Debug:
http://one.denizenscript.com/paste/36577
Reproduce:
/ex sidebar remove

Potential fix pushed to inbound dev build

It works as it should now! :)


keyconf: Document expected endianness of keys

We should document the expected endianness of raw key bytes.

keyconf was removed with the move to x509 based CPPKI


Chore: Updated the usage pulse format

Description
The usage pulse format is updated
Fixes https://github.com/appsmithorg/cloud-services/issues/148
Type of change

Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Manual
JUnit

Checklist:
Dev activity

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

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=85c248100d45dbb1f1ba8219cc6a920b0739e1b7


Broken Link

Learn More link for "Build Azure Functions" is resulting in a 404

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

ID: d5900fe4-4399-9b09-3e42-4ff71f3a8fb9
Version Independent ID: 16e8e4eb-6e63-620e-3811-cd6265aca1fa
Content: PowerApps for enterprise developers, partners, and ISVs - PowerApps
Content Source: powerapps-docs/maker/canvas-apps/dev-enterprise-intro.md
Service: powerapps
GitHub Login: @ImadYanni
Microsoft Alias: iyanni

@roshangautam Thanks for reporting this. The link is fixed now, and will be updated in our next daily live update. Please check back in a day. Closing this issue.


fix: access to download binary from mirror sites

Installation will fail when network is not access to https://yt-dl.org/downloads/latest/youtube-dl

Thanks for that, additionally can you add it as part of the README?
Similar to https://github.com/puppeteer/puppeteer/blob/eddb23b52175a3dad8cec4a5e9b3c13e58f6f144/docs/api.md

Thanks for that, additionally can you add it as part of the README?
Similar to https://github.com/puppeteer/puppeteer/blob/eddb23b52175a3dad8cec4a5e9b3c13e58f6f144/docs/api.md

yeah，it looks like a role model.

Released a 2.2.0 🎉


No suitable kits found (QtCreator)

I cannot figure this out right now. Very frustrated.
I installed qt 4..8.7
I installed qt creator
Do I need to install vs 2010??
Is vs 2022 not compatible and I need vs 2019??
Compiler for 2010??
https://i.imgur.com/MCkUu09.png
https://i.imgur.com/jKJaXxg.png
I don't under stand bro I am very frustrated.
mb if I use this?
https://i.imgur.com/4UTtlPa.png
mb this?
https://i.imgur.com/5rw1M71.png
nope that's not the compiler..
trying to use
https://stackoverflow.com/questions/68668084/installing-a-compiler-for-qt4-8-7-on-windows10
bro wtf you did not go through all of this i don't under stand what i need to do please assist
is this needed?
https://i.imgur.com/AX9x3VF.png
found
https://doc.qt.io/qt-6/windows-deployment.html
it's working now.
thanks any ways. delete if you'd like mb some one else can use this as a somewhat tarnished guide.
i installed qt5 in stead and can at least build and see the project in qt creator
but now when build and run exe it says stuff like qt5 dll missing not found ugh
ok i see the release is bundled with these files i will see how to have build place them in the build

what a huge speedbump (forgot to close earlier)
it's handled
thanks for this project

Qt 4 is very old, to use it with modern compilers you'll have to build it yourself.
The easiest is to use Qt 5 that has prebuilt binaries for msvc2019.
The project doesn't support Qt 6 yet.

Thanks for response. I have a small pull request coming your way in about 10 minutes.
I eventually used precompiled qt5 and just now build qt5 from source be cause VS2022 didn't like my mingw qt5.
Very cool that you responded, respect.

cause VS2022 didn't like my mingw qt5

well, of course it didn't, because these are different compilers :) For mingw you can use Qt Creator.

note that you can install msvc2019 toolchain (compiler) and use it inside VS 2022

My main issue is seeing so many red underlines. I am trying to diagnose this. I am able to build in qt creator, though not yet in vs. I may be able to under stand more precisely if you could list which distribution set you would have gone with?
Would you have used this or this?
Do you use legacy qt vs tools or do you upgrade the project for use with current qt vs tools?
I ended up going with this, though with legacy or current qt vs tools, there are red underlines and no build is possible in vs. I would be happy building in qt creator if the red underlines were gone to edit in vs.

I used online installer to download 5.15.2 binaries for msvc2019, but you can build any 5.15.x from source (better take the latest - 5.15.13).
iirc the project is configured to use the legacy Qt VS tools. I rarely use VS for this project nowadays, mostly just to build it from command line.

Oh to be so skillful.
Any idea about this?
Using legacy tools and compiled source qt.

right click solution properties - set Qt version. I think you should read the Qt VS tools manual :)

:o surprise pikachu
Qt version is set already ;)


netdata: bump to 1.38.0

updated version and hash
changed the patches so they apply

Commit message should look like this: attribute: old version -> new version, see more here: CONTRIBUTING.md


how to set up a local instance and debug this application.

Hello @asingh263,
To debug locally you will need all resources required for Company communicator should be deployed on your Azure subscription. You need to download the code and start it in Visual studio using its .sln file or you can fork and clone the git repo in VS.
You need to follow Deployment Guide Step 1, 3 and 5.
There are two way you can proceed from this point. You need following resources as mentioned in appsettings.json.
First is, You can do the deployment using ARM Template option (Deployment Guide) and from the configuration of App service, you will get the required information.
Or you need to create all resources manually.
Once you have all the required information you need to fill the appsettings.json.
For AppDomain you will ngrok  or equivalent tunneling solution. You need to run it for the local host app is running on.
Follow Step 5 of Deployment Guide just replace app domain with ngrok url.
Once done run the code using VS.
I hope this will help you in debugging.
Thanks

I tried this..but when opening the tab in Teams im getting the following error:
The reply URL specified in the request does not match the reply URLs configured for the application


Translation into Chinese

Hi, shekhargulati!
I am really like your posts in java8-the-missing-tutorial. I want to translate them into Chinese so that more people can learn about them. I will add your name and links to this repository. Can you give me a chance?

Hello @gavinfish yes please go ahead. Let me know when you are done I will add link to Chinese translation to the repo as well.

any update on the translation progress? @gavinfish

Here are some chapters java8-the-missing-tutorial-zh  @yjqg6666

I suggest that this issue could be closed.