Go to File (Quick Open)

Type: Bug
Go to File (Quick open) on Command+P is not autofilling the selected word. when I type the work it is working fine which means the funcationlity is fine. But autofilling is not happening similar to Intellij which lacks the speed of my searching
VS Code version: Code 1.89.0 (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:10:10.196Z)
OS version: Darwin x64 23.4.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
3, 4, 4

Memory (System)
16.00GB (0.05GB free)

Process Argv
--crash-reporter-id db1f707a-c75c-4afc-949e-cf05d9476c88

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

turbo-console-log
Cha
2.10.4

vscode-generate-getter-setter
DSK
0.5.0

gitlens
eam
14.9.1

todo-tree
Gru
0.0.226

vscode-docker
ms-
1.29.1

remote-containers
ms-
0.362.0

sublime-keybindings
ms-
4.1.10

tsimporter
pmn
2.0.1

tabnine-vscode
Tab
3.98.0

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
tftest:31042121
vswsl492:30256859
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:30973076
dsvsc021:30996838
da93g388:31013173
pythonprc:31039816
dwnewjupytercf:31039676

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

FYI I am using the updated version only.

/duplicate https://github.com/microsoft/vscode/issues/194573

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Annotation support

How do you folks feel about supporting annotations, e.g.:
struct foo {
  1: i32 bar ( presence = "required" );
} (
  annotation = "Foo",
  another.annotation = "Bar"
)

Currently errors are produced when annotations are encountered.

This is definitely on the list of things we want to support in the not too distant future, just haven't had the bandwidth for us to work on it.

I'd be happy to add support for annotations.


"Refresh" on each entry in coin list

The button would create a transaction that sends-to-self the coin.

We'll do that as part of the overhaul of the UI. It might not make it into v1.


Use vimPlugin.extend, try to be more clever about treesitter grammars, add tests

My stab at #3.
I've tried to make everything work automagically, and added tests that show intended usage. I also updated the README accordingly. What do you think? Note that I moved the grammar patches to nvim-treesitter, it works a bit differently than tree-sitter (since recently I think).

vimPlugin.extend should prevent inter-plugin dependency breakage.
vimPlugins.nvim-treesitter.{withPlugins,withAllGrammars} now auto-adds the required norg grammars. I didn't find a way to make plain vimPlugins.nvim-treesitter work without triggering inifinite recursion.
See the tests for for detailed behaviour. I also added a GitHub workflow that runs them.

BTW I'm using it in my nixos system flake with further overriden nvim-treesitter and neovim (both from master branch) without issues so far

Now this is incredible, thank you so much!


Land Library form to add content

I see the 'keywords' are added to the form when you add Land Library content.
Personally, I would prefer to have that in a format that you can tick the box, not having to type it in.
Also, I think it's better to call it 'Overarching categories', not keywords. And then also have a separate field for the Themes (cross-cutting categories) and call those Themes. Keywords and topics is now very confusing and I wasn't even sure at first what the difference was. :)

Keywords is deprecated and was only intended/used by importers.
The LLR resource 'cleaning' is still a wider work in progress (Antonella).
Overarching and Themes have been added and should now be correct, also renamed topics to  concepts. For the field names, taxonomy bindings and selection widgets should be all good.


Migrate one test from compiler to regular code

The reason this works on all targets is that the test still passes even when Poko compiler plugin does not run. The next test, once the structure is approved, will require the compiler plugin and will contain the updates to ensure it runs on all targets.


Added missing instructions for sign in with Twitter.

Not related to an issue.
There are some additional permissions to be set to the Twitter app. The PR mentions them.

App details: Enable Sign in with Twitter must be checked
After creating the app: go to Permissions tab -> edit ->  Request email address from users must be checked
twitterOptions.RetrieveUserDetails = true; is already mentioned

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: MintPlayer sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Further improvements on textarea

Changed x-on:load.window to x-init and added wire:ignore after discussion on PR #8177

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Please remove the random key, we shouldnt do that

Ok do you have any suggestion on how to fix the problem?

Just a note: GitHub doesn't even seem to render auto-growing textareas at the full content height on page load, only after you start typing. Makes me think what's actually the best UX in this case.

Ok interesting point. I think that the possibility to immediately have a glance to the full content of a textarea without manually expanding each of them is very convenient, but if you think it is unnecessary we can rollback all the changes and update only on input.

We could use something like IntersectionObserver .
While this could work, it's ultimately up to you to decide whether it's worth it or not. Using markdown editor with no toolbar buttons might be a good alternative.

Little update: I have added an intersection observer as suggest by @qrasa1 on https://github.com/filamentphp/filament/pull/8193/commits/285b38bf4577275b376e882b85dba9f5b704e446. This indeed fixes the behavior with modal. I am still looking for a fix on a full page save.

Summarizing the updates as of now, the following cases are fixed:

initial page load (in dedicated init() function instead of  x-on:load.window as it is live now)
browser resize (with x-on:resize.window="render()")
modal opening (with x-intersect.once="render()").
Instead, in case of page refresh with Livewire the height is reset. The possible solution are:
wire:ignore but it breaks the conditional disabling
wire:key="{{ rand() }}" but it not a best practice
listen to a global Livewire page refresh event but I did not manage to find one.

Thanks


Add pynx-ellips plugin to extras

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 81.088%

Files with Coverage Reduction
New Missed Lines
%

tests/dataconverter/test_writer.py
1
96.77%

pynxtools/dataconverter/convert.py
2
75.14%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2564

Relevant Lines:
3162

💛  - Coveralls


fix(datastore): observeQuery snapshot on ready event

Issue #, if available:
https://github.com/aws-amplify/amplify-ios/issues/1759
Description of changes:
ObserveQuery is an opinionated API that provides a stream of data snapshots including the sync state. Roughly the behavior of the snapshot's emit intervals is this: The intervals adjusted based on the sync state, sending less frequent snapshots during the syncing process and more frequent snapshots after is synced. The issue, which was confirmed other platforms do not have and is expected, is that in between the last snapshot during sync and the first snapshot after sync is that the operation is missing a snapshot to indicate the sync state toggle. The customer impact is when there is an infrequent number item changes after syncing then the first snapshot after sync is delayed until there is a new item change, causing a large interval between the two snapshots.
The fix is to listen for the datastore ready event and emit a snapshot when receiving the ready event, which introduces the behavior of the missing snapshot.
Check points: (check or cross out if not relevant)

[ ] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2105 (3d7a733) into main (f0c3534) will decrease coverage by 0.01%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##             main    #2105      +/-   ##
==========================================
- Coverage   59.50%   59.48%   -0.02%
==========================================
  Files         719      719
  Lines       22561    22568       +7
==========================================
  Hits        13425    13425
- Misses       9136     9143       +7

Flag
Coverage Δ

API_plugin_unit_test
62.47% <ø> (-0.10%)
:arrow_down:

AWSPluginsCore
70.29% <ø> (+0.07%)
:arrow_up:

Amplify
48.20% <ø> (-0.04%)
:arrow_down:

Analytics_plugin_unit_test
71.09% <ø> (ø)

Auth_plugin_unit_test
78.16% <ø> (ø)

DataStore_plugin_unit_test
75.60% <57.14%> (-0.04%)
:arrow_down:

Geo_plugin_unit_test
52.12% <ø> (ø)

Predictions_plugin_unit_test
26.81% <ø> (ø)

Storage_plugin_unit_test
58.04% <ø> (ø)

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

Impacted Files
Coverage Δ

...gin/Subscribe/DataStoreObserveQueryOperation.swift
75.00% <57.14%> (+0.35%)
:arrow_up:

Amplify/Categories/Hub/HubFilter.swift
47.36% <0.00%> (-10.53%)
:arrow_down:

...lugin/Operation/AWSAPIOperation+APIOperation.swift
73.68% <0.00%> (-5.27%)
:arrow_down:

...oreCategoryPlugin/Sync/Support/Model+Compare.swift
68.75% <0.00%> (-3.13%)
:arrow_down:

