Added a session mechanism.

Added a session mechanism. Session data is kept only in memory

Thanks for the contribution @ArtdSky? What's the use case for this API?
At a first glance I don't see why this should be part of the library rather than being just part of the specific bot app that requires this session mechanism.

hello @vjgarciag96!  Use case in dialogs where you want to save the user's answers. In my opinion, it is convenient if the API has the ability to keep some information from the user.  I was inspired by telegraf.js

I second @vjgarciag96 on that one, and since there has been no activity for more than a year, I'll close the PR as there is no final decision.
Anyway, I'm grateful for your change proposal @ArtdSky and looking forward to your future PRs


After configuring control unit, remote unit update may not be scheduled immediately

There were a lot of changes to scheduling, so most likely fixed.


Use standard deviation for indicator

A good idea to use standard deviation to calculate critical/warning range.

Now uses standard deviation.


macOS: if note is renamed changing only capitalization/case, then subsequent image pastes are failing

Test environment

macOS 14.5
Obsidian 1.6.5
Plugin 0.9.9

Reproduce steps

create new note, title=foo test (make sure to use all lower case)
paste an image to that note
now, rename the note to Foo Test (only changing case foo test→Foo Test)
paste another image

It will fail, with a similar message in the console:

If you then rename the note to Foo Test 2, all images will be renamed successfully.

Fixed in latest version, upgrade it and try again.

Yes! Thank you 🙏 🙏 !
New version is working well.


Improve comparison page

The current comparison page is very basic.
We should add more features:

[ ] Add support for sorting columns alphabetically
[ ] Add support for filtering each column by value
[ ] Improve padding and margin
[ ] Add filter for the minimum number of votes
[ ] Add checkbox for only showing open source tools (i.e. tool.proprietary === false)
[ ] Do you have more ideas?

If anyone finds the time to work on this, feel free to add a comment below and let us know what you're working on.
Thanks!

I will be working on this, also I will add an icon on the votes column that will show the number of Upvotes and downvotes

Some more details:

Sorting: Click on the Tool field or the Votes field and the entries will be sorted by that field
Example: https://autodesk.github.io/react-base-table/examples/sortable
Filtering: Click on the Category, Type, Tags, and License field and the
entries can be filtered by user input


Implement test_allow_volume_creation_with_degraded_availability_restore

Split original into two scenarios.
https://github.com/longhorn/longhorn/issues/1701

Currently, the two tests both failed.
The _restore failed from 2.2, by observation only 1 replica is found where expecting a total of 3 replicas(1 running, 2 stopped).
The _dr failed from 2.1 where the schedule condition stayed false.

The scheduling failed replicas somehow are marked as ERROR during the restore, which leads to unexpected test failures. I will check it later.

Rebased.

@shuo-wu Can you check the issue?

I just re-checked the test step. The failure of the tests is caused by the transient state. For restore/DR volumes, Longhorn will automatically and immediately attach the volume once it's created. The volume schedule condition will be false once the volume is attached/attaching. And the scheduling failed replicas will be cleaned up once Longhorn automatically detaches the volume after restoration complete. In brief, you need to:

Check the volume current state before verifying other fields.
Avoid checking the transient state

@shuo-wu thanks for the review and explanation.
I've removed the checks for failed replicas to bypass the transient state. However, tests are still failing.

No additional replica got scheduled after enable the second node. Observe that the restoration of additional replica starts when the volume gets attached near the end of the tests.
During restore, test _restore schedule condition stayed true, but test _dr stayed false.

Sometimes the replica scheduling of the restoring volume may take several seconds after enabling the 2nd node. And you may need to be careful of the race condition: the restore is complete before the scheduling success. But based on my manual test with Longhorn v1.1.0, it does work fine. BTW, you can find the restore status besides the rebuilding state in the engine for the newly scheduled replica since the rebuilding of a restore/DR volume is actually full restoration.
The scheduling condition of both DR volumes and restore volume is False during the restore. I am sorry for not pointing out that this wrong in the skeleton. Remember, the scheduling condition of a volume is always False if the node scheduling is not enabled and there is an unscheduled replica in the volume.

Here is the modified test skeleton for the restore volume part:
1. Disable scheduling for node 2 and 3.
2. Restore a volume with 3 replicas.
    1. Volume should be attached automatically and `Scheduled` is true.
    2. Only 1 replica becomes scheduled.
3. During the restore, enable scheduling for node 2. Then check the followings if the volume restore is still in progress:
    1. 1 additional replica of the volume will become scheduled.
    2. The restore status and the rebuild status for this newly scheduled replica.
    3. The scheduled condition is still false.
4. Wait for the restore to complete and volume detach automatically. Then check the followings:
    1. After the volume detached, the only unscheduled replica will be removed.
    2. The scheduled condition will become true.
5. Attach and wait for the volume.
    1. A new replica will be created with scheduling failure.
    2. The scheduled condition becomes false.

As for DR volumes, the main difference is that the scheduling condition will become true as long as all node scheduling is enabled and all replicas become running before activation.

Any update @c3y1huang ?

Any update @c3y1huang ?

Any update @c3y1huang ?

I've almost forgotten about this one, will come back to this later.

Any update @c3y1huang ?

I've almost forgotten about this one, will come back to this later.

Sometimes the replica scheduling of the restoring volume may take several seconds after enabling the 2nd node. And you may need to be careful of the race condition: the restore is complete before the scheduling success. But based on my manual test with Longhorn v1.1.0, it does work fine. BTW, you can find the restore status besides the rebuilding state in the engine for the newly scheduled replica since the rebuilding of a restore/DR volume is actually full restoration.

@shuo-wu I've tried again and observed the restore gets completed very quickly (~1 second), and the 2nd node replica never got scheduled, nor is the rebuilding. I guess this is the race condition you've talked about. I've tried to increase the backup to 1600MB and seeing the same result. Is this expected?

Hmmm... I just retied the test. Restoring 800MB~900MB data from the test NFS backupstore took 5~15s, which does not be able to guarantee the test always successful. Maybe we can remove the healthy/replica count check for the restore volume. As long as the data of the restored volume is correct, I will consider the test is passed.

Hmmm... I just retied the test. Restoring 800MB~900MB data from the test NFS backupstore took 5~15s, which does not be able to guarantee the test always successful. Maybe we can remove the healthy/replica count check for the restore volume. As long as the data of the restored volume is correct, I will consider the test is passed.

