Foundation 6.2 Babel breaks browsersync

I upgraded to 6.2 after some issues with Babel and the migration guide not being what ultimately worked. I dug around and found the new babel includes in the package.json from the Zurb 6.2 templates and that did the trick.
HOWEVER, since upgrading to 6.2, making ANY syntax errors in my JS leads to Babel crashing and me having to restart the browsersync gulp task. Everything works fine until there is a syntax issue.
The error -
SyntaxError: src/assets/js/core.js: Unexpected token (20051:4)
    at Parser.pp.raise (.../node_modules/babylon/index.js:1412:13)
    at Parser.pp.unexpected (.../node_modules/babylon/index.js:2895:8)
    at Parser.pp.expect (/.../node_modules/babylon/index.js:2889:33)
    at Parser.pp.parseObj (.../node_modules/babylon/index.js:937:12)

Here's my task -
gulp.task('javascript', function() {
  var uglify = $.if(isProduction, $.uglify({
    <...>
      }
    })
    .on('error', function(e) {
      console.log(e);
    }));

  return gulp.src('src/assets/js/core.js')
    .pipe($.include())
    .on('error', console.log)
    .pipe($.sourcemaps.init())
    .pipe($.babel())
    .pipe(uglify)
    .pipe($.if(!isProduction, $.sourcemaps.write()))
    .pipe(gulp.dest('dist/assets/js'));
});

core.js actually contains all the imports (similar to how Sass does imports) using the Gulp Include plugin - https://www.npmjs.com/package/gulp-include
You can see above that .pipe($.include()) concats them, and then I pass babel. If I pass babel before the include, then no JS would be parsed in this method.
Any pointers on how to fix this so babel doesn't terminate the browsersync process? Thanks!

It looks like the answer for this may involved the gulp-plumber plugin (https://www.npmjs.com/package/gulp-plumber).  Will dig into this in the template once we've got the 6.3 RC packaged up

We did not fully switch to webpack. This is normal fur Gulp when the exceptions are not caught by something like gulp-plumber or gulp-notify.
This is a question about a custom implementation.

We might close this as this is the same with all Gulp setups.

If I understand correctly this is a problem coming from a custom build setup not using gulp-plumber. This should not be related to Foundation.
Closing this issue. @alanontheweb please reopen if we are wrong.


Update image filename

Coverage remained the same at 86.018% when pulling 1231cddde06d2a570f9f5b787a149ee1b962da33 on zhangshuoyang:theme_selection into 2cdab5b9be3fc9306ae70a3af1d224002147f241 on CS2103AUG2017-W11-B1:master.


No date and buttons shown

I used the same code as given in the readme.md but when I run it I am not able to see the dates on the timeline as well as the button or its configurations. So where can find corresponding code to the gif file of readme .md .  or where is the documentation about the dates on timeline and those buttons

You can find the source code of the documentation here :
https://github.com/stephane-monnot/react-vertical-timeline/tree/master/docs


Multi Field not working

rails 4.2 + elk 1.5
I have a model like this:
class My
  include Elasticsearch::Persistence::Model

  attribute :foo, Array,    mapping: {type: 'array'}
  attribute :title, String,   mapping: {type: 'string'}
  attribute :name, String,   mapping: { fields: {
                                                                name: { type: 'string', analyzer: 'snowball' },
                                                                raw:  { type: 'string', analyzer: 'not_analyzed' }
                                                               } }

in My.mapping.inspect I can see the correct mapping:
:name=>{:type=>"string", :fields=>{:name=>{:type=>"string", :analyzer=>"snowball"}, :raw=>{:type=>"string", :analyzer=>"not_analyzed"}}}

If I create a bunch of document I have this problem:
res_raw = My.search aggregations: {  names: { terms: { field: 'name.raw' } } }
res_raw.response.aggregations.tests.buckets.count  #=> 0

res_raw = My.search aggregations: {  names: { terms: { field: 'name' } } }
res_raw.response.aggregations.tests.buckets.count  #=> 10

I tried different approach like, change field type to 'multi_field' but I got same result. I created the docs using:
my = My.new {title: 'foo', name: 'bar'}
my.save
my.name #=> bar

Am I doing something wrong?

+1, multi field isn't working for me either in Rails 4.2

in My.mapping.inspect I can see the correct mapping

And when you look directly at localhost:9200/my/_mapping? Are you recreating the index when you changed the mappings?

@karmi I'm deleting the index and creating it again
Only workaround I found is to do the mapping "directly" before ES:Persistence do it

@jalberto Hm, this is weird, I really don't see why this wouldn't work. There's quite complicated mapping configs being used here: https://github.com/elastic/elasticsearch-rails/blob/master/elasticsearch-persistence/examples/music/artist.rb#L12, and that works. Would you be able to use that example and try the multi field with that? So we can have something I can run & debug on my end?

@karmi it's quite weird :)
the only way it works for me is creating the index and mapping in a different step and then feed the data
Trying to go deeper in the problem

@jalberto But yeah, you have to create the index first and then start indexing the data, otherwise the dynamic (default) mapping will kick in and ignore your configuration

@jalberto Can I help more?

@jalberto Double check the version of Elasticsearch you are running. I ran into numerous issues on our servers because of some old Elasticsearch packages, and it won't warn you if you try to create an index with options that it doesn't understand.

@delwaterman you are right, updating to last ELK fixed it. Now I can see multifield resuls :)
In other hand, how I access the secondary field:
res = My.search query: { match: {'foo.raw': 'bar'} }
res.first.foo #=> bar
res.first.foo.raw #=> NoMethod (as expected)
res.response.hits.hits.first._source[:foo] #=> bar
res.response.hits.hits.first._source['foo.raw'] #=> empty

So How can I access foo.raw?

Any fix for this? Still having the issue to create multi_fields, they appear on the Model.mapping but it seems to not be created with create_index! force: true

When relying on Model.import for index creation - the index gets created through the default mappings and any defined/custom mappings are ignored as @karmi pointed out.
The work around is to create the index before the import.
Model.__elasticsearch__.create_index! force: true
Model.import

Hi I've the same issue ,
@tamersalama , I've tried forcing the index creation , and then run the import but it does not work

@jalberto The "artificial" field, like foo.raw value isn't accessible from the _source -- that is purely a Lucene index level thing, so you can use it in queries, aggregations, sorting, and so on.

@tamersalama What "does not work" mean specifically?

@karmi , Sorry , "does not work" means that when the index is creates and then the import is made then in the search the use of not_analyzed index fields are not filtering results at all

the search hash used for this is somethink like the following
q = {
  query: {
    multi_match:
      {
        query: "oli",
        fields: ['first_name', "last_name", "type"],
        operator: "or" ,
        type: "phrase_prefix",
        slop: 10
      }
  },
  filter: {
    and: {
      filters: [
        { term: { type: "sometype" } },
        { term: { color: "red" } }
      ]
    }
  }
}

@michelson So, are you 100% sure you're using the force: true option? Can you attach here the (snippet) of mapping definition, and the resulting mapping?

Hi @karmi , thanks for your reply
and yes I've reindexed many times, with force true and with delete index
the mapping is something like this:
vagrant@miguel:/vagrant$ curl  http://localhost:9200/people/person/_mapping?pretty=true
{
  "people" : {
    "mappings" : {
      "device" : {
        "dynamic" : "false",
        "properties" : {
          "type" : {
            "type" : "string",
            "fields" : {
              "raw" : {
                "type" : "string",
                "index" : "not_analyzed"
              }
            }
          },
          "color" : {
            "type" : "string",
            "fields" : {
              "raw" : {
                "type" : "string",
                "index" : "not_analyzed"
              }
            }
          }
        }
      }
    }
  }
}

@michelson what versions are you using?

Closing as this is out of date.


Table rendering glitch

In viewing a Markdown table I get a garbled result:
            • Consistent doubled commas should be read as a single delimiter.
            • Missing data in the Favorite Color field should be substituted with the string <missing>.
            • Student ages should be between 9 and 14, and all other values are considered missing data.
            • Some colors are numerically coded, but should be unaliased.  The mapping is:

           | Number | Color    | Number | Color |:------:|:---------|:------:|---------- | 1      | beige
           | alabaster | 2      | eggshell | 7      | sandcastle | 3      | seafoam  | 8      | chartreuse
           mint     | 9      | sepia | 5      | cream    | 10     | lemon

           Using the small test data set is a good way to test your code.  But try also manually adding mo
           similar, or different, problems in them, and see how well your code produces a reasonable resul
           not discussed tools to accomplish this exercise yet, although you likely have used a programmin
           capable of solving it.  Try to solve it now, but you can come back to this after later chapters
           prefer.

Tables rendered as Pandas DataFrame outputs look very nice in the same notebook.  The example I tried is:
https://github.com/PacktPublishing/Cleaning-Data-for-Effective-Data-Science/blob/main/00-Preface.ipynb

Oh
(cleaning3.9) 6236-cleaning-data [main|✔]
% nbterm --version
nbterm 0.0.7
(cleaning3.9) 6237-cleaning-data [main|✔]
% uname -a
Linux popkdm 5.11.0-7612-generic #13~1617215757~20.10~97a8d1a-Ubuntu SMP Thu Apr 1 21:09:17 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
(cleaning3.9) 6238-cleaning-data [main|✔]
% python --version
Python 3.9.2

Markdown rendering is delegated to Rich, not sure what is going on.

The markdown renderer used by Rich does not support tables: https://github.com/Textualize/rich/issues/1868#issuecomment-1036106767


Inline mode: Is it possible to display the exact time, accurate to the second? Currently, committer.date only provides precision to the date.

Inline mode: Is it possible to display the exact time, accurate to the second? Currently, committer.date only provides precision to the date.

Hey Deja-vu. Thanks for the question/feature request!
Currently it does not. Would a token like ${committer.time} that would render like 18:54:32 be what you are looking for?


Editing a snippet in an editor

When editing an existing snippet (the-way search -> select -> shift+right), after confirming the other fields, the prompt says Code snippet (<RET> to edit in external editor). What is <RET> in this case? Return/enter appears to only submit the snippet as it is.
I have tried with $EDITOR both unset and set to vi.

Been looking at this again and it only behaves like this if the command/snippet is a single line. Happy to submit a PR for this but not sure what the preferred behaviour would be.
Options I can think of:

