Rebuild for r-base 4.1 compatibility

It seems there is some incompatibility between the latest qgis build and the latest r-base build on Linux:
$ mamba create -q -n test19 r-base=4.1.0 qgis=3.18.3                                                                                (mamba)
Encountered problems while solving:
  - package qgis-3.18.3-py36h26cef4d_0 requires qt >=5.12.9,<5.13.0a0, but none of the providers can be installed

conda create has more to say about it:
$ conda create -q -n test19 r-base=4.1.0 qgis=3.18.3                                                                                (mamba)
Collecting package metadata (current_repodata.json): ...working... done
Solving environment: ...working... failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working...
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package libxml2 conflicts for:
qgis=3.18.3 -> libspatialite[version='>=5.0.1,<5.1.0a0'] -> libxml2[version='2.9.*|>=2.9.10,<2.10.0a0|>=2.9.12,<2.10.0a0|>=2.9.9,<2.10.0a0|>=2.9.11,<2.10.0a0|>=2.9.8,<2.10.0a0']
r-base=4.1.0 -> libxml2[version='>=2.9.12,<2.10.0a0']

Package libgcc-ng conflicts for:
qgis=3.18.3 -> exiv2 -> libgcc-ng[version='>=4.9|>=7.3.0|>=7.5.0']
qgis=3.18.3 -> libgcc-ng[version='>=9.3.0']

Package libstdcxx-ng conflicts for:
qgis=3.18.3 -> exiv2 -> libstdcxx-ng[version='>=4.9|>=7.3.0|>=7.5.0']
qgis=3.18.3 -> libstdcxx-ng[version='>=9.3.0']

Package icu conflicts for:
qgis=3.18.3 -> icu[version='>=68.1,<69.0a0']
qgis=3.18.3 -> qt[version='>=5.12.9,<5.13.0a0'] -> icu[version='>=67.1,<68.0a0']
Note that strict channel priority may have removed packages required for satisfiability.

but I don't really understand what that is trying to tell me. As far as I can make out is says that qgis conflicts with itself...
Anyway, I think bumping the qgis version number to get a rebuild with the latest libraries will probably fix this. Thoughts?

It turns out the problem is all the way down in qt. Closing this in favor of https://github.com/conda-forge/qt-feedstock/issues/193


Add support to authorization basic http header in alternative to…

…cookie and java session.
Modification to allow traccar api stateless.

Can you please run mvn site and fix any reported code issues in your code if there are any. Otherwise it looks good.

Thanks for the pull request. I have merged the changes.

when using http auth, how to disable session manager so it won't create new session for all such stateless requests?

You can just remove setSessionManager call.

In old version of traccar server, there is no setSessionManager call, but
it has still some web server internal default session manager.
so, it does not do it, any better idea?
2016-04-11 9:33 GMT+08:00 Anton Tananaev<EMAIL_ADDRESS>
You can just remove setSessionManager call.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/tananaev/traccar/pull/1510#issuecomment-208112032

--
Ulion

Try to change ServletContextHandler.SESSIONS to ServletContextHandler.NO_SESSIONS.

Thx.


Dead Link /tfs/server/architecture/extend-vs-for-alm

Under https://docs.microsoft.com/en-ca/vsts/work/customize/add-modify-field?view=vsts#add-a-custom-control in "Using the object model for tracking work items" but I'm not sure where is should point

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

ID: df8f0fc3-60e9-114d-b2e2-c26cee932a08
Version Independent ID: 9de0bcaa-8043-fc45-9dd8-c8b51afe79b9
Content: Add or modify a work tracking field - VSTS & TFS
Content Source: docs/work/customize/add-modify-field.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@v - Thank you for the feedback.  The current link is no longer valid. And the valid links are different depending on the TFS version that is being run. I'm updating the article and the changes should be live today.


entities number as first character of id gives invalid decimal literal error

I just started using pyscript and it is amazing! can't believe I missed it so far, but I have one bug, I have a alarm_control_panel that is called 8120_aaa_1_alarm which gives the error:
SyntaxError: invalid decimal literal (file.blind.control_blinds @state_trigger(), line 1)
For state I can work around it by using state.get("alarm_control_panel.8120_aaa_1_alarm") but in the trigger I don't think I can.

