add enable-node-pool parameter for yurthub in order to disable nodepools list/watch in filters when testing.

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

/kind enhancement
What this PR does / why we need it:
add a --enable-node-pool parameter for yurthub component. by setting  up --enable-node-pool=false for disabling nodepools list/watch in filters so local-up-openyurt.sh can work when nodepools resource doesn't exist in cluster.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

/assign @Congrool
Does this PR introduce a user-facing change?

other Note

It looks strange to have an API-related option at the edgenode-side. It's more suitable to diable the module that uses the nodepool resource. It looks like ingressControllerFilter and serviceTopologyFilter use nodepool resource. How about adding option --disable-filters instead of the --enable-node-pool?

@Congrool Thanks for your feedback. we already have --disable-filters parameter. In this case(start local-up-openyurt.sh, yurt-app-manager will not be installed) we don't want to disable serviceTopology filter, we only want to disable service traffic inclose of pool topology only, so we can continue use service traffic inclose in node topology ability. so a new parameter --enable-node-pool is added.

/lgtm


[multimodal] Update torchmetrics map

Use latest implementation if torchmetrics.__version__ > 0.11.0
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Shall we just upgrade torchmetrics (make it >=0.11.0?) I think @zhiqiangdon mentioned that there is another issue about pos_label

Shall we just upgrade torchmetrics (make it >=0.11.0?) I think @zhiqiangdon mentioned that there is another issue about pos_label

I think 0.11.0 is not ok for map since the bug is fixed in 0.11.1. I update this so that we don't need to force the version >=0.11.1.

Code looks good. One question, after switching to using torchmetrics 0.11.0, will performance on several datasets/tutorials change?

I tested the two versions of map implementation on two datasets and they performs similarly. I haven't done a speed analysis on heavy task but the latest one is at least not slower than the previous one.

Tried on COCO17 val split. Both implementations output the same result for checkpoint_name = yolov3_mobilenetv2_320_300e_coco and in about the same time (0.11.1 takes 340 seconds and previous one takes 352 seconds). @bryanyzhu @sxjscience

Do we need to directly upgrade torchmetrics so that the logic can be more clean.


Unable to use and initialize nvim configuration

Error content

After press enter:

Basic configuration
system:macos 13.2
package manager:homebrew
neovim version:0.8.2
lua version:5.4.4

Looks like your using a self-compiled nvim which lack of some necessary functions. Reinstall a github-compiled nvim and try it again.

My previous neovim was installed through homebrew. Now I try to download the compiled version (compressed package) on github but still have the same problem below：

Vimspector unavailable: Requires vim compiled with +python3
I think your using a apple-silicon machine. Search that error then your might found a way out.

side note: @Jint-lzxy we might need to update our issue template for apple silicon machines.

My previous neovim was installed through homebrew. Now I try to download the compiled version (compressed package) on github but still have the same problem below：

https://github.com/ayamir/nvimdots/issues/445#issuecomment-1407387208

It seems that our problems are somewhat different, I don't have the lazy package manager.

And I'm using the latest version of the configuration.

I tried some methods on the Internet but none of them solved this problem.
Vimspector unavailable: Requires vim compiled with +python3
This error seems not to be the point. I used the old version of nvim configuration (packer) before, and occasionally the same error will appear after updating the plugin, but the overall use is no problem.

lazy.nvim haven't start it's bootstrap due to this part:
https://github.com/ayamir/nvimdots/blob/e34a73c6db055cef1693086446683a9bc4674768/init.lua#L4-L14
Which called vimspector at the very first and blocking the entire lazy bootstrap.

I guess:

u might have left older version of nvim uninstalled.
apple silicon issues.

It seems that our problems are somewhat different, I don't have the lazy package manager.  And I'm using the latest version of the configuration.

lazy.nvim will bootstrap itself when you nvim for the first time like below picture:

It seems that our problems are somewhat different, I don't have the lazy package manager.  And I'm using the latest version of the configuration.

lazy.nvim will bootstrap itself when you nvim for the first time like below picture:

I didn't get the guide as shown in the picture.The problem may be that an error occurred when vimspector was called first.

It's because the clone of lazy.nvim failed. So it showed you Shell 已返回129. The key problem is your git version maybe too old and it doesn't support git clone --filter=blob:none --branch=stable instruction.

I guess:

u might have left older version of nvim uninstalled.
apple silicon issues.

If u tried anything to solve it, please state it in this issue so we can have a better idea of the problem. Otherwise we don't know how to help u.

The most common solution on the Internet is：
pip3 install neovim

Use this command to configure the python3 environment on neovim.But it didn't work for my problem.

It's because the clone of lazy.nvim failed. So it showed you Shell 已返回129. The key problem is your git version maybe too old and it doesn't support git clone --filter=blob:none --branch=stable instruction.

Thanks, it's the git version problem, after I use homebrew to update the git version, the problem is solved.

side note: @Jint-lzxy we might need to update our issue template for apple silicon machines.

@CharlesChiuGit No, FWIW it has nothing to do with chips. For what I can tell Homebrew has almost fully supported Apple Silicon. There should be no case where source code is the same but machine code is interpreted differently :)

lazy.nvim haven't start it's bootstrap due to this part:
https://github.com/ayamir/nvimdots/blob/e34a73c6db055cef1693086446683a9bc4674768/init.lua#L4-L14
Which called vimspector at the very first

It has nothing to do with vimspector. In fact, this config does not require vimspector at all. I suspect that legacy plugins were still loaded (via native package mgr) as the author did not completely clean up previous installation.
This warning message is issued by vimspector itself:
if !has( 'python3' )
  augroup VimspectorNoPython
    autocmd!
    autocmd VimEnter *
          \   echohl WarningMsg
          \ | echom 'Vimspector unavailable: Requires Vim compiled with +python3'
          \ | echohl None
  augroup END
  finish
endif

and blocking the entire lazy bootstrap.

Hmm but this is the exact reason for using vim.schedule instead of just calling the function:
:h vim.schedule

vim.schedule({callback})                                      *vim.schedule()*
    Schedules {callback} to be invoked soon by the main event-loop. Useful
    to avoid |textlock| or other temporary restrictions.

It will wait until all resources are available before attempting to run this function 😄

I realize it now! Much thanks to the elaborate explanations!

@CharlesChiuGit There's an awesome video where TJ explains vim.schedule. 👍

Actually I had saw that video already lol
I just blindly guessing around, sorry for the miss-leading!

@CharlesChiuGit There's an awesome video where TJ explains vim.schedule. 👍

Actually I had saw that video already lol I just blindly guessing around, sorry for the miss-leading!

No worries, happens to the best of us 🍻

I am meeting the same problem, upgrading git didn't solve it.

@Dennis-Zhang-SH r u using nvim0.9?

Yes, somehow the git in the ~/.local/share/nvim/lazy messed up, I manually delate&update the repo and then it works.


Simplify the Readme.

The first sentence should be a 25-word description of WHAT THIS GEM DOES.
The second sentence may be a 25-word description of HOW IT DOES IT. The big picture.
And only then the rest of Readme (what it integrates with, the options, the settings etc.).
Ideally, it should be a website with a new page for each section.
Request for contributions goes to the bottom.

@zoopyserg Wow, you must be a very lovely person to deal with.


Update for new endpoints

Tesla has moved quite a bit around on the API with the release of 6.0 and the latest apps. There are a couple new endpoints and most have been moved around.
The server has switched to owner-api.teslamotors.com and there is certificate pinning in the apps, making sniffing via proxy more difficult. I may try poking around with APK Studio to see if I can remove the pin or have it trust a different cert.
Changes

[ ] Update server to owner-api.teslamotors.com
[ ] New /command/ endpoints

[ ] charge_max_range
[ ] charge_standard
[ ] sun_roof_control
[ ] flash_lights
[ ] honk_horn
[ ] door_lock
[ ] charge_port_door_open
[ ] trunk_open
[ ] remote_start_drive
[ ] upcoming_calendar_entries
[ ] set_temps
[ ] charge_start
[ ] auto_conditioning_start
[ ] charge_stop
[ ] auto_conditioning_stop
[ ] door_unlock

[ ] New /data_request/ endpoints

[ ] charge_state
[ ] climate_state
[ ] drive_state
[ ] gui_settings
[ ] vehicle_state

[ ] Misc vehicle endpoints

[ ] wake_up
[ ] mobile_enabled

[ ] notification_preferences
[ ] vehicle_subscriptions

Hi - also
https://owner-api.teslamotors.com/api/1/vehicles gives a list of vehicles on the acount as far as I can tell. Empty if there are none yet.
What is the full URL of the vehicle_subscriptions endpoint and what does it do?


Inteliphense format clear all marks

Description
If create a mark example, ma...
... and Format file :Format
all marks are removed

This only happens when formatting the file and only with inteliphense, this does not happen with anything else.

my solution:
I used Inteliphense through Mason, I uninstalled it and started using PHP Actor, it's perfect.

there is no format command check you plugin first please


Add test coverage for existing backend code

Upon some digging into Rust testing and trying to do this, making the executive decision this is a nightmare and not a rabbit hole worth venturing down. Closing.


Update .NET 9 Preview to .NET 9

Fixes #34263
Internal previews

📄 File
🔗 Preview link

aspnetcore/fundamentals/aot/native-aot-tutorial.md
Tutorial: Publish an ASP.NET Core app using Native AOT

aspnetcore/test/http-files.md
Use .http files in Visual Studio 2022

aspnetcore/tutorials/first-mvc-app/start-mvc.md
Get started with ASP.NET Core MVC

aspnetcore/tutorials/min-web-api.md
Tutorial: Create a minimal API with ASP.NET Core

aspnetcore/tutorials/razor-pages/razor-pages-start.md
Tutorial: Get started with Razor Pages in ASP.NET Core

Thanks @timdeschryver


Addressing Issue #152 and adding link to dev guide from contributing.md

lgtm.  Need to check to make sure we don't need the CLA signed (I'm pretty sure we don't, but I need to ask)

I'm a Tableau employee so I'm pretty sure I already am covered.

Hah, oops, didn't realize who you are!


cleanup: removed typechain-types folder

typechain-types should not be pushed to git, as mentioned in .gitignore file.

ty!


Show Past Ensembles for members in Descending order

When we switched to the new layout for the member registration page, I forgot that I wanted the adapter to sort them in descending (new-->old) order.

Should also sort Upcoming Ensembles in ascending (oldest-->newest) order.


Clear notebook cell output has no effect

Refs: #93742

Have the following cell and execute it

label:debug repo:microsoft/vscode milestone:"March 2020" sort desc by comments

Click on the "Clear Notebook Cell Output" - no effect 🐛
Click on the "Clear All Notebooks Cell Output" - works

Fixed via https://github.com/microsoft/vscode/commit/563997c6de826b77a28181927ad5822c904438d0


Add dark mode in inheritance flow

Feature Description
Add dark mode in inheritance flow.

not in 1.2.6 (344)

Completed


helm trust path for new signing key