Open the editor for all snippets immediately instead of using the prompt (keep the prompt for the other fields)
Open the editor with the original command if  you delete the contents of a single line command. Potentially more convenient for single line commands but a bit unintuitive
Change the prompt to only mention editor when there are multiple lines (but keep the behaviour the same)
Something else?

Ah yes, good point, it's not super obvious now. I personally would prefer option 3

Change the prompt to only mention editor when there are multiple lines (but keep the behaviour the same)

since spinning up an editor for a single line command seems unnecessary in most cases - but let me know if you think otherwise or there are cases I'm not thinking of where editor support would be useful.

Another alternative would be to use a different key combo (Shift-Enter for instance) to open up the editor in this case - so would need a change in the prompt and behaviour.

The only issue I can see is if you want to add a second line to a single line command. Not sure how common a use case that is though. How easy is it to handle key-combos from Dialoguer? I think that would be the best of both worlds but is probably  the most involved change.

if you want to add a second line to a single line command

Oh this is a great point, hadn't considered it. Also, looks like dialoguer has some issues with certain characters (e.g. #128) so I think your Option 1 ( Open the editor for all snippets immediately instead of using the prompt ) makes the most sense now, even if it is a bit cumbersome for single line snippets.
Would you be up for making a PR?

Sure, will have a look this evening.

a bit cumbersome for single line snippets.

Thinking about this, would a fourth option be to prompt for edit snippet [y/N]?? Given edit also lets you edit the other metadata, it's not unlikely that the only edit is to change tag/description and this would prevent the editor opening every time which may be slow (can $EDITOR be set to a GUI app?).

Thinking about this, would a fourth option be to prompt for edit snippet [y/N]??

Yep, I like this idea! And yeah EDITOR could be anything so it's a pretty good way to make sure you don't open it unless you want to.


Feature/342 conda env

Closes #342

Coverage remained the same at 88.404% when pulling 92c41c129b9ae2e0f1867f738e0233cd5f6f172e on feature/342-conda-env into ef06280ede70bd1a1dc79441dfbac6a8a63b2de7 on master.


What is MSI?

Nowhere in this document has mentioned the full name of MSI. During Uninstall MSI part, I couldn't find MSI in search. Should I search for a different term, or MSI is not installed at all?

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

ID: 3426a777-4377-a1ec-73ea-31094e4713ee
Version Independent ID: b3ce94fa-6e76-4ffe-e70e-07f7a321fcd4
Content: Uninstall Azure PowerShell
Content Source: docs-conceptual/azps-1.2.0/uninstall-az-ps.md
GitHub Login: @sptramer
Microsoft Alias: sttramer

