Guess Packages for Config Options

For certain config options where we are trying to load a class.
Say choosing the term story for inference.
Or perhaps the CLI choosing what inference or weight learning to use (even though this is not a config issue).
It would be great if someone could specify just the class name instead.
So LazyMPEInference instead of org.linqs.psl.application.inference.LazyMPEInference.
The classloader may not have loaded all the classes yet, so we probably can't rely on that.
Maybe we can have maven put all the classnames in a properties file.
Or have some expected prefixes that we assume if we cannot find the specified class name.

Of the proposed options:

The first one will require a new maven plugin (I found none that had this functionality by default).
The second one would require all relevant config calls to declare an expected package.

Of these, 1 is more maintainable.
We will go with that.

Plugin implemented and in Maven Central:
https://search.maven.org/search?q=a:list-classes-maven-plugin

Complete in 00b603211d070729bc486c558846c3cfebcc4bb7.


Deployment not respecting tolerations to taint

Environmental Info:
Two different environments facing the same issue:
K3s Version:
k3s version v1.24.6+k3s1 (a8e0c66d)
go version go1.18.6
k3s version v1.24.2+k3s1 (b0ed1348)
go version go1.18.1
Node(s) CPU architecture, OS, and Version:
Linux  5.4.0-126-generic #142-Ubuntu SMP Fri Aug 26 12:12:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Linux 5.4.0-121-generic #137-Ubuntu SMP Wed Jun 15 13:33:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:

3 Control Nodes

2 Worker Nodes

Control nodes run control-plane, etcd and are master

Utilizing kube-vip (v0.4.4) as a control plane HA VIP instead of dedicated HA proxy.

Utilizing antrea (v1.8.0) for CNI

Describe the bug:
I have tainted the control nodes for NoExecute so that I can add tolerations to coredns and antrea-controller, however it appears the deployments are not respecting the tolerations and scheduling coredns + antrea-controller on worker nodes.
Steps To Reproduce:
Add the following taints to the control nodes.  Keep in mind I never needed the NoSchedule taint before, as I have only used NoExecute but I added it to be on the safe side (It did not make a difference).  No matter how many times I restart the coredns and antrea-controller deployment they keep getting scheduled on worker nodes.  However, I can manually cordon + drain both worker nodes and the pods will get scheduled on the control-plane nodes.
  taints:
    - key: k3s-controlplane
      value: 'true'
      effect: NoExecute
    - key: node-role.kubernetes.io/control-plane
      value: 'true'
      effect: NoSchedule

Add tolerations to deployment coredns and antrea-controller:
      tolerations:
        - key: CriticalAddonsOnly
          operator: Exists
        - operator: Exists
          effect: NoExecute
        - key: node-role.kubernetes.io/control-plane
          operator: Exists
          effect: NoSchedule
        - key: node-role.kubernetes.io/master
          operator: Exists
          effect: NoSchedule

Expected behavior:
I expected the referenced coredns and antrea-controller deployments to be only scheduled on control-plane nodes since I have added the appropriate taints + tolerations.
Actual behavior:
coredns and antrea-controller deployments are getting scheduled on worker nodes instead
Additional context / logs:
No logs are visible that I can see are an issue.

I expected the referenced coredns and antrea-controller deployments to be only scheduled on control-plane nodes since I have added the appropriate taints + tolerations.

That is not how that works. Taints prevent things from running on that node, tolerations allow them to run there despite the taint. You have tainted your control-plane nodes, then added tolerations to those taints, for a net zero result as far as your workload is concerned.
If you want to require your workload to run on nodes with a particular set of attributes, you should be looking at nodeSelectors or affinity: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity


Translate "Create Job" button name

Fixes #225

This change, which fixes #225 (not 27) is redundant with #227.

Already fixed in WIP PR #225


Date handling from BQ

There seems to be an issue with handling dates returned from BQ.
Problem query
SELECT EXTRACT(DATE FROM <timestampe> ) as Date, <some_metric> FROM <some_table>
returns a nested json object like

and can't be rendered in a chart since I have to reference values as

working query
When I extract only month as:
SELECT EXTRACT(MONTH FROM <timestampe> ) as Date, <some_metric> FROM <some_table>
The json object is not nested and the chart renders fine

@mikeyoungyoung -- can you share the contents of the package.json file at the root of your project?

{   "name": "~TODO~",   "version": "0.0.1",   "scripts": {     "dev": "svelte-kit dev",     "build": "svelte-kit build",     "preview": "svelte-kit preview"   },   "devDependencies": {     "@sveltejs/adapter-static": "^1.0.0-next.11",     "@sveltejs/kit": "next",     "vite-plugin-full-reload": "^0.2.2"   },   "type": "module",   "dependencies": {     "@evidence-dev/components": "^0.0.10",     "@evidence-dev/db-connectors": "^0.0.6",     "@evidence-dev/preprocess": "^0.0.3",     "@google-cloud/bigquery": "^5.6.0",     "blueimp-md5": "^2.18.0",     "d3": "^6.7.0",     "d3-scale": "~3.3.0",     "fs-extra": "^9.1.0",     "layercake": "^4.1.0",     "svelte": "^3.34.0",     "vite-plugin-live-reload": "^2.1.0"   } }

Hey @mikeyoungyoung, looks like you're on an old version. The date issue is fixed in our most recent release. You can initialize a new project to get the up to date release. Let us know if you run into any issues with it.

@hughess so, likely a n00b question.... but... I did npm init @evidence-dev/new in a new folder and got the same package file and dependency versions. Probably user error, but that shouldn't be the case right? Also, has does one just update a current project?

@mikeyoungyoung not a noob question at all -- I was able to reproduce your issue, and we'll be adding this to the docs. Thank you.
I believe your local NPM registry is falling back to an earlier, cached, version of the installer. You can force it to use the latest version of the installer (0.1.4) by running the following command:
 npm init @evidence-dev/new@latest my-project
re: updates to existing projects
This is coming soon. In a release or two, the whole dependency tree (as well as a bunch of the default scaffolding files) will be behind a single "evidence" dependency. At that point, you'll be able to install updates using npm update. See issue #45
I am going to close the issue for now, but feel free to re-open if @latest doesn't solve it for you.


Add an option to choose which timeframe should be displayed by default

Add an option, either in the web interface (it could be an option different for each user or the admin choose it) or in the environment variable. And allow to  choose which timeframe should be displayed by default.
For exemple always display this week instead of the current day.

Hi @HellsCrimson, thanks for your feedback. I'll add this as a low-prio feature request. A temporary solution would be to bookmark the respective URL.

I was super confused for a few minutes when I first imported my wakatime data because of this. Made me think it only imported one day's worth of stats since it showed a much lower hour count, right after clicking on dashboard, compared to the 7 days wakatime shows by default.
At the very least, I think if you change it, it should stay on that value for the session. Right now if you change it, then click on one of the projects, it stays the same timeframe which is great, but if you click Dashboard to go back rather than using the browser's back button, it reverts back to 1 day.

Thanks for your feedback.
I think I'd rather opt out from the proposed solution of being able to explicitly configure the default time frame. But will implement the time frame in a way that it is remembered across page changes.

I can work on this. I think that we can hold the last used interval in the browser's local storage as something like wakapi_summary_interval. Whether to always store the interval selected by the interval query param, or only do that when clicked manually (through the interval picker) is your decision though. I think that always overwriting the last used time interval is a more natural approach, as the user which clicks a link (even from an external source or a bookmark) will see the same summary when they come back again.
I'll need some help here, because I don't know how to easily change the selected time interval for data fetching without updating the window.location. From what I can tell, it's the only option now, because changing only the return value of the currentInterval getter in components/summary.js doesn't influence the actual time range displayed on the summary page, when query params are empty.
I made a quick prototype. When there is wakapi_summary_data in the browser's local storage, it adds the interval query param to window.location. This works, but causes an additional page reload. I also dislike the mutation being in a getter function, but can't quite figure out where to put it.
Modified code in static/assets/js/components/summary.js:
PetiteVue.createApp({
    $delimiters: ['${', '}'],
    get currentInterval() {
        const urlParams = new URLSearchParams(window.location.search)
        if (urlParams.has('interval')) {
            window.localStorage.setItem('wakapi_summary_interval', urlParams.get('interval'))
            return urlParams.get('interval')
        }

        const localStorageInterval = window.localStorage.getItem("wakapi_summary_interval")
        if (localStorageInterval) {
            window.location += `?interval=${localStorageInterval}`
            return localStorageInterval
        }

        if (!urlParams.has('from') && !urlParams.has('to')) return 'today'
        return null
    }
}).mount('#summary-page')

I can open a pull request with these changes, but I'm posting them here first to avoid any confusion and get feedback where to place this new logic.

Here's a quick demo:

Hi @Daste745, thanks for looking into this!

[...] always overwriting the last used time interval is a more natural approach [...]

I agree!

[...] From what I can tell, it's the only option now [...]

You're right. Since (almost) everything in Wakapi is server-rendered, the only way to fetch data for a certain interval is to actually update the page.
One option could be: the user logs in, sees the default summary page, then JavaScript kicks in, checks localStorage for the last viewed interval and updates the URL, resulting in a page reload. This wouldn't be a nice solution, though, because of the additional redirect. The user would see the default (i.e. today) summary for a short second before actually being redirected to the correct time frame. So you can't wait for JavaScript to handle this, because of that aforementioned, ugly "content flash".
Would you would need is a mechanism that allows the server to decide which interval to present to the user, even before the page is first rendered.
One option here could be to actually always persist the last visited interval in the database. However, I don't like that either, because (a) I think it's overkill and (b) because the database shouldn't have to mess with UI-specific data / properties.
Long story short: I propose to use a cookie for this and get the best of both of the above worlds. Cookies are only stored client-side, can nevertheless be read by the server (because automatically included with every request) and don't require any JavaScript to read them. There would be a cookie, that is set from JavaScript, essentially the exact same way how you're currently setting the localStorage attribute. But then, upon requesting the /summary route, the backend would (1.) check if a query param is explicitly set (what we already had so far) and (2.) if not, check if the summary_interval cookie is present.

Check this method, that'll be your starting point on the backend side. Thanks again for looking into this!


Vanish funky groups from govuk

We want to vanish two broken placeholder_working_group editions from pub-api and from relevant services downstream. This is due to data being inconsistent or missing for these groups causing them to be flagged as live in pub-api and content-store but missing routes and not present in the original publishing application (whitehall).
Trello:
https://trello.com/c/ygOqmhWw/1921-remove-legacy-placeholderworkinggroup-code-data-from-govuks-codebase