Seem the intermediate checks are hard to catch (couldn't in my case), I've modified tests to mostly only verify the expecting result.


hi, does the movenet.pth is trained or ported from tf?

I tried to run, but seems default config didn't fit pretrained weights under models:
Creating model...
Skip loading parameter backbone.body.6.conv.2.weight, required shapetorch.Size([56, 336, 1, 1]), loaded shapetorch.Size([32, 192, 1, 1]). If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Skip loading parameter backbone.body.16.conv.2.weight, required shapetorch.Size([280, 1680, 1, 1]), loaded shapetorch.Size([160, 960, 1, 1]). If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Skip loading parameter backbone.body.11.conv.1.0.bias, required shapetorch.Size([672]), loaded shapetorch.Size([384]). If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Skip loading parameter backbone.body.5.conv.2.bias, required shapetorch.Size([56]), loaded shapetorch.Size([32]). If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Skip loading parameter backbone.body.16.conv.2.bias, required shapetorch.Size([280]), loaded shapetorch.Size([160]). If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Skip loading parameter backbone.body.13.conv.2.weight, required shapetorch.Size([168, 1008, 1, 1]), loaded shapetorch.Size([96, 576, 1, 1]). If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Skip loading parameter backbone.body.3.conv.2.weight, required shapetorch.Size([40, 240, 1, 1]), loaded shapetorch.Size([24, 144, 1, 1]). If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.

any idea?

It's ported from tf directly. You may check the model definition. I think there's some inconsistency there.

@lee-man I just running instructions in your readme. Does it work out of box? On my side it's not.

@jinfagang Actually I am not very sure cus this repo is taken over by other guys later. I suggest that you may check the previous few commits. I am pretty sure that at some point this repo work out correctly.

Great! Thanks for your work. I will add the link in README later.


[Website] Features: missing items in list

Current State of the Meshery.io site
On this page, https://meshery.io/features, items are missing.

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Hey @leecalcote, can I work on this issue?

Sure @shailpujan88 go ahead. Take a look at https://layer5.io/pricing for content to be added.


Add location type filter to impact map and table

@alexeh thanks a lot for the review! I added the requested changes, tell me if it is better like this. Else we can look at the types details together, maybe come up with better solution..


Mod incompat. Crash on entering world

Caused by mixin incompat between TFL and Waystones
See https://github.com/TwelveIterationMods/Waystones/issues/674 for info

fixed in 1.3.5!


Srawm-listener -> Proxy

If I have:
  proxy:
    image: vfarcic/docker-flow-proxy
    ports:
      - target: 80
        published: 80
        protocol: tcp
        mode: host
      - target: 443
        published: 443
        protocol: tcp
        mode: host

Is it ok to have_
  swarm-listener:
    image: vfarcic/docker-flow-swarm-listener
    networks:
      - proxy
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - DF_NOTIFY_CREATE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/reconfigure
      - DF_NOTIFY_REMOVE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/remove

Now I get error from swarm-listener not when it tries to update proxy and it is maybe because i changed ports to host mode. I need this to log real ip addresses of web users.
Thank you for any help.

It will not work with the current config. Listener belongs to the network proxy but proxy doesn't. They cannot find each other using service names (as described in DF_NOTIFY_CREATE_SERVICE_URL env. var.). You'd need to change the proxy address in the listener to point to the IP of the node where the proxy is running. If you do that, your solution will not be fault tollerant. The moment that node dies, the communication will break. Even if you do that to solve the communication between the listener to the proxy, it would not work the other way around. The proxy would not be able to find the listener (they're not in the same network). On top of all that, the proxy would not be able to communicate with other services in your cluster.
Maybe it would make sense to reset the conversation and go back to the start. Can you please tell me what you're trying to accomplish?

If proxy is running in service network, it will report wrong ip for all sites. So all visitors seem to be coming from same ip. If it is running in host mode network, it is possible to get visitors ip for web analytics. This was in one discussion I found from web. I thought that I will run proxy in global mode, and use host networking. What I did not understood, is that communication between proxy and swarm listener changes.
Is there another way to forward real visitor ip adress to web container so that it can be used in web analytics?

Another strange thing that is now (I think because updated docker-flow-version) log messages like:
<EMAIL_ADDRESS>  | [WARNING] 315/201507 (248) : parsing [/cfg/haproxy.cfg:55] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
<EMAIL_ADDRESS>  | [WARNING] 315/201507 (248) : parsing [/cfg/haproxy.cfg:56] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
It does seem to work still. No changes has be done in docker compose of web containers. So they are like:
labels:
- com.df.notify=true
- com.df.distribute=true
- com.df.serviceDomain=tukoke.tek.fi
- com.df.port=8002
- com.df.redirectFromDomain=www.tukoke.fi,tukoke.fi
- com.df.httpsOnly=true

DFP works only with Overlay network which removes "real" IPs. There's no way around it (as far as I know). Alternative would be to publish ports of your services and let DFP forward requests without networking. That would have to apply even to DFSL>DFP communication. I think that downsides of such an approach are much bigger than benefits of having the "real" IP.
I'll correct the warning message. It should not affect how DFP works though.

Can I move proxy to swarm-listener communication to another network and let only 80 and 443 ports be in host mode? I think this way it should work?

I did preliminary testing and it seems to work like expected and is easy to set up. Currently I'll try to test letsencrypt with our wildchar certificate.

Can you add it to /docs directory in the repository and make a PR?

I do not promise I have time this week, but next week propably. This is my docker-compose if you want to see it:
version: "3.3"
services:
proxy:
image: vfarcic/docker-flow-proxy
ports:
- target: 80
published: 80
protocol: tcp
mode: host
- target: 443
published: 443
protocol: tcp
mode: host
networks:
- proxy
- proxy-conf
environment:
- LISTENER_ADDRESS=swarm-listener
- MODE=swarm
deploy:
replicas: 2
swarm-listener:
image: vfarcic/docker-flow-swarm-listener
networks:
- proxy-conf
volumes:
- /var/run/docker.sock:/var/run/docker.sock
environment:
- DF_NOTIFY_CREATE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/reconfigure
- DF_NOTIFY_REMOVE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/remove
deploy:
replicas: 1
networks:
proxy:
external: true
proxy-conf:
external: false

Closing due to inactivity. Feel free to reopen...


Connecting Projects

We need suggestions/solutions regarding connection between major projects and any related sub-projects. Projects we know are reoccuring every year for instance, how do we handle those (other than adding a new project everything). Research and suggestions are needed.
High Priority

More details required


[Feat] Render SVG from text input

Hi @csgoh, thank you for your work on processpiper.
It's the best OSS Diagram-as-Code solution for BPMN that I've found so far.
I have a feature idea that I believe would add value to the project.
I noticed that the render() function in text2diagram.py relies on PIL, while the SVGPainter class uses DrawSVG.
Then, I understand that currently there is no way to create an SVG diagram from text:

From Text
From Code

PNG
:heavy_check_mark:
:heavy_check_mark:

SVG
:x:
:heavy_check_mark:

Do you think the implementation of a text2SVGdiagram solution is feasible?

Hi @nhpf ,
Yep, I will add that to the next release. 😊

Hi @nhpf, I have just released v0.7.0. You can now save output to SVG by using the render() method. See the change logs in wiki for more information.

Thank you, @csgoh!
It works really well!


Register package

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/80625
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.6.0 -m "<description of version>" c8ef6d9817037b01f9dd30cea11c9002216eb46f
git push origin v0.6.0

Also, note the warning: This looks like a new registration that registers version 0.6.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


Implement kubeconfig rotation

Description
Changes proposed in this pull request:

Periodic secret rotation implemented
Forced secret rotation implemented
Statuses set for operations

Related issue(s)
#10

/retest

What should be taken into account during review:

Errors handling
Resilience: we must be sure that the controller is self healing
Unit tests should be reviewed
Unit test stability (it would be good to run it couple of times)
Force rotation scenario: there is update failure caused by the Kubebuilder cache


apps: copying  references to messages appears to be broken

Check the video for a reproduction of this issue:
https://user-images.githubusercontent.com/1195363/234759818-9c43471e-bbe7-44f9-b755-725dafb3e613.mov
I'm not able to copy references of notebook posts or gallery blocks as well.
Seeing this on Chromium Engine Version 112.0.5615.137
Edit: This is broken on Safari Version 16.4 (186<IP_ADDRESS>.23) as well:
https://user-images.githubusercontent.com/1195363/234760639-09a1dfbb-947e-449d-ab7d-9c1ab81850eb.mov

Are you still able to repro? I remember seeing this at some point but can't repro now.

I'm seeing this too on:
macOS Ventura 13.3.1
Arc Version 0.101.2 (38549) (Chromium Engine Version 112.0.5615.137)
Safari Version 16.4 (186<IP_ADDRESS>.23)

I'm still seeing this issue, when I check out devtools, I see this:


chore(proto): introduce rocketmq-apis as submodule

fix #460

Great job, it looks solid overall, and I left a comment.


Using .babelrc for Babel 6 plugins will interfere w/ add-ons/dependencies that use Babel 5

I'm trying to use a plugin (babel-plugin-transform-object-rest-spread) with the latest version of ember-cli-babel. Since it's not included as a preset in babel-preset-env, I'm forced to configure babel directly via .babelrc or package.json
According to Babel, it will search parent directories for a babelrc if it does not have one in its project dir. I am seeing this happening with some add-ons that are trying to use the plugin, which is a Babel 6 plugin, when the add-on is using babel v5.x.x, causing issues.
I was able to confirm by removing/replacing the .babelrc file

I need to update the docs for this (would love a PR to the README once you get it working). The basic gist is:
// ember-cli-build.js
// ember-cli-build.js
module.exports = function(defaults) {
  let app = new EmberApp(defaults, {
    babel: {
      plugins: [
        [require('babel-plugin-transform-object-rest-spread').default, /* any options needed for it */]
      ]
    }
  });

  return app.toTree();
}

FWIW, I do not believe we are allowing usage of .babelrc yet (if we are, I need to fix that 😉 )...

FWIW, I do not believe we are allowing usage of .babelrc yet (if we are, I need to fix that 😉 )...

Ya, as far as I know .babelrc stuff doesn't work correctly \w symlinks and npm linking and stuff, so ya... Not sure if we can ever quite support it (unless babel fixes this)

@rwjblue should it be this instead?
// ember-cli-build.js
module.exports = function(defaults) {
  let app = new EmberApp(defaults, {
    'babel6': {
      plugins: [
        ['transform-object-rest-spread', /* any options needed for it */]
      ]
    }
  });

  return app.toTree();
}

babel6 instead of babel
plugin referenced by name instead of required directly

@Turbo87 - babel6 is only needed for ember-cli < 2.13 (e.g. when ember-cli itself is still sharing the host apps babel configuration for its fallback transpilation).

Hm, found this issue, but cannot get this to work. This https://github.com/babel/ember-cli-babel/issues/134#issuecomment-296393640 I get:
TypeError: Cannot read property '__esModule' of undefined
    at Function.normalisePlugin (/Users/simonihmig/Projects/tlw/node_modules/babel-core/lib/transformation/file/options/option-manager.js:142:20)
    at /Users/simonihmig/Projects/tlw/node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
    at Array.map (native)
    at Function.normalisePlugins (/Users/simonihmig/Projects/tlw/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
    at OptionManager.mergeOptions (/Users/simonihmig/Projects/tlw/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
    at OptionManager.init (/Users/simonihmig/Projects/tlw/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
    at File.initOptions (/Users/simonihmig/Projects/tlw/node_modules/babel-core/lib/transformation/file/index.js:212:65)
    at new File (/Users/simonihmig/Projects/tlw/node_modules/babel-core/lib/transformation/file/index.js:135:24)
    at Pipeline.transform (/Users/simonihmig/Projects/tlw/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
    at Babel.transform (/Users/simonihmig/Projects/tlw/node_modules/ember-cli-babel/node_modules/broccoli-babel-transpiler/index.js:78:21)

@simonihmig - Not sure if that is actually related to what this issue was about initially?  Can you make a repro and report a separate issue?

@rwjblue sorry for the confusion. In a clean fresh app, I do get the same exception with your proposed config, but I did get it to work when not requiring it directly as @Turbo87 suggested. So this config was working for me:
babel: {
  plugins: [
    ['transform-object-rest-spread']
  ]
}

It did not work in the first place in an existing app, but that was due to some other upgrade issue (ember-cli-mocha)...
So actually no issue to report, other than an example like this should maybe be mentioned in the docs as part of #127.

Doesn't work for me in an addon's dummy app.
I have this:
module.exports = function (defaults) {
  var app = new EmberAddon(defaults, {
    babel : {
      plugins : [
        'transform-object-rest-spread',
      ],
    },

This doesn't help. :( I still get "SyntaxError: Unexpected token" at an object spread.
I also tried providing an incorrect plugin name -- and I don't see any error.
Please help.

@lolmaus depending on your Ember CLI version you might have to use babel6 instead of babel

@Turbo87 I'm on Ember CLI 2.13.2. I had tried babel6, didn't help.

Resolved with this in my addon's index.js:
  treeForAddon (tree) {
    let addon = this.addons.find(addon => addon.name === 'ember-cli-babel') // find your babel addon

    return addon.transpileTree(tree, {
      babel : {
        plugins : [
          'transform-object-rest-spread',
        ],
      },
    })
  },

Wait, this messes up addon modules names. :sob: Same as this.
Come on, is it currently impossible to use rest/spread in Ember addons?

@lolmaus - Not really sure what you expect to get with that tone.  This functionality is present and quite simple to use.

The issue that was originally reported here has been addressed (a .babelrc file will no longer be used by ember-cli-babel).
Closing...

To answer what @lolmaus said (since I came here for the same reason) this is how I solved it:
// index.js
init () {
	this._super.init.apply(this, arguments);

	if (!this.options.babel.plugins) {
		this.options.babel.plugins = [];
	}

	this.options.babel.plugins.push('transform-object-rest-spread');
}

@rwjblue I'm a bit frustrated by this same issue. fwiw it just doesn't seem to be simple to use (at least not from an addon)
I'm tying to use the spread operator in an addon and am including the babel plugin and it's config in the addon.
Is the expectation that it should work when consumed by another app (w/o adding any config to the consuming app)?
please bear in mind that I'm a bit of a junior dev (working on an application that was built by much smarter folks than me) so there maybe additional config that is causing issues that I'm not understanding.


Books toursim yield still wrong

Any example values for this bug?

https://github.com/iElden/BetterBalancedGame/pull/73


Add Icons to Navbar

Hello Project Admin
I would like to add Icons to Navbar to make website attractive
Can you assign me this issue under GSSOC'24 @Abidsyed25

@sailaja-adapa ok

@Abidsyed25 Can you add label level 1 or level 2 Under GSSOC'24


Warning on running action: Node.js 12 actions are deprecated.

I've noticed the following warning appear on a workflow run. I've included a screenshot of to what it looks like. It would help to have a new release using a supported version of Node. The warning suggests using Node 16.

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: cakeinpanic/jira-description-action

Looks like there is a fix or partial fix in #27 already.

@javierjulio you seem to be right!
Thank you for the PR, merging it!


master build failure on Windows (tests)

built using cygwin (gradelw) and powershell (gradlew.bat) also in eclipse

Also the link to builds is empty (returns a 404)
https://hub.docker.com/r/typefox/yang-lsp/builds
$ java -version
java version "1.8.0_191"
Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
:io.typefox.yang.ide:testClasses
:io.typefox.yang.ide:test
io.typefox.yang.tests.editor.syntaxcoloring.YangSemanticHighlightingCalculatorTest > checkDescription_multiLine FAILED
org.junit.ComparisonFailure at YangSemanticHighlightingCalculatorTest.java:210
org.junit.ComparisonFailure: expected:<... : []
1 : []
2 : [3:[1:[keyword.other.unit, source.yang]]
3 : [0:11:[keyword.other.unit, source.yang]]
4 : [0:2]:[keyword.other.unit...> but was:<... : []
1 : []
2 : [3:[2:[keyword.other.unit, source.yang]]
3 : [0:12:[keyword.other.unit, source.yang]]
4 : [0:3]:[keyword.other.unit...>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.eclipse.xtext.testing.AbstractLanguageServerTest.assertEquals(AbstractLanguageServerTest.java:1305)
at io.typefox.yang.tests.editor.syntaxcoloring.YangSemanticHighlightingCalculatorTest.assertInfos(YangSemanticHighlightingCalculatorTest.java:210)

same problem, in win10 and java 1.8.0_201.
by using -x test as postfix for build command, build is successful, but still cannot work in VS code with Yang plugin.

@carldou why do you want to recompile instead of just consuming the VS Code extension from the VS Code marketplace?

@carldou why do you want to recompile instead of just consuming the VS Code extension from the VS Code marketplace?

I install the Yang VS Code Extension from VS Code marketplace, but it only highlights the grammer without automatic code completion. So I thought maybe I need to install this yang-lsp additionally. Now, it seems not necessary.

I just tried on Windows 10 with latest VSCode and I do get code completion

Did you install the correct extension? There is another one with syntax highlighting only.
It may also be a problem with (locating) Java on your machine. Do you get messages from VSCode that the language server couldn't be started or keeps crashing?

I just tried on Windows 10 with latest VSCode and I do get code completion

Did you install the correct extension? There is another one with syntax highlighting only.
It may also be a problem with (locating) Java on your machine. Do you get messages from VSCode that the language server couldn't be started or keeps crashing?

I also use Windows 10 with VS code version 1.31.1.

There is one error from VS Code, as shown here.

Hello,
I have exactly the same issue with VSCode and building yang-lsp and I noticed that it started to apear after I install GIT with VSCode as default text editor. Before that Yang VS Code Extension was working fine.

Which version of Java is installed on your system?

Which version of Java is installed on your system?
This one:
java -version java version "1.8.0_241" Java(TM) SE Runtime Environment (build 1.8.0_241-b07) Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode)


[skip ci]Convert Sprint Release into pipeline

Convert Sprint Relase into pipeline

@panpan0000 @changev @anhou @yyscamper @keedya


Separable Fully Connected Layer

Separable Fully Connected Layers (Paper https://doi.org/10.1101/146431 accepted to ICML2017 Workshop on Comp Bio)
It is a module for deep neural networks specific to genomic sequences. This is a decomposable fully connected layer (separable fully-connected layers, abbrv. SeparableFC) as well as a second difference (curvature) regularizer and constraint. The layer separates positional patterns from channel dependent patterns, allowing each to be learned independently.  This in turn leads to a more efficient and interpretable modeling of complex patterns in genomic data. The regularizer and constraint can be readily applied to the tensor concerned with the positional weights.

Hi @farizrahman4u @the-moliver
Just touching base for a quick update on this because at least a few people asked us for useable Keras extensions instead of our lab's fork. Please let us know.
Many thanks!


SQLite state store and concurrent access by multiple Dapr instances

Description
SQLite does not support concurrent writes to the database, and trying to execute multiple queries that modify the database can corrupt the DB.
Within a single Dapr instance, the component is using Go locks to ensure that no more than one operation on the database happens at the same time. This works really well to prevent issues when there's only one Dapr sidecar accessing the database.
However, if multiple Dapr sidecars are initialized with the same SQLite database, there's no protection against concurrent writes.
This could be implemented by adding a transaction around each SQL query. We could also add a metadata option to make this optional, if users developing locally don't need concurrent access to the same DB.
Release Note
RELEASE NOTE: *ADD Protections against concurrent access to the same SQLite database in state.sqlite

As discussed the component should be updated to run all queries transactionally. It is also worth investigating whether there are any file locking concerns - not sure how multiple processes writing to the same SQLite database file is handled.


chore(scanner): remove 4.3.7 from RELEASE_VERSION

Description
Not needed, as 4.3 doesn't have Scanner V4
Checklist

[x] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

Testing Performed
Here I tell how I validated my change
no
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

Damn, automation adds it without looking at the version. Sorry, I will be correcting this manually if needed.


Weird top bar behavior on KDE plasma

System Details

OS: Arch linux
Thorium Version: Version 117.0.5938.157 (Official Build) stable, built on Linux (64-bit)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.3-arch1-1 (64-bit)
Graphics Platform: X11

Problem
Unlike chromium, the top bar shows up, and all controls are handed over to the desktop managers topbar
Screenshots

You just need to disable the system title bar in Thorium settings:
Settings > Appearance > Use system title bar and borders
@NightMare-Vortex


Merge main: monthly schedule bugfix for update.sh

Thank you. I wonder if the monthly action should rebase on main before doing the update? This way it'll stay up to date?

Tricky, since the monthly branch does make change to "releases.nix" differently, hence there is always a conflict to resolve. Not sure about the exact nitty gritty of doing that in the auto-commit workflow.

Hm good point! Will think about this more...

Oops looks like it didn't work: https://github.com/shazow/foundry.nix/commit/78973231e8301e2205bb126d1c5cec47b499fa0c
Sorry I can't take a closer look at this myself right now, thanks for helping out. :)

Ah, you triggered manually, yea, this month there is no permanent build :(
Sorry, my bad.
Do you mind me do a patch work, and revert to previous version of the release.nix?
if [[ "$timestamp" == null ]];then
    echo "Sad month, no build :("
    exit 0
fi

Wanna just make the change to the derivation locally and send a PR for that? :)

I'll revert for now.


Fix string for associated placement resources

Signed-off-by: Zack Layne<EMAIL_ADDRESS>Related issue: https://github.com/stolostron/backlog/issues/21140

/test ci/prow/lint-check-unittests-sonarcloud

/test lint-check-unittests-sonarcloud


Explore DWave's solver datasheet

after #68, I create this issue for when I have time to study a few dwave topics into more detail
https://docs.dwavesys.com/docs/latest/doc_qpu.html

Dissertation already defended


MODELIX-710 bulk-model-sync-gradle fails with "unexpected concept change"

TODO: additional tests

Test coverage on SetConceptOp.kt looks pretty weak now. Probably reverting such a change is not tested?

:tada: This PR is included in version 7.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add event support to junebug message sender integration

While we have the endpoint for Junebug events to be received, we're not sending that URL along with each message so that the events get back to us.
The plan is to add the sites framework, and use the sites framework to create an absolute URL, and send the absolute events url along with each message to Junebug.

@KaitCrawford Ready for review.

:+1:


fix: fix bugs about 3rd-party login in cas flow

fix: fix bugs about 3rd-party login in cas flow

@ComradeProgrammer fix linter:


Get http json response

How can i access the http body response ?
Thats the code im using right now, but i can't detect a body in the res object.
value.form.submit(url, function (e, res) {     deferred.resolve(res); });

Submit returns a standard nodejs "http#request". You have to listen for "data" events, buffer the data and parse it yourself (or using a module). Check out https://nodejs.org/en/docs/guides/anatomy-of-an-http-transaction/ for more info.

Closing this for now, let me know if this didn't help your issue.


RFE: Move away from using deprecated nose for testing

Feature
nose is deprecated, so it'll be good to move to another testing tool, perhaps py.test.
Motivation
nose is deprecated upstream (the last commit was in 2016.) and is also being deprecated in Fedora.
https://github.com/nose-devs/nose/commits/master
It is still in use here, though
https://github.com/BlueBrain/MorphIO/blob/master/tests/requirement_tests.txt#L3
The nose website says:
https://nose.readthedocs.io/en/latest/
"Nose has been in maintenance mode for the past several years and will likely cease without a new person/team to take over maintainership. New projects should consider using Nose2, py.test, or just plain unittest/unittest2."
Deprecation of nose in Fedora: https://fedoraproject.org/wiki/Changes/DeprecateNose
Alternatives
py.test or nose2 (but nose2 doesn't seem to be at par with nose or py.test)
Additional context
This came up while working on including NeuroM in Fedora as part of the NeuroFedora initiative:
https://pagure.io/neuro-sig/NeuroFedora/issue/438

fixed via #291


Add the motion.preamble to the motion.create view

Current behaviour:
If a motion is created and a preamble is saved in the settings then the preamble is not displayed int the motion-create view but it is displayed in the motion-detail view
Reproduction:
in a meeting:

settings > motions > save something in the "Motion preamble" input
create new motion
the preamble is nowhere to be seen
save the motion
the preamble is at the beginning

Wanted behaviour:
the preamble should be visible in the creation mask directly above the editor from the motion.text

Do you mean instead of the text label or above it?

there is no "text" label while you create a new motion

The preamble should be between the title and the editor


Object

Describe the bug
My error is when i start Occultism and minecfrast says that the server doesnt recognize an obect i think that is the
remote storer

Please provide additional info

latest.log
your exact minecraft version, forge version and mod version
the exact error message you are referring to
your mod list or the exact modpack version

Closed as stale, please ping me to reopen if you have the required info


Subtotals

Is there a way to create subtotals on rows and columns when exists more than one field in each axis?
Rafael

hi nicolas great work done by you..:)
i need subtotals concept in that pivot table..is there any progress in it..?if it means please let me know nicolas ..:)

I'm not actively working on this feature, no.

anyone done this feature?
i can managed do for first level, but next level,i cant . :(

anyone manage to do this? :)

@nicolaskruchten, Thanks a lot for such a useful library.
I have added the support for roll-up summary (sub-total rows) using aggregators and renderer concepts . Its available at OnFieldClick branch of the fork that I have made
Would like to receive your comments/feedback from friends here before I send the pull request. I plan to add collapse-and-expand feature on top of this. Thanks.

goooood work Nagaraj :)

@nagarajanchinnasamy do you have a sample of how to use your SubTotals branch. Are there any settings to turn it on or off?

@vivianjayakaran there are no settings as of now... its directly built into the code. You can try any of the pivot or pivotUI examples... you will get to see them with new summary (sub-total) rows.

@nagarajanchinnasamy thanks for this contribution!
My feedback is as follows:

I don't wish to add subtotals to the main Table renderer, so I would ask that any PR you submit contains a new renderer in a new file.
I understand that enabling subtotals requires some changes to the PivotData class, so these are the changes that are of greatest interest to me. I will need to take some time to carefully read through the changes you made. I notice that you've modified the most performance-sensitive part of the PivotData class (this bit with the "tight loop" comment) so this will require a bit of performance-testing on very large datasets as well.

@nicolaskruchten Thanks for your feedback.

I've made a new commit to the SubTotals branch with subtotal_renderers.coffee added. Name of the renderers is: subtotal_renderers.
Added a new example subtotal.html to demo the subtotal_renderers

Pls check and let me know your feedback

@nicolaskruchten , friends... I have further enhanced subtotal_renderers with both row-wise and column-wise subtotals. Also added Collapse/Expand functionality for rows. Collapse/Expand for column subtotals is under construction....
Please check Subtotals branch. and provide your feedback. Steps to use:

Download pivottable-Subtotals.zip
Extract and place pivottable and its subfolders under document root of your local webserver
Access the demo using url: http://localhost/pivottable/examples/subtotal.html

Sample screenshot:

@nagarajanchinnasamy There is an error in computation of "Sum as Fraction of Rows" and "Count as Fraction of Rows". Do you know how to correct this?

I think the "Totals" of Subtotals don't include in computation element in aggregator "fraction Of", cause i check the subtotal Alberta don't divided with itself but with subtotal of NDP in Quebec, etc... etc...

Ups sorry, not subtotal "Alberta" but subtotal "Female"... subtotal "Alberta" divided by subtotal "conservative"...

@ahmad003  Thanks for the feedback... I will look into this issue and get back. Thanks again.

@ahmad003 I do not see any issue with the aggregators. For e.g., in the picture shown below, after selecting Sum as Fraction of Total and Age, the overall total is 15603 and for Females in Age Bin 60, the subtotal value is 883. Converting this to percentage ((883/15603)*100)) yields 5.7% as shown rightly in the pivot. Or, am I missing something? Please confirm.

Thank you @nagarajanchinnasamy for reply my question... And, yes, for Sum as Fraction of Total there is no error, but if you use Sum as Fraction of Rows, you will see there is an error like this...

And if you continue to make subtotals for column, most likely there will be an error in  Sum as Fraction of Columns... Thank you once again for fast reply... I hope this will help you in developing this project...

If you see the image bellow, the result of Sum as Fraction of Rows for subtotal Alberta is divided by total of Conservative in Alberta... (240/180)*100 = 133.3... When i check the result of Sum as Fraction of Rows for **Female **, it divided by total of NDP in Quebec.

@ahmad003 , Yes... I see the issue now. Let me check and get back to you. Thanks for clarification.

@ahmad003 the issues is fixed now in both as Fraction of Rows and as Fraction of Columns
Please check-out the latest version from SubTotals Branch
Thanks again for your feedback.

Thank you once again @nagarajanchinnasamy... You're Awesome... For my reference, is there a way to make default expand/collapse to expand,.. And for future development, I think it's necessary to make tool to expand/collapse all rows, to hide/show subtotals for row and column... when your data so many, you don't want to click one by one to expand/collapse all rows, isn't it...
Anyway Great Work !!

@ahmad003 Thanks :-)
Yes, I plan to add rendererOptions  to control expansion/collapsing of pivot when it is drawn initially. I am still thinking what the option could be. Of course, expandAllRows or expandAllColumns are easy ones. Just wondering if more finer control can be given or not!!!
I have enabled issues tab in the forked repository here in case if you want to discuss subtotal_renderers specific issues.

@ahmad003 I have added an option collapseRowsAt as a rendererOptions that takes one of the row attributes as it's value and collapses rows at that level.E.g.:
rendererOptions: {
    collpseRowsAt: "Province"
}

Default behavior is to expand all rows.
Please check subtotal.html example at the forked repository here...
Thanks for your feedback.

@ahmad003 in addition to the collapseRowsAt option, I will also expose a function to be invoked at runtime to expand/collapse rows/columns. I would not want to change the standard user interface to provide the tool to expand/collapse rows/columns. Instead, the application can have its own UI, when clicked, can call the exposed function.
I will also see if I can provide a function to show/hide subtotals

@nagarajanchinnasamy, its awesome.
I think you can make new aggregation function like % of Parent Row Total and % of Parent Column Total in excel (option Show Value as), that you can make subtotals output...

@ahmad003 Thanks.
% of Parent Row/Column is a good suggestion. Willl add and let you know. Thanks again.

@nagarajanchinnasamy, can subtotals generate without UI?

@ahmad003 sorry I did not understand what you mean by:

can subtotals generate without UI?

@nagarajanchinnasamy, Sorry..
I mean to change this code in example/subtotal.html in line 38
        **$("#output").pivotUI(mps, {**

to
        **$("#output").pivot(mps, {**

but when i try, the subtotals didn't generate..

@ahmad003  got it. I will check. Thanks for the feedback.

Are you gona PR this on the nicolaskruchten repo?

@nagarajanchinnasamy I've put some thought into how we can modify this library to allow your fine work to be compatible. My proposal is that we accept a new parameter which would allow the developer to override the PivotData class altogether, instead of just the processData function, so that someone could actually choose to store the data differently as well as process it differently. If I made this change, would you consider modifying your code to follow?

Definitely @nicolaskruchten.... My pleasure :+1: Please confirm once this change is done. I will modify the code accordingly and submit a PR.

@nicolaskruchten, as u had suggested, I've created SubtotalPivotData class that extends PivotData. Overridden ProcessRecord function. Introduced a link in index.html to the example subtotal.html.
Submitted PR #506. Please review and let me know of your feedback.

@nicolaskruchten , @ahmad003 , @anandakumarramaswamy , @vivianjayakaran  and friends, happy to inform you that Subtotal.js is available for download as an NPM module or Bower component.
Subtotal.js is hosted in GitHub as pivottable-subtotal-renderer
@nicolaskruchten , In setting up Subtotal.js, I have shamelessly copied the structure, style and some portions of text and code as is from Pivottable.js repository. Hope you don't mind.
Thanks again to all of you for your feedback and support :+1:

All right, I think we can finally consider this issue resolved! The official answer in the FAQ is now "use Subtotal.js" :)


fix(docker/builders): fixed libelf-dev and dwarves incompatibilities in debian backports

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
What this PR does / why we need it:
Fixes master CI for build-images-arm64:

#0 2.886  libelf-dev : Depends: libelf1 (= 0.176-1.1+deb10u1) but 0.183-1~bpo10+1 is to be installed

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
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:

OWNERS [FedeDP]

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: EXONER4TED, FedeDP
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:

OWNERS [EXONER4TED,FedeDP]

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


adds specification on triplet name format

The format of the triplet name actually matters sometimes.
See: https://github.com/Microsoft/vcpkg/issues/1463
I wasn't able to find the best location in the code to add the error without causing potential backward compatibility issues. Until this is resolved, this change will at least document the until now implicit constraint on a triplet name.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

I propose to cancel this request as another, better solution was found.
See the last comment on: https://github.com/Microsoft/vcpkg/issues/1463


[Deprecation][v1.8.0-beta-7] List broken when used new line

Latest Parsedown beta version 1.8.0-beta-7, breaks list markdown containing new line like
1. a

  b

turning to

a

b

While it works fine in latest stable v1.7.3, returning

a

b

The result given by 1.7.3 isn't correct—the line with "b" needs to be indented by one more space so that it matches up with the original list content's indentation.

@aidantwoods, you are wrong. I just rechecked it in https://parsedown.org/demo and I switched to Parsedown v1.7.3, and it works as I mentioned above.

@aidantwoods, you are wrong. I just rechecked it in https://parsedown.org/demo and I switched to Parsedown v1.7.3, and it works as I mentioned above.

The result given by Parsedown 1.7.3 isn't correct (not for). I agree that Parsedown gives the result you mentioned, however it is this result which is incorrect.
The CommonMark reference parser indeed agrees with the new (1.8.x-beta) result, giving:

a

b

To see why this is the case, see the spec description under example 224, which says:

The most important thing to notice is that the position of the text after the list marker determines how much indentation is needed in subsequent blocks in the list item. If the list marker takes up two spaces, and there are three spaces between the list marker and the next non-whitespace character, then blocks must be indented five spaces in order to fall under the list item.

@aidantwoods, having space/s or not, 1.8.0-beta-7 currently fails on it and doesn't wrap inside

As mentioned, it needs to be indented to match the indentation of the list content where the marker begins, like this:

@aidantwoods, sorry, You are right! With right spacing, spec wraps correctly
https://spec.commonmark.org/dingus/?text=1. a

   b
1. a

   b

results

a

b

Meaning Parsedown and Markdown PHP doesn't yet fallow the latest spec.

Or are you saying that 1.8.x-beta fallows the latest spec?

1.8.x-beta follows spec here as far as I can tell, did you have an example where it differs from CommonMark?

Sorry @aidantwoods, it was my mistake. I got confused by latest stable vs beta resulting different results. 1.8.x is resulting fine based on latest spec.
Any ETA for 1.8.x release as stable?

And thanks @aidantwoods  for so quick responses!

Sorry @aidantwoods, it was my mistake. I got confused by latest stable vs beta resulting different results. 1.8.x is resulting fine based on latest spec.

No worries :)

Any ETA for 1.8.x release as stable?

I ended up deciding not to release 1.8.x as a minor upgrade due to quite a few internal changes that might break extensions (context: https://github.com/erusev/parsedown/issues/601#issuecomment-396345464). If you're not using any extensions then I'd just go ahead and use 1.8.x for now (it contains quite a few bug fixes over 1.7.x).
I'm also holding off releasing it as a major upgrade since there are a couple things in the public API that, given the opportunity to change, will make things a lot better. There's quite a bit of progress towards 2.0.x over in https://github.com/erusev/parsedown/pull/708, but still a couple bits and pieces that need ironing out before that'll be ready (also needs documenting :) )


fix headers in INSTALL.md for gfm compatibility

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

whoa dude chillax

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

INSTALL.md has been overhauled in #15802 (and is now BUILDING.md).
The .md formatting has already been fixed by another change.

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @boneskull isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot


[RAISE-BP] Enable the 03-matrix-multiplication tutorial

The 03-matrix-multiplication.py tutorial is a good target to verify that the raising pass is capable of handling real use cases.
The -triton-raise-block-pointer pass should be run on the 03-matrix-multiplication.py tutorial and we should check:

the pass is able to generated code successfully.
the execution produces correct results.

The triton-shared pass on which our pass is based has some limitations:

semantic difference between triton-shared dialect and triton dialect.
We need to find solutions for safely handling modulo and masks for the raised memory accesses.

The raised code does not produce the expected outputs. Further investigation is required.

The pass has started to produce correct results. But it is based on unsafe assumptions. This should be improved to meet production standards.

In progress


Added an e2e test for session on prod.

This change tests and demonstrates how to use memcached based sessions on Managed VMs. Personally I'd like to keep it in user-land, which means you have to enable it by having the following php.ini.
extension=memcached.so
session.save_handler=memcached
session.save_path="${MEMCACHE_PORT_11211_TCP_ADDR}:${MEMCACHE_PORT_11211_TCP_PORT}"

Actually we can have the above configurations in our default php.ini, but I'd rather not make it default. This is because this image can be potentially used on other systems, for example on Kubernetes, or Google Container Engine, etc and on other systems, those environment variables are not there.
@bshaffer
@sjlangley
@cedricziel
Please take a look and let me know what you think.

IMHO this should go into the documentation and not into the main php.ini.
It's quite cool to be able to use memcached through some environment variables, but I vote for less magic and more documentation. :)
I'm fine with the change though :+1:

@cedricziel Thanks for the feedback! I added the documentation for this.

Awesome! Thx :)

@raggi Can you take a look?

I would actually strongly vote in the other direction, and go for convention over configuration. Users should be able to get more things going with less reading and less configuration than forcing them to manually read and configure lots of features that are configured as-standard in competing environments.
As far as the impact on using the image in GKE and so on, this is a secondary goal, not a primary goal. Our primary goal is seamless UX for GAE users.
GKE users by nature of GKE know they'll have to do further configuration. If their apps don't use these features, the env vars being missing won't affect them. If they do, it's trivial to add the env vars in your pod configuration. It's actually harder work for the user to customize their app image to change php.ini and keep it up to date over time.

@raggi
Alright. Do you prefer having those configurations by default?

Other than the discussion above, the code looks fine.
Am I correct in assuming that the current default session storage behavior is files, and that's actually broken for more than one node?

@raggi

Other than the discussion above, the code looks good.

Thanks. Let me make these configurations by default.

Am I correct in assuming that the current default session storage behavior is files, and that's actually broken for more than one node?

Yes.

Great, thanks, yes, lets absolutely make this work for multinode configurations by default.

Sounds reasonable.

@raggi @cedricziel
I updated this PR, and now we automatically enable the memcached based session if there are relevant envvars.
PTAL

Couple of minors :+1:

I squashed the commits. I will merge this after the test passes.

I found that I made a mistake for checking the return value from the gcloud deployment, so I fixed it.
I will merge this after the test pass.

Alright, merging. Thanks @raggi @cedricziel


[en] update assign-pod-node.md

update the description about the example.

@tengqm @divya-mohan0209 done. Thanks for the advices.

@NoicFank 👋🏻 Please feel free to /reopen when you're ready to continue.
/close

/reopen

/close. already edited.


dotnet: Fix GD0107 not applying to arrays and dictionaries containing nodes

Fixes #94589.

Thanks for contributing to the .NET module! This makes sense to me, and GDScript already reports an error for exported Array[Node] variables.
This PR currently only applies to Node[] but the diagnostic should also be reported for Godot.Collections.Array<Node>.
Also, since you are a new contributor, make sure to read CONTRIBUTING.md and the contributing documentation if you haven't already.
Feel free to reach out in the development chat if you need help.

Nice catch, thanks! I've added checks for Godot.Collection.Array<T> and Godot.Collections.Dictionary<TKey, TValue>.
Here's a new resource class to test with:
using Godot;
using System;

[GlobalClass]
public partial class AResource : Resource
{
	[Export] public ANode3D[] DotnetArrayField;
	[Export] public Godot.Collections.Array<ANode3D> GodotArrayField;
	[Export] public Godot.Collections.Dictionary<ANode3D, string> GodotDictionaryWithNodeAsKeyField;
	[Export] public Godot.Collections.Dictionary<string, ANode3D> GodotDictionaryWithNodeAsValueField;

	[Export] public ANode3D[] DotnetArrayProperty { get; set; }
	[Export] public Godot.Collections.Array<ANode3D> GodotArrayProperty { get; set; }
	[Export] public Godot.Collections.Dictionary<ANode3D, string> GodotDictionaryWithNodeAsKeyProperty { get; set; }
	[Export] public Godot.Collections.Dictionary<string, ANode3D> GodotDictionaryWithNodeAsValueProperty { get; set; }
}

You'll also need to add tests for the new cases that are expected to report the diagnostic in the ExportDiagnostics_GD0107.cs file.
The C# you just shared is pretty close, just need to add {|GD0107:Identifier|} in the places were the GD0107 diagnostic is expected.

Thanks! And congrats for your first merged Godot contribution :tada:

Cherry-picked for 4.3.1.


Atom.Object.defineProperty.get is deprecated.

can't toggle view. to fix:
to fix change KeybindingCheatsheetView.initialize - /Users/phawk/.atom/packages/keybinding-cheatsheet/lib/keybinding-cheatsheet-view.coffee:16:9
from: atom.workspaceView.command 'keybinding-cheatsheet:toggle', => @toggle()
to: atom.commands.add 'atom-workspace', 'keybinding-cheatsheet:toggle', => @toggle()
atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app/src/atom.js:55:11)
KeybindingCheatsheetView.initialize (/Users/phawk/.atom/packages/keybinding-cheatsheet/lib/keybinding-cheatsheet-view.coffee:16:9)

Thanks for the report, will fix it this week along with a handful of other
deprecation warnings.
On Sun, Jan 25, 2015 at 8:43 AM, hawkerchuck<EMAIL_ADDRESS>wrote:

can't toggle view. to fix:
to fix change KeybindingCheatsheetView.initialize -
/Users/phawk/.atom/packages/keybinding-cheatsheet/lib/keybinding-cheatsheet-view.coffee:16:9
from: atom.workspaceView.command 'keybinding-cheatsheet:toggle', =>
@toggle https://github.com/toggle()
to: atom.commands.add 'atom-workspace', 'keybinding-cheatsheet:toggle', =>
@toggle https://github.com/toggle()
atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app/src/atom.js:55:11)
KeybindingCheatsheetView.initialize (/Users/phawk/.atom/packages/keybinding-cheatsheet/lib/keybinding-cheatsheet-view.coffee:16:9)
—
Reply to this email directly or view it on GitHub
https://github.com/jkasky/atom-keybinding-cheatsheet/issues/4.

Works Thanks so much
-- Paul Hawk
On Wed, Jan 28, 2015 at 3:11 AM, Jesse Kasky<EMAIL_ADDRESS>wrote:

Closed #4 https://github.com/jkasky/atom-keybinding-cheatsheet/issues/4
via e4c1300
https://github.com/jkasky/atom-keybinding-cheatsheet/commit/e4c13007b1f0ce69cc7eebae6ddbeed3bf483459
.
—
Reply to this email directly or view it on GitHub
https://github.com/jkasky/atom-keybinding-cheatsheet/issues/4#event-225935516
.


Add ld_preload to images

Coverage remained the same at 79.248% when pulling 622fda4b64ee08f94d8caecf15957ebf515b56dc on mklotton:ld_preload into 740f5282f01851aa511ad3c87cacba8ccedea753 on contiv:master.

#32

Coverage remained the same at 79.248% when pulling 0677d64bc586325b063ade5148d978638921b2b4 on mklotton:ld_preload into 0aa17618f80a6a8a78bcc1af89478f4b21c59282 on contiv:master.

Coverage decreased (-28.5%) to 50.428% when pulling 86ca2e293100fcba9cd9587c9ae5160928374d51 on mklotton:ld_preload into 76375392a8d5a48ccd0f5294cda4bca450c5553b on contiv:master.

Coverage decreased (-28.5%) to 50.428% when pulling 92db0fa3f5134f3395a20073108dfa89cea8f1bd on mklotton:ld_preload into 76375392a8d5a48ccd0f5294cda4bca450c5553b on contiv:master.

Coverage decreased (-31.7%) to 47.274% when pulling e6c36e26ce58493c8082ff659751f7da0631def5 on mklotton:ld_preload into 76375392a8d5a48ccd0f5294cda4bca450c5553b on contiv:master.


resolves #60 don't crash when no page- attributes are defined

I have the same problem (#60), please merge this pull request !

@mkobit Can you confirm the fix? Once we merge, would you be able to make a 1.1.2 release?

The fix works, I tested it

Oh, super!

Thanks!


how to filter out some commands?

Hi @deivid-rodriguez
I've (finally) returned to the task to make debugger-xml work with byebug (I thought I only need to add multi-process support now) and it turns out that it doesn't work completely again :(
After your recent refactorings the monkey-patching debugger-xml uses doesn't work.  So the question is: how to modify list of available commands?  debugger-xml adds a few commands and also wants to disable several (such as help or kill).  I remember we had discussed this some time ago but I do not remember the solution was found.
BTW have you considered use of gitter for such discussions/support?

Hi Oleg! I'm on holidays and I'll still be for a while so I'm not sure I'll be good help.
Anyways:

Yes, I broke backwards compatibility again. As you can see in the current major version number in byebug I'm prioritizing other stuff over backwards compatibility because we have very few plugins. But this obviously affects the few plugins we have. Sorry...

Excluding commands is easy now. You just need to return the list of available commands from a commands method in your processor. If you're inheriting from byebug's processor you can use super + except (see byebug's post mortem processor). Otherwise you can just return an explicit list of commands.

I think the use of gitter is a good idea for this stuff.

Hope this helps!

thank you for information.  Will play with it.  Enjoy your holidays ;)

Cool! Thanks!! :)


Tests cover only 2 out 6 main CLI

xref.: https://github.com/pyOpenSci/software-review/issues/7

I added a test for nbexec with this commit: 526dc06
I will not close this issue until I write click tests to make sure the CLI behaves as expected.

I wrote many new tests. I'm at 92% coverage:
---------- coverage: platform darwin, python 3.7.3-final-0 -----------
Name                     Stmts   Miss  Cover
--------------------------------------------
src/cli/__init__.py          0      0   100%
src/cli/nbconv_cli.py       10      0   100%
src/cli/nbdeck_cli.py       12      1    92%
src/cli/nbexec_cli.py       13      1    92%
src/cli/nbless_cli.py       14      1    93%
src/cli/nbraze_cli.py       11      0   100%
src/cli/nbuild_cli.py       13      1    92%
src/nbless/__init__.py       9      0   100%
src/nbless/nbconv.py        21      5    76%
src/nbless/nbdeck.py         7      0   100%
src/nbless/nbexec.py         8      0   100%
src/nbless/nbless.py         9      0   100%
src/nbless/nbraze.py        12      3    75%
src/nbless/nbuild.py         8      0   100%
--------------------------------------------
TOTAL                      147     12    92%


de-dupe order and resource dependencies

Changes
In case of a pipeline with a huge list of redundant dependencies, the list of dependencies is growing exponentially. This way of calculating the list of dependencies is causing extra delay in the validation cycle. This delay sometimes hit the webhook timeout during validation. This is one of the changes being proposed to make the validation cycle efficient and avoid unnecessary delay.
Introducing a test case which was running until a timeout was hit (without @rafalbigaj's changes in https://github.com/tektoncd/pipeline/pull/5421). Thanks @rafalbigaj for the efficient implementation of building a graph. This test now runs to competition, on average taking 3 minutes. With the changes in this PR, this test runs under two seconds.
/kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
De-dupe task dependencies - order and resource dependencies all together. It's very common to have a task with multiple when expressions referring to the same task but different results. Maintain a set of dependencies and add only a new parent.

Thanks @pritidesai - could you apply the change to the v1 API as well?

thank you @afrittoli for pointing that out 👍 I have applied these changes to v1. Thanks!

/lgtm

Do we need to cherry-pick this one too? @pritidesai

/cherrypick release-v0.37.x

/cherrypick release-v0.38.x

/cherrypick release-v0.39.x


Problem using type alias & tuples as Resolve Parameter

I had working code till the Xcode update yesterday.
container.register() {(credentials: LoginCredentials) in
            try Login(credentials: credentials, validation: self.container.resolve(), request: self.container.resolve(), persist: self.container.resolve()) as Login
        }

    func resolveLogin(credentials: LoginCredentials) -> Login {
        return try! container.resolve(arguments: credentials) as Login
    }

This was working great. Login Credentials was a type alias for (String, String) Tuple.
Starting today it results in a Runtime crash:
No definition registered for type: Login, arguments: (email : String, password : String), tag: nil.
When I change the resolve to:
    func resolveLogin(credentials: LoginCredentials) -> Login {
        return try! container.resolve(arguments: (credentials.email, credentials.password)) as Login
    }

It's working again

I will look at that later to figure out what changes in Swift 3.1 might have caused that and if that is a bug.
Currently there are different ways to workaround that: you can either do what you do, or you can cast result of register call to Definition<Login, LoginCredentials>, or you can resolve it like resolve(arguments: email, password)

It feels like registering factories with tuple arguments was not working correctly in swift 3 too. What happens is that register call incorrectly infers its generic parameters and calls the variant for factory that accepts two parameters instead of one. But at the same time  I guess it might be connected with this proposal https://github.com/apple/swift-evolution/blob/master/proposals/0110-distingish-single-tuple-arg.md
According to CHANGELOG it should be already implemented for swift 4

According to this thread the issue addressed by SE-0110 should be fixed in swift 4. Though issue with type aliases still can be something different. I will close this and will reference it in #107


AutoGrow and MaxLines Properties Not Working in MudTextField

Bug type
Component
Component name
MudTextField
What happened?
I have been using MudBlazor in my project for the past 10 months. According to the project requirements, I need the MudTextField component to automatically grow as text is bound to it. Based on the documentation, the MudTextField should have an AutoGrow property that fulfills this requirement. Unfortunately, it is not working for me, and it appears highlighted in red. Can you please advise if I am missing something?

Additionally, the MaxLines property is also not functioning as expected.
Expected behavior
AutoGrow and MaxLines should not be highlighted as red and should work properly.
Reproduction link
Can not provide reproducible link. Its working in try.mudblazor.com but not working in my local.
Reproduction steps
Add the MudTextField.
Try adding AutoGrow.
Relevant log output
No response
Version (bug)
6.8.0
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On which operating systems are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Did you try to update MudBlazor to the latest 6.20.0 ?
I did not search specifically for your issue but 6.8.0 is not about 10 months old and perhaps some things have changed that may fix your issue.

Thank you for your response. After updating the version to 6.20.0, the issue is fixed.


[WIP][#5543 toolchain only] Fix library linkage (internal&external)

Same as #5543 but only the toolchain changes without all the other port changes. The port changes are probably no longer required because I added the possibilities for find_library to add common debug suffixes to the searched library name (which also helps with future CMakes find_package Module updates).
fixing library linkage for internal and external uses for single and multi config generators

split function code from toolchain into seperate files
split also some other code from the toolchain file into seperate files
added override for find_library (also added the search for common debug suffixes in the library name)
added override for set_target_properties (because some imported targets dont like generator expressions in IMPORT_LOCATION)
added recursion guards since the overwrite of cmake internal functions is not really a supported feature
added vcpkg_ to counter the above and added extra options to disable the override of the cmake functions
extend logic in find_package override(properly not required anymore and find_library handles all the cases!)
made all internal&external wrong linkage cases FATAL_ERRORs. Can be descalted via an option.

Can somebody run a full CI build with this PR? I am currently searching regressions and I do not know where to look anymore because so many fixes have been merged ;)