MSI refers to a Windows Installer (https://docs.microsoft.com/en-us/windows/desktop/msi/windows-installer-portal) package. The description in Add/Remove Programs should be similar to "Azure Powershell". There are different MSI packages for different versions of Azure Powershell, for example this one: https://github.com/Azure/azure-powershell/releases/tag/v6.13.1-November2018

The exact MSI package name should be "Microsoft Azure Powershell" followed by a date, for example "Microsoft Azure Powershell - November 2018"

Thanks ConcreteGannet for a clear explanation. Please go ahead and make a judgement call on whether a link that explains what MSI is should be added on this page. Other than that feel free to resolve and close this issue. 👍


Modify the invite members flow to invite participants

Summary
Simple change so that the invite members action becomes an invite participants action.
New action:

Ticket Link
Fixes #1416

@abhijit-singh Updated experience:


Some duplicates of the information deleted. And some formatting to sp…

…lit a data information and descriptions added.
Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. Your PR title can be also used in here.
Types of changes
What types of changes does your content introduce to this project?
Put an x in the boxes that apply (without "`")

[x] Proofreading (fix spelling, grammar, punctuation, accuracy) Proofreading
[ ] New content (new section, new readme, etc)
[ ] Modifications (modifying existing content, adding new content)
[ ] Other (please describe)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. Don't hesitate to ask if you're unsure about any of them. We're here to help! This simply reminds us of what we will look for before merging your code.
Note: If you submit code make sure to test it

[x] Tested any code that was added/modified in this PR
[ ] Added the necessary explanation
[ ] I have added the necessary links in the working section
[ ] Added external links
[ ] Added internal links
[ ] Added images
[ ] Added videos
[ ] Added code snippets

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Adding your name to the contributor's list
Comment "@all-contributors please add @your_username for content" to add your name to the contributor's list.
You can change the "content" with any of this
Reviewers:

[ ] @username

If you add code, please ensure that you are not adding any sensitive information like API keys, secrets, passwords, tokens, usernames, or other credentials. Refrain from adding your name, email, or other personal information to the code.

@all-contributors add @Technic143 for typo

@all-contributors add @Technic143 for doc

Content 09.11.2022, 11:22, "allcontributors[bot]"<EMAIL_ADDRESS>couldn't determine any contributions to add, did you specify any contributions?Please make sure to use valid contribution names.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Epoll patch and HTTP2 frame size tune.

Include epoll in gradle build.
Add config for http2FrameMaxSize, http2initialWindowSize and WriteBufferWaterMark to support larger frame size.
Background:
In a recent performance test, we noticed 1MB http2 response time is high: round trip time is good but time from first frame to last frame is terrible. The reason is Netty chunks 1MB data to multiple 64KB frames and this caused multiple round trips and delayed Netty processing. The change is to support large frame size by configuring http2FrameMaxSize, http2initialWindowSize and WriteBufferWaterMark.

Some explanations about watermark:
https://stackoverflow.com/questions/25281124/netty-4-high-and-low-write-watermarks


dash in database name is not supported

Connection fails for jdbc driver if database name has a dash

fix is included in PR #247


Cannot Use doublequotes on settings.json (even escaped)

Windows Terminal version (or Windows build number)
10.0.18363.0
Other Software
cmd.exe
Steps to reproduce
On settings.json use the following:
"commandline": "powershell.exe Start-Process cmd.exe '/c wt.exe -p \"Windows PowerShell\"' -verb runAs",

Double quotes is required since the name has an space character.
settings.json.txt
Expected Behavior
If you ran the same on powershell or cmd directly, you can get the expected result which is open the Windows Terminal with a Desired Profile:
PowerShell
Start-Process cmd.exe '/c wt.exe -p "Windows PowerShell"' -verb runAs

Command Prompt
powershell.exe Start-Process cmd.exe '/c wt.exe -p \"Windows PowerShell\"' -verb runAs```

Actual Behavior
This configuration is not being taken, instead opens the default profile.

Not sure what version of WT you're running but here version 1.10.2383.0 doesn't have a "-p" option. I guess that would be for selecting a profile. My take is WT uses GUIDs for selecting profiles not profile names, and it defaults to PS.
Sample WT help:

Run "wt.exe -h" to see WT help.

@elsaco you are wrong, it is documented and work just fine directly from the command line (I though that was clear that on the "expected behaviour" section it works)
https://docs.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows#open-a-new-profile-instance

@G3NSVRV true, I'm wrong sometimes!
I've changed your command to:
"commandline": "powershell.exe Start-Process cmd.exe '/c wt.exe -p Windows PowerShell' -verb runAs",
and it launches a new windows with admin privileges:

@elsaco Still didn´t work. I think in your case you got that result because your default profile is powershell, mine is ubuntu:

This should do it:
"commandline": "powershell start-process wt.exe '-p \"Windows PowerShell\"' -verb runAs",
I tried with a Bash profile and it worked. Also there's no need to have powershell launch cmd to launch a powershell session with admin privileges. Too many chained commands, IMO.

@elsaco that is what I tried first time, but didn't work, I got this error:

Hi,
I'm not sure why it is not working for you. I've changed my default profile
to launch Ubuntu and then use a profile with the command mentioned before.
The only funny thing is that the color scheme seems to be inherited from
Ubuntu, at least the background.
Sample screenshot with new profile. I did edit the settings.json directly,
but it shouldn't matter:
[image: ubuntu_ps-admin_launch.png]
Looking at the error message there might be a file access issue at
your end. Hope this helps!
On Sun, Sep 12, 2021 at 1:07 PM [G3NSVRV] @.***> wrote:

@elsaco https://github.com/elsaco that is what I tried first time, but
didn't work, I got this error:
[image: image]
https://user-images.githubusercontent.com/11720535/133001268-d9ad416c-30ff-4032-8897-4d4a53b2c32b.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/11206#issuecomment-917701791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6ANYCUGZI5EPSF4L55OQTUBUB7RANCNFSM5D4JRV2Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@elsaco same happened to me, that means that does not load the "Powershell" profile properly.
I did this workaround and works flawlessly:
settings.json
"commandline": "powershell D:\\elevated-wt.ps1",

elevated-wt.ps1
Start-Process cmd.exe '/c wt.exe -p "Windows PowerShell"' -verb runAs

so that means that is possible to configure it is just that by default from the JSON config something happened with the quoting and you got weird behaviours.

Yea, something weird is going on with the quote escaping here, but it's hard to tell exactly what because there are just so many layers of commandline escaping here. I'm sure someone with more time than me could figure it out.
At the end of the day though, looks like what you're looking for is #632 😉
I'm gonna close this for now since you've seemed to figure it out for yourself, though if anyone else finds the right way to escape the commandlines here, feel free to share it!

I'm sure someone with more time than me could figure it out.

That means that all the team will not be able to resolve this? the case is closed, and should be open.

At the end of the day though, looks like what you're looking for is #632 😉

Yes and no, I don't have issues with the escalation privileges persé, I have issues with the quoting and because of that I believe that this case should remain open.

I'm gonna close this for now since you've seemed to figure it out for yourself, though if anyone else finds the right way to escape the commandlines here, feel free to share it!

A workaround does not mean that is a permanent solution, the quoting issue is still present.

A workaround does not mean that is a permanent solution, the quoting issue is still present.

Unfortunately, this issue is going to remain until somebody (not us!) figures out shell quoting rules. The problem is that we're passing your commandline directly to CreateProcess (the main engine of process creation on Windows), and whatever happens after that is utterly out of our control. We don't change, quote, de-quote or re-quote the command line in any way before we do that.
In short, there are at least three programs handling your commandline, and each getting different subsets of it based on the way you quote it.
"commandline": "powershell.exe Start-Process cmd.exe '/c wt.exe -p \"Windows PowerShell\"' -verb runAs",

Terminal processes this into (this should be no surprise):
powershell.exe Start-Process cmd.exe '/c wt.exe -p "Windows PowerShell"' -verb runAs

PowerShell processes this into (hopefully?)
Start-Process cmd.exe '/c wt.exe -p "Windows PowerShell"' -verb runAs

However, it does not.
It actually turns it into this:
Start-Process cmd.exe '/c wt.exe -p Windows PowerShell' -verb runAs

Note the missing quotes.
This spawns...
cmd /c wt.exe -p Windows PowerShell

Which causes Terminal to look for a profile called Windows.

@DHowett  adding profiles without space in the profile name would take care of the issue? How about using profile's UUID instead of name?

Both of those should work!
You can definitely use the profile's guid!
wt -p "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}"

should work for the Windows PowerShell profile.

@DHowett @elsaco @zadjii-msft Far as I tested, this does not works too:
"commandline": "wt.exe -p \"Windows Powershell\"",

But this works:
"commandline": "wt.exe -p {61c54bbd-c2c6-5271-96e7-009a87ff44bf}",

So it is clearly an issue with the space, and as you see I'm not using any other layer like powershell or cmd, just wt.exe.

ok, I tried again, I forget that commandline is case sensitive, I replaced Powershell to PowerShell and that works fine, so as @zadjii-msft and @DHowett pointed out, it might be an issue with another layer like powershell or cmd.

this works perfectly fine, so yeah, I think it is good to have it closed, I will reference this issue on the elevation issue if someone tries to configure a profile with spaces:
"commandline": "powershell Start-Process cmd.exe '/c wt.exe -p {61c54bbd-c2c6-5271-96e7-009a87ff44bf}' -verb runAs",

came here via the email (presumably) you sent out from the other long, locked thread, and using the guid for the profile solved it!! i get a new window that is properly elevated and colored and is in powershell and not bash and everything. excellent work, thank you so much


Scrolling in alternate screen buffer

I was just testing the scrolling implementations and saw that these use the alternate screen buffer. So I was curious why this is done. I understand that the alternate screen buffer might do stuff differently, but shouldn't the very basic scrolling test just use the default screen buffer?
They also use the YES constant which already is filled with quite a few lines. This probably makes things quicker, but that doesn't really seem to be the goal here. If they would just print a single y, it would be possible to also allow the -c color flag to change the color with every line, which I think would make some sense with this test.
This diff shows the approach I had in mind:

diff --git a/src/bench.rs b/src/bench.rs
index c103990..43f1235 100644
--- a/src/bench.rs
+++ b/src/bench.rs
@@ -82,14 +82,15 @@ pub fn scrolling_in_region<W: Write>(ctx: &mut Context<W>, options: &Options) ->

 pub fn scrolling<W: Write>(ctx: &mut Context<W>, options: &Options) -> Result<usize> {
     let mut written = 0;
+    let mut rng = rand::thread_rng();

-    written += ctx.smcup()?;
     while written < options.bytes {
-        ctx.write_all(YES)?;
-        written += YES.len();
+        if options.colorize {
+            written += ctx.setaf(rng.gen_range(0, 8))?;
+        }
+        ctx.write_all(b"y\n")?;
+        written += b"y\n".len();
     }
-    ctx.rmcup()?;
-    ctx.sgr0()?;

     Ok(written)
 }

You're totally right about the alt screen changes being necessary, I wasn't thinking about it properly last night. I was just annoyed that it was blasting all the old output in the main view 🙃 .
Regarding colorize here, it's starting to test multiple things. Right now it's just testing line feed with single character outputs. This is two bytes per line. If we start adding color, that's another 5 bytes per line and hitting additional code paths in the emulator to change color state.

Yeah it would definitely test a path that doesn't really have anythingh to do with the basic scrolling test. But I thought it would be fairly simple to support the flag with this test and might show some performance differences.


Region cache stuck once try to load region until +inf

I have noticed this call never return:
	rs, err := c.Cache.LoadRegionsInKeyRange(bo, startKey, []byte(""))

According to dlv, this call generated a infinite loop in github.com/tikv/client-go/v2/internal/locate.(*RegionCache).LoadRegionsInKeyRange(), which tests whether the last region contains the end key is by a buggy function:
// ContainsByEnd check the region contains the greatest key that is less than key.
// for the maximum region endKey is empty.
// startKey < key <= endKey.
func (r *Region) ContainsByEnd(key []byte) bool {
	return bytes.Compare(r.meta.GetStartKey(), key) < 0 &&
		(bytes.Compare(key, r.meta.GetEndKey()) <= 0 || len(r.meta.GetEndKey()) == 0)
}

The left hand side of && simply always evaluates to false when the key is empty (which means inf). Which returns a false false when the input region has range (*, +inf].

fixed.


Ping services module is not work when using an https service

Environment
Docker
Version
0.4.0
Describe the problem
Ping Services module seems not working with services on https://
All services with https:// is offline but they work.
Additional info

Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues
[X] You've tried to debug yourself

I think you did a typo. If you host homarr on https it won't be able to ping http. I can look into it though

Sorry, i updated first comment and added screenshot for more details
Host homarr is on http://
But services on https:// say that they are offline, but no

This is not an issue, You are using a https on a local host. Just disable automatic redirect in Synology Login portal from http to https. Remove the https and add http.

Thanks for your knowledge @mariushosting! Marking this as closed. 🦞


CDAP-13262: Make WranglerContext implement metadata apis

CDAP PR: https://github.com/caskdata/cdap/pull/10107
mvn clean package -DskipTests passes locally

@albertshau: Fixed.


Support git lfs

It seems githack.com does not work with git lfs. Here's a test repo (not mine) with an LFS file: https://github.com/Schoonology/git-lfs-test - the file binary.jpg is stored with LFS. If I understand how githack is supposed to work, I should be able to wget that file straight from githack.com:
wget https://raw.githack.com/Schoonology/git-lfs-test/master/binary.jpg

But that just returns the pointer file:
% head binary.jpg
version https://git-lfs.github.com/spec/v1
oid sha256:6fe2e48ef494b7855e6d8f93c59cf38d38350274e304a9ac35102d5c365ee002
size 620773

which is not good.
Downloading straight from github raw works fine:
% wget https://github.com/Schoonology/git-lfs-test/raw/master/binary.jpg
% file binary.jpg.2
binary.jpg.2: JPEG image data, JFIF standard 1.01

but downloading using raw.githubusercontent.com (which may be where githack.com is proxying from?) does not:
% wget https://raw.githubusercontent.com/Schoonology/git-lfs-test/master/binary.jpg
% file binary.jpg.3
binary.jpg.3: ASCII text

So it would appear that at this point, githack doesn't support LFS. It would be great if it could!

It is related to #16 and I am currently working on that. Thank you.


Additional bridges don't respond after restart

I created three bridges for the different device types I am using. Only after changing the PIN code for the second and the third bridge to something unique was I able to find them in the Home app. However, after restarting Node-RED, these two bridges don't respond anymore. Only the first bridge I created still works after restarting Node-RED.

Hi Jonathan,
confirmed and fixed in 0.3.5!

I can confirm. Thank you!


Fix xcode 6.4 build

Closes #28.

This doesn't appear to have fixed the issue yet.  The xcode 6.4 build is still failing

I'm looking into this.

@phlptp Thanks for checking on this. I'm not sure how this happened, but the changes I'd made must have got reverted when I get a rebase onto develop. I've added the changes back and now it builds successfully on both.

@kdheepak what is pcre?

It's Perl Compatible Regular Expressions. The error messages I got without upgrading this on Travis OSX indicated that this was the problem when building swig from source.

See log for this build for the error message.
checking whether to enable PCRE support... yes

checking whether to use local PCRE... no

checking for a sed that does not truncate output... /usr/bin/sed

checking for pcre-config... no

configure: error: in `/tmp/swig-3.0.10':

configure: error:

        Cannot find pcre-config script from PCRE (Perl Compatible Regular Expressions)

        library package. This dependency is needed for configure to complete,

        Either:

        - Install the PCRE developer package on your system (preferred approach).

        - Download the PCRE source tarball, build and install on your system

          as you would for any package built from source distribution.

        - Use the Tools/pcre-build.sh script to build PCRE just for SWIG to statically

          link against. Run 'Tools/pcre-build.sh --help' for instructions.

          (quite easy and does not require privileges to install PCRE on your system)

        - Use configure --without-pcre to disable regular expressions support in SWIG

          (not recommended).

See `config.log' for more details

make: *** No targets specified and no makefile found.  Stop.


fix(clipboard): fix copy to clipboard functionality

Added a copyTextToClipboard function to handle text copying across different browsers and fallback scenarios. This function utilizes the Clipboard API when available, providing an asynchronous method to copy text securely. For browsers where the Clipboard API is not available or the page is not served over a secure context, a fallback method using a temporary textarea element and document.execCommand is employed. Replaced direct use of navigator.clipboard.writeText with this function in the 'shareget' click event listener to enhance cross-browser support and error handling.

added the doubt  label 7 hours ago

reason?

What browsers has problems with one line clipboard function?

What browsers has problems with one line clipboard function?

Safari on non-https pages and Firefox

Thanks!


Travis should not fail on v1.0

Currently we're waiting on 0.7 fixes for

[x] DiffEqBase
[ ] RandomNumbers

Once these are done, we can fail builds on 1.0 in .travis.yml

My DiffEqBase changes are merged, just waiting on a version bump (no need to move to bleeding edge at this stage).

The random numbers fix is merged, version bumps need to happen in DifferentialEquations before the error goes away. Builds are passing even on nightly though, so no issues there really.


Improve handling of memory regions

Avoid using a From implementation to turn &mut [u8] into Mem and instead hoist that logic into try_refill_and_get. Recover memory from the Region's vector directly since we know it starts at the beginning of the region.

Not relevant anymore.


Rename master to main

We've been discussing this for a while internally, but the last point of uncertainty was the new naming convention. Github itself is switching to use the less problematic name main by default, so let's go with that.
We're currently checking with some stakeholders to coordinate the timing of this, but are planning the change in the future.

The main branch has been create and is now the default. Update local clones with:
git submodule update origin
git checkout --track origin/main

Assigning @brycelelbach -- I'll let you decide whether to close this or leave it open until the github pages issue is fixed.

Let's close it.


feat: minimize panel on inactive

I found that, sometimes, the floating panel took a bit too much space from the app. So I am thinking of having a way to minimize it when not in use for a while.
The effect looks like this (shorten the timeout to 2s for demo):
https://github.com/nuxt/devtools/assets/11247099/4cbafb99-0f92-4666-bd4c-8064db0e78cf
I'd like to hear your opinion on this, and if we should make it configurable?

I thought about it, too. My idea is that we can output a open DevTools tip in the project's terminal, and when the user clicks on it, we can trigger the DevTools to open in the page. We need a configuration to allow users to toggle between these two options.

I thought about it, too. My idea is that we can output a open DevTools tip in the project's terminal, and when the user clicks on it, we can trigger the DevTools to open in the page. We need a configuration to allow users to toggle between these two options.

Additionally, regarding the minimize option, I think it makes sense. Completely hiding it might be necessary for some users.

@webfansplz I was thinking about doing it shortcut-only as well. It might be an option, but in that case, we also need to find a way to trigger it on touch devices.

Awesome work 🤩. I’ll port it to the Vue DevTools🤓


test CI/CD

Codecov Report

Merging #3 (8844625) into master (983db5b) will decrease coverage by 6.09%.
The diff coverage is 16.66%.

@@             Coverage Diff             @@
##            master       #3      +/-   ##
===========================================
- Coverage   100.00%   93.90%   -6.10%
===========================================
  Files            6        6
  Lines           76       82       +6
===========================================
+ Hits            76       77       +1
- Misses           0        5       +5

Flag
Coverage Δ

unittests
93.90% <16.66%> (-6.10%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pyraliddemo/example/math.py
75.00% <16.66%> (-25.00%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 983db5b...8844625. Read the comment docs.


//tests/tools_tests:generate_assets_declaration_test | which: no gh in (.:/bin:/usr/bin:/usr/local/bin)

@ b02049d666952d3bb07c45aa0bcd56d90766dd76
$ bazel test //tests/tools_tests:generate_assets_declaration_test --test_output=errors
INFO: Analyzed target //tests/tools_tests:generate_assets_declaration_test (2 packages loaded, 10 targets configured).
INFO: Found 1 test target...
FAIL: //tests/tools_tests:generate_assets_declaration_test (see /home/jamison/.cache/bazel/_bazel_jamison/04f084c324ba0be0b9506e8091939f14/execroot/buildifier_prebuilt/bazel-out/k8-fastbuild/testlogs/tests/tools_tests/generate_assets_declaration_test/test.log)
INFO: From Testing //tests/tools_tests:generate_assets_declaration_test:
==================== Test output for //tests/tools_tests:generate_assets_declaration_test:
which: no gh in (.:/bin:/usr/bin:/usr/local/bin)
Could not find Github CLI (gh).
================================================================================
Target //tests/tools_tests:generate_assets_declaration_test up-to-date:
  bazel-bin/tests/tools_tests/generate_assets_declaration_test
INFO: Elapsed time: 0.134s, Critical Path: 0.04s
INFO: 2 processes: 2 linux-sandbox.
INFO: Build completed, 1 test FAILED, 2 total actions
//tests/tools_tests:generate_assets_declaration_test                     FAILED in 0.0s
  /home/jamison/.cache/bazel/_bazel_jamison/04f084c324ba0be0b9506e8091939f14/execroot/buildifier_prebuilt/bazel-out/k8-fastbuild/testlogs/tests/tools_tests/generate_assets_declaration_test/test.log

INFO: Build completed, 1 test FAILED, 2 total actions

Yea, unfortunately this script requires it https://github.com/keith/buildifier-prebuilt/blob/b02049d666952d3bb07c45aa0bcd56d90766dd76/tools/generate_assets_declaration.sh#L34-L36

ah there is also a small issue

should be fixed if you have it installed, otherwise please let me know!


chore: deploy demo to surge.sh

Travis automatic deployment: https://101-pr-glimpse-cognitedata.surge.sh

@rumeshwick not sure what's better for you. should I just merge, or you guys will do it yourself?

@polomani i will merge this

@rumeshwick not sure what's better for you. should I just merge, or you guys will do it yourself?

I will merge this


Update obsolete link in network-flow-visibility.md

Signed-off-by: Quan Tian<EMAIL_ADDRESS>Fixes #2917

/skip-all

/test-integration

/test-integration


db migration from 1.24 to 2.x without going via 2.0.0 causes db corruption

Hi,
Bug description
After updating portainer from 1.24.1 to 2.1.1 (it should be 1.24.1 -> 2.0.0 -> 2.1.1) i have an error displayed when i access to the dashboard : https://[portainer]:9000/#!/1/docker/dashboard
This error is :
"Failure
Cannot read property 'length' of null"
It doesn't stuck me but maybe something went wrong during migration process.
I already managed this point : https://github.com/portainer/portainer/issues/4422
Expected behavior
No error displayed
Portainer Logs
2021/04/09 06:22:40 Instance already has defined endpoints. Skipping the endpoint defined via CLI.
2021/04/09 06:22:40 server: Reverse tunnelling enabled
2021/04/09 06:22:40 server: Fingerprint a5:cb:f3:ba:db:2c:69:b1:14:86:39:49:3e:55:5d:89
2021/04/09 06:22:40 server: Listening on <IP_ADDRESS>:8000...
2021/04/09 06:22:40 Starting Portainer 2.1.1 on :9000
2021/04/09 06:22:40 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]
Steps to reproduce the issue:

Connect to portainer
Select Primary Endpoint
Click to Dashboard Menu
See error : Failure \n Cannot read property 'length' of null

Technical details:

Portainer version: 2.1.1
Docker version (managed by Portainer): 20.10.5
Platform (windows/linux): Debian 10
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker stack deploy --compose-file=portainer-agent-stack.yml portainer
Browser: Chrome
Use Case (delete as appropriate): Using Portainer as Dev Envrionment
Have you reviewed our technical documentation and knowledge base? Yes

Additional context
Everything else seems to work fine

The compose file :
`version: '3.2'
services:
agent:
image: portainer/agent
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /var/lib/docker/volumes:/var/lib/docker/volumes
networks:
- agent_network
deploy:
mode: global
placement:
constraints: [node.platform.os == linux]
portainer:
image: portainer/portainer-ce
command: -H tcp://tasks.agent:9001 --tlsskipverify
ports:
- "9000:9000"
- "8000:8000"
volumes:
- nfs-portainer-data:/data
networks:
- agent_network
deploy:
mode: replicated
replicas: 1
placement:
constraints: [node.role == manager]
networks:
agent_network:
driver: overlay
attachable: true
volumes:
nfs-portainer-data:
driver_opts:
type: "nfs"
o: "addr=<IP_ADDRESS>,nolock,soft,rw"
device: ":[address]/Portainer/"`

@jpoupee Could you please try and clear out the browser cache, Also is it possible you could try another browser as well and let me know the results please.

@coop59 I can confirm this, it is persistently happening on dashboard since upgrade to 2.0 No amount of standard troubleshooting makes it go away and all user are experiencing it. Just upgraded to 2.5.1 and it still pops.

Hi
pl try on incognito mode, and also share the inspect screenshot

Same effect in incognito mode

Please, accept that all reasonable browser solutions were already attempted. Similar error happens to ALL our users across major browsers, MacOS and Linux, on freshly installed machines too. Firefox:

Safari:

All on dashboard load, every other "page" works alright.
Console log in Chrome incognito

I can record you a HAR file, if needed.

Hello @ZVilusinsky,
    I will take a look at this later this afternoon. I will get back to

you as soon as possible. Is there a particular reason you haven't upgraded
to 2.5.1?
On Wed, Jun 23, 2021 at 3:36 AM ZVilusinsky @.***>
wrote:

Same effect in incognito mode
[image: image]
https://user-images.githubusercontent.com/47591967/122972961-fe4ad300-d390-11eb-9f8b-6a2250d51aa2.png
Please, accept that all reasonable browser solutions were already
attempted. Similar error happens to ALL our users across major browsers,
MacOS and Linux, on freshly installed machines too. Firefox:
[image: image]
https://user-images.githubusercontent.com/47591967/122974013-2424a780-d392-11eb-96ca-5010e6d4a240.png
Safari:
[image: image]
https://user-images.githubusercontent.com/47591967/122973444-86c97380-d391-11eb-8290-f2f1e48874b9.png
All on dashboard load, every other "page" works alright.
Console log in Chrome incognito
[image: image]
https://user-images.githubusercontent.com/47591967/123055555-5374fc00-d406-11eb-98a1-bbe464081f74.png
I can record you a HAR file, if needed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/4975#issuecomment-866604592,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGNDERRCMGB42KIS4S6YTX3TUGFG3ANCNFSM42UK7RGA
.

--
Michael A Cooper
Linux Certified
Zerto Certified
http://www.coopfire.com

@coop59 not sure where you get I did not upgrade to latest, I literally wrote I just did that :)

Just upgraded to 2.5.1 and it still pops.

Right here -> Re: [portainer/portainer] Portainer 2.1.1 (updated from
1.24.1) :9000/#!/1/docker/dashboard - Failure cannot read property 'length'
of null (#4975)
On Wed, Jun 23, 2021, 9:27 AM ZVilusinsky @.***> wrote:

@coop59 https://github.com/coop59 not sure where you get I did not
upgrade to latest, I literally wrote I just did that :)
Just upgraded to 2.5.1 and it still pops.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/4975#issuecomment-866834957,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGNDERQ7K77WSPKEN3IGFC3TUHOLHANCNFSM42UK7RGA
.

It says 2.1.1 we ate at 2.5 1
On Wed, Jun 23, 2021, 9:27 AM ZVilusinsky @.***> wrote:

@coop59 https://github.com/coop59 not sure where you get I did not
upgrade to latest, I literally wrote I just did that :)
Just upgraded to 2.5.1 and it still pops.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/4975#issuecomment-866834957,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGNDERQ7K77WSPKEN3IGFC3TUHOLHANCNFSM42UK7RGA
.

I am so sorry I missed, let me work on it and I will get back to you.
On Wed, Jun 23, 2021, 9:27 AM ZVilusinsky @.***> wrote:

@coop59 https://github.com/coop59 not sure where you get I did not
upgrade to latest, I literally wrote I just did that :)
Just upgraded to 2.5.1 and it still pops.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/4975#issuecomment-866834957,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGNDERQ7K77WSPKEN3IGFC3TUHOLHANCNFSM42UK7RGA
.

That was the original poster :) I just used the topic, since it already existed with (from my point of view) the same problem.

Got ya no problem, I will try to get you squared away.....
On Wed, Jun 23, 2021, 9:50 AM ZVilusinsky @.***> wrote:

That was the original poster :) I just used the topic, since it already
existed with (from my point of view) the same problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/4975#issuecomment-866852902,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGNDERQPRFBMZ2NUMUZMIJ3TUHRARANCNFSM42UK7RGA
.

@ZVilusinsky I am looking in to this now just so you know.

Hello ZVilusinsky,
      May I get  the logs from Portainer and Agent Containers?

Thanks,
On Thu, Jun 24, 2021 at 6:20 PM Michael Cooper @.***>
wrote:

@ZVilusinsky https://github.com/ZVilusinsky I am looking in to this now
just so you know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/4975#issuecomment-867990927,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGNDERSHYOCJENYSXOLTUM3TUOVSTANCNFSM42UK7RGA
.

--
Michael A Cooper
Linux Certified
Zerto Certified
http://www.coopfire.com

Sure, though there is nothing really interesting in them. Agents last logs are from 21.6. (a network incident)
2021/06/21 09:38:36 http error: An error occured during websocket exec hijack operation (err=websocket: close 1000 (normal): websocket: close 1005 (no status)) (code=500) 2021/06/21 09:38:36 http: response.WriteHeader on hijacked connection from github.com/portainer/agent/vendor/github.com/portainer/libhttp/error.writeErrorResponse (error.go:37) 2021/06/21 09:38:36 http: response.Write on hijacked connection from encoding/json.(*Encoder).Encode (stream.go:227)
2021/06/21 11:53:07 http: TLS handshake error from <IP_ADDRESS>:58160: EOF 2021/06/21 11:53:07 http: TLS handshake error from <IP_ADDRESS>:58162: EOF
2021/06/21 09:36:57 websocketproxy: Error when copying from backend to client: websocket: close 1006 (abnormal closure): unexpected EOF 2021/06/21 09:38:53 websocketproxy: Error when copying from backend to client: websocket: close 1006 (abnormal closure): unexpected EOF 2021/06/21 10:34:47 http error: Unable to proxy the request via the Docker socket (err=context canceled) (code=500)
and Portainer log is just the same token info as console.
2021/06/22 10:51:23 Migrating database from version 25 to 27. 2021/06/22 10:51:23 Instance already has defined endpoints.
Given the error name across browsers, it seems that some tag list is null (maybe this?

/api/tags )and Portainer does not expect that.

The 2.0 release added endpoint tags information to the dashboard: https://github.com/portainer/portainer/issues/4218
Which added this code:
https://github.com/portainer/portainer/blob/d2404458ead60adefb054cf155e5fc35f2fe2bf2/app/docker/views/dashboard/dashboardController.js#L73
So it might have something to do with that /api/tags call.
Can you try the following workaround?
Create an endpoint tag and add that to your endpoint:

Does that remove the error from the dashboard?
What if you remove the tag afterwards?

@huib-portainer Tried now, was stopped kinda halfway through. I was able to create tags no problem, but when I tried to select them on endpoint details, nothing happened.

Compose file, should you see something that might be an issue.

version: '3.4'
networks:
agent_network:
driver: overlay
attachable: true
proxy_net:
external: true
services:
portainer:
image: 'portainer/portainer-ce:2.5.1'
command: '-H tcp://tasks.agent:9001 --tlsskipverify'
ports:
- '888:9000'
volumes:
- '/data/infra/portainer:/data'
- '/etc/localtime:/etc/localtime:ro'
labels:
elastic.index.rollover: infra
networks:
- agent_network
- proxy_net
deploy:
labels:
traefik.docker.network: "proxy_net"
traefik.port: "9000"
traefik.frontend.rule: $TRAEFIK_FRONTEND_RULE
traefik.protocol: http
resources:
limits:
cpus: '0.5'
memory: 256M
reservations:
cpus: '0.05'
memory: 128M
update_config:
delay: 30s
monitor: 60s
order: start-first
failure_action: pause
parallelism: 1
placement:
constraints:
- node.role == manager
- node.labels.nodeploy != true
restart_policy:
condition: any
window: 60s
delay: 30s
agent:
image: 'portainer/agent:1.6.1'
environment:
# REQUIRED: Should be equal to the service name prefixed by "tasks." when
# deployed inside an overlay network
- AGENT_CLUSTER_ADDR=tasks.agent
volumes:
- '/var/run/docker.sock:/var/run/docker.sock'
- '/var/lib/docker/volumes:/var/lib/docker/volumes'
- '/etc/localtime:/etc/localtime:ro'
labels:
elastic.index.rollover: infra
networks:
- agent_network
deploy:
mode: global
resources:
limits:
cpus: '0.5'
memory: 512M
reservations:
cpus: '0.05'
memory: 128M
update_config:
delay: 30s
monitor: 60s
order: start-first
failure_action: pause
parallelism: 1
restart_policy:
condition: any
window: 60s
delay: 30s

@ZVilusinsky in your endpoint details, can you select that test tag and then click on Update endpoint? That should set the tag for the endpoint.
Finally, navigate to the Dashboard screen to see if that error still occurs or not.

@huib-portainer That's the weird part where nothing happens - it does not get selected on click. This pops up in the console, sorry, should have included it yesterday.

If I interpret it correctly (js is not my strong suit), it seems the tag list of the endpoint is null/not existing, so function calls on it are failing.

This pops when I try the same tag again second time. It clears on page reload.

I see what you mean now. I was hoping that the problem could be prevented by assigning tags. Looks like something may have gone wrong during one of the upgrades in the past, as I haven't been able to reproduce it myself.
And I assume that when you try to set that tag against a Endpoint Group you'll have a similar problem?

fyi in the db I would expect something like

And I assume that when you try to set that tag against a Endpoint Group you'll have a similar problem?
Actually, no. I tried it now and on endpoint group, both unassigned and created were able to be updated with tags.

Looks like something may have gone wrong during one of the upgrades in the past, as I haven't been able to reproduce it myself.
I think so too, though it must be something systemic, because it happened an all of our swarms (10+) during updates to 2+, even the "youngest" one, few months old. Though, after reading the the OP again, it seems we both went from 1.24.1 to 2.1.1, I wonder if I inserted 2.0 as a middle step, if that would avert this. Should have still some swarm running on 1.X where I can test this. Might be some migration issue.

I'll get hands on boltbrowser and the db later, see if I can find something there.

@huib-portainer And we have a winner. Not skipping 2.0.0 prevents the error.

Downgrading to 2.0.0 is going to leave the database in it's current state unfortunately.
It will look at the database version number and determine that there's nothing to upgrade:
https://github.com/portainer/portainer/blob/8b80eb1731461ad897cad81cb5b4ed55d7a58d73/api/bolt/migrator/migrator.go#L333
The 2.0.0 upgrade itself:

sets some defaults in the settings
https://github.com/portainer/portainer/blob/8b80eb1731461ad897cad81cb5b4ed55d7a58d73/api/bolt/migrator/migrate_dbversion24.go#L22

set stacks statuses
https://github.com/portainer/portainer/blob/8b80eb1731461ad897cad81cb5b4ed55d7a58d73/api/bolt/migrator/migrate_dbversion23.go#L27

So it isn't obvious to me why that would have an impact on the tags to be honest.
However, the issue around the tag metadata itself could have existed before 2.0.0, but just not manifest itself, because from 2.0.0 we load that information in the Dashboard (which causes the error to be shown). And for instance the upgrade to version 1.24.0 did make some changes to the tags in the database.
But I do wonder what happens if you assign the endpoint to the endpoint group that has a tag assigned? Does the error in the Dashboard screen still happen then?

But I do wonder what happens if you assign the endpoint to the endpoint group that has a tag assigned? Does the error in the Dashboard screen still happen then?

Yes, it does, as I said, I tried both unassigned group and created

Which is kinda weird since I can actually see the list in inspect

Ah, yeah that's what I was going for. I was hoping that would prevent the error from happening.
Sounds like you may have to give boltbrowser a go to have a peek after all.

I'll see if I can get some time tomorrow or day after between the regular explosions. Was just tagged in a priority task for Nexus, yay me.

Ticket update by Michael Cooper<EMAIL_ADDRESS>Hello,
Did you get this taken care of? Let me know please so we can get you taken
care of.
Thanks,
Michael

Not as of yet. There seems to be a way to avoid this, but not a fix for already migrated PT. We've had a public holidays here this week, I hope to have time to dive into the database file on Monday.

Okay let me know when you do So I can be ready to help if needed.
Thanks,
On Thu, Jul 8, 2021 at 10:00 AM ZVilusinsky @.***>
wrote:

Not as of yet. There seems to be a way to avoid this, but not a fix for
already migrated PT. We've had a public holidays here this week, I hope to
have time to dive into the database file on Monday.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/4975#issuecomment-876464917,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGNDERQ6KHWDNABNLLDEPTTTWWVQFANCNFSM42UK7RGA
.

--
Michael A Cooper
Linux Certified
Zerto Certified
http://www.coopfire.com

Well, spent evening digging through the db file to no avail. Nothing seems to be amis, I even experimented with changing the version number and deleting entries to trigger migrations again. Sadly, changing to version 24 and deploying 1.24.1 worked, no error, but after upgrading to 2.0 and later the error shows again. So I am kinda baffled what list it's actually trying to read into UI.
Thinking about next steps, I could sanitise the db of users and stuff, and send it to you if you can find something. Or if you can think how to effectively export and import users (really don't want to deal with 50+ accounts manually), fresh deploy might work that way. Or just live with the error message.

let me talked to the gusy and see what is the next steps and I will get back with you as soon as I can.
Thank you for that info and your time, I do aprpeciate it.
Michael

From: ZVilusinsky @.>
Sent: Tuesday, July 13, 2021 8:05 AM
To: portainer/portainer @.>
Cc: Michael Cooper @.>; Comment @.>
Subject: Re: [portainer/portainer] Portainer 2.1.1 (updated from 1.24.1) :9000/#!/1/docker/dashboard - Failure cannot read property 'length' of null (#4975)
Well, spent evening digging through the db file to no avail. Nothing seems to be amis, I even experimented with changing the version number and deleting entries to trigger migrations again. Sadly, changing to version 24 and deploying 1.24.1 worked, no error, but after upgrading to 2.0 and later the error shows again. So I am kinda baffled what list it's actually trying to read into UI.
Thinking about next steps, I could sanitise the db of users and stuff, and send it to you if you can find something. Or if you can think how to effectively export and import users (really don't want to deal with 50+ accounts manually), fresh deploy might work that way. Or just live with the error message.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/portainer/portainer/issues/4975#issuecomment-879029760, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABF2ZF6J3REKWNTCQRLDFV3TXQTXPANCNFSM42UK7RGA.

Maybe you could add an endpoint that points to the same environment as the one that has the dashboard issue. See if that solves it. You will need to set any access control on it again and associate any stacks from the old endpoint to the new endpoint (for more details see https://github.com/portainer/portainer/issues/4397).
Then after a while when all is stable you can decide to remove the old endpoint.
(Note that you can create a Portainer Backup from the Settings page)
And if you decide to start with a new instance of Portainer, consider configuring Portainer to use OAuth instead.
(that will allow you to do other cool things as well if you ever need it, e.g. the next version of the Business Edition can sync Teams in Portainer with Group memberships defined in the OAuth provider)

Hi!
We have two docker swarm clusters. The "old" one from the earlier v1.2x times, upgraded in multiple steps to 2.6.2. And a "new" one fresh initialized with V2.6.1
After digging around with the browser debug console I compared the portainer bolt DB and found this difference:
First 270 chars and last 100 chars of database (endpoints) - "old" swarm:
{"Id":1,"Name":"docker-old","Type":2,"URL":"tcp://tasks.agent:9001","GroupId":3,"PublicURL":"","TLSConfig":{"TLS":true,"TLSSkipVerify":true},"Extensions":[],"AzureCredentials":{"ApplicationID":"","TenantID":"","AuthenticationKey":""},"TagIds":null,"Status":1,"Snapshot
-CUT-
agementFeatures":true},"LastCheckInDate":0,"AuthorizedUsers":[4],"AuthorizedTeams":[1,2],"Tags":[]}
First 270 chars and last 100 chars of database (endpoints) - "new" swarm:
{"Id":1,"Name":"docker-new","Type":2,"URL":"tcp://tasks.agent:9001","GroupId":3,"PublicURL":"","TLSConfig":{"TLS":true,"TLSSkipVerify":true},"Extensions":[],"AzureCredentials":{"ApplicationID":"","TenantID":"","AuthenticationKey":""},"TagIds":[],"Status":1,"Snapshots":[{"T
-CUT-
mentFeatures":false},"LastCheckInDate":0,"AuthorizedUsers":null,"AuthorizedTeams":null,"Tags":null}
@huib-portainer:
TagIds and Tags values are inverted from old to new version. Maybe that's the reason for this error?
Tom

I think its fair to consider this reproduced :)

I wonder if this is an example where it would help for our backups to be to yaml / json, allowing editing and re-use, and then import from that.

Just wanted to confirm, that using boltbrowser and manually editing TagIds":null -> TagIds":[] and Tags":[] -> Tags":null on environment fixes the persistent error notice.
I guess it is the only way, since no version update up to date cleared it.

Just a heads up that I ran into this same problem, but I'm pretty sure I went from 1.24.0 -> 1.25.0 -> 2.0.1 -> 2.17.1.  I had to use the boltbrowser and do this same operation.
I have another 1.24.0 portainer env to upgrade, and I will try again, going from 1.24.0 -> 2.0.0 to see if that works and avoids this problem.


[Feature] Disable Features on Low Power Mode

It would be great if there was a global option, per widget option to turn off the tilt, or sensor-based tilt on low power mode to preserve the battery, thank!

@SethuSenthil hi~
If you want to turn off the sensor in low power mode,
You can configure TiltConfig -> enableGestureSensors to turn off the sensors completely.
Tilt(
  TiltConfig: TiltConfig(
    enableGestureSensors: false,
  ),
  child: ......
)


Fix for 1.17.0

As title. The game developers change the field BeatmapData.cuttableNotesType to BeatmapData.cuttableNotesCount in 1.17.0. I think this is the only place where it breaks. Other than this change, I just bumped the versions.
Since I don't think I can get PrivateKeys.cs file, I can't build the mod from source. In order to test the changes, I edited the dll in dnSpy and recompiled it. It is working as far as I can tell.

BeatSaviorData.zip
This is the edited file, if anyone want to use it for now.
I only changed BeatmapData.cuttableNotesType to BeatmapData.cuttableNotesCount.


Upload simply returns 502 Something Went Wrong

Platform
This bug report concerns: (select all that apply)

[ ] Client
[x] Server

Details
Trying to upload new map through BeatSaver results in 502, and the only info I get in the UI is the message: "Beatsaver ZIP: Something went wrong! Try again later." No idea what the issue is (maybe my ZIP file?) But I have no idea how to figure out what the issue is.

Reproducing the Problem
Attempt to upload the new map through beatsaver reloaded. I would expect to upload to process, and if there was a problem to tell me what the problem is (or at least link me to a guide). A 502 seems like a server/gateway issue, so if this is unrelated to this repo itself (and on the implementation) then disregard and close this PR.

They have troubles with servers since some days, I think they are currently trying to solve it.

We waiting for the fix ... it's since 12 December 2020 but Yesterday someone upload a map ...

This codebase does not serve any 502 errors on upload, this problem is upstream and relies on the people running beatsaver.com to solve.

@lolPants I suspected so but just wanted the clarification. Thanks 👍


extract clusterOpts for readability

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: utako
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@utako: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
f1df6a9bfccc5f324d5ad35783b70c753f58b3ad
link
/test e2e-simpleTests-master

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram, utako
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@utako: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
bf06fd023c0a433e9af1a780e601387ba1123ae6
link
/test integ-security-k8s-presubmit-tests-master

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn, rshriram, utako
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [howardjohn,rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test integ-security-k8s-presubmit-tests-master

@utako: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
bf06fd023c0a433e9af1a780e601387ba1123ae6
link
/test integ-security-k8s-presubmit-tests-master

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

/test integ-security-k8s-presubmit-tests-master

@utako: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
bf06fd023c0a433e9af1a780e601387ba1123ae6
link
/test integ-security-k8s-presubmit-tests-master

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

Tests seem stuck?
/test all

@utako: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
bf06fd023c0a433e9af1a780e601387ba1123ae6
link
/test integ-security-k8s-presubmit-tests-master

prow/integ-pilot-local-presubmit-tests.sh
bf06fd023c0a433e9af1a780e601387ba1123ae6
link
/test integ-pilot-local-presubmit-tests-master

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

/test integ-pilot-local-presubmit-tests-master
Infra flake, it says it passed but reported failure? https://k8s-gubernator.appspot.com/build/istio-prow/pr-logs/pull/istio_istio/14345/integ-pilot-local-presubmit-tests-master/939


Run scheduled benchmark test on self-hosted runner

Description
This PR fixes https://github.com/layer5io/meshery-smp-action/issues/38, implements running scheduled benchmark test on self-hosted runner.
There are two method Scheduled benchmarking test can be triggered:
Manual test: we can trigger the test by giving specific test configurations (load-test, soak-test), then the matrix will be tested.
Scheduled test: the matrix test will run everyday.
There are three steps for scheduled benchmarking test like configurable benchmarking test:

Create CNCF CIL machines and register them as github self-hosted runners
Install Kubernetes, Service mesh and meshery. Then run benchmarking tests.
Destroy machines and delete self-hosted runners.
Workflows:

Github self-hosted runners:

CNCF CIL machines:

Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

This PR also fixed https://github.com/layer5io/meshery-smp-action/issues/21, the names of  test profile, machines, and runners will not contain .yaml

@hershd23 @navendu-pottekkat  @leecalcote  Can you review and give any comments? Thanks.

Great work @gyohuangxin. I have made one comment.
I have one more thing to ask, the manual and scheduled runs reuse almost all the code, what is the reason for having another copy entirely for scheduled? Is there any difference in logic that I am unable to see?

Thanks for your comments, the matrixs are different between manual and scheduled runs. And I think it's hard to reuse codes from anyone of them because the event types are also different.

Excellent. 😄


Implement bytes.splitlines()

Refs: #38
Implementation of bytes.splitlines() with tests.
Also fixes a couple of syntax problems discovered in microbenchmarks,py

Hi there! It looks like this PR might be dead, so we're closing it for now. Feel free to re-open it if you'd like to continue, or think about directing your efforts to https://github.com/beeware/briefcase or https://github.com/beeware/toga. Both of these have more active development right now. 😄


fix(show-more): should hide button when show more is not available

As noticed by @timkelty in #2160, showMore button should not be rendered
if there are not enough items to display based on the limits. With the
new connector API, this means that we should add a new parameter to
the renderer to give the information that this button should be
displayed.
fixes #2160
http://faithful-anger.surge.sh/?query=Canon - PowerShot SX720 HS 20.3-Megapixel Digital Camera - Red&idx=instant_search&p=0&dFR[brand][0]=Canon&hierarchical[hierarchicalCategories.lvl0][0]=Cameras %26 Camcorders&nR[popularity][>%3D][0]=0&is_v=2
Check the menu widget and the collapsible refinement list.

Great 💯  !


Fixups

Move the IHttpMessageHandlerBuilderFilter in the samples into its own class so it reads better in the README snippet.
Sort the using statements.
Remove redundant suppressions.
Updates to new workflow to make consistent with the build workflow.

Codecov Report

Merging #330 (73e4980) into main (f84b6e1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #330   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           16        16
  Lines         1128      1128
=========================================
  Hits          1128      1128

Flag
Coverage Δ

linux
100.00% <ø> (ø)

macos
?

windows
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f84b6e1...73e4980. Read the comment docs.


text file of database doesn't work???????

what about the database structure ? , you provided the text file of database but that doesn't work. so can you share the .sql file of the project..

Hi ,
This project no longer in maintenance so if you want database then you have
to payout $100.
Let me know if you want.
Thanks
On Wed, Apr 3, 2019 at 5:12 PM abhijeet3486<EMAIL_ADDRESS>wrote:

what about the database structure ? , you provided the text file of
database but that doesn't work. so can you share the .sql file of the
project..
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Aksaxena/mlm/issues/4, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEf3HIPdOB4AmpAmTI054tQstnEMLvcGks5vdJOmgaJpZM4caTHr
.

--
Alok kumar Saxena
Software Engineer
Mob:7061128990
skype:aksaxena878
(Every body can not do every thing but every body can do some thing)


sym-link rust-nightly-version

Similar to what was done in #467 for the proto files, this adds a symlink to the rust-nightly-version in apps and shared that use it in their build.rs script. This fixes rust-analyzer which runs from the workspace root and fails to find these from the previous relative path ../rust-nightly-version.

Nvm, this doesn't help. The issue actually seems to be with the path to .proto - it looks like the rust-analyzer doesn't follow symlinks


Make duration not required

Fixes #2274
Reopening this branch since there is a bug with current forms not working with their change.
TypeError
unsupported operand type(s) for &: 'NoneType' and 'bool'

https://github.com/HyphaApp/hypha/blob/220edd813c5efab597203758cbf6bd625451e99c/hypha/apply/stream_forms/models.py#L94

@Parbhat Needed to revert this since current forms and submissions did not work. Bad testing on my side.
Current forms only needed a resave to start working but for all submitted submissions that is not an option.


[WIP] Add section on Eclipse in the implementation chapter

This will be moved to the discussion instead.


Enter not triggering on root menu

Run app
Press Down
Press Enter

Expected: New window to show
Observed: Nothing happens
Ctrl+N still works.  Probably there was a change in key handling that is causing this or some new guard statement in global handlers in TGD.

Fixed in 4d710a2


JOSS: Add  Issue templates

If this repo will be used by "biomechanics researchers and clinicians with a limited mathematical background", we'll need to guide them properly
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
cc https://github.com/openjournals/joss-reviews/issues/3490

Addressed in ae753f020cfc80696ee74e28224fb259153975ef.


ignore DNSPolices in the spoke if it is a multi-cluster gateway managed by a hub

What
It is possible to create DNSPolicies in the hub and the spoke. This could trip up a user and cause unexpected results where two different controllers were trying to manage the same dns records.
In order to prevent this, if the gateway is a "multi-cluster" gateway instance then we should use some form of label to identify this (one may already exist). Any policy controller on the spoke should then not reconcile a DNSPolicy targeting this gateway and should report an error in the policy status :  "DNSPolices for multi-cluster gateways must be created in the hub cluster"

This issue is stale because it has been open for 60 days with no activity.

This issue is stale because it has been open for 60 days with no activity.

This issue was closed because it has been inactive for 30 days since being marked as stale.


WikiLinks support?

Hi! I'm looking for the WikiLinks support (links within two square brackets, e.g. https://python-markdown.github.io/extensions/wikilinks/). Does this library support it, via plugin maybe?
If it is not supported, I do not mind to implement it. Could you maybe guide me a bit on what would be the right approach?
Kind regards,
Alex

Hi! I'm looking for the WikiLinks support (links within two square brackets, e.g. https://python-markdown.github.io/extensions/wikilinks/). Does this library support it, via plugin maybe?

Not that I'm aware of.

If it is not supported, I do not mind to implement it. Could you maybe guide me a bit on what would be the right approach?

I would start with an existing similar parser like the LinkInlineParser but Wikilinks should be simpler in the end (no image support, no special link rules as in regular links).

This feature would be great for parsing Obsidian notes.
No pressure, just wondering, any development or plans?

As the topic starter, I feel that I need to inform you that I will not proceed with it further because I no longer use wikilinks. The name clashes in the large knowledge base have become too much of a nuisance.

I would also love this feature... very useful for Dendron workspaces.
@alex-netkachov FYI, Dendron solves the namespacing issue using hierarchical dot notation, e.g. [[languages.c-sharp]] is distinct from [[tags.c-sharp]]

Describe the basic specification for this.
Take a phrase in your document, e.g. cheese on toast
You add double square brackets around it, e.g. [[cheese on toast]]
It becomes an  in the rendered document, with the href set to cheese_on_toast ?
What are the rules to slugify the phrases? How do you deal with punctuation?
Just trying to flesh it out. I'm using markdig for a wiki right now, but I'm forcing the users just to make full links because I've not got it smart enough to do it wiki-style yet.

@djradon That's a format I've not seen before for "Wiki" style links. The original wikis used a strange CamelCaseFormat like that to create links, which clearly isn't very readable for normal humans. The link at the top of this thread, which I finally remembered to check out, uses basically the same format as WikiMedia, which is close to ideal as it allows spaces and punctuation in links and then does its best to slugify them in a way where they end up looking often identical to the original text.
The one I decided on for my wiki allows spaces in the text, but uses a hyphen instead of an underline in the link, and lower-cases everything, just because that's my personal preference for links.
I'm hard-pressed to see the use case for the one in your post -- is there a specific reason you don't want spaces in the link text? Obviously it makes converting it to a filename even easier, but filenames actually are less restricted than URL slugs as they can more easily have spaces in them.

@QINGCHARLES My use case is for Dendron, which only allows dashes in filenames, and the wikilink corresponds directly to the filename (without the .md extension), see https://wiki.dendron.so/notes/90mrtp10ucyyvt60qekuj4y/. But supporting spaces would be fine, doesn't affect my use case.

Ah, that's a shame. I think the easiest way to fix that would be to swap the assignments in WikilinkParser.cs, lines 97-98.

Yes, it would be easy to modify your code @Temetra. I checked it out, very nice, thank you. We need more example extensions like this to learn from.


Undefined class Future in lib/src/runner.dart

The file is missing the import 'dart:async'; directive.
This means that pub global activate mono_repo currently exits with
Failed to precompile mono_repo:mono_repo:
file:///Users/philippschiffmann/.pub-cache/hosted/pub.dartlang.org/mono_repo-1.2.0/lib/src/runner.dart:36:3: Error: 'Future' expects 0 type arguments.
  Future<Null> runCommand(ArgResults topLevelResults) async {
  ^
file:///Users/philippschiffmann/.pub-cache/hosted/pub.dartlang.org/mono_repo-1.2.0/lib/src/runner.dart:36:16: Error: The return type of the method 'MonoRepoRunner::runCommand' is invalid-type, which does not match the return type of the overridden method (dart.async::Future<dart.core::Null>).
Change to a subtype of dart.async::Future<dart.core::Null>.
  Future<Null> runCommand(ArgResults topLevelResults) async {
               ^

on OS X with Dart Version 2.0.0.

@kevmoo - need to add the import and publish a +1. Probably don't want to bump the SDK constraint until 2.1.0 stable.
This happened because the SDK opened a very easy hole to fall in to allowing you to omit the import on newer SDKs and we typically work with dev versions locally.

I have a fix coming, @pschiffmann – excited you're using this package!

Thanks for the report, @pschiffmann – run pub global activate mono_repo again and you should be good to go!

This happened because the SDK opened a very easy hole to fall in to allowing you to omit the import on newer SDKs and we typically work with dev versions locally.

Now I'm a bit confused. I'm currently looking into Travis CI explicitly because it lets me validate that I don't accidentally violate my packages SDK constraints. The dartanalyzer task catches bugs like this one if you add stable as a language version to your mono_pkg.yaml, right?

if you add stable as a language version to your mono_pkg.yaml, right?

Right!

The dartanalyzer task catches bugs like this one if you add stable as a language version to your mono_pkg.yaml, right?

That's true for now. Once Dart 2.1.0 is released then adding stable won't help catch this. In order to be safe you'd need to add the specific lower bound from your pubspec.yaml SDK constraints as one of the versions to run against in CI. stable is a moving target.

You can always add 2.0.0 – or whichever stable version you like – to be
specific about a shipped version. These are not a moving target.
On Tue, Oct 9, 2018 at 3:31 PM Nate Bosch<EMAIL_ADDRESS>wrote:

The dartanalyzer task catches bugs like this one if you add stable as a
language version to your mono_pkg.yaml, right?
That's true for now. Once Dart 2.1.0 is released then adding stable
won't help catch this. In order to be safe you'd need to add the
specific lower bound from your pubspec.yaml SDK constraints as one of the
versions to run against in CI. stable is a moving target.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/mono_repo/issues/109#issuecomment-428375765,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCihiIeFQbopfdslpezuEnt0kb75CPks5ujSPfgaJpZM4XMUFP
.


Replace job status svgs with empty plot

Instead of the iconographic plot, show the regular viz in step 3. To be more precise, let's replace the step 3 here:

with the step 3 shown below

Some issues with this switch arose here: https://github.com/VEuPathDB/web-eda/pull/1577#issuecomment-1405591194

Looks good, now see an empty, greyed-out plot before setting up and running the 1st step


rename asg to mmi_bigram

Looks OK to me.
Motivation is that while, like ASG, we're jointly training the probs with the model, we actually use a different objective, chosen to keep the LM probabilistic.  So not sure that it makes sense to call it ASG, plus MMI has a much longer history.

Looks OK to me.
Motivation is that while, like ASG, we're jointly training the probs with the model, we actually use a different objective, chosen to keep the LM probabilistic.  So not sure that it makes sense to call it ASG, plus MMI has a much longer history.

Merging

Merging


Reset/clear history

Not really an issue, but more of a question that I didn't find answer to in the documentation. (or possibly a feature request)
Is there a way to reset the history?
I have the following scenario/use case:
Sometimes the user might reach a form directly (via URL), and in normal cases, the cancel button triggers a goBack(), but when they go there directly, the previous page might not be part of the app (even an empty tab, as an empty tab is considered a page) they will go back to that page instead and leave the app. But, if they request the form normally (reachable from more than one place), the cancel button works great and they go back to where they were.
I thought about checking for the history.length, and if it's less than 2 then just go to a specific route instead of the goBack().
However, that wouldn't work unless I manage to reset the history. How can I do that? Is it something this package can do (now or in the future) or it is something on browser level and cannot be accessed?
Thanks!

From MDN:

There is no way to clear the session history or to disable the back/forward navigation from unprivileged code. The closest available solution is the location.replace() method, which replaces the current item of the session history with the provided URL.

So probably cannot be done. If you confirm this, the issue is ready to be closed.

For others having similar scenarios:
I managed to workaround it by adding a boolean state after the history is imported and then check before going back if that boolean is set or not.
main.js
import { createBrowserHistory } from "history";
browserHistory = createBrowserHistory();
browserHistory.replace({ firstPage: true });

util.js
/**
 * Go back or redirect to URL
 * @param {{location: {firstPage: boolean}}} history History object.
 * @param {string} fallbackURL URL to redirect to if it is the first page.
 */
const goBack = (history, fallbackURL) => {
  if (!history.location.firstPage) {
    history.goBack();
  } else {
    history.push(fallbackURL);
  }
};

component_reachable_directly_by_URL.js
import { goBack } from "../util";

...

cancel() {
  goBack(this.props.history, "/route_to_redirect_to");
}

There's no way for us to programmatically reset the history stack (at least in a browser, in memory history this would be trivial). If you need to clear the history stack for some reason, I'd suggest you use window.location.reload().


[embedded] Mark basic-irgen-no-stdlib.swift as REQUIRES: swift_in_compiler

Otherwise the test fails when building with bootstrapping disabled.

@swift-ci please test


rxjs/rx no longer needed

When I install the component, I'm getting these errors:
Module '".../node_modules/rxjs/Rx"' has no exported member 'Observable'.
node_modules/ng2-combobox/src/combo-box.component.ts(2,21): error TS2305: Module '".../node_modules/rxjs/Rx"' has no exported member 'Subscription'.
In the code you have import { Observable, Subscription} from 'rxjs/Rx';.
As of Angular 6, it needs to be just ...from 'rxjs';

Mind providing a PR for us?

Fixed with PR #39
This is my first PR, so I hope I got it right.


Bkr 1115 Allow options-file to be configured via ENV

In order to run beaker acceptance tests unmodified behind a proxy, the host_env configuration needs to be externally settable (i.e. outside of the tests).   As this is passed in to beaker via the --options-file, it makes (made?) sense to use expose this runtime parameter.
When used in conjunction with BKR-1114 pull request, it is possible to do the following:
git clone https://github.com/puppetlabs/puppetlabs-inifile.git
cd puppetlabs-inifile
export BEAKER_options_file=~/beaker-proxy.cfg
export DOCKER_BUILDARGS="HTTP_PROXY=http://<IP_ADDRESS>:3128/ HTTPS_PROXY=http://<IP_ADDRESS>:3128/     http_proxy=http://<IP_ADDRESS>:3128/       https_proxy=http://<IP_ADDRESS>:3128/"
PUPPET_INSTALL_TYPE=agent BEAKER_debug=true BEAKER_set=docker/centos-7   bundle exec rake -v beaker

Where ~/beaker-config.cfg contains:
{
  :package_proxy => 'http://<IP_ADDRESS>:3128/',
  :host_env => {
    "http_proxy" => "http://<IP_ADDRESS>:3128/",
    "https_proxy" => "http://<IP_ADDRESS>:3128/",
    "HTTP_PROXY" => "http://<IP_ADDRESS>:3128/",
    "HTTPS_PROXY" => "http://<IP_ADDRESS>:3128/"
  }
}

Can one of the admins verify this patch?

@barrymw apologies for the huge delay looking at this. Looks good to me, I'll put it through testing, & hopefully we'll get this out soon for you.
@puppetlabs-jenkins test this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker-rspec_btc-intn-sys/44/

@puppetlabs-jenkins retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker-rspec_btc-intn-sys/46/

Not a problem @kevpl, I have been running with my mods up until now. Thanks for getting around to merging though!

@barrymw np! I'm pretty confident that your changes are fine & that we're having issues that we should resolve with our automation & shouldn't block merging on them. Since that's the case, I'll merge this now. Thanks for the addition!


Added a modal component to the project

Codecov Report

Merging #8 (ba89f84) into master (802b624) will increase coverage by 0.92%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
+ Coverage   90.47%   91.39%   +0.92%
==========================================
  Files          13       15       +2
  Lines          84       93       +9
  Branches       18       20       +2
==========================================
+ Hits           76       85       +9
  Misses          8        8

Impacted Files
Coverage Δ

src/App.jsx
100.00% <ø> (ø)

src/components/pages/Home.jsx
100.00% <ø> (ø)

src/components/widgets/SanitizedHtml.jsx
100.00% <ø> (ø)

...mponents/widgets/blog-posts/BlogPostsContainer.jsx
83.33% <ø> (ø)

...widgets/blog-posts/blog-post-card/BlogPostCard.jsx
100.00% <ø> (ø)

src/components/widgets/editor/BlogEditor.jsx
84.09% <ø> (ø)

...ponents/widgets/editor/DisplayMarkupFromEditor.jsx
100.00% <ø> (ø)

src/components/widgets/layout/Footer.jsx
100.00% <ø> (ø)

src/components/widgets/layout/Header.jsx
100.00% <ø> (ø)

src/components/widgets/layout/Layout.jsx
100.00% <ø> (ø)

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 802b624...ba89f84. Read the comment docs.


conduit-iconv-<IP_ADDRESS> missing hsiconv.h

conduit-iconv fails to build:
Configuring conduit-iconv-<IP_ADDRESS>...
cabal: Missing dependency on a foreign library:
* Missing (or bad) header file: hsiconv.h

I think you need to add hsiconv.h to your .cabal file.

https://github.com/fpco/stackage/pull/1016#issuecomment-161547653
I think this is a problem wherever this is tried to be built. Seems no iconv.h is available there. Can you confirm? What platform is this built on?

There is no .h file in the tarball.  I think it should be in c-sources.

Ah, that makes sense. Thanks!

Can you update here when you make a new release? :)

Done already, there's <IP_ADDRESS> on hackage now

Thank you!


Hamburger and minor changes

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
@pooranjoyb
[BUG] Filter not working in product #349
[BUG] Missing Burger Menu for routing in other pages #348
Fixes #349 #348 (issue)
Type of change
Please give a X on it which is applicable

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactor Code
[ ] A documentation update
[ ] Others(mentioned in the issue number)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Test A Describe here
Test B Describe here (if Requred)
Screenshots and Videos:
https://github.com/user-attachments/assets/a4eba937-001f-4284-97bd-0405cbb9122f
Give screenshots and video of the changes you made
Checklist:
Give a X on, which is applicable

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

Hey @dhruv8433 I can see 15commits here including the unmerged PR for Profile UI. Are you sure you're not adding them here?

Oh yes i forgot

i make another pr


Raidboss: Sohm Al (hard) dungeon package

Mostly standard, but unfortunately we can't do a timeline for boss 2. Gowrow works slightly differently from any other boss I've come across. It's all "count to 3":
Auto, auto, special
Unfortunately, the special attacks all have different timers, both in terms of when they resolve and in how long the animation blocks auto-attacks thereafter. This is further dependent on whether or not Gowrow has self-buffed.
All of this is to say that a timeline would not only be difficult, but also largely useless. The best we could really hope for is to sync to Volcanic Howl every time it comes up in the rotation, but that wouldn't gain us much. The most we can tell the user is "okay, a special of some kind is coming up". That's honestly not worth it, at least for now.
Separate from that, we're missing the Korean translations because I don't have that scripted nicely as I do the others. (API access is so much nicer than dealing directly with CSV, but CSV is the only option I know of for Korean right now.) I'm working through that, and if this hasn't been fixed by then I'll come back and take care of it.

Re: Gowrow.  It seems very similar to the cyclops boss in Amanesis Anyder.  Aren't the spawning of the explosive adds at a regular time, even if the individual attacks were not?

Leightonward is the boss with the spawning adds. Gowrow is "will the melee remember to get out and not get hit with the healing debuff THIS time?"

Leightonward is the boss with the spawning adds. Gowrow is "will the melee remember to get out and not get hit with the healing debuff THIS time?"

:innocent:
I thought there were spore pods and explosions? Maybe they're not targetable and calling them adds is a bit much.

No, Leightonward, the first boss, is the one that has those, hence the whole thing with me forgetting the syntax for "Spore Sac" vs "Small Spore Sac". Gowrow has only itself.

Haha, sorry, I apparently totally forgot how this dungeon works.  I watched a video, and I think this makes total sense to not have a timeline here.  Sorry for my bad memory, it's been a while.


My documentation tokens keep disappearing

For the second time today my documentation tokens have vanished, no plugin crash or anything, just gone… is there some kind of know issue here -    there are close to a hundred of these swatches and theyve all reverted their 3 linked values. The inspect shows no tokens applied to the objects.

And, any way to back them up? Im not inclined to remap them for a third time only for this to happen again :(

Not that I'm aware of, are you able to reproduce this? By reverted do you mean they're gone or have they reverted to what a main component was using?
Are you using the plugin solo or with other designers using it at the same time? Any pointers would be greatly appreciated 🙏

I will try to reproduce it if i can during the coming workdays.
Tokens were applied to instances, not the master. whilst working on other things in the documents I on two occasions noticed the instanced were initialized, and my nice dynamic values from documentation tokens were gone. I am unsure of exactly what triggered this, but i can think of a few things:

I 've experienced semi-frequent Figma plugin runtime error (i think it was… that red toast thing pops up in the bottom of the screen) alerts while working with Figma Tokens, requiring a restart of Figma in order to open Figma Tokens again in the same document.

I did make some minor adjustments to the main component, nothing i should thing would trigger a rest of overrides causing a loss of tokens, but i might be wrong.

On another note, some way of applying documentation tokens more quickly would be awesome, when i have eight series of 050, 100, 150, 200 etc colors and want to get 3-4 values for each swatch from doc tokens, thats a lot of manual work (specially if they reset :D )
Thanks again for a great plugin, really shapes the way we work with Figma now.

I am soloing atm, other designer will get read only eventually for refrencing purposes.

Thanks for the context, I'll try to keep an an eye on this and see if I can reproduce.

On another note, some way of applying documentation tokens more quickly would be awesome, when i have eight series of 050, 100, 150, 200 etc colors and want to get 3-4 values for each swatch from doc tokens, thats a lot of manual work (specially if they reset :D )

On that note: I recently published something for the Automator community that creates documentation layers for you really quickly, but I definitely want to have something like this in the plugin natively!

Got a link for your automation? I’ve yet to try that, pricing puts me a bit off until I see something I NEED 😅

Should be up at the automation.community soon, until then it's also here: https://github.com/six7/automator/blob/main/create-documentation.json

Thanks!

Been trying this out today, cannot get it to produce anything but an empty autolayout - are there any other plugins i need for it to work correctly? Also would it work with remote tokens? (Been trying on local ones just in case)

Perhaps this helps:
Basically, have a layer selected that serves as a template. Then, name layers according to what property should be set (e.g. __fill, __tokenValue)
https://user-images.githubusercontent.com/4548309/160466324-c5613c3f-73d9-49f5-8e8c-7c7503c71523.mp4

I haven't had any feedback like this - which is why I'm closing this issue. Let me know if it appears again.