PR #5555, time to listen to the whole of Interstellar #5555

🕺 🕺 🕺


fix toggle button can't click

Summary
https://github.com/harvester/dashboard/assets/24985926/7faa6d20-99be-43f8-8a7d-450b9ac6dd82
setting page hide and show buttons are not clickable。
reproduce step:

Configure backup-target, click Save
Click on any show or hide button on the setting page.

PR Checklist
~- Is this a multi-tenancy feature/bug?
- [ ] Yes, the relevant RBAC changes are at:~
~- Do we need to backport changes to the old Rancher UI, such as RKE1?
- [ ] Yes, the relevant PR is at:~
~- Are backend engineers aware of UI changes?
- [ ] Yes, the backend owner is:~
Fixes #

Occurred changes and/or fixed issues

Technical notes summary

When the websocket is updated, the settings object and the categorySettings object are completely unrelated, so changing the value of this.settings will not affect the value of categorySettings.
Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

@mergify backport release-harvester-v1.2


struct RefMvsFrame::{rp,rp_ref}: Remove raw ptr fields and pass through the callstack

Looks like this needs a rebase, but I reviewed the last commit which seems to be the only one for this PR. Let me know if I missed any commits that need review though.

Looks like this needs a rebase, but I reviewed the last commit which seems to be the only one for this PR. Let me know if I missed any commits that need review though.

Oops.  It's the last two actually.


in place update with data validation

Checks
I haven't see a builtin way to update a model in place, with data validation. Am I missing something ?
The only thing I could come with is this ugly stuff :
class MyModel(BaseModel):
    x: float = 0.0
    y: float = 0.0

>>> m = MyModel()
>>> for k,v in m.parse_obj( m.copy(update={'x':4.5}) ).dict().items(): setattr(m, k, v)
>>> m.x
4.5
...

a m.update( x=4.5 ) would be nice.

Use validate_assignment on the config, then just set the property.
Example in the docs.

Thanks, but if I used validate_assignment  the data will be validated all time and not in demand, which is not suitable when they are updated at high frequency from trusted source (a server in my case).

This seems to be closed. However the proposed solution does not fill the requirement.
I guess so that the feature is not wanted.

Hi @SylvainGuieu
I would go with something like this
class MyModel(BaseModel):
    x: float = 0.0
    y: float = 0.0

    class Config:
        validate_assignment = True

    def update(self, **kwargs: Any) -> None:
        set_validate_assignment = self.__config__.validate_assignment
        try:
            self.__config__.validate_assignment = False
            for k, v in kwargs.items():
                setattr(self, k, v)
        finally:
            self.__config__.validate_assignment = set_validate_assignment

But it means you can indeed do m.update(x=[0], y=123)
Hope it helps


"Not you?" button closes paypal popup.

Description
I am developing a cordova application (both on android & ios). I'm rendering paypal button in popup. when i'm clicking "not you?" link, paypal popup closes and user doesn't logout.
Issue is reproducing on android & ios with sandbox env & production env.
Connect checkout in app.html in head section:
<script src="https://www.paypalobjects.com/api/checkout.js" data-version-4 data-log-level="info"></script>
Render checkout button:
paypal.Button.render({
	env   : 'sandbox',
	client: {
		sandbox:    paypalConfig.sandbox,
		production: paypalConfig.production
	},
	commit: true,
	payment: function(data, actions) {
		return paypal.request({
			method: 'post',
			url   : CREATE_PAYMENT_URL
		}).then(function(data) {
			return data.id;
		});
	},
	onAuthorize: function(paymentData, actions) {
		var data = {}
		data.paymentID = paymentData.paymentID;
		data.payerID   = paymentData.payerID;
		return paypal.request.post(EXECUTE_PAYMENT_URL, data).then(function(res) {
			alert('PAYPAL_SUCCESS');
		}).catch(function(e) {
			alert('PAYPAL_REJECT');
		});
	}
}, '#buyPaypal');
Console errors:
types.js:19 Uncaught Error: No handler found for post message ack for message: xcomponent_delegate_ppcheckout from file:// in https://www.sandbox.paypal.com/checkoutnow
types.js:101 Uncaught Error: No handler found for post message response for message: xcomponent_delegate_ppcheckout from file:// in https://www.sandbox.paypal.com/checkoutnow
exceptions.js:14 Uncaught TypeError: Cannot read property 'auth' of undefined
paypal.version from console: 4.0.131
When i'm starting my project in browser, logout button works fine. All payments with any env or browser work fine
Full console Log from the moment of paypal button rendering until user clicks "not you?" is available here: log.txt
Issue occures consistently.
Steps to reproduce

Click Paypal Button
Log in
Close paypal popup
Open it again
Click "Not you?" link

Affected browsers