Output of helm version: N/A
Output of kubectl version: N/A
Cloud Provider/Platform (AKS, GKE, Minikube etc.): N/A
Yo,
With the release of 3.10.3 there is a new key doing releases. I can't seem to find any trust path between @mattfarina and @hickeyma and would appreciate if this could be resolved.
If Matt could sign Martins key, or if Matt could publish a signed statement about this key, that would be preferable.
Thanks!

Closing as duplicate of #11596

@joejulian how is this a duplicate of that issue?

Re-opening as this is not really a duplicate of #11596
@Foxboron Are you able to find my key in https://github.com/helm/helm/blob/main/KEYS?

Refer to #6093 for more details.

@hickeyma I have no clue how I have missed this file :/ sorry.
I'd like if commits with key additions where properly signed with something that is not Githubs signing keys, preferably by an existing keyholder as well.  Or the file itself signed by one of the older keys in the file.
Validating additions would require the github pull-request history and I don't think that is necessarily great if we consider VCS compromises.

Do you have specific ways that we can improve the process?

Yes,
The addition of a new release key should only be added with a signed commit from an existing release key. This can either be the existing release manager adding the key, or a locally signed merge commit.
The subsequent release should also be done by an existing manager, not the newly added key.
If there is a supply chain attack that compromises the build server + vcs repository, they can do seemingly legitimate releases by adding a new key and it would be indistinguishable from the existing release manager keys. The current model also assumes the github pull-request history is always going to be present to validate any commits that adds new release manager keys. If we only have the git checkout there is no chain of trust from an existing release manager to a new release manager.
I haven't found a release where a new release manager cuts the release after being added, but I don't see any such notes in the checklist either.


Feat multi undo log builder

What this PR does:
Which issue(s) this PR fixes:

Fixes #300
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

先合并PR：https://github.com/seata/seata-go/pull/289，再合并本PR

Codecov Report

Merging #301 (7fcb713) into master (c272389) will decrease coverage by 1.30%.
The diff coverage is 18.78%.

@@            Coverage Diff             @@
##           master     #301      +/-   ##
==========================================
- Coverage   56.83%   55.53%   -1.31%
==========================================
  Files          83       83
  Lines        4094     4217     +123
==========================================
+ Hits         2327     2342      +15
- Misses       1627     1736     +109
+ Partials      140      139       -1

Impacted Files
Coverage Δ

pkg/datasource/sql/async_worker.go
35.65% <ø> (ø)

pkg/util/fanout/fanout.go
87.30% <ø> (ø)

...e/sql/undo/builder/mysql_multi_undo_log_builder.go
2.66% <2.66%> (ø)

.../sql/undo/builder/mysql_update_undo_log_builder.go
29.90% <25.00%> (-5.54%)
:arrow_down:

.../sql/undo/builder/mysql_delete_undo_log_builder.go
40.57% <26.31%> (-1.24%)
:arrow_down:

pkg/datasource/sql/parser/parser_factory.go
62.79% <52.17%> (-11.41%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Channels.connect endpoint requires a token parameter which is not needed for connecting a chatplugin channel

curl -H "Content-Type: application/json" -H "Authorization: $token" -d \
"{ \
    \"source\": \"chat_plugin\", \
    \"source_channel_id\": \"my-chat-channel-1\", \
    \"name\": \"chat plugin source\"
}" api.airy/channels.connect

{"timestamp":1606291874857,"status":400,"error":"Bad Request","message":"","path":"/channels.connect"}%

Nice catch, I think we should make it required depending on the source? I'm not sure how comfortable the code would look like (but conditionally requiring fields by source is what makes most sense from a user perspective as far as I can say)


Stable Laravel 5.1 Version

How can I get a stable 5.1 Install ?
"pingpong/modules": "2.1.*" doesn't work.

https://github.com/pingpong-labs/modules/issues/182

This package has been released for Laravel 5.1 support with new version 2.1.0. Thanks!


240 NPSP Localization - all languages

Critical Changes
Changes
Translated labels for current language set. The changes made in feature/240__Localization are reflected in this PR as well.
Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Deleted Metadata

deleted this branch in and PR in order to rename localization branch to point to main


make a cli tools like 'create-react-app'

Hello, can you please make a cli tool like 'create-react-app' to start a bootstrap project scaffold from cli.

I used to maintain a private fork of foundation's cli and I wouldn't mind teaming up with people on this.
However, CLI's are a lot of work to build and maintain...
Personally, I'd rather team up and build a feature rich extension for vscode to accomplish the same things.
MJML is a good example of what i mean,
it has a built in preview of markup, and fetch official example templates, but adding a search feature for community driven templates (similar to CRA templates) shouldn't be that hard either.

Thanks @HansUXdev

Thanks @HansUXdev

No problem @jamal-pb95. In the meantime, if you use bootstrap 5 and vscode, you may be interested in collaborating on the extension I maintain.
It's not very hard compared to a full CLI and just wraps snippets (including the example templates) of html, css, js inside json.
I've been meaning to look into upgrading it to a full extension and not just snippets by adding the command api and webview api.

No problem @jamal-pb95. In the meantime, if you use bootstrap 5 and vscode, you may be interested in collaborating on the extension I maintain.
It's not very hard compared to a full CLI and just wraps snippets (including the example templates) of html, css, js inside json.
I've been meaning to look into upgrading it to a full extension and not just snippets by adding the command api and webview api.


ENH Keyboard functionality for interactive colorbar

What does this implement/fix?
Adds keyboard functionality to interactive colorbar plotting TFRs. Until now, interactivity of the colorbar relied on mouse buttons and movements. I added +, -, pageup and pagedown that now have the same functionality.

@stfnrpplngr is there a code snippet you've been using to test this?

I used a shorted version of this example. You could use this gist.

Works great! I'll fix the conflict and merge, thanks @stfnrpplngr


update dependencies

@davidstrouk it's a little risky change.
We need to test this version with widget-server at least before merging


target rate sensor schedule change error

Describe the bug
When I edit an existing target rate sensor, it does not apply the new parameters consistently. The target hours parameter is not updating and retains the old value in the scheduling result.
Reproduction steps
Edit an existing target rate sensor. Change the number of hours and save. When you view the sensor in development tab it is still scheduling based on the old sensor.
Expected behaviour
Update the targer hours to the new vaue.
Tariff Code
agile
Integration Version
11.0
Home Assistant Version
2024.05
Fresh Install?
Not specified
Home Assistant Logs
Adding developer tools view. Previously had set 1hr and changed to 2.5hr.
icon: mdi:camera-timer
friendly_name: Octopus Energy Target home_washer_nighttime
name: home_washer_nighttime
hours: 2.5
type: Continuous
mpan: xxxx
rolling_target: false
last_rates: false
target_invert_target_rates: false
start_time: 22:00
end_time: 05:00
kind: target_rate
account_id: A-xxxx
is_target_export: false
rates_incomplete: false
target_times:

value_inc_vat: 0.090615
start: '2024-05-13T02:00:00+01:00'
end: '2024-05-13T02:30:00+01:00'
tariff_code: E-1R-AGILE-23-12-06-A
is_capped: false
value_inc_vat: 0.090405
start: '2024-05-13T02:30:00+01:00'
end: '2024-05-13T03:00:00+01:00'
tariff_code: E-1R-AGILE-23-12-06-A
is_capped: false

target_times_last_evaluated: 2024-05-12T16:16:31.900012+01:00
overall_average_cost: 0.09051
overall_min_cost: 0.090405
overall_max_cost: 0.090615
current_duration_in_hours: 0
next_time: 2024-05-13T02:00:00+01:00
next_duration_in_hours: 1
next_average_cost: 0.09051000000000001
next_min_cost: 0.090405
next_max_cost: 0.090615
last_evaluated: 2024-05-12T16:39:31.768367+01:00
weighting: 7,*
Confirmation

[X] I confirm that I cannot find my solution within the documentation
[X] I confirm that I cannot find my solution within the FAQ

Update: a reload of the integration entry seems to fix the issue.

Hello and sorry you were experiencing an issue. I believe this is tied to HA's restoration of the sensors. When I get a chance I'll see if I can make this a bit more intelligent

Ok thanks. I notice the target rate sensor sorts itself out after some time. There must be some background processing.
Low priority issue for me on that basis.