...e/AWSPluginsCore/Auth/AWSAuthServiceBehavior.swift
87.50% <0.00%> (+12.50%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Autogenerate the docstring examples

There is a https://deprecat.readthedocs.io/en/latest/source/usage.html#docstring section which is hardcoded in rST instead of showing the actual output.
I would try to create a showcase module inside the library that is not used by it nor exposed when imported but has one example of each deprecation type, class, function, method, kwarg... and then create a showcase api docs. I think this will serve also as a rudimentary test that the output looks as desired when doing changes in a way that automated tests can't

this was a great idea, i did this just now https://deprecat.readthedocs.io/en/latest/source/api.html#examples thanks @OriolAbril !!!


Update ch8-04-4.md

读不通顺，参考原文发现少译了一部分。

Channels are deeply connected to goroutine scheduling, and without another goroutine receiving from the channel, a sender—and perhaps the whole program—risks becoming blocked forever.

thx！


大家都是怎么使用Apollo这个平台的？

大家好，我是一名研一的学生。然后导师想做自动驾驶相关的项目，购买了一套Apollo的D-kite套件，现在基本上把官网的教程快全部跑完了，想问一下大家，接下来可以做哪些研究呢？是从代码角度继续借由Apollo平台研究无人驾驶的架构还是使用LGSVL绘制高精地图呢？大家有什么建议吗？谢谢大家啦~

You can do it in many ways.
You know that autonomous driving systems can be divided into: localization, perception, planning, and control modules. choose anyone you are interested in and dive in it.
First, you can search on the Internet and learn about good practices and the state-of-art methods for solving problems.
Second, you can read the code and learn from it then improve it.
Last, you can do some meaningful projects. There are many open source autonomous driving small projects on the Internet. Like carla, dataviz

You can do it in many ways.
You know that autonomous driving systems can be divided into: localization, perception, planning, and control modules. choose anyone you are interested in and dive in it.
First, you can search on the Internet and learn about good practices and the state-of-art methods for solving problems.
Second, you can read the code and learn from it then improve it.
Last, you can do some meaningful projects. There are many open source autonomous driving small projects on the Internet. Like carla, dataviz

好的，很有帮助，谢谢你。昨天我还在看您那篇Dig-into-Apollo呢，写的很好，对我很有启发。

好的，很有帮助，谢谢你。昨天我还在看您那篇Dig-into-Apollo呢，写的很好，对我很有启发。

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


[Question] build own CDN service?

HI, would you pls tell which part on readme show any solution to build own CDN service

Your question is unrelated to this project.


send_transaction mutation returns non-encoded txid

The following graphl query:
mutation SendTx {
  send_transaction(
    request: {
      encoded_hex: "0100000001f17ebad1a9324ff82faf9b5054066bc5172bc6cf3ea78219400648a61015eb07000000006441cbed835372fca913a22b41fa1f54a62fcf2d66de86b59444bd8fbf3d4ba4056c2ceb58e34fa5d7222535a4759d465fa7fc4bcf474e1d938f32ccfe5b5816de8141210277ca380aff06f4cb50047c14a4ec192b0c9d30d5caad7fc9b4002bc0a69ecd59feffffff0239590000000000001976a914fe0d9c981cd67b0181d5f994ac77b391fe74244988ac97c57900000000001976a9146aef70d3eb17970780647492589deb34b18eab6f88ac87f90b00"
      node_internal_id: 3
    }
  ) {
    transaction_hash
    validation_success
    transmission_success
    transmission_error_message
    transmission_error_message
  }
}

returns:
{
  "data": {
    "send_transaction": {
      "transaction_hash": "8d800122aa869bb081f8308aebdad74fc96ae8e565af600c6dace2454533e237",
      "validation_success": true,
      "transmission_success": true
    }
  }
}

but for consistency I think it should return:
{
  "data": {
    "send_transaction": {
      "transaction_hash": "\\x8d800122aa869bb081f8308aebdad74fc96ae8e565af600c6dace2454533e237",
      "validation_success": true,
      "transmission_success": true
    }
  }
}

Thanks for the issue!
Yes, there are several places where the returned result is just a hex string rather than Postgres' bytea hex encoding. My preferred solution would be to fix https://github.com/bitauth/chaingraph/issues/48 such that all hex-encoded values are returned without the escape sequence.
I'm not able to focus on this currently, but I would love to merge a PR if you're interested!


Specified defaults and lockout mechanism

@mmcla : Thanks for your contribution! The author, @MicrosoftGuyJFlo, has been notified to review your proposed change.

Moved change to release branch to get updated. #please-close


Better Excel compability

Hi David,
I am using your library in a project and it's very nice, saved me some work :). However, our users mostly use Excel and there are two problems with Excel:

it does not properly open the file unless you explicitly state the separator you are using on the first line with 'sep=SEPARATOR'
it does not play well with utf-8, so we needed utf-16le. But since we are getting the data from somewhere else, we get it in utf-8, and we needed to re-encode it.

I made some modifications to address these problems:

I added the possibility to add the separator on the first line with the add-sep attribute (just like add-bom)
I implemented some encoding methods for utf-8, utf-16, utf-16le and utf-16be so that when these charsets are used, it returns a correctly encoded file.

I need these fixes, so for now I will use my repository, but if you choose to put them in the main repository, it would be great.
Cheers,
Eugen

hello,
I have the same problem as you. I tried also with charset="windows-1252" or iso-8859-1 or ANSI or ansi.
I also tried to change the charset directly in the JS code :+1:
...
var charset = scope.charset || "windows-1252";
...
everywhere utf-8 was present, but at the end, it seems to not use the given charset, using all the time the UTF-8. Is there something to do previously to specify the charset?
Thanks

@Phoenix1978
Hi,
You can check my fork https://github.com/eugenpodaru/ng-csv. I have added some code to convert between different charsets. I use \t as field separator, utf-16le as charset, and I also add the BOM, and it works perfectly for me.
Eugen

Thanks a lot, it works well.

Can I ask you another question, I try to load your fork version directly using bower with this address: https://github.com/eugenpodaru/ng-csv.git
But it don't get the version I can download via the relevant button or via the github website directly.
Do you know which address i had to put to automatically get via bower the last version?

@Phoenix1978
Hi,
You need to prepend the commit id (hash) https://github.com/eugenpodaru/ng-csv.git#a2aea1f
Regards,
Eugen

Ok I understand better, thanks again

@Phoenix1978
Hi,
When you put https://github.com/eugenpodaru/ng-csv.git in bower it will take the latest tagged commit. So in order for that to work I should increase the version number and tag the latest commit.
But I want to be in synch with the original repository when it comes to versioning, so that's why I did not do that.
Eugen

@eugenpodaru Did you not go through with this PR? I think this should definitely be added to the library, it is great!
I've been trying to add a region-independent solution, and as far as I can see the best solution is UTF16-le with \t as separator.

@eirikb Yes, the solution that worked for me was UTF16-le and \t as separator. My fork has support for encoding to UTF16-le.
As for the PR, I need to rethink how the encoding is integrated with the solution before I make another PR.


"Source file '...' not found." error occurs at version 6.2.2-dev.7 with Bun.

Describe the bug
I'm using Bun(1.1.4), and got Source file '...' not found. Check your 'entitiesTs' option and verify you have 'compilerOptions.declaration' enabled in your 'tsconfig.json'. If you are using webpack, see https://bit.ly/35pPDNn error while using v6.2.2.
My mikro-orm.config.ts looks like this:
export default defineConfig({
  // other configs
  entities: ['./src/**/entities/*.entity.ts', './src/lib/ddd/BaseEntity.ts'],
  entitiesTs: ['./src/**/entities/*.entity.ts', './src/lib/ddd/BaseEntity.ts'],
  metadataProvider: TsMorphMetadataProvider,
})

I tried to pass full paths of the entity files and use imported entities, but it was the same.
The version where this bug first started occurring is 6.2.2-dev.7.
I looked up the diff between .7 and .6 and found this commit (d64be7e) has to do with the issue.
I don't fully understand the code base, so I can't diagnosis what caused the problem right now.
Please help me to fix it.
Reproduction
You need Bun v1.1.4, and v6.2.2-dev.7 of mikro orm.
What driver are you using?
@mikro-orm/postgresql
MikroORM version
6.2.2-dev.6
Node.js version
Bun 1.1.4
Operating system
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
[X] The provided reproduction is a minimal reproducible example of the bug.

See this discussion for explanation https://github.com/mikro-orm/mikro-orm/discussions/5496#discussion-6544778. I have started to work on the PR to fix that.

@Ruby184 Sorry for missing the discussion. Then let me close the issue and follow your work.


How can i get the peak json data of an audio；

versions<EMAIL_ADDRESS>
I want to get the peak json data of an audio,how to do that?

I have not found the api about this;
could someone help me ?

what i want the peak data just like this :
[
{'x':1.00 ,'y':-66.14356552},
{'x':2.00 ,'y':-66.3397134},
{'x':3.00 ,'y':-66.90808776}
.....
]

You can read it here.
Good luck!

You can read it here. Good luck!
Is there someway generate waveform data on the client in browser?;

For now you may follow the https://github.com/bbcrd/audiowaveform route as specified in the FAQ here https://wavesurfer-js.org/faq/
I had a service that did just this online before, once I update to the new domain I will be adding a api integration for wavesurfer.js project as a plugin.


Update datetime_convert.py

Trying to change to create pull request

Left over from class, submitted to incorrect repo


Don't hide loading state

If a query is loading but was found from cache the current implementation tells us that the loading is false.
I'd like if this app would report errors, loading and data independently because there may be a case where a query has data from cache and is loading and I'd like to display a loading indicator alongside the data to show that it is loading and if this query errors I'd like to show the error but not stop showing the cached data.
What's your take on this API change? I'm using a fork that does this and if you agree on this change of the API I could submit a PR with it.

I'll try to show in code what I mean. Currently if the data is cached then it won't pass the loading state.
But we could say that it is loading AND give the result, so we may show the old data and show an icon that tells the user new data is being fetched.
Like here.

@degroote22 Nice idea!

#199 adds an optimistic field to results, which I think we could extend to queries here to indicate an optimistic cache response

We should really just add a responseType enum or something, as there are so many aspects to this basic problem.
A result can be some vector of loading, eagerly returned from cache,  optimistic only, optimistic with partially normalized results from cache, eager with the previous call to the query, etc, etc.
Will take more consideration

Maybe change QueryResult introducing fields like networkLoading and fromCache. This way is possible to know if a result is coming from the cache while waiting for a Network updated response.

Closed with a source attribute on QueryResult:
/// The source of the result data contained
///
/// Loading: No data has been specified from any source
/// Cache: A result has been eagerly resolved from the cache
/// OptimisticResults: An optimistic result has been specified
///   (may include eager results from the cache)
/// Network: The query has been resolved on the network
///
/// Both Optimistic and Cache sources are considered "Eager" results
enum QueryResultSource {
  Loading,
  Cache,
  OptimisticResult,
  Network,
}

:tada: This issue has been resolved in version 1.1.1-beta.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Build instructions broken

The doc says:
"Note: <DISCOUNT_DIR> is the directory that contains the include directory that contains mkdio.h Probably you need to specify --with-discount=/usr or --with-discount=/usr/local"
But on recent debian based distros, the path to the file mkdio.h is:
/usr/include/x86_64-linux-gnu/mkdio.h
I symlinked it to /usr/include/mkdio.h and it seemed to work.

Hi,
./configure --with-discount=/usr will find /usr/include/x86_64-linux-gnu/mkdio.h
see:
https://github.com/hamano/apache-mod-markdown/blob/master/configure.ac#L29
so no need to link symlinks.


Please expand on what "Monitor OS vulnerabilities in Azure Security Center" specifically monitors

Documentation says "Servers which do not satisfy the configured baseline will be monitored by Azure Security Center as recommendations". This sentence does not make sense. Which baseline is being referred and what action exactly means and how to re-mediate it?

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

ID: 9c78cb0a-edfb-a403-1096-1aeaaa5344fc
Version Independent ID: 77d5f52a-08ad-edc0-14e5-f8f9fb05c739
Content: Azure policy definitions monitored in Azure Security Center
Content Source: articles/security-center/security-center-policy-definitions.md
Service: security-center
GitHub Login: @rkarlin
Microsoft Alias: rkarlin

@artisticcheese  Thanks for your feedback! We will investigate and update as appropriate.

@artisticcheese Azure Security Center monitors security configurations by applying a set of over 150 recommended rules for hardening the OS. If a machine is found to have a vulnerable configuration, Security Center generates a security recommendation.  Please refer to What are OS security configurations? for details.

There is no option to see Security Configuration in my Security Center. Also if I look for computers which report compliant vs which are reported non compliant. Both of those report as missing something. How exactly decision is being made which one is compliant and which is not

@artisticcheese Complaint/Non-Complaint statuses are based on the security policies you have applied to your management group or subscriptions.  Please refer to Create a policy assignment to identify non-compliant resources
Also, you can refer to below screenshot to to check the OS configurations which are assessed by Azure Security Center.

@artisticcheese We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Languages: Add yield keyword in PHP

Please, see http://php.net/generator.

Hi @Hywan, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks @Hywan !

You're welcome :-).


system_fingerprint is None

Confirm this is an issue with the Python library and not an underlying OpenAI API

[X] This is an issue with the Python library

Describe the bug
Per the documentation here, the OpenAI API should return a system_fingerprint. However, when calling any model that is not gpt-3.5-turbo-1106 or gpt-4-1106-preview, the system_fingerprint is always None.
Is this working as designed? Is this parameter only supported in these two models? If so, can this requirement be documented? The link above doesn't mention this requirement and neither does the API documentation.
To Reproduce

copy and paste notebook here
change this line to an older model:
GPT_MODEL = "gpt-3.5-turbo-1106"

For example:
GPT_MODEL = "gpt-3.5-turbo-0613"

the system_fingerprint returned is None

Code snippets
No response
OS
Unix
Python version
Python v3.10
Library version
openai v1.6.1

@elisa-abridge – the section you've linked to is marked "beta", which is probably why it's only available in certain models.
cc @logankilpatrick @nknj – I assume the linked docs should be updated for clarity?
Either way, this does not sound like a bug in the SDK, so I'm going to go ahead and close this issue.

The API documentation does not have any beta flag and has system_fingerprint. The API is not behaving as documented currently.
Here is the link to the API documentation:
https://platform.openai.com/docs/api-reference/chat/object

Note that the types in this SDK indicate that system_fingerprint may be None.


Changing Configuration causes the visible region of the map to change.

https://user-images.githubusercontent.com/1428315/213885855-2c2f94f5-ec59-4d15-b481-82c1a5329938.mov
See video above. Discovered while resolving #18. cc @HanSolo

This issue only surfaces when switching from hybrid to imagery (and in reverse) configuration styles. Other transitions appear to be fine.

Works great with 0.06


How to install via RPM?

I'm a bit confused as what this means:
The distributions provided for Divolte Collector are:

A .tar.gz archive distribution containing the binaries and startup scripts.
A .zip archive distribution containing the binaries and startup scripts.
A RPM that can be installed onto Red Hat/CentOS systems. This includes startup and init scripts.

Where can I find this RPM package?

It's linked from the website (divolte.io) under Downloads. Direct link for 0.9.0 is here.

When I install the package:
yum install -y http://divolte-releases.s3-website-eu-west-1.amazonaws.com/divolte-collector/0.9.0/distributions/divolte-collector-0.9.0-2.el7.noarch.rpm

it installs fine but after
service divolte-collector start

It doesn't occupy any port, journalctl -xe:
pam_unix(runuser:session): session opened for user divolte by (uid=0)
runuser[29721]: pam_unix(runuser:session): session closed for user divolte

Status is running (exited). So something seems to be wrong with the rpm package and I don't get any errors. I got divolte running using the tar, but I would like to have it as a service so I can monitor it more easily.

Anything in /var/log/divolte* ?

JAVA_HOME is not

Ok, I've set
JAVA_HOME=/usr/
in /etc/divolte/divolte-env.sh and it now runs fine!
I know that using logs in var/log is common practice, but an error on the service level would make sense as well, I wouldn't have opened this ticket otherwise.


(PE-26658) apply JVM security policy to FIPS

For full FIPS certification, you must disable the security providers
that are not compliant and make the BC FIPS provider the primary
provider.
The BC FIPS provider requires the BCFKS keystore implementation instead
of JKS.
The Sun SSL provider isn't present, but adding the BC-TLS jar gives us a
proper TLS implementation.

Works in JDK 8, fixing it in JDK 11 now


README: Add a mention to cxxopts dependency

From what I tried:
https://github.com/jarro2783/cxxopts

master: build failed
v2.0.0: build failed
v1.4.4: build success
v1.4.3: build success
v1.4.2: build success
v1.4.1: build success
v1.4.0: build faild

Fixes https://github.com/QuantStack/xeus-cling/issues/92

thanks @r9y9 !!


dblp lookup

Finding conferences by proceedings title  in the dblp dataset should work.
Acceptance criterion
Situation
"Proceedings of  8th International Conference on Software Engineering and Knowledge  Engineering (SEKE’96), Nevada, June 1996" is cited in https://archive.org/stream/springer_10.1007-3-540-49205-4/10.1007-3-540-49205-4_djvu.txt
Action
Lookup conference by proceedings title
Expected Result

https://dblp.org/rec/xml/conf/seke/1996.xml

<dblp>
<proceedings key="conf/seke/1996" mdate="2014-12-04">
<title>
The 8th International Conference on Software Engineering and Knowledge Engineering, SEKE '96, Lake Tahoe, Nevada, USA, June 10-12, 1996
</title>
<booktitle>SEKE</booktitle>
<publisher>Knowledge Systems Institute</publisher>
<year>1996</year>
<isbn>0-9641699-3-2</isbn>
<url>db/conf/seke/seke1996.html</url>
</proceedings>
</dblp>

as part of series https://dblp.org/db/conf/seke/index


Clion 2023.1 non-project files protection window bugged

The Selector is bugged. After hovering over it it displays text and wrong colors below that. It also appears that this happens every time i drag my mouse over the buttons again.
Also this is just an assumption but i think it is displaying the window name "Clion non-project files protection" after hovering over it.

Hi @codethinki, is this caused by this plugin? You can remove the plugin and restart the IDE to check if the plugin is causing the problem. Because I have no idea about the non-project files protection, so I need to make sure.

no sorry confused tabs in browser nevermind


报错

WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 15 total children
WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 17 total children
WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 19 total children
WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers),
之前用elementor 去编辑wordpress 首页，不会卡顿，但现在连保存都成问题

是不是安装了很多wordpress插件或者访问有链接被墙的url？

插件还好，不多，服务器在硅谷，这个可以排除
主要是另外一台服务器配置还低，2核2G，感觉不到卡，这台2核4G反而卡顿

问题定位到了吗？


Using $FILE:wsdlendpoint syntax for publishWSDL attribute in integration studio

Problem
Hi Team,
This ticket is related to [1].
MI 4.2.0-alpha currently supports injecting values into publishWSDL attribute of the proxy services via a properties file. For example, the following.
<?xml version="1.0" encoding="UTF-8"?>
<proxy name="SampleProxy" startOnLoad="true" transports="http https" xmlns="http://ws.apache.org/ns/synapse">
    <target>
        <inSequence/>
        <outSequence/>
        <faultSequence/>
    </target>
    <publishWSDL uri="$FILE:endpointURL"/>
</proxy>

However, this syntax ($FILE:endpointURL) is not allowed in the integration studio 8.1.0. I tried this after updating the integration studio as well, but experienced the same result. To be more specific, the following error is shown in the integration studio.

[1] - https://github.com/wso2-enterprise/wso2-apim-internal/issues/1622
Solution
Update integration studio to support $FILE:wsdlendpoint syntax for publishWSDL attribute in proxy services.
Affected Component
MI
Version
4.2.0-Beta
Implementation
No response
Related Issues
No response
Suggested Labels
No response

Did the change in wso2-synapse integration-studio branch. But still a error pops up without the reason.

It was identified that the above Error message is a result of an NPE thrown from synapse-core.jar, when accessing the value of endpointURL attribute from a Map which should be initialised and populated reading file.properties file.
Unlike in MI where we have file.properties inside the conf directory,  in an integration-studio project file.properties file is not available.


Timeout while downloading Artifacts

BCContainerHelper 6.0.17 timeouts when downloading artifacts
Trying to download artifacts from both bcinsider and bcartifacts storage.
After 5 mns of downloading, the bccontainerhelper would raise an error :
Downloading artifact /sandbox/24.1.18927.20043/fr
Downloading C:\Users\ronny\AppData\Local\Temp\4d47bdec-9358-413c-9456-c5348d593993.zip
Could not download from CDN..., retrying from blob storage in 6 seconds...

Scripts used to create container and cause the issue
$artifact = Get-BCArtifactUrl -storage bcartifacts -type sandbox -version 24.1 -accept_insiderEula -country fr -select latest
Download-Artifacts $artifact

Full output of scripts
PS C:\Windows\System32> Import-module bccontainerhelper
BcContainerHelper version 6.0.17
WinRM service is not running, will not try to use WinRM sessions
BC.HelperFunctions emits usage statistics telemetry to Microsoft
Running on Windows, PowerShell 7.4.2
WARNING: The names of some imported commands from the module 'bccontainerhelper' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
PS C:\Windows\System32> $artifact = Get-BCArtifactUrl -storage bcartifacts -type sandbox -version 24.1 -accept_insiderEula -country fr -select latest
PS C:\Windows\System32> Download-Artifacts $artifact
Downloading artifact /sandbox/24.1.18927.20043/fr
Downloading C:\Users\ronny\AppData\Local\Temp\4d47bdec-9358-413c-9456-c5348d593993.zip
Could not download from CDN..., retrying from blob storage in 6 seconds...

Additional context

it happens very very frequently
I've noticed it started after the release of BC 24. I've never had this issue before.

Could you try to run:
$bcContainerHelperConfig.artifactDownloadTimeout = 0

I have this error
PS C:\Windows\System32> $bcContainerHelperConfig.artifactDownloadTimeout = 0
PS C:\Windows\System32> Download-Artifacts $artifact
Downloading artifact /sandbox/24.1.18927.20043/fr
Downloading C:\Users\ronny\AppData\Local\Temp\7185dd16-8833-49c4-83be-a6a3bbb133e4.zip
Could not download from CDN..., retrying from blob storage in 5 seconds...
Download-Artifacts Telemetry Correlation Id: c2e39fcd-85c0-45a6-96fd-97d9f72e99ae
Exception: C:\Users\ronny\OneDrive - Capset\Documents\PowerShell\Modules\bccontainerhelper\6.0.17\Common\Download-File.ps1:95
Line |
  95 |                  throw (GetExtendedErrorMessage $_)
     |                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Exception setting "Timeout": "value ('00:00:00') must be greater than '00:00:00'. (Parameter 'value') Actual value was 00:00:00."

The artifactDownloadTimeout is default 300 seconds - but I will increase that to 600 seconds.
If your runners are slower than this, you would need to add this setting to bccontainerhelper.settings.json on your runners (or specify it in al-go repo settings if running AL-Go for GitHub)

which settings exactly in the al-go repo settings ? I can't find it on https://github.com/microsoft/AL-Go/blob/main/Scenarios/settings.md

in .github/AL-Go-Settings.json you can specify settings for BcContainerHelper directly.