[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge
[ ] IE
[ ] Chrome Mobile/Tablet
[ ] Safari Mobile/Tablet
[X] Web View / Safari ViewController
[ ] Other

Screenshot of my console:

Thanks for the report! I'll take a look

This is fixed and ready to go out in the next release.

Pushed. Please let me know if you still see this issue.


Tab no longer works with Emmet

VSCode Version: Code 1.15.0 (8b95971d8cccd3afd86b35d4a0e098c189294ff2, 2017-08-09T20:06:21.685Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

jsx
Twe
0.0.1

Not sure why, but suddenly tab no longer triggers expansion. I see there's a menu, but no way to assign a key command to that. Not having a keyboard shortcut makes using Emmet annoying. The whole thing about Emmet is that it's suppose to be the quick way to create markup. You just made it not quick. As someone who uses Emmet every day, this is beyond annoying.

Steps to Reproduce:

Reproduces without extensions: Yes/No

Tab is no longer associated with Emmet
Please read the Release Notes or the blog on Emmet 2.0

@ramya-rao-a Please at least give us the option to bind "Tab" to Emmet. "Tab" is a shortcut we've relied on across many editors for years.

@johnlindquist tab was the logical choice for all editors because it's synonymous with auto-completion/content-assist.
Now that emmet shows up in the auto-completion/content-assist, pressing tab selects emmet from the list and you get your abbreviation expansion.
Of course, if you have editor.quickSuggestions turned off, you are now forced to either press Ctrl+Space to get the suggestions or use a new key binding for the emmet command.
Is that your scenario?
Also,I am assuming you read the blog which states the issues that came out of tab being bound to emmet

Re-opening issue to continue the discussion post the 1.15 release

The tab binding has been a staple of Emmit from day one and I would push for not changing that. Technical issues aside, the editor now fundamentally no longer works like I would expect.

I do disable quickSuggestions. I personally find boxes popping up all over the place unprompted annoying, so I turn off as much as I can. I invoke autocomplete often, but on my terms.

If one was to say that they don't use the suggestion widget/ content-assist, I can understand how this fundamentally changes things.
If one was using the suggestion widget/content-assist, then pressing tab still completes the abbreviation. In css, the emmet abbreviation is sorted appropriately among the css suggestions (all of which are fuzzy matched themselves). In html, the emmet abbreviation is the first one (pre-selected) that shows up in the suggestion list and so pressing tab selects the abbreviation which results in the expansion. The end result being no different than before.
Thanks for sharing that you fall under the first camp above @johnlindquist
I am interested in hearing feedback from more people.

Maybe a setting in quickSuggestions like displayOnlyTopResult or displayOnlyEmmet would be a happy middle-ground...

@johnlindquist
displayOnlyEmmet is not possible. Emmet now is an extension. And like any other extension can only say that it has suggestions to provide and no control over if there are suggestions from other extension. And VS Code cannot play favorites with extension, giving an option to show only that.
But your other suggestion of displaying only a single result is interesting, I'll look into it

If you have a custom component, Foo, you have to manually invoke Emmet to expand to <Foo></Foo> now.

True, otherwise the suggestion list would keep appearing for every word that was being typed. Because technically every word is a valid abbreviation that can be expanded to <word></word>

and fwiw, it misses common tags like header/footer as well.

Update https://github.com/Microsoft/vscode-emmet-helper/issues/5 for requests for more common tags

Tabbing through an expansion like nuxt-link[to]*5 with quickSuggestions enabled is immensely frustrating. You have to escape at every single stop.

Sorry, what stops are you referring to that you need to escape?  In the below gif, I keep typing (no esc) and when ready, hit the tab.

Btw, am not trying to negate your experience, just trying to understand the user experience better. I appreciate all the feedback.

It's a matter of filling out the stops and dismissing all the completion popups. Also, if you accidentally hit escape when completion doesn't popup, you have to start over.
I'm accustomed to tabbing and shift-tabbing through all the stops without even thinking about it.

@burkeholland It did work before.. Read https://github.com/Microsoft/vscode/issues/32243#issuecomment-321705997 for why simple text words do not trigger emmet suggestions

So, I looked at the documentation. Seriously??? You expect people to have to navigate through the command palette for what was a simple tab before? Do you want us to go back to Atom and Sublime? The documentation also mentions editor.action.emmet.expandAbbreviation. However, when I try to add this configuration to my settings, it gets squiggles underneath and hovering I get "Unknown configuration setting". Did anyone even try that before pushing this?

@rbiggs expandAbbreviation is a keyboard shortcut:

Thanks John, that helps. But I really don't want to be doing a three finger salute when tab was so simple. I'd like to have the option to restore Emmet abbreviation with tab.  Tab saves me tons of time. I've never had a problem with it. Don't just take something away. Give us an option for those who prefer tab use for Emmet expansion.

Sorry about the mistake in the documentation, that has been corrected.
I can see how heavy users of emmet never seem to have had a problem with using tab. Maybe they were real careful (or got used to) not hitting tab right after a word for indentation purpose or never had css suggestions show up and get chosen when intending to expand css emmet abbreviation (this might be because people turned off quick suggestions for css as a work around).
Or compared to the amount of emmet usage, the above 2 occurrences were too small to matter for such users
But we have seen precisely these problems from a number of users.
These new features (no tab, emmet in suggestions) have been in preview (opt-in) for over 2 months now in stable builds. And the Insiders had the new features enabled by default in these 2 months. I got to work with quite a few Emmet users and act on their feedback. Its unfortunate that no-one felt so strongly about tab being removed as the shortcut for emmet.
Is it possible to bring back tab as the keyboard shortcut for emmet and have it fall back to normal tab i.e indent when there is nothing to expand in the current released version?
You can bind tab key to editor.emmet.action.expandAbbreviation command explicitly and it will definitely work.
But if you hit tab expecting indentation in any file, you will be see with the message "Running the contributed command:'emmet.expandAbbreviation' failed.". This is because there is no fallback to provide indentation.
You can add the resourceLangId == html to the when clause in your keybinding and restrict this behavior to specific file types i.e the ones where you are using emmet.
So what's the real solution?
I can add the fallback to indenting based on the value of the setting  emmet.triggerExpansionOnTab (which was deprecated in 1.15, but can be brought back). It will be false by default as opposed to true before. This is so that the issue of emmet abbreviation expanding on tab when non-emmet users are pressing tab doesnt occur. You can enable the setting and get tab -> emmet
When can we expect this solution?
We currently don't have a recovery build planned for 1.15 i.e there is no 1.15.1 planned. If we do plan such a build, then I can include this fix there. Else, this will be available in the Insiders build for the next version i.e 1.16 which should be out sometime next week.

As a fairly new user of vs code I really don't understand the change of this behavior. Like others have pointed out we have been relying on the tab for emmet in other editors for quite some time now.
As emmet is a way to make typing of tags and other default language stuff, it feels to me that that speed is now mostly lost. As @burkeholland mentioned, it is now working in a way we don't really expect it and is causing us to be less fast in development. And quite frankly annoying me 😞

@rbiggs another workaround is to do the following which makes it expendable by emmet (still annoying 😆 )

Thanks nealoke, that helps. But I'd rather have the option to keep using tab. Otherwise, I'm going to have a terrible experience context switch from VSCode to every other editor (Atom, Sublime) that use tab for Emmet :-(.
I've been using Emmet Since it was called Zen Coding back in 2010. That's seven years of using tab to expand. I'll repeat, text editors have been supporting Emmet expansion with tab for seven years.  Somehow the VSCode team decided seven years of use didn't matter. They didn't bother checking out what the use history was, what other editors were doing, or what the Emmet users expect. Bad decision.

I would also argue that Emmet being included in a list of "suggestions" is misunderstanding how Emmet is used.
Emmet is a precision tool. When I type .foo, I expect

. There is no other expectation or suggestion, it's simply an exact expansion of what I typed.
"Suggesting" an Emmet expansion is like asking, "Did you mean

?" And the answer will always be, "Yes, of course, I typed .foo!" I would never pick another option from a list of suggestions when using Emmet, it simply makes no sense.

We are working on the option to use tab for emmet.
Should be out in our next Insiders build in a few hours.

All,
If you have VS Code Insiders, update it.
If not, then please download the latest Insiders from https://code.visualstudio.com/insiders
Add setting emmet.triggerExpansionOnTab to true and you should be able to get emmet expansions on tab
Take it for a spin and let me know if it works as expected.

Looks like this is already basically resolved, but I wanted to point out that there is a setting, "editor.wordBasedSuggestions": false, which will disable suggestions that are only based on text in the document (the ones with the abc icon).
I disable it because this is responsible for a lot of the noise that shows up in the suggestions box, and that shows up in some of the gifs above. With this, I never see the suggestion box pop up in an html file, except for emmet completions, so I think the experience is as close to the proposed displayOnlyEmmet option as you can get.
Looks like emmet.triggerExpansionOnTab is closer to what people expect, but disabling wordBasedSuggestions is another option, if you find the suggestions box useful!

For those having trouble with autocompleting JSX in React, a quick fix is to add "emmet.includeLanguages": {"javascript": "javascriptreact"}

Setting the editor.action.emmet.expandAbbreviation  to Tab also breaks the "highlight->Tab" indent process.

@alchermd Which is why we don't recommend that. Try out the latest Insiders and set emmet.triggerExpansionOnTab to true there and tab should work with appropriate fallback

Just installed the insider's edition. And yes, now I have Emmet working the way I would expect. 🎉 👏🏋 I suggest you put something prominent in the documentation for Emmet about how users can get the expected tab expansion back. And maybe point our any side effects this may cause for other functionality. I noticed that the only thing about Emmet in the current docs is under Languages/HTML. That makes its discoverability hard. I just spent quite a bit of time digging around to find it. And then the Emmet info is just a a short piece about snippets. Thanks for your patience and perseverance. 👍🏻

@rbiggs When the recovery build (1.15.1) is ready for release, I plan to update the current Emmet blog with notes on how to get tab->Emmet working (by setting emmet.triggerExpansionOnTab to true) and its side effects.
Was finding the blog difficult too?
I was hoping for the blog to the source of truth for all things Emmet in the future.

As a developer, you expect the docs to be the one source of truth for a product. It will be up-to-date. Blogs can go stale and buried under new posts, so I don't expect blogs to have relevant information. I only ready a product blog when it comes up as a search result. Otherwise I always dig through the docs. Usually product blogs are mere announcements. Case in point, I didn't even know that blog post about Emmet existed. Developers go to the documentation. When the documentation isn't good, then they consider it a questionable product. I'm pretty sure every Emmet user is going to be digging around in your docs trying to figure out why they can't get Emmet to work. And then wind up going to stackoverflow, not to your blog post.
I notice that for Atom they have all the docs for Emmet in their section on packages, which are the same as VSCode extensions. In your case, basic Emmet support is provided out of the box, so I would expect it to be in the docs somewhere. Looking at your docs right now, I'd expect it somewhere in the User Guide section. Emmet is not a language, and it does fit in Extension Authoring or Extension Reference. My two cents.

Good points.
@gregvanl had the same thoughts about having emmet in the docs section and the blog being info for a snapshot in time.
I'll work on the docs right away.

Closing the issue as the required changes have been merged to the release branch.
Will update this issue once 1.15.1 version is released

you're joking right, tab so awesome,you deprecated,it's a big mistake!

Ramya, I think keeping it in a blog post is a big mistake. I've been using VScode since it first launched and I never, ever look in the blog. Blogs are for announcements, not documentation. Since you include Emmet by default, it needs to be in the documentation. In contrast Atom and Sublime to not include Emmet out of the box. You have to install the extension. And the extension authors provide the documentation. Blog posts are dated, and they get buried by newer posts. Documentation is the current state of support.

what a pity……

emmet.triggerExpansionOnTab is not working,because there is no emmet.triggerExpansionOnTab in vscode
emmet 2.0 config,so you can't add it in user config,it will be give you a error:unknow emmet attribute!

@sjy219 As mentioned in https://github.com/Microsoft/vscode/issues/32243#issuecomment-321961991 before, the emmet.triggerExpansionOnTab setting is available in the VS Code Insiders. You can get it from https://code.visualstudio.com/insiders
We will be releasing VS Code 1.15.1 in 2 days or so, the setting will be available there as well

For anyone still struggling with this, in my VsCode I simply bound the TAB key in the Keyboard Shortcuts file to Emmet: Expand Abbreviation.
None of the 'suggested' solutions worked for me anyway, but this seems to solve it.
I'm unsure why VsCode suddenly disabled this pretty standard functionality, it would be nice if there was a warning for breaking changes like these when VsCode updates.

@TheDutchCoder Did you try any shortcut other than tab in VS Code 1.15? If you did and it didnt work, please let us know.
Else, please see https://github.com/Microsoft/vscode/issues/32243#issuecomment-322373908

Other keys work fine, though a ton of them give conflicts of course.
I have (for now) bound it to command + e, but waiting for tab to return ;)

@ramya-rao-a I code in VS Code 1.14,I will be waiting for 1.15.1.Yes ,I renew to bind tab key to emmet 2.0, and it worked,but there was a problem, there was a conflict with editor's tab,it means the editor's tab key was not working, so I don't know how to fix it, how to config "when" attribute ,may be that's the main problem!

@sjy219 Don't try to bind tab to emmet in 1.15.0. There is no fallback to editor's tab for indenting.
Either use a different key for emmet in 1.15.0 or in the latest Insiders (and the upcoming 1.15.1), set emmet.triggerExpansionOnTab to true

@ramya-rao-a I got it,waiting for the upcoming 1.15.1(1 2 3....)

@ramya-rao-a  thank you very much!

@ramya-rao-a you are doing great 👍 🔥

Waiting for next version. Remove tab from Emmet kills me.

Is it that much harder to press Enter, to confirm your emmet selection? I guess I'm just used to it, cause I didn't start using emmet until they added the improved version.

Alright people, VS Code 1.15.1 is out. Restart your VS Code windows to update.
Set emmet.triggerExpansionOnTab to true to expand Emmet abbreviations and snippets on pressing tab
The Emmet 2.0 blog has been updated to reflect the changes.
And https://code.visualstudio.com/docs/editor/emmet is the new page under docs for all things Emmet in VS Code
Thanks for your patience and Happy Coding!

No dice for me, still doesn't work (1.15.1)

@TheDutchCoder when your .foo became .footer was there a suggestion list open with .footer being suggested with the icon "abc" like below? If yes, that would be word based suggestions which you can control with editor.wordBasedSuggestions.

When the suggestion list is open tab never triggered emmet before, nor will it trigger emmet now. When suggestion list is open, tab selects the first value from the suggestion list.

@ramya-rao-a I believe it did yeah. I normally ESC out of the suggestions anyway because of it.
Now emmet shows up in the suggestions, so that negates the issue (after I changed all my settings), but I might disable the word suggestions anyway, I don't really seem t use it.
Thanks!

The tab key is come back,I just want to say perfect! Thanks guys！

after updating, tab is still invalid in the Vue project

after updating. In the Vue project, CSS can be used with tab, but creating documentelement is still invalid

@ramya-rao-a I just found a small bug (in 1.15.1):
When setting emmet.triggerExpansionOnTab to true, any keyboard shortcut that is bound to emmet.expandAbbreviation (not just Tab) will insert a tab/indent when an expansion isn't available. This also includes when you select "Emmet: Expand Abbreviation" from the command palette or the Edit menu.
I assume this is unintended.

@noinkling That's an unfortunate side effect that existed earlier as well.
You see, the code running the expansion has no knowledge of how the expand abbreviation command was triggered i.e command pallet vs keyboard shortcut. It isn't aware of which keyboard shortcut was used either. This is why the setting emmet.trigerExpansionOnTab is important. That is how the code decides to fallback to tab->indent.
Am curious, why would you have both emmet.triggerExpansionOnTab enabled and have another keyboard shortcut.

Am curious, why would you have both emmet.triggerExpansionOnTab enabled and have another keyboard shortcut.

In reality I wouldn't personally, I just came across this while playing around. Some people might prefer chaos though 😄

This change should be marked in bold in release notes, if i didn't click on a small link pointing to list of fixed issues, i would not know what is wrong.
For about a week i was wondering what extension broke or what happened and i did not even update  VSC at home, to keep my TAB working :)
but finally i can just type div then TAB it again, so much less work ♥

I can't get emmet's tab completion to work:

{
    "emmet.triggerExpansionOnTab": true,
    "html.format.wrapAttributes": "force-aligned",
    "vsicons.projectDetection.autoReload": true,
    "workbench.iconTheme": "vs-seti",
    "terminal.integrated.shell.windows": "C:\\Program Files\\Git\\bin\\bash.exe",
    "window.zoomLevel": -1,
    "files.autoSave": "afterDelay",
    "editor.fontFamily": "Fira Code",
    "editor.fontLigatures": true,
    "editor.formatOnSave": true,
    "editor.tabSize": 2,
    "html.format.unformatted": "",
    "html.format.wrapLineLength": 80,
    "files.autoSaveDelay": 3000,
    "files.exclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/CVS": true,
        "**/.DS_Store": true,
        "**/*.js": {
            "when": "$(basename).ts"
        }
    },
    "typescript.tsdk": "./node_modules/typescript/lib",
}