Hi, an update. I notice this issue also arises if I change the target rate sensor by calling a service. I looked into the logs and notice this entry - looks like the weighting code has an unwanted regression impact. This sensor has weighting set to blank and the service only updated the target hours.
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 258, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 414, in _async_refresh
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 168, in async_update_listeners
    update_callback()
  File "/config/custom_components/octopus_energy/target_rates/target_rate.py", line 203, in _handle_coordinator_update
    self._target_rates = calculate_continuous_times(
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/octopus_energy/target_rates/__init__.py", line 118, in calculate_continuous_times
    continuous_rates_total = rate["value_inc_vat"] * (weighting[0] if weighting is not None else 1)
                                                      ~~~~~~~~~^^^
IndexError: list index out of range

and here is the sensor output from the development tab (sensitive data obfuscated)
name: dhw_yutaki_daytime
hours: 5
type: Continuous
mpan: 9999
rolling_target: false
last_rates: false
target_invert_target_rates: false
start_time: 08:00
end_time: 15:00
kind: target_rate
account_id: A-XXXX
offset: -00:01:00
is_target_export: false
icon: mdi:camera-timer
friendly_name: Octopus Energy Target dhw_yutaki_daytime
weighting: null

Thanks for raising this. I'll see if I can fix it soon.

@ragg987 I'm failing to recreate your second issue. The only thing I can see is that the target rate sensor was possibly set to zero target hours at some point to produce this result?

Your original issue along with some additional validation should now be fixed in v11.0.1. This should resolve your latter issue as well, although I'm unsure how it got into that state.

Hi, 11.0.1 seems to have fixed it, I'll continue to test - thanks. However new issue found. Creatin a separate incident.

Thanks for responding. I'll close this issue as complete.


Proposition to simplify risk level

Description

Checklist:

[ ] Have you documented your changes in the pull request description?
[ ] Does the change present any security considerations?
[ ] Is any gem functionality overloaded? Eg: Devise controller methods being overloaded.
[ ] Has acceptance criteria been tested by a peer?
[ ] Has the CHANGELOG been updated? (If change is worth telling users about.)

General testing (author)

[ ] Test without JavaScript
[ ] Test on small screen

Accessibility testing (author)

[ ] Works keyboard only
[ ] Tested with one screen reader
[ ] Zoom page to 400% - content still visible
[ ] Disable CSS - does content make sense and appear in a logical order?

@StupidCodeFactory thanks again for doing this. Made some small changes to get it ready to merge against the parent PR. Now everything should be ready to go! :raised_hands:


Improve memory usage when reaching diff limits

Related to #2669, also related to https://github.com/go-gitea/git/pull/93
This change introduces a hand-rolled implementation of input.ReadString() that stops reading if the line buffer gets bigger than maxLineCharacters.
I thought the performance of this would be terrible, but actually it appears to be ~slightly faster~ slower when timing the ParsePatch function (with real loose timing so might be good to check out).
For commits that are shown completely the memory usage is slightly better, but for commits where files are hidden because they are too big, the memory usage is much, much better (my test was a 100mb one-liner which went from 322mb to 55mb).
The ParsePatch function does not behave completely identical because line is now truncated to whatever the user sets as maximum. I checked all usages a little and it does not appear to matter (diffs are only shown to the user and if IsIncomplete is set the line member is not used), however this needs some attention during review.
Possible follow-up for this is to completely rewrite the diff functions to use things like git diff --numstat to figure out if diffs have to be truncated and which files are part of a diff instead of this ugly parser.

Codecov Report

Merging #2990 into master will increase coverage by <.01%.
The diff coverage is 61.11%.

@@            Coverage Diff             @@
##           master    #2990      +/-   ##
==========================================
+ Coverage   32.51%   32.52%   +<.01%
==========================================
  Files         267      267
  Lines       39270    39277       +7
==========================================
+ Hits        12770    12774       +4
- Misses      24712    24715       +3
  Partials     1788     1788

Impacted Files
Coverage Δ

models/git_diff.go
60.05% <61.11%> (-0.06%)
:arrow_down:

Continue to review full report at Codecov.

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

I will refactor this to use io.LimitReader instead...

Okay, I'm not going to rewrite this with io.LimitReader because weird things start to happen...

I fixed an issue where it would hard crash when trying to parse https://try.gitea.io/mrexodia/DarkSouls3.TextViewer/commit/629cf9b3d6b295bbcddf76d1f6167259b764d9dc

I personally don't mind adding it to a function, but it would become rather ugly:
func ReadLineWithMaxLength(reader io.Reader, maxLineCharacters int) (line string, isEof bool, isTruncated bool) {
...
}

I could read maxLineCharacters + 1 and leave the original check at 298 but that feels a bit hacky...

Fair enough, LGTM

@lunny why backport for this?


Inserting into table with out-of-order qualified columns is ignored

terrier=# CREATE TABLE tbl (c1 int not null primary key, c2 int, c3 int);
CREATE TABLE
terrier=# insert into tbl (c3, c1, c2) VALUES (3, 1, 2);
INSERT 0 1
terrier=# SELECT * FROM tbl;
 c1 | c2 | c3
----+----+----
  3 |  1 |  2
(1 row)
terrier=#

@17zhangw suspects that the problem is in the codegen layer.

Fixed in #758


adaptiveHeight not working on Responsive breakpoint

adaptiveHeight working great on " slidesToShow: 2" when it load and onClick on read more button.
When on Responsive breakpoint 768 adaptiveHeight  not working on "slidesToShow: 1" when onClick ead more button. The adaptiveHeight not working.
When on Responsive breakpoint 768, onClick ead more button; Only when try to resize the browser or drag the slider the adaptiveHeight work.
====================================================================
(http://jsfiddle.net/nzrgd8bc/30/)

Have you found a solution yet?

Found solution,
http://jsfiddle.net/nzrgd8bc/31/


Feature/adding enable blackfire command

Description
Adds the nitro enable blackfire command which makes its own service container for the blackfire agent. Updates the sites container to use the BLACKFIRE_AGENT_SOCKET configuration.
To do

[x] Add client id and token to the Nitro config and populate the site container environment variables
[x] Check if the blackfire container environment variables have changed
[x] Allow overriding the port with NITRO_BLACKFIRE_PORT

@angrybrad ready for you to try locally. All that is required is to set make local to build a new binary and then the following:

nitro blackfire on to enable blackfire for a specific site
nitro enable blackfire to spin up the service at tcp://blackfire.service.nitro:8307


Running network from JSON seems inaccurate with hundreds of JSON objects?

I'm utilising the fromJSON option of Brain JS to output my network to a json file and load it back in, however, I'm confused as to how I'm meant to train this...
Am I meant to run one set of data through the network in the .run([]) and then use that one json file for other data running through the data, or, am I meant to train it and keep appending data to the JSON file, either way, the following seems to return mostly the same result all of the time, I've stripped most of the training data, but the array of objects would be thousands of objects:
// require packages
const brain = require('brain.js')
const fs = require('fs');
const path = require('path');
const args = require('minimist')(process.argv.slice(2))

// check if we have a trained network already
const checkIfNetworkExists = fs.existsSync('./js/generate/data/trained-network.json')

// Loan & Term: init Training Pattern
const myNetwork = new brain.NeuralNetwork({hiddenLayers: [7, 7]})
if (!checkIfNetworkExists) {
  const trainingData = [
    {input:[451,2200,42,0,650,200,150],output:[0,1,1,0,0,1,1]},{input:[851,1400,52,150,500,50,850],output:[0,1,1,0,0,0,0]}
  ]

  // train the network
  if (args['enableAsyncTraining'] && args['enableAsyncTraining'] === 'true') {
    myNetwork.trainAsync(trainingData, trainingOptions)
  } else {
    myNetwork.train(trainingData, trainingOptions)
  }

  // write trained network to file
  fs.writeFileSync('./js/generate/data/trained-network.json', JSON.stringify(myNetwork.toJSON(), null, '  '));
} else {

  // load network if it exists
  myNetwork.fromJSON(JSON.parse(fs.readFileSync('./js/generate/data/trained-network.json', 'utf8')));
}

// run the network
myNetwork.run([100, 2000, 40, 6, 650, 200, 100])

Each time you train network with new data, network is updated. This means you just need to update/replace your json with newly generated one.

@mubaidr My JSON file is 292 lines long, do I need to add another parent object to the end with each training? How would I update the network whilst retaining the performance?
{
  "sizes": [
    7,
    7,
    7,
    7
  ],
  "layers": [
    {
      "0": {},
      "1": {},
      "2": {},
      "3": {},
      "4": {},
      "5": {},
      "6": {}
    },
    {
      "0": {
        "bias": 0.09439083188772202,
        "weights": {
          "0": -0.7670116424560547,
          "1": -0.6642861366271973,
          "2": -0.19578738510608673,
          "3": -0.21747833490371704,
          "4": -0.14496855437755585,
          "5": -0.11916668713092804,
          "6": -0.2401152402162552
        }
      },
      "1": {
        "bias": -0.15841266512870789,
        "weights": {
          "0": -0.5381118655204773,
          "1": -0.5877346992492676,
          "2": -0.04498208686709404,
          "3": 0.09252215921878815,
          "4": -0.4555858373641968,
          "5": 0.0008982665603980422,
          "6": 0.1640717089176178
        }
      },
      "2": {
        "bias": -0.04460155963897705,
        "weights": {
          "0": 1.3179415464401245,
          "1": 0.6098086833953857,
          "2": 0.1907377690076828,
          "3": 0.2269635796546936,
          "4": -0.11790905147790909,
          "5": 0.30080828070640564,
          "6": 0.1771688163280487
        }
      },
      "3": {
        "bias": -0.006974233780056238,
        "weights": {
          "0": 0.19547560811042786,
          "1": 0.14253273606300354,
          "2": 0.12966442108154297,
          "3": 0.15862159430980682,
          "4": 0.06666643172502518,
          "5": 0.06027138978242874,
          "6": 0.09067974984645844
        }
      },
      "4": {
        "bias": 0.04890609532594681,
        "weights": {
          "0": -0.26986971497535706,
          "1": -0.2122180163860321,
          "2": -0.19262979924678802,
          "3": 0.2195170819759369,
          "4": -0.09843645244836807,
          "5": 0.0943814292550087,
          "6": -0.11620646715164185
        }
      },
      "5": {
        "bias": 0.007766162045300007,
        "weights": {
          "0": 0.19123606383800507,
          "1": 0.17956386506557465,
          "2": -0.16825221478939056,
          "3": -0.2137739360332489,
          "4": 0.0667356327176094,
          "5": 0.20001071691513062,
          "6": 0.06469400972127914
        }
      },
      "6": {
        "bias": -0.14158064126968384,
        "weights": {
          "0": 0.269572913646698,
          "1": 2.356199026107788,
          "2": -0.04505547136068344,
          "3": 0.27069488167762756,
          "4": 1.0695784091949463,
          "5": 0.6510146260261536,
          "6": 1.067539930343628
        }
      }
    },
    {
      "0": {
        "bias": -0.7611159086227417,
        "weights": {
          "0": -0.0686710998415947,
          "1": -0.24292978644371033,
          "2": -0.8989506959915161,
          "3": -1.0361626148223877,
          "4": -3.3347342014312744,
          "5": -0.9127030372619629,
          "6": -0.7809993028640747
        }
      },
      "1": {
        "bias": -0.6161317229270935,
        "weights": {
          "0": 0.01872648298740387,
          "1": -0.44291770458221436,
          "2": -0.8336756229400635,
          "3": -0.8752111196517944,
          "4": -3.327821969985962,
          "5": -0.8654630184173584,
          "6": -1.1974551677703857
        }
      },
      "2": {
        "bias": -0.5951817631721497,
        "weights": {
          "0": -0.00733727402985096,
          "1": -0.6064631342887878,
          "2": -0.9993404746055603,
          "3": -0.6716686487197876,
          "4": -3.4572129249572754,
          "5": -0.9579042196273804,
          "6": -1.1782407760620117
        }
      },
      "3": {
        "bias": -0.5544703602790833,
        "weights": {
          "0": 0.03121502883732319,
          "1": -0.4008966386318207,
          "2": -1.0554537773132324,
          "3": -0.9632909297943115,
          "4": -3.0501139163970947,
          "5": -0.8849554061889648,
          "6": -0.8785363435745239
        }
      },
      "4": {
        "bias": -0.8543322682380676,
        "weights": {
          "0": 0.03028627671301365,
          "1": -0.08175212144851685,
          "2": -1.1896885633468628,
          "3": -0.7588884830474854,
          "4": -3.4440109729766846,
          "5": -0.9725902080535889,
          "6": -0.6348049640655518
        }
      },
      "5": {
        "bias": -0.895724356174469,
        "weights": {
          "0": 0.19649137556552887,
          "1": -0.44556358456611633,
          "2": -1.098259449005127,
          "3": -0.960195004940033,
          "4": -3.355997085571289,
          "5": -0.73044353723526,
          "6": -0.7049161791801453
        }
      },
      "6": {
        "bias": -0.7397876381874084,
        "weights": {
          "0": -0.113799549639225,
          "1": -0.2322213351726532,
          "2": -0.8513315916061401,
          "3": -0.8888430595397949,
          "4": -2.009086847305298,
          "5": -0.775073766708374,
          "6": -1.0452015399932861
        }
      }
    },
    {
      "0": {
        "bias": 0.4242694079875946,
        "weights": {
          "0": 1.6234968900680542,
          "1": 1.6203052997589111,
          "2": 1.6591789722442627,
          "3": 1.513173222541809,
          "4": 1.6682435274124146,
          "5": 1.6272711753845215,
          "6": 1.2238273620605469
        }
      },
      "1": {
        "bias": 6.9684882164001465,
        "weights": {
          "0": 1.5869325399398804,
          "1": 1.2068145275115967,
          "2": 1.763297438621521,
          "3": 1.39811110496521,
          "4": 1.450259804725647,
          "5": 1.299032211303711,
          "6": 0.8678433299064636
        }
      },
      "2": {
        "bias": 6.967097282409668,
        "weights": {
          "0": 1.4249857664108276,
          "1": 1.0491899251937866,
          "2": 1.8390330076217651,
          "3": 1.521957278251648,
          "4": 1.408325433731079,
          "5": 1.5694714784622192,
          "6": 1.032562017440796
        }
      },
      "3": {
        "bias": -0.10140286386013031,
        "weights": {
          "0": 0.7015955448150635,
          "1": 0.6939533948898315,
          "2": 0.7209612727165222,
          "3": 0.6339335441589355,
          "4": 0.7265103459358215,
          "5": 0.7037737965583801,
          "6": 0.4587821364402771
        }
      },
      "4": {
        "bias": -1.1545584201812744,
        "weights": {
          "0": -0.706428587436676,
          "1": -0.6880828142166138,
          "2": -0.7451974153518677,
          "3": -0.6021878719329834,
          "4": -0.7454286813735962,
          "5": -0.7167820334434509,
          "6": -0.07689554244279861
        }
      },
      "5": {
        "bias": -1.7900606393814087,
        "weights": {
          "0": 0.41949495673179626,
          "1": 0.4168839454650879,
          "2": 0.41511523723602295,
          "3": 0.3618548810482025,
          "4": 0.43424156308174133,
          "5": 0.40631112456321716,
          "6": 0.12862923741340637
        }
      },
      "6": {
        "bias": -1.7644935846328735,
        "weights": {
          "0": -2.5884010791778564,
          "1": -2.545736789703369,
          "2": -2.7074363231658936,
          "3": -2.383005142211914,
          "4": -2.6837635040283203,
          "5": -2.63854718208313,
          "6": -1.3939564228057861
        }
      }
    }
  ],
  "outputLookup": false,
  "inputLookup": false,
  "activation": "sigmoid",
  "trainOpts": {
    "iterations": 20000,
    "errorThresh": 0.005,
    "log": true,
    "logPeriod": 10,
    "learningRate": 0.3,
    "momentum": 0.1,
    "callbackPeriod": 10,
    "beta1": 0.9,
    "beta2": 0.999,
    "epsilon": 1e-8
  }
}

Just over-right JSON from network.TOJSON after each train:
// write trained network to file
  fs.writeFileSync('./js/generate/data/trained-network.json', JSON.stringify(myNetwork.toJSON(), null, '  '));

@mubaidr So I just need to update the trainingData Array with new data and rerun?

Yes.

train network
save json
load network
train network with new data
replace old json file from network

while were here NN work better with numbers between 0 and 1 is deviding your training data by your highest input is a good way to get this.

@vorticalbox Are we saying that this: input:[451,2200,42,0,650,200,150] should be: input:[0.451,0.2200,0.42,0,0.650,0.200,0.150] ?

@vorticalbox Are we saying that this: input:[451,2200,42,0,650,200,150] should be: input:[0.451,0.2200,0.42,0,0.650,0.200,0.150] ?

that that it should be but it's generally better to geta  value betwork 0 and 1.
in the code you posted in the issue i would divide by 3000 and get something like this
const trainingData = [
    {
        input:[ 0.15033333333333335,0.7333333333333333,0.014,0,0.21666666666666667,0.06666666666666667,0.05 ],
        output:[0,1,1,0,0,1,1]
    },
    {
        input:  [0.2836666666666667,0.4666666666666667,0.017333333333333333,0.05,0.16666666666666666,0.016666666666666666,0.2833333333333333 ],
        output:[0,1,1,0,0,0,0]
    }
  ]

@vorticalbox Sweet! How should I handle negative numbers that happen as a result of a division by X? Or can Brain JS handle this?

@vorticalbox When I run numbers through, would they need to be divided as well? myNetwork.run([100, 2000, 40, 6, 650, 200, 100])

Normalize them to between 0 and 1 for the best results (NOTE: this isn't a brain.js thing, it is just machine learning in general).  Normalize the most negative number (or least number) to 0, and then the highest number to 1, everything else should be within that 0 to 1 range for effective normalization.

@robertleeplummerjr Thanks! Using this idea, would I potentially receive better results? E.g:
I have a random number generator that builds an array of 7 whole numbers, if a number is between 200 & 500, it scores 1 as the output, and a number less than 200 or greater than 500 scores 0. I need Brain to detect this and score a higher output in this bracket, and outside of it to score lower.
Normalizing the numbers and converting them would score better? What would you advise? Currently I'm seeing error thresholds of between 0.10 and 0.15, is this acceptable

@mubaidr So this is what I'm currently doing:

Create a training data set (an Array of 35,000 objects containing various number combinations) which have been normalized between 0 and 1.
Running normalized numbers in myNetwork.run([0.5, 0.54, 0, 0.69, 0.25, 0.9, 1]), it takes a while to run through 20,000 iterations
A file is then generated using fs.writeFileSync using toJSON()
I then load that file into the JS file, just after the training data Array, but before where the network is trained through: myNetwork.train(trainingData, trainingOptions)
I then pass a different set of numbers into myNetwork.run([0.4, 0.15, 1, 0.3, 0.2, 0.95, 1]),
a new file is created in replace of the initial one.

Is this correct? I've tried doing this loop 4 times, and the error threshold remains around 0.050 each time, and it takes the same amount of time?

/cc @mubaidr

@sts-ryan-holton Can you please create a playground here, with your sample code: https://runkit.com/home
This will allow us to understand the code and we will be able to update code.

@mubaidr @robertleeplummerjr I've created a playground here: https://runkit.com/ryan-holton/brain-js-network-from-json
Granted, it's missing a few things that would otherwise be available on a physical environment such as filesystem read/write, you'll see some "WOULD BE" comments as to where this would be.

This looks good. My apologies looks like this is correct way to train with new data:

train network
save json
create new network
train network with (old + new data)
replace old json file from network


How do you calculate the relevance of a document to each topic? Where is the code modified?

 I am a student from China and I want to get the probability that each document belongs to the topic. How can I get it ? Hope you can help me, thank you very much!!!!!!!

hi there,
Non-negative Matrix Factorisation (NMF) is not a probabilistic method, but rather a "brute force" algorithm which decomposes a term-document matrix in a term-topic matrix and a topic-document matrix. the topic-document matrix then contains membership weights of topics present in a document.
hope this helps.
p.


Slider: RTL support

Really excited about this pr! 👀
Added two more orientations for sliders, horizontal-rl and vertical-tb, effectively adding RTL support for sliders with an added bonus of top-to-bottom orientation for vertical sliders. I also documented the two orientations.
I manually tested all 4 orientations with and without ticks. Everything seems to be placed correctly and keyboard shortcuts work. I haven't added any automated tests, though.

Hey @huntabyte, dir="rtl" makes sense for horizontal sliders, but what about vertical sliders? dir="rtl" doesn't make sense in that context. Should we add dir="ttb"? What if the user passes orientation="horizontal" and dir="ttb"? If you have any suggestions, I'm willing to modify the code.

Hm, the slider is one of the more unique ones I suppose.
I know for a fact we should have either a dir or rtl prop, likely rtl to keep it simple which we can apply to basically every builder as we add RTL support and ensure a consistent DX across the builders.
As for the top to bottom, I imagine this is the only/one of the only builders that it makes sense for right? If that's the case, then maybe a prop for topToBottom? It sounds a bit odd though and I do see what you mean, I'm just trying to ensure we have some sort of standard, as RTL support is definitely something we want across all builders.
Open to suggestions from the community on this one as well!


Names of buildingprofiles in technology table is not displayed correctly

In this LES: testing buidingprofiles I am using self uploaded baseload profiles. Although it seems the right profiles are used when looking at the dashboard, the technology table shows EDSN2a profiles to be used.

Please include a link to your LES @JeroenvdLogt

Assigned @grdw

https://moses.energytransitionmodel.com/testing_grounds/479


Support for predicateHints option in delta_sharing.load_as_spark

Hello team :wave:
From my understanding, the predicateHints option allows querying a table using S3 partitions as filters https://github.com/delta-io/delta-sharing/blob/main/PROTOCOL.md#read-data-from-a-table to retrieve fewer signed URLs.
Right now, we are loading our data through a Spark job using the delta_sharing.load_as_spark(url: str, version: Optional[int] = None) -> "PySparkDataFrame" function. However we don't see any argument for the predicateHints option.
Are you planning to add this option? If not, what should we do? I was thinking about making the POST query to the DeltaShare server ourselves and then providing the list of S3 signed URLs from the response to spark.read.parquet. Would that work?

Hi @ycrouin , sorry for the late response.
Do you still need this feature, we could prioritize this in Q4, to make it an argument  in the spark query, and pass it from the client to the server.
Also making the POST query your selves should work, have you tried that?

Hello @linzhou-db, thanks for reaching back to me!
No, we don't really need this feature anymore, but it might be useful to others.
Eventually, we were facing timeouts with Delta Sharing POST query, probably because of the large number of parquet files to pre-sign (up to millions). To overcome this issue, we're now using Delta Lake on Spark directly, with s3 cross-account permissions.

I want support for predicateHints on load_as_pandas function, can it be done ?
As of now load_as_pandas will load whole table, there is no way to pass filter.

@desingho I figured this out recently:
import os
import delta_sharing

rest_client = ...
table = delta_sharing.Table(
  share='share-name',
  schema='schema-name',
  name='table-name')
predicateHints = ('a >= 7', 'a < 10')

data = delta_sharing.delta_sharing.DeltaSharingReader(
  table=table, predicateHints=predicateHints, rest_client=rest_client,
).to_pandas()


AO-14225 Postgis adapter support

Thanks for this PR, I need to run some tests, but there is a good chance I can add it to the upcoming release.

@molafson I ran tests and it looks good to me. Once it is merged I'm going to change this regex /postgres|postgis/ to /^postgres|^postgis/, copying the regex Rails uses to determine the adapter.
Sound good?


'ascii' codec can't decode byte 0xff

File "WinboxExploit.py", line 76, in
dump(d[55:])
File "C:\Users\turjo\AppData\Local\Programs\Python\Python37-32\extract_user.py", line 45, in dump
user_pass = get_pair(data)
File "C:\Users\turjo\AppData\Local\Programs\Python\Python37-32\extract_user.py", line 38, in get_pair
user  = user.decode("ascii")
UnicodeDecodeError: 'ascii' codec can't decode byte 0xff in position 4: ordinal not in range(128)

Did you try changing it to something else than ASCII?

no I did not try to change anything rather than ASCII....do you have any suggestion.

Here is a list of standard encodings:
https://docs.python.org/3/library/codecs.html#standard-encodings
Other than that I have no clue. Try utf_8 and such.

Ok I will try with utf_8 and post if it works or not. Thanks again for your suggestion.

According to documentation of string.decode(), you can also tell it what to do with decode errors. Such as make it ignore invalid chatacters.
See: https://www.tutorialspoint.com/python/string_decode
For example:
user = user.decode("utf_8", "backslashreplace")

Thanks, it worked!


d3.geo.path doesn't handle zero-area polygons correctly

d3.geo.path sometimes renders polygons where all points are in a straight line (so no inside) as an "infinite" area with a line shaped "hole". The polygons are created by TileStache from a postgis database and served as topojson. The polygons start out as valid RHR geometries and are turned into lines due to the shift from floating point space to integer space; see the drawing below.

If the order of the last three points in the topojson is changed the feature is drawn correctly. I've setup a page showing the difference here: http://research.geodan.nl/sites/vectortiling/test/faultytile.html
Is there a correct clockwise order for points on a line? If so it might be that TileStache is wrong here serving the points in the wrong order, but following the above drawing the points are in a valid order. I would think that if a polygon has an area of 0, the order of points doesn't matter and D3 shouldn't try to create an infinite area with a zero area hole in it.

Fixed in 3.5.17; see #2784 by @lukasappelhans.


feat(core): provide a lightweight and simple way to configure SDK

closes #4

@RomanReznichenko once you finish with these comments, we can merge the PR


Question about commits.

I have a question, for securing the points we need to make multiple commits, so, If I fork a repository and say, make 3 commits and request for a pull so would it be counted as three commits or only one because the pull request was just one? I hope the first one is correct, otherwise there should be a lot of pull requests, right?

Yeah, the first one is correct.

Okay, makes sense, then I should give proper descriptions, as I am not so far. Thank you.

The first one is correct.


question on timestamps corresponding  the images

hi. how can I get the timestamps while I get the left and depth image Simultaneously???

There is a retrieval time example in the ROS-Wrapper sample.
The "real" timestamps should be identical, since the depth image corresponds to that stereo pair at that timepoint.

https://www.stereolabs.com/developers/documentation/API/v2.3.3/classsl_1_1Camera.html#a737689d57677bfdbb030b36c5498cdec
Just search the API, it is quite small.

thank you very much!


How to use alembic in dagobah?

I have changed the Dagobah model and added remote_host.
Then I do this:
cd dagobah/backend
(sched)zengr@V2 (master *) ~/dev/python/dagobah/dagobah/backend: ls
__init__.py       alembic.ini       base.pyc          migrations        mongo.pyc         sqlite.pyc        sqlite_models.pyc
__init__.pyc      base.py           dagobah.db        mongo.py          sqlite.py         sqlite_models.py
(sched)zengr@V2 (master *) ~/dev/python/dagobah/dagobah/backend: alembic revision -m "add remote host"
  Path doesn't exist: 'dagobah/backend/migrations'.  Please use the 'init' command
  to create a new scripts folder.

The migrations dir exists but I get the error, am I missing anything?
I am using alembic for the first time and I am referring to this: https://alembic.readthedocs.org/en/latest/tutorial.html

hey guys, I'm getting problem in flask, while trying to migrate that on heroku.
heroku run python manage.py init db

Creating directory /app/migrations ... done
Creating directory /app/migrations/versions ... done
Generating /app/migrations/env.py ... done
Generating /app/migrations/alembic.ini ... done
Generating /app/migrations/env.pyc ... done
Generating /app/migrations/script.py.mako ... done
Generating /app/migrations/README ... done
Please edit configuration/connection/logging settings in '/app/migrations/alembic.ini' before

proceeding.

But when I tried to migrate it, I got error like ...
///////////////////////////////////////////

Traceback (most recent call last):
File "manage.py", line 14, in
manager.run()
File "/app/.heroku/python/lib/python2.7/site-packages/flask_script/init.py", line 412, in run
result = self.handle(sys.argv[0], sys.argv[1:])
File "/app/.heroku/python/lib/python2.7/site-packages/flask_script/init.py", line 383, in handle
res = handle(*args, **config)
File "/app/.heroku/python/lib/python2.7/site-packages/flask_script/commands.py", line 216, in call
return self.run(*args, **kwargs)
File "/app/.heroku/python/lib/python2.7/site-packages/flask_migrate/init.py", line 171, in migrate
version_path=version_path, rev_id=rev_id)
File "/app/.heroku/python/lib/python2.7/site-packages/alembic/command.py", line 74, in revision
script_directory = ScriptDirectory.from_config(config)
File "/app/.heroku/python/lib/python2.7/site-packages/alembic/script/base.py", line 120, in from_config
version_locations=version_locations
File "/app/.heroku/python/lib/python2.7/site-packages/alembic/script/base.py", line 57, in init
"scripts folder." % dir)
alembic.util.CommandError: Path doesn't exist: 'migrations'.  Please use the 'init' command to create a new scripts folder.

/////////////////////////////////////////////////////////////////////////////////////////////////
any idea, to fixed this problem
I'm trying to build an registration app using technology.

Flask
Postgresql
SqlAlchemy

@Deepakdubey90 You would probably have better luck with your question on Stack Overflow or in Alembic's issue tracker. Your question doesn't seem to be related to Dagobah.

@Deepakdubey90  i have some problem ,and i don`t know how to fix ,did you have fix this problem anyway???

@yusank , Yes I have fixed that.

@Deepakdubey90 hello，how to fix this problem ？i face the same problem，thx！
version_locations=version_locations
File "/app/.heroku/python/lib/python2.7/site-packages/alembic/script/base.py", line 57, in init
"scripts folder." % dir)
alembic.util.CommandError: Path doesn't exist: 'migrations'. Please use the 'init' command to create a new scripts folder.

@Deepakdubey90 how did you fixed the problem? I am facing the same issue!


Failed to minify the code from this file

I am using Create React App and on 'npm run build' getting the following error -
Failed to minify the code from this file:
./node_modules/parse-asn1/node_modules/asn1.js/lib/asn1/decoders/der.js:58

Read more here: http://bit.ly/2tRViJ9

I'm guessing its the same issue as #98


[PORT] Add build YAML for Twilio functional test

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/3287

Description
Adds a YAML file to set up a pipeline to run the functional test for Twilio.
This pull request depends on the test added in the PR #3286
Changes made
We added the file botbuilder-dotnet-ci-twilio-test.yml inside the build/yaml folder.
Before Setup
The following step by step guide uses a Trial Twilio account, which should last for approximately 200 text messages or runs of the test. If you want to use this functional test for an unlimited amount of time, you will need to upgrade your account to a paid version and add a balance to it.
Requirements
This test requires a valid phone number to receive text messages from the bot when it answers.
You can use a personal number, register a second Twilio account or buy a second number in a no trial account.
Prerequisites

Valid phone number, required to receive the messages from the bot.
Azure subscription, required to deploy the bot to Azure.
App Registration in Azure Portal, we need its AppId and AppSecret. More info here.
Azure DevOps organization.
Configured Service Connection in Azure DevOps (Steps below).
Set up a Twilio account (Steps below).

Set up Twilio account

Go to Twilio's page to sign up for a free trial account.

The signup process requires a valid phone number to receive text messages, this number will be the one we will be using to receive the messages as the SenderNumber.

You can later check this number or verify a new one to use in the test in the Verified Caller IDs dashboard. Trial accounts can only send text messages to numbers verified there.

Go to your Console Dashboard, click on Get Trial Number to register a new phone number with SMS capabilities, this will be your TwilioNumber, also take note of your account sid (TwilioAccountSid) and auth token (TwilioAuthToken).

Go to your Twilio's Active Numbers dashboard and click in your number.

Then, scroll down to the Messaging section.
In the A message comes in field, select "Webhook" and fill it with the Bot Web App URL. https://<BOT_NAME>.azurewebsites.net/api/messages

The URL may change depending on the value for the BotName variable you choose in the pipeline.

Set up build pipeline

Create a new build pipeline. Then, select the Use classic editor option.

Configure the repository and branch. Then, in the configuration as code, click on Apply for the YAML file option.

In section YAML, write the build name and select the build YAML file inside the folder build/yaml in the root of the directory.

In the Variables section add the following variables.

AppId (From app registration).
AppSecret (From app registration).
AzureSubscription (Name of your Azure Resource Manager service connection).
SenderNumber (Number where the bot will be sending the messages, in format +123456423).
TwilioAccountSid (Twilio account Sid, you can see it in your Twilio's dashboard).
TwilioAuthToken (Twilio Auth token, you can see it in your Twilio's dashboard).
TwilioNumber (Twilio number, you can see it in your Twilio's dashboard, in format +123456423).
BotName (The name that will be used to deploy the bot to Azure).
BotGroup (The resource grop name used to deploy the bot to Azure).

(Optional) Configure the triggers for the pipeline. By default, this pipeline runs every time a pull request is created or a commit is made in the master branch.

Create an Azure Resource Manager service connection
This step is required to use your Azure Subscription for the Windows and Linux CI builds. If you already have a Connection Service configured, save its Connection name to use it later as AzureSubscription.
For more info go to this link.
1-  Navigate to Project settings -> Service Connections -> New service connection.

2- Select Azure Resource Manager and click Next. Then, select Service principal (manual)

3- In the New Azure Service Connection section, complete the next fields. Then, click on verify and save.

Subscription Id (stand for Azure Subscription Id)
Subscription Name
Services Principal Id
Service principal key
Tenant ID
Services connection name (Name used to refer to this service connection in the pipelines)

Testing
In the image below you can see the run of a pipeline set up using this YAML file.

[channel adapters]

We're not porting the Twilio adapter right now


Enable users take 2

Messed up a little with the git history, so creating a new PR. This replaces #13.

Thanks!


Warning: rewind(): stream does not support seeking

PHP version used: 7.1.0
mongo-php-library version: 1.1.0
Hello,
Using this code

/*
Uses MongoDb\GridFS\Bucket::openDownloadStreamByName($filename, array $options = []); to retrieve the file
*/
$file = $gw->retrieveFileByName('3142184dbed342fbb5ad6dc495d02405');

$metadata = stream_get_meta_data($file['stream']);
rewind($file['stream']);

I get a "Warning: rewind(): stream does not support seeking" even though stream_get_meta_data function advertises that the stream is seekable
array (
  'timed_out' => false,
  'blocked' => true,
  'eof' => false,
  'wrapper_data' => '(removed for brevity)',
  'wrapper_type' => 'user-space',
  'stream_type' => 'user-space',
  'mode' => 'r',
  'unread_bytes' => 0,
  'seekable' => true,
  'uri' => 'gridfs://mydb/fileStore.files/585bc30888461f001a7a4412',
)

This behavior causes an error in Slim framework which tries to rewind the stream in the Response object if the stream is seekable before sending it out

Seeking GridFS streams is an outstanding feature, which is being tracked in PHPLIB-213.
Based on discussion in https://github.com/fruux/sabre-dav/issues/787, StreamWrapper implementations have no control over the "seekable" property of stream_get_meta_data() and always advertise themselves as seekable. Slim may want to implement similar fseek() checks that went into sabre-dav to address this (not just for GridFS but other StreamWrappers that do not support seeking).
/cc @codeguy @akrabat

@acid24: We have an implementation of seeking for readable streams in https://github.com/mongodb/mongo-php-library/pull/325 if you'd like to test that out. Since it's a new feature, it will not be released until 1.2.0; however, I'd be interested to hear whether it meets your needs.

@jmikola OK, I will test it and let you know. Thank you

1.2.0-alpha1 is now tagged and includes seeking functionality for GridFS.


When claiming from many small balanceid, the transaction times out

To prevent that, I would recommend to put the expiration time in the transaction only after the (unsigned) transaction is finalized

This needs to be claimed and worked by someone. @valzav thoughts? Moving to 1118

@jcalfee is best equipped to handle this.

xeroc [1:13 PM]
oh .. I can't replorduce this since I was able to claim using a different (faster) browser (chromium)
xeroc [1:14 PM]
https://graphn.slack.com/archives/D0AA476AC/p1447355623000033
￼James Calfeejcalfee
I increase the expiration time for about 1 sec per signature.
Today at 1:13 PM
xeroc [1:14 PM]
seems reasonable
jcalfee [1:14 PM]
Also, I group balance claims in groups of 60 ..
jcalfee [1:14 PM]
so the trx does not become too large..
xeroc [1:14 PM]
:+1:
jcalfee [1:14 PM]
So did you have the issue more than maybe 2 weeks ago?
xeroc [1:14 PM]
i'd say so .. yes
jcalfee [1:15 PM]
good news then I'll close it -tq
xeroc [1:15 PM]
I posted the report after I noticed someone else having the same issue
xeroc [1:15 PM]
yes .. please close it!

@jcalfee I assigned this to you as well. If you are able to get into the groove, please claim items you are working on. Thanks.

Another case:
https://bitsharestalk.org/index.php?topic=20081.msg255901;topicseen#new

@jcalfee Can you squeeze this edge case in before the Milestone ends?

@wmbutler: James talked to me about this already and he had it fixed .. I think the case above may have another reason that needs investigation first .. wouldn't count on this being fixed today already as we need input first

ok, so I'll push it again, close it if you think it enough of an edge case to not worry about it.

Closing due to no feedback for many months.


Internal proxy hangs with error when mirrord doesn't load into the process

Bug Description
Internal proxy hangs with error when mirrord doesn't load into the process:
... failure
mehularora@Mehuls-MacBook-Air mirrord % Error:
  × Internal proxy error: FirstConnectionTimeout
  ╰─▶ Couldn't accept connection before timeout

Steps to Reproduce
target/debug/mirrord exec --target pod/py-serv-deployment-5c57fbdc98-pdbn4 --agent-ttl 100  -- sh
Backtrace
No response
Relevant Logs
No response
Your operating system and version
Darwin mehuls-air.lan 21.4.0 Darwin Kernel Version 21.4.0: Mon Feb 21 20:36:53 PST 2022; root:xnu-8020.101.4~2/RELEASE_ARM64_T8101 arm64
Local process
mehularora@mehuls-air ts-test % file $(which sh) /bin/sh: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64 - Mach-O 64-bit executable x86_64] [arm64e:Mach-O 64-bit executable arm64e - Mach-O 64-bit executable arm64e] /bin/sh (for architecture x86_64):      Mach-O 64-bit executable x86_64 /bin/sh (for architecture arm64e):      Mach-O 64-bit executable arm64e
Local process version
No response
Additional Info
No response

What would you consider as the correct behavior?

The correct behavior would be for the internal proxy to terminate along with the mirrord process if it fails. An approach I had in mind was that the child keeps reading an fd, and waits for an EOF i.e. when parent dies/ killed the child knows it read an EOF and can exit itself. Perhaps would be better to use pipes in this case?

Related to #1761 - unfortunately, I couldn't find a solution that would work for extension.


Cannot open new window after closing all windows

VSCode Version:
1.46.0
a5d1cc28bb5da32ec67e86cc50f84c67cc690321
x64

OS Version:
OSX Catalina 10.15.5

Steps to Reproduce:

Open VS Code
CMD-SHIFT-W
CMD-SHIFT-N

Does this issue occur when all extensions are disabled?: Yes/No
Yes
Notes:
This was working until I factory reset my Mac and then reinstalled VS Code. I've done a (thorough) reinstallation of VS Code, and the bug persists.
Tail of verbose log:
[main 2020-06-17T15:43:27.907Z] Lifecycle#window.on('close') - window ID 1
[main 2020-06-17T15:43:27.907Z] Lifecycle#unload() - window ID 1
[1738:0617/084328.010406:INFO:CONSOLE(1669)] "%cTRACE color: #888 lifecycle: onBeforeUnload (reason: 1)", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
[1738:0617/084328.010472:INFO:CONSOLE(1669)] "%cTRACE color: #888 lifecycle: onBeforeUnload continues without veto", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
[main 2020-06-17T15:43:28.010Z] Lifecycle#unload() - no veto (window ID 1)
[1738:0617/084328.012259:INFO:CONSOLE(1669)] "%cTRACE color: #888 lifecycle: onWillUnload (reason: 1)", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
[1738:0617/084328.017431:INFO:CONSOLE(1669)] "%cTRACE color: #888 [storage state.vscdb] updateItems(): insert(Map(1) {lifecyle.lastShutdownReason => 1}), delete(Set(0) {})", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
[1738:0617/084328.017854:INFO:CONSOLE(1669)] "%cTRACE color: #888 [storage state.vscdb] Trace (event): BEGIN TRANSACTION", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
[1738:0617/084328.018040:INFO:CONSOLE(1669)] "%cTRACE color: #888 [storage state.vscdb] Trace (event): INSERT INTO ItemTable VALUES ('lifecyle.lastShutdownReason','1')", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
[1738:0617/084328.018568:INFO:CONSOLE(1669)] "%cTRACE color: #888 [storage state.vscdb] Trace (event): END TRANSACTION", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
[1738:0617/084328.024945:INFO:CONSOLE(1669)] "%cTRACE color: #888 [storage state.vscdb] close()", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1669)
[main 2020-06-17T15:43:28.033Z] Lifecycle#onBeforeWindowClose.fire() - window ID 1
[main 2020-06-17T15:43:28.034Z] Lifecycle#window.on('closed') - window ID 1
[main 2020-06-17T15:43:30.291Z] [uncaught exception in main]: TypeError: Cannot read property 'id' of undefined
[main 2020-06-17T15:43:30.291Z] TypeError: Cannot read property 'id' of undefined
    at fallbackMenuHandlers.workbench.action.newWindow (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:542:489)
    at t.click (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:555:626)
    at MenuItem.click (electron/js2c/browser_init.js:1572:9)
    at Function.executeCommand (electron/js2c/browser_init.js:1833:13)
[main 2020-06-17T15:43:30.292Z] telemetry/workbenchActionExecuted { id: 'workbench.action.newWindow', from: 'menu' }
[main 2020-06-17T15:43:45.345Z] update#checkForUpdates, state =  idle
[main 2020-06-17T15:43:45.345Z] update#setState checking for updates
[main 2020-06-17T15:43:45.460Z] update#setState idle
[main 2020-06-17T15:43:45.461Z] telemetry/update:notAvailable { explicit: false }
[main 2020-06-17T16:15:01.480Z] [uncaught exception in main]: TypeError: Cannot read property 'id' of undefined
[main 2020-06-17T16:15:01.480Z] TypeError: Cannot read property 'id' of undefined
    at fallbackMenuHandlers.workbench.action.newWindow (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:542:489)
    at t.click (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:555:626)
    at MenuItem.click (electron/js2c/browser_init.js:1572:9)
    at Function.executeCommand (electron/js2c/browser_init.js:1833:13)
[main 2020-06-17T16:15:01.481Z] telemetry/workbenchActionExecuted { id: 'workbench.action.newWindow', from: 'menu' }
**[main 2020-06-17T16:15:56.476Z] [uncaught exception in main]: TypeError: Cannot read property 'id' of undefined
[main 2020-06-17T16:15:56.476Z] TypeError: Cannot read property 'id' of undefined
    at fallbackMenuHandlers.workbench.action.newWindow (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:542:489)
    at t.click (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:555:626)
    at MenuItem.click (electron/js2c/browser_init.js:1572:9)
    at Function.executeCommand (electron/js2c/browser_init.js:1833:13)
[main 2020-06-17T16:15:56.477Z] telemetry/workbenchActionExecuted { id: 'workbench.action.newWindow', from: 'menu' }**

/duplicate of #99998 and will be fixed in upcoming 1.46.1

Ah got it. Yeah, I just built VS Code from source and it's working there.


Show actual level for nearest 99s

I found myself wondering what the skill levels on nearest 99s were and had to look at the other skill component to see.
This PR shows those levels of the top 5 nearest skills to 99 on the player overview.
Screenshot:

The lint-app ci job was failing to run, looking back it seems like it's failed for several months.
I fixed that, and in the process got hit with 75 lint errors.
Went ahead and fixed those too, let me know if you'd like any of it done differently.

you fixed old linting issues too, tyvm


on "Publish" step, I want to continue to add a new publication/dataset

Describe the improvement
When I have finished the "add" workflow for a publication/dataset, I would like to add another publication/dataset without first having to go to the publications/datasets overview. I expect to have a button "Add publication/dataset" on this page (maybe next to the button "Continue to overview").
Screenshots

Done


Broken SSL certificate when I am using HTTPS for Traefik

I am using traefik 1.2.1 and I have problems with the SSL certificate that I am generating using ACME.
I am providing my .toml file:
logLevel = "DEBUG"
defaultEntryPoints = ["http","https"]
[entryPoints]
  [entryPoints.http]
  address = ":80"
    [entryPoints.http.redirect]
      entryPoint = "https"
  [entryPoints.https]
  address = ":443"
    [entryPoints.https.tls]
      MinVersion = "VersionTLS12"
      CipherSuites = ["TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"]
      [[entryPoints.https.tls.certificates]]
      CertFile = "/ssl/tls.crt"
      KeyFile = "/ssl/tls.key"
    [acme]
    email =<EMAIL_ADDRESS>    storage = "/acme/acme.json"
    entryPoint = "https"
    onDemand = true
    onHostRule = true
    acmeLogging = true
    caServer = "https://acme-staging.api.letsencrypt.org/directory"
    [[acme.domains]]
      main = "example.domain"
      sans = ["example.domain"]

I want to configure Letsencrypt certificates for HTTPS for my applications on Kubernetes 1.5.3 cluster.
When I am trying to access the url from browser (https://example.domain) I see: This site can’t provide a secure connection, ERR_SSL_PROTOCOL_ERROR

what was the problem? I'm having this issue as well...

what was the problem? I'm having this issue as well...

The solution was implemented by Traefik in v1.5.


Previously working k8s probe workers are crash looping

Describe the bug
I am running some probes on Kubernetes following the guidance on https://cloudprober.org/. They began crash looping on Dec 10.
The proximate cause is that runProbe calls req.WithContext without checking whether req is nil https://github.com/google/cloudprober/blob/34627fb79d281b4236c7f21f1eec2ba785c5a773/probes/http/http.go#L336 This causes a segmentation violation.
The issue was introduced in PR #521.
A related issue is that I was using the latest Cloudprober Docker container, and that caused me to run unreleased code. See "Additional Context" below.
Cloudprober Version
unreleased
To Reproduce
I can send the actual config file if you message me directly, but I'm able to produce a nil request with this slight modification of the config in the documentation.

cat > /tmp/cloudprober.cfg <<EOF
probe {
name: "google_homepage"
type: HTTP
targets {
host_names: "https://www.google.com" # Note the https
}
interval_msec: 5000  # 5s
timeout_msec: 1000   # 1s
}
EOF

cloudprober --config_file /tmp/cloudprober.cfg

Additional context
I followed the cloudprober.org suggestion to use the latest Cloudprober Docker container. Since this was on the official page, I assumed that the :latest tag tracked the latest official release.
However, a container was pushed 8 days ago on Docker Hub with code that isn't associated with any release tag. You may want to clarify in the documentation whether :latest is intended to track development or whether it's intended to track releases.

Thanks a lot for filing this issue @greglaun-google. This is very helpful.
IIUIC, it's getting triggered by invalid host names. Where earlier cloudprober will simply ignore if there is an error in creating requests, now it crashes because we are not checking for nil requests. We need to fix this ASAP.
Other than that, this issue highlights a bunch of other possible improvements:

We need to verify targets.host_names when we create probes. We'll be able to provide better error message at that time.
We'll also add more tests for HTTP probe code (we have quite a few tests but we always provide correct targets for testing).

Regarding docker versions:
I agree that the current behavior of "latest" is probably not appropriate. Currently latest is built from the HEAD of the master branch. I think the right behavior here will be to point "latest" to the latest release, instead of pointing it to the latest build docker image.
I am planning to change tags in the following manner:

Tag
Built from

master
HEAD of the master branch.

latest
Latest tagged release.

v0.11.1.
Release v0.11.1.

Just wanted to update that docker tag changes mentioned above have been implemented. "latest" is now pointing to the last release.

Awesome thanks for the update and for responding so quickly! I'm not sure the issue I was facing with my real config was caused by a bad host name. I'll send it to you outside this bug so you can take a look.

Awesome thanks for the update and for responding so quickly! I'm not sure the issue I was facing with my real config was caused by a bad host name. I'll send it to you outside this bug so you can take a look.

It's the "https://" in the targets field that fails the request creation. It should have only hostname in it.

targets {
host_names: "https://www.google.com" # Note the https
}

It's the "https://" in the targets field that fails the request creation. It should have only hostname in it.

targets {
host_names: "https://www.google.com" # Note the https
}

I was able to create a minimal example based on the problem with my config. The issue is the presence of a custom HTTP verb, which Google indicates by appending the verb to the URL after a colon..
This issue appears to have been introduced in PR #505. The issue is likely the line https://github.com/google/cloudprober/blob/f16a0a0419916fb40a0198e9281d10cec751efff/probes/http/request.go#L118
which appears to treat a host as a literal IPv6 address if it contains a colon.
Here's the config to reproduce:
probe {
  name: "google_homepage"
  type: HTTP
  targets {
    host_names: "www.google.com/foo:customVerb"
  }
  interval_msec: 5000  # 5s
  timeout_msec: 1000   # 1s
}

I was able to create a minimal example based on the problem with my config. The issue is the presence of a custom HTTP verb, which Google indicates by appending the verb to the URL after a colon..
This issue appears to have been introduced in PR #505. The issue is likely the line https://github.com/google/cloudprober/blob/f16a0a0419916fb40a0198e9281d10cec751efff/probes/http/request.go#L118
which appears to treat a host as a literal IPv6 address if it contains a colon.
Here's the config to reproduce:
probe {
  name: "google_homepage"
  type: HTTP
  targets {
    host_names: "www.google.com/foo:customVerb"
  }
  interval_msec: 5000  # 5s
  timeout_msec: 1000   # 1s
}

In Logs Explorer, I'm seeing logs that say
target: www.google.com/foo:customVerb, error creating HTTP request: parse http://[www.google.com/foo:customVerb]: missing ']' in host

In Logs Explorer, I'm seeing logs that say
target: www.google.com/foo:customVerb, error creating HTTP request: parse http://[www.google.com/foo:customVerb]: missing ']' in host

That's correct. We started doing things assuming that a host is actually a host.
For HTTP probe, verb and URLs should be configured in the http_probe{} stanza. It's a mistake on cloudprober's part that error message is not clear. Quoting my previous comment:

We need to verify targets.host_names when we create probes. We'll be able to provide better error message at that time.

We need to verify that "targets.host_names" contains only host names .. i.e. no port, no URL, no protocol, etc. I'll do that soonish.

That's correct. We started doing things assuming that a host is actually a host.
For HTTP probe, verb and URLs should be configured in the http_probe{} stanza. It's a mistake on cloudprober's part that error message is not clear. Quoting my previous comment:

We need to verify targets.host_names when we create probes. We'll be able to provide better error message at that time.

We need to verify that "targets.host_names" contains only host names .. i.e. no port, no URL, no protocol, etc. I'll do that soonish.

Ok thanks! So host_names should really truly be a comma separated list of actual host names.
I can confirm that moving the URL to the relative_url field of http_probe works.
One of the things that confused me is that the following config is still valid on master, but IIUC, this will soon be rejected by rules that validate the host name:
probe {
  name: "google_homepage"
  type: HTTP
  targets {
    host_names: "www.google.com/foo"  # path with no colon is currently OK, but should be rejected IIUC.
  }
  interval_msec: 5000  # 5s
  timeout_msec: 1000   # 1s
}

Ok thanks! So host_names should really truly be a comma separated list of actual host names.
I can confirm that moving the URL to the relative_url field of http_probe works.
One of the things that confused me is that the following config is still valid on master, but IIUC, this will soon be rejected by rules that validate the host name:
probe {
  name: "google_homepage"
  type: HTTP
  targets {
    host_names: "www.google.com/foo"  # path with no colon is currently OK, but should be rejected IIUC.
  }
  interval_msec: 5000  # 5s
  timeout_msec: 1000   # 1s
}


Wrong alignment for labels of axis on top.

{
  "marktype": "point",
  "encoding": {
    "x": {"name": "MPAA_Rating","type": "N"},
    "y": {"name": "Release_Date","type": "N"}
  },
  "config": {"singleHeight": 400,"singleWidth": 400,"largeBandMaxCardinality": 20},
  "data": {"url": "data/movies.json"}
}

I think it's more of wrong rotation for axis on top

Fixed


Custom view in body

Please, implemented or allow users insert custom views in body section.

What is wrong with
- (nonnull instancetype)initWithViewAndTitle:(nullable NSString *)title
                                     message:(nullable NSString *)message
                                       style:(LGAlertViewStyle)style
                                        view:(nullable UIView *)view
                                buttonTitles:(nullable NSArray<NSString *> *)buttonTitles
                           cancelButtonTitle:(nullable NSString *)cancelButtonTitle
                      destructiveButtonTitle:(nullable NSString *)destructiveButtonTitle;

Demo project has an example


CEF UDP Plugin does not handle non-standard (other than Application, Security, System) in post-Vista Windows forwarded by OSSEC Server.

From @gjahchan on September 14, 2016 8:48

Windows event logs other than the Application, Security and System logs in post-Vista flavors of Windows are silently dropped by the CEF UDP Plugin in Graylog2.
Expected Behavior

These events should be logged, much like any other event picked up by the CEF UDP plugin from OSSEC alerts.json file.

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

I will use an AppLocker event as an example:
In OSSEC alerts.json:

{"rule":{"level":2,"comment":"Windows - AppLocker allowed program to run.","sidid":18302,"firedtimes":13,"groups":["windows","applocker"],"PCI_DSS":["10.2.2","10.6.1"]},"dstuser":"GJahchan","full_log":"2016 Sep 14 10:44:43 WinEvtLog: Microsoft-Windows-AppLocker/EXE and DLL: INFORMATION(8002): Microsoft-Windows-AppLocker: GJahchan: DESKTOP: Desktop: %SYSTEM32%\NSLOOKUP.EXE was allowed to run.","id":"8002","status":"INFORMATION","data":"Microsoft-Windows-AppLocker","systemname":"Desktop","decoder":{"name":"windows"},"hostname":"Win10EntDsktp","agentip":"<IP_ADDRESS>","timestamp":"2016 Sep 14 10:44:56","location":"WinEvtLog"}

In Elasticsearch: (OSSEC alerts.json --> filebeat --> logstash --> elasticsearch)
{
"_index": "ossec-2016.09.14",
"_type": "ossec",
"_id": "AVcnqBakhBmn8wp-jU8U",
"_score": null,
"_source": {
"rule": {
"sidid": 18302,
"firedtimes": 13,
"groups": [
"windows",
"applocker"
],
"PCI_DSS": [
"10.2.2",
"10.6.1"
],
"description": "Windows - AppLocker allowed program to run.",
"AlertLevel": 2
},
"dstuser": "GJahchan",
"full_log": "2016 Sep 14 10:44:43 WinEvtLog: Microsoft-Windows-AppLocker/EXE and DLL: INFORMATION(8002): Microsoft-Windows-AppLocker: GJahchan: DESKTOP: Desktop: %SYSTEM32%\NSLOOKUP.EXE was allowed to run.",
"id": "8002",
"status": "INFORMATION",
"data": "Microsoft-Windows-AppLocker",
"systemname": "Desktop",
"decoder": {
"name": "windows"
},
"location": "WinEvtLog",
"@version": "1",
"@timestamp": "2016-09-14T07:44:56.000Z",
"fields": null,
"offset": 1937063,
"count": 1,
"input_type": "log",
"beat": {
"hostname": "capricorn",
"name": "capricorn"
},
"source": "/var/ossec/logs/alerts/alerts.json",
"type": "log",
"host": "capricorn",
"tags": [
"ossec",
"beats_input_codec_json_applied"
],
"AgentName": "Win10EntDsktp",
"AgentIP": "<IP_ADDRESS>",
"machine": "false"
},
"fields": {
"@timestamp": [
1473839096000
]
},
"highlight": {
"AgentName": [
"@kibana-highlighted-field@Win10EntDsktp@/kibana-highlighted-field@"
]
},
"sort": [
1473839096000
]
}
In Graylog2: (OSSEC alerts.json --> OSSEC csyslogd --> Graylog CEF UDP Plugin --> Graylog
Zero Applocker events.
I can confirm that OSSEC csyslogd is indeed forwarding AppLocker events by dumping traffic to udp port 2514:
$ sudo tcpdump -i lo -vvv -nn -p -A udp and port 2514

11:11:10.500410 IP (tos 0x0, ttl 64, id 56708, offset 0, flags [DF], proto UDP (17), length 507)
<IP_ADDRESS>.59218 > <IP_ADDRESS>.2514: [bad udp cksum 0xfffa -> 0xc1dc!] UDP, length 479
E<EMAIL_ADDRESS>.....<132>Sep 14 11:11:09 CEF:0|Trend Micro Inc.|OSSEC HIDS|v2.8|18302|Windows - AppLocker allowed program to run.|2|dvc=capricorn cs2=(Win10EntDsktp) <IP_ADDRESS>->WinEvtLog cs2Label=Location classification= windows,applocker,pci_dss_10.2.2,pci_dss_10.6.1, suser=GJahchan suser=GJahchan msg=2016 Sep 14 11:10:56 WinEvtLog: Microsoft-Windows-AppLocker/EXE and DLL: INFORMATION(8002): Microsoft-Windows-AppLocker: GJahchan: DESKTOP: Desktop: %SYSTEM32%\NSLOOKUP.EXE was allowed to run.

Activate AppLocker in Audit mode on Windows system with OSSEC Agent installed.

Configure agent to collect the AppLocker logs (in /var/ossec/etc/shared/agent.conf on OSSEC server):
<agent_config name="AgentName">

<log_format>eventchannel</log_format>
Microsoft-Windows-AppLocker/EXE and DLL

<log_format>eventchannel</log_format>
Microsoft-Windows-AppLocker/MSI and Script

<log_format>eventchannel</log_format>
Microsoft-Windows-AppLocker/Packaged app-Deployment

<log_format>eventchannel</log_format>
Microsoft-Windows-AppLocker/Packaged app-execution

</agent_config>

Add the following AppLocker-specific rules to /var/ossec/rules/local_rules.xml:
...

18103
^8000$
Windows - Application Identity Policy conversion failed.
pci_dss_10.6.1,

18101
^8001$
Windows - AppLocker policy was applied successfully to this computer.
pci_dss_10.6.1,

18101
^8002$
Windows - AppLocker allowed program to run.
pci_dss_10.2.2,pci_dss_10.6.1,

18102
^8003$
Windows - AppLocker allowed program to run in audit mode.
pci_dss_10.2.2,pci_dss_10.6.1,

18103
^8004$
Windows - AppLocker blocked program.
pci_dss_10.6.1,

18101
^8005$
Windows - AppLocker allowed an MSI or script to run.
pci_dss_10.2.2,pci_dss_10.6.1,

18102
^8006$
Windows - AppLocker allowed an MSI or script to run in audit mode.
pci_dss_10.2.2,pci_dss_10.6.1,

18103
^8007$
Windows - AppLocker prevented an MSI or script to run.
pci_dss_10.6.1,

18101
^8020$
Windows - Packaged app allowed.
pci_dss_10.2.2,pci_dss_10.6.1,

18101
^8021$
Windows - Packaged app audited.
pci_dss_10.2.2,pci_dss_10.6.1,

18101
^8022$
Windows - Packaged app disabled.
pci_dss_10.6.1,

18101$
^8023$
Windows - Packaged app installation allowed.
pci_dss_10.2.2,pci_dss_10.6.1,

18101
^8024$
Windows - Packaged app installation audited.
pci_dss_10.2.2,pci_dss_10.6.1,

18102
^8025$
Windows - Packaged app installation disabled.
pci_dss_10.6.1,

18102
^8027$
Windows - No packaged app rule configured.
pci_dss_10.2.2,pci_dss_10.6.1,

4. Restart OSSEC agent and OSSEC server:
    $ sudo /var/ossec/bin/ossec-control restart
    $ sudo /var/ossec/bin/agent _control -R
1. Install the CEF Syslog Plugin in Graylog2.
2. Configure the CEF UDP plugin on a specific port (2514 in my case).
3. Activate csyslogd in OSSEC and configure it to forward CEF format events to listener on UDP/2514.

<IP_ADDRESS>
2514
cef

## Context

This is a pilot for a PCI-regulated environment. In the target environment, the inability to bring in event logs other the standard Windows logs precludes the use of Graylog2, which (along with elasticsearch in SIEMonster) otherwise fulfills the majority of organizational security event and information management needs.

Your Environment

Graylog Version: 2.0.0-rc1.1
Elasticsearch Version: 2.2.0
MongoDB Version: 3.5.3-1
Operating System: debian jessie/sid
Browser version: Google Chrome v53.0.2785.101 m (64-bit) on Windows 10

(The machine is a SIEMonster Capricorn that is up-to-date as of the time of this posting).
Copied from original issue: Graylog2/graylog2-server#2825

Duplicate #9


Frostfruit inn - floating props

Describe the bug
Some firepit items, a mead cask, and a business ledger all hang in the air. the cask and ledger in particular impede NPC movement throughout the lower part of the building.
To Reproduce
Steps to reproduce the behavior:

Go to the Frostfruit inn (Rorikstead)
stuff floats

Expected behavior
less floating

This is likely caused by the holds patches, after checking some comments there. I'll fix them after I set up an SE version of the pack and do some further investigation.


How to change logging level?

While executing the crawler, it sends a lot of DEBUG level messages to the console. I've tried to override the configuration of Log4J using a log4j.xml in my projects, but it did not work, it keeps sending the DEBUG msg do the console. It seems that somehow crawler4j has its own configuration.

it is using slf4j and logback
On Mon, Apr 10, 2017 at 9:59 PM, Marco Aurelio Gerosa <
<EMAIL_ADDRESS>wrote:

While executing the crawler, it sends a lot of DEBUG level messages to the
console. I've tried to override the configuration of Log4J using a
log4j.xml in my projects, but it did not work, it keeps sending the DEBUG
msg do the console. It seems that somehow crawler4j has its own
configuration.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/yasserg/crawler4j/issues/207, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABrbW7ke826yKIYPtQsUDQFuC8jy5BFuks5runwJgaJpZM4M5LwO
.

@marcogerosa adding the following to /src/main/resources/logback.xml should do the trick
<configuration>

    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
        <!-- encoders are assigned the type
             ch.qos.logback.classic.encoder.PatternLayoutEncoder by default -->
        <encoder>
            <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
        </encoder>
    </appender>

    <root level="info"><!-- hush! -->
        <appender-ref ref="STDOUT" />
    </root>
</configuration>

ok, it worked. Thank you

Hi,
It seems that this is a common request. Can you make it part of the README?
Thanks!


python312Packages.pymodbus: 3.6.9 -> 3.7.2

Diff: https://github.com/pymodbus-dev/pymodbus/compare/refs/tags/v3.6.9...v3.7.0
Changelog: https://github.com/pymodbus-dev/pymodbus/releases/tag/v3.7.0
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 335212 run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.modbus

6 packages built:

expliot
expliot.dist
python311Packages.pymodbus
python311Packages.pymodbus.dist
python312Packages.pymodbus
python312Packages.pymodbus.dist

Part of #345326


Support allowing multiple notifiers to send out Notifications

@sfgeorge Whenever you have a chance to review this please.
CC: @rsuddeth
Pretty straight-forward change; replaces the notion of a single notifier with an array of registered Notifier classes. To preserve the original default behavior we list only a single notifier by default, AirbrakeNotifier, but we'll be overriding this in Phoenix itself to support the use of both Airbrake and Email.
The EmailNotifier was updated to include the environment from which we're sending out notifications (in the subject line). The host from which the notification originated from will be in the 'From:' field.

Looks great, thank you!! :+1:
@ajayanty Merging this, thank you!

@bklang @benlangfeld @polysics Howdy, guys!  Hope you're having a groovy Summer!
We liked the email support in adhearsion/adhearsion-reporter#10 and thought we'd extend it by being able to register multiple notifiers at the same time.  Would this be useful to the community?
Initially, we did this by changing the "notifier" property to "notifiers".  If you like the idea of this general, we're happy to add-back the support for the "notifier" property so that this is backwards-compatible.  What do you think?

Hody back Stephen!
First, thank you very much for taking the time to offer this to the community and to polish it up.  I think this is entirely appropriate to be merged upstream. I also agree that we'll want to keep backward compatibility with notifier.  My only other request would be to squash this before we merge it.
Thanks Stephen and Scott!

Thank you, Ben!  Sounds like a plan!  We're looking forward to contributing back to the community more often! =)

Just FYI our colleague Rachel (@rsuddeth) has just added-back backwards compatibility in our #2 PR.  We'll late polish it up so that it's all nice & squashed as it goes back into the mainline, but if you're curious of the overall diff, here it is!
https://github.com/cloudvox/adhearsion-reporter/compare/dd9f753...rsuddeth:feature/US6761-allow_notifier_with_notifiers
(FYI we have some additional functionality we added to the email notifier as well, such as mentioning the environment name.  We can easily pull that out in our upcoming 'notifiers' PR if you like)


Multiple Minor Fixes And Enhancement In Websites

Related Issue
Multiple Fixes And Enhancement In Websites
Fixes:  #1599  (issue number)
Description
1. Increased Button & Text  Size ( Poor  Visibility ) Of Book Now & View  Itineraries Button

before

now

2. Image was horizontally distorted in solo adventure page & It was not connected to solo_adventure.css

before

now
connected its css file

3. Images Are Not Aligned In Same ln On Romantic Gateway

before

now

4. Main  Page Image is distorted on flight booking page

before

now

5. Footer Links Are Not Connected on fly Page =+> Contact Section

=> Connected support to contact us page AND media to blog page under contact part (last section of footer)
@PriyaGhosal please review this
Type of PR

[x] Bug fix
[x] Feature enhancement

Checklist:

[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@samarth-6

@samarth-6 @PriyaGhosal please review this pr . it has been 2 days since generated


Deep compare arguments

readerAst is an array of ast nodes, there is no readerAst.arguments, it should be ok to compare these without ast, right?
Closes #126

No need to take a look at this now, I'll have to take a look what merge from main has changed

https://github.com/isographlabs/isograph/blob/3f50636d6d1a968ef0a88bf3f52f2d3ea81b769a/libs/isograph-react/src/core/componentCache.ts#L14-L16
Right now we just create a new component whenever, fragmentReference.variables change, so we don't have to do anything to rerender.
Don't we lose all the state doing this? We should probably change cache to have two layers:

unique id for every useLazyReference; not every fragmentReference, because it changes whenever variables change
component name

this way we can subscribe to change of variables and data with this unique id.
Is that what we want to do here?
If so, how do we generated a stable id, do we just use useId?

Right now we just create a new component whenever, fragmentReference.variables change, so we don't have to do anything to rerender.
Don't we lose all the state doing this?

This is a really good point. I'll think about this. Thanks for pointing that out.


Commented broken images code lines in README.md file

I have commented the code that leads to broken images in README.md file.

Fixes Issue
#476

Changes proposed

Removing/ commenting the code lines that leads to broken images in README.md file

Screenshots

Before remove/comment code.

After remove/comment code.

Note to reviewers

ok, So could you provide me some resource so, that I can add those icon.


To contribute to this project I am forced to share my behavioral data with Microsoft

To contribute to this project I am forced to register to Microsoft/ GitHub and create an account and I am forced to share my behavioral data. Microsoft knwo what system and dev tools I am using or at which times I am working and with whom I am connected or for which projects I am interested.
This is not Privacy by Design and Default. Is SAP or Telekom not fit and capable to run an own instance of GitLab or Gitea? Every small Developer can do this. Big projects like GNOME do this aswell. Why not SAP or Telekom?

Cry me a river.

@TomTeeJay this is ridiculous, GitHub being the de-facto standard for open source collaboration. Every serious developer in this world does already have an account on GitHub. And, to be honest, I do trust GitHub/Microsoft more than I will trust the "own instance" approach.
I don't want to be rude but, nobody forces you to collaborate here so, well..

Hey @TomTeeJay , thanks for raising your concerns. In our opinion, GitHub is a well-established and respected platform to maintain open-source projects. In case somebody does not want to create a GitHub account, it is possible to reach us via mail at<EMAIL_ADDRESS>