Add support for IE11.

🚀 Feature request
Motivation

https://www.w3counter.com/globalstats.php

Thank you @leerob
If anyone with more experience on this (I stopped making sites for IE a long time ago) is willing to try and fix the bugs (or at least identify them), I can help pointing to files and lines in the source code.

It'd be awesome to use Reakit, but we have to support IE11 due to lots of our users requiring older browser support. Viewing the docs did not work on IE11, either.

For supporting IE11, most flexbox things should work, minus justify-content.

Alright, if the problem is only style, the reakit package should work on IE11 as it doesn't include any (with a few exceptions that shouldn't count). It may be using JavaScript that is not supported though, not sure.
The styles on the website depend on the reakit-system-palette and reakit-system-bootstrap packages. Despite being used by the Reakit website, they are really experimental right now and I don't recommend using them in production.
reakit-system-palette takes care of the default color palettes:
https://github.com/reakit/reakit/blob/master/packages/reakit-system-palette/src/palette.ts
reakit-system-bootstrap uses reakit-system-palette to style Reakit components (there may be issues with IE11 here):
https://github.com/reakit/reakit/tree/master/packages/reakit-system-bootstrap/src
The website merges the systems and override some values in this file:
https://github.com/reakit/reakit/blob/f5585d7ceb9a08b0a71d90f8fdd619d9aa8abc07/packages/website/src/components/Provider.tsx
Website specific styles are spread across components, pages and templates. The code is a huge mess right now (I'm sorry about that, I had to prioritize the main package), but it shouldn't be hard to update the styles.

Hello.
For an anecdote on why I am here, check the following details:

We are using `reakit` v0 at a client's project for quite some time now, which is also required to work on IE11.
I ported the project from v0 to v1 on friday, ultimately removing most of the basis components in favor of default DOM elements (e.g. div instead of Box, etc.). This seems to have worked out alright. When I remembered to check IE11 for compatability it failed to render the app.

The main issue I encountered was that reakit v1 is using Array.prototype.find, which is not supported by IE11: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/find#Browser_compatibility
I am open to get into this issue and add a polyfill, try to circumvent Array.prototype.find, etc. and to create an appropriate PR. Whatever works best for this project. :smile: :+1:

What I find curious, is that babel.config.js contains browsers: "defaults" as config for production builds... and the minified bundle seems to have clauses that guard these array prototype functions (as Yt and Zt), but still they are used directly in code that is at the very beginning of the bundle output.

OK, I tried to explicitly set "ie 11" as the compilation target but it still uses e.find in the compiled bundle... the defaults targets also include ie11, so I really don't understand what is going on... 🤔

@fleischie I think you may be missing the useBuiltIns options for @babel/preset-env: https://babeljs.io/docs/en/next/babel-preset-env.html#usebuiltins. That said, I'm not sure reakit should include polyfills in its bundle, as several packages including their own polyfill each, for several features, can their consumer's bundle explode. Two other solutions to be considered are:

Make it clear to consumers that reakit uses some modern ES features and recommend that they use babel to polyfill it (in that case, only one polyfill would be included per feature, instead of one per feature per package; it also shouldn't be too tricky to setup a cache in webpack for build-time performance)
Just stop using some features (meh)

There's been a blog post from a Babel maintainer arguing for this, I'll like to it if I can find it.

@vhfmag ok granted, I could potentially polyfill .find and .findIndex myself on a project level. But this issue specifically asks for support of IE11, so I assumed it would be desired to do this on a library level.
(Also technically you wouldn't really need to polyfill .find and .findIndex in its entirety, because popper.js uses a pretty "simple" find and findIndex wrapper.)

@fleischie I also understand that the solution being discussed here was to bundle it with polyfills, I just wanted to provide a counterpoint.
Does popperjs provide its own implementation of find and findIndex? If so, that should be same as the second solution I proposed, isn't it?

Another possible solution is to mark corejs as an external dependency in the bundler, so that its import statements are included in the final bundle and the consumers bundler can deduplicate it efficiently, but that would mean reakit would only be usable with a bundler.

Yo, I found another thing in<EMAIL_ADDRESS>: src/Dialog/__utils/usePortalRef.ts has the following line:
  ...
  portalRef.current = dialog.closest(Portal.__selector) as HTMLElement;
  ...

which is not compiled away in any way and which is additionally not available in IE: https://developer.mozilla.org/en-US/docs/Web/API/Element/closest.
As long as nobody says anything I guess I will add these things here and polyfill them in the app level. This is really not the desirable solution to this issue, but it will do for now.

For bundle size alone, I would hesitate in adding library level polyfills for IE11.
As @vhfmag mentioned, I think a better solution would be to make it clear that IE11 is not supported, and suggest that user's include their own polyfills.
Ideally Reakit would provide a list of APIs that may need polyfilling in older browsers so user's can write code to conditionally load these.

There are two main issues with that:

If bundle-size is the main concern, why not directly write this lib in es5 w/o external dependencies,
IE11 might be the only browser that I as a developer care about no matter how "old" it is.

Disregarding that I still would appreciate anything regarsing this topic: a Caveat section in the Readme, a library-included polyfill, a refactored usage of non-IE11 Array functions (with/without polyfills), anything.
I will post my solution for this problem on monday if I don't forget, for anybody having the same issue.

Just to let you guys know that I'm gonna give this issue more attention over the next couple of weeks. Hopefully, we'll have the core library working on IE 11 with automated tests by the end of October.

We're using Reakit pretty extensively (Menu, Popover, Tooltip & Dialog) and I was able to get these components functioning on IE pretty well by adding a few polyfills. Could a simple solution be to add a package (packages/reakit-polyfills) for the one required? That way it would be opt in if you need to support IE (and other browsers)

@andycarrell Yes, that's an option! Can you share the list of polyfills you had to add in order to make it work?

I can give a list of polyfills we're using - it'll be more than is needed for reakit (since we depend on other libraries too)
This is the list we use:
import "core-js/features/array/find";
import "core-js/features/array/find-index";
import "core-js/features/array/fill";
import "core-js/features/array/includes";
import "core-js/features/object/entries";
import "core-js/features/object/values";
import "core-js/features/map";
import "core-js/features/number/is-nan";
import "core-js/features/set";
import "core-js/features/string/includes";
import "core-js/features/string/repeat";
import "core-js/features/string/starts-with";

import "react-app-polyfill/ie11"; // Promise, Object.assign, 'core-js/features/symbol', 'core-js/features/array/from'

// Also
// https://developer.mozilla.org/en-US/docs/Web/API/Element/closest#Polyfill
// https://developer.mozilla.org/en-US/docs/Web/API/ChildNode/remove#Polyfill

Would highly recommend taking each one out and seeing what fails to check if it's necessary

Here are the polyfills we're using in our app that uses Reakit, all the tests pass in IE.
import './promise'
import './array-find'
import 'core-js/features/object/assign'
import 'core-js/features/array/includes'
import 'core-js/features/object/entries'
import 'core-js/features/url'
import 'whatwg-fetch'
import './childnode-remove'

Thank you @andycarrell and @tom-sherman for sharing your solutions. From what I tested, these are the required polyfills for<EMAIL_ADDRESS>to work on IE11:
import "core-js/features/array/find";
import "core-js/features/array/find-index";
import "core-js/features/array/includes";
import "core-js/features/object/entries";
import "core-js/features/object/values";
import "core-js/features/object/get-own-property-descriptors";
import "core-js/features/string/includes";
import "react-app-polyfill/ie11";
// Also
// https://developer.mozilla.org/en-US/docs/Web/API/Element/closest#Polyfill
// https://developer.mozilla.org/en-US/docs/Web/API/ChildNode/remove#Polyfill

Except for the DOM methods closest and remove, @babel/preset-env automatically adds the needed polyfills in production, so I think we should leave this to the user (either by using @babel/preset-env or importing the polyfills manually).


Use vscode panel border color for table header box shadow

.oi-f09d35-table thead th {
    box-shadow: 0 1px 0 #ccc;
}

It needs to be there, just not as prominent.

yeah, I might need to pull observable inputs table source code into my repo to do more work on that table styles without !important overwrites.

I think this should for for now:


Add Teamcity integration

I've implemented a webhook integration with Teamcity. It uses the well-known Teamcity plugin tcWebHooks (https://netwolfuk.wordpress.com/category/teamcity/tcplugins/tcwebhooks/) which sets Teamcity up to send a webhook event on build start/finish.
I still have to write the test suite for it, and will set up a pull request for what I have so far. I'd love any and all feedback.

Fixed in #688.  @dwrpayne FYI if you put Fixes: #688 as a paragraph at the end of the commit message for the commit adding the integration (as opposed to in the GitHub issue text), it'll automatically close the GitHub issue when the commit is merged.


thread 'main' has overflowed its stack

PS> .\target\debug\scanner.exe --dump "C:\Users\Daniel\AppData\Roaming\Factorio\script-output\data-raw-dump.json" --out c:\temp\out.png --factorio "C:\Program Files (x86)\Steam\steamapps\common\Factorio" --blueprint "C:\Users\Daniel\AppData\Roaming\Factorio\script-output\blueprint.txt"
loaded BP

thread 'main' has overflowed its stack

input.zip

hmm so #1 was not actually fixed by #3?

ok I can reproduce it in my windows VM!
interestingly enough it does not happen when compiling in release mode (which I did since the start of the project when running it was pretty slow even in release but its been better after some optimizations so I should switch to debug building again 😄)

#8 should fix this

Fixed


[BUG]: Relation Query type merges when using the same "with" key

What version of drizzle-orm are you using?
0.30.10
What version of drizzle-kit are you using?
0.21.13
Describe the Bug
schema:
author: text('id') // a reference to the author id

relation:
author: one(author, {... // notice the same key as the schema "author"

query:
with: {
   author: true // The "author" should be the data from the author table, and not the "id" reference
}

This results is type: author: (string & {what ever type the relation query is})
Expected behavior
When using with: sameKeyAsSchema, the types shouldn't merge. It should use the types from the with relation.
Environment & setup
No response

Drizzle separate's relations and table columns under with and columns respectively.

I still see the types getting merged in the current versions 🤷

I still see the types getting merged in the current versions 🤷

Thought this was fixed. We'll keep track of this issue then.


Create a Basic Flow with a SOAP Endpoint

Tutorial URL: https://developers.sap.com/tutorials/cp-integration-create-basic-flow.html
Please specify the step you are referring to: Step 8: Trigger the integration flow
When I hit send button in Postman, I get the error "unauthorized_user<error_description>Bad credentials</error_description>".   I'm using my trial tenant and my i-number as the user.  Also I'm not sure how to assign ESBMessaging.send role to the user.
Best Regards,
Masahiro Obata

Tutorial URL: https://developers.sap.com/tutorials/cp-integration-create-basic-flow.html
Please specify the step you are referring to: Step 8: Trigger the integration flow
When I hit send button in Postman, I get the error "unauthorized_user<error_description>Bad credentials</error_description>". I'm using my trial tenant and my i-number as the user. Also I'm not sure how to assign ESBMessaging.send role to the user.
Best Regards,
Masahiro Obata

Agree they need to clarify the user id password. But it should be  similar to what is mentioned in this tutorial.
https://developers.sap.com/tutorials/cp-starter-integration-cpi-onboard-subscribe.html

as suggested by Skantheri, authorization issue at Postman can be fixed by maintaining Service instance and Service key , created in your trial account.
However we get error at step 8 - Could not convert socket to TLS;
@author_of _tutorial - Please advise

not convert socket to TLS;

Same problem here! Still trying to find out what's happening with this TLS error

I had the same problem/error. I found on the internet that the Google certificate has to be uploaded in the key store. But after I have done that I am getting another error:
"javax.mail.AuthenticationFailedException: No authentication mechanisms supported by both server and client"
I have tried 2 way authentication in google with a special password for the CPI trial account, but it didn't change the error message.
I like these tutorials, but I think they should be tested better so users don't come across these errors. Also I see that this issue didn't receive no updatee from SAP since a long time.  Please assist I am sure that Skantheri and I are not the onbly ones with this issue.

Hello @jonkerpeter
Thank you for the feedback. I am currently trying to replicate this error but unable to. Request you to please give us a little more time to figure this out and update the tutorials.
Thanks & Best Regards, Gautham

I have also had problems with this tutorial. I suspect because I only have a trial "P" user account, not like the SAP employee "I" user account illustrated in the tutorial, I don't have the ability to set the ESBMessaging.send role and this is why Postman send doesn't even register on the message monitor. Using Integration client id and secret at least registers on the message monitor, it has the ESBMessaging.send role, but fails when it tries to send to the Receiver.
Please see the attached document that lists my anonymized configuration and the results of a few experiments. Hopefully this help you find a solution to our problem.
Kind regards, Andrew
T01089 - Step 8 - Postman Error.pdf

I found the reasonS for the error:

you need to use teh google app password if you connect to your gmail account and not your own credentials. see:
https://devanswers.co/create-application-specific-password-gmail/
the settings in the mail adapter should be different and use SMTPS and NOT STARTTLS and also plain user instead of encrypted.  Then it works

Thanks for the advice jonkerpeter. I tried all you suggested, but unfortunately with the same results :(
I suspect that the Roles tile in Process Integration Monitor tab seems to be broken on my account, and doesn't have the ESBMessaging.send role has something to do with it. Can you access the Roles tile? If yes, is the ESBMessaging.send role in it?
Thanks, Andrew

@ASRHARDING.  You do not need the role tile and you do not need to add the ESBMessage send role to your user.  You need the Client ID and client secret that you got when generating a service plan as user password in postman.  For the user credentials of the mailserver (gmail) you need to add them in the Manage Security/Security Material tile. In there you use your user for gmail and the app password that you generated at google.

Dear All,
You need to the ESBMessage send role as well. Also, please try to execute this scenario on our new integration suite trial on the CF environment.
Best Regards, Gautham

Hi jonkerpeter
So far I haven't found a way to add the ESBMessage.send role to my user id.
I have setup gmailSender with my Gmail userid and App password, then sent From / To as my Gmail userid.
I have setup service plan with Client ID and Client Secret as described in https://developers.sap.com/tutorials/cp-starter-integration-cpi-onboard-subscribe.html
I have tried the Client ID and Client Secret used for generating the service plan as user id and password in Postman, but was getting an error between End and Receiver.  That was until this morning, bizarrely this morning retrying it again it worked.
They need to update this tutorial to fully explain how to get it to work for a trial user, including:

How to assign ESBMessaging.send to your trial user id
How to setup mailSender for gmail, and other email systems
Prerequisites for the From & To emails in the Processing tab
Update the tutorial for Connection/Processing tabs, screens have changed since this tutorial was written

Thanks for your help jonkerpeter, now I can continue with the rest of the tutorials in the Mission.
Kind regards, Andrew

Hi gauthamkrishna
I have rebuilt my trial environment to use the new "integration suite" and the results are exactly the same. There appears to be no way that you can get the gmail port 587 settings to work, only the gmail port 465 with app password worked.
As a trial user I have found no way to assign my user id with the ESBmessaging.send role, so have had to use the Client ID & Client Secret instead to get the flow to work.
A link to help information on how to setup source email addresses for different email providers would be very helpful here. I tried to do the same with hotmail, but still failed after trying many different ways of contacting the smtp service, and was unable to set an app password for hotmail.
When you try out these tutorials have you used a trial account that is not a full SAP user id?
Kind regards, Andrew

Hi jonkerpeter
Having played around with different emails in the From: field on the Process tab it appears to server no purpose at all. The sender is always the email address you've set up in the user credential you've set up in the Security Material tile.
Kind regards, Andrew

I have figured out a solution to assigning ESBMessing.send role to your user id.
Follow the steps given at the end of this tutorial issue - https://github.com/SAPDocuments/Tutorials/issues/5519.
Kind regards, Andrew

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.

Depends what you mean by being resolved.
The tutorial instructions have not been changed so anyone else who tries to do the tutorial will run into the same difficulties.
At the very least you could incorporate what has been discovered by people attempting this tutorial, and listed in this problem thread, into the tutorial to make it easier for other people attempting this tutorial. For instance Step 4 still illustrates an ixxxxxx user (International SAP Employee user ID) which would have a SAP email address, not gmail, so makes no sense to set as the mailSender. Advice on using other email sources such as Hotmail, Office365, etc., as the mailSender would be even better - or at least a link that gives more information on how to configure different email sources.


async or configure timeout

in code action finder:
local all_results, err = vim.lsp.buf_request_sync(opts.bufnr, "textDocument/codeAction", params, 1000)

can you make the 1000 configurable, or switch to async request? usually for my many slow LSPs the first request will timeout and i get no code actions until LSPs have warmed up

Hello,
It is normally done. I've increase it to be 2000, but it is now configurable with opts.lsp_timeout

It is now async, so opts.lsp_timeout is now unused. Can you tell me if it works for you ? Thanks !

lgtm!


Running mattermost + Jitsi Plugin in a subdir returns 404

When running mattermost in a subdir, the jitsi plugin is not working.
Same as described here: https://github.com/mattermost/mattermost-server/issues/14106 and https://github.com/mattermost/mattermost-plugin-zoom/issues/96

This is solved in the new plugin version that is going to be released soon.

is this solved?  I have the same issue and its been a while...


Is there a way to get the executed SQL statement directly?

Your Question
For example:
models.db.save (& user)      I want to get the executed SQL statement. Is there any way to get it?

The document you expected this should be explained

Expected answer

Hi, @zhangxuanru, is models.db.Debug().Save(&user) that you expect for? You can setup logger and do whatever you want with the executed SQL statements.

Is there a function or method that can get SQL directly?

Hi, @zhangxuanru, is models.db.Debug().Save(&user) that you expect for? You can setup logger and do whatever you want with the executed SQL statements.

Is there a function or method that can get SQL directly?

@zhangxuanru there is no method to get SQL directly, because that's impossible and that's why: GORM SQL queries building is based on fetched data, so it can execute by one request several SQL queries. Use custom logging mechanism and get them all.

you can use the following code to get SQL statement , It is usually used in the gorm's plugin @zhangxuanru
sql := db.Dialector.Explain(db.Statement.SQL.String(), db.Statement.Vars...)

you can use the following code to get SQL statement , It is usually used in the gorm's plugin @zhangxuanru
sql := db.Dialector.Explain(db.Statement.SQL.String(), db.Statement.Vars...)

thanks !


Bump RL9 host image to RL9.3

I've updated as CI job wasn't running (hoping this means we pick up the recent changes to CI)

Rocky 9 jobs failed because the image wasn't uploaded to Leafcloud. I've run the new workflow to do this.
Upgrade jobs failed because the ci-aio env in yoga was updated to disable heat, but it is still enabled in zed, so DB migrations fail. I'll merge through the relevant changes to zed & antelope.

I've changed the target branch, hopefully it will pass now. Please wait for #950 to merge before merging this though.


migrating from gh-badges to 1.3.0 to 2.0.0

gh-badges v2.0.0 declares a new public interface which is synchronous. If your version 1.3.0 looked like this:
const badge = require('gh-badges')

const format = {
  text: ['build', 'passed'],
  colorscheme: 'green',
  template: 'flat',
}

badge.loadFont('/path/to/Verdana.ttf', err => {
  badge(format, (svg, err) => {
    // svg is a string containing your badge
  })})

To upgrade to version 2.0.0, refactor you code to:
const { BadgeFactory } = require('gh-badges')

const bf = new BadgeFactory({ fontPath: '/path/to/Verdana.ttf' })

const format = {
  text: ['build', 'passed'],
  colorscheme: 'green',
  template: 'flat',
}

const svg = bf.create(format)

I suspect some people who haven't thought about this package for some time may appear seeking help upgrading. Lets leave this open here for a bit ^^

@chris48s or even better: put it in the README please :)

He's added it to the changelog in this PR: https://github.com/badges/shields/pull/2300/files#diff-15aafd020967f222d8ddfcee3457317f.

Ok so this changelog is very invisible to the regular github user. I would expect changes either to be listed in the releases or in a changelog file which I would expect in the project root.
Not judging this projects structure, just stating what I would expect :)

Appreciate your perspective. It's a tricky balance to provide what's helpful without unduly confusing people.
For what it's worth, the main thing going on in this repo is the badge service, and most people who come here don't know or care that we publish an npm package. I feel including that entire code block is too much detail, though having some kind of link to upgrade instructions or a changelog seems worthwhile.
Do you want to take a look at the root readme in that PR and comment with some suggested edits?

Maybe a dumb question, but before my code was like this:
const badge = require("gh-badges"),
badge(
        {
          text: ["storybook", "up to date"],
          colorscheme: "orange",
          template: "flat"
        },
        function(svg, err) {
          fs.writeFileSync(folder + outputFile, svg);
        }
      );

I don't use a fontPath but I get this error now:
                ^

TypeError: Cannot destructure property `fontPath` of 'undefined' or 'null'.```

I don't see anything about `BadgeFactory` documented anywhere - am I looking in the wrong place?

@paulmelnikow I'm sorry, I didn't realize, that this is a ongoing PR. There is already a link in the root README to the changelog file. From my point of view this should be sufficient!
And yes, as you said, most people just use the service. In my case, we use the npm package in order to run our custom badge service which uses our custom tokens to display badges from private services. Our CI failed with gh-badges v2 and I had a hard time tracking down the changelog. Looking at the github issues tab was my last resort :)

Sorry you had a hard time finding the information; glad you found it!
It's cool to hear from people who use the package! I'd be curious to have your input about improvements going forward. One question, out of curiosity: do you use the raster badges (.gif, .png) or only SVG?

We use SVG only.
I'm also not sure if we will update to v2... v1 is running flawless and we will probably not touch the system until we need to implement new private services to generate badges from.

now #2300 is merged and we've got this linked somewhere a bit more obvious I'm going to close this


[RFC] Add VerifyObjectStoreStep

Add a new maintenance step: VerifyObjectStoreStep that runs the git commit-graph verify and git multi-pack-index verify commands. If these fail, then delete the corrupt file. In the case of a multi-pack-index, we can regenerate the file. The commit-graph will regenerate after the next non-trivial prefetch.
We've had issues with users data in the past, and this gives us a way to automatically detect and repair these scenarios.
This PR is labeled as [RFC] so I can get opinions on whether this is a good idea or not.

@jrbriggs pointed out that this would be better to do after every write to these files. Limits the window where there could be problems.

@jrbriggs pointed out that this would be better to do after every write to these files. Limits the window where there could be problems.

I like this suggestion. It also keeps our maintenance tasks more deterministic, in that it will run in response to generating these files, instead of at a different set of (seemingly random) times.
Do we have any ideas on what is causing the corruption? For instance, are we writing out corrupt files or, or is something else corrupting them after we generate them? If we are generating corrupt files, then this approach should let us identify it right away. If something else is corrupting them, then we might not pick it up as quickly...

Do we have any ideas on what is causing the corruption? For instance, are we writing out corrupt files or, or is something else corrupting them after we generate them? If we are generating corrupt files, then this approach should let us identify it right away. If something else is corrupting them, then we might not pick it up as quickly...

In the cases where I can get in contact with the user, the only ways the file could have been corrupted were on-disk bit flips or in-memory bit flips. We literally were validating the data right before sending it (via a buffer) to disk. Those users that ran memcheck found issues with their RAM.
The perf machine recently had an issue that was caught by the git multi-pack-index repack command, but the problem may have existed much earlier. I'm not sure what caused it, but we could have noticed right away had we verified right afterward.

If corruption occurs strictly after a write (e.g., midx verify would have passed immediately after the write, but would have failed a day later), I don't think it's within the scope of this project to fix. If we can detect corrupt data was written (e.g., a bit flip in memory was persisted to disk), we should mitigate.

@derrickstolee Is it safe to assume the verify / write should be quick tasks?

@derrickstolee Is it safe to assume the verify / write should be quick tasks?

They take about as long as it would take to write them from scratch. I've measured 11-16 seconds.


Mapbox dissapear, when call routerExtensions.back()

I use mapbox in my application. When I navigate on the page, where I use map, all works perfect. After that I tap on one of the markers and I navigate on the next page. But when I click backButton, or call routerExtensions.back() on the next page, I return on the page with map, but map dissapears. I can tap blindly on my map markers and I will navigate on the next page, but I don't see map.
Here is the code of class with map:
export class CarwashListComponent implements OnInit {

ngOnInit() {
    this.initMap();
}

initMap(){
    var _this = this;
    this.mapbox.show({
            accessToken: "pk.eyJ1IjoiaWxqYWdyYWJhcjE0IiwiYSI6ImNpd25laGw2YTAwMTIyeW10ZXM0a3l6M2UifQ.CfGJKVjVzM-lRzko7cP37g",
            mapStyle: "light",
            center: { // optional without a default
                lat: this.cities[0]['coordinates'][1],
                lng: this.cities[0]['coordinates'][0]
              },
                markers: [
                {
                 lat: 52.3732160,
                 lng: 4.8941680,
                 title: 'Nice location',
                 subtitle: 'Really really nice location',
                 onCalloutTap: function () {
                             _this.routerExtensions.navigate(["next_page"]))
        }
            ],
            zoomLevel:9.5,
            showUserLocation: "true"
    })

}
}

What am I doing wrong?

Not sure, but you should declare your map in XML to make it easy to navigate back and forth and avoid having to manually show and hide the map.

hi @iljagrabar14 I have the same issue, but I need to declare my map programatically because of some other functionalities. Did you manage to solve this issue?


error  - Copy-DbaSqlServerAgent : Unable to find type [DbaInstanceParameter]

i'm getting this error when i run the copy-dbasqlserveragent -source server1 -destination server2
Copy-DbaSqlServerAgent : Unable to find type [DbaInstanceParameter]. Make sure that the assembly that contains this
type is loaded.
At line:1 char:1

Copy-DbaSqlServerAgent -Source callisto.enterprise.nacorporation.com -Destinatio ...

  + CategoryInfo          : InvalidOperation: (DbaInstanceParameter:TypeName) [], RuntimeException
  + FullyQualifiedErrorId : TypeNotFound

Closing this issue, if you are still receiving this error under the latest release please reopen.


help request: multiline settings don't work?

Description
The requirement is to collect multiline log information. like this:

I tried the tail input plugin setting the multiline true or the multiline filter setting the parser.
But the problem is  these settings don't seem to work.
maybe something's wrong,but I have no idea, anybody can give some effective advice. thx!!!
I've already seen at https://docs.fluentbit.io/manual/pipeline/inputs/tail#multiline-and-containers-v1.8
But! you kown!
then this is my yaml:

The results fell short of expectations:

How did you install fluent operator?
helm upgrade --install fluent-operator --create-namespace -n fluent fluent-operator.tgz
Additional context
version:
Kubernetes v1.21.5
Docker 20.10.9
Linux CentOS Linux release 7.9.2009 (Core)
Fluent Bit v1.8.11

we support multi-line as I can remember? @wenchajun

Yes, you can also take a look at this plugin. https://github.com/fluent/fluent-operator/blob/master/apis/fluentbit/v1alpha2/plugins/filter/multiline_types.go
You can take a look at the secret and see if the configuration inside is as expected all the time. But I think you can look more at regular expressions for validation. https://mp.weixin.qq.com/s/PI3E5-S0Qhbmn0OgEvYy-Q

@wenchajun first,I tried using the multiline filter and the built-in Java parser worked,The results fell short of expectations:

This should be one record, but it actually returns multiple records.
then I want to customize the MULTILINE_PARSER: https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/multiline-parsing
but I can't find the relevant configuration in fluent-operator.
I've tried many times with the tail input plugin regular expression, but the results are not good.
Every time I used this site to confirm: https://rubular.com/

So, what should I do?

@wenchajun How can I customize the MULTILINE_PARSER in fluent-operator.

Here is an example
https://github.com/fluent/fluent-operator/pull/176

@wenchajun thank you. I saw it: https://github.com/fluent/fluent-operator/pull/176
but it used a built-in plugin,not customize. I kown built-in plugin parsers support: go, java and more.
I means [PARSER] and [MULTILINE_PARSER] is different.
so, fluent-operator not support customize the MULTILINE_PARSER, right?

@wenchajun thank you. I saw it: #176 but it used a built-in plugin,not customize. I kown built-in plugin parsers support: go, java and more. I means [PARSER] and [MULTILINE_PARSER] is different. so, fluent-operator not support customize the MULTILINE_PARSER, right?

Yes, the consideration will be integrated accordingly at a later date.

Is there any updates to the multiline parser support?


Support for Eastron SDM630

Hello,
is it possible to integrate the Eastron SDM630 V2 as the most supported device?
I have a Waveshare RS485 TO POE ETH connected to an "Eastron SDM630 V2".
When I use the INtegration and select the "Eastron SDM230" as a device, the data of a phase is also displayed. Are there any plans or extensions to support the "Eastron SDM630 V2"?

I am happy to take a look at this for you. I do not have this device. Would you be have to test a configuration file for me?

Hello
i can test this device to, i also use a Waveshare Modbus Gateway.

This should be resolved in release v1.4.0


potential pio DSL?

### algae.pio

def init(LED):
    LED.set_intensity("A", 20)

def loop(counter, LED, OD):
    new_itensity = 20 * (OD.get_normalized_od()-1) + 0.2

    if new_intensity > 100:
        LED.set_intensity("A", 100)
        LED.set_intensity("B", new_intensity - 100)

    else:
        LED.set_intensity("B", new_intensity)

### chemostat.pio

def init(LED):
    pass

def loop(counter, Pumps):

    if counter % 1200 == 0 and counter > 0:
        Pumps.cycle_media(mL=1.5)

Closing this - I think importing the classes like in https://github.com/Pioreactor/pioreactor/blob/00e91e2784187fec11cb4cab336cd20b06f4f5cd/experiments/example_of_custom_dosing_automation.py is fine and still pretty friendly. Also means there is a single API vs multiple.


Fix duplicate dependencies in package.json

Hello there!
I've found a bug with duplicating plugins in package.json. Imagine situation:
"dependencies": {
  "my-cool-optimizer": "^0.0.1"
},
"devDependencies": {
  "my-cool-optimizer": "^2.0.0"
}

In this case, optimizer from my-cool-optimizer plugin would work two times. I think it is wrong, isn't it? And it can break (and, actually, it break my build process) somebody build process if it is doing something with output (e.g. wrapping it).
What do you think about it? Is it needed or I'm too captious?
And, I think we need to have some FAQ for developers - even starting from 'how to roll out dev env for contributing brunch' - because that loadBrunch && loadGlobalBrunch, which appeared recently, made my day for a while when I tried to debug brunch :)

Yup, although you are the first to report a use case like this, I think for cases like this, we can print a warning and init the plugin only once.
Regarding a contributing document — yeah, I think that makes sense as well. I'll add that one to our backlog.

I added it to my devDependencies and on next day runned npm i --save it again - so it appeared in both places :)
Should I add a warn at line 105 in my PR? In that map function body?

Yeah, a warning would be 👍
Something along the lines of "You have my-cool-optimizer declared in both dependencies and devDependencies"


Add color to active player

Highlight the score box and possibly the mark column of the active player with a different color

changed active player score box to gold in cricket and 01


how is the difference between the website demo and the amg.py in project?

the segmentation results between the the website demo and the amg.py in project are different, why?

I had the same problem. I think I solved it by increasing the number of  points_per_side option. In my example code this was 32. When using the demo it shows the points and it was defenitly much more than 32 along each axis.
I plotted the points onto the image just to make sure all objects are hit.

@cmayer thanks for your advise, I'll have a try.

I used 80 or 100. It is a while ago that I did this. If you upload an image on the web demo, the number of points was about 80 as far as I remember, which seemed to be a good compromise. 32 is pretty small. One point should hit at least every feature you want to find. I used opencv to draw a the grid that I specified and made sure all features were hit by at least one point.


Could not create data channel, is usrsctp available?

Attempting to run gstWebRTC sendrecv on Ubuntu 18.10.   The system worked well until we modified the pipeline (could see the ball and hear the noise).
 " RTP_CAPS_VP8 "96 ! sendrecv. ",
&error);
When we tried to connect to another computer using the following commands we received the following response/errors:
ubuntu@bionic-xfce:~/gstwebrtc-demos/sendrecv/gst$ ./webrtc-sendrecv --peer-id=2750
Connecting to server...
> GET  HTTP/1.1
> Soup-Debug-Timestamp:<PHONE_NUMBER>
> Soup-Debug: SoupSession 1 (0x231f098), SoupMessage 1 (0x21b1170), SoupSocket 1 (0x25c8498)
> Host: webrtc.nirbheek.in:8443
> Upgrade: websocket
> Connection: Upgrade
> Sec-WebSocket-Key: WS84Vt3H03mQm8guZLFSlQ==
> Sec-WebSocket-Version: 13
> Accept-Encoding: gzip, deflate

< HTTP/1.1 101 Switching Protocols
< Soup-Debug-Timestamp:<PHONE_NUMBER>
< Soup-Debug: SoupMessage 1 (0x21b1170)
< Server: Python/3.5 websockets/3.3
< Upgrade: WebSocket
< Connection: Upgrade
< Sec-WebSocket-Accept: YY4BsKaet7VNG5aWPGrlxv6D0Ks=

Connected to signalling server
Registering id 6541 with server
Registered with server
Setting up signalling server call with 2750

(webrtc-sendrecv:1637): GLib-GObject-WARNING **: 12:10:03.199: ../../../../gobject/gsignal.c:3492: signal name 'create-data-channel' is invalid for instance '0x25d8148' of type 'GstWebRTCBin'
Could not create data channel, is usrsctp available?

(webrtc-sendrecv:1637): GLib-GObject-WARNING **: 12:10:03.200: ../../../../gobject/gsignal.c:2523: signal 'on-data-channel' is invalid for instance '0x25d8148' of type 'GstWebRTCBin'
Starting pipeline
ERROR: failed to start pipeline

(webrtc-sendrecv:1637): GLib-CRITICAL **: 12:10:03.208: g_main_loop_unref: assertion 'loop != NULL' failed
ubuntu@bionic-xfce:~/gstwebrtc-demos/sendrecv/gst$
Our pipeline settings are as follows:
pipe1 =
gst_parse_launch ("webrtcbin bundle-policy=max-bundle name=sendrecv " STUN_SERVER
"v4l2src ! video/x-raw,format=YUY2,width=320,height=240 ! videoconvert ! queue ! vp8enc deadline=1 ! rtpvp8pay ! "
"queue ! " RTP_CAPS_VP8 "96 ! sendrecv. ",
&error);

WebRTC's data channel is for data transmission and is not a media channel (for audio/video).
Your error is not related to data channel. It seems to be in the pipeline.
Anyway, you need gst 1.15 version to use data channels.

You need GStreamer >= 1.16 to be able to use data channels and the examples in the default code.
We cannot provide support for every modification you make to these programs.  Sorry.


open index.html fail

when I just open index.html,the error is:
Image from origin 'file://' has been blocked from loading by Cross-Origin Resource Sharing policy: Received an invalid response. Origin 'null' is therefore not allowed access.
when I run it with a server ,it's ok. I want to know why?

Does this answer your question? https://github.com/sirxemic/jquery.ripples/issues/1#issuecomment-38381566

get it. thx!


Fixed in Bug in Issue #168

Fixed Bug in Issue#168. Please merge this PR.

kindly solve the merge conflict then I will merge it.
try to shoe me exact output

kindly solve the merge conflict then I will merge it.
try to shoe me exact output

after this PR whole website going to be mashed-up...
kindly check it and try to make changes only in your file.
kindly fix it


ImportError: cannot import name Activity

I am late to the party, but I am hoping there is still some support around.  I'm on Ubuntu 17.04 running python 2.7.13 and am receiving the following error when I try to run fittotcx:
File "/usr/local/bin/fittotcx", line 11, in
load_entry_point('fit-to-tcx==0.1', 'console_scripts', 'fittotcx')()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 561, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2631, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2291, in load
return self.resolve()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2297, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "build/bdist.linux-x86_64/egg/fittotcx/program.py", line 34, in
ImportError: cannot import name Activity

Hi. I think python-fitparse was recently updated to a 2.0 version. FIT-to-TCX relies on the 1.0 version. Try installing it from the v1-archive branch at https://github.com/dtcooper/python-fitparse/releases/tag/v1-archive instead and see if that will work.

Thanks, that solved the problem!
Sadly, it did not solve my initial problem.  I think Wahoo has recently changed something about they way they export .fit files because nothing processes them any longer.  The output fails with "Unexpected exception while parsing (KeyError: 1)" and I think that has nothing to do with your code.  Greatly appreciate the help!

Nice to hear that it solved at least the initial problem. You could try to see if the 2.0 version of fitparse works better for you. There is an FIT to CVS converter there that you could try, and if that works it should be easy enough to update FIT-to-TCX to use the newer version (I should do that anyway). If not it might be a problem with Wahoo. I could take a look at one of the FIT files as well if you'd like (when I got time) to see if I can spot something weird in them.

Thanks.  I think it was a change to the way the fit file is being written
as it seems to have happened after a firmware update the Bolt Element.
I've attached a sample of the fit file.
On Tue, Aug 15, 2017 at 5:18 PM, Gustav Tiger<EMAIL_ADDRESS>wrote:

Nice to hear that it solved at least the initial problem. You could try to
see if the 2.0 version of fitparse works better for you. There is an FIT to
CVS converter there that you could try, and if that works it should be easy
enough to update FIT-to-TCX to use the newer version (I should do that
anyway). If not it might be a problem with Wahoo. I could take a look at
one of the FIT files as well if you'd like (when I got time) to see if I
can spot something weird in them.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Tigge/FIT-to-TCX/issues/8#issuecomment-322592299, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AdljDVC1oUpGmYujACqEoCSdYH09TVZYks5sYgsLgaJpZM4O3Gzu
.

looks like I did not attach the file.  Trying again.
Sample Files from Wahoo.zip

It seems to parse almost fine with the new fitparse version. I've created an issue in the that project -
see https://github.com/dtcooper/python-fitparse/issues/35 for more information. Once that is fixed I can release a new version of FIT-to-TCX which should work with the Wahoo files.

@r-shawgo this should be solved now and FIT-to-TCX should work on the Wahoo files from now on. Thanks.


Changes to support multiple instances of Datatable component per html…

Hello Vincjo,
I am new to Github as well as the entire node.js ecosystem. My only exposure to node.js started recently when I tried to build a website using Svelte, that's when I found your table component. It seemed the table component cannot support multiple instances on a single page. I tried some changes using set/get Context and it seemed to work well in my local development.
Note that the changes I made were strictly constrained to the files in the /src directory, which means they are no longer compatible with the files in the /example directory.
rgds
Pang

Hello Pang,
Just saw your pull request, it seems you did a huge work.
Multiple instances is a key feature
I pulled your work locally on a separated branch and i'm trying to mount the Datatable.
Can you give me a sample of code example to instantiate the Datatable ?
Tbh i'm quite lost since the "rows" store is not exported anymore
Otherwise nvm I'll take a closer look this weekend ;)
Thx for your help.
Regards,
vincjo

Hello Vincjo,
app.zip
Attached is the zip of app.svelte where I showed instantiation of 3 instances of Datatable (does the attached zip link work ?).
Yes, the rows store is no longer exported, because it's hard to manage and use exported store when we need a way to derive multiple instances of an entity using a common exported store. Hence, I made the rows entity a bindable component property that is exported from Datatable.
The key changes in my attempt to making Datatable supporting multiple instances is using svelte setContext and getContext module. Instead of exporting all the stores, for every instantiation of Datatable I invoked instantiation of new stores and group them into an object using setContext. Hence, all these stores are only accessible from the Datatable instance that initializes the context object. If any child components need to get an access to the stores, they use getContext to retrieve the stores.
I must apologize the pull request shows way more changes that are required to support multiple instances of Datatable than it actually needs, it really  looks unprofessional. I was new to npm, svelte, node js, git, github (am still not good at them), so when the code editor I used was formatting the code unnecessarily, I didn't know how to undo the format changes, so I decided to just commit the changes while keeping the functionality.
Other than setContext and getContext related changes, I also changed data.sortAsc and data.sortDesc to include support for sorting columns with boolean values. Another change I made was in datatable.init(), before the changes, the table columns wouldn't resize by themselves when the table rows were updated. I think I also touched up here and there a bit to make sure functions that need to be aware of table instances work on the correct table by using the exported table name.
Please let me know if there's anything else I could help. Feel free to change the code the way you see appropriate.
If it helps, in my opinion, the core of the changes I made is in Datatable.svelte, in lines below:
//Initialize context for all stores.
setContext(key, {})
initContext()

const { rows } = getContext(key)
export const dataRows = rows

const datatable = getDataTable(name)
const { options } = getContext(key)

You'll see that in initContext(), the pattern repeats itself for each store that used to be exported, but are not instantiated for each instance of Datatable.svelte, and grouped in a context object.
rgds
Pang

Hello Pang,
Thank you very much for all these precisions.
I was able to understand your work easily and I took the opportunity to update the documentation.
You made the right choices, I don't know of a better way to instantiate the component yet. Despite everything, it remains very simple, which is the goal.
Overall, this was exactly what the component needed to evolve. And using the Svelte context API was the best solution.
So a big thank you
I kept everything you added, including sorting columns with boolean values :thumbsup:
At the same time, I introduced a small breaking change: the rowPerPage option becomes rowsPerPage
Maybe some bugs will appear, with all these possible use cases, so I'll try to keep an eye on github to fix it faster.
 I love the functionality the "simple-table" provided, as well as its ease of use. Your clear and concise documentation was also what attracted me to it, and the code was beautifully written.
rgds
Pang

Hello Vincjo,
Regarding the removal of Datatable property "name", and the usage of table id store "id", I would like to share some input with you with regards to my use case. In my current use case, a user can click on another table, or you can imagine it as a menu, and the frontend javascript would insert a text string based on where the user clicks into the filter input box in the Datatable stickyheader, programmatically filtering the Datatable columns. If there are multiple instances of Datatable, then it seems some sort of table identification is needed so that top level user application code could target the table it needs to interact with. Removal of Datatable prop "name" seems making table identification a little more challenging. One might still be able to create the unique reference by creating a container for each Datatable and give the container a unique ID, but this reference is not used anywhere in Datatable module/package.
I am not sure if this is a valid use case, or if I overlook better ways of uniquely identifying the Datatable instances other than using the old/previous "name" property field.
rgds
Pang

Hello Pang,
The id store could be set by the user, passing by a component property.
The id would have a default value (a random string like now) if it's not set in the component.
There are surely some difficulties with the context, but it worth a try
regards
vincjo

Hello Vincjo,
I could only see 4 export properties from Datatable.svelte, i.e data, setting, classList and dataRows, did you mean user could access theidstore through getContext and setContext ?
rgds
Pang

Sorry, I meant it could be added easily
It's not possible for now
the easiest way would be to add a key to the settings object
const settings = {
    rowsPerPage: 50,
    id: 'my-first-table',
    ....
}

And then pass the settings.id value to the id store
Something like that :
stores/state.js
function getId(){
    const getStore = () => {
         const {options} = getContext(key)
         const id = options.get().id ?? 'ssd-' + (Math.random() + 1).toString(36).substring(5)
	const {subscribe } = readable(id)
	return {
        ....

Unfortuanately I won't be able to work on it this week :/

Hello Vincjo,
That's an excellent idea. I tried the changes you suggested, I need to make some modifications for it to work. Here are my observations:
In Datatable.svelte:
	setContext(key, {})
	initContext()

	const { rows } = getContext(key)
	export const dataRows = rows

	const datatable = getDataTable()
	const { id, options } = getContext(key)

	$: {
		datatable.setRows(data)
		options.update(settings)
	}

The table id store is created/initialized before options store is updated with the table settings passed in from user application, hence const id = options.get().id ?? 'ssd-' + (Math.random() + 1).toString(36).substring(5) returns id string from the Math function and this value is populated in the id store.
What I tried-
In options.js update method, added "id" field in the parsed object.
const parsed = {
                    sortable:     typeof opt.sortable       === 'boolean' ? opt.sortable      : true,
                    pagination:   typeof opt.pagination     === 'boolean' ? opt.pagination    : true,
                    rowsPerPage:  typeof opt.rowsPerPage    === 'number'  ? opt.rowsPerPage   : 50,
                    columnFilter: typeof opt.columnFilter   === 'boolean' ? opt.columnFilter  : false,
                    scrollY:      typeof opt.scrollY        === 'boolean' ? opt.scrollY       : true,
                    css:          typeof opt.css            === 'boolean' ? opt.css           : true,
                    id:           typeof opt.id             === 'string'  ? opt.id            : null,
                    labels: labels,
                    blocks: blocks
                }

In state.js, I changed the getId() function as below. Note that I needed to change the id store from readable store to writable store, so that the store value could be updated in Datatable.svelte.
function getId(){
	const getStore = () => {
		const {options} = getContext(key)
		const idVal = options.get().id ?? 'ssd-' + (Math.random() + 1).toString(36).substring(5)
		const {subscribe, update} = writable(idVal)
		//const {subscribe } = readable('ssd-' + (Math.random() + 1).toString(36).substring(5))
		return {
			subscribe,
			update,
			get: () => {
				let $store
                                id.subscribe(store => $store = store)
                                return $store
			}
		}
	}
	const id = getStore()
	return {id}
}

In Datatable.svelte, the changes I made were:
$: {
   datatable.setRows(data)
   options.update(settings)
   if (settings.id) {
      id.update(id => options.get().id ?? id)
   }
}

I am not sure if these changes meet your expectation as you made a conscious decision to use a readable store for table id.
rgds
Pang


Auto build the release tool with the dry-run option in post build stage

The current release publish workflow is

dry run - manually set the parameter of job https://ci.adoptium.net/job/build-scripts/job/release/job/refactor_openjdk_release_tool/
rerun the dry run job with dry run parameter unchecked.

The mistakes might happen when manually setting the parameters besides sometime it's hard to find the dry run build if the job is triggered by nightly build automatically at the same time.
If the dry run can be triggered automatically by the pipeline build the process  would be easier and more reliable  for  for release champions.
Part or related with #739

We can do it at two different stages.

After each jdk build per platform:  either in jdk build . Or in pipeline . This way we don't need to wait all platform builds are done.

After all jdk builds are done, similar to nightly build . Have to wait until all platforms are done.

Either way we need to do per platform so each platform has its own release build job which can be rerun to publish. The build information with url link can be added as pipeline job description e.g https://ci.adoptium.net/job/build-scripts/job/release-openjdk11-pipeline/40/

@smlambert thoughts?

The release job ( not necessarily related with this issue) https://ci.adoptium.net/job/refactor_openjdk_release_tool_new/

@sophia-guo I think I like the idea of running a dry run of the release after each platform is built for the nightly build, but I wonder if its possible to have the behaviour different for nightly / release pipelines, and have the dry-run for a release pipeline wait until all jdk builds are done?.

Adjusted the title since I misinterpreted as a proposal to run another complete dry-run pipeline like we do before release after every build :-)

I'm 👍🏻 on this, however some other things to consider:

The value of this is in having something a job can quickly re-run without the dry-run option. We need to make sure that we can easily find the correct build of the release_tool to be able to publish it. Hopefully we can do that in a way that isn't slower than just re-running it.
We also need to ensure we are retaining the builds of the release_tool for long enough so they aren't deleted when you want to re-run them. So we'll need ensure they are retained for an absolute minimum of two weeks based on recent release cycles.

The value of this is in having something a job can quickly re-run without the dry-run option. We need to make sure that we can easily find the correct build of the release_tool to be able to publish it. Hopefully we can do that in a way that isn't slower than just re-running it.

I'm thinking attaching all rerun build links to the bottom of the release pipeline job description. When I do the publish I always  check the release pipeline job itself. So I think it should be good to attach the rerun link to the release pipeline job itself. If dry run fails the link would be dry run link. If dry run succeeds the link is the publish link.

We also need to ensure we are retaining the builds of the release_tool for long enough so they aren't deleted when you want to re-run them. So we'll need ensure they are retained for an absolute minimum of two weeks based on recent release cycles.

It's common that the rerun link will be mixed or deleted if nightly also triggers the job. Max # of builds to keep need to be increased. Also might help if nightly and release publish can be separted.

@sophia-guo I think I like the idea of running a dry run of the release after each platform is built for the nightly build, but I wonder if its possible to have the behaviour different for nightly / release pipelines, and have the dry-run for a release pipeline wait until all jdk builds are done?.

I'm not sure if I understand correctly. Currently for nightly build pipelines the binaries are published until all jdk builds are done and no publish process for release build pipeline. Also for nightly there are no dry runs.
Are you suggesting

nightly pipeline :  add dry run process and instead of publishing after all jdks build publishing per platform right after jdk build is done.

release pipeline: have the dry-run for a release pipeline until all jdk builds are done.

We can definitely have the behaviour different for nightly / release pipelines. Just want to compare the Pros and Cons.

We also need to ensure we are retaining the builds xso they aren't deleted when you want to re-run them. So we'll need ensure they are retained for an absolute minimum of two weeks based on recent release cycles.

Actually if we don't care about of the dry run build we might not need to keep that build.
We can provide the dry run build in two ways. One is the link of dry run build itself, which asks to retain the builds of the release_tool for long enough so they aren't deleted when you want to re-run them. The dryrun link would be 'https://ci.adoptium.net/job/build-scripts/job/release/job/refactor_openjdk_release_tool/dryrunbuildNumber/'
The other way is just to provide the rerun link of the dry run (same parameters of the dry run) something like 'https://ci.adoptium.net/job/build-scripts/job/release/job/refactor_openjdk_release_tool/parambuild/?TAG='specificTag'&&VERSION='specificVersion'&RELEASE=true&UPSTREAM_JOB_NAME='upsteamjobname'&UPSTREAM_JOB_NUMBER='jobnumber'&ARTIFACTS_TO_COPY='specifiedFilter'&ARTIFACTS_TO_SKIP="**/testimage'"&DRYRUN=false'.  This way no dry run build itself is required to keep.

option 1 means you have each platform as an individual dry-run job which is consistent with what we need during a release cycle since we don't publish all together. There are two sub-options within this though
1a) Start the dry run within the individual platform pipelines, but that would require it to pull from the platform pipelines, which is now where we usually publish from
1b) Start the dry run from the openjdkXX-pipeline after the platform pipeline is complete (maybe just after the artifacts are archived from the subjob).
1b is probably better as it can point to the release-openjdkXX-pipeline for the artifacts, and also keeps all of the references to the dry-run jobs in one place making them easier to find.

I'm thinking attaching all rerun build links to the bottom of the release pipeline job description.

Yes I agree - that would be really useful I think.

@sxa https://github.com/adoptium/ci-jenkins-pipelines/compare/master...sophia-guo:release1?expand=1 is option1 with sub option 1b.


Are there any version that support for iOS 12.0?

@minhDTNHust no there isn't unfortunately.
Technically there's nothing stopping it, just need to write some shims for some missing CGColor initializers if you're prepared to fork the codebase.

Thanks you for your support very much. I've done this!

Hey mate - v18.0.0 now supports iOS 11 as a minimum target.

Yes I love it. Thanks you!


Add optimistic cache updates to saving blocks

In elemental ^4.
Now there's a button to save in-line edited blocks individually with #296. This is awesome but it still reloads the list of blocks on save. Preferably we can update Apollo with optimistic cache updates and avoid the reload.

My initial attempt with narrative: https://github.com/dnadesign/silverstripe-elemental/pull/392#issuecomment-422897050


mac issues

Hi, I stumbled across a few issues while evaluating mlab for our project. For two of them I found the cause, on the third I gave up and moved on ;-). Anyway here's what I found, hope it helps. And sorry for reporting everything in one issue, but unfortunately I can't spend to much time on this.

The mac system is not detected correctly in mlabraw.py since sys.platform returns "darwin" on the mac which obviously contains the string "win".
The module always launches two instances of Matlab. I think it's because releases.py instantiates MLabWrap twice in get_mlab_instance.
Every call to Matlab seems to hang while reading back the results. Here's the stack trace:

Error
Traceback (most recent call last):
  File "/.../mycode.py", line 61, in test_mlab
    mytest()
  File "/.../mycode.py", line 47, in run
    a = matlab.svd(np.array([[1, 2], [1, 3]]))
  File "/usr/local/lib/python2.7/site-packages/mlab/mlabwrap.py", line 607, in mlab_command
    return self._do(name, *args, **update({'nout':nout}, kwargs))
  File "/usr/local/lib/python2.7/site-packages/mlab/mlabwrap.py", line 547, in _do
    res = self._get_values(resSL)
  File "/usr/local/lib/python2.7/site-packages/mlab/mlabwrap.py", line 483, in _get_values
    res.append(self._get(varname))
  File "/usr/local/lib/python2.7/site-packages/mlab/mlabwrap.py", line 568, in _get
    vartype = self._var_type(varname)
  File "/usr/local/lib/python2.7/site-packages/mlab/mlabwrap.py", line 436, in _var_type
    res_type = mlabraw.get(self._session, "TMP_CLS__")
  File "/usr/local/lib/python2.7/site-packages/mlab/mlabraw.py", line 72, in get
    return matlab.get(var_name)
  File "/usr/local/lib/python2.7/site-packages/mlab/matlabpipe.py", line 250, in get
    self._read_until('start_binary\n', on_new_output=on_new_output)
  File "/usr/local/lib/python2.7/site-packages/mlab/matlabpipe.py", line 294, in _read_until
    raise MatlabConnectionError('timeout')
MatlabConnectionError: timeout

I encountered the third problem, and its stack trace was totally same as yours. It shows mlab.matlabpipe.MatlabConnectionError:timeout.
It happened when I want to execute the following commands in Ubuntu:
from mlab.releases import latest_release as matlab
matlab.plot([1,2,3,4,5],-'o')   #failed
But in Windows, it succeeded.
I tried to solve it, but found nothing.
If you have any suggestions, I will be very thankful.

I encountered the same issue, and solved by following the official website instruction: https://cn.mathworks.com/help/matlab/matlab-engine-for-python.html


Add mat383.com

Hi, I love website collections like these.
I'd like to add my personal website https://mat383.com
The homepage is 38.72kb in size, I'm not sure how much it is compressed.
Thanks in advance for your time!

I love that logo animation. Nice idea!
Welcome to the 250kB Club!


[PE-D] Documentation bug

The UG specifies that the email must be of form<EMAIL_ADDRESS>but contains some formatting errors.

There is inconsistency issue between the stated email format and the examples that are given.

Labels: type.DocumentationBug severity.Medium
original: Halpfrog/ped#4

put one example of non-nus email


false WARN messages after extension upgrade

Hi, as I mentioned here after an upgrade the datadog lambda extension to version v64 we got weird messages popped up in the logs
2024-09-11 15:09:38 UTC | DD_EXTENSION | WARN | config key flare_stripped_keys is unknown
2024-09-11 15:09:38 UTC | DD_EXTENSION | WARN | failed to get configuration value for key "flare_stripped_keys": unable to cast <nil> of type <nil> to []string
2024-09-11 15:09:38 UTC | DD_EXTENSION | WARN | config key scrubber.additional_keys is unknown
2024-09-11 15:09:38 UTC | DD_EXTENSION | WARN | failed to get configuration value for key "scrubber.additional_keys": unable to cast <nil> of type <nil> to []string

we don't have any of these configurations configured, therefore I assume it's a bug
here is our config:
apm_config:
  enabled: true

site: datadoghq.eu

use_dogstatsd: false

cloud_provider_metadata:
  - "aws"

# https://docs.datadoghq.com/opentelemetry/otlp_ingest_in_the_agent/?tab=host
otlp_config:
  receiver:
    protocols:
      grpc:
        endpoint: <IP_ADDRESS>:50052
  metrics:
    enabled: true
    resource_attributes_as_tags: true
    tag_cardinality: low
  traces:
    enabled: true
    span_name_remappings:
      go.opentelemetry.io_contrib_instrumentation_google.golang.org_grpc_otelgrpc.server: grpc.server
      go.opentelemetry.io_contrib_instrumentation_google.golang.org_grpc_otelgrpc.client: grpc.client
      go.opentelemetry.io_contrib_instrumentation_net_http_otelhttp.client: http.client
      go.opentelemetry.io_contrib_instrumentation_net_http_otelhttp.server: http.server
      observability_lambda.server: aws.lambda
      aws.lambda.internal: aws.lambda

logs_enabled: true
logs_config:
  processing_rules:
    - type: exclude_at_match
      name: exclude_start_and_end_logs
      pattern: (START|END|REPORT)\s

I did tried to add empty list to the config
scrubber:
  additional_keys: []

but it didn't solve the problem

Hey @Vladikamira,
Is this on v64? If so, could you try upgrading to v65?
If the problem persist, let me know!

v65 has the same issue

Is it the only one? If so, does removing

I did tried to add empty list to the config

scrubber:
  additional_keys: []

This from your config file solves it?

no, nothing is solving these messages. Here is what I have on v64/v65
2024-09-16 07:34:40 UTC | DD_EXTENSION | WARN | config key fleet_policies_dir is unknown
2024-09-16 07:34:40 UTC | DD_EXTENSION | WARN | failed to get configuration value for key "scrubber.additional_keys": unable to cast <nil> of type <nil> to []string
2024-09-16 07:34:40 UTC | DD_EXTENSION | WARN | failed to get configuration value for key "flare_stripped_keys": unable to cast <nil> of type <nil> to []string
2024-09-16 07:34:40 UTC | DD_EXTENSION | WARN | failed to get configuration value for key "scrubber.additional_keys": unable to cast <nil> of type <nil> to []string
2024-09-16 07:34:40 UTC | DD_EXTENSION | WARN | config key scrubber.additional_keys is unknown
2024-09-16 07:34:40 UTC | DD_EXTENSION | WARN | failed to get configuration value for key "flare_stripped_keys": unable to cast <nil> of type <nil> to []string
2024-09-16 07:34:40 UTC | DD_EXTENSION | WARN | config key flare_stripped_keys is unknown

Hi. Is there any update on this? Having same issue on arm v65.

any update? V65 is having the same issue

I'll assign someone on Monday to look over this, sorry haven't been able to reproduce this.

Hello @Vladikamira
Thank you for opening this. This has been fixed in https://github.com/DataDog/datadog-agent/pull/30622. We plan on doing a Lambda extension release this week.

Awesome! Thanks for the update @nhulston , I will wait for the release and check

Hey @Vladikamira, apologies for coming back to this. That PR I linked doesn't actually fix this issue. Sorry for the confusion. However, we've identified the real issue and are working on a fix. The change should be out soon!

Hey everyone,
Sorry for the delay.
The latest release v66 should include this fix.
Feel free to re-open if issue persist!


Hide Youtube videos you already watched not working

What filter does this issue target?
Hide Youtube videos you already watched
What changes should be made?
To simply put, the filter is not working on "https://www.youtube.com/c/[CHANNEL]/videos" page.
And only this option is checked.

Edit: It works when the 2nd option is checked like this.

Did you write a uBlock filter solving this?
No response
Additional notes
No response

So on specific channel no longer exist tag:
<ytd-grid-video-renderer> blah blah blah </ytd-grid-video-renderer>

Hello @FahadBinHussain and @krystian3w, thanks for reporting this! I'm a bit swamped at the moment, but I'll take a look at it this month. Sorry for the delay.

Heya, thanks for your patience. This is fixed in today's deploy.
The issue is that the homepage rule was not specific enough, and matching the channel page too. This is why I could not reproduce this issue.


Update styles.css

Done the changes according to issue number pranjay-poddar #1669
Title and Issue number
Added some Hovering effect on responsive footer and the issue number is #1669
Close #<1669>
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

Template is still wrong please correct the format, remove <>


Installation of LXDE fails, because of udisks2

The configuration script of the package udisks2 returns an error, causing the installation of lxde to fail.
It's only a recommended dependency. The following command works:
sudo DEBIAN_FRONTEND=noninteractive apt-get -y install lxde udisks2-

symlink(../proc/self/mounts, /etc/mtab) failed: Invalid cross-device link....
various symlink


Spurious MANUAL CONTROL LOST on Pixracer

Every few seconds, I see the following warning on a Pixracer with only USB and debug console connected:
WARN  [commander] MANUAL CONTROL LOST (at t=17692ms)

So far I've found that manual_control_setpoint is published  because input_rc has been published. I have however not found who is publishing input_rc.

Is your GCS sending joystick commands? Do you have on-Screen or real joystick enabled?

Is your GCS sending joystick commands? Do you have on-Screen or real joystick enabled?

No, that was my initial suspect as well.
According to the rc_input struct, the input source is PX4FMU SBUS:
listener input_rc

TOPIC: input_rc instance 0 #1
 input_rc_s
        timestamp: 152511328  (10.958436 seconds ago)
        timestamp_last_signal: 152511328
        channel_count: 18
        rssi: 255
        rc_lost_frame_count: 1
        rc_total_frame_count: 0
        rc_ppm_frame_length: 0
        values: [874, 1036, 1274, 1394, 874, 884, 874, 878, 884, 1204, 1004, 1208, 2143, 2135, 2033, 1842, 998, 998]
        rc_failsafe: False
        rc_lost: False
        input_source: 9

It looks like sbus is parsing something.

What is connected to that port? Anything? Nothing? Where did you purchase the bird from?

It's a Pixracer R15 in purple, presumably from mRo. Nothing is connected.

It feels like it's floating and reading garbage.

This is what it looks like:
new bytes: 1: 0x00
new bytes: 1: 0x02
new bytes: 2: 0x00 00
new bytes: 4: 0x00 01 80 48
new bytes: 8: 0x90 d0 06 41 00 00 18 a1
new bytes: 2: 0xa2 1d
new bytes: 6: 0x00 00 11 09 cc 7e
new bytes: 1: 0xfe
new bytes: 8: 0xf4 7b 53 50 00 06 3c 62
new bytes: 8: 0x01 91 40 00 81 00 20 18
new bytes: 6: 0x02 b8 00 ae 3f f2
new bytes: 3: 0xff fe f0
new bytes: 1: 0x00
new bytes: 1: 0x00
new bytes: 4: 0x00 00 10 00
new bytes: 5: 0x81 10 00 20 00
new bytes: 9: 0x00 0c 0e 00 18 26 bb f0 fb
new bytes: 16: 0xff f8 e1 7e bf ff 7e e8 d0 ed 93 76 8f 22 20 01
new bytes: 7: 0x1c 07 40 40 00 00 00
new bytes: 6: 0x00 00 60 00 08 38
new bytes: 5: 0x0c 03 de ff ff
new bytes: 2: 0x00 02
new bytes: 10: 0x00 a2 3d 20 20 70 ee fd f0 ff
new bytes: 13: 0xf0 fa f0 56 9e f0 ff bc ff 86 03 00 40
new bytes: 7: 0x07 2c e0 00 00 00 00
new bytes: 6: 0x00 00 40 08 0f e0
new bytes: 5: 0x00 71 04 5a f0
new bytes: 21: 0xfe f9 f0 fb d0 da ce d4 5e b5 7e 00 20 66 bc 00 81 00 d3 7b c1
we parsed from SBUS
received RC in
publishing sp_man
new bytes: 1: 0xf4
copy sp_man
WARN  [commander] MANUAL CONTROL LOST (at t=11511ms)

I tried another identical Pixracer and the problem does not happen, however, it consistently reads one 0x00 byte about every 2 seconds. Presumably that's a different problem.
Closing this as it's apparently just faulty hardware.


Failed to build trackerjacker :  Ubuntu 18.04 Bionic Beaver

~$ pip3 install trackerjacker
Collecting trackerjacker
  Using cached https://files.pythonhosted.org/packages/d2/81/4dca960aeb78e070c1639ccbacfaa17182762f5c808c2eee0f1906c5fff4/trackerjacker-1.8.7.tar.gz
Collecting scapy==2.4.0 (from trackerjacker)
Collecting pyaml>=17.12.1 (from trackerjacker)
  Using cached https://files.pythonhosted.org/packages/17/c1/5892f756109e54ed53c753129b0da4acf6b6add8dff5a85b18667553b16d/pyaml-17.12.1-py2.py3-none-any.whl
Collecting ruamel.yaml==0.15.0 (from trackerjacker)
  Using cached https://files.pythonhosted.org/packages/d4/01/13c17da38beeb4a53f4db875b5d19298d24ddf9c6101821e9737f87b98c2/ruamel.yaml-0.15.0-cp36-cp36m-manylinux1_x86_64.whl
Collecting PyYAML (from pyaml>=17.12.1->trackerjacker)
Building wheels for collected packages: trackerjacker
  Running setup.py bdist_wheel for trackerjacker ... error
  Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-5_u6ggw1/trackerjacker/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmpmi8gcf02pip-wheel- --python-tag cp36:
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib
  creating build/lib/trackerjacker
  copying trackerjacker/macos_device_management.py -> build/lib/trackerjacker
  copying trackerjacker/dot11_tracker.py -> build/lib/trackerjacker
  copying trackerjacker/common.py -> build/lib/trackerjacker
  copying trackerjacker/dot11_frame.py -> build/lib/trackerjacker
  copying trackerjacker/config_management.py -> build/lib/trackerjacker
  copying trackerjacker/version.py -> build/lib/trackerjacker
  copying trackerjacker/plugin_parser.py -> build/lib/trackerjacker
  copying trackerjacker/__init__.py -> build/lib/trackerjacker
  copying trackerjacker/ieee_mac_vendor_db.py -> build/lib/trackerjacker
  copying trackerjacker/linux_device_management.py -> build/lib/trackerjacker
  copying trackerjacker/dot11_mapper.py -> build/lib/trackerjacker
  copying trackerjacker/__main__.py -> build/lib/trackerjacker
  creating build/lib/trackerjacker/plugins
  copying trackerjacker/plugins/foxhunt.py -> build/lib/trackerjacker/plugins
  copying trackerjacker/plugins/__init__.py -> build/lib/trackerjacker/plugins
  running egg_info
  writing trackerjacker.egg-info/PKG-INFO
  writing dependency_links to trackerjacker.egg-info/dependency_links.txt
  writing entry points to trackerjacker.egg-info/entry_points.txt
  writing requirements to trackerjacker.egg-info/requires.txt
  writing top-level names to trackerjacker.egg-info/top_level.txt
  reading manifest file 'trackerjacker.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  writing manifest file 'trackerjacker.egg-info/SOURCES.txt'
  copying trackerjacker/oui.txt -> build/lib/trackerjacker
  installing to build/bdist.linux-x86_64/wheel
  running install
  running install_lib
  creating build/bdist.linux-x86_64
  creating build/bdist.linux-x86_64/wheel
  creating build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/macos_device_management.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  creating build/bdist.linux-x86_64/wheel/trackerjacker/plugins
  copying build/lib/trackerjacker/plugins/foxhunt.py -> build/bdist.linux-x86_64/wheel/trackerjacker/plugins
  copying build/lib/trackerjacker/plugins/__init__.py -> build/bdist.linux-x86_64/wheel/trackerjacker/plugins
  copying build/lib/trackerjacker/dot11_tracker.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/common.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/oui.txt -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/dot11_frame.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/config_management.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/version.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/plugin_parser.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/__init__.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/ieee_mac_vendor_db.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/linux_device_management.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/dot11_mapper.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  copying build/lib/trackerjacker/__main__.py -> build/bdist.linux-x86_64/wheel/trackerjacker
  running install_egg_info
  Copying trackerjacker.egg-info to build/bdist.linux-x86_64/wheel/trackerjacker-1.8.7-py3.6.egg-info
  running install_scripts
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-build-5_u6ggw1/trackerjacker/setup.py", line 54, in <module>
      'Operating System :: MacOS'
    File "/home/aditya/.local/lib/python3.6/site-packages/setuptools/__init__.py", line 129, in setup
      return distutils.core.setup(**attrs)
    File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
      dist.run_commands()
    File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
      self.run_command(cmd)
    File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
      cmd_obj.run()
    File "/usr/lib/python3/dist-packages/wheel/bdist_wheel.py", line 257, in run
      self.distinfo_dir)
    File "/usr/lib/python3/dist-packages/wheel/bdist_wheel.py", line 427, in egg2dist
      distribution=self.distribution)
    File "/usr/lib/python3/dist-packages/wheel/metadata.py", line 177, in pkginfo_to_dict
      new_requirements = sorted(convert_requirements(requirements))
    File "/usr/lib/python3/dist-packages/wheel/metadata.py", line 234, in convert_requirements
      parsed_requirement = pkg_resources.Requirement.parse(req)
    File "/home/aditya/.local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2995, in parse
      req, = parse_requirements(s)
  ValueError: not enough values to unpack (expected 1, got 0)

  ----------------------------------------
  Failed building wheel for trackerjacker
  Running setup.py clean for trackerjacker
Failed to build trackerjacker
Installing collected packages: scapy, PyYAML, pyaml, ruamel.yaml, trackerjacker
  Running setup.py install for trackerjacker ... done
Successfully installed PyYAML-3.13 pyaml-17.12.1 ruamel.yaml-0.15.0 scapy-2.4.0 trackerjacker-1.8.7

With GitHub Build Installed But =>
~$ trackerjacker
Traceback (most recent call last):
  File "/usr/local/bin/trackerjacker", line 11, in <module>
    load_entry_point('trackerjacker==1.8.7', 'console_scripts', 'trackerjacker')()
  File "/home/aditya/.local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 480, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/home/aditya/.local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2691, in load_entry_point
    return ep.load()
  File "/home/aditya/.local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2322, in load
    return self.resolve()
  File "/home/aditya/.local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2328, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/local/lib/python2.7/dist-packages/trackerjacker-1.8.7-py2.7.egg/trackerjacker/__main__.py", line 269
    print('Vendor for {} not found'.format(args.mac_lookup), file=sys.stderr)
                                                                 ^
SyntaxError: invalid syntax

Make sure you have run:
sudo apt-get install python-scapy
I had to su to root then ran
pip3 install trackerjacker
to resolve that issue.

Yes, this issue is due to an old version of pip. @Adity-dev, does it work if you pip3 install --upgrade pip first?

@calebmadrigal https://github.com/calebmadrigal/trackerjacker/issues/11#issuecomment-415812115 : Nope ! But it does broke pip3 in Ubuntu !
Tried Solution provided by @zwieberl https://github.com/calebmadrigal/trackerjacker/issues/11#issuecomment-414563117
It Does work But Still I'm facing a Issue:
$ sudo trackerjacker -i wlp2s0
Enabling monitor mode on wlp2s0
Monitoring all available channels on wlp2s0: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140]
Traceback (most recent call last):
  File "/home/aditya/.local/lib/python3.6/site-packages/trackerjacker/__main__.py", line 229, in start
    scapy.sniff(iface=self.iface_manager.iface, prn=self.process_packet, store=0)
  File "/home/aditya/.local/lib/python3.6/site-packages/scapy/sendrecv.py", line 767, in sniff
    p = s.recv()
  File "/home/aditya/.local/lib/python3.6/site-packages/scapy/arch/linux.py", line 600, in recv
    pkt, sa_ll = self.ins.recvfrom(x)
OSError: [Errno 100] Network is down

Sniffer error occurred. Restarting sniffer in 3 seconds...
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
command failed: Device or resource busy (-16)
^C
Disabling monitor mode for interface: wlp2s0
command failed: Device or resource busy (-16)

Take a look at #15 . I think you have to deactivate NetworkManager:
systemctl stop NetworkManager

@Adity-dev Please take a look at @zwieberl's suggestion. The Device or resource busy typically means something else is managing the device, like a network manager.


Continue the old 0.2.x series and widen the version range of the native-tls dependency

Hi, an old codebase of mine is still using reqwest 0.6, the last sync one. I've been hesitant to to change to the async ones for time being, as I'm just maintaining the code and not willing to have a lot of code churn. reqwest 0.6 uses hyper-native-tls 0.2.x for TLS, and because of this, I'm not able to use modern OpenSSL versions, as they require the openssl crate 0.10.x version whereas hyper-native-tls pulls in 0.9.x via native-tls 0.2. Widening supported native-tls version range to include both 0.2 and 0.3 seems to fix this.
I know that 0.2.x hyper-native-tls is old and possibly unsupported, but I was wondering whether it would be possible to widen the version range and publish a patch version bump? My reasoning is that widening the range while keeping the lower range the same should be backwards compatible, as it doesn't force anyone to bump their transitive dependencies if there is another dependency that requires strictly 0.2.x.
Another alternative would be to publish reqwest 0.6.x that depends on hyper-native-tls 0.3.0. I'm unsure which one is more feasible.

The 0.2.x series is over 3 years old. I am not interested in continuing maintenance on it.

I see. I'll try sending a PR to reqwest. Thanks.


What android versions will this work on?

Jason this is a nice looking plugin that should solve some permission problems I've been having.  The readme does not explicitly state what android versions this will work with.  Could you elaborate?  How far back does this go?  Will it work on kitkat?
Thanks for sharing this plugin.

This plugin is based on Cordova plugin framework which version should >= 5.0.0.
plugin.xml
Android Platform Guide
So this plugin supported Android SDK version >= 14.

Issues resolved.  Thanks!!


v6 blew uglifyjs

Updating to v6 breaks build which use ugilfyjs in the pipeline with:

ERROR in app-32ad34666c9e041dfb35.js from UglifyJs
Unexpected token: name (onClickOutside) [app-32ad34666c9e041dfb35.js:111558,33]

Which seems to be caused by this line in the generated code (let is not valid in es5)
v5.11.1 doesn't have this issue..

It's a major version update for a good reason: v6 is pure ES6, so you'll have to either tell uglify to run on modern JS, or run it after you've bundled everything with ES5 conversion.

closing this as duplicate of #185 , we're also having this issue in a webpack+babel setup


problems occured

Hi, nice buddy. Thanks for your brilliant project.
After I finished preprocessing work, I ran the command roslaunch gazebo_multirobot.launch . There were some warnings printed in the terminal, e.g.,
[ WARN] : Timed out waiting for transform from robot3_tf/robot3_tf/base_link to robot3_tf/robot3_tf/map to become available before running costmap, tf error: canTransform: target_frame robot3_tf/robot3_tf/map does not exist. canTransform: source_frame robot3_tf/robot3_tf/base_link does not exist.. canTransform returned after 0.1 timeout was 0.1.
And in the RVIZ, RobotModel reported the information like "No transform from [robot1_tf/base_footprint] to [world]". Would you mind giving some advice on how to fix these problems?
Thanks in advance!

@voiceheard Thanks for your feedback! I will try to look at the issue asap. Meanwhile, can you give me your system details like ROS and Ubuntu version?

@emrecanbulut Thanks for your reply. My system is Ubuntu16.04, and my ROS version is kinetic.

Hi, nice buddy. Thanks for your brilliant project.
After I finished preprocessing work, I ran the command roslaunch gazebo_multirobot.launch . There were some warnings printed in the terminal, e.g.,
[ WARN] : Timed out waiting for transform from robot3_tf/robot3_tf/base_link to robot3_tf/robot3_tf/map to become available before running costmap, tf error: canTransform: target_frame robot3_tf/robot3_tf/map does not exist. canTransform: source_frame robot3_tf/robot3_tf/base_link does not exist.. canTransform returned after 0.1 timeout was 0.1.
And in the RVIZ, RobotModel reported the information like "No transform from [robot1_tf/base_footprint] to [world]". Would you mind giving some advice on how to fix these problems?
Thanks in advance!

Did you resolve this?


tests: fix sip tests

The correct numbers of alerts logged is not correct and OISF/suricata#4330
fixes this issue, so this commit fixes tests that are broken.
I removed the test added previously, because it's a duplicate of sip-method test.
Previous PR: #156

I've merged this. It seems to be fixed with https://github.com/OISF/suricata/pull/4393 as well.
Thanks Giuseppe!


feat(client/palette): align palette

This aligns the palette to the Camunda Modeler Palette, except DataObject and DataStore action, which are not supported as by now.
It also adds support for some elements with no execution semantics (cf. #112)
Closes #113
Closes #117

This includes known issues for the ContextPad, e.g. having not allowed actions.

This should be fixed in #114.

🎉


pythonPackages.av: 0.4.1 -> 0.5.3

Things done
Update av to the latest version.
I switched to using a newer version of ffmpeg (it was previously using ffmpeg 2, which is no longer supported by this library). I also removed libav as a build input, because it does not seem to be necessary.
I've tested it with aiortc (out of nixpkgs tree) and it seems to work correctly.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build pythonPackages.av

Success on x86_64-darwin (full log)
Attempted: pythonPackages.av
Partial log (click to expand)
  The script pyav is installed in '/nix/store/6dgm795yh4y40kyyjzn0lhyi6k2yaa0g-python2.7-av-0.5.3/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed av-0.5.3
/private/tmp/nix-build-python2.7-av-0.5.3.drv-0/av-0.5.3
post-installation fixup
strip is /nix/store/9xjkb4xz0b5lmizij9ppxy7lkxdxhx6b-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/6dgm795yh4y40kyyjzn0lhyi6k2yaa0g-python2.7-av-0.5.3/lib  /nix/store/6dgm795yh4y40kyyjzn0lhyi6k2yaa0g-python2.7-av-0.5.3/bin
patching script interpreter paths in /nix/store/6dgm795yh4y40kyyjzn0lhyi6k2yaa0g-python2.7-av-0.5.3
wrapping `/nix/store/6dgm795yh4y40kyyjzn0lhyi6k2yaa0g-python2.7-av-0.5.3/bin/pyav'...
/nix/store/6dgm795yh4y40kyyjzn0lhyi6k2yaa0g-python2.7-av-0.5.3

Success on x86_64-linux (full log)
Attempted: pythonPackages.av
Partial log (click to expand)
shrinking /nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3/lib/python2.7/site-packages/av/container/output.so
shrinking /nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3/lib/python2.7/site-packages/av/container/streams.so
shrinking /nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3/lib/python2.7/site-packages/av/container/core.so
shrinking /nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3/lib/python2.7/site-packages/av/container/pyio.so
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3/lib  /nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3/bin
patching script interpreter paths in /nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3
checking for references to /build in /nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3...
wrapping `/nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3/bin/pyav'...
/nix/store/7fn4ic1js5s6lq3fw363bhk6xfvd8d9k-python2.7-av-0.5.3

Success on aarch64-linux (full log)
Attempted: pythonPackages.av
Partial log (click to expand)
shrinking /nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3/lib/python2.7/site-packages/av/packet.so
shrinking /nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3/lib/python2.7/site-packages/av/plane.so
shrinking /nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3/lib/python2.7/site-packages/av/stream.so
shrinking /nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3/lib/python2.7/site-packages/av/utils.so
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3/lib  /nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3/bin
patching script interpreter paths in /nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3
checking for references to /build in /nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3...
wrapping `/nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3/bin/pyav'...
/nix/store/xip48gaqvhnls62dvc4m7zh0w6fa355c-python2.7-av-0.5.3


Distribute database

I was looking at doing Electron with linvodb3. Is there a way to ship a pre-filled database?

From what I can tell, there isn't a way to write the DB outside of the webpage (see: http://stackoverflow.com/a/35142175). Distributing a pre-filled database would not work.
I could use an form interface to load documents into the DB (in the form of Markdown)  for testing.
Is there a way to read a local folder to populate the database? I guess I would need to add documents to something like src\app\docs then move that folder over when it's built.
I require the whole project to be completely offline.

I cannot read local files directly. The only choice I have is HTTP requests to get each file. I really don't want/need to do this. Looks like I am at a stand still. =(

I think this is kind of out of scope. LinvoDB3 is an abstraction to any leveldown compatible store, so you should either change store to something that allows an offline database to be shipped or indeed pull the files at init time somhow
how big are the files?

Not sure how big they will be. Probably mostly smaller ones. I created a NodeJS custom command to run and migrate the files from X format to markdown to use in the DB. Then I was converting Markdown -> HTML.
Reasoning for this is because Markdown is similar to write if I was to generate a doc directly then other formats. I have some existing documents that I need to transition over which are a bit large but those shouldn't be that much.
I have considered PouchDB which might work. Thoughts?

Looks like I am going to use Pouchdb. I rewrote https://github.com/gr2m/spawn-pouchdb-server to work for me as well. Thanks for the support!


Minor modification in Kubectl cheatsheet.md

Fix: #36640

@NitishKumar please edit the title and description for this PR to summarize the change you are making.
We need that detail so we can check that the change you're making matches up with that summary.

Your PR contains no changes!

@mtardy The suggested changes were to remove the " at the end of the sentence.  It's applied now!

@mtardy The suggested changes were to remove the " at the end of the sentence.  It's applied now - here

Mmmh the " at the end of the sentence was introduced by you in a previous commit...
The actual change asked for the associated issue is suggested here https://github.com/kubernetes/website/pull/36645#discussion_r974516508.
At the moment, your PR has no changes in comparison to upstream.

kubectl get nodes -o='custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect' works
/approve


Strange rendering of remarks

Maybe I'm missing something but that seems off. Why the double space after the first word. Is that being treated as some kind of keyword? I'm using remarks as it was specified in TSDoc.

Hi @jasonkuhrt !
Sorry for the delay! This doesn't follow TSDoc, but JSDoc so don't expect all the tags from TSDoc to work out of the box.
Now, this is a really easy fix; for tags like this one, where there's no "type" nor "name", the comments' parser takes the first word as the "name". I'll just configure the plugin, so it will handle it the same way it handles @see or @license.
I'll try to push the fix today.
Btw, let me know if you see other issues with TSDoc, I'm not against adding compatibility, but I don't have time right now to go and do a full research :P.
Regards.

Awesome thanks! And will do.


Added Verdal

@sindrefag I am sorry for a delay with processing your request. Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


Notification fakes don't work for password reset notifications

Laravel Version: 5.3.10
PHP Version: 7.0.8
Database Driver & Version: MariaDB 10.1.18

Description:
Faking Notification does nothing when testing built in Laravel password reset notifications. Notifications are still sent and all assertions fail.
Steps To Reproduce:
This is my test:
use App\Notifications\ResetPassword;
use Illuminate\Support\Facades\Notification;

class PasswordResetTest extends SeleniumTestCase
{
    /**
     * @test
     */
    public function user_can_reset_password()
    {
        Notification::fake();

        $this->visit('/')
             ->press('Forgot password?')
             ->type($this->user->email, 'email')
             ->press('Send')
             ->hold(3)
             ->see(trans('general.email_sent'));

        Notification::assertSentTo($this->user, ResetPassword::class);
    }
}

Im using phpunit and Selenium. When running this test, a mail is actually being sent to the users email and the assertion fails. Just for fun, I tried faking Mail too, but that also didnt do anything.

@zachleigh this test doesn't look right to me, are you sure this is testing the built in password reset form?

This works:
public function testBasicExample()
{
    $user = factory(\App\User::class)->create();

    Notification::fake();

    $this->visit('/password/reset')
        ->type($user->email, 'email')
        ->press('Send Password Reset Link');

    Notification::assertSentTo($user, ResetPassword::class);
}

@themsaid I dont use the built in form, but my form points to same route as the built in one so the test should work. Anyway, it works for you so it must be something on my end. Thank you!

@zachleigh keep us updated please if you ever found a bug in this area :)


better behaviour for the case when the bot fails a mission

So... the bot still occasionally fails. 1 time out of 1000000, and for a good reason: when the agent is really badly blocked from the very beginning:

I think it's fine, and want to continue generating demos. This PR tweaks make_agent_demos.py a bit to just skip the seed on which agent fails and proceed to other missions. This way we'll have 999999 demos instead of 1000000 for some levels, which I think is bearable.

Hm, I would say just keep trying to generate demos until you hit 1M, don't generate less than requested.

It's not that simple. I generate demos in parallel. I launch 50 jobs and
each of them gets a segment of seeds to generate demos for. E.g. job 1 gets
seeds from 20000 to 39999. If let's say the mission for the seed 33455 is
failed, where should the job get more seeds? If it goes for the seed 40000,
there will be duplicate demos. I have considered that and decided that it's
better to have 999999 demos rather than 1000000 but with an unknown number
of duplicates. Do you agree?
On Fri, 1 Feb 2019 at 10:35 Maxime Chevalier-Boisvert <
<EMAIL_ADDRESS>wrote:

Hm, I would say just keep trying to generate demos until you hit 1M, don't
generate less than requested.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mila-udem/babyai/pull/44#issuecomment-459762586, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAn8YvOSs-WlY3szN_4Qmm9cBg4itGcAks5vJF7IgaJpZM4aeXuk
.