I'm trying it on the line li>a[routerLinkActive="active" [routerLink]="['/applications']"].  But this error appears anytime I include [...] in my emmet snippet.  If I just have a normal HTML5 tag, it works fine, but I find it annoying to have to add all my attributes in after the fact.

@jakehockey10 You seem to have nested [] and I am not sure what your expected output is
li>a[routerLinkActive="active" routerLink="/applications"]
expands to

@ramya-rao-a I did have square brackets around routerLink because it needs to have those square brackets around routerLink after the expansion.  Before the last update, this was valid and upon pressing the tab key, I would get the following:

@jakehockey10 I'll look into the nested brackets
But you say even the outermost square brackets give you the error message. Can you try li>a[routerLinkActive="active" routerLink="/applications"] ?

Yes, that gives me the error as well :(

@jakehockey10 Let's continue this in a separate issue since this is specific to the square brackets in abbreviations (https://github.com/Microsoft/vscode/issues/32986)
This current issue has a lot of people and I don't want their notifications to be spammed

As a coder, the last month without emmet tab function is painful, I didn't realize 1.15.0 version abandoned emmet tab until I see this issue. I decided to go back to sublime because of this, though you finally fix this in new version, I still think that this kind of casual change on important functions should be avoided.

I'm not sure what happened in the latest updates, but I can't get any autocompletion on tab at all anymore. I have enabled and disabled all possible settings in userconfig.json and in keybindings. (For example, in settings.json: "editor.tabCompletion": true).
When I type div in the editor and press tab, nothing happens.
When I type < in the editor and choose a html tag from the list, and press enter, nothing happens. The tag is not even closed.

@Skura23 @KokoDoko Whenever you see a feature acting different or stopped working, please spare a few minutes in scanning through the Release Notes for that release.
Here are a few links that might interest you

Release Notes on Emmet for VS Code 1.15
Emmet 2.0 blog if you are interested in the why and the how
Docs for Emmet in VS Code for the current complete state of Emmet in VS Code

@ramya-rao-a I find the release notes somewhat unclear on what setting to set to true or false to get autocompletion working again. Either way, nothing I tried so far has worked... or is this expected behavior and do we need an extension just to autocomplete a html tag?

@KokoDoko If you are looking to auto complete
 to

, you need an extension for it in VS Code versions 1.15 and earlier. If you are on 1.16 you don't need an extension. See https://code.visualstudio.com/updates/v1_16#_html-close-tags
If you want to expand Emmet abbreviations and snippets using tab, set emmet.triggerExpansionOnTab to true. Read Docs for Emmet in VS Code for everything related to Emmet.
If the above still don't work for you , please open a new issue.
This current issue is about tab and Emmet which has already been resolved and I'd rather not spam the notifications of the many people already on this thread.

@KokoDoko i can personally recomment this one: https://marketplace.visualstudio.com/items?itemName=abusaidm.html-snippets

VS Code -v 1.16

So I have these settings:
  "emmet.triggerExpansionOnTab": true,
  "editor.wordBasedSuggestions": false,
  "emmet.showExpandedAbbreviation": "always"

What i get is this:
autocompletion-screenshot
As you can see "width: ;" is the fourth option because of the alphabetical order. Is there a way to prioritize the emmet type of autocompletions over those "key" options (intellisense options i guess)?
I wouldn't want to disable the "key" ones completely. It would be handy :).

@sebhewelt See https://code.visualstudio.com/updates/v1_16#_emmet-suggestions-as-snippets

Not working here... 😩
I've set
{
    "emmet.includeLanguages": {
	   "javascript": "javascriptreact"
    }
}

I've tried to expand App to <App></App> through  Emmet: Expand Abbreviation from Command Pallete, nothing. Language is set to JavaScript React (Babel), file extension is .js.
Driving me crazy

@selrond See if https://github.com/Microsoft/vscode/issues/34750 helps

@ramya-rao-a Wow!
It works, thanks!
However—how was I supposed to solve it by myself? Is there a way to see what language identifier I'm using in a file?

BTW, Tab extension still not working (even though it's set to true) but that's less of a problem for now

@selrond I understand this is one of the cases, where one couldnt have figured the solution out on one's own. I have logged an issue in the babel extension repo to see what can be done to get Emmet support in embedded languages out of the box. Once we get a decent solution there, I can reach out to other extensions that provides similar embedded language support.
You can use the Developer: Inspect TM Scopes command to get the language info under the cursor.

@ramya-rao-a Thanks for the Developer: Inspect TM Scopes tip, extremely helpful!

@ramya-rao-a

For tab still not working, can you log a separate issue and we can take it from there?

Here it is: #34929


Wording with SPN permissions

Assign Contributor permission to the SPN previously mentioned at the root management group scope (/), which allows tenant-level operations. This permission level ensures that the SPN can be used to deploy and manage resources to any subscription within your organization.
The wording tenant-level is wrong, the SPN ca only perform root management group scope and not tenant-leve

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

ID: e38786a5-e931-e614-55a1-2980b8a28087
Version Independent ID: a72b6f97-dd0f-252c-f6d9-f1c517aa9a2f
Content: Management group and subscription organization - Cloud Adoption Framework
Content Source: docs/ready/enterprise-scale/management-group-and-subscription-organization.md
Service: cloud-adoption-framework
Sub-service: ready
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#326066

This issue has been addressed.  Thank you for your feedback.


All ports are getting configured with same speed on Novus

when configuring the speed to 40 or 100 on the novus, all ports in the card are getting configured with 40 or 100 and other user ownership is getting cleared.
same thing tried manually, the vport configuration is applied to physical ports that were assigned to.

This should address in https://github.com/open-traffic-generator/ixnetwork/commit/6efdc9ce5883463113ba3a76624636c2b885e671

This should address in https://github.com/open-traffic-generator/ixnetwork/commit/6efdc9ce5883463113ba3a76624636c2b885e671


Some SafeFileApiNativeMethods do not supports OAuth credential

These function from Microsoft.InformationProtectionAndControl::SafeFileApiNativeMethods supports pass only SymmetricKeyCredential for credential:

IpcfEncryptFile
IpcfEncryptFileStream
IpcfDecryptFile
When you working against Rights Management Servers that have setup OAuth2 authentication, you need pass your OAuth2CallbackContext instead symmetric credential.

Code looks prepared for OAuth2, because all these functions calls SafeNativeMethods.CreateIpcPromptContext which supports OAuth2.
Note: You can inspire with my PR #25.

@kkanakas is any update / sample code regarding OAuth2 support?


Synthesis failed for Google.Cloud.Dialogflow.V2

Hello! Autosynth couldn't regenerate Google.Cloud.Dialogflow.V2. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to branch 'autosynth-Google.Cloud.Dialogflow.V2'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', 'synth.py', '--']
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.Dialogflow.V2/synth.py.
Cloning into 'gapic-generator'...
Cloning into 'gapic-generator-csharp'...
Submodule 'api-common-protos' (https://github.com/googleapis/api-common-protos.git) registered for path 'api-common-protos'
Submodule 'protobuf' (https://github.com/protocolbuffers/protobuf.git) registered for path 'protobuf'
Cloning into '/tmpfs/src/git/autosynth/working_repo/gapic-generator-csharp/api-common-protos'...
Cloning into '/tmpfs/src/git/autosynth/working_repo/gapic-generator-csharp/protobuf'...
Submodule path 'api-common-protos': checked out '6084c8a7fb1aea1d8440805e12fa8ebc6784de76'
Submodule path 'protobuf': checked out '74fa874537d8baa2fbff29a3ab71754995f6b0b7'
Submodule 'third_party/benchmark' (https://github.com/google/benchmark.git) registered for path 'protobuf/third_party/benchmark'
Submodule 'third_party/googletest' (https://github.com/google/googletest.git) registered for path 'protobuf/third_party/googletest'
Cloning into '/tmpfs/src/git/autosynth/working_repo/gapic-generator-csharp/protobuf/third_party/benchmark'...
Cloning into '/tmpfs/src/git/autosynth/working_repo/gapic-generator-csharp/protobuf/third_party/googletest'...
Submodule path 'protobuf/third_party/benchmark': checked out '5b7683f49e1e9223cf9927b24f6fd3d6bd82e3f8'
Submodule path 'protobuf/third_party/googletest': checked out 'c3bb0ee2a63279a803aaad956b9b26d74bf9e6e2'
Cloning into 'googleapis'...
> Task :buildSrc:compileJava NO-SOURCE
> Task :buildSrc:compileGroovy
> Task :buildSrc:processResources NO-SOURCE
> Task :buildSrc:classes
> Task :buildSrc:jar
> Task :buildSrc:assemble
> Task :buildSrc:compileTestJava NO-SOURCE
> Task :buildSrc:compileTestGroovy NO-SOURCE
> Task :buildSrc:processTestResources NO-SOURCE
> Task :buildSrc:testClasses UP-TO-DATE
> Task :buildSrc:test NO-SOURCE
> Task :buildSrc:check UP-TO-DATE
> Task :buildSrc:build
> Task :extractIncludeProto
> Task :extractProto
> Task :generateProto

> Task :compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

> Task :processResources
> Task :createProperties
> Task :classes
> Task :shadowJar

BUILD SUCCESSFUL in 12s
7 actionable tasks: 7 executed
Generating Google.Cloud.Dialogflow.V2
ERROR: google/longrunning/operations.proto:74:3: http: In path template 'v2/{name=projects/*/operations/*}': effective path must start with leading '/'.
ERROR: google/longrunning/operations.proto:74:3: http: In path template 'v2/{name=projects/*/operations/*}': effective path must start with leading '/'.
cp: cannot stat ‘tmp/Google.Cloud.Dialogflow.V2/Google.Cloud.Dialogflow.V2’: No such file or directory
synthtool > Failed executing /bin/bash generateapis.sh Google.Cloud.Dialogflow.V2:

None
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 87, in <module>
    main()
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 79, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 205, in _call_with_frames_removed
  File "/tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.Dialogflow.V2/synth.py", line 20, in <module>
    hide_output = False)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 418, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '('/bin/bash', 'generateapis.sh', 'Google.Cloud.Dialogflow.V2')' returned non-zero exit status 1.
synthtool > Wrote metadata to synth.metadata.

Synthesis failed

Google internal developers can see the full log here.

It looks like this is a genuine error which is likely to trip up other languages. Looking into it.

This is due to a bug in the service YAML file. Will get it fixed internally.

Autosynth passed, closing! :green_heart:


Fix documentation error relating to File.cwd()!

File.cwd()! is not a valid elixir syntax. I have amended it to File.cwd!() instead.

Thank you! 💖💖💖💖


fixed spelling issue in key concepts

@danvega Thank you for signing the Contributor License Agreement!

late to merge, but thanks.  Fixed in 5ca54af25fa1a93f535f276e793c41997d53bc18


libWPEBackend-fdo-1.0.so installed but not shipped

ERROR: recipe wpebackend-fdo-1.0.0git-r0: task do_populate_sysroot: Succeeded
ERROR: wpebackend-fdo-1.0.0git-r0 do_package: QA Issue: wpebackend-fdo: Files/directories were installed but not shipped in any package:
/usr/lib/libWPEBackend-fdo-1.0.so
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid install
**Root cause: **
Bump API version to 1.0 in preparation for the 1.2.x series
https://github.com/Igalia/WPEBackend-fdo/commit/b5de2adbbbdba391b54d0c014f35fca431ecd520

that's for WPE WebKit 2.24, @aperezdc  is going to merge it to the release branch today. Will be in wpebackend-fdo 1.2.x as well, also will make the release branch today.

The wpebackend-fdo-1.2 release branch is now available. Later I will be doing a 1.3.90 release candidate.


i used the dockerfile to build images, then an error appeared when running a container.

sh entrypoint.sh
==> /home/logs/gunicorn-access.log <==
==> /home/logs/gunicorn.log <==
[2019-04-29 07:37:42 +0000] [7] [INFO] Starting gunicorn 19.9.0
[2019-04-29 07:37:42 +0000] [7] [INFO] Listening at: http://<IP_ADDRESS>:8000 (7)
[2019-04-29 07:37:42 +0000] [7] [INFO] Using worker: sanic.worker.GunicornWorker
[2019-04-29 07:37:42 +0000] [15] [INFO] Booting worker with pid: 15
[2019-04-29 07:37:43 +0000] [17] [INFO] Booting worker with pid: 17
[2019-04-29 07:37:43 +0000] [19] [INFO] Booting worker with pid: 19
[2019-04-29 07:37:43 +0000] [21] [INFO] Booting worker with pid: 21
[2019-04-29 07:37:43 +0000] [22] [INFO] Booting worker with pid: 22
/usr/local/lib/python3.6/dist-packages/sklearn/ensemble/weight_boosting.py:29: DeprecationWarning: numpy.core.umath_tests is an internal NumPy module and should not be imported. It will be removed in a future NumPy release.
from numpy.core.umath_tests import inner1d
/usr/local/lib/python3.6/dist-packages/sklearn/ensemble/weight_boosting.py:29: DeprecationWarning: numpy.core.umath_tests is an internal NumPy module and should not be imported. It will be removed in a future NumPy release.
from numpy.core.umath_tests import inner1d
/usr/local/lib/python3.6/dist-packages/sklearn/ensemble/weight_boosting.py:29: DeprecationWarning: numpy.core.umath_tests is an internal NumPy module and should not be imported. It will be removed in a future NumPy release.
from numpy.core.umath_tests import inner1d
/usr/local/lib/python3.6/dist-packages/sklearn/ensemble/weight_boosting.py:29: DeprecationWarning: numpy.core.umath_tests is an internal NumPy module and should not be imported. It will be removed in a future NumPy release.
from numpy.core.umath_tests import inner1d
/usr/local/lib/python3.6/dist-packages/sklearn/ensemble/weight_boosting.py:29: DeprecationWarning: numpy.core.umath_tests is an internal NumPy module and should not be imported. It will be removed in a future NumPy release.
from numpy.core.umath_tests import inner1d
INFO:sanic.root:using static path /home/dataplay/filesvc/../static
INFO:sanic.root:using static path /home/dataplay/filesvc/../static
INFO:sanic.root:using static path /home/dataplay/filesvc/../static
INFO:sanic.root:using static path /home/dataplay/filesvc/../static
INFO:sanic.root:using static path /home/dataplay/filesvc/../static
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 210, in run
self.sleep()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 360, in sleep
ready = select.select([self.PIPE[0]], [], [], 1.0)
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 245, in handle_chld
self.reap_workers()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 525, in reap_workers
raise HaltServer(reason, self.WORKER_BOOT_ERROR)
gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/gunicorn", line 10, in
sys.exit(run())
File "/usr/local/lib/python3.6/dist-packages/gunicorn/app/wsgiapp.py", line 61, in run
WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/app/base.py", line 223, in run
super(Application, self).run()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/app/base.py", line 72, in run
Arbiter(self).run()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 232, in run
self.halt(reason=inst.reason, exit_status=inst.exit_status)
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 345, in halt
self.stop()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 393, in stop
time.sleep(0.1)
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 245, in handle_chld
self.reap_workers()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 525, in reap_workers
raise HaltServer(reason, self.WORKER_BOOT_ERROR)
gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3>
[2019-04-29 07:37:53 +0000] [19] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/gunicorn/arbiter.py", line 583, in spawn_worker
worker.init_process()
File "/usr/local/lib/python3.6/dist-packages/sanic/worker.py", line 51, in init_process
super().init_process()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/workers/base.py", line 129, in init_process
self.load_wsgi()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/workers/base.py", line 138, in load_wsgi
self.wsgi = self.app.wsgi()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/app/base.py", line 67, in wsgi
self.callable = self.load()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/app/wsgiapp.py", line 52, in load
return self.load_wsgiapp()
File "/usr/local/lib/python3.6/dist-packages/gunicorn/app/wsgiapp.py", line 41, in load_wsgiapp
return util.import_app(self.app_uri)
File "/usr/local/lib/python3.6/dist-packages/gunicorn/util.py", line 350, in import_app
import(module)
File "/home/dataplay/server.py", line 39, in
app.blueprint(file_svc)
File "/usr/local/lib/python3.6/dist-packages/sanic/app.py", line 555, in blueprint
blueprint.register(self, options)
File "/usr/local/lib/python3.6/dist-packages/sanic/blueprints.py", line 141, in register
uri, future.file_or_directory, *future.args, **future.kwargs
File "/usr/local/lib/python3.6/dist-packages/sanic/app.py", line 533, in static
content_type,
File "/usr/local/lib/python3.6/dist-packages/sanic/static.py", line 146, in register
)(_handler)
File "/usr/local/lib/python3.6/dist-packages/sanic/app.py", line 192, in response
name=name,
File "/usr/local/lib/python3.6/dist-packages/sanic/router.py", line 147, in add
self._add(uri, methods, handler, host, name)
File "/usr/local/lib/python3.6/dist-packages/sanic/router.py", line 303, in _add
route = merge_route(route, methods, handler)
File "/usr/local/lib/python3.6/dist-packages/sanic/router.py", line 255, in merge_route
uri, ",".join(list(duplicated))
sanic.router.RouteExists: Route already registered: /ui<file_uri:/?.+> [GET,HEAD]

Yes, it seems something wrong with route, did you have that issue when you run locally out of docker?  I mean run doit sever

the current dockerfile need improving to make it self contained, will fix it.

thanks for your time, I have successful to start the server in the container by 'doit server'. but an other problem arises. the Listening address is <IP_ADDRESS>:8000, I cannot access outside.
/code/dataplay3/server # doit server &
/code/dataplay3/server # .  server
[2019-04-30 11:03:31 +0000] [1595] [INFO] Starting gunicorn 19.9.0
[2019-04-30 11:03:31 +0000] [1595] [INFO] Listening at: http://<IP_ADDRESS>:8000 (1595)
[2019-04-30 11:03:31 +0000] [1595] [INFO] Using worker: sanic.worker.GunicornWorker
[2019-04-30 11:03:31 +0000] [1609] [INFO] Booting worker with pid: 1609
[2019-04-30 11:03:31 +0000] [1610] [INFO] Booting worker with pid: 1610
[2019-04-30 11:03:32 +0000] [1611] [INFO] Booting worker with pid: 1611
[2019-04-30 11:03:32 +0000] [1612] [INFO] Booting worker with pid: 1612
[2019-04-30 11:03:32 +0000] [1613] [INFO] Booting worker with pid: 1613
INFO:sanic.root:using static path /code/dataplay3/server/dataplay/filesvc/../static
INFO:sanic.root:using static path /code/dataplay3/server/dataplay/filesvc/../static
INFO:sanic.root:using static path /code/dataplay3/server/dataplay/filesvc/../static
INFO:sanic.root:using static path /code/dataplay3/server/dataplay/filesvc/../static
INFO:sanic.root:using static path /code/dataplay3/server/dataplay/filesvc/../static
/code/dataplay3/server # curl <IP_ADDRESS>:8000
[2019-04-30 11:03:59 +0000] - (sanic.access)[INFO][<IP_ADDRESS>:58220]: GET http://<IP_ADDRESS>:8000/  302 0
INFO:sanic.access:
/code/dataplay3/server # ps
PID   USER     TIME  COMMAND
1 root      0:00 /bin/sh
1594 root      0:00 {doit} /usr/local/bin/python /usr/local/bin/doit server
1595 root      0:00 {gunicorn} /usr/local/bin/python /usr/local/bin/gunicorn dataplay.server:app 鈥攂ind=<IP_ADDRESS>:8000 --worker-class=sanic.worker.GunicornWorker --workers=5
1609 root      0:01 {gunicorn} /usr/local/bin/python /usr/local/bin/gunicorn dataplay.server:app 鈥攂ind=<IP_ADDRESS>:8000 --worker-class=sanic.worker.GunicornWorker --workers=5
1610 root      0:01 {gunicorn} /usr/local/bin/python /usr/local/bin/gunicorn dataplay.server:app 鈥攂ind=<IP_ADDRESS>:8000 --worker-class=sanic.worker.GunicornWorker --workers=5
1611 root      0:01 {gunicorn} /usr/local/bin/python /usr/local/bin/gunicorn dataplay.server:app 鈥攂ind=<IP_ADDRESS>:8000 --worker-class=sanic.worker.GunicornWorker --workers=5
1612 root      0:01 {gunicorn} /usr/local/bin/python /usr/local/bin/gunicorn dataplay.server:app 鈥攂ind=<IP_ADDRESS>:8000 --worker-class=sanic.worker.GunicornWorker --workers=5
1613 root      0:01 {gunicorn} /usr/local/bin/python /usr/local/bin/gunicorn dataplay.server:app 鈥攂ind=<IP_ADDRESS>:8000 --worker-class=sanic.worker.GunicornWorker --workers=5
1614 root      0:00 /usr/local/bin/python -c from multiprocessing.semaphore_tracker import main;main(17)
1615 root      0:00 /usr/local/bin/python -c from multiprocessing.semaphore_tracker import main;main(17)
1616 root      0:00 /usr/local/bin/python -c from multiprocessing.semaphore_tracker import main;main(17)
1617 root      0:00 /usr/local/bin/python -c from multiprocessing.semaphore_tracker import main;main(17)
1618 root      0:00 /usr/local/bin/python -c from multiprocessing.semaphore_tracker import main;main(17)
1620 root      0:00 ps

did you try to run make docker and then make run from dataplay dir? that will build a docker locally and run it for you.

I have made some change to the dockerfile, check if that fix your problem


Implements 5.4. Download the top-level targets metadata file

Implements 5.4 to 5.4.4 which is similar to the logic for the snashot.json file in 5.3.x.
The logic in 5.4.5 is targets specific so my plan was to do 5.4.5 to <IP_ADDRESS>.3(the last step in 5.4) in the next PR

Good job, guys, I'm here myself with tuf-on-a-plane

@trishankatdatadog I think I remember what a plane is 😂


vkquake: install a deskstop file

The PR does the following things:

It copies an icon file for vkQuake and installs a vkquake.desktop file.
It also formats the code using nixfmt-rfc-style and explicitly targets the GitHub tag using the refs/tags prefix.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Will conflict with https://github.com/NixOS/nixpkgs/pull/354942. Maybe submit a code review with your changes on that PR?


window is undefined

This happens in both the Editor and this package. It seems you use the window in the code which is not available when compiling in a nodejs environment.
Can we remove window object from the code?

Duplicates https://github.com/jpuri/html-to-draftjs/issues/78 .


fixing key control for gaming demo

Fire keydown when class first is predicted, fire keyup when class stops being predicted. This is much more natural for gameplay.

This change is

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Abandoning for larger change.


SYS_getrandom undefined

Hi,
I was trying out your package and ran into some compilations issues. I had some looking around and found a related error call (here), but I am not running the mentioned kernel there (<3.17 vs 5.19.4) do you perhaps know how to solve this underlying issue?
Detail:
nim 1.6.4

 output
/home/casper/.cache/nim/nimwc_main_r/stdlib_sysrand.nim.c: In function 'urandomInternalImpl__stdZsysrand_17':
/home/casper/.cache/nim/nimwc_main_r/stdlib_sysrand.nim.c:61:56: error: 'SYS_getrandom' undeclared (first use in this function); did you mean 'SYS_getuid'?
   61 |                         readBytesX60gensym0_ = syscall(SYS_getrandom, ((void*) ((&dest[result]))), ((int) ((NI)(TM__sT0fWggTrXhnxQ79bl9a8nHg_2))), ((unsigned int) 0));
      |                                                        ^~~~~~~~~~~~~
      |                                                        SYS_getuid
/home/casper/.cache/nim/nimwc_main_r/stdlib_sysrand.nim.c:61:56: note: each undeclared identifier is reported only once for each function it appears in
Error: execution of an external compiler program 'gcc -c  -w -fmax-errors=3 -O3 -fno-strict-aliasing -fno-ident   -I/home/casper/.choosenim/toolchains/nim-1.6.4/lib -I/home/casper/projects/nimwc/nimwcpkg -o /home/casper/.cache/nim/nimwc_main_r/stdlib_sysrand.nim.c.o /home/casper/.cache/nim/nimwc_main_r/stdlib_sysrand.nim.c' failed with exit code: 1

Hi @cvanelteren
That is a new one to me. Could you try adding -d:nimNoGetRandom to nimwc.nim.cfg before compiling?

The problem is coming from this:
https://github.com/ThomasTJdev/nim_websitecreator/blob/25da50c01a15338336d9a624c729f8f51c9697a0/nimwcpkg/passwords/passwords.nim
let useUrandom = urandom.open("/dev/urandom")

You could try setting that to false. That will affect the makeSalt() procedure to not using urandom.

Unfortunately, same error when setting it to false. It seems like it is not an issue with nimwc, the error originates from the stdlib it seems.

This automagically fixed itself, closed!

Perfect 😃
tor. 29. sep. 2022 20.47 skrev Casper van Elteren @.***

:

This automagically fixed itself, closed!
—
Reply to this email directly, view it on GitHub
https://github.com/ThomasTJdev/nim_websitecreator/issues/142#issuecomment-1262680279,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAONDOHFVJNVUTVJ7W453UDWAXP43ANCNFSM6AAAAAAQIZULFI
.
You are receiving this because you commented.Message ID:
@.***>


Reference data is unusable

From @skwalker:
This definitely used to work, but currently reference data can't be used as an input for a job, because there are hyphens in the key name, and apparently that's no longer kosher. This is to the point that the officially recommended fix is to add the reference data in Terra and fix the key names in FC.
We either need to change how we construct the keys here, or fix whatever underlying issue has made the dashes invalid, assuming it wasn't intentional.

Closing as duplicate of #1312


Testing pull_request triggers from PRs

Can this be triggered without being merged?

This doesn't actually trigger a github action, which matches my expectation - arbitrary users can't trigger actions, only merges can.


Add views between services and API routes in dashboard

In the arch diagram, add a clickable 'routes' box between APIs and services to display all route details.
In the API Explorer, show which service the API originates from and provide a way to display an "Open in VSCode" button.

Referenced by in API explorer:

Will wrap to a column if more than 3 services.

reference added to api explorer routes:


Add SO terms for meiotic and mitotic recombination regions

INSDC will soon be adding a recombination_class for recombination features, to include class types for both meiotic and mitotic recombination regions, also non_allelic_homologous_recombination (SO:0002094), breakpoint_junction (SO:0001021) and other (SO:0000298). Since the former two currently lack a specific SO term, can you add one for each of those?
The intended INSDC terms and definitions for these are:
Term: meiotic_recombination
Definition: A genomic region in which there is an exchange of genetic material as a result of the repair of meiosis-specific double strand breaks that occur during meiotic prophase.
Term: mitotic_recombination
Definition: A genomic region where there is an exchange of genetic material with another genomic region, occurring in somatic cells.
Thanks for considering these!
Catherine Farrell, Ph.D
Staff Scientist - RefSeq Project
NCBI/NLM/NIH

How would you feel if we called them mitotic_recombination_region and meiotic_recombination_region?

I'll weigh in for Catherine, who is out on vacation for another week. We discussed it here and agree mitotic_recombination_region and meiotic_recombination_region make sense for the SO terms. Thanks for the additions.
Best regards,
-Terence Murphy, Ph.D.
NCBI/NLM/NIH

SO:0002154 - mit
SO:0002155 - mei
added - will be checked in shortly


Suggestion: Goodness.ai

Hey there,
Firstly, although I'm no expert in AI, it seems like there's some really great work going on here! Just wanted to make a suggestion that I've been thinking of for a long while.
There's a badness.ai to catalogue all the bad things AI can possibly do (and thus help fix those). Could a sister platform (similarly designed) be created to catalogue the good aspects too (goodness.ai)? More specifically, I feel a catalogue of all the known use cases of generative AI would be immensely helpful. The internet is full of people who have discovered things they Generative AI can do (there's literally a linkedin page on Generative AI showcasing these). If this information could be compiled effectively, it would make it much easier for people to become inspired about what the AI tools can do and help raise full awareness about its capabilities. I follow AI news regularly and am amazed by the new tools coming up, but I fail to effectively integrate them into my life – I just never realise "oh, this is something I could get the AI to do and here's how". Having a catalogue like goodness.ai would be helpful.
What do you think? Am I making sense?
I'd love to start this thing off myself; unfortunately, I'm too caught up in work to take on the big first step!

Thanks for this suggestion! You bring up a really interesting idea. To me, the generative AI startup landscape today is a fairly representative sample of the different positive use cases and capabilities of modern generative AI. There's almost a market incentive to document this "goodness." For example, many folks have put out comprehensive generative AI market maps that also serve as catalogs of useful, good things that AI systems can do.
On the other hand, there's not much of an incentive to document when things go wrong, even though it's really important for practitioners to learn from mistakes. That's why we focused Badness.ai on that side of the story and structured it as an open-source collaborative catalog.
Let me know what you think!

Closing for now, but I hope we can keep this conversation going!

Fair point @coderrg! I didn't think of it from that perspective. Thanks for that link!


Index

Add an index property to Scatter to add an extra dimension such as the time
to x,y,z array and to be able to use it in an embed version.

Ok, the comments are not in the order I put them in, I hope you can follow them (the check that failed is a travis error, don't worry about it).

I just updated and modified accordingly. I just kept the  animation_time_index , because if not it does not work

Yes you are right.
In another branch I started to play with having different color for different points
Time + color
For  this I introduce a multi_colors component that can be 1D or 2D

Check out (Union)[https://github.com/ipython/traitlets/blob/35b0f68f7b3652d36d06f7528748d5778c632a73/traitlets/traitlets.py#L1792], I think color should be able to be a string, a list of strings (or a sequence or a list of strings actually) (and later also support for an array of float, in combination with a colormap). Would love to see this in a PR as well! But lets first finish this one.

Coverage increased (+0.02%) to 86.47% when pulling 821af84bcf7eaaed4c9b672f50dc4bc15fc30934 on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

Coverage increased (+0.02%) to 86.47% when pulling 821af84bcf7eaaed4c9b672f50dc4bc15fc30934 on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

Coverage increased (+0.02%) to 86.47% when pulling 821af84bcf7eaaed4c9b672f50dc4bc15fc30934 on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

Coverage increased (+0.02%) to 86.47% when pulling 821af84bcf7eaaed4c9b672f50dc4bc15fc30934 on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

I added the check with x, y , z on create_mesh.
But I also merged your changes, and the new coordinate are not taken into account anymore.

I added a demo notebook to try it

Is it a real problem to keep animation_time_index

Yeah, no need for it, I send you the fix for that.

Ok, I'd like to keep this PR clean, if you drop the notebook (I have a copy, I'll make sure I'll it goes somewhere in the examples, or in the docs), and confirm that it is working, I can accept this PR.

Ok its done ! And I confirm it works!

Coverage increased (+0.02%) to 86.47% when pulling ccc3921df120b0ae84d128f23e05e5c7c6759b3a on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

Coverage increased (+0.02%) to 86.47% when pulling ccc3921df120b0ae84d128f23e05e5c7c6759b3a on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

Coverage increased (+0.02%) to 86.47% when pulling ccc3921df120b0ae84d128f23e05e5c7c6759b3a on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

Great! thank you!

Thank you, check this out:
https://www.astro.rug.nl/~breddels/test/stream.html
Something I had in mind, but you made possible (it's a stellar stream, simulation of small galaxy getting ripped apart, you don't see the host galaxy)

So cool!!!!
It is really nice to watch !
What widget did you use to have this play button?

Thank, I didn't do the simulation btw.
See http://ipywidgets.readthedocs.io/en/latest/examples/Widget List.html#Play-(Animation)-widget

It really combines well with the animation/interpolation, you can get away with a coarse timestep.

And if you refresh it, you'll see velocities are also working, nice work :+1:

Coverage increased (+0.02%) to 86.47% when pulling 6ac4a108060bc47b725cbb161cdfe2e8b4407eda on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

Coverage increased (+0.02%) to 86.47% when pulling 6ac4a108060bc47b725cbb161cdfe2e8b4407eda on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

Coverage increased (+0.02%) to 86.47% when pulling 6ac4a108060bc47b725cbb161cdfe2e8b4407eda on jeammimi:Index into 2828f934e30d05a5552e2dfc94663393ba1311f3 on maartenbreddels:master.

It is really nice!
To make it ligther ( in terms of megabite) I multilply x ,y , ... by a scale factor, and then
I give np.array(x,dtype=np.int) to your function. If you give it the float version, it is going to keep a lot
of numbers that are not necessary.


not an issue

but can this project be uploaded on valve store as a tool or it cant?

@massatt212 that would be tight im down


nft extension detection v5

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4399  👈
#4397
#4395
#4394
#4392
#4391
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jnsdls and the rest of your teammates on  Graphite


Implement evaluation context transformer requirement (1.6.1) and test

Requirement 1.6.1

The client SHOULD transform the evaluation context using the provider's context transformer function if one is defined, before passing the result of the transformation to the provider's flag resolution functions.

Replace this todo with the test.

Without having access to generics implementing this requirement isn't as trivial as one would hope.
If I've understood the intent, we want to allow providers to transform the EvaluationContext into their own custom type.
The only way I can envision this happening is by changing the FeatureProvider's EvaluationContext function parameter to the interface{} type. This isn't ideal as it'd mean that the Provider would be forced to assert the EvaluationContext's type in its calls. This would be especially cumbersome for Providers that don't want to transform an EvaluationContext, they'd still be forced to assert the interface{} to EvaluationContext.
Is this an acceptable downside? Can we find another way of achieving this behaviour without burdening the Providers with the type assertions?
@toddbaert @beeme1mr @james-milligan

Technically this isn't required by the spec. Perhaps the go lang SDK simply doesn't support a context transformer.
There was recently a proposal to add support to the spec for provider hooks. Perhaps that would be sufficient in this case.

Technically this isn't required by the spec. Perhaps the go lang SDK simply doesn't support a context transformer.
There was recently a proposal to add support to the spec for provider hooks. Perhaps that would be sufficient in this case.

As this isn't strictly required by the spec I'm closing this. Perhaps it can be revisited when upgrading to 1.18


Move goal execution to general handling

I'm creating this issue to track an architectural direction of the code, a major refactoring that is not fully complete.
Goals used to each have their own handler class. This was necessary to get each subscription a different name, because they didn't work right otherwise.
Now we have ExecuteGoalOnRequested and ExecuteGoalOnSuccessStatus, and I'm moving goal handlers to use them.
These general ones are moving toward handling the SdmGoal updates as well. It is recommended to use them in that way -- currently that means passing a "true" to the constructor. Once they all pass 'true' that will become the default.
Sometime, we will create FunctionalUnits for each goal based on whether it has preconditions (needs to trigger on success of other goals; when parameters work we can even wait a more specific list) or not (OnRequested is sufficient).

this does not have to be complete for any particular release


Added option for redirctUri to authProvider

Purpose
Adds an option to specify the redirect URI when configuring the auth provider, which is passed through to the same option in the MSAL UserAgentApplication.
Does this introduce a breaking change?
[ ] Yes
[x] No
Pull Request Type
What kind of change does this Pull Request introduce?
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:
How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information
This addresses the issue covered by #55

 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.:x: abrunyee sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Profiling alpha version

Alpha, experimental, unstable (and all of the other warning words) version of profiling.
Profiling is set to be disabled by default, when using instrumentation via CLI, SPLUNK_PROFILER_ENABLED=true needs to be set.
Or when using advanced options, startProfiling({ serviceName: 'my-service' }) can be called instead.
By default call stacks are sampled with a 1 second interval and the collection is done for 60s after which they are processed and exported.
Exporting is currently done via a custom OTLP logs exporter - meant as a placeholder until we contribute one to OpenTelemetry.
Additional testing will be available in the next PR when we are reaching beta state.
For more of the technical details refer to our design doc.

+1 Awesome work. The cpp parts are mostly magic for me.
There was a discussion between us about moving compiled resources into a separate package after the implementation of the metrics. IIRC you were looking into introducing another repo? Now there's even more of that and I feel even stronger separating those concerns.

My current thinking is to keep them in the same codebase (feel free to sway me in either direction).
Points for the native extension being in a separate package:

CI is a bit faster
Codebase is slightly smaller to navigate in

Points against the native extension being in the same package:

More maintenance overhead (maintaining 4 different CIs instead of 2 due to the repo mirroring we have :weary:)
Slower feedback loop when developing (build the native package, then build this package and then do the test runs)

At the moment I haven't put it into a separate repo just because it's less work to do so.


Fix: Use data provider

This PR

[x] uses data providers

Related to https://github.com/opencfp/opencfp/pull/852#issuecomment-349336156.
💁♂ Probably best reviewed with https://github.com/opencfp/opencfp/pull/853/files?diff=split.

Thank you, @BackEndTea!


Add missing nullability macros HUBComponentFallbackHandler.h

Makes sure Swift implementors don’t get the force-unwrap of the types by default.
@spotify/objc-dev

Current coverage is 93.02% (diff: 100%)

Merging #184 into master will not change coverage

@@             master       #184   diff @@
==========================================
  Files            63         63
  Lines          4547       4547
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           4230       4230
  Misses          317        317
  Partials          0          0

Powered by Codecov. Last update 6e9b712...3ee2e15

Awesome @rastersize! 🚀


[DPR2-1363] Dashboard/interactive filters

Also will addition the dashboard filter to the DashBoard and DashBoardDefinition classes be part of next changes?


Make host application define URL schemes

KeyboardKit Pro 8.6 added a new KeyboardHostApplication enum, that defined many popular apps and made it easy to identify them with the controller or keyboard context.
KeyboardKit Pro 8.7 will extend this information, and also add an optional URL scheme, which can resolve a URL that can be used to open most of the pre-defined apps.
This will hopefully make it possible to navigate back to some of the most popular apps, when performing in-app dictation.

This has been added to the v8.7 branch.


Add Shota Matsuo to Contributors list

Congratulations on your Pull Request! See you in the next class.


Cannot resolve module fbjs/lib/invariant in /react-phaser/~/react-anything/src/ReactAnythingMount.js 25:16-45

ERROR in ./~/react-phaser/~/react-anything/src/ReactAnythingMount.js
Module not found: Error: Cannot resolve module 'fbjs/lib/invariant' in /gamegen/node_modules/react-phaser/node_modules/react-anything/src
 @ ./~/react-phaser/~/react-anything/src/ReactAnythingMount.js 25:16-45

can you try
npm install fbjs

seems to fix it


GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging<EMAIL_ADDRESS>

Hi,
Doing a ddev start this morning and I've bumped into an issue that I'm struggling to fix.
Reading package lists...
W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging<EMAIL_ADDRESS>E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
', stderr='Building db
Building web
Service 'web' failed to build : The command '/bin/sh -c apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests build-essential' returned a non-zero code: 100'

A Google of this and I've seen there is a fix: https://github.com/yarnpkg/yarn/issues/7866
My problem is I'm not so hot on docker so I'm struggling to figure out where this fix needs to go.
Cheers
Tom
DDEV version: 1.16.5
Docker Dekstop: 3.0.4 (updated to 3.1.0 and no change)
MacBook Pro: Catalina 10.15.7

Can confirm this for v1.16.5 as well as v1.17.0-alpha3 on MacOS

I found a fix by adding
#temp gpg error fix
RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
#temp gpg error fix
RUN apt-get update

to my web-build/Dockerfile
@carstendietrich any chance you could post a code snippet for your fix? Looks a bit cleaner than mine!

Same here, quickfix suggested by @tommym9 solves the problem for now. Hope there will be an official fix/release for this soon.

@tommym9 in my project I don't have any complex setup therefore I only rely on the webimage_extra_packages option in the .ddev/config.yaml for adding additional apt packages. Therefore I don't have a dedicated web-build/Dockerfile since adding that will disable the webimage_extra_packages setting.
So as a temporary fix I pretty much did the same as you, only that I needed to add the web-build/Dockerfile manually and add the stuff that I had previously specified in webimage_extra_packages.
So my web-build/Dockerfile now looks like this:
ARG BASE_IMAGE
FROM $BASE_IMAGE

# fix yarn key
RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -

# install packages previously set in webimage_extra_packages
RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests php7.1-mcrypt php7.1-tidy make redis-tools

Guess now we are waiting for an updated web-base image that already contains the latest yarn key.

It's amazing that this happens every Feb 1. This is https://github.com/yarnpkg/yarn/issues/6865 and it just seems to be every single year.
I guess I'll need to do a release. The two answers here are perfect.

It's amazing that this happens every Feb 1. This is yarnpkg/yarn#6865 and it just seems to be every single year.
I guess I'll need to do a release. The two answers here are perfect.

Yeah or maybe switch the way Yarn is installed. According to docs it is recommended to use NPM for installing Yarn globally: https://yarnpkg.com/getting-started/install
That could avoid the yearly key issue 😁

I can definitely switch to the npm approach. Will that break people?

The current shipping/installed version of yarn in the ddev web container is 1.22.5 - the npm approach will switch to yarn v2.

I note that the problem in this issue probably only affects people who one way or another do an apt-get update in their project, either via webimage_extra_packages or a custom Dockerfile. So it won't affect all ddev users right away.

As far as I understand the docs this shouldn't be breaking. If you install yarn globally via NPM you get version 1.22.10..
If you want to use yarn v2 and all later versions you need to actively switch on a per-project basis via: yarn set version berry (this will set v2 for the project folder you're in)

Using a single package manager across your system has always been a problem. To be stable, installs need to be run with the same package manager version across environments, otherwise there's a risk we introduce accidental breaking changes between versions - after all, that's why the concept of lockfile was introduced in the first place! And with Yarn being in a sense your very first project dependency, it should make sense to "lock it" as well.
For this reason, Yarn 2 and later are meant to be managed on a by-project basis.

https://yarnpkg.com/getting-started/install

Thanks, yes, just installing via npm gets v1; I missed that part. I'll do a new v1.16.6 release and also fix it for v1.17 in https://github.com/drud/ddev-images/pull/43

It's amazing that this happens every Feb 1. This is yarnpkg/yarn#6865 (and yarnpkg/yarn#7866 as mentioned above) and it just seems to be every single year.

I've been meaning to fix it so that the Yarn key can be automatically renewed (eg by packaging it in a Debian package), but never got around to it, and so far nobody else has been willing to spend time to help with it.

Thanks @Daniel15 - I'm changing this to use the npm installation technique. That will solve everything right?

Thanks so much for reporting this issue @tommym9 and @carstendietrich - ddev v1.16.6 and v1.17.0-alpha4 are building right now and will be available shortly. Please check to make sure they resolve your issues.

I'm changing this to use the npm installation technique. That will solve everything right?

Sure.
It's only an issue with GPG signing. npm repositories are not signed at all, so there's no problem, in the same way that you can solve the issue of losing or breaking your keys by removing the lock from your front door :)


Design: One-pager content development

User story
As a prospective ReportStream partner, I need to understand ReportStream's offerings in a concise sell sheet format, so I can make an informed decision to partner with ReportStream and/or share back with my organization.
Background & context
This is the sister content ticket of Create ReportStream one-pager draft design #9440. This ticket captures the work of content development for the sell sheet: creating a content outline, draft content, and circulating for review throughout the development process.
Open questions

What metrics would we like to capture in this sell sheet and how can we get the answers?
Is it possible for design to begin to evaluate and quantify what it takes to get onboarded to RS (it’s free, but what time/money investment is needed for onboarding + maintenance?)

Working links

Resource: Secondary branch research
Outline word document
Figma link to come

Next steps

[x] Design meet with content strategist to brief
[ ] Design take first pass at outlining sell sheet content
[ ] Review with cross team members (particularly Content and Engagement team) and revise per feedback

Acceptance criteria

[ ] Draft one-pager content created for review
[ ] Reviewed in public channel and/or All Teams Sync, with direct feedback ask from Engagement team
[ ] Reviewed by client-facing stakeholders

hi @lizzieamanning and @audreykwr, tagging you here for awareness! audrey, we decided to split the content work into a separate ticket from the design work. see the next steps outlined above and lmk if you have thoughts.

hi @chris-kuryak, letting you know I broke the one-pager development into separate tickets (design #9440 and content #9470, this ticket is the latter).
I gave it 5pts due to the review dependencies. this work will begin this sprint and can go into Sprint Backlog, if ok by you. thank you!

Thanks @jillian-hammer as this is a content task, will this be taken up by Audrey?

since Audrey's plate is pretty full, Lizzie and I will work on the draft outline & content and involve Audrey as a reviewer. I imagine she will be more heavily involved during the content finalization period, but that will be a separate ticket. @chris-kuryak

Hey @jillian-hammer nice work on splitting the ticket! Do we need to move design #9440 into Backlog or In Progress?

@Andrey-Glazkv thanks! I believe #9440 is already in the Sprint Backlog. it's not ready to be moved into In Progress yet.

Status: on track, collecting feedback from engagement team

On track alongside overlapping messaging work

status: in review with design team + lead

Need to be approved by Mo

Closing, @audreykwr incorporated Mo's comments into the WIP one pager document. thanks audrey!


[Map] DM-FSW-Hotel-FreakShow][

Hash: ba0562fcaea190cbf39237268a43a5f87a23b7f5
Current name: DM-FSW-Hotel-FreakShow][
This author has other aliases which include his real name Michael Lalla

These include  Michael<(DxTrEm3Fx)>Lalla

For this one I guess I'm going with an author file.


Add new Flint SQL grammar

Description
Added latest Flint SQL grammar changes as below.
Issues Resolved

ALTER statement: https://github.com/opensearch-project/opensearch-spark/pull/279
BLOOM_FILTER skip type: https://github.com/opensearch-project/opensearch-spark/pull/283

Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Confirmed with @vamsi-amazon that https://github.com/opensearch-project/sql/pull/2554 will cover all latest Flint SQL grammar changes, including:

ALTER statement: https://github.com/opensearch-project/opensearch-spark/pull/279
BLOOM_FILTER skip type: https://github.com/opensearch-project/opensearch-spark/pull/283
ANALYZE statement: https://github.com/opensearch-project/opensearch-spark/pull/284

Closing this PR as not needed any more.


"Open Google Sheet" returns error

I received an email that the Google sheet was created and shared with me, but when I try to open the sheet from the DROID dashboard, it looks the .cogs directory cannot be found.
I checked the server, and .cogs is present in /var/www/droid.ontodev.com/projects/IHCC/workspace/metadata.
My only idea is that because src/workflow.py is in the src/ directory, perhaps it's looking for the .cogs directory there? This may be something we need to fix in cogs.helpers get_sheet_url() and validate_cogs_project() - see https://github.com/ontodev/cogs/issues/85

I'm still able to do other tasks with COGS from the Makefile, such as running the automated mappings.


added flag for PIPES_AS_CONCAT connection setting

Fix for PlanetScale (and other) databases that throw an error when the PIPES_AS_CONCAT connection setting is set.
#2034
Added a flag to MySqlConnectSettings struct that defaults to true, per request.

@jakerieger How come this PR was closed?

Dunno, it wasn't me.

@marcustut Wasn't sure if I needed to open a new one to fix my original commit. Looks like I don't.


Fix craftax imports

I made a breaking change to the Craftax folder structure in v1.2.0, so the imports now require a craftax. prefix.

Thanks so much for fixing this. Its currently failing the linters, would you mind running a pre-commit to fix formatting and push that again. You can do it simply by:
pip install pre-commit
pre-commit run --all
then just commit that and push and I'll merge. I would do it myself but i cant push to your branch.


Can not find source code

Hello,
I'm looking for the source code of https://github.com/MobiFlight/MobiFlight-Connector/blob/main/lib/MobiFlightWwFcu.dll
But can not find it anywhere.
Can you please point me to the source of it?
MobiFlight doesn't support my simulator but I would like to get the FCU working for it too and I need some pointers to figure out how it works

The code is not available in GitHub. You can join the MobiFlight discord and ask for assistance in #development

I don't have discord cause I don't consent to their terms of service and piracy policy Is there a reason the code for the open source project isn't public (aka open)?

That specific DLL is a separate project and not currently open source.


Chatter = Undefined

I have a question about     steamFriend.on('message')
I figured out that Source is an actual SteamID of chatter, but why when we use chatter property of function it always says 'Undefined' in console.log ?

The 'message' event is meant for use cases where you want to respond in the same way to both chat messages and friend messages. In the former case, source is the chat room and chatter is the chatter. In the latter case, defining chatter would be meaningless since there is no chat.

So, is there a way I can get a chatter nickname in console.log too?

Yes, by using the personaStates object.
steamFriends.personaStates[chatter || source].player_name

Thanks a lot, that solved my problem.


Cannot set Pagination Limit in API UI

Version: v2.1.8, v2.2.0, v2.2.2, Master
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a cluster with multiple nodes
Visit /v3/nodes
In the API UI set a Pagination limit less than total of nodes. Click the Set button.

Result:
Nothing happens, the page just refreshes with a setting of undefined.
HTTP doesn't show we submitted (POST'ed or PUT anything to the server.

Manually setting limit via URI works fine. Just the button seems to be broken.
I.e. try /v3/nodes?limit=5 and this will work fine.
Possibly related to issue where Log Out link also does not work?

"Logout" is for basic auth, if you're in from "View in API" or otherwise authed by the cookie then there's no (generic) way for the API UI to do that.

Then we should remove or hide "Logout" ?

It is not possible to know if it will work or not because neither the fact that basic auth was used (or not) or the presence of the cookie (or lack thereof) are not visible to the client.

Ah gotcha; that makes sense


BLD: included pandas.api.* in setup.py

Lots of good refactoring in #13147 , but can't use them if they aren't included!

good point! thanks!


Update to only link on presence of href

** Update options.link to come from href="" in the tag.
** Default do not create a link on all elements.

I have incorporated these changes into another PR. An a tag with no href needs to use the text content of the href for backward compatibility, and the link needs to use the inherited style for the href, rather than just the tag options, so sub tags are also links.