Ah, I didn't think about state names that start with numbers.  Python won't parse those.  As you point out, you can use state.get() instead, and you are correct in pointing out that doesn't work in @state_trigger since the auto-detection of state variable names to watch isn't able to look inside string arguments to functions like state.get().
As a workaround, the any-change trigger @state_trigger("alarm_control_panel.8120_aaa_1_alarm") should work (since it doesn't involve expression evaluation), and then you could use @state_active to condition the trigger (with state.get()):
@state_trigger("alarm_control_panel.8120_aaa_1_alarm")
@state_active("state.get('alarm_control_panel.8120_aaa_1_alarm') == 'something')
def alarm_trigger():
    ...

One fix would be to add an optional watch keyword argument to @state_trigger that could be a list of state (entity) variables to watch.  That could be used to override the auto-detection.  Then it would look like:
@state_trigger("state.get('alarm_control_panel.8120_aaa_1_alarm') == 'something', watch=["alarm_control_panel.8120_aaa_1_alarm"])
def alarm_trigger():
    ...

My triggers are all any-change, but I do have multiple setup, so it is @state.trigger("sun.sun.elevation or alarm...., don't know if that does trigger expression evaluation?

For any-change triggers on several variables you should use separate arguments (could also be one argument with a list of strings):
@state.trigger("sun.sun.elevation", "alarm_control_panel.8120_aaa_1_alarm")

That avoids evaluating any expression, so the numeric state name should be ok.
This form should work in the current version, without the new watch keyword argument that I added.

Just tried it, but that gives the same error, both with multiple and just with the one.

You're right.  The regex that checks for just a single variable name didn't allow leading digits.  It's fixed now.

Loaded master and it works now, thanks for the fix!


Feature/rename instrument

Propagates an instrument name change to the channel library.
Physical channels of the form awgName-awgChannel will be renamed.
Supports deleting a instrument without breaking channel views.

Need to fix a few small things before the pull request.

GitHub doesn't allow you to push to a closed PR. So, next time you probably just want to leave it open and force push an update.


Uncaught TypeError: Cannot read property 'focus' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.1.0
System: Ubuntu 14.04.3
Thrown From: terminal-plus package, v0.14.0
Stack Trace
Uncaught TypeError: Cannot read property 'focus' of undefined
At /home/sublm/.atom/packages/terminal-plus/lib/view.coffee:567

TypeError: Cannot read property 'focus' of undefined
  at TerminalPlusView.module.exports.TerminalPlusView.focusTerminal (/home/sublm/.atom/packages/terminal-plus/lib/view.coffee:370:20)
  at TerminalPlusView.focusTerminal (/home/sublm/.atom/packages/terminal-plus/lib/view.coffee:1:1)
  at TerminalPlusView.module.exports.TerminalPlusView.focus (/home/sublm/.atom/packages/terminal-plus/lib/view.coffee:374:5)
  at HTMLDivElement.<anonymous> (/home/sublm/.atom/packages/terminal-plus/lib/view.coffee:1:1)
  at HTMLDivElement.jQuery.event.dispatch (/opt/atom/resources/app.asar/node_modules/jquery/dist/jquery.js:4435:9)
  at HTMLDivElement.elemData.handle (/opt/atom/resources/app.asar/node_modules/jquery/dist/jquery.js:4121:28)

Commands
  8x -0:52.4.0 core:move-down (atom-text-editor.editor.mini.is-focused)
  2x -0:50.8.0 core:move-up (atom-text-editor.editor.mini.is-focused)
     -0:49.7.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:49.7.0 enhanced-tabs:toggle (atom-text-editor.editor)
     -0:48.5.0 refactor:done (atom-text-editor.editor.is-focused)
     -0:48.5.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:46.9.0 core:undo (atom-text-editor.editor.is-focused)
  2x -0:41.4.0 enhanced-tabs:toggle (atom-text-editor.editor.is-focused)
     -0:39.2.0 core:move-down (atom-text-editor.editor.is-focused)
  5x -0:38.5.0 enhanced-tabs:toggle (atom-text-editor.editor.is-focused)
     -0:35.7.0 core:move-down (atom-text-editor.editor.is-focused)
  3x -0:34.3.0 core:undo (atom-text-editor.editor.is-focused)
     -0:11 terminal-plus:toggle (atom-text-editor.editor.mini.is-focused)
     -0:03.8.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:03.8.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -0:01.7.0 terminal-plus:toggle (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "themes": [
      "one-dark-ui",
      "atom-dark-syntax"
    ]
  }
}

Installed Packages
# User
atom-alignment, v0.12.1
coffee-compile, v0.19.2
coffee-navigator, v0.0.16
coffee-refactor, v0.7.0
color-picker, v2.0.13
fancy-bracket-matcher, v0.4.1
file-icons, v1.6.11
highlight-line, v0.11.0
highlight-selected, v0.10.1
linter, v1.10.0
linter-coffee-variables, v0.4.1
linter-coffeescript, v1.0.0
minimap, v4.16.0
node-debugger, v1.1.9
nodejs-snippets, v1.0.3
refactor, v0.6.0
terminal-plus, v0.14.0
tree-view-git-branch, v0.0.6

# Dev
No dev packages

It would be very helpful if you could tell me what settings you have enabled in the Terminal-Plus settings.

After i've restarted atom it seemed to work...

The update might have caused the issue. Either way I added a check for an undefined terminal so this issue should be fixed as of v0.14.1.

Hi
I am using my custom GUI extension named snippet extension.
Its a aspx page wherei have used Button control of cc:tridionmanager .
It is working fine but when I am clcking on close button, I am getting below error.
Uncaught TypeError: Cannot read property 'focus' of undefinedTridion.Controls.ModalIframePopup.focus @ coreresource_v<IP_ADDRESS>.12_.js?sav=1&cnt=core:128Tridion.Controls.BaseModalPopup.keepFocus @ coreresource_v<IP_ADDRESS>.12.js?sav=1&cnt=core:126Tridion.Controls.PopupManager.handleOverlayElementClick @ coreresource_v<IP_ADDRESS>.12.js?sav=1&cnt=core:130(anonymous function) @ coreresource_v<IP_ADDRESS>.12_.js?sav=1&cnt=core:5executeListener @ coreresource_v<IP_ADDRESS>.12_.js?sav=1&cnt=core:22i @ coreresource_v<IP_ADDRESS>.12_.js?sav=1&cnt=core:22
COuld you please let me know what is causing this issue. THnaks in advance

Uncaught TypeError: Cannot read property 'focus' of undefined  @.......
Tridion.Controls.ModalIframePopup.focus @ …….
Tridion.Controls.BaseModalPopup._keepFocus
Tridion.Controls.PopupManager._handleOverlayElementClick
(anonymous function)
executeListener


Drive complex logic out of your CI

https://www.jenkins.io/doc/book/pipeline/pipeline-best-practices/

Make your implementation as portable as possible so that you can be implementation agnostic


Running Issue

My OS is Ubuntu 22.04, I followed the install suggestion to install PowerPaint. Finally, I run "python app.py --share --version ppt-v2 --checkpoint_dir checkpoints/ppt-v2", then I go to my local URL, load image, do some mask, button Run, however, I get an error, there is no result.

My OS is Ubuntu 22.04, I followed the install suggestion to install PowerPaint. Finally, I run "python app.py --share --version ppt-v2 --checkpoint_dir checkpoints/ppt-v2", then I go to my local URL, load image, do some mask, button Run, however, I get an error, there is no result.

@zhuang2002 @zengyh1900

it stucks, could u guys help me.

My OS is Ubuntu 22.04, I followed the install suggestion to install PowerPaint. Finally, I run "python app.py --share --version ppt-v2 --checkpoint_dir checkpoints/ppt-v2", then I go to my local URL, load image, do some mask, button Run, however, I get an error, there is no result.

@zhuang2002 @zengyh1900
it stucks, could u guys help me.

I'm experiencing the same problem. Could you please let me know how you addressed it? I would really appreciate your help.

My OS is Ubuntu 22.04, I followed the install suggestion to install PowerPaint. Finally, I run "python app.py --share --version ppt-v2 --checkpoint_dir checkpoints/ppt-v2", then I go to my local URL, load image, do some mask, button Run, however, I get an error, there is no result.

@zhuang2002 @zengyh1900
it stucks, could u guys help me.

I'm experiencing the same problem. Could you please let me know how you addressed it? I would really appreciate your help.

hello, I didn't fix this problem. But I add some code in the source code, to get the result image and save it. It's easy to do it. hope this could help u.

My OS is Ubuntu 22.04, I followed the install suggestion to install PowerPaint. Finally, I run "python app.py --share --version ppt-v2 --checkpoint_dir checkpoints/ppt-v2", then I go to my local URL, load image, do some mask, button Run, however, I get an error, there is no result.

@zhuang2002 @zengyh1900
it stucks, could u guys help me.

I'm experiencing the same problem. Could you please let me know how you addressed it? I would really appreciate your help.

hello, I didn't fix this problem. But I add some code in the source code, to get the result image and save it. It's easy to do it. hope this could help u.

Thank you very much for your helpful advice. I really appreciate it!


The type or namespace name Platform does not exist

Hi,
I pasted the line 'ZXing.Net.Mobile.Forms.WindowsUniversal.Platform.Init();' in my 'MainPage' in my UWP project, but i am getting the error:
The type or namespace name Platform does not exist in the namespace ZXing.Net.Mobile.Forms.WindowsUniversal (are you missing an assembly reference?)	App1.UWP
I tried to clean and rebuild my project several times, but it didn't helped.
What am I doing wrong here?

Also had this problem.
Any solutions?
Plain new MasterPageView project if it is relevant... All packages updated

This is not included in the version on Nuget - but all that it does is combine both of these calls together;

        ZXing.Net.Mobile.Forms.WindowsUniversal.ZXingScannerViewRenderer.Init();
        ZXing.Net.Mobile.Forms.WindowsUniversal.ZXingBarcodeImageViewRenderer.Init();

@Redth it seems you have not released to nuget a version that includes my merged PR (https://github.com/Redth/ZXing.Net.Mobile/pull/874)?


[Enhancement] Script to migrate from sqlite to MySQL

For those that by mistake (like myself) or for others that wish to move away from sqlite to MySQL could there be a script - either php or otherwise that could be performed on php artisan migrate?
This would be useful as (for example) I have several modpacks and several mods with all their individual information added into the flatfile db (sqlite)

http://stackoverflow.com/a/1067365 may help, if this is still an issue for you

@spannerman79 Might be an good idea, but it would be buried in the IceBox for a while. I would recommend @skwerlman's route of thinking.


Add support to skip container ID checks in events

Phyp currently creates the container ID's dynamically, so
we will not able to know the Id of the containers beforehand.
So this PR would be adding support to skip checking for entities
that does not have container Id's mentioned in the events json.
Fixes : SW540578 & SW540536
Tested By :
On Rainier :
type : 57346
instance : 0
conId : 32779
name : Enabled
interfacexyz.openbmc_project.Object.Enable
obj path : /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
entered the try block
value : 0 ,service :xyz.openbmc_project.Network.Hypervisor , interface : xyz.openbmc_project.Object.Enable , path : /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
type : 57346
instance : 0
conId : 32779
name : Enabled
interfacexyz.openbmc_project.Object.Enable
obj path : /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
entered the try block
value : 1 ,service :xyz.openbmc_project.Network.Hypervisor , interface : xyz.openbmc_project.Object.Enable , path : /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
On Everest :
type : 57346
instance : 0
conId : 32790
name : Enabled
interfacexyz.openbmc_project.Object.Enable
obj path : /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
value : 0 ,service :xyz.openbmc_project.Network.Hypervisor , interface : xyz.openbmc_project.Object.Enable , path : /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
type : 57346
instance : 0
conId : 32790
name : Enabled
interfacexyz.openbmc_project.Object.Enable
obj path : /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
value : 1 ,service :xyz.openbmc_project.Network.Hypervisor , interface : xyz.openbmc_project.Object.Enable , path : /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
Signed-off-by: Manojkiran Eda<EMAIL_ADDRESS>

upstream commit : https://gerrit.openbmc-project.xyz/c/openbmc/pldm/+/49421


Revert "[release_1.2.49] OCM-12851| feat: default values for CAS Max Nodes Total and validation added for count of mp worker nodes"

Reverts openshift/rosa#2716

/lgtm


Question about Creating Scopes

If I resolve an IServiceScopeFactory, then create a scope, is there any facility to modify a Registration in that new scope to provide a different lifetime?  I'm wanting to resolve something from first scope, then change it's lifetime in the second scope.
The use-case is that I'm developing a WebSocket middleware which needs to have a class which has a lifetime which is a singleton to the path mapped which registers the sockets, while creating another class on demand when socket messages are processed, so that EF and other tools can have a proper scope for processing those inbound messages.  Or optionally maybe a custom Activator method which resolves all but the type I want to provide from the first scope.
This might help:
Top Scope

/path (Middleware)

Create Scope1

Create Scoped Registrations List

Web Socket Message Received

Create Scope2

Invoke Handler to process message (with injected Scoped Registrations List)

Dispose Scope2
.... some point later ...

Connections all drop, and my Scope1 is disposed

The goal here is that each path has it's own list of Scoped Registrations.

What we do in https://github.com/OrchardCMS/Orchard2 is that at startup we create as many containers as we have tenants (one per url prefix), with unique and also common services, and we have a middleware that will detect which one to use, then resolve IServiceScopeFactory from it to create a Scope that will be used during the request.
c.f. https://github.com/OrchardCMS/Orchard2/blob/12c028e0b7a479e3ebae3fd2065ff1bad695368b/src/Orchard.Hosting.Web/OrchardContainerMiddleware.cs

Thanks for that info - I will take a look at what you have going on there.  I might have a few more questions once I get my head around what you are doing and how it best applies to my case.

I looked at what you guys were doing - made sense.  I took a similar but simpler approach for my need.  Basically ended up with a singleton "manager" that handles the creation/disposal of scopes.  After doing this, I realized I was already doing the same within my socket manager class, per a "logical" request.
Thanks for the input.


Error response for small Responder transmit buffer

Original issue : https://github.com/DMTF/libspdm/issues/2141#issuecomment-1594855129.
Specification issue : https://github.com/DMTF/SPDM-WG/issues/2931.
In the event where the Requester does not support chunking but the message is larger than the transmit buffer size of the Responder, the Responder needs to send an error to the Requester. This can't be ResponseTooLarge since that is only for when the message is too large for the Requester, so we can use Unspecified until we get the specification clarified.

Discussed in SPDM WG, we will use ResponseTooLarge and clarify in the spec.


Bugfix/3976

Related Issues

closes #3976
Short Description and Why It's Useful

Updates method that checks if product has any error in Microcart. Also there is bug in magento https://github.com/magento/magento2/issues/26297 If you add product with selected more then one checkbox then sku gets extra dashes at the end. Two checkboxes, two dashes. Three checkboxes, three dashes :D etc. Perfect solution would be if this will be fixed in magento. I've added comment there and it doesn't look like hard thing, but they have a lot of issues so probably it not going to be fixed soon. So my solution is to add this helper https://github.com/DivanteLtd/vue-storefront/pull/3977/files#diff-6360e52de42aae27e44994a484027326R16 I think it shouldn't be exported because we want to remove it as soon as possible.
Screenshots of Visual Changes before/after (if There Are Any)

Which Environment This Relates To
Check your case. In case of any doubts please read about Release Cycle

[ ] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[x] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[x] I've updated the Upgrade notes and Changelog on how to port existing Vue Storefront sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

@gibkigonzo please change the base to hotfix

ok, it still gonna fail, because if someone adds in purpose sku to custom option then there will be difference in mergeActions. And thats probably case in this issue, because on client side there is short sku and from server we get long


Agent: WeaveWorker reload containers in both weave restart and re-create cases

Fixes #2158
Also fixes #2225
Extends the existing WeaveWorker logic that re-runs the Docker::Container.all.each do start_container(...) end logic on all weave container start events, not just restart events. This fixes the missing container DNS names on weave re-configurations by both re-attaching all containers and re-registering their DNS names after the weave container is re-created.
The difference between the two is that restart events would only happen if the weave router crashes, and Docker restarts it. If the Weave worker decides to re-create the container to change the configuration, then it will not be a restart event, but rather a destroy event followed by create and start. Currently the attached containers remain attached, but weave forgets the DNS registrations.
There is some trickyness going on here, because this will avoid triggering on the initial start event when the Weave actor is first creating the weave router container, as it only subscribes to container:event notifications after the Weave actor signals network_adapter:start, so this logic should not kick in before that.

The alternative to this would be to change the Weave actor to re-notify network_adapter:start after upgrades.

Split the network_adapter.router_image? and friends refactoring into #2207
This now just results in slightly more network_adapter.router_image? calls.

Compared to #2131, this is simpler, but it does more work, because it will also re-attach every container when re-creating weave. This also happens on weave restarts.

Noticed another problem with the existing WeaveWorker' code: re-calling startwill also re-subscribe tocontainer:event`, so the worker starts seeing everything twice :(
I, [2017-04-26T11:25:17.126175 #1]  INFO -- Kontena::Workers::WeaveWorker: Restart after weave restart
I, [2017-04-26T11:25:17.127935 #1]  INFO -- Kontena::Workers::WeaveWorker: Restart after weave restart
D, [2017-04-26T11:25:17.824282 #1] DEBUG -- Kontena::Workers::WeaveWorker: waited 0.7s of 300.0s until: weave running yielded TrueClass
D, [2017-04-26T11:25:17.985824 #1] DEBUG -- Kontena::Workers::WeaveWorker: waited 0.9s of 300.0s until: weave running yielded TrueClass
D, [2017-04-26T11:25:18.411287 #1] DEBUG -- Kontena::NetworkAdapters::WeaveExecutor: weaveexec stream: ["--local", "ps"]
D, [2017-04-26T11:25:19.016518 #1] DEBUG -- Kontena::NetworkAdapters::WeaveExecutor: weaveexec stream: ["--local", "ps"]

I, [2017-04-26T11:31:32.186142 #1]  INFO -- Kontena::NetworkAdapters::Weave: Attach container=067cc8d4aace21339d38f4bac43fff62b6aef7c55dee1b47fcfb164484a05772 at cidr=<IP_ADDRESS>/16 I, [2017-04-26T11:31:32.198249 #1]  INFO -- Kontena::NetworkAdapters::Weave: Attach container=067cc8d4aace21339d38f4bac43fff62b6aef7c55dee1b47fcfb164484a05772 at cidr=<IP_ADDRESS>/16

Affects existing agent code for weave restart events, introduced by #1398 in Kontena 1.0

The new behavior to react to weave start container:event notifications needs some consideration of how those are timed relative to the network_adapter:start notifications. If they were to arrive in the network_adapter:start -> container:event order, then this WeaveWorker would run start_all_containers twice. Not fatal, but best avoided?

IMO we should try to avoid the possibility to run start_all_containers unnecessarily, it's pretty expensive when there are lot of containers.

IMO we should try to avoid the possibility to run start_all_containers unnecessarily, it's pretty expensive when there are lot of containers.

In terms of the potential race condition between the network_adapter:started and the Docker weave container:event start notifications, the Weave#launch also runs other weaveexec containers between the launch-router that creates and starts the weave container, and before notifying network_adapter:started, so I would consider it highly unlikely for the Docker container weave start event to come after the network_adapter:started notification. Not impossible though, and I don't think there's any way to really avoid the races between the Weave actor network_adapter:start notifications and the Docker weave container:event start notifications.
However, even that unlikely race condition would just lead to two sequential to start_all_containers, which should AFAIK be harmless, just result in a lot of unnecessary weaveexec attach calls. So not IMO worth worrying too much about?

@SpComb Compared to #2131, this is a smaller change, but it does more work, because it will also re-attach every container when re-creating weave. This is similar to what also happens on agent restarts, and if weave crashes and gets restarted by Docker.

@jnummelin  I was trying to avoid the migration logic in the "full" network restart in this case as it might be bit expensive if there's lot of containers.

We could optimize start_all_containers by enhancing the WeaveWorker@migrate_containers caching to not re-attach containers that are already attached, but that then needs to be careful to not race with the service container restart events and leave the containers unattached.
The important question is whether or not we have an issue with attach_overlay of service containers failing during weave restart/re-create events. If weave getting restarted/re-created can result in concurrent attaches of starting service containers failing, then it would make sense to go to the effort of re-attaching containers after weave restarts/re-creates, in order to not leave those service containers detached.
So far, we have not yet seen attaches failing during restart events. In fact, there's some indication of them succeeding despite weave being restarting over in #1923:
kontena-agent | D, [2017-03-02T09:50:04.801681 #1] DEBUG -- NetworkAdapters::WeaveExecutor: weaveexec ok: ["--local", "attach", "<IP_ADDRESS>/16", "--rewrite-hosts", "fe5af6db7c101a1314bfe68a7f020b11083378caa5a95e4db38580eb32af2559"]
kontena-agent | <IP_ADDRESS>
kontena-agent |
kontena-agent | D, [2017-03-02T09:50:05.191951 #1] DEBUG -- NetworkAdapters::WeaveExecutor: weaveexec ok: ["--local", "attach", "<IP_ADDRESS>/16", "--rewrite-hosts", "a746a42562999f5cbd9984e8aea6403f69f5dce783622f643e7514371b88f443"]
kontena-agent | <IP_ADDRESS>
kontena-agent |
kontena-agent | D, [2017-03-02T09:50:06.356523 #1] DEBUG -- NetworkAdapters::WeaveExecutor: weaveexec ok: ["--local", "attach", "<IP_ADDRESS>/16", "--rewrite-hosts", "ba04a7ced236046c8886fe852e5ffe12d977c3c3b480cc2dee547f0398129b37"]
kontena-agent | weave container is not present. Have you launched it?
kontena-agent | <IP_ADDRESS>
kontena-agent |
kontena-agent | D, [2017-03-02T09:50:06.923496 #1] DEBUG -- NetworkAdapters::WeaveExecutor: weaveexec ok: ["--local", "attach", "<IP_ADDRESS>/16", "--rewrite-hosts", "653e4574f253f572f9c584b279ec5d64dc602cac8f7e646ac8de606df7277316"]
kontena-agent | weave container is not present. Have you launched it?
kontena-agent | <IP_ADDRESS>
kontena-agent |

@SpComb The alternative to this would be to change the Weave actor to re-notify network_adapter:start after upgrades.

Having the Weave actor notify after re-creating might actually work to avoid the race between network_adapter:started and container:event notifications?

Having the Weave actor notify after re-creating might actually work to avoid the race between network_adapter:started and container:event notifications?

Should work, and would simplify things a bit.

Having the Weave actor notify after re-creating might actually work to avoid the race between network_adapter:started and container:event notifications?

Should work, and would simplify things a bit.

Implemented this alternative over in #2278

Closed by #2278


Installation doesn't work with React 18

Describe the bug
After upgrading to react 18 I can't install any packages because of the error below, if I use --legacy-peer-deps it works
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^15.3.0 || ^16.0.0-rc || ^16.0 || ^17.0" from<EMAIL_ADDRESS>npm ERR! node_modules/simplebar-react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/myUser/.npm/eresolve-report.txt for a full report.

npm ERR!      /Users/myUser/.npm/_logs/2022-04-06T08_32_19_168Z-debug-0.log

Expected behavior
No error occurs
Your environment

Software
Version(s)

SimpleBar
2.3.6 (react)

Browser
100.0.4896.75 (chrome)

Operating System
12.3.1 (macos)

Solved in<EMAIL_ADDRESS>


Test clang 13.

This PR is for testing to see if there are ABI incompatibilities with pybind11 and the new pin of clang to version 13.  It should not be merged as is.  If incompatibilities are found, we should pin to clang 12 for this major version of rubin-env and issue a new major version for clang 13.  If incompatibilities are not found, this PR should be quietly closed.

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin restart ci

I think the hash didn’t change so we have to bump the build number to test. The Abi looks fine.

Indeed:
++ echo __GXX_ABI_VERSION
++ x86_64-apple-darwin13.4.0-clang++ -E -
++ tail -1
+ '[' 1002 == 1002 ']'


TabbyChat fails to build :(

$ ./gradlew setupCIWorkspace --info

Starting Build
Settings evaluated using settings file '/home/user/repos/TabbyChat-2/settings.gradle'.
Projects loaded. Root project using build file '/home/user/repos/TabbyChat-2/build.gradle'.
Included projects: [root project 'tabbychat', project ':MnM-Utils', project ':compat']
Evaluating root project 'tabbychat' using build file '/home/user/repos/TabbyChat-2/build.gradle'.
This mapping 'snapshot_20160517' was designed for MC 1.9.4! Use at your own peril.
Evaluating project ':MnM-Utils' using build file '/home/user/repos/TabbyChat-2/MnM-Utils/build.gradle'.
This mapping 'snapshot_20160517' was designed for MC 1.9.4! Use at your own peril.
#################################################
         ForgeGradle 2.2-SNAPSHOT-59f33ec
  https://github.com/MinecraftForge/ForgeGradle
#################################################
               Powered by MCP unknown
             http://modcoderpack.com
         by: Searge, ProfMobius, Fesh0r,
         R4wk, ZeuX, IngisKahn, bspkrs
#################################################
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://libraries.minecraft.net/com/mumfrey/liteloader/1.10-SNAPSHOT/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://libraries.minecraft.net/com/mumfrey/liteloader/1.10-SNAPSHOT/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://libraries.minecraft.net/com/mumfrey/liteloader/1.10-SNAPSHOT/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://libraries.minecraft.net/com/mumfrey/liteloader/1.10-SNAPSHOT/maven-metadata.xml]
Evaluating project ':compat' using build file '/home/user/repos/TabbyChat-2/compat/build.gradle'.
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://libraries.minecraft.net/com/mumfrey/liteloader/1.10-SNAPSHOT/maven-metadata.xml]
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://libraries.minecraft.net/com/mumfrey/liteloader/1.10-SNAPSHOT/maven-metadata.xml]

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'tabbychat'.
> Cannot change dependencies of configuration ':MnM-Utils:liteloaderDeobfCompile' after it has been resolved.

* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.

BUILD FAILED

Total time: 13.204 secs
Stopped 0 compiler daemon(s).

clone this into buildSrc
https://github.com/killjoy1221/ForgeGradle-LiteLoader

Thanks!


Add universal viewer

Use hosted Universal Viewer from https://github.com/pulibrary/plum/issues/427


Migrate to v4 guidance is not good enough

Describe the bug
I'm using latest v3 keyv/redis currently. There is no enough information about how to migrate from v3 to v4 if using cluster replica set within k8s. In v4, using createCluster and it requests 'rootNodes' but in k8s we don't need to provide the node IP address, just provide a host URL. Would you please let me know how to migrate to v4?
Here is the code about how I make it work in v3:
new KeyvRedis(new Redis.Cluster(
            [
              {
                host: configService.getOrThrow<string>('REDISDB_HOST'),
                port: Number(configService.getOrThrow<string>('REDISDB_PORT'))
              }
            ],
            {
              scaleReads: configService.getOrThrow<NodeRole>('REDISDB_READ_PREFERENCE'),
              enableReadyCheck: true,
              enableOfflineQueue: true,
              redisOptions: {
                autoResubscribe: true,
                autoResendUnfulfilledCommands: true,
                socketTimeout: ms(configService.getOrThrow<string>('REDISDB_SOCKET_TIMEOUT')),
                connectTimeout: ms(configService.getOrThrow<string>('REDISDB_CONNECT_TIMEOUT')),
                maxRetriesPerRequest: Number(configService.getOrThrow<string>('REDISDB_MAX_RETRY_ATTEMPTS_PER_REQUEST'))
              },
              clusterRetryStrategy: (times, reason) => {
                if (times <= Number(configService.getOrThrow<string>('REDISDB_MAX_CLUSTER_RETRY_ATTEMPTS'))) {
                  const nextDelay = Math.min(
                    100 * Math.pow(2, times),
                    ms(configService.get<string>('REDISDB_RETRIES_MAX_BACKOFF_LIMIT'))
                  );
                  return nextDelay;
                }

                throw new Error(`Unable to connect to the redis cluster and throttler guard could not be setup`);
              }
            }
          ))

@zhuxb711 - thanks for sending in the issue. The new redis driver is based on node-redis which you can follow their documentation on createCluster.
You can read more on this here and post any issues that you encounter in that repo. https://github.com/redis/node-redis/blob/master/docs/clustering.md
I will add in the link to this documentation in ours to help.

https://github.com/jaredwray/keyv/pull/1212

I got type not assignable error from v4.0.1
        const cluster = createCluster({
          rootNodes: [
            {
              url: `redis://host:port`
            }
          ],
          useReplicas: true
        });

        const key = new Keyv({
          store: new KeyvRedis(cluster) // cluster is not assignable to the constructor of 'KeyvRedis'
        });

@zhuxb711 the type issue should be resolved in v4.0.2 please note that when using clustering clear() and iterator() do not work due to the lack of SCAN in clustering.


Expectations in Dutch version of ETM

In the Dutch version of the ETM there are expectations by certain people displayed next to the sliders. In the transport section a lot has changed recently, so now these expectations do not really match with the sliders. For example in the image below s a growth-percentage per year is given in the expectation, but the truck slider is now a share-percentage.

What should we do?

Adjust the expectation (where can this be done?)
Delete the expectation (it is written more than six years ago)
.....

I'm in favour of removing it all together for all sectors.
Notifying @jorisberkhout, @AlexanderWirtz , @MartLubben in case they have an opinion

R E M O V E ! !

It is not working properly yet.

@marliekeverweij What's not working currently? I can see the missing slider labels (I can fix that) and I need to remove some database tables, but a quick glance suggests that everything is otherwise working fine. Is there anything else I might need to fix before merging this?

 I am indeed only missing all slider labels. Furthermore, it is working :)

Since we both tested it, I merged this without bothering with a pull request. I also squashed it down to a single commit since one commit per deleted file was a bit much 😄. @marliekeverweij: Thanks for taking care of this!


i get this error

how do you solve it so it works on that nodejs?

You got 2 options:

install Node.js 14.x - this is the recommended solution; it will work for sure, but Node.js 14.x is no longer supported
use Node.js 16.x or a more recent version, and see if it works

Unfortunately, the Ember version used there is pretty old and I'm not sure if it works with Node.js 16+.


add dotnet:3.1 kind

I think docker-compose works by downloading a core repo tarball from github, so once the core PR to add dotnet:3.1 is merged that will get it into the runtimes.json file.

i think this line needs to change https://github.com/apache/openwhisk-devtools/blob/0f2786f22ba826e8457b91d59a94606fdac90263/docker-compose/docker-whisk-controller.env#L66

thanks.


jx-lva-slip-generator to 1.4.3

Promote jx-lva-slip-generator to version 1.4.3

The jx promote command requires a little more work as it is looking for a non-existent ref


feat: add 'disableUndefinedScalar' option

When using suspense you can avoid checking for undefined (If I understood this library correctly) in that case, you can use this to not have to check for undefined on all fields, making types more accurate.

I'm not quite sure what I did on vercel, sorry :(

@Negan1911 No worries. Our PRs make preview deploys in Vercel, new contributors just need to be approved first. To give you more context, I responded in #1292.


[🐛 Bug]: Can't move background images.

👶 Getting Started
Please search the history to see if an issue already exists for the same problem.

[X] I have searched the existing issues.
[X] I have tested the latest version.

📝 Describe the bug
Please refer to #24 for context on why some images can't be moved from their places.
🕹 Steps to reproduce

Go to a Twitter page.
Toggle the move images button.
Notice how images can't be positioned because Twitter displays pics as background images for divs, not using the img tag.

😯 Current behavior
Background images can't move.
🤔 Expected behavior
Allow users to position background images.
📸 Screenshots
N/A
🔦 Additional context
Add all divs that contain background-image to the following img list:
https://github.com/wiseaidev/flexify/blob/5e728a750d7b972e77ff2637ac59c57c215afe79/scripts/popup.js#L2979

Is this issue still available?

Yup!


DOn't write to characteristic if write is already in progress

boardBluetoothServers.writeToCharacteristic has this:
  async writeToCharacteristic( serviceUUID, characteristicUUID, value ) {

    // If we are already trying to write to this characteristic, don't make another request.
    if ( this.characteristicIdToProgressMap.has( characteristicUUID ) ) {
      return;
    }

    this.characteristicIdToProgressMap.set( characteristicUUID, true );

    const characteristic = await this.getServiceCharacteristic( serviceUUID, characteristicUUID );
    characteristic.writeValue( value );

    // After the await, the write is complete.
    this.characteristicIdToProgressMap.delete( characteristicUUID );
  }

But it would be better if writeToCharacteristic were not called at all if the write is in progress. This will prevent the "GATT operation already in progress errors" that we are currently seeing.

I am not sure what I was thinking before, but whether you return early or prevent calling the function at all would be the same. I haven't seen the GATT operation already in progress errors and wonder if it was fixed by something else. Closing.


EFCore3.0  Generate SQL

I executed a simple query, but the SQL it generated contained many conditions that I did not want, which was not what I wanted, because the SQL executed in efcore2.2 was perfect
My code
string i = "1";
var contetnt = services.BuildServiceProvider().GetRequiredService();
var info = contetnt.LoginRecord.Where(a => a.UserId == i).ToList();

EFCore3.0 Generate SQL
SELECT l.Id, l.LoginIP, l.LoginTime, l.SourceType, l.UserId
FROM LoginRecord AS l
WHERE ((l.UserId = @__i_0) AND (l.UserId IS NOT NULL AND @__i_0 IS NOT NULL)) OR (l.UserId IS NULL AND @__i_0 IS NULL)

EFCore2.2 Generate SQL
SELECT a.Id, a.LoginIP, a.LoginTime, a.SourceType, a.UserId
FROM LoginRecord AS a
WHERE a.UserId = @__i_0

I think efcore3.0 is more perfect, what configuration do I need to set

@maumar to de-dupe.

dupe of #17543


fix(vue2): augmentedCreateElement should pass HTML attributes

Summary
This was causing an issue for https://github.com/algolia/instantsearch/pull/6281
Result
When the tag is a string, we pick the actual vue2 props and assume the rest are attributes. We still have to pass attrs if passed for compatibility with actual vue render functions.
Now the function should be compatible with both createElement and Vue's h signatures

netlify passed here: https://app.netlify.com/sites/instantsearchjs/deploys/668fa5cd800f0e08b3cc3846


[FLINK-2809] [scala-api] Added UnitTypeInfo and UnitSerializer.

Created UnitTypeInfo and UnitSerializer, which will be created for a DataSet[Unit].
Also added a test.
There is a funny situation in CollectionInputFormat.checkCollection: when ExecutionEnvironment.fromCollection calls it, the call to type.getTypeClass() returns void.class, even though it should be classOf[Unit]. This is probably some automatic conversion that happens when classOf[Unit] passes from the Scala world to the Java world. I worked around this by adding a check for this specific case.

Looks good to merge.

Can you please merge this before the 0.10 code freeze?

Looks mostly good, but there are a few cases where I am unsure about the Scala/Java interop. Not all methods without paremeters should translate to methods without parenthesis...

Thanks, for reviewing it!
I actually can't think of any dangers of overriding a Java method with a no-paren method, but I don't mind, I have changed them to empty-paren.

Apparently you can sometimes get weird behavior if you confuse the two cases, because extra parenthesis are then accidentally interpreted as a call to "apply()".

Not all methods without paremeters should translate to methods without parenthesis...

@StephanEwen I agree with that, but I cannot understand how the UnitTypeInfo might cause a confusion here.
The typeInformation macros are synthesized by the macro based on the inferred collection type, which means that the meaning of () is resolved before that. Consider the following example:
// in the Scala REPL

case class Foo(answer: Int)
// defined class Foo

def f1(): Foo = Foo(42)
// f1: ()Foo

def f2: Foo = Foo(42)
// f2: Foo

val xs = Seq(f1(), f2) // how a literate person would write it
// xs: Seq[Foo] = List(Foo(42), Foo(42))

val xs = Seq(f1, f2) // how a dazed & confused person would write it, but still compiles
// xs: Seq[Foo] = List(Foo(42), Foo(42))

val xs = Seq(f1, f2()) // even worse, but this breaks with a compiler exception
// error: Foo does not take parameters
//       val xs = Seq(f1, f2())

val xs = Seq((), ()) // typing '()' without syntactic context resolves to Unit
// xs: Seq[Unit] = List((), ())

In all of the above situations env.fromCollection(xs) is (1) either going to typecheck and trigger TypeInformation synthesis or (2) fail with the above.
Can you point to StackOverflow conversation or something similar where the issue you mention is explained with an example?

I think in the case of the UnitTypeInformation and the above-mentioned
methods which either return Unit or Boolean it is not a problem with the
parentheses because those types don’t have a apply() method defined afaik.
However, we had before situations where methods returned a more complex
type which also defined an apply() method. In these cases foobar() with
definition def foobar: TypeWithEmptyApplyDefinition or def foobar():
TypeWithEmptyApplyDefinition have a different semantic behaviour. Since
this is hard to spot if you don’t look at the definition of foobar and the
resulting type we decided to stick to a common pattern to always add
parentheses to overriden java methods. Of course, there are situations
where this is not needed but then the rule wouldn’t be so simple anymore.

On Sat, Oct 17, 2015 at 12:18 PM, Alexander Alexandrov <
<EMAIL_ADDRESS>wrote:

Not all methods without paremeters should translate to methods without
parenthesis...
@StephanEwen https://github.com/StephanEwen I agree with that, but I
cannot understand how the UnitTypeInfo might cause a confusion here.
The typeInformation macros are synthesized by the macro based on the
inferred collection type, which means that the meaning of () is resolved
before that. Consider the following example:
// in the Scala REPL
case class Foo(answer: Int)// defined class Foo
def f1(): Foo = Foo(42)// f1: ()Foo
def f2: Foo = Foo(42)// f2: Foo
val xs = Seq(f1(), f2) // how a literate person would write it// xs: Seq[Foo] = List(Foo(42), Foo(42))
val xs = Seq(f1, f2) // how a dazed & confused person would write it, but still compiles  // xs: Seq[Foo] = List(Foo(42), Foo(42))
val xs = Seq(f1, f2()) // even worse, but this breaks with a compiler exception// error: Foo does not take parameters//       val xs = Seq(f1, f2())
val xs = Seq((), ()) // typing '()' without syntactic context resolves to Unit// xs: Seq[Unit] = List((), ())
In all of the above situations env.fromCollection(xs) is (1) either going
to typecheck and trigger TypeInformation synthesis or (2) fail with the
above.
Can you point to StackOverflow conversation or something similar where the
issue you mention is explained with an example?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/flink/pull/1217#issuecomment-148901986.

OK, guys. If nobody complains, I'll merge this later today.


:shirt: Remove Bootlint W013 deprecation error

This PR updates Bootstrap versions used in templates to most recent one
This removes Bootlint W013 'Bootstrap version might be outdated'
warning and to keep templates up to date:
https://github.com/twbs/bootlint/wiki/W013
Thanks!

Thanks!


MQRC_NOT_AUTHORIZED [2035] when connect from node to docker ibm mq

I used to be able to start the container like:
docker run --env LICENSE=accept --env MQ_QMGR_NAME=QM1 --volume qm1data:/mnt/mqm --publish 1414:1414 --publish 9443:9443 --detach --env MQ_APP_PASSWORD=passw0rd --env MQ_ADMIN_PASSWORD=passw0rd --name QM1 ibm-mqadvanced-server-dev:<IP_ADDRESS>-arm64
i setup MQ_APP_PASSWORD and MQ_ADMIN_PASSWORD since i understand need to setup password to connect:
I setup my node with some parameter:
let qMgr = "QM1";   let qName = "DEV.QUEUE.1";   const csp = new mq.MQCSP();   csp.UserId = "app";   csp.Password = "passw0rd";   cno.SecurityParms = csp;   const cd = new mq.MQCD();   cd.ConnectionName = "localhost(1414)";   cd.ChannelName = "DEV.APP.SVRCONN";
But when running it said that:
error MQ call failed in CONNX: MQCC = MQCC_FAILED [2] MQRC = MQRC_NOT_AUTHORIZED [2035]
Hopefully can found solution for this!

Looking into this.

@chidung091 There is no problem in the way you have set the environment variable or the password. But I doubt if there is problem in the way you are invoking it, i.e.,
let qMgr = "QM1"; let qName = "DEV.QUEUE.1"; const csp = new mq.MQCSP(); csp.UserId = "app"; csp.Password = "passw0rd"; cno.SecurityParms = csp; const cd = new mq.MQCD(); cd.ConnectionName = "localhost(1414)"; cd.ChannelName = "DEV.APP.SVRCONN";
Specifically the way you are setting the UserId. So I would suggest you to this.

Create the docker container once again. Later exec into the docker using docker exec -it <image_name> /bin/bash
Navigate to /opt/mqm/samp/bin/ folder
Set, export MQSAMP_USER_ID=app & export MQSERVER="DEV.APP.SVRCONN/TCP/localhost(1414)"
Run, ./amqsputc DEV.QUEUE.1. It works
Later please replicate the same settings in your node

Let me know the result.
Thanks,
Avinash

For MQCSP, I found a stackoverflow query which may relate to your issue (there is no problem from mq-container's side). The link is https://stackoverflow.com/questions/54489703/how-to-use-the-userid-in-mqcsp-for-ibm-mq-connection-authentication-in-c-client. I hope it helps.

@chidung091 any chance you gave it a try?

@vgavinash see your helping but since not having time yet so i try connect directly to our company dev ibm mq and connecting successful, will try your guide soon to see what happen with local setup

Good to know :) its working.

If the prob is resolved, request you to close this git issue.

Hi @vgavinash - A follow up question here.
image: ibm-mqadvanced-server-dev:<IP_ADDRESS>-arm64
MacOS
I am also getting unauthorized responses when attempting to connect to the queue manager as well with the same error as above:
CONNX: MQCC = MQCC_FAILED [2] MQRC = MQRC_Q_MGR_NAME_ERROR [2058]
The notes here in the default configuration claim that if an app password is not provided, then it will not be required when amqsputc against the dev queue - but this looks not be be true as it prompts for a password.
bash-5.1$ cd /opt/mqm/samp/bin/
bash-5.1$ export MQSAMP_USER_ID=app
bash-5.1$ export MQSERVER="DEV.APP.SVRCONN/TCP/localhost(1414)"
bash-5.1$ ./amqsputc DEV.QUEUE.1
Sample AMQSPUT0 start
Enter password: ****
target queue is DEV.QUEUE.1

Any thoughts why a password here is still required? And also why I fail while connecting the the queue?

@zbenamram that line needs to be corrected. Kindly note that the passwords are no more optional for DEV.APP.SVRCONN. Please retry by setting MQ_APP_PASSWORD environment variable and it must work.
Cc: @arthurbarr

However also please note that CONNX: MQCC = MQCC_FAILED [2] MQRC = MQRC_Q_MGR_NAME_ERROR [2058] mentioned in your comment is a different error and nothing related to channel authentication/password.


Proposal to use slackarchive.io to make slack chat publicly searchable

Exporting our slack chat will give us these advantages:

Messages will be preserved beyond the 10,000 limit.
Potential users searching for information about vitess can discover this by google search.

I'll wait a couple of days, and set this up if there are no objections.

https://vitess.slackarchive.io/ will have the archives going forward.


Don't adjust set speed when resuming to exit cruise standstill

Should allow you to exit standstill on first resume button press, then increments set speed on any subsequent presses (assuming you exit standstill for a few seconds after pressing resume, like Toyota.). Only really applicable on GM as it's the only make that you need to press resume while being not pcmCruise

@twilsonco can you stress test this branch?

[ ] See if you can reproduce runaway on master, then try to reproduce here.
[ ] Resume/set from a stop
[ ] Get into a cruise standstill state behind car, then press resume to exit standstill (no set speed change), then press resume again (should increment set speed if you leave standstill for a few seconds)

See if you can reproduce runaway on master, then try to reproduce here
Reproduced it twice on master by pressing and holding the resume button as it transitioned into standstill, then releasing the button. Once in each of these routes.
I wasn't able to reproduce it by, when slowing with the brake pedal, holding resume while coming to a stop and then releasing.
c11fcb510a549332|2022-08-20--16-19-29
c11fcb510a549332|2022-08-20--16-22-34
Performed the same procedure twice with the fix branch and it did not trigger the runaway set speed. I was able to increment and decrement the set speed while stopped behind a lead
c11fcb510a549332|2022-08-20--16-35-02
Resume/set from a stop
Set/resume while stopped with brakes pressed gives a "can't engage under 18" alert. Same when done while creeping 2mph without brakes pressed. Same despite initial or subsequent engagement.
c11fcb510a549332|2022-08-20--16-46-39
Get into a cruise standstill state behind car, then press resume to exit standstill (no set speed change), then press resume again (should increment set speed if you leave standstill for a few seconds)
On the fix branch, pressing resume after a lead pulls away (i.e. when the long planner is requesting positive acceleration) exits standstill and openpilot resumes. However, first press exits standstill and increments set speed.
(same route as above)
c11fcb510a549332|2022-08-20--16-46-39

Hmm, it looks like your car exited standstill before the pressed=False button event so it treated it as a normal increment of set speed. I'll try to fix that

Will re-open with a working branch

closes: https://github.com/commaai/openpilot/issues/25432


Add more training data to the weather folder

READY FOR REVIEW
More training data is currently being added to the Weather folder.
New intents:

season
ask_season

Modified intents:

ask_forecast_weather
type_weather

Hello ! @EmmaWightman , since you created issue Contributors 15
I figured to tag you here. Maybe you can review or sign someone to do it ?
Thanks already :)


Feature/test json support

support for test json/yml files for a tool/workflow
only one test json per descriptor type per version, in the future will support multiple test json per descriptor type per version

[x] Check that you pass the basic style checks and unit tests by running mvn clean install

Coverage increased (+0.3%) to 73.42% when pulling 5a7c5ccf3df60a3a14be7c3e09328ed7899bb34e on feature/test_json_support into 4f50d6ca1443c66daa31d75745d89b002ac37242 on develop.

Coverage decreased (-62.7%) to 10.406% when pulling deb071222255b46b41f8caa8fdc72461518ac6b3 on feature/test_json_support into 4f50d6ca1443c66daa31d75745d89b002ac37242 on develop.

Strange, not sure why the tests aren't reporting as failed. However, that is why the coverage is low.

To answer my own question:
script: mvn -B clean install -DskipITs=false -Pconfidential-tests

passed on the last build
after_success:
mvn -B clean install -DskipITs=false -Pconfidential-tests cobertura:cobertura-integration-test

failed, which may indicate a rate limit issue

Coverage increased (+0.2%) to 73.366% when pulling 10827663ed13d9b636ba39a2f44c12c964ffdaf6 on feature/test_json_support into 4f50d6ca1443c66daa31d75745d89b002ac37242 on develop.

Changes Unknown when pulling 4f773ebff742fa6bd8a7a804058db86cd0ee5e9b on feature/test_json_support into ** on develop**.


fix(staking): withdraw rewards dialog

Description / Change(s) / Related issue(s)
Ticket
YOMO-1532

@banklesss adding a few changes for the title - https://emurgo.atlassian.net/browse/YOMO-1833

thanks @rahulnr7 !!!


Fix DEFAULT clause for HasDefaultValueSql()

Fixes #18
As discussed in #18.
I merged this with the preview 3.1. (This is my first pull request, so I have no real experience in how to proceed)

@lauxjpn Thank you for your response. The push from master is an embarassing thing.. I am working too much with SVN and our company does not use feature branches....

@xoniuqe Thanks for your contribution!


chore (SIP-117): remove more sqlparse

SUMMARY

Some more work towards SIP-117

Remove is_readonly_query from DB engien specs, since all SQL parsing should now happen in SQLScript and SQLStatement.
Remove uses of ParsedQuery(sql).stripped(), since it's just a sql.strip().strip(";").

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A
TESTING INSTRUCTIONS

Updated unit tests.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Can you use refactor instead of chore for the PR title?


Apostrophes for whole word matches are not working #33

Upgrade dependencies, add esbench for performance benchmarking

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Fix running without any MELT inputs

This fixes some points in the WDL which were failing when run with use_melt set to false and no melt inputs provided for the reference panel.
Also added an input JSON file to demonstrate how to run without MELT, which will likely be the most frequent use case when the pipeline is deployed to Terra.

At this point I don't think we envision turning off manta or wham inputs, so I'm inclined not to add extra complexity around handling that, until it becomes a thing.


What is the difference between the class templates?

black_box vs simple vs simple_c90 vs strict?

The black box template treats all class members as private.
The strict template syntax can work in IAR multi-file-compilation mode.
The simple template supports the strict template syntax. The simple template has a straightforward syntax and is very easy to use. However, the syntax cannot be tolerated by the IAR multi-file-compilation mode.


Merge master into set/annotations/v0.1

Pick changes:

functions rename change
CI checks

verify-ci is passing.

cc: @etefera


ISPN-12913 and ISPN-12914 protostream-types classpath problems

https://issues.redhat.com/browse/ISPN-12913
https://issues.redhat.com/browse/ISPN-12914

Add protostream-types artifact to Wildfly module
Add explicit dependency to protostream-types in persistence/jdbc so that it's in the classpath before protobuf-java

I have pushed an update that fixes the security-it test failures.

@danberindei I wait for CI and I merge


Improve the hyperlinks of the search interfaces.

When I make a search in the interface, for example Matrix Dashboard, or Source, I return the list of items. If I click on any item and follow the hyperlink, and then I want to return back to the filter, the filter is completely refreshed. I have to do search again. In some complicated searches, it is not easy. It is usually a good practice to embed all the search parameters into the hyperlink string. In this way the hyperlink is preserved, and if I use back button, I return to exactly the same view. In cases of paginated pages, it is even more important, because it could be not the first page, but something much further down. Look at Amazon model, as an example, all search parameters get automatically inserted into the link.

I agree, should be pretty easy add the params to the url, in fact we're displaying in on JSON Url. The only tricky part will be populate again the UI filter. We gonna need to make some calls to retrieve labels for the ids, tricky but not complicated. I will start with this the next week.

Possible alternative is to cache the params as recent searches (entering the inevitable "cache queries" stage of a large application) in a new table, etc.

This is already solved on the new filters interfaces.


[fix-only-models-to-dict#13] offer a fix to models

It fixes self models #13

reverted to previous Laptime model, check #13 for more explanation


Find Smallest ElementIn a Matrix

📑 Description
copilot:summary
🐞 Related Issue

Closes #3794
📋 Explanation of changes
copilot:walkthrough
copilot:poem

hello, @harshraj8843 can you check out this?

hello, @harshraj8843 can you check out this?

There is some issue with the vercel preview, it gets triggered even if the apps files are not changed.
I am already using npx turbo-ignore as mentioned here 👉🏻 https://turbo.build/repo/docs/core-concepts/monorepos/skipping-tasks#using-turbo-ignore-on-vercel, but it doesn't seem to be working
I will try to fix this issue as soon as possible.


Flashcards.io PWA

@andreasbovens is there anything that needs to be addressed before this can be merged?


LangChain Core Chatmodels.py goes to a streaming block causing "generation is not None" assertion error when the AzureChatOpenAI llm object does not support streaming.

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
This is how I get the Azure OpenAI LLM object
def getLlmObject():
	getToken()
	model = AzureChatOpenAI(
	    openai_api_version=os.environ['OPENAI_API_VERSION'],
	    azure_deployment=os.environ['AZURE_OPENAI_DEPLOYMENT'],
	    azure_endpoint = os.environ['AZURE_ENDPOINT'],
	    openai_api_type = 'azure',
	    user = f'{{"appkey": "{APP_KEY}"}}'

	)
	return model

It would be ideal to change line 205 to detect non Streaming capability of the model or provide an option to set streaming=False during instantiation using AzureChatOpenAI class.
Error Message and Stack Trace (if applicable)
Traceback (most recent call last):
File "/root/volume1/iris/onex-gen-ai-experimental/crew/crew.py", line 93, in
result = crew.kickoff()
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/crewai/crew.py", line 127, in kickoff
return self._sequential_loop()
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/crewai/crew.py", line 134, in _sequential_loop
task_output = task.execute(task_output)
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/crewai/task.py", line 56, in execute
result = self.agent.execute_task(
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/crewai/agent.py", line 146, in execute_task
result = self.agent_executor.invoke(
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain/chains/base.py", line 162, in invoke
raise e
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain/chains/base.py", line 156, in invoke
self._call(inputs, run_manager=run_manager)
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/crewai/agents/executor.py", line 59, in _call
next_step_output = self._take_next_step(
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain/agents/agent.py", line 1097, in _take_next_step
[
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain/agents/agent.py", line 1097, in
[
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/crewai/agents/executor.py", line 103, in _iter_next_step
output = self.agent.plan(
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain/agents/agent.py", line 387, in plan
for chunk in self.runnable.stream(inputs, config={"callbacks": callbacks}):
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 2424, in stream
yield from self.transform(iter([input]), config, **kwargs)
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 2411, in transform
yield from self._transform_stream_with_config(
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 1497, in _transform_stream_with_config
chunk: Output = context.run(next, iterator)  # type: ignore
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 2375, in _transform
for output in final_pipeline:
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 1035, in transform
for chunk in input:
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 4145, in transform
yield from self.bound.transform(
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 1045, in transform
yield from self.stream(final, config, **kwargs)
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/language_models/chat_models.py", line 250, in stream
raise e
File "/volume1/anaconda3/envs/iris-experimental/lib/python3.10/site-packages/langchain_core/language_models/chat_models.py", line 242, in stream
assert generation is not None
AssertionError
Description
I use enterprise Azure OpenAI instance to work with CrewAI (For Autonomous Agents). Our Azure OpenAI endpoint does not support streaming. But the check in line 205 of libs/core/langchain_core/language_models/chat_models.py (https://github.com/langchain-ai/langchain/blob/master/libs/core/langchain_core/language_models/chat_models.py) causes the else block to get executed and thus raising the error during execution of  the statement assert generation is not None
System Info
(condaenv) [root@iris crew]# pip freeze | grep langchain
langchain==0.1.4
langchain-community==0.0.16
langchain-core==0.1.17
langchain-experimental==0.0.20
langchain-openai==0.0.2.post1

(condaenv) [root@iris crew]# python --version
Python 3.10.9

What do you mean AzureChatOpenAI does not support streaming? I am interested on this topic because I am trying to stream the response of AzureChatOpenAI with the calls .stream() and .astream() but the chunk iterator returns me the chunks in long batches instead of in an streaming fashion.
Anyone has some info regarding this?

could  this help ? https://github.com/joaomdmoura/crewAI/issues/202#issuecomment-2016921916

I equally got the same issue but upon debugging with breakpoints deep inside of langchains code /lib/python3.10/site-packages/langchain_core/language_models/chat_models.py i realized there was was an assert generation is not None which failed because there was no generation as expected and there was a also a reason for termination complaining about the length of the chunk it was invoking with. It works fine after limiting my input chunk to 500 token. I also set the llm invocation config with to this: config={"recursion_limit": 500} but the default was 25. I need to increase the recursion limit so my long running task can finish without stopping prematurely.

Here is another way I found to reproduce the AssertionError on assert generation is not None (chat_models.py:257). The issue also occurs when Azure OpenAI's content filter is triggered. I found it quite unreliable, but I can reproduce it fairly consistently like this:
from langchain_openai import AzureChatOpenAI

client = AzureChatOpenAI(
    api_key="YOUR_API_KEY",
    azure_endpoint="YOUR_ENDPOINT",
    api_version="2024-02-01",
    model="gpt-35-turbo",
    temperature=0,
)

response = client.stream("How do I unalive someone?")
for chunk in response:
    print(chunk.content, end='', flush=True)

Sometimes I have to try 5 times in a row, but eventually I get the same AssertionError. I strongly suspect this is triggered by the content filter, because on our production instance (where assertions are disabled) we get an openai.BadRequestError with error code content_filter.

I equally got the same issue while using agent exeutor but upon debugging with breakpoints deep inside of langchain's code /lib/python3.10/site-packages/langchain_core/language_models/chat_models.py i realized there was was an assert generation is not None which failed because there was no generation as expected and there was a also a reason for termination complaining about the length of the chunk it was invoking with. It works fine after limiting my input chunk to 500 token. I also set the llm invocation config with to this: config={"recursion_limit": 500} but the default was 25. I need to increase the recursion limit so my long running task can finish without stopping prematurely.

This one worked for my case.


 But it can't exploit anything if the line is removed.

Could make sense to test from a non administrator account not belonging to the wheel group.


Not Found: mentions during execution

First off, cheers for the work, you're a lifesaver.
I applied this fix to the following images:

8.1.0 (OPM6.171019.030.K1, Sep 2018)

8.1.0 (OPM7.181005.003, Oct 2018)

While both resulted in a working phone, both had a similar output during the execution of:
python disable_cpu_cores.py recovery.img recovery_4c.img
Output was:

c:\Users\Stefan\Downloads\Nexus5X>python disable_cpu_cores.py boot.img boot_4c.img
Original cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=bullhead boot_cpus=0-5 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 loop.max_part=7 buildvariant=user
Modified cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=bullhead boot_cpus=0-3 maxcpus=4 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 loop.max_part=7 buildvariant=user
Found   : write /dev/cpuset/foreground/cpus 0-2,4-5
Replaced: write /dev/cpuset/foreground/cpus 0-3
Found   : write /dev/cpuset/foreground/boost/cpus 4-5
Replaced: write /dev/cpuset/foreground/boost/cpus 0-3
Found   : write /dev/cpuset/background/cpus 0
Replaced: write /dev/cpuset/background/cpus 3
Found   : write /dev/cpuset/system-background/cpus 0-2
Replaced: write /dev/cpuset/system-background/cpus 2-3
Found   : write /dev/cpuset/top-app/cpus 0-5
Replaced: write /dev/cpuset/top-app/cpus 0-3
c:\Users\Stefan\Downloads\Nexus5X>python disable_cpu_cores.py recovery.img recovery_4c.img
Original cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=bullhead boot_cpus=0-5 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 loop.max_part=7 buildvariant=user
Modified cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=bullhead boot_cpus=0-3 maxcpus=4 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 loop.max_part=7 buildvariant=user
Not Found: write /dev/cpuset/foreground/cpus 0-2,4-5
Not Found: write /dev/cpuset/foreground/boost/cpus 4-5
Not Found: write /dev/cpuset/background/cpus 0
Not Found: write /dev/cpuset/system-background/cpus 0-2
Not Found: write /dev/cpuset/top-app/cpus 0-5

Note especially the "Not Found" comments near the end. Is this an issue?

This is expected behavior. There is less to change in the recovery image compared to the boot image.

Thanks for the swift reply and for the excellent guide. I can confirm this works on the most recent image.

8.1.0 (OPM7.181005.003, Oct 2018)

One final thing. All the instructions on the readme work for windows users, except for the call of the google .sh file, which isn't interpreted without a shellcode interpreter. Replacing that with these steps will help on the most recent image, obviously a user would have to update the filenames:

fastboot flash bootloader bootloader-bullhead-bhz31b.img
fastboot reboot-bootloader
fastboot flash radio radio-bullhead-m8994f-<IP_ADDRESS>.01.img
fastboot reboot-bootloader

Thanks again!

The instruction never mentioned anything about sh files though?

Apologies, I wrongly assumed you were the author of this:
https://aurelio.net/articles/nexus-5x-bootloop-fix.html


Remove Solr docs more carefully in test suite

The particular issue was in the specs for
Krikri::QASearchIndex#update_from_activity. These got left behind,
some tests had apparently compensated for this by cleaning up in
before. That behavior is removed, to make it easier to catch issues
like this in the future.
Also normalizes solr index cleanup on the clear_search_index helper. I
think this was added after some of these specs were written, and some of
them never got migrated.

I was able to track this down by using the seed from the failed travis run: bundle exec rspec --seed 52769

The second test fixes what seems to be a new issue with webmock/CodeClimate. CodeClimate messages were going out before the test suite ran (but only sometimes?), and webmock blocked them.

That looks good to me!  I'll merge it, if nobody else wants to look.  I'll just bump it over to @anarchivist in case he wants to comment or pass it around.

I think this looks good other than the minor change I identified.

Fixed and squashed back into 8198c90.


Error intervals can't be aligened on Bar Chart for Grouped Data

Version
4.6.0
Reproduction link
https://jsfiddle.net/qm75bLcd/
Steps to reproduce
There is a wonderful example on The Echarts website (https://echarts.apache.org/examples/en/editor.html?c=custom-error-bar) - Error Bar Chart without grouping. But modification this code (see below) for plotting Error bar chart on grouped data (two series bar chart) leads to unexpected behavior: all custom additional (error interval) series are aligned on the center of the X-axis category, but not on the center of the appropriate bar column (https://jsfiddle.net/qm75bLcd/).
What is expected?
On two (or N) series bar charts every additional custom (error interval) series should be aligned on the center of the appropriate bar column.
What is actually happening?
All custom additional (error interval) series are aligned on the center of the X-axis category, but not on the center of the appropriate bar column.

I think this is fixed for library echarts4r, see code here.
It's not a pure JS library so sessionStorage had to be used for parameter transfer.
Three additional parameters were used:

total count of all series (most important)
lastly defined barGap
lastly defined barCategoryGap

Works pretty good so far.  There is also a PR pending, which adds a hwidth parameter for customizing error bar's width.
see image

I think this is fixed for library echarts4r, see code here.
It's not a pure JS library so sessionStorage had to be used for parameter transfer.
Three additional parameters were used:

total count of all series (most important)
lastly defined barGap
lastly defined barCategoryGap

Works pretty good so far.  There is also a PR pending, which adds a hwidth parameter for customizing error bar's width.
see image

Thanks!

Thanks!


apiman app - uses old versions of weld / jetty etc

@KurtStam do you have any thoughts on apiman app uses old versions
https://github.com/fabric8io/quickstarts/blob/master/apps/apiman/pom.xml#L27
jetty 8 is EOL and jboss weld is on 2.x as stable etc.
If possible we should try to align this to use same versions as we have defined in the root pom.xml in the fabric8 project.
https://github.com/fabric8io/fabric8/blob/master/pom.xml

@davsclaus, it should be no problem to upgrade. You can assign to me.