So I added the config in the AL-GO-Settings.json but It's skipped during the build phase :
Import from C:\ProgramData\BcContainerHelper\6.0.17\BcContainerHelper\BcContainerHelper.ps1
BcContainerHelper version 6.0.17
Ignoring config setting artifactDownloadTimeout as the type in the config file is different than in the default configuration
Ignoring config setting defaultDownloadTimeout as the type in the config file is different than in the default configuration
BC.HelperFunctions emits usage statistics telemetry to Microsoft
Running on Windows, PowerShell 7.4.2
use settings and secrets
Analyzing repository
  Checking type
  Checking appFolders, testFolders and bcptTestFolders
  Application Dependency <IP_ADDRESS>
  Checking artifact setting for project
  Downloading artifacts from https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/sandbox/24.0.16410.20025/fr
  Downloading platform artifact /sandbox/24.0.16410.20025/platform
  Downloading C:\Users\Administrateur\AppData\Local\Temp\66f7a408-59c8-45d4-8f1e-652ee873[68](https://github.com/CapsetPF/Capset_AL_Framework/actions/runs/9260111950/job/25473310589#step:8:70)ae.zip
  Could not download from CDN..., retrying from blob storage in 2 seconds...

That is actually a new bug caused by a type difference in PowerShell 7
Only thing you can do right now is to run PowerShell 5.1
I will fix the issue in ContainerHelper asap

Fixed in 6.0.18


barcode-detector not mentioned

I wanted to use this but was about to give up because I found no example using the webcam. You should advertise barcode-detector in this repo too, and maybe mention "camera" and "barcode" as keywords.

Yeah, probably I should, but barcode-detector doesn't have examples about using the webcam either 🫤. Currently camera is not in the scope of these two repos. Perhaps you want to take a look at some higher level repos like vue-qrcode-reader.
A react component was planned in this repo, but I got less and less time to complete it. Meanwhile, I'm also preparing a breaking major version change to encompass the latest code from zxing-cpp and zint 😩

barcode-detector is now mentioned in the v2 README file: https://github.com/Sec-ant/zxing-wasm?tab=readme-ov-file#faq


[SPARK-34551][INFRA] Fix credit related scripts to recover, drop Python 2 and work with Python 3

What changes were proposed in this pull request?
This PR proposes to make the scripts working by:

Recovering credit related scripts that were broken from https://github.com/apache/spark/pull/29563
raw_input does not exist in releaseutils but only in Python 2
Dropping Python 2 in these scripts because we dropped Python 2 in https://github.com/apache/spark/pull/28957
Making these scripts workin with Python 3

Why are the changes needed?
To unblock the release.
Does this PR introduce any user-facing change?
No, it's dev-only change.
How was this patch tested?
I manually tested against Spark 3.1.1 RC3.

Thanks guys. I just made a simple cleanup. I will merge this once linters pass.

Test build #135502 has started for PR 31660 at commit 6b510a0.

Merged to master and branch-3.1.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40083/

Test build #135502 has finished for PR 31660 at commit 6b510a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135502/


APK files in releases show wrong version number

For the 1.4 release, the APK still shows 1.4:
package: name='cn.nekocode.camerafilter' versionCode='1' versionName='1.0'

Could you please upload a fixed version, and keep numbers in sync? Thanks in advance!

Yes, I will fix them in the next version. Thanks for your suggestion.

Thanks a lot! Please let me know then (I'll leave this issue open for that purpose). I'd really like to include your app with my repo, if that's OK with you :)

Yes, of course that's OK. I have already fixed it just now, you can take a look at the 1.5 version.

Thanks a lot! Here you go ;) Maybe you also want to add some license information – if you already chose a license, that is?
PS: If you want me to add/change something to the description, let me know. I basically copied the details from the README.md of the project.

Thanks for your reminder, I had already declared the license for this project at the top of README.md (see the badge).

Ouch :see_no_evil: Sorry, sure. I was looking for some License.* file. As those badges at that position in most cases show results from build processes etc, I've started ignoring them...
Thanks again!

Um, it just happened again: v2.1.1 and v2.2 have the same versionCode:
package: name='cn.nekocode.camerafilter' versionCode='211' versionName='2.1.1' platformBuildVersionName='6.0-2704002'
package: name='cn.nekocode.camerafilter' versionCode='211' versionName='2.2' platformBuildVersionName=''

To not have my repo stuck, I've removed v2.1.1 manually. Please ensure to update both, versionCode and versionName when releasing a new version :)

@IzzySoft Ok, I will remember it ~


uninitialized constant Informers::Utils::Hub::VERSION (NameError)

Hi!
With the following file:
require "informers"

qa = Informers.pipeline("question-answering")
qa.("Who invented Ruby?", "Ruby is a programming language created by Matz")

I'm receiving the error:
lib/ruby/gems/3.3.0/gems/informers-1.0.0/lib/informers/utils/hub.rb:43:in `get_file': uninitialized constant Informers::Utils::Hub::VERSION (NameError)

 headers["User-Agent"] = "informers/#{VERSION};"

Thanks @pedroaugustofsilva! Just released 1.0.1.


 A few small things for you to take another look.
Selection methods: For consistency, Is it possible to add a caption under the image for the Multiple categories section? I noticed captions are added to the Single selection and Multiselect sections but not Multiple categories.

Behaviors: Are "Scroll" and "Keyboard interaction" only tailored to Larger breakpoints (max, xl, LG)? If they are, the "Scroll" and "Keyboard interaction" need to be styled a level down. If not, will it work better to have the sections in the order of"Larger breakpoints (max, xl, LG)," "Smaller breakpoints (MD and sm)", "Scroll", then "Keyboard interaction"? I wonder if this helps adopters see the differences between the groups of two breakpoints better?

Looks like James's feedbacks are addressed as well. Since he's out this week, I will clear's request for change and merge this one. Great work!


fix: typo in docs in creating custom_llm huggingface example about st…

Description
This is a fix about a typo in docs in creating custom_llm huggingface example in stablelm_predictor declaration.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[X] I stared at the code and made sure it makes sense

thanks!


Get rid of ValueUtils

cooked-validators should not provide any kind of utility module. This goes against the philosophy of it being minimal. We still have a few utils in ValueUtils.hs. Let's see if they are not already provided by plutus-script-utils, or if they could be removed/replaced altogether.

I found a builtin equivalent of our positivePart and negativePart functions.


data.vespa.oath.cloud -> data.vespa-cloud.com

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Checks fail due to new vespa.ai release yesterday that broke some links and removed some assets.


[PAGOPA-1012] feat: added queries for search by broker description

This PR contains two new queries that will be used by APIConfig core service in order to permits a search by broker description.
List of Changes

Added two queries for search by broker description.

Motivation and Context
These changes are required in order to permits the seach by broker description by APIConfig core backend and by the frontend portal.
How Has This Been Tested?

Tested in local environment

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as
expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

update_code


Update for Arduino Due support

Updated your awesome FIFO code to support the Arduino Due

Awesome work, thanks for the pull request!
Quickly looking over your pull request, I believe this might already be implemented in the dev branch which uses this SimplyAtomic for handling saving a restoring interrupts.
Please take a look, and let me know if I am mistaken.

  It was a drop in replacement for my Sam3 code.
Had put this together back in December, just hadn't gotten around to uploading.  You beat me to it!  Seems to be working well.  Maybe it deserves to be in the main branch?

Should of pushed it in December and saved me the trouble!
I plan to replace master with it at some point, but I am yet to have been able to test it on most of the platforms it is supposed to support, glad to hear it is working correctly on ARM.

Haha.  Yep.  Procrastination is one of my weaknesses...
I'll see if I can write a test case for you on AVR in the next month or two.  If you don't see anything by then, send a message as a reminder!

Same here...
That would be fantastic, thanks!


[WebSocketServer][SSL] WSS does not work

Godot version:
3.1.beta2
OS/device including version:
Clientside : Gentoo Linux Kernel 4.20 / Serverside : Debian 9 Kernel 4.9
Issue description:
When serving a HTML5 game on HTTPS, we must use secure websockets (wss:// instead of ws://).
However, we can't just do this because nothing is happening on the server (the client browser is performing certificates verification but the godot linux server ignores it).
How do you tell the godot server to start using TLS with a privatekey ? This seems unclear in the wiki because you can't just add the privatekey in a .crt file.
Error at this point
Error in connection establishment ; net::ERR_SSL_PROTOCOL_ERROR

Update: Should I use a nginx proxy so that nginx handles TLS traffic and then redirect it to the godot server ?

Fixed by using 'proxy_pass' with nginx. See https://www.nginx.com/blog/websocket-nginx/

I am having the same issue as you with ws and wss. I spent quite a bit of time trying to understand how to fix it with nginx but I have not made much progress so I am wondering if you could give a few short step by step instructions on what exactly needs to be done to make a fresh nginx installation work with a websocket godot client and server?
I am sure many other people will benefit as there doesn't seem to exist any information specifically on that topic.
For example, I used these two tutorials: https://www.reddit.com/r/godot/comments/buphx4/tutorial_about_hosting_godot_server_via_google/
https://www.reddit.com/r/godot/comments/bux2hs/how_to_use_godots_high_level_multiplayer_api_with/?utm_source=share&utm_medium=web2x
So now my godot server works fine on port 44444 with some ip given to me by the google virtual machine (works with ws but not wss).
I am guessing you added/changed something in nginx.conf your server machine? If so could you please share it?

When will this feature be added? really blocking from hosting a game on a https website and security ofcourse.


Move isAvailible from method to module

Just moved function isAvailible from 'inside method' to avoid each time creation new function.

What kind of change does this PR introduce?
Refactoring

Did you add tests for your changes?
No

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
None

Thanks


[BUG] DS3 Convergence crash on start

I'm trying to log into a friend's server with the Convergence mod active. DS3 will start with a white screen for 3 seconds, turn black for 2 seconds, then crash. During this time the DS3 cursor is displayed  Its not happening on the vanilla copy.
The confusing thing is, that several other friends are able to connect with Convergence just fine. DS3 starts just fine when launched normally.
Which log files should I send?
Any help in this matter will be greatly appreciated especially since the fromsoft servers are down.

Does Convergence modify the game's exe at all? It might be offseting the key that needs to be patched.
Otherwise I'm not sure, if you can send the server log for around the time you attempt to connect that might help.

I don't even get to the dev logos unfortunately, so I don't think the server log will help. Game launches normally without using the server loader though. I don't beleive the mod edits the .exe based on the uninstallation instructions.
https://i.imgur.com/wXsJtkm.png: taken from https://www.nexusmods.com/darksouls3/mods/672
I do have a vanilla copy of the game as well, and that loads and connects just fine.

Do you use blue sentinel by any chance? If you do, can you try booting the game via ds3os with and without it, just want to double check its not causing issues, as I've seen some bugs in their nexusmods bugs for similar behaviour.

I did uninstall blue sentinel while trying to troubleshoot this myself. I even went so far as to reinstall the game and moding it from fresh.

Thanks for the info.

my friend had the same issue, but when he tries to start the game via steam, it works fine, but when he started it trought the newest loader it crashes, with loader version 12 it works again

I can confirm with the current version of the launcher (version 12) Convergence works fine.

what was the solution to this? a friend of mine is having this exact issue. me and another friend have been playing fine for a few days and when we try to get our 3rd friend in now he starts having this issue. fire wall is disabled, antivirus doesn't pick it up, he's tried fresh installations for both the game and the mod and it still wont startup. it launches fine through steam but not through the server loader. i'm at a complete loss and i cant even get a solution from their discord.


Added 2 new buttons and fixed previous two buttons one by adjusting the size and one by adding a new button

Created 2 buttons and fix the errors that I have mentioned @Spyware007
This closed #733
This closed #730
(doing a single PR for both issue)
Screenshots:-

Thank You

@Spyware007 Have you checked my changes ?

Hi, there seems to be a merge conflict, please resolve it

@PoorviShetty Ok
The error was from my side
Fixed
Now please check
Thank You @Spyware007

@Spyware007 @PoorviShetty Everyone is adding their data in the Data.js file and it's showing merge conflicts
Can you please merge it
Otherwise I have to merge conflicts everyday!!


fix(log): replace bunyan with winston to ensure browser compatibility

Bunyan tries to work in the browser, but it has issues with extensions so reverting back to an updated winston that uses the console export by default

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Feature-8026][Document] Add example and notice about task type DataX

close: https://github.com/apache/dolphinscheduler/issues/8026

PTAL @zhongjiajie @Tianqi-Dotes


invoking popper from another python program

it looks like this line in Settings will never get hit, because it's within the if kbpath == False: condition. for this reason, it doesn't seem currently possible to run Popper from another Python program (as in the README). would it be okay to move the line to outside the condition?

another related question about invoking from python: if I call learn_solution multiple times within the same run, is it possible that there will be interference between the calls, or should they be completely independent? I'm seeing some warnings suggesting that there might be interference

Just pushed a fix for the first issue.
It should work as follows:
from popper.util import Settings, print_prog_score
from popper.loop import learn_solution

kbpath='examples/trains4/'
exfile=kbpath+'exs.pl'
bkfile=kbpath+'bk.pl'
biasfile=kbpath+'bias.pl'
settings = Settings(cmd_line=False, ex_file=exfile, bk_file=bkfile, bias_file=biasfile)

prog, score, stats = learn_solution(settings)
if prog != None:
    print_prog_score(prog, score)

For the second question, there is a problem with Prolog/pyswip that prohibits us doing what you want to do.
The workaround is to spawn a new process for each call to Popper like so:
import multiprocessing
from multiprocessing import Process
from popper.util import Settings, print_prog_score
from popper.loop import learn_solution

def do_it__(settings, values):
    prog, score, stats = learn_solution(settings)
    values['prog'] = prog
    values['score'] = score

def do_it(settings):
    manager = multiprocessing.Manager()
    return_dict = manager.dict()
    p = Process(target=do_it__, args=(settings, return_dict))
    p.start()
    p.join()
    print_prog_score(return_dict['prog'], return_dict['score'])

def main():
    kbpath='examples/trains1/'
    exfile=kbpath+'exs.pl'
    bkfile=kbpath+'bk.pl'
    biasfile=kbpath+'bias.pl'

    settings = Settings(cmd_line=False, ex_file=exfile, bk_file=bkfile, bias_file=biasfile)
    do_it(settings)

    kbpath='examples/iggp-minimal-decay/'
    exfile=kbpath+'exs.pl'
    bkfile=kbpath+'bk.pl'
    biasfile=kbpath+'bias.pl'

    settings = Settings(cmd_line=False, ex_file=exfile, bk_file=bkfile, bias_file=biasfile)
    do_it(settings)

if __name__ == "__main__":
    main()

It is not elegant but works

that works, thanks!


Crash when changing resolution

Describe the bug
Fabulously Optimized just crashes when changing resolution from Video Settings > Fullscreen Resolution.
(I just used pure Fabulously Optimized modpack with no mods added.)
Java vendor : GraalVM
Java version : 17
Crash Log :
hs_err_pid9980.log
Fabric Log :
latest.log
Modpack version
5.8.1
Launcher
MultiMC (auto-update)
Confirm

[x] This bug report is about an issue with the modpack itself, I have not modified the mods nor added any resource packs. If this is not the case, I know that I should post the issue to modpack's Discord support channel instead.

Additional context
No response

Please try Adoptium or Oracle Java.

Closed due to lack of response. Others can confirm it works well with suggested JVMs (my previous comment).


Query: What is supposed to happen with multiple  tags in a document ?

Query
I just accidently came across this. But if you have multiple <materialx></materialx> blocks what is supposed to occur ?
Currently it will just read the first block and discards subsequent blocks without any error / warning.
A trivial thing, (and assume it's just how the parser works?) but users may become confused if some content does not read in.

This is a good question, @kwokcb, and my initial thought is that documents with multiple materialx elements should be considered invalid, and should generate a warning in Document::validate.  That would allow the current parser behavior to remain unchanged, but would provide guidance for exporters that unintentionally create this category of invalid documents.


Value of numeric field acting weird after masking fields already masked

Hello!
first of all, thank you for the great lib!
I've been implementing the lib on my project and making default masks based on classes and got a weird behavior after calling the inputmask twice.
I'm doing this because I apply all the masks again after an ajax call to apply the mask to new fields
Is there a way to avoid this behavior or not apply the mask to fields already masked?
here's the fiddle: https://jsfiddle.net/xslok/cbcw0c1y/
Thanks!

I forgot to mention, this also happen to date fields, if there is no value when the mask is applied
https://jsfiddle.net/xslok/7hnqoz08/

@xSlok ,
This is fixed in version 5.x
See https://jsfiddle.net/jkntvh5y/
(embarrassing late response, ... sorry)


"Artifact does not exist. v5.0.4/win-x64" when packaging with .NET 5.0.4

It seems like there are no patches for .NET 5.0.4 currently available.

uploaded

It still seems like it doesn't exist, I'm getting the same error. Do I need to update NetCoreBeauty?

no, it will fetch the lastest artifacts automatically. can you show me the logs?

Oh, it also seems to error on linux and mac.
patching hostfxr...
using compatible rid linux-x64 for linux-x64
Artifact does not exist. v5.0.4/linux-x64
patch failed

What are the effects of this step failing anyway? The final build still seems to work correctly.

NetCoreBeauty does not have 5.x-linux 5.x-osx artifacts yet.

if the app successfully running outside the APP_BASE(root of the app), then it should be OK. i successfully running one of my app with unpatched runtime 5.0.3 under windows, and it works fine,  even though i haven't heard any of the related issues have been fixed. you can have a try.


Add specification to rule out windows compatibility

I couldn't find a way to change the install message to warn against Windows.  Suggested change to the description may get us closer.

Closing in favor of printing an error message if a Windows client is supported.

cool


adding completion service to Kernel is working for Azure OpenAI but not for OpenAI

It looks like something went wrong while building the config/add_completion_service.py file. The completion service gets added to the Kernel when defining the LLM_SERVICE as AzureOpenAI, but not when using OpenAI.

The wrong environment variable was used, it was still referencing the AzureOpenAI ID, while choosing the OpenAI LLM service.
The way how the chat service or completion service was creation didn't work as it was creating a new kernel instead of extending the existing kernel.

Hopes this helps ;) For me at least it now works with both LLM services. Thanks for the great tutorials!
Cedric

Closing this PR since another PR also fixed this issue; thanks for raising!


Change to enable active sync and acl by default

@gpang PTAL

This addresses #9117

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3884/
Test FAILed.


FFAR rack mass

Several missile racks are not the masses they say they should be. The 40mm and 70mm FFAR racks weigh 200kg and 400kg respectively when spawned, when the description says 6 and 12kg.
The description for the stinger also says it is 101kg, which is incorrect.

Where did you get the 6kg and 12kg from? Are those the masses of the FFAR pods when spawned as props? Also, were the racks loaded at all?
I believe these values are part of a balancing measure we were doing, similar to how some ACF guns have masses far beyond realism. I'll take a look at our rack definitions and see if anything needs changing.

there is small issue with props aswell - acf ents cant weight less than props
most of racks has been fixed in this case

The 6 and 12kg are in the description of the racks. Unloaded they were 200 or 400kg.

I see the issue at hand now: the displayed weight is that of the missile, not of the rack it will be loaded into. I don't remember the reason behind this, but it does seem like a good idea to have it display the rack's weight instead.

Oh snap, thanks for the report.  Will check it when I get the chance.

In the meantime, I lowered the mass on the 70mm and 40mm FFAR pods to a significantly lower amount, which I think is fair considering they missiles are unguided.

Sure, gotta always keep in mind though that these pods are effectively high
caliber HMGs with incredible HEAT performance and small mags, but the
recent rack buff has also given them really nice reload times too.  Got to
balance them with guns as well as other missiles!
On 29 May 2015 06:42, "Cre8or"<EMAIL_ADDRESS>wrote:

In the meantime, I lowered the mass on the 70mm and 40mm FFAR pods to a
significantly lower amount, which I think is fair considering they missiles
are unguided.
—
Reply to this email directly or view it on GitHub
https://github.com/Bubbus/ACF-Missiles/issues/54#issuecomment-106696795.


Adapt ReadMe according to template

ICCS ReadMe structure template:
Readme and Essential Repo Information
The Readme is a vital document as it is the first impression that users and potential developers get of a piece of code. There are lots of resources online that describe templates for GitHub repos. The following is a suggested structure. Note that while it is advised that the Readme covers each of these items it is possible to link out to other places in the software documentation.

Overview of Software: This should be a statement of intent and answer the question "What is this software's purpose?" i.e. What does the software do.
Project Status: Status of the software with respect to its development and release. I.e. Is the software in active development. Is the software released or pre-released. Are aspects of the software experimental.
Requirements and Environment: List the requirements or dependencies of the software and detail the process of how to obtain/install them. If using containerisation then this should be described here. If the software is available from a package index or channel then include the details but also include details on how to install from source for development.
Installation
Usage/Quick start guide: Getting started with the software.
Documentation and Support: Are there any of the following for the software;

User Guide: More extensive documentation on using the software and its features
Help or Discussion: How does a user seek help for the software. E.g. Should they raise an issue (tagged with a specific label), is there a GitHub discussions feature or an external system such as Slack.
Website: Is there a promotional website for the software (i.e. not a documentation site).

Building: Including build options. For example if using CMake this might include a tabular description of Configure or target options.
Contributing: Clear guidelines should be described on what the process is for contributing (see Contribution Guidelines section). This may include a code of conduct which describes expectations of behaviour.
Authors and Acknowledgement: GitHub does a reasonable job of logging contributions (by line or commits) but acknowledgement section is a good place to highlight core contributors or funders. Ideally Any repository with contributions from ICCS should have an acknowledgement with a link back to our site. If the software has a paper or DOI that should be used for citations then it should be listed here. Ideally a CITATION.cff file should be used to provide citation metadata. A cff file will also play nicely with Zenodo for release DOIs.
Licence: The code should have a licenced attached. There are many discussions about the best licence but assuming your code is to be open source, not copy-left and have permissible terms, MIT is a good choice. Note: Always confirm in writing from the PI or original author that they are happy with a licence before attaching it to code!
Known Issues: Version specific issues should be noted in the release notes for specific versions. More general known issues and limitations can be included in the readme, possibly with links to issues where they are discussed. If there is external documentation then it can be appropriate to linked to this instead.

There are other items that may be included in a readme such as development and release plans but these are not essential.

I think that, in the current version, a large proportion of this is already covered by the readme, the contributing.md, etc

Duplicate of #94


Defer Creation of XmlMapper to Allow for Exclusion of Dataformat XML

Description
Refactors JacksonAdapter/ObjectMapperFactory so that all code referencing Jackson Dataformat XML is in a standalone file allowing for projects using azure-core, or other Azure SDKs built on top of azure-core, to exclude com.fasterxml.jackson.dataformat:jackson-dataformat-xml from the dependency list. NOTE, if the project ends up using XML serialization in JacksonAdapter and Jackson Dataformat XML is excluded that application will crash with ClassNotFoundExceptions and MethodNotFoundExceptions, this change is purely to support scenarios where an application is known to never require XML serialization.
Example POM using this change:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.example</groupId>
  <artifactId>ExcludeDataformatXml</artifactId>
  <version>1.0-SNAPSHOT</version>

  <properties>
    <maven.compiler.source>11</maven.compiler.source>
    <maven.compiler.target>11</maven.compiler.target>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

  <dependencies>
    <dependency>
      <groupId>com.azure</groupId>
      <artifactId>azure-core</artifactId>
      <version>1.31.0-beta.1</version>
      <exclusions>
        <exclusion>
          <groupId>com.fasterxml.jackson.dataformat</groupId>
          <artifactId>jackson-dataformat-xml</artifactId>
        </exclusion>
      </exclusions>
    </dependency>

    <dependency>
      <groupId>com.azure</groupId>
      <artifactId>azure-search-documents</artifactId>
      <version>11.5.0-beta.13</version>
      <exclusions>
        <exclusion>
          <groupId>com.fasterxml.jackson.dataformat</groupId>
          <artifactId>jackson-dataformat-xml</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
  </dependencies>

</project>

In this XML the application is using Azure Cognitive Search which is a JSON-based service and doesn't require the use of Jackson Dataformat XML. The next example is a case where the application would crash due to XML serialization being required:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.example</groupId>
  <artifactId>ExcludeDataformatXml</artifactId>
  <version>1.0-SNAPSHOT</version>

  <properties>
    <maven.compiler.source>11</maven.compiler.source>
    <maven.compiler.target>11</maven.compiler.target>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

  <dependencies>
    <dependency>
      <groupId>com.azure</groupId>
      <artifactId>azure-core</artifactId>
      <version>1.31.0-beta.1</version>
      <exclusions>
        <exclusion>
          <groupId>com.fasterxml.jackson.dataformat</groupId>
          <artifactId>jackson-dataformat-xml</artifactId>
        </exclusion>
      </exclusions>
    </dependency>

    <dependency>
      <groupId>com.azure</groupId>
      <artifactId>azure-storage-blob</artifactId>
      <version>12.19.0</version>
      <exclusions>
        <exclusion>
          <groupId>com.fasterxml.jackson.dataformat</groupId>
          <artifactId>jackson-dataformat-xml</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
  </dependencies>

</project>

Azure Storage Blob is an XML-based service and when the first attempt to make a call to the service is made the application will crash as XML serialization won't be available.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run java - storage

/azp run java - servicebus

/azp run java - storage

/azp run java - servicebus

/azp run java - core

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-core


Voting start date and voting termination date

To generate the ISO DIS/FDIS cover pages we need to have the voting start and voting end date in the XML.
This issue is to add these attributes.
Originally posted by @ronaldtse in https://github.com/metanorma/mn-native-pdf/issues/97#issuecomment-611341376

Related to https://github.com/metanorma/metanorma-standoc/issues/247


devmapper: Little code cleanup and code reorganization

There are 3 patches which do following.

Move delete transaction operation into a separate function.
Save deviceset metadata file little early in shutdown sequence.
Move issue discard operation into a separate function.

CC @LK4D4 @calavera @vbatts

@rhvgoyal You have misspell in third commit.

@LK4D4 I noticed a wrong spelling in debug message and another one in commit message. Fixed it.

can you squash the commits please

@jfrazelle I have squashed all the 3 patches into one. PTAL.

@thaJeztah Fixed the issues your raised and pushed new version of patch. PTAL.

Thanks @rhvgoyal! comments LGTM (not a code reviewer, so I'll leave that to the other maintainers)

Pushed patch one more time fixing 's/befor/before'

@LK4D4 @jfrazelle PTAL

LGTM

LGTM


added Standards Platform Events

Hi Philippe,
I added the possibility of subscribing to the new standard platform events, like BatchApexErrorEvent, FlowExecutionErrorEvent,...
Regards.

Hi Daniel, that's a great idea and I'd like to include it.
However, your implementation needs a fixes and an improvement.
With your SOQL query update I'm seeing monitoring event like login/logout in the list of Platform events:

That brings two issues:

some of these are duplicates of the monitoring events category.
these monitoring events can't be subscribed to with the default platform event channel prefix. For instance, if I select Platform Event > Login Event, that sets the streaming channel to /event/LoginEvent which is invalid. The right channel (/event/LoginEventStream) is the one you get when selecting Monitoring events > Login Event Stream.

Can you update your PR:

rename the existing 'Platform event' category into 'Custom Platform event'.
list standard platform events in a new 'Standard Platform event' category.

Let's keep Monitoring events in their own category for now because they require manual activation in Setup.

Hi Phillipe,
I created the new Event category and fixed the bug about subcriptions to some standard plantform event.
Thx a lot for your review and QA

Thanks again for the contrib @Torsen. I made a few final changes and merged your PR:

ran Prettier
prevented standard platform event publication (only the Platform may do that)
improved inline help text for actions


resx related sample code not working

the sample source code here is not working. ResXResourceWriter  ResXResourceReader comes from System.Windows.Forms ??!!
we have to use resource file somewhere else than desktop application

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

ID: 28432106-fc6a-c726-23b5-f08d7038f538
Version Independent ID: b6f9d6e3-dcfd-d9b0-7768-01d46696f92f
Content: Working with .resx Files Programmatically
Content Source: docs/core/extensions/work-with-resx-files-programmatically.md
Product: dotnet-fundamentals
GitHub Login: @tdykstra
Microsoft Alias: dotnetcontent

@buyaa-n @joperezr @steveharter who can help with this?

I believe @tarekgh could help

@buyaa-n this doc is relevant to .NET Framework and not .NET Core in general. I think it is fair to mark this doc as so. There is other doc here talking how to create and reads the resource which I believe it'll work for .NET Core.
By the way, I am off so I may not be responsive.


I2c/fix funcs helper

Moving these to a separate pull request

@lauralt @jiangliu can any of you review/approve/merge this ? Thanks.


exec_record_done not working

env
nginx: 1.7.6,    nginx-rtmp-module: master

config
application record {
            live on;
            record all;
            record_path /data/video/recordStreams;
            record_unique on;
            record_interval 30s;
            exec_record_done ffmpeg -i $path -c copy $dirname/$basename.mp4;
        }

debug log
2014/11/29 23:01:43 [info] 56972#0: *2 exec: starting unmanaged child 'ffmpeg', client: <IP_ADDRESS>, server: <IP_ADDRESS>:1935
2014/11/29 23:01:43 [debug] 56972#0: *2 exec: child 'ffmpeg' started pid=56987
...
2014/11/29 23:01:43 [debug] 56972#0: kevent timer: 59714, changes: 0
2014/11/29 23:01:43 [notice] 56972#0: signal 20 (SIGCHLD) received
2014/11/29 23:01:43 [notice] 56972#0: unknown process 56987 exited with code 1
2014/11/29 23:01:43 [debug] 56972#0: shmtx forced unlock
2014/11/29 23:01:43 [debug] 56972#0: kevent events: -1
2014/11/29 23:01:43 [info] 56972#0: kevent() failed (4: Interrupted system call)

Although I don't yet have a debug log, but I am facing similar issue where exec_record_done doesn't invoke the given command
Any updates?

@jordzhang I'm also experiencing this – exec_record_done works if I call ffmpeg, but not a .sh script that works manually.

Facing this issue again, any solution?

@jordzhang @Sheikh-Aman I'm also experiencing this – exec_record_done works if I call ffmpeg, but not a .sh script that works manually... Any solution?

same here

Found the solution : don't create your scripts on windows but on the terminal !

Found the solution : don't create your scripts on windows but on the terminal !

what does this mean?


[WIP] Use halo regions to enforce Value and Gradient boundary conditions

This PR modifies fill_halo_regions! and calculate_boundary_source_terms! so that halo regions are used to enforced Value and Gradient boundary conditions. This is done by linearly extrapolating the interior field across the boundary into the halo region, using

the specified gradient (for Gradient boundary conditions)
the gradient between the interior node of a field and the associated boundary where the boundary condition is prescribed (for Value boundary conditions)

calculate_boundary_source_terms! is still a part of the algorithm and is used to enforce Flux boundary conditions. This function may also prove useful in the future for more sophisticated boundary conditions and for enforcing boundary conditions associated with irregular boundaries.
This algorithm permits the gradients of fields to be computed accurately on the boundary both in time stepping and post processing (which is useful, for example, for computing nonlinear diffusivities on the boundary when Value or Gradient boundary conditions are prescribed), and the code is more mathematically correct as a result. It also means that diffusivities are never involved in enforcing boundary conditions, which is an important simplification.
Previously, the diffusivity of a field (or some proxy for diffusivity) on the boundary was used to add the flux associated with a Value or Gradient boundary condition.
This PR also adds special boundary conditions for tendency terms (sometimes called 'source terms' in the code), and for the pressure field.
Finally, we introduce the boundary condition BoundaryCondition{Flux, Nothing} as a synonym for a no-flux boundary condition that does not require the calculation of boundary source terms, to save a few accesses to global memory.
Right now there is a bit left to do:

[x] adapt the checkpointer for the new timestepper structure (checkpointer tests currently fail)
[ ] decide whether pressure boundary conditions should be precomputed and stored in poisson_solver (currently they are computed at the beginning of a time-stepping cycle inside time_step!).

If we add pressure boundary conditions to poisson_solver, we can also get rid of the special PoissonBCs types, since the pressure fields now have explicit bcs associated with them. But this is not urgent.

decide whether pressure boundary conditions should be precomputed and stored in poisson_solver (currently they are computed at the beginning of a time-stepping cycle inside time_step!).
If we add pressure boundary conditions to poisson_solver, we can also get rid of the special PoissonBCs types, since the pressure fields now have explicit bcs associated with them. But this is not urgent.

I agree that the PoissonSolver struct is a better place to store the pressure boundary conditions, but what do you think of just storing them in model.boundary_conditions? We could do the same for the tendency boundary conditions. It would provide a simple and central store of all field boundary conditions.
If we go with indexing model.boundary_conditions by name rather than number/range then we won't have to worry about the order we put them in (which might become cumbersome for many fields) and it'll make the time-stepping code clearer.
But we should probably leave this for a future PR focused on cleanup.

To me a no-flux boundary condition sounds the same as a no-penetration boundary condition. I agree they mean different things in the code but semantically it feels confusing to have both. Not sure if there's a solution to this other than documentation.

I'm not sure about how they sound. Mathematically, a no flux condition should literally mean that there is no flux of a given quantity. In the Navier-Stokes equations that we use there are two terms that contribute to the flux of a quantity: an advective flux, and a diffusive flux, eg the flux of a quantity c through a surface with normal n̂ is:
J = n̂ ⋅ ( u c - κ ∇c )

Our definition of the Flux boundary conditions implicitly assumes that there is no flow through the surface on which the boundary condition is defined, in other words n̂ ⋅ u = 0. This is true for the time being because we don't have 'open' or non-zero 'penetration' boundary conditions.
On the other hand, a penetration boundary condition is a condition on mass specifically --- a condition on n̂ ⋅ u. More specifically because we only have NoPenetration, it is the statement that n̂ ⋅ u = 0 on that boundary. Currently we only have horizontal boundaries in the vertical direction, so this boundary condition can only be applied to w. Consider that we can apply a no penetration condition to the velocity field on all boundaries, but still permit a (diffusive) flux of velocity / momentum at the boundaries --- this will be the case, for example, for the free decay of turbulence to a quiescent state in a closed, impermeable box.
Earlier there was also confusion about the difference between a Value (Dirichlet) condition and a no penetration condition. Mathematically speaking I do think these are the same. However, their implementation on the staggered grid differs, since we assume that Value conditions are applied to fields that are not defined on the boundary, but in between the boundary face and the boundary-adjacent face. On the other hand, we assume that a penetration boundary condition applies to fields that have values on boundaries; e.g. to the velocity components that are normal to that boundary.
Does that make sense? Documentation is of course easy, but I'm open to changing the API or refactoring the code internally as well. I think that in part an internal refactoring will require dispatching on field type / location at some level; for example we have to interpret a Value condition applied to a field that is defined on a certain boundary in the same way that we interpret a Penetration condition currently, while interpreting a Value condition applied to a field defined between the boundary and boundary-adjacent face in the same way that we do now.

I agree that the PoissonSolver struct is a better place to store the pressure boundary conditions, but what do you think of just storing them in model.boundary_conditions?

I don't like this idea, because I would like the tuple of boundary conditions to have the same length as the number of solution variables to permit automation / code reduction / arbitrary tracer stuff in the future.
While not crucial, I think it makes sense (though of course we don't currently have a solution tuple, though that would be easy to add).

Thanks for the explanation! It makes a lot more sense with the staggered grid. We should probably copy paste your comment into the documentation page on boundary conditions (when we build it).

Edit: we could achieve both aims by adding a level of hierarchy to boundary_conditions, so that it has fields solution, tendencies, pressure, (each of them a tuple), or something.

Hmmm, yeah while the tendency and pressure BCs probably won't be part of the public API, might be nice to have them all in one place.
Sounds like something we can revisit when we get around implementing support for arbitrary tracers (#25) as we could probably clean up some of the abstractions in the process (e.g. merge velocities and tracers).

Got the checkpointer to work by defining a saveproperty! on AdamsBashforthTimestepper. Tests passed on my laptop, so I'm hoping CI pipelines will also pass.

Approving this PR on @christophernhill's part.

@glwagner Should we merge this?

I am going to take a look this morning
Chris
On Fri, Sep 6, 2019 at 07:16 Ali Ramadhan<EMAIL_ADDRESS>wrote:

@glwagner https://github.com/glwagner Should we merge this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/climate-machine/Oceananigans.jl/pull/389?email_source=notifications&email_token=AA27DYF6O6X2NMSGFGFPZ3DQII3W7A5CNFSM4ISPX6O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6CREXA#issuecomment-528814684,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA27DYGPWIIHTVITBWP4FB3QII3W7ANCNFSM4ISPX6OQ
.

oops - pasted this in the wrong place earlier!
@glwagner and @ali-ramadhan I took a quick look.
I think you should go ahead and merge, but quick comments for future reference -
there are a bunch of changes unrelated to the PR in the PR. They are probably there by accident, but the Git gods really don't like that. When done well a PR can be a very helpful record for show what needs to be changed to achieve "X". When the PR is polluted with random other stuff that valuable use is lost. Most git projects more diligent about avoiding polluted PRs, which can be useful.
I think ultimately we want halos to just be a thing that does a slightly more general form of what is in ::PBC mode. Everything else is not in halo rules. This is where we ended up in MITgcm and is similar to what is in MPIStateArray in the DG work (I am fairly sure!). A distinction to maybe think about is a set of halo() functions that just do the stuff that does not appear in any of the equations. Anything in equations turns out to be stuff that people may want to tinker with in surprisingly interesting ways. For example someone ultimately might want to do a numerical experiment that has flux BC on some set of the one bit of a boundary, something else on another bit etc.... (people do do things like this). For better or worse having bc's better separated from halos may ultimately prove the right thing. For now I wouldn't worry about it though!
Related to 2. I suspect that trying to express complicated things like hybrid bc's will eventually break reducing bc to a type. Types are good for simple things, but Type::ItsComplicated is often also needed eventually.
summary - +1 for merge,
per https://github.com/google/eng-practices/blob/master/review/reviewer/standard.md "its a step forward, its not a step backward, its maybe not the ultimate answer"

Thanks @christophernhill ! That google link is a good read. Thanks for sending that.

When done well a PR can be a very helpful record for show what needs to be changed to achieve "X". When the PR is polluted with random other stuff that valuable use is lost.

Fair criticism. We got a little lazy.

Related to 2. I suspect that trying to express complicated things like hybrid bc's will eventually break reducing bc to a type.

Well --- I know this is just an example --- but I should point out that such a boundary condition actually can be specified in the code today (in two different ways). This functionality is provided by the fact that we allow a boundary condition to be specified by a user-defined function, which provide fairly wide flexibility in boundary conditions. (If hybrid BCs were popular, we could make it easier to users by designing a wrapper / API for this boundary condition --- but its important that its currently possible for a user to implement this bc if they need to.) So a hybrid BC can be specified by computing the flux associated with the given boundary condition and then using a boundary condition of the type BoundaryCondition{Flux, Function}. If the boundary condition involves only Gradient/Value conditions, then a second way to specify the hybrid bc is via a boundary condition of type BoundaryCondition{Gradient, Function}, where the gradient function computes the correct gradient across the boundary for each cell. The second choice would be preferred if knowledge of the gradients of fields across the boundary is needed (which is the case, for example, for computing LES diffusivities).
A crucial aspect of this PR is that is preserves the calculate_boundary_source_terms! in the algorithm --- this means that arbitrary boundary conditions that cannot be fulfilled by filling halos can still be implemented (and indeed, a Flux boundary condition with LES closure falls into this category). This design choice preserves code extensibility.

@ali-ramadhan feel free to merge if all is well.


Poll Command

Proposal:
Proposal written by Milchreis#8855
What is the title of your proposal?: Poll Command
Is it a suggestion for the website or for the bot?: Bot
Explain your proposal more accurately (It's best to give as much information as possible, so that we can implement the proposal better): If you want to do a Poll, you make the Command ?Poll create Question,answer1,answer2,answer3,answer4. You can vote with typing the number of your Favorite. With the Command ?pollend you can Finish the Poll.
Why we should add this feature?: Polls are Always good.
ReportID: 26

➤ LenoxBot commented:
Approve:
I agree with Dadi
Denarioyt#3352

➤ LenoxBot commented:
Approve:
good idea, but I think a ?pollstats command, that shows you the current result would be also nice
Dadi#7808

➤ LenoxBot commented:
Approve:
Very good idea, but I think there should be a feature where you say if there are for example 4 votes for A, that the vote ends.
JUV#4292

Questions:

How long should the duration of a poll be max.?
How many polls for non premium users?
Where to send the results? Private dm to the creator of the poll or in the channel where the poll has been posted in?

Polls should have:

Individual ids to stop the poll whenever they want

?poll <start/list/stop>


终端不能定位当前项目目录

Issue Type: Bug
近期更新后，打开项目，很长时间自带的控制台终端都定位不到当前项目目录下
VS Code version: Code 1.63.2 (Universal) (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:37:28.172Z)
OS version: Darwin x64 21.2.0
Restricted Mode: No

Translate for the question:
Issue Type: Bug
After a recent update, when I opened a project, the self-contained console can't locate the current directory for a long time.
VS Code version: Code 1.63.2 (Universal) (899d46d, 2021-12-15T09:37:28.172Z)
OS version: Darwin x64 21.2.0
Restricted Mode: No


Feature/token

Simple correction of EIGHT to EIGHTH in 3 Tokens

As this comes from the Python code @saniemi  should review this PR also.

Why is this "EIGHT"?
Reference: https://github.com/ONSdigital/address-index-data/blob/develop/DataScience/ProbabilisticParser/common/tokens.py#L68

This branch doesn't look quite right; I will fix; please don't merge.

Because I cannot spell.. this needs to be fixed in Python as well. I can make a hotfix, retrain a new model, and re-generate the validation results. I doubt that anything changes, but I think we should fix it  nonetheless, as it may change future behaviour. Happy to discuss.


Feature request: New "Query" command that handles entire window of text

I changed my mind re: #89. Here is a way qStudio can solve that problem. (TL;DR: Cmd-E / Ctl-E sends the selected text. If the selection is a partial PRQL query, the error message that returns is particularly abstruse.)
Proposal: Add a new menu command named simply "Query" that processes the entire window of text. Attach a reasonable keyboard shortcut.
Reasoning:

Making a query of the entire window's text is a frequent operation. It deserves its own command
I was always curious why qStudio only offered "Query selected text", but was also relieved that the default was the entire text if there wasn't a selection
Having a good keyboard shortcut is important: people will train their fingers to use it and never think about it again
Keyboard shortcut might be Cmd-Shift-E (Ctl-Shift-E) or any other reasonable alternative. I was hoping for Cmd/Ctl-R, (mnemonic for "run") but that's already taken. I definitely do not want to disturb other people's "trained fingers" - I'm the newcomer, I can learn Cmd-Shift-E...

Update: I recorded a movie of me screwing up. https://youtu.be/AquxzK8l4f4
Here's what happened:

The take 100 line was not commented: Cmd-E worked as expected.
I then commented that line out (Cmd-/) and wanted to re-run the query (with Cmd-E), but I got the PRQL error.
I then clicked to remove the selection, and Cmd-E worked as expected.

My request: to create a keyboard shortcut that sends the entire pane of text, regardless of what's selected.


model testing

Models can be easily tested to improve coverage based on simplecov coverage report

I will be working on this, and will list the file I am working on here:
Starting with bio.rb


Shared Memory Example not working

Hello,
Current I have install fedora 36 install on my desktop,I have read the documentation regarding villas node, i am trying for shared memory example but seem its not working for me. i have follow the same.when i run villas-shmem client there no data present. for more details i have added the screen shot.
Example
https://villas.fein-aachen.org/docs/node/nodes/shmem

The invocation of villas-Sheen is missing mandatory arguments as the usage message indicates. You will need to pass the name of the shared memory segments.
Can you please also provide the config file used by villas-node?

Hello,
I have added the share memory name as the argument but its saying segmentation fault. For reference i have added the screenshot.
configuration file: https://github.com/VILLASframework/node/blob/master/etc/examples/nodes/shmem.conf
Example that i have run is https://github.com/VILLASframework/node/blob/master/clients/shmem/villas-shmem.cpp

The example shmem.conf config file is made in such a way that it tests a loopback connection. Hence, the settings nodes.shmem_node.{in,out}.name are the same (sn1_in) in both directions.
If you want to test the shared memory connection between a VILLASnode instance (villas-ndoe) and the test program villas-shmem, you will need to use different names for each direction and also pass those different names as command line arguments to villas-shmem.
Please also note, that the shared memory node-type has note been used that much in the past.
Are you sure that you really need it? Maybe socket-based communication e.g. mqtt or plain UDP socket are better suited for your use case.

actually i want to import/export data to DPSIM for that reason i am using the share memory. so could you guide me how i can import/export data from DPSIM

Ah I see. The interface between VILLASnode and DPsim is no longer using the shared memory interface. This is obsolete. VILLASnode is now embedded into DPsim directly. I suggest you have a look at the DPsim examples. Especially those using the VillasInterface.

Closed due to lack of feedback.


Completely switch to python3

pam-python 1.0.8 can be build using python3. At this moment, howdy has a workaround applied do support python2 for pam-python (like here). Now we can switch to pam_python 1.0.8 and completely drop Python2-specific stuff.

Good idea, but we're taking it a step further and rewriting the PAM part in c++, checkout the WIP PR

I've just upgraded to Ubuntu 23.04 and it seems that this prevents howdy from running. That's what I get in the auth.log:
2023-04-21T10:38:50.406977+03:00 alex-ZenBook /lib/security/howdy/pam.py[14914]: Traceback (most recent call last):
2023-04-21T10:38:50.407061+03:00 alex-ZenBook /lib/security/howdy/pam.py[14914]:   File "/lib/security/howdy/pam.py", line 10, in <module>
2023-04-21T10:38:50.407095+03:00 alex-ZenBook /lib/security/howdy/pam.py[14914]:     import ConfigParser
2023-04-21T10:38:50.407130+03:00 alex-ZenBook /lib/security/howdy/pam.py[14914]: ModuleNotFoundError: No module named 'ConfigParser'


Set good defaults for mouse wheel

It would be good if mouse wheel could match current applications that uses it but should also allow user to tweak it.

Switching Qt and C++ (for now, will be reevaluated when there are some good Rust bindings for Qt) so closing.


Return response structs where applicable

There are still a few methods on the SDK where the return values from the operations are stripped down into more basic types like string or slice. That damages extensibility (without breaking) and introduces inconsistencies.
Ideally a method must map 1:1 to a REST API call and should be like
func(f FooClient)VerbBar([r requiredParams...], params VerbBarParams) (VerbBarResponse, error)

in the schema above adding things to VerbBarParams (e.g. CreateDeploymentParameters) and VerbBarResponse (e.g. ListHostedServicesResponse) can be done without breaking the caller.
requiredParams must be list of arguments that don't go into the XML request body but rather used in constructing the REST API request URL. Those must be validated. But we must not validate the  arguments in params structs if they're required or not on the client side (because REST API already does that.)
Opening this issue as a cleanup task.

:confused: REST, XML, Hm?

Ong wrong repo

:-)


[FEATURE]

Description
allow users to like others posts.
Use Case
Likes serve as immediate feedback for bloggers, indicating that their content is appreciated and resonating with the audience. This positive reinforcement can motivate bloggers to continue creating content, fostering a vibrant and active community.
Proposed Solution
I have already familiar with the blogging app backend. You can check it here. Here i have created separate controller and route for like.
I can also have abilities to create the frontend as well.
I am very much excited to contribute like stuff to this project. Please assign this issue to me under GSSOC'24
Additional Information
No response
Attachments
No response

Hi @krishnaacharyaa,  please assign this issue to me.

Violates the code of conduct