Form Select-Search and Select-No Search Icons are different colors

In Form example 2, The first Select (Select-No Search) icon is lighter grey than the second Select (Select-Search) icon. First Select (Select-No Search) also needs an on hover color change.
https://grommet.github.io/hpe/docs/form/examples#2
Your Environment

Browser Name and version: Firefox 48.0 and Chrome 53.0.2785.116

Fixed in grommet commit 223fd9e2e0937bec4d4ee160e96c93ef52e79bba.


Handle unavailable Clickhouse/Elasticsearch instances

As a developer I want to ensure that GQL queries do not fail when a backend service is not available because the application should be sufficiently resilient to handle failure until service is restored.
Background
Executing a query on the GraphQL API will result in an internal server error is ES or CH cannot be reached. We either should handle these exceptions gracefully, or provide more information in the error message provided to the API about what the problem is.
Acceptance tests
Given a running instance of the API which cannot communicate with either ES or CH, a query should return either a valid response (ideal, but perhaps misleading?), or a 5xx error with sufficient detail to identity the problem without consulting the application log. Sufficient detail means that I know which of the services is unavailable.

I also think it could be misleading but I think it would depend on how often is the data updated?

The status code is going to be a 200 because the error is occurring while executing the query. So we will need to send a response message with errors object populated. This is how it would look like for Clickhouse:
{     "data": {         "target": null     },     "errors": [         {             "message": "Error connecting to the Clickhouse db. Contact system administrator",             "path": [                 "target",                 "literatureOcurrences"             ],             "locations": [                 {                     "line": 6,                     "column": 5                 }             ]         }     ] }
and this is how it would look like for elastic search:
{     "data": {         "target": null     },     "errors": [         {             "message": "Error connecting to Elastic Search. Contact system administrator",             "path": [                 "target"             ],             "locations": [                 {                     "line": 2,                     "column": 3                 }             ]         }     ] }
what do you think? is the message ok? should I change it to something else? @JarrodBaker

That looks good to me @remo87.
Realistically we're the only people who are likely to see these messages, and the purpose is so we can quickly identify if we've got an infrastructure issue or there is a problem in the API logic.


[WIP] Bump eirini

this is WIP because kubecf requires a newer CAPI to get this working
https://github.com/SUSE/kubecf/issues/49
Once that issue is done, we can test this PR

I've bumped the eirini-ssh and eirini-persi extentions. On kubecf the kubecf-ssh-proxy-public is pointing to the kubecf-scheduler-v1-0 pod but there is no container listening on port 2222 inside that pod. It seems that the ssh-proxy is not started correctly. I'm investigating why that is. Still need to test eirini-persi.

We tried this on kubecf and everything works (at least what's on this bosh-release, we had to change a number of things on the kubecf side). Merging.


SOLVED: sudo: unable to create sockets: Socket type not supported (CentOS on WSL)

Hello,
@jdmansour pointed out in Atlas on Windows that he was also getting sudo: unable to create sockets: Socket type not supported. This was the only reference to sudo: unable to create sockets: Socket type not supported that I was able to find.
Since sudo works under Ubuntu but fails under CentOS, I thought it must be a CentOS issue rather than a WSL issue.
If you're running as root, you can use sudo -V to dump a detailed sudo configuration, along with ./configure compile time flags. After a lot of trial and error, I was able to get sudo working under CentOS via WSL Distribution Switcher.
First, download the sudo sourcecode from sudo.ws.
Then you'll need to install a boatload of dependancies to get this to build.
yum install file make zlib zlib-devel \
gcc vim svn wget make \
sssd sssd-libwbclient-devel \
pam-devel libselinux-devel

Then you'll want to configure with:
./configure  -v --with-all-insults --with-pam \
--with-nsswitch=no --without-ldap --without-sendmail \
--with-logfac=authpriv --with-logging=syslog \
--with-editor=/bin/vi --with-env-editor \
--with-timeout=15 --with-password-timeout=0 \
--with-passprompt="[sudo] password for %p:" \
--without-lecture --with-tty-tickets \
--disable-root-mailer --enable-admin-flag \
--with-sssd --with-sssd-lib=/usr/lib64 \
--with-selinux --enable-zlib \
--without-fqdn

Last, you'll want to edit /etc/sudoers.  You'll also want to make sure to include a blank line after this line, as it also seems to be required by sudo.  This should fix: sudo: no tty present and no askpass program specified errors.
I'm sure that it's not the best solution, but it's a viable way to get sudo working on CentOS under WSL. I wish I could think of a way to include this into the post_install script but it's such a long winded process, building a custom RPM would seem to be the most viable option, but then is WSL-Distribution-Switcher going to want to host packages that handle compatability for certain programs?

Hi,
Thanks for your write-up. I'll look at it over the weekend and decide how to solve it. The installer script does support running multiple hooks, including filtering by distribution. For example, one can include the sudo compiler in a separate hook_postinstall_centos_7.sh script, to only run for centos:7.
WSL does not support Unix sockets at this time, so if that is what the CentOS version of sudo is trying to do, it will not work. (It was added in the Insider builds, or is in the process of being added, if I'm not mistaken.)
As for the TTY error, you can just run sudo -S to instruct sudo to read the password from stdin, which will work.

Yep, the problem is datagram sockets, and they're fixed in the insider builds.

@ryanerwin thanks for the fix

Instead of having the title start with SOLVED you can close the issue, which works better with Github's issue system


stubs out cosmos_walletconnect_provider

Aiming to achieve the following in Flutter: cosmology/cosmos-wallet
Example in TypeScript (Keplr):
https://github.com/cosmology-tech/cosmos-wallet/blob/main/packages/keplr/src/connectors/keplr-walletconnect.ts

https://github.com/CosmWasm/CosmWasmJS#create-a-wallet-and-a-signing-stargate-client


Integer column names not working

When a Table is backed by a DataFrame with integer column names, indexing the columns fails with a confusing error message. The resulting schema appears to be invalid, since DataShape does not currently allow integer column names.
t = blaze.Table(pd.DataFrame(data=[0,1], columns=[0]))
t[0]

TypeError                                 Traceback (most recent call last)
 in ()
1 t = blaze.Table(pd.DataFrame(data=[0,1], columns=[0]))
----> 2 t[0]
/media/extra/kaggle/birds-scipy2014/blaze/expr/table.pyc in getitem(self, key)
54         if isinstance(key, TableExpr):
55             return Selection(self, key)
---> 56         raise TypeError("Did not understand input: %s[%s]" % (self, key))
57
58     def sort(self, key=None, ascending=True):
TypeError: Did not understand input: _31[0]

We can construct these now, but I don't think we can get at the individual columns:
In [24]: d = Data(pd.DataFrame([[1,2]]))

In [25]: d.fields
Out[25]: ['0', '1']

Closing old issues. Feel free to reopen with up to date info.


Update syn to v1

Fixes #2.

Yes please, ran into this as well as an dependency and the only one that brings in the old pre-1.0 syn


Added PolicySettings and DeleteModal components for PolicyDetails UI

Signed-off-by: Eric Lobdell<EMAIL_ADDRESS>Description
Adds PolicySettings and DeleteModal components used by the PolicyDetails UI. PolicySettings is the upper render box that shows basic details of the given policy, excluding States display. DeleteModal is responsible for confirming that the user wants to delete the policy.

Known Issues

interfaces.ts file includes too many changes and may need to be reduced to just relevant changes.

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Seems like you have to update snapshot
2021-08-12T01:10:41.8589340Z FAIL public/pages/PolicyDetails/components/PolicySettings/PolicySettings.test.tsx
2021-08-12T01:10:41.8591242Z   ● <PolicySettings /> spec › renders the component
2021-08-12T01:10:41.8591617Z
2021-08-12T01:10:41.8592212Z     expect(received).toMatchSnapshot()


Some inconsistencies with the calculate_heat_index_adjusted function

I have noticed some differences between the equations in the heat index function, as incorporated in this package, and the equations listed here: https://www.wpc.ncep.noaa.gov/html/heatindex_equation.shtml
adjustment2 should be:
adjustment2 = (rh[hi_filter1 and hi_filter4 and hi_filter5] - 85) /10* (
(87 - t2m[hi_filter1 and hi_filter4 and hi_filter5]) / 5
[first term should be divided by 10]
and should be added to hi, not subtracted.
adjustment1 should be:
adjustment1 = (
(13 - rh[hi_filter1 and hi_filter2 and hi_filter3])
/ 4
* np.sqrt(
17 - np.abs(t2m[hi_filter1 and hi_filter2 and hi_filter3] - 95) / 17
)
[95 instead of 0.95]
Additionally, hi_filter6 should be for hi<80 (or, in practice, the average of the simpler formulation of hi and t2m being less than 80 degree F), not for only t2m<80.
Let me know if I am missing something or if you are pulling the equations from a different source.
Regards,
TC

Hi TC,
Thanks for your report. We are looking into it.
Kind Regards,
Chloe

For reference, here is the function I have been using (takes Temp in degree C and relative humidity in % as inputs), partly based on your code:
convert Fahrenheit to Celsius
def fahrenheit_to_celsius(tf):
tc = (tf - 32) * 5 / 9
return tc
def HI_NWS(Ta, RH):
rh = np.array(RH)
t2m = np.array(Ta*9/5 + 32)

hi_init=0.5*(t2m+ 61.0+((t2m- 68.0) * 1.2)+ (rh*0.094))

hiarray = [
42.379,
2.04901523,
10.1433312,
0.22475541,
0.00683783,
0.05481717,
0.00122874,
0.00085282,
0.00000199,
]
hi = (
-hiarray[0]
+ hiarray[1] * t2m
+ hiarray[2] * rh
- hiarray[3] * t2m * rh
- hiarray[4] * t2m ** 2
- hiarray[5] * rh ** 2
+ hiarray[6] * t2m ** 2 * rh
+ hiarray[7] * t2m * rh ** 2
- hiarray[8] * t2m ** 2 * rh ** 2
)

if ((hi_init+t2m)/2<80):
    hi_final=hi_init
elif ((t2m > 80)&(t2m < 112)&(rh <= 13)):
    adjustment1 =(
    (13 - rh)/4*np.sqrt(17 - np.abs(t2m - 95) / 17))
    hi_final=hi-adjustment1
elif ((t2m > 80)&(t2m < 87)&(rh > 85)):
    adjustment2 = (rh - 85)/10 * ((87 - t2m) / 5)
    hi_final=hi+adjustment2
else:
    hi_final=hi
hi_final = fahrenheit_to_celsius(hi_final)
return hi_final

Hi TC,
Thank you, I have made the changes in the develop branch. We are currently checking our unit testing and have taken the time to make some examples and look at our documentation. We aim to have a new release to fix our unfortunate typo this week.
Best Wishes,
Chloe

@chlobrim -
Regarding the issues @TC25 raised, is the package use for the Climate extreme indices and heat stress indicators derived from CMIP6 global climate projections data release? And if so, will they be updated if errors are found in the package?
Thanks!

Hi Cascade,
The dataset you are referencing is separate to thermofeel. You can see their code for heat indices here: https://github.com/schwings-clemens/CDS_heat_stress_indicators/blob/main/calc_heat_stress_indicators.py#L171
Heat index appears correct in this repo. However, WBGT and UTCI in this dataset are the indoor versions only as radiation is not considered.
We hope to have an update to heat index adjusted soon, as I said above we have also taken this opportunity to check other aspects of our library.
Hope that helps,
Best Wishes,
Chloe

Thank you for the quick following up so quickly Chloe and for pointing me to the repo. Keep up the good work!
-Cascade

@cascadet and @TC25 we have just released version 1.2.0
That should fix this issue. Let us know if anything else remains to be addressed.

Closing


carthage build failing

xcode 9.1
*** Building scheme "BonMot-iOS" in BonMot.xcodeproj
Build Failed
Task failed with exit code 65:
anyone experience this?  any solution?

I know you emailed me some of this in private, but just for completeness and so other people can benefit, could you please provide a little more detail on how your project is set up? Precise repro steps or a sample project would be greatly appreciated if you have the time.

cartfile entry:
github "Raizlabs/BonMot"
carthage version:   0.26.2
error from terminal when trying to update:
*** Building scheme "BonMot-iOS" in BonMot.xcodeproj
Build Failed
Task failed with exit code 65:
/usr/bin/xcrun xcodebuild -project /Project\ Work/Source\ Code/...-iOS/Carthage/Checkouts/BonMot/BonMot.xcodeproj -scheme BonMot-iOS -configuration Release -derivedDataPath /Users/Nathan/Library/Caches/org.carthage.CarthageKit/DerivedData/9.1_9B55/BonMot/5.0 -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath ./ SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO (launched in /Project Work/Source Code/...-iOS/Carthage/Checkouts/BonMot)
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/gv/qkc8m_v51lv_0cm6ygj0gcp00000gn/T/carthage-xcodebuild.FWn1RU.log

i was digging thought he log file that carthage makes and saw this line:
SwiftLint failed with exit code 2. Is SwiftLint installed and up to date?
do i downloaded and re-installed (i think i did it before) swift lint
i did two tests and had no problems so far.   now i dread converting my project to swift 4.   thank goodnees for source control

Hm, interesting. We could probably make SwiftLint fail less hard in that case. It looks like Carthage defines a build setting for CARTHAGE=YES https://github.com/Carthage/Carthage/pull/1151/files. @nboyd-sportdx would you be interested in adding a pull request that does not fail SwiftLint when building via Carthage?


Support portable data alongside executable

Fixes #1882

[ ] Added an entry to CHANGELOG.md if this change could be valuable to users

The issue stated this about Windows portable build, however I consider portable mode useful for any OS. Tested on Linux

we don't provide portable builds for any other platform

Closing in favour of #1888


CI run takes very long time to finish

maybe we could speedup test if we stop the test when render api returns some data
https://github.com/pyroscope-io/pyroscope-rs/issues/73

make it so we have test matrix only for python versions,
and the rest of matrix is fork executed inside the script


Multiple keyboard layouts

Hi, how to add multiple keyboard layouts? For example I would like to add in addition to the fr azerty, the fr bepo (bépo) ?

I believe your distro has a way to change the keyboard layout when in a TTY, you might want to look into that.

I am interested in this issue. I messed up the default keyboard config (etc/default/keyboard) and could not login after next boot. I did not found a way to change the layout at TTY. I would appreciate it if you could point me toward some links.


Angular2+ AOT build giving error!

Angular2+ AOT build ng build --prod is giving error

ERROR in Error during template compile of 'AppModule'
Function calls are not supported in decorators but 'AppBreadcrumbModule' was called.

To regenerate

Download angular2+ template branch
npm i
ng build --prod

Any workaround?

Hi, we're working on this issue.
BTW This is not angular version repository, here is proper repository: https://github.com/coreui/coreui-free-angular-admin-template


[backport] test: Stabilize roll_axis test by adjusting tolerance

This PR backports test: Stabilize roll_axis test by adjusting tolerance #3375

Please rebase.

@niboshi Rebased.

Could you resolve conflict again?

jenkins test this please

jenkins, test this please

LGTM!


Position limits do not handle encoder directions correctly

If the encoder direction is clockwise, position limits signs are incorrect, resulting in incorrect limits being set.

Will be included in release V1.0.2


Share REQUIRED in setup.py and collect_info.py

🌟 Feature Description

Motivation

Application scenario
Related works (Papers, Github repos etc.):
Any other relevant and important information:

The REQUIRED packages is use in setup.py and collect_info.py. To avoid incosistency, better use the same REQUIRED dict.
Alternatives

Additional Notes

Thanks for your advice :)
I agree with you


Add hint about possibility to use babel plugin to improve reported st…

These changes are already included in #1797 .


how to abort request which is sending a big file

Imagine we have an interface for uploading to a server some files
we should create saga which is monitoring action with file in payload and send a file with the xhr request.
sending file is a simple task, but aborting any of sending request become a problem
how to abort any particular request which is sending a file to a server in saga?

How do you make your requests? Cause the answer depends on that :)

I'm talking not about canceling a fetch task but about abort real http request

As I said - it depends on how do u do your requests. What kind of API/library are u using?

@budarin if you're using XMLHttpRequest, you could use an eventChannel and abort the XHR from there if the large file upload is taking too long.
Like @Andarist said though, it really depends on how you are implementing the file upload. If you are not using Fetch or XMLHttpRequest, can you explain what you mean by a "real" HTTP request? After all, any implementation of the protocol HTTP will send a request

Its also worth mentioning that fetchs are non-cancellable

Hi !
I use to superagent as HTTP request library
So, as I've understood, I have to save the instance returned by call superagent instance and than manually call abort/cancel method on it?

from what I understand its API you can make some wrapper and use it like this
function* callAPI(url) {
	const req = request.get(url)
	req[CANCEL] = () => req.abort()
	const result = yield req
	return result
}

function* saga() {
	const requestTask = yield fork(callAPI, 'http://...')

	// ...

	yield cancel(requestTask)
}

Thanks for the sample.
But I need to cancel running request not from within the same saga - it must be another saga which look for an action { CANCEL_UPLOADING_FILE, id }
so I need to store result of the request in a store by id ?

Just pass the reference to the request task there so it could be canceled, storing in the store is preventing u from serialization of the store
You could have also use setContext/getContext effects.

How does this work with auto cancel when used with takeLatest (or how should i do it)?

if you use such solution as above the cancelation process will know how to cancel the forked (internally by takeLatest) task

This thread got a little bit stale, so I'm closing it. If you need to discuss this further, please just reply back here.


feat: Add historic blocks tree interfaces

Description
closes: https://github.com/AztecProtocol/aztec-packages/issues/1160
Adds the interfaces to handle the historic blocks roots tree, but does not add any circuit logic to check them
Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:

[ ] I have reviewed my diff in github, line by line.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[ ] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[ ] The branch has been merged or rebased against the head of its merge target.
[ ] I'm happy for the PR to be merged at the reviewer's next convenience.

@Maddiaa0 Were these submodule folders removed on purpose here? If yes, we need to remove them from .gitmodules, otherwise add them back in the dir structure

@Maddiaa0 Were these submodule folders removed on purpose here? If yes, we need to remove them from .gitmodules, otherwise add them back in the dir structure

Ah this was an accident after a merge, ill fix


Ansible 2.5 compatibility

Ansible 2.5 broke the callback.

It would be nice if this worked, we're having to remove datadog from our ansible runs since we need a feature in 2.5.

@austinmills This has been fixed with the latest version: 2.4.2. For more context about the issue: https://github.com/ansible/ansible/issues/38036 (yaml import broke with ansible 2.5).
I'm going to close this issue but feel free to reopen it if needed !


Migration tool improperly propagates non-nullability back via type-inferred variables.

Consider the following code:
class C {
  int v;
  C(this.v);
}
f(C c) {
  var x = c.v;
  print(x + 1);
}
main() {
  C(null);
}

The migration tool currently migrates this to:
class C {
  int v; // (1)
  C(this.v);
}
f(C c) {
  var x = c.v; // (2)
  print(x + 1); // (3)
}
main() {
  C(null!); // (4)
}

What's happening is that since the use of x at (3) is guaranteed to fail if x is null, and that use post-dominates the declaration of x at (2), the tool infers that the type of x should be non-nullable.  But since the type of x is inferred from the type of C.v, it propagates this non-nullability back to the declaration of C.v (at (1)).  Which in turn means that null can't be validly passed to the C constructor at (4).
What should happen instead is that the back-propagation of non-nullability should stop at (2), allowing C.v to be nullable, so the migration would be:
class C {
  int? v; // (1)
  C(this.v);
}
f(C c) {
  var x = c.v!; // (2)
  print(x + 1); // (3)
}
main() {
  C(null); // (4)
}

This issue is causing incorrect migration of package:logging.  Specifically, the following code in logging_test.dart is causing problems:
  test('cannot directly manipulate Logger.children', () {
    var loggerAB = new Logger('a.b');
    var loggerA = loggerAB.parent;                                              // (1)

    expect(loggerA.children['b'], same(loggerAB), reason: 'can read Children'); // (2)

    expect(() {
      loggerAB.children['test'] = null;
    }, throwsUnsupportedError, reason: 'Children is read-only');
  });

Seeing (1), the migration tool reasons (poorly) that since the type of loggerA is inferred from the type of Logger.parent, any conclusions we draw about the nullability of loggerA should be reflected in the nullability of Logger.parent.
Since loggerA is unconditionally dereferenced right after it is declared (at (2)), the migration engine decides that loggerA should be non-nullable, so it tries to make Logger.parent non-nullable.
I believe what should happen instead is that it should decide that loggerA should be non-nullable, and therefore the call to loggerAB.parent should be null-checked, so line (1) should be changed to var loggerA = loggerAB.parent!;
Thanks to @leafpetersen for noticing the migration tool making this mistake.


Add NestJS to package.json/dependencies

Fix pcc-backend error "nest: command not found"

to use nest cli without installing it globally use /payment-common-component $ ./node_modules/.bin/nest


Set up the CI

Motivation
There should be some automatic CI pipeline, that at least check if the pull request does not break the build of the environment.
Proposed solution
Use https://appveyor.com for that.
Additional context
If you need any assistance, ask @Simply007.

Appveyor has been setup


Addition of innovation consistency checks to all observations with user tuneable gate sizes

Fixed by https://github.com/PX4/ecl/pull/35 and https://github.com/PX4/ecl/pull/17


Pass X-Remote-User to backend

Allows authentication modules to supply a username that gets passed to proxied service via X-Remote-User header.

Fixed username -> decorate. Regarding user.email, I used the same strategy as the email check, which makes the same assumption. I don't really know enough about the OAuth services in question to tell whether this value can be empty.


Resource Not Appearing in Repo

Describe the bug
When attempting to install the ssi-dim-wallet-stub directly from the Helm chart repository, the response indicates that the chart does not exist.
To Reproduce

Add the Helm repository:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev

Attempt to install the ssi-dim-wallet-stub Helm chart:

helm install ssi-dim-wallet-stub tractusx-dev/ssi-dim-wallet-stub

The following error message appears:

Error: INSTALLATION FAILED: chart "ssi-dim-wallet-stub" matching  not found in tractusx-dev index. (try 'helm repo update'): no chart name found

Update the Helm repository:

helm repo update

Search for the expected Helm Chart:

helm search repo tractusx-dev

Expected Behavior
The Helm chart for ssi-dim-wallet-stub should be successfully found and installed without errors.
Actual Behavior
The installation fails, and Helm reports that the chart does not exist in the repository.
Screenshots/Error Messages

Context Informations

Helm version: v3.15.4

Thanks for rising this issue.
Helm chart is not pushed yet to tractusx-dev repository.


add 'apriltag_msgs' and 'apriltag_ros' to 'humble' and 'rolling'

Please Add This Package to be indexed in the rosdistro.
humble and rolling
The source is here:

https://github.com/christianrauch/apriltag_msgs
https://github.com/christianrauch/apriltag_ros

Checks

[x] All packages have a declared license in the package.xml
[ ] This repository has a LICENSE file
[x] This package is expected to build on the submitted rosdistro

See also the PR for the release repos: https://github.com/ros2-gbp/ros2-gbp-github-org/issues/109.

@quarkytale Is this still held for a distro sync? Would it make sense to split this PR in order to get one of the distros merged before the other?

Hi @christianrauch, its not held for sync anymore. Could you update the release repos to ros2-gbp ones since that PR is now merged?
But I see the release repos to be empty, is this supposed to merged first in that case?

But I see the release repos to be empty, is this supposed to merged first in that case?

That was my understanding from the release documentation:

If your repository is new to the ROS community, you should first open a pull request on ros/rosdistro adding a source entry for your repository. [...] Once your package name has been approved and merged, fill in the Add New Release Repositories issue issue template if you don’t have a release repo for your project yet.

There it says that the package name should be approved first by merging the source entry. I send both requests in parallel to speed up the process, but my understanding is that new packages should not have entries other than source populated initially. I probably then have to send another PR that is generated by bloom-release and will contain the release repo etc.
Is my understanding correct or should I generate a single PR that contains the full entry, including the source and release entries?


metadata of textlint.js

textlint.js bundle should include meta-information like Greasemonkey script.

rule
rule config
plugin

→ original .textlintrcis included
Also, greasemonkey installation experience requires the file name pattern like .textlint.js.

compiler embed texltintrc as json and metadata

editor/packages/@textlint/script-parser at master · textlint/editor


Implement getChainTip Ogmios query.

Closes #169

We have an issue with CI. I opened a PR to fix it, so we can merge this after merging in those changes


Satellite image search notebook missing

Hi there. I saw this notebook on Satellite image search a few months ago: https://github.com/pinecone-io/examples/blob/master/search/image/satellite-image-search/satellite-image-search.ipynb
It is not available anymore. Is the notebook somewhere? I tried to explore different branches, but I had no luck.
Is it possible to still have access to it?
Thank you,

Hi @estebanpdl! I think you are looking for this example: https://github.com/pinecone-io/examples/blob/master/learn/search/image/satellite-image-search/satellite-image-search.ipynb
It has been moved to the /learn directory.


musl is not always dynamically linked

See:

https://github.com/ziglang/zig/issues/5364
https://github.com/ziglang/zig/issues/11909

.NET RIDs like linux-musl-x64 (and friends) are meant for systems with a dynamic musl libc, such as Alpine. Linking musl statically is not what we want and is likely to blow up in 'fun' ways. As a result, our support for musl-based RIDs for C/C++ code is effectively unusable right now (but should work fine for Zig code).
I think this is strictly an upstream Zig bug; we pass all the right flags on our end.

I've been trying to build a dynamic Python interpreter executable with zig cc/ musl, and can confirm that it is not working - the resulting binary is always statically linked, no matter extra -dynamic flags or whatnot.
Unless I am doing something wrong, I would say this issue is a showstopper for zig cc usage with any big and complex projects requiring a dynamic executable, where setting up own build.zig flow from scratch is prohibitively tedious.

Need to try the workaround mentioned here: https://github.com/ziglang/zig/issues/11909#issuecomment-1837496974

Need to try the workaround mentioned here: ziglang/zig#11909 (comment)

This appears to work.
Also, as I noted in https://github.com/ziglang/zig/issues/11909#issuecomment-2081634630, this bug does not actually affect shared libraries.

This appears to work. We can do this as a temporary workaround.

This won't actually work after all, as it requires the dynamic linker to be present at the given path (e.g. /usr/lib/ld-musl-x86_64.so.1), which is fundamentally incompatible with cross-compilation.


hosts file?

Does this method bypass the hosts file?

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

ID: bd3de4e8-2530-2565-2873-053d4b0d9d38
Version Independent ID: 058be335-0104-8c08-5adb-a9b5aea2a077
Content: Dns.GetHostAddresses(String) Method (System.Net)
Content Source: xml/System.Net/Dns.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

I learned that it does NOT bypass the hosts file.
This is confusing because the name of the class is "DNS". I would assume this would return results strictly from DNS, like how the nslookup utility functions.

Aren't host files kind of explicit DNS configuration?
AFAIK we do not parse the files ourselves, we ask DNS APIs which return us values based on their configuration.
cc @wfurt @davidsh

DNS is network protocol. However it is often used as broader "name resolution" service.
host file processing is not part of RFC1035 but is used on all supported platforms as part of the name services including  Dns.GetHostAddresses()
On Unix for example that function will also use other providers (like NIS)

AFAIK we do not parse the files ourselves

Correct.  Our System.Net networking layer does not parse any 'hosts' file directly.  The DNS subsystem in the operating system uses the 'hosts' file.

This is confusing because the name of the class is "DNS". I would assume this would return results strictly from DNS, like how the nslookup utility functions.

Unfortunately, you are correct about what the System.Net.Dns class actually does.  It does NOT strictly use DNS protocol.  It uses higher-layer "name resolver" functions in the OS.  This means it will use non-DSN protocol mechanisms to resolves names, like NetBIOS, etc.
We have had requests for enhancements to the System.Net.Dns class such as adding the ability to return TXT or MX records for example.  But strictly speaking, despite the name 'Dns' of the .NET type, this class is not strictly a DNS class.

DNS apparently can refer to both - the protocol or subsystem. We use it in the sense of subsystem.
Unless it confuses more developers, I suggest to close the issue as answered. @samrueby are you ok with that?

The documentation explicitly wrote "The GetHostAddresses method queries a DNS server...". "DNS Server" is the reason this is confusing and seemed to make it clear it meant the protocol.
I am okay with closing this because I created a documentation pull request: https://github.com/dotnet/dotnet-api-docs/pull/653


efuse: allow overriding base mac

ESP-IDF defines several kinds of mac addresses, but this doesn't map well to the esp-hal design, because:

This isn't actually required by hardware.
Wifi / Ble drivers are external to esp-hal.

Hence this patch only allows overriding the base mac and does not introduce the concept of other types of mac addresses.
Resolves https://github.com/esp-rs/esp-hal/issues/971.
Must

[x] The code compiles without errors or warnings.
[ ] All examples work.
[x] cargo fmt was run.
[x] Your changes were added to the CHANGELOG.md in the proper section.
[x] You updated existing examples or added examples (if applicable).
[x] Added examples are checked in CI

Nice to have

[x] You add a description of your work to this PR.
[x] You added proper docs for your newly added features and code.

Hi all, I think this patch is ready for review. Just one question regarding All examples work -- I don't have the capacity to check examples on all boards, I've only verified that the feature I've added works. Am I to assume that if CI passes and I didn't knowingly introduce any breakage that this point is fulfilled?

Having CI pass is good enough IMHO if your changes are not likely to change other code paths - you might want to mention on which targets you were able to test your changes on (I assume you don't have access to all the supported chips)
Checking all the examples on all targets is definitely a lot of effort - especially since some of them require wiring external hardware to the board

Can we please avoid get_? It's generally not recommended.
I would also like to shamelessly plug my atomic_enum fork that may look a bit nicer than magic numbers.

Can we please avoid get_? It's generally not recommended.

This is to maintain the public API. The get_mac_address was already defined on Efuse. I'd like to keep this PR focused.

I would also like to shamelessly plug my atomic_enum fork that may look a bit nicer than magic numbers.

I actually thought of using it, but I don't know what's the policy on adding new dependencies. Can I?

Having CI pass is good enough IMHO if your changes are not likely to change other code paths - you might want to mention on which targets you were able to test your changes on (I assume you don't have access to all the supported chips)

Added to top comment, tl;dr esp32 only. The change is not hardware specific, so as long as all targets have a notion of base-mac it should work the same.


Assembler init throws

Hello, can you please describe, why this method throws? I checked sources, and here no functions that can throw inside this init.
public init(assemblies: [Assembly], parentAssembler: Assembler?) throws

@ManWithBear Thanks for pointing this out!
Indeed it seems redundant. There is also an unnecessary optional, as pointed out by @tomassliz.
I think we should improve this API. However, it would technically be a breaking API change, so we might need to tread carefully here. @yoichitgy what do you think? Maybe quick improvement might be more important here, given how (in most cases) negligible impact these changes would have on existing code.

Thanks @ManWithBear and @tomassliz for pointing out the issues.
Swinject v1 had dependency of Assember on SwinjectPropertyLoader. When I removed the dependency from Assember, I forgot taking care of throws and the optional argument.
I agree @jakubvano with the quick improvement in Swinject v2. I think we can keep the existing API (initializers) with @available(*, deprecated) annotation to avoid breaking changes.

Can I help with that?

Thanks @ManWithBear😃 Yes, it's very helpful if you make a pull request👍👍👍

Thanks, I will try to find time today.

Hm, it's kinda weird.
From Swift Programming Language:

The throws keyword is part of a function’s type, and nonthrowing functions are subtypes of throwing functions. As a result, you can use a nonthrowing function in the same places as a throwing one.

So removing throws keyword will not break API and should be fully compatible with previous versions.
But statements with guard like:
guard let childAssembler = try? Assembler(assemblies: [], parentAssembler: assembler) else {
    return
}

Produce "Segmentation fault: 11"
Right now it's only issue.

Even if compiler wasn't buggy in this case, it would still produce warning about no throwing functions occuring within try expression.
With your PR it produces deprecation warning, but it is much more clear what change caused it.

Thanks again for your work :)


Added DataAccess Class Library and SQL Server Projects

Added a .NET Framework Class Library for Data Access with SqlCrud and SqlDataAccess classes.  Added SQL Server Project.  Moved Models from UI to Class Library.
Note that Models are needed in the Class Library.  If there is a need to have a different model in the UI, or to have data annotations that are UI specific, then UI-specific Models can be created (again) in the UI Project.
I hadn't realized the csproj file updates hadn't been committed in the first commit, which is why there are 2 separate commits.
There are still a few TODOs in the SqlCrud class's async methods to make them truly distributed processing, but they will work async as written (and of course the synchronous methods will work fine as well).

I've modified the DataAccessLibrary DataModels and the SQL Server DB project tables & stores procedures to match the structure you had in your single SQL script file.  I then modified the SqlCrud class to match.  I also restored the Models in the UI project based on what you had originally; as mentioned, you will need to do a mapping between the DataAccess Models and the UI Models, if you want them to be different.
I also added data annotations on the DataAccess DataModels for the max string lengths.  I made the value types nullable where applicable, but string is a reference type, and since you are using an older version of the .NET Framework (4.6.2 vs. current 4.8.1), I could not make the strings nullable.  I'm not sure if sending an empty string to a nullable nvarchar will put in an empty string in the DB or leave it at null; to be safe, I recommend going to a more recent .NET Framework, or perhaps even moving to .NET 6.  We can then have the strings nullable as well.

I was going to post an issue about not being able to connect to a DB, until I saw this. I think this pull request will take care of that issue.


[WIP] Adds setting to Annotation UI to change quality of the chunk request

This pull request implements a switch in player settings to change the image data request.
The switch is off by default resulting in no changes to default behaviour (chunk request is quality=compressed).
When the switch is on, behaviour changes chunk requests to use quality=original.

Motivation and context

This feature has been requested in #3303 and #3824
For our particular context where compression time is much greater than any time savings from transferring smaller chunks, requesting quality=original is more efficient.
How has this been tested?

Have run E2E tests as spec'd in documentation.
General functionality testing around loading initial chunk, new chunks, using video playback.
Checklist

[x] I submit my changes into the develop branch
[x] I have added a description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] I have linked related issues (read github docs)
- [ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@brendando-csiro , thanks for the contribution! I have run tests. Please give us some time to review the PR.

Hi @brendando-csiro
Thanks a lot for the patch. Can you consider proposed changes?
Code linter says there is minor issue with trailling comma:

And one question about the implementation:

When we switch the option, for example from default compressed to original, will it update currently uploaded images?

Hi @bsekachev,
Thanks for the review. I'll try and get these changes implemented ASAP.
As for the question regarding currently uploaded images, current behaviour doesn't change anything with regard to already loaded chunks in the UI, only chunks loaded after the switch. Its a bit inconsistent but unsure how I would go about implementing more consistent behaviour (unfortunately not a web dev).

@brendando-csiro , thank you for the contribution. Could you please help us to resolve conflicts in the PR? What is the status of the PR? Is it ready?

Hi @nmanovic , apologies for delayed response. PR is not ready for merge, I've been busy with internal projects but should have some time next week to have a look.

I will close this PR for now. Do not hesitate to reopen if you are ready to continue this useful work


Wrong Int64 Serialization

When i try to serialize Int64 then i get result that is not a string.
https://deck.net/b292188f47ec87457e2cdc470c58b55e
public class Program
{
    public static void Main()
    {
        long a = 19L;
        var serialized = JsonConvert.SerializeObject(a);
        Console.WriteLine(serialized);
        serialized.Substring(0, 1);
    }
}

Fixed and merged! The fix will make it live the next Bridge.Newtonsoft.Json package release!


Create documentation for current infrastructure state

Goes into detail into each application/service's deployment strategy and links to the tf configs and source for each.

This is super nice!


Update setup.py to prevent installing v2.0 of djangocms-cascade

@jrief the recent update of https://github.com/jrief/djangocms-cascade requires Django>=3.1, whereas django-shop 1.2.3 requires Django<3.1 (line 9 below).
This PR simply prevents the 2.0 version from being installed. When this change is not made, there will be a VERSION NOT FOUND ERROR
ERROR: Could not find a version that matches django<3.1,<3.2,<4.0,>=1.6,>=1.8,>=1.8.0,>=2.0,>=2.1,>=2.2,>=3.1

  django<3.1,>=2.1 (from django-shop==1.2.3->-r /var/folders/yb/4bmdr0l927n7zk6m_jdfq4p00000gp/T/pipenvgrarsd7mrequirements/pipenv-ydxt677t-constraints.txt (line 17))
  django>=3.1 (from djangocms-cascade==2.0->-r /var/folders/yb/4bmdr0l927n7zk6m_jdfq4p00000gp/T/pipenvgrarsd7mrequirements/pipenv-ydxt677t-constraints.txt (line 18))

Your pull request is merged into version 1.2.4


Test FIPS mode on ubuntu in the umbrella pipeline.

Currently Chef Infra Server supports FIPS only on Centos. From release 14.3 onwards we will also support FIPS on Ubuntu.
Umbrella pipeline has a scenario for testing FIPS. This can be used to test FIPS only with RHEL at this time.
REF: https://github.com/chef/umbrella/tree/master/chef-server/scenarios/aws/fips
The adhoc build does not test FIPS : https://github.com/chef/chef-server/blob/master/omnibus/omnibus-test.sh#L64 that is always set to false.
Chef if we can identify the distribution and enable FIPS accordingly or add different scenario to test for FIPS on Ubuntu.
Acceptance Criteria:

Umbrella pipeline has support for FIPS on ubuntu.
The nightly pipeline run enables FIPS on ubuntu test.
The server-full pipeline enables FIPS on ubuntu test.

Aha! Link: https://chef.aha.io/features/SH-3016

Verified the openssl included FIPS (by @tas50 )
# An openssl config that enables FIPS by default
openssl_conf = openssl_conf_section
[openssl_conf_section]
alg_section             = evp_sect
[evp_sect]
fips_mode = yes

And were are able to reconfigure chef-server on that box.

Since we'd need to pay for FIPS support in Ubuntu I think we can probably close this one out as a won't fix for now


Comet Effects

Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentaion

Describe the bug

A clear and concise description of what the bug is.

Possible solution

Describe the solution you thought of.

Screenshots

If applicable, add screenshots to help explain your problem.

please assign me

Go ahead @Skapsime
And must complete all issue before 10 August

okay, i complete all issue within 10 aug


Phase I: Preperation for JNK1, PTP1b, EGFR and Factor Xa

Input submission checklist

[x] created a directory for each system based on the template directory
[x] named and placed the directory with the following pattern: input_structures/prepared_structures/<set_name>/<system_name>

For each submitted directory:

[x] filled in system preparation details in the PREPARATION_DETAILS.md file
[x] added a PDB file with the protein named protein.pdb
[x] removed any cofactors from the PDB file and placed them in cofactors.sdf
[x] kept cystallographic waters and metals in the PDB file
[x] tested the PDB and, if available, cofactors.sdf file using the input validation script
[x] copied over the ligands SDF file to a file named ligands.sdf and removed any duplicate binding modes or protonation states, keeping the more favorable state

Summary of changes

Licensing agreement

[x] I agree to release these inputs under the combined MIT and CCBY SA 4.0 licenses of this repository

@hannahbaumann : oh will look into the protonations, thanks for pointing it out! :)

@hannahbaumann
ups! yeah, you are right, I will fix the jnk1 accident and try to keep all the waters (somehow the prep workflow did remove them after a certain threshold)
Todos:

[ ] keeping waters
[ ] fixing JNK1

Thank you @RiesBen ! I looked through it again and I noticed two things that I didn't see before, so sorry about that!

JNK1 (charge annihilation set) residue 325 (TYR): The carbonyl O for some reason doesn't belong to this residue, but is assigned to residue 553. I have no idea if this would cause any issues, but could you possibly change that?
JNK1 (JACS set): There are some duplicate ligands in the file with flipped binding modes. Could you remove the ones that are less favorable and document the steps in the preparation details file?

@hannahbaumann
hui, updated the files :)


Provide wheel package on PyPI

Hi!
Please could this package also by made available as a wheel on PyPI?
https://pypi.python.org/pypi/blessings
Wheels have the following advantages:

Faster installation time
Allows the wheel cache to work even when using the new pip hash-checking mode
Allows tools to statically inspect the package metadata without having to execute untrusted code.
...and more - see: http://pythonwheels.com

Since this package uses 2to3 on Python 3, it will need to have separate wheels for each, rather than a universal wheel:
https://packaging.python.org/tutorials/distributing-packages/#wheels
The Python packaging guide recommends using Twine to upload packages:
https://packaging.python.org/tutorials/distributing-packages/#uploading-your-project-to-pypi
As such, the steps for building/uploading a new release are then:
$ pip2 install -U twine setuptools wheel
$ pip3 install -U setuptools wheel
$ rm -rf dist/ build/
$ python2 setup.py sdist bdist_wheel
# Work around https://bitbucket.org/pypa/wheel/issues/147/bdist_wheel-should-start-by-cleaning-up
$ rm -rf build/
$ python3 setup.py bdist_wheel
$ twine upload dist/*

The PyPI package listing will then display three entries for the new release, one with type "Source" and two of type "Python Wheel" (one for each of Python 2 and 3).
Many thanks :-)

Ah I just spotted the use of 2to3, so this will need separate wheels for each of Python 2 and Python 3. I've updated the steps in the OP accordingly :-)

FYI the https://github.com/jquast/blessed fork uses wheel distribution, this project is not getting much attention, partly the reason for forking, sorry for any inconvenience :(

Related to #121


Constrain the main point of a spline on the Y-axis if the shift button is held down

Added code to constrain the main point of a spline on the Y-axis if the shift button is held down.
This is similar to constraining the angle of the offset control points of a spline.
Also, my code editor made some cosmetic code formatting changes as well. Sorry.

Seems useful. I might mess with it at some point to make it work for the X-axis as well but you're welcome to try too if you get to it before I can.


feat(chat): redesign mobile and overlay (Issue #618)

Description:

minor style changes for mobile and overlay messages
added context menu on tap if mobile

Issues:

Issue: https://github.com/epam/ai-dial-chat/issues/618

UI changes
https://www.figma.com/file/lwL5jneveZczAj5RLcLFH2/DIAL-Chat?type=design&node-id=5613-9394&mode=design&t=UXZMitpQSYuvcam4-4
Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix:, feat:, feature:, chore:, hotfix: or e2e:
[x] if contains breaking changes then the pull request name starts with fix!:, feat!:, feature!:, chore!:, hotfix!: or e2e!:
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:
No release type found in pull request title "resolve conflict". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - fix
 - hotfix
 - feat
 - feature
 - chore

/deploy-review

/deploy-review

/deploy-review

/deploy-review

/deploy-review

/deploy-review


portaudio devices and GUI

Added methods to:

Get devices

Count
List all / list inputs / list outputs
Default input and output
Device at specific index

Handle GUI

Start
Poll
Stop

Made computeAudio optional / dynamic: default is true on init, that can be changed at runtime via an instance method.
Changed types accordingly.
Added tests for new functions + test for receiving sample array.

Hey, many thanks for all the work, let me know when you would like to merge
aside would you like that I add you as maintainer of the lib? This is not something we are still actively using on our side so maybe that would make sens, let me know

Hey!
Thank you for this work!
I think you can merge now. I'm getting in the selectDevice part and it may be a bit longer.
And, yes, with pleasure to be a maintainer...


Changing display names for HTML formats (from dipl to Diplomatic, norm to Normalized, etc)

If you navigate to this page in the administrative view, http://coptic.aweb.io/admin/texts/htmlvisualizationformat/, you will see the four specified HTML formats that currently exist on the site. To change the display name for one (not the internal ANNIS name, but the one that appears for users on the URN resolver app), click on the title of the format you want to change.  Then edit the title to the value you want to be shown on the site.

These values can be changed anytime in the future, so let me know what your thoughts are here.

title and button title edited; slug left the same since that is what is linked to ANNIS


More structure

added dotenv, logging, helmet
split server and app (for testing in particular)
separate api
basic smoke unit test
some signal/exception stuff

TODO:

unify form of api response
basic validation (library or in-place ...)
better abaplint exception handling

dont add more to this PR, if its working
there is a lot of different parts happening

ok. I'll doublecheck it a bit later and release from WIP.
By the way i potentially closes #2 (depending on what was the intention)
Also a question regarding #1 : a framework - could be cool but isn't it an overkill ? Just a question

by the way it actually works ... but I change the shape of the API checkobject api... so will need a fix from abap side as well

OK, so actually it works. tests (sinlge one :)) ) pass. Postman works. Importantly - the backend will not work for now as I changed api response shape (I will fix there). Also I commented out the "addInfo" so far - I think it should be a separate issue to understand what is required there

suggest rolling back the breaking changes and introducing breaking changes in a separate PR

Ok, agree

checked the code. I actually forgot to rewrite check_object to the new  api shape, just the ping :D
so should work with the existing abapend for now. (abapend - it is a new term I guess)

can we merge ? I have some docker stuff in the pipeline :)

will have a look during the weekend, dont have much time this week

so, the cf push does not work anymore after #16, moving ts-node and typescript to a runtime dependency will probably solve it, but it does not seem very nice
suggest going back to the
"start": "tsc && node build/server.js"

will have a look a bit later. But from the top of my head - maybe the start command should not be npm start, but directly node build/server.js. Npm may swallow termination signals, it is kind of not encouraged for production. And changing start script this way will ruin other flows, nodemon in particular.

hmmm, what does the cf push checks to start the script by the way ? I'm not familiar with cf =( Is there are  some docs ?

conceptually it should be something like here: https://github.com/sbcgua/abaplint-cloud-foundry/blob/docker/docker/Dockerfile
npm ci
npm run build
npm prune --production
node build/server.js

it runs https://github.com/abaplint/abaplint-cloud-foundry/blob/master/manifest.yaml#L9, within https://docs.cloudfoundry.org/buildpacks/node/index.html
I use https://cockpit.hanatrial.ondemand.com/ for testing CF, free trial by SAP

Well, I read some links - it is quite obscure how and where cf does the actual preparation (npm install in particular) ... also examples - https://github.com/drnic/cf-sample-app-nodejs-typescript - do have separate build and run in package.json but just npm start in the manifest (???)
I have the following ideas for now:

The quickest: add a script - "start:cf": "npm run build && node build/server.js" and put it to manifest instead of start - could you try ?
there is some scn post mentioning some mta.yaml where several deployment commans can be given, but quite unclear from the first glance... - https://blogs.sap.com/2019/07/01/cloudfoundryfun-6-run-typescript-apps-on-cloud-foundry/
deploy with docker ? https://docs.cloudfoundry.org/devguide/deploy-apps/push-docker.html - most unified option in the long run !

fixed in https://github.com/abaplint/abaplint-cloud-foundry/commit/72c7e5ec9be05accfdb0d6e5ad76a3130062a20a, not super nice, but it runs

But why ? What's wrong with the start:cf suggestion ? What's wrong with the proposed scripts ?

suggestions welcome, but I dont want to spend too much time researching, just need something that can run

runs = on cloud foundry and locally(eg http://sci.abaplint.org)

Yes, so this PR is a suggestion. I did the study, this part is done. I spent some time and effort, read some posts picking good things. Considered different scenarios: development, testing, production. All to be consistent. With good clear naming. Wihtou unnecessary &&. Maintainable, reusable. On the cf subject I made 3 (!) proposal one of which should run from scratch. And canceling it with just "not super nice, but it runs" ... Sorry, but this is very demotivating. (and not the first time either).

Sorry, I feel the same, master worked previously, I don't want to spend hours fixing it, its very demotivating
the main problem with the PR is that it does not run in the environment that it is intended to run on, I'm not challenging the content

to summarize owr conversation in chat and in general. I think there should be clear criteria of "master works". Better to be defined somewhere openly like contribution.md or readme. Or at least clearly communicated in the comments. But not via direct adjustment of the code. A contributor might not be against some extra effort if clearly end reasonably communicated.
Anyway coming back to the constructive. I'll have a look at CF. Any links with "howtos" would be helpful. Is it same idea like in non-sap PaaS platforms ?
Long term: I'm really not sure that CF is the major solution for such a tool (although judging from my statistics). I think docker will have at least similar popularity among the enterprises. I have clients with own servers, with azure, but no one with cf. So I'd suggest to widen the "master works" criteria, maybe even renaming the repo ...

howtos: only the buildpack link, https://docs.cloudfoundry.org/buildpacks/node/index.html, I have not focused much on deployment and structure

sure that CF is the major solution for such a tool

agree, just wanted something that fits into the SAP story. This is a difficult area, CF handles scaling quite well, node runs in a single thread so this is an issue with the current implementation. Running this code in a 100+ developers setup probably doesnt work right now, solving this might bring us into the area of Kubernetes / Knative / Kyma, which is uncharted territory for me

taking a look at this now, trying to get this branch running on CF

-> https://github.com/abaplint/abaplint-cloud-foundry/pull/24

large parts of this PR merged via #24
closing


inspircd: 3.11.0 -> 3.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/inspircd/versions.
meta.description for inspircd is: "A modular C++ IRC server"
meta.homepage for inspircd is: "https://www.inspircd.org/"
meta.changelog for inspircd is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/n4i08ay2krzzqgpxayrkn23rkysccz2a-inspircd-3.12.0-bin/bin/inspircd passed the binary check.
/nix/store/n4i08ay2krzzqgpxayrkn23rkysccz2a-inspircd-3.12.0-bin/bin/inspircd-testssl passed the binary check.
/nix/store/n4i08ay2krzzqgpxayrkn23rkysccz2a-inspircd-3.12.0-bin/bin/inspircd-genssl passed the binary check.
1 of 3 passed binary check by having a zero exit code.
3 of 3 passed binary check by having the new version present in output.
found 3.12.0 with grep in /nix/store/n4i08ay2krzzqgpxayrkn23rkysccz2a-inspircd-3.12.0-bin
found 3.12.0 in filename of file in /nix/store/n4i08ay2krzzqgpxayrkn23rkysccz2a-inspircd-3.12.0-bin

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
docbookrx
inspircd
inspircdMinimal

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n4i08ay2krzzqgpxayrkn23rkysccz2a-inspircd-3.12.0-bin \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A inspircd https://github.com/r-ryantm/nixpkgs/archive/f408d29ddf282805a8928e8b6bea5f60d0d421d9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n4i08ay2krzzqgpxayrkn23rkysccz2a-inspircd-3.12.0-bin
ls -la /nix/store/n4i08ay2krzzqgpxayrkn23rkysccz2a-inspircd-3.12.0-bin/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

inspircd
inspircdMinimal

Maintainer pings
cc @sternenseemann for testing.

@ofborg test inspircd


Revert "Revert "Revert "Revert "Update the game over message""""

Reverts EdGilmour/skills-review-pull-requests#4

cool commit, no issues


Doesn't work with rspec raise_error

let(:record) { FactoryGirl.create(:thing, name: "") }

it "fails" do
  expect { record }.to raise_error(ActiveRecord::RecordInvalid, "Name can't be blank")
end

Doesn't catch the error that pops up.

It should be like,
It "fails" do
  expect { FactoryGirl.create!(:thing, :name => "") }.to raise_exception(ActiveRecord::RecordInvalid, "Name can't be blank")
end

@krainboltgreene if you remove the message, does it work? If you call record outside the expect block, does it raise any exceptions? If so, where are they misaligned?
FactoryGirl doesn't impede in any manner when it comes to this - so any appropriate exceptions should be getting raised.


Is there a support network now, can you access the Internet? How to set

Is there a support network now, can you access the Internet? How to set

Internet access works, provided your guest OS supports the network card you choose


cython friendly setup.py

https://github.com/dmlc/mxnet/pull/4723

please check the usage of setup tools and distutils. In general, use setup tools for general build and distutils for inplace build


Root :index route incorrectly matches single-character URLs

Create a minimal project with padrino-gen, add a "get :index { }" block to it.
Request /a, and be surprised when it actually matches the route and blows up trying to extract params from it:
NoMethodError - undefined method `names' for nil:NilClass:
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router/matcher.rb:58:in `params_for'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router/route.rb:112:in `params_for'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router/compiler.rb:54:in `block in call_by_request'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router/compiler.rb:86:in `block in rotation'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router/compiler.rb:85:in `loop'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router/compiler.rb:85:in `with_object'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router/compiler.rb:85:in `rotation'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router/compiler.rb:51:in `call_by_request'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/path_router.rb:43:in `call'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/application/routing.rb:943:in `route!'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/application/routing.rb:926:in `block in dispatch!'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1066:in `block in invoke'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1066:in `catch'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1066:in `invoke'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/application/routing.rb:924:in `dispatch!'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:906:in `block in call!'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1066:in `block in invoke'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1066:in `catch'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1066:in `invoke'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:906:in `call!'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:894:in `call'
    lib/ruby/gems/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
    lib/ruby/gems/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'
    lib/ruby/gems/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
    lib/ruby/gems/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
    lib/ruby/gems/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'
    lib/ruby/gems/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
    lib/ruby/gems/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
    lib/ruby/gems/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
    lib/ruby/gems/2.2.0/gems/rack-1.6.1/lib/rack/head.rb:13:in `call'
    lib/ruby/gems/2.2.0/gems/rack-1.6.1/lib/rack/methodoverride.rb:22:in `call'
    lib/ruby/gems/2.2.0/gems/rack-1.6.1/lib/rack/session/abstract/id.rb:225:in `context'
    lib/ruby/gems/2.2.0/gems/rack-1.6.1/lib/rack/session/abstract/id.rb:220:in `call'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:2021:in `call'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1486:in `block in call'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1795:in `synchronize'
    lib/ruby/gems/2.2.0/gems/sinatra-1.4.6/lib/sinatra/base.rb:1486:in `call'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/router.rb:84:in `block in call'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/router.rb:75:in `each'
    lib/ruby/gems/2.2.0/gems/padrino-core-0.13.0.beta2/lib/padrino-core/router.rb:75:in `call'
    lib/ruby/gems/2.2.0/gems/rack-1.6.1/lib/rack/handler/webrick.rb:89:in `service'
    lib/ruby/2.2.0/webrick/httpserver.rb:138:in `service'
    lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
    lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread'

Test case: https://github.com/Freaky/padrino-test-app

@Freaky Thank you for the thorough explanation. Fixed.
Please let me know if you still have the issue.

Looks good, thank you :)


Unsupported .version 8.1

I'm using Python 3.11.3 on Ubuntu 22.04.2 amd64 with numba 0.57.0 and cuda-python 12.1.0. Cuda scripts were working fine with cuda-toolkit-11.5. After upgrade to cuda-toolkit-12.1, I'm getting this error:
numba.cuda.cudadrv.driver.LinkerError: [222] Call to cuLinkAddData results in UNKNOWN_CUDA_ERROR
ptxas application ptx input, line 9; fatal   : Unsupported .version 8.1; current version is '8.0'

When you installed the CUDA toolkit 12.1, did the installer also update the NVIDIA graphics driver?  This first looks to me like the toolkit has bene updated but the system driver has not.

I opted not to update NVIDIA graphics driver, because I had problems with such an update before. Should I update the driver too, in order for Numba to work?

I finally managed to update the driver to version 530.30.02 and @cuda.jit works fine now.

I also ran into the same problem and as @pauljurczak I finally fixed it by installing a more recent driver (in my case the 545). These are my findings so far in case it helps someone else:
525 -> 8.0
530 -> 8.1
535 -> 8.2
545 -> 8.3


fix #138 add removeAllSwipeListner function

BTW, prettify the code.

@jpshelley @linfaxin when available, please check it.

It's a very simple change.


Add EmptyContent to the BitBasicList component

We need to show an empty state when there is no item in the list.
https://github.com/dotnet/aspnetcore/pull/49185/commits

Since this parameter is added in .NET 8 and our product is a multi-TargetFramework library, it is hard to support such a feature.
I suggest manually handling this requirement for now which is easy. You only need to show the empty content when the Items parameter is null or its length is zero, or when the ItemsProvider has a TotalCount of zero.

Thanks for contacting us. We're investigating this issue.
We'll let you know if it's possible to work on this issue.

The issue is accepted and planned. Resolving it will start ASAP.

The issue is accepted and planned. Resolving it will start ASAP.

Resolving this issue has started. It will be announced when this issue is resolved.

The pre-release has been published. Please give it a try and give feedback.


wrong post. please delete me

wrong post, please delete this

moved to https://github.com/getsentry/sentry/issues/37076

please delete me


Experimental SelectPanel2: Keyboard navigation for list

⚠ Merge after https://github.com/primer/react/pull/3764
Closes https://github.com/github/primer/issues/2636
Context: https://github.com/github/primer/issues/2579

Before focus zone for list:
https://github.com/primer/react/assets/1863771/48b460e1-1ef6-4cac-b535-81d1a08f9586
After focus zone for list:
https://github.com/primer/react/assets/1863771/5f3d1d44-f985-44a3-8fab-20ef498c3862
Notice how the list remembers the last item that had focus and jumps back to that 😇 (thanks @T-Hugs who wrote the original behaviors)

I'm glad they're still useful :)

When the item is selected with the space key, the list shifts.

Yes!
That is a bug in ActionList that I'm tracking in the epic come back to.

Tested it on Firefox. When the focus is moved to the list, the focus ring is not visible. It becomes visible if I go to the footer with tab and come back to the list.

Just want to resurface my other question in case it got lost.  (reference) Let me know if you address it in a different PR too 🙌🏻

Tested it on Firefox. When the focus is moved to the list, the focus ring is not visible. It becomes visible if I go to the footer with tab and come back to the list.

Wow! Thanks for flaging this again, I missed this in a hurry. It's strange because the ul list element is getting tabIndex in firefox but not in webkit 🤔

Let me know if you address it in a different PR too 🙌🏻

Yes. I think I'd like to reproduce this with primer/behaviors first, so fix it in a different PR


Update hdinsight-hadoop-customize-cluster-linux.md

updated the blob store support reference

@ashishthaps1 : Thanks for your contribution! The author, @hrasheed-msft, has been notified to review your proposed change.

#sign-off


fix(nuxt-js): fix include path in tailwind config

The current source JavaScript files of Flowbite does not exist in the path provided.

The current source JavaScript files of Flowbite does not exist in the path provided.

Hi @zoltanszogyenyi, I'm not sure if I'm supposed to tag someone to review my PR, it's been pending for a few days now. Whenever you get a chance, could you please help review this request? Thanks!

Hey @rabikr,
Thanks for contributing - merged!
Cheers,
Zoltan


cmd/mr_show: golint: if block ends with a return statement

Remove the else clause considering the if ends with return.
Signed-off-by: Bruno Meneguele<EMAIL_ADDRESS>

LGTM, ack


Add new feature: attred. Docs and tests are included.

Pull Request Check List
This is just a friendly reminder about the most common mistakes.  Please make sure that you tick all boxes.  But please read our contribution guide at least once, it will save you unnecessary review cycles!
If an item doesn't apply to your pull request, check it anyway to make it apparent that there's nothing left to do.

[x] Added tests for changed code.
[x] New features have been added to our Hypothesis testing strategy.
[x] Changes or additions to public APIs are reflected in our type stubs (files ending in .pyi).

[x] ...and used in the stub test file tests/typing_example.py.

[x] Updated documentation for changed code.

[x] New functions/classes have to be added to docs/api.rst by hand.
[x] Changes to the signature of @attr.s() have to be added by hand too.
[x] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.  Find the appropriate next version in our __init__.py file.

[x] Documentation in .rst files is written using semantic newlines.
[x] Changes (and possible deprecations) have news fragments in changelog.d.

If you have any questions to any of the points above, just submit and ask!  This checklist is here to help you, not to deter you from contributing!

First of all, I marked as done check-list item about hypothesis, about stubs and changelog just because template says "check it anyway", but I didn't make them.
So, attred is a decorator that takes any number of kwargs and apply key-vakue pairs to decorated callable object. Docs and tests are included.

I'm sorry but that out of scope for attrs. I can see that the name might indicated otherwise 😅 but we are squarely about helping people to write (better) classes.

Okay, good luck in development :D


Add command that prints installed KPOps version

It could be cool to have a version command like kpops version or perhaps a flag kpops --version/-v
This doesn't add much functionality, it wouldn't be much different from pip show kpops, but it feels intuitive that CLI tools have a dedicated way to output their version,
example

@raminqaf I didn't know one existed already


The skin will be reset after the character dies

The skin will be reset after the character dies

fixed


Fix hygiene in expansion

Resolves #163.

Note that this breaks compatibility with no-std environment.
See also https://github.com/dtolnay/async-trait/issues/132.

Reading through the issue, you mentioned a trick is needed to get this to work. I don't work outside of the std environment, so am not familiar with what would need to be done here. Would be happy to help if there's some good reading material to get me caught up.

The basic idea is to import the alloc in front of the trait/impl when expanding the code and refer that crate.
extern crate alloc as _alloc;
trait ...
    fn method() -> ::_alloc::boxed::Box<...>

However, this way may result in crate name collisions (multiple _alloc in the same scope).
One of the workarounds for collisions is using the crate name that contains the hash value of the input tokens instead of _alloc. Something like:
#[proc_macro_attribute]
pub fn async_trait(args: ..., input: ...) -> ... {
    // ...
    let alloc_crate = format_ident!("_alloc{}", hash(&input));
    // ...
    quote! {
        extern crate alloc as #alloc_crate;
    }
}

use std::{collections::hash_map::DefaultHasher, hash::Hasher};

fn hash(input: &TokenStream) -> u64 {
    let mut hasher = DefaultHasher::new();
    hasher.write(input.to_string().as_bytes());
    hasher.finish()
}


Dockerize client-fhir-testing

I had issues running this. It's probably another docker on windows thing. I was able to build and run the image, but couldn't access anything on the server. I noticed that running this natively, I see this message before the server actually starts:
Loading options from file proxy.yml
@ backend set to: https://r4.smarthealthit.org
But when running from docker, I don't see these messages.

I had issues running this. It's probably another docker on windows thing. I was able to build and run the image, but couldn't access anything on the server. I noticed that running this natively, I see this message before the server actually starts:
Loading options from file proxy.yml
@ backend set to: https://r4.smarthealthit.org
But when running from docker, I don't see these messages.

Can you update the README with instructions?
Also if someone were to pull this from DockerHub do we have any guidance on updating the proxy.yml? We could mount a new proxy.yml in I imagine.

Can you update the README with instructions?
Also if someone were to pull this from DockerHub do we have any guidance on updating the proxy.yml? We could mount a new proxy.yml in I imagine.


make server cert path return None if tls disabled

title says it all
charm tracing expects Optional[str], where None means: there's no TLS, and str means: here's your cert.
Alertmanager is returning str even though the file doesn't exist, which makes charm-tracing log exceptions on every hook.

obsoleted by #251


Occupation of Germany

1946.1.1 when the game starts, the faith of Germany was largely undecided. So, somethings needs to be done with the end of occupation in Germany. The French where against a reunified Germany - that should be reflected as a game play option for them. Similarly, the Roosevelt initially advocated US zone the be in northern Germany. From the Cairo Conference of 1943 Roosevelt drafted this division proposal for Germany .

The US and British zones was decided on military planning grounds. With UK in the north and Germany in the south. And Churchill came up with a proposal similar to Roosevelt’s except it put the border between the two northern zones much further to the west (thus getting support by Stalin). Respecting the historical boundaries of the German states. Whereas Roosevelt had drawn a straight line through the Rhineland, Hesse and north of Bavaria.

Stalin did not agree on dividing Germany. The Committee on Dismemberment of Germany established at Yalta, was torpedoed by Gusev the USSR representative (ref Stalin's Unwanted Child: The Soviet Union, the German Question). Stalin's view was that if divided, by force, Germany would inevitably want to unite.
As a player of UK, France, US you should be able to go with the fragmentation vision of Germany. Constrained by realities of the Potsdam occupation zones, but in line with these earlier ideas (including Churchill's idea of a “Danubian Confederation”, comprised of the southern German states, Austria and Hungary).

The UK would thus be given the options to:

Reunite Germany (that potentially would end up as West Germany depending on the actions of others)
Form Bizonia (Trizonia). I.e. West Germany (if US agree)
Release a North German state

The UK would decide for it's Austrian zone, to

Reunite Austria
Form Bizonia with the US zone.

The US would thus be given the options to:

Reunite Germany (that potentially would end up as West Germany depending on the actions of others)
Form Bizonia (Trizonia). I.e. West Germany (if the UK agree)
Release a South German state

The US would decide for it's Austrian zone, to

Reunite Austria
Form part of a South German state.

The Soviet would thus be given the options to:

Reunite Germany (that potentially would end up as West Germany depending on the actions of others)
Release a East German state

The Soviet would decide for it's Austrian zone, to

Reunite Austria (that potentially would end up as democratic Austria depending on the actions of others). If the others decide on South Germany, Austria may become communist.

The French would be given the options to:

Reunite Germany (that potentially would end up as West Germany depending on the actions of others)
Form Bizonia (Trizonia). I.e. West Germany (if the UK and US agree)
Propose to annex the Rhine land (giving up ares to the east to the US decision) and for a International Rhine zone (if the UK and US agree on the dividing Germany policy)

The French would decide for it's Austrian zone, to

Reunite Austria
Form part of a South German state.

Every thing would be driven by event as the faith of Germany is inevitable. The player would be given the option to delay deciding but only 2 times.
It is possible to block decisions of others - i.e all must agree for a reunified Germany or Austria. Division takes presence with the excretion of the French annexation of the Rhine land - which requires US to decided for a South German state.

For the french it would be version of an unhinged Monnet Plan - "The then French government originally wanted to leave the possibility of annexing further areas of the Left Rhine after the conversion of Saarland into a protectorate."(from wikipedia) ". But in the French zone only. Remember, the prerequisite for this alt history, is that the allies don't get along on what to do with Germany.  The Monnet plan mostly concerned the Rhur. But that was part of the British zone. I.e. not under direct french control. They did however want special treatment of Germany-west of the Rhine. And Roosevlets initial idea supported that.
The Monnet plan

The French would give up occupied areas east of the Rhine to the new South German state, and put the rest under direct French administration.

Could you add an option for a UK player to give some land to the Netherlands? https://en.wikipedia.org/wiki/Dutch_annexation_of_German_territory_after_World_War_II

@James9883 that should only happen if Germany somehow would not lose all the territory east of the Oder-Neiße, since 10 millions refugees from there had to move to the West and therefore the allies prohibited annexations as well as the expulsion of Germans from Alsace;
@simsulla how would South Germany look like? would it include hungary or south tyrol? and according to trizonia would that include terrytories that are polish at the start of the mod eg. pommerania?
btw. more gameplay options and less railroading = more fun :D

Would new tags have to be created for both the North and South German states, if so what will the new two countries be called?

@James9883 in this alt-history scenario the UK would be the deciding power (i.e. the one controlling the territory) - and the recipient of ethnically cleansed Germans. Why would a UK player give the Dutch (a vic2 greater power) these territories?
@Liegnitz, no, the Donau thingy,was Churchills idea. Roosevelt outlined is the underpinning idea of a different US policy (in contrast to what they did in reality -> bizonia -> trizonia) - with some practicality adding parts of Austria, depending on if the allies agrees on Austria or not.
@arandomperson5000 IAR would be retired. SGF and NGF from vanilla would be introduced. NGF with some different flag. The French was the one who resisted "trizonia" the most, and instead wanted a split-up Germany. So, yes, maybe a Rheinland-Pfalz is a more likely scenario than direct french annexation. But I don't think the UK would give up its parts west of the Rhine to France.

Already 1946 there where elections in the german states (landtagswahl) in the Soviet zone and in the US zone (Hessen, Bayern). To my limited understanding, the elections where manipulated by eligibility (excluding german nationalists, forcing Communist/Socialist unification in the SBZ), but once performed relatively free. In the reminder of states elections where held in 1947.
Bizonia was formed 1 Jan 1947. Already in Oct 1946 minister-presidents of the US, UK zones discussed cooperation.

The flags of East Germany will have to be changed if a North and south German dates are added in as the flags are the exact same flags of the South German Federation in vanilla Victoria 2. Also if IAR is retired which tag will take its place in the events about the International Authority for the Ruhr.

On the change primary culture decisions for the UN mandates, I'm a little bit confused on how to approach the German Occupation Zones should I edit the decisions to include the new tags or the current tags used ingame.

Use the new tags..
trigger = {   OR = { tag = NGF tag = SGF... }   NOT = { government = provisional_government }   NOT = { primary_culture = german } }
then change the primary culture.


watcherService causing high CPU and memory usage when opening workspace

VSCode Version: 1.19.0
OS Version: Linux x64 4.3.0-kali-amd64

Steps to Reproduce:

Open Folder: select my project folder, and the CPU usage is normal;
If I choose "Add Folder to Workspace" instead, the CPU usage is still normal; But if I close VSCode and open it again (resume the workspace), the CPU usage becomes 100% and never falls down.

"node_modules" is a large folder in my project, and I set files.watcherExclude for USER SETTINGS, WORKSPACE SETTINGS and Folder Settings.
It is like:
"files.watcherExclude": {
		"**/.git/objects/**": true,
		"**/.git/subtree-cache/**": true,
		"**/node_modules/**": true,
		"**/dist/**": true
    }

This issue only occurs in workspace. The CPU usage is pretty normal when I open it as a folder.

Reproduces without extensions: Yes
Run code --status
Version:          Code 1.19.0 (816be6780ca8bd0ab80314e11478c48c70d09383, 2017-12-14T09:56:48.842Z)
OS Version:       Linux x64 4.3.0-kali1-amd64)
CPUs:             Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz (4 x 2999)
Memory (System):  7.66GB (1.60GB free)
Load (avg):       1, 1, 1
VM:               0%
Screen Reader:    no

CPU %	Mem MB	Process
    2	   102	code main
    0	    24	   zygote
    5	   196	     window (settings.json - score-manage2 (工作区) - Visual Studio Code)
   99	  1373	       watcherService
    1	    63	       extensionHost
    1	    55	         electron_node jsonServerMain.js
    1	    94	     shared-process
    1	    86	   gpu-process

Workspace Stats:
|  Window (settings.json - score-manage2 (工作区) - Visual Studio Code)
|    Folder (score-manage-frontend): 660 files
|      File types: variables(154) overrides(146) js(127) css(93) less(47)
|                  vue(17) map(12) ttf(11) woff(9) svg(9)
|      Conf files: package.json(2) gulp.js(2) settings.json(1)
|                  webpack.config.js(1)

Thanks.

@Silas-Yang could it be possible that you have circular symlinks in your workspace?
/cc @Tyriar

I tried deleting all symlinks in my folder, and the issue is still there.

The issue disappears only when I delete node_module or choose "open folder" instead of "Add folder to workspace".

The problem will occur even if there is only one root folder in workspace.

it won't occur at the first time I add the folder to workspace. If I close VScode and open it to continue with the workspace, the issue occurs.

Does it reproduce if you only open that one folder and set "files.useExperimentalFileWatcher": true after a restart?

@bpasero Yes, it does.
I found the reason. It's because I used cnpm to install the modules. The simplest workaround may be
to use cnpm install --by=npm to avoid symlinks.
It seems occurring in Windows too: https://github.com/Microsoft/vscode/issues/35659
But I don't know why "files.watcherExclude" doesn't work.
I set it like this:
    "files.useExperimentalFileWatcher": true,
    "files.watcherExclude": {
        "**/.git/objects/**": true,
        "**/.git/subtree-cache/**": true,
        "**/node_modules/**": true
    },

Thanks.

@Silas-Yang that setting is not used if the new experimental watcher is used.
Closing as duplicate of https://github.com/Microsoft/vscode/issues/36307


Update Composer dependencies (2023-12-09-00-12)

Visual regression test passed!
View the visual regression test report


add production_configs/20240727_v0.10.11_src12_tuned

New Prod config
Self check-list:

[x] I have checked the lstchain config, in particular for:

[x] az_tel instead of sin_az_tel if data to be analyzed have been produced with lstchain <= v0.9.7
[x] "increase_nsb" and "increase_psf" are provided in "image_modifier" (if used)

[x] I have checked the environment in the lstmcpipe config and it is the one used to analyse DL>1 data
[x] I have provided the command (in README), or script (in additionnal .py file) used to produce the lstmcpipe config

Prod_ID
20240727_v0.10.11_src12_tuned
Short description of the config
full DL1ab production (with NSB tuning for src12) with lstchain v0.10.11
NSB level was checked in the following way:
input_mc_base = Path("/fefs/aswg/data/mc/DL0/LSTProd2/TrainingDataset/GammaDiffuse/")
input_mc = input_mc_base / "dec_min_413/sim_telarray/node_corsika_theta_33.058_az_173.79_/output_v1.4/simtel_corsika_thet
a_33.058_az_173.79_run1.simtel.gz"

input_data_base = Path("/fefs/aswg/data/real/DL1/")
input_data = input_data_base / "20240701/v0.10/tailcut84/dl1_LST-1.Run17967.0000.h5"

print("this config was downloaded (and modified) on %s" % download_config_modified_time)
config_file = Path("./lstchain_standard_config.json")

!lstchain_tune_nsb --input-mc $input_mc --input-data $input_data --config $config_file

The resulting values are the followings:
this config was downloaded (and modified) on 2024-07-27 10:21:03

Real data:
   Number of bad pixels (from calibration): 13
   Median of FF pixel charge: 75.561 p.e.
   Median across camera of good pixels' pedestal std 2.217 p.e.
   Number of pixels beyond 3 std dev of median:    34, (above 2.73 p.e.)
Good and not too bright pixels: 1812

{
  "increase_nsb": true,
  "extra_noise_in_dim_pixels": 1.297,
  "extra_bias_in_dim_pixels": 0.385,
  "transition_charge": 8,
  "extra_noise_in_bright_pixels": 1.536
}

These are pasted on the lstchain_config_2024-07-27.json.
Why this config is needed
Reprocess the data of src12 with version of lstchain v0.10.11 and with NSB tunning.
Other information
command-line:
prod_id = "20240727_v0.10.11_src12_tuned"
dec_list = "dec_min_413" # declination=-4.13, Decl. of G17.8+16.8 = -5.145
source_prod_id = "20240131_allsky_v0.10.5_all_dec_base"
!lstmcpipe_generate_config PathConfigAllSkyFullDL1ab --overwrite --prod_id $prod_id --kwargs source_prod_id=$source_prod_id --dec_list $dec_list

Production started 🚀


v1.13 Backports 2024-02-08

[ ] #30247 (@marseel)
[ ] #30536 (@hemanthmalla)
[ ] #30525 (@tklauser)
[x] #30496 (@giorio94)
[ ] #30378 (@brlbil)
[ ] #30612 (@gailsuccess)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 30247 30536 30525 30496 30378 30612

/test-backport-1.13

The expected Conformance Gateway API check is missing because it has been renamed in this PR to Conformance Gateway API (ci-gateway-api).
All testing has passed, awaiting for reviews now.

This should be ready to merge as soon as reviews are in.


Improve Cards complex interaction documentation example

A working menu in this example could be a good addendum to newbies.
Please find the associated PR here : https://github.com/mui-org/material-ui/pull/19166

Thanks for the feedback. We need to balance the complexity of the demos with the objective of it. I'm not sure making the 3 dots interactive would bring much value, when you can find the solution in the Menu docs page. Here, we make sure the dots are displayed at the right place, it should do 80% of the job.

okay I can understand.
But at the first newbie look this 3 dots with nothing seems like a bug or a missing part in this particular demo.
A light menu don't add so much complexity in this particular code IMO that is titled "complex interaction" demo ;).
Thanks for the great lib and all the job done, Regards.


BPMSPL-160: DRL text editor improvements.

https://github.com/uberfire/uberfire-extensions/commit/1e9bc9b31


Align text with ruler

Is there a way to align text or label ruler for average/ custom value?

btw, these kind of questions might be easier on Discord, but here works too.  Discord can be nice to chat back and forth.

@JonathonRP Something like this..

@JonathonRP Something like this..

Yes, close enough, I wanted value and label on both sides but this is good enough

Discussed further on Discord, and updated vertical/horizontal examples.  Instead of <Point>, just leveraged let:yScale and <Text y={yScale(avg)} />


Nopaste with middle mouse button in linux.

Missing the usual way to paste text in linux.
Middle mouse button and/or shift+insert.
Bug or feature?
~$ atom --version
0.96.0-4fa0b6e

@kevinsawicki thanks again for this patch. There is a $5 bounty on this issue at BountySource. You will be able to claim it if you want - or if not you can waive it and after a refund I'll repush it to some other issue.

Is there a way to disable this feature?

@varemenos see #6712.

This issue is still open, right? I see varemenos saying about disabling it but for me it is not enabled/i don't have the option to enable it.
I have version 1.0.0.
Are we going to have the middle click pasting the 'selection clipboard' in the next release??

What OS are you on? I also have 1.0.0 in Linux and it works. I don't
think it's supposed to work on other OSs.
2015-07-06 11:40 keltezéssel, Emmanouil (Manos) Karamanos írta:

This issue is still open, right? I see varemenos saying about
disabling it but for me it is not enabled/i don't have the option to
enable it.
I have version 1.0.0.
Are we going to have the middle click pasting the 'selection
clipboard' in the next release??
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/2244#issuecomment-118787437.

Linux ** 3.19.0-21-generic #21-Ubuntu SMP x86_64 GNU/Linux
Is the new version affected by the old configuration?
Maybe I should purge and install again?
Certainly there is no option in the configuration.

For someone else that might be searching the same thing:
I 'reset' Atom configuration (mv ~/.atom ~/.atom-old) and middle click works.
I will install the packages (the ones i still need) and will report here if there is a conflict (that is if a package breaks the middle click)

With a clean install of
	node -v && npm -v
		v2.3.4
		2.12.1
	atom --version
		1.0.3-5566d54

on
	lsb_release -rd
		Description:    openSUSE 13.2 (Harlequin) (x86_64)
		Release:        13.2

I've no middle-click paste in atom -- either of primary or clipboard contents.

Ctrl+Shift+V for paste...
#SM


tag versions of gems in source repo

It would very useful to be able to look in this repo for example for changes between version of the tool installed via gem (ex: see the git log or git diff between 1.7.17 and 1.7.16).

The convention right now is that a commit comment indicates a release.
See https://github.com/cabo/kramdown-rfc/commits/master/, which also gives you the commit comments for what changed (here, just one commit, but it often is more than one).
Maybe try
https://my.diffend.io/gems/kramdown-rfc/1.7.16/1.7.17
for a quick look at a diff betweentwo given gem releases.
Of course, since most changes are in the nested kramdown-rfc2629 gem,
https://my.diffend.io/gems/kramdown-rfc2629/1.7.16/1.7.17
is a bit more interesting.


CASE expr with NULL literals panics 'WHEN expression did not return a BooleanArray'

Reproducer:
> select CASE WHEN NULL THEN 'foo' ELSE 'bar' END;
thread 'main' panicked at 'WHEN expression did not return a BooleanArray', datafusion/src/physical_plan/expressions/case.rs:381:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The correct output is 'bar'
I think the solution will likely be to teach CaseExpr about type coercion (as is done in BinaryExpr and function calls) once coercion knows about the null type (and that it can be cast to any other type). See https://github.com/apache/arrow-datafusion/issues/1184 for more details

rough fix here #2197


Handle the move which makes the ova first

Ref #962

I feel like this should just reorder the moves in the various ?- cases rather than removing the flop at the end.  Virtually every core that maintains a (list move) flops it at the end so that incrementally adding is easy and happens in the order you'd expect.

Yeah, if the issue is (the moves of) notify-clients ought to happen after
set-wake, it would be a lot clearer if the invocations were reordered
accordingly in ++call.
On Thursday, 3 January 2019, Philip Monk<EMAIL_ADDRESS>wrote:

I feel like this should just reorder the moves in the various ?- cases
rather than removing the flop at the end. Virtually every core that
maintains a (list move) flops it at the end so that incrementally adding
is easy and happens in the order you'd expect.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/963#issuecomment-451256851, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhtoei0Tbc9dLa9lA9rNWlXLXLt9dks5u_l75gaJpZM4Zoqil
.

Hm, or barring that due to data flow constraints, a renaming to e.g.
(set-wake-before moves)
On Thursday, 3 January 2019, Anton Dyudin<EMAIL_ADDRESS>wrote:

Yeah, if the issue is (the moves of) notify-clients ought to happen after
set-wake, it would be a lot clearer if the invocations were reordered
accordingly in ++call.
On Thursday, 3 January 2019, Philip Monk<EMAIL_ADDRESS>wrote:

I feel like this should just reorder the moves in the various ?- cases
rather than removing the flop at the end. Virtually every core that
maintains a (list move) flops it at the end so that incrementally adding
is easy and happens in the order you'd expect.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/963#issuecomment-451256851, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhtoei0Tbc9dLa9lA9rNWlXLXLt9dks5u_l75gaJpZM4Zoqil
.

A comment explaining why we prepend the Unix move would also be helpful.


Accessing Google Sheets using service account

Since I am developing something on AWS Lambda, I need the API to be able to access Google Sheets using service account. I saw Sheets can only access using API Key and client_json credential files... is it possible to use service account?

I was looking at this repository and saw a recent question so I decided to comment because I just implemented a system where a service account is used to periodically download certain Google sheets as .csv files using Google Sheets API v4. You will need to create a service account, get a JSON file that contains service account credentials and then grant access to the created service account to desired resources in Google Drive. You will need to install some third-party libraries, e.g. google-api-python-client, google-auth-httplib2 and google-auth-oauthlib. Here is my implementation:
import csv
from typing import Sequence

from googleapiclient import discovery
from google.oauth2 import service_account
from config import GOOGLE_SHEETS_CREDENTIALS_PATH

SCOPES = [
    "https://www.googleapis.com/auth/spreadsheets.readonly"
]

class GoogleSheetsAPIRequest:

    def __init__(self, credentials_fpath: str = GOOGLE_SHEETS_CREDENTIALS_PATH, scopes: Sequence[str] = None) -> None:
        scopes = scopes or SCOPES
        credentials = service_account.Credentials.from_service_account_file(credentials_fpath, scopes=scopes)
        self.service = discovery.build("sheets", "v4", credentials=credentials)

    def download_sheet_to_csv(self, spreadsheet_id: str, tab_name: str, output_fpath: str, **kwargs) -> None:
        result = self.service.spreadsheets().values().get(spreadsheetId=spreadsheet_id, range=tab_name).execute()
        output_file = output_fpath if output_fpath.endswith(".csv") else output_fpath + ".csv"
        with open(output_file, "w") as f:
            writer = csv.writer(f, delimiter=kwargs.get("sep", ","), quotechar=kwargs.get("quotechar", "\""),
                                quoting=kwargs.get("quoting", csv.QUOTE_ALL), escapechar=kwargs.get("escapechar", "\\"))
            writer.writerows(result.get("values"))
        f.close()

Thanks! I made a similar solution to get around from it as well: https://github.com/stephenhky/SSSpend/blob/master/ssspend/spenddataframe.py#L18