Not compatible with Origins mod

I installed Origins mod(https://www.curseforge.com/minecraft/mc-mods/origins)on the server and my client. And when connecting to this server through velocity, It shows
'This server requires you to install the Origins mod (v1.3.1) to play.'
I tried turning off the ’performVersionCheck‘ option in the Origins config file. When I try to connect again, velocity shows
'[17:07:11 ERROR]: [server connection] Epresin -> lobby: exception encountered in com.velocitypowered.proxy.connection.backend.BackendPlaySessionHandler@33f555a6
com.velocitypowered.proxy.util.except.QuietRuntimeException: A packet did not decode successfully (invalid data). If you are a developer, launch Velocity with -Dvelocity.packet-decode-logging=true to see more.'
After the client and server removed the origins mod, I was able to join the server.
velocity latest.log
server latest.log

I also have this problem when using FabricProxy

Have you tried without FabricProxy-Lite?

你有没有试过没有FabricProxy-Lite？

I tried it and it can join the server normally

You need to install CrossStitch.
As origins mod only send command to player with OP permission, issue will only cause on OP join server.
Please refer to the velocity documentation: https://velocitypowered.com/wiki/users/server-compatibility/

您需要安装 CrossStitch。由于源模组仅向具有OP权限的玩家发送命令建议，因此问题仅在OP加入服务器上引起。请参阅速度文档：https://velocitypowered.com/wiki/users/server-compatibility/

Thank you for your help.


Add discord-bot

Solution to issue #38
All information on: how to run it, how it works, what does it do; is in README file.

Great Work Love it


Is multiple reference supported

Hi, Is multiple references supported ? (e.g., for SummEval, where each sample has 10 references)
Thanks!

We are sorry that this version does not support multiple references.
UniEval can only use multiple reference summaries for evaluation in relevance dimension, as it is a reference-free evaluator in other dimensions for summarization. In our experiments, we used the first reference summary to calculate the score for relevance.
If you want to use multiple references, one possible approach is to average the scores of all 11 reference summaries in SummEval, which may get a small boost based on previous papers (CTC, BARTScore).

Yeah that makes sense, thanks!


Operation Interface Enhancement + Clarification

added set notation to all the geometry operations
added a warning to say sample_surface=True doesn't work

Ok the fix in the documentation, mergeable.


Incompatible with Indium

Yes, I was the one asked about the same issue in the Discord but no response, so I try to test every single mod that affect rendering myself, found out that Indium was the cause of "Resource loading failed"

Run with Indium
Log: latest.log
Video: https://streamable.com/fndxbf

Run without Indium
Log: lastest.log
Video: https://streamable.com/luefks

My resource pack is 100% came from VanillaTweaks, every others are from the mods, already listed in the log

Fixed in 0.1.1, thank you for reporting
Cheers


working trigram

working trigram homework
assorted lab assignments.

For your mailman project, it looks like you have chosen a list of lists for your data structure.
What are the other structures you could have chosen? Would any of them simplified your code, especially to get rid of so many for loops through the data.


Write a JavaScript program to find minimum of n numbers

Description
Write a JavaScript program to find minimum of n numbers
Input  : 10 20 30 40 50
Output : 10

How to contribute

Save the solution in program/FindMinimumOfNNumbers.js file
Add FindMinimumOfNNumbers.js file in find-minimum-of-n-numbers folder

!assign


Add 'layout' function to obtain the size of the outer container

Hello!
We discussed in Discord the possibility of adding an easier means of obtaining the outer container's (or page's) dimensions from within any element/content.
This PR should make it possible with the syntax of layout(size => {... element using size.width and size.height ...}), which always returns the dimensions of the outer container, or of the page (excluding margin).
From my tests, all seems to be working; just one thing seems off: when working with certain very tight dimensions, at some point the incredible height of infpt was produced (try, for example, removing the line #set page(height: 120pt) from the block-sizing test).  I will try to later investigate if fixing this is possible, or the cause of this in the first place, but I appreciate any help in this regard from other contributors.
Also, feel free to say if this function is better suited for another category, or if the tests should be changed / more tests should be added. (Do not worry, I made sure the PNGs were optimized, haha.)

infpt happens when the page size is auto.

infpt happens when the page size is auto.

Well, that explains it; I'm guessing (from the fact that measure doesn't check for this, though I don't know if it can be affected) that this (infpt) should be the expected output for the end user then? Or should we maybe return some other value instead, such as 0pt, or auto itself (which could be slightly undesirable in terms of units, but could also be an acceptable alternative to the others)?

I think infinity is fine.

I think infinity is fine.

Alright! I've added this to the proposed documentation then, just in case (to avoid possible questions regarding this :p).


Error in _valid_configuration method

Add
else:     return True
if host, user and password is in config

Error fixed


Add historical_trades endpoint

The /historical_trades/{ticker_id} is used to return data on historically completed trades for a given market pair
It's possible to get everything from swap table, just define denom_a and denom_b
the structure is here
[
  {
    "id": 28457,
    "price": "4.00000100",
    "qty": "12.00000000",
    "quoteQty": "48.000012",
    "time":<PHONE_NUMBER>590,
    "isBuyerMaker": true,
    "isBestMatch": true
  }
]

"id" is msg_index field
"price" is swap_price filed (1/ swap_price in case of selling)
"base_volume" is selling coin amount
"target_volume" is buying coin amount
"trade_timestamp" is block timestamp
"type" buy or sell


use new HttpPipeline builder

closes https://github.com/Azure/azure-sdk-for-cpp/issues/626
closes https://github.com/Azure/azure-sdk-for-cpp/issues/1048
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[x] C++ Guidelines
[x] Doxygen docs
[x] Unit tests
[x] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[x] Related issue listed

[x] Comments in source
[x] No typos
[x] Update changelog
[x] Not work-in-progress
[x] External references or docs updated
[x] Self review of PR done
[x] Any breaking changes?

/azp run cpp - storage

/azp run cpp - storage

/azp run cpp - storage

@vhvb1989 I added assignment operators for ClientOptions, please review.

/azp run cpp - storage

/azp run cpp - storage

/azp run cpp - storage

/azp run cpp - storage

/azp run cpp - storage

/azp run cpp - storage


python3Packages.yangson: 1.4.8 -> 1.4.9

Motivation for this change
New release, no changelog. Just optimizations.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[x] Fits CONTRIBUTING.md.

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

12 packages built:

ansible (ansible_2_11 ,python38Packages.ansible-core)
ansible-lint (python38Packages.ansible-lint)
ansible_2_10 (python38Packages.ansible-base)
python38Packages.ansible-collections
ttp (python38Packages.ttp)
python38Packages.yangson
python39Packages.ansible-base
python39Packages.ansible-collections
python39Packages.ansible-core
python39Packages.ansible-lint
python39Packages.ttp
python39Packages.yangson


after update to Release 4.0.2 props not working...

Version
Tell us which versions you are using:

react-native-router-flux v 4.0.2 (v3 is not supported)
react-native ~0.55.2

Expected behaviour
login .js
Actions.Account_list({ data: 'test!' })
accontlist.js
console.log(this.props.data) = undefined
Actual behaviour
console.log(this.props.data) = test!

https://github.com/lordenas/reactNativeJfSerive
In the loginForm.js function myoutput() after a response is received, makes the transition to Action.Account_list({token: this.state.token, userName:this.state.userName})
But Account_list.js stopped seeing these props

Something went wrong... I went back to yesterday's version and everything worked. Somehow ceased to be transferred to the props...

I am also noticing that my props are not being populated
<TouchableOpacity
	style={_Challenges.container}
	onPress={() => Actions['ChallengeDetails'](
		{
			...props,
			challenge: challenges[i]
		}
	)}
>
    // ...
</TouchableOpacity>

Output from this.props within componentDidMount:
Object {
  "animationEnabled": false,
  "drawerImage": 2,
  "drawerPosition": "right",
  "headerMode": "none",
  "init": true,
  "name": "_ChallengeDetails",
  "navigation": Object {
    "actions": Object {
      "closeDrawer": [Function closeDrawer],
      "dismiss": [Function dismiss],
      "goBack": [Function goBack],
      "navigate": [Function navigate],
      "openDrawer": [Function openDrawer],
      "pop": [Function pop],
      "popToTop": [Function popToTop],
      "push": [Function push],
      "replace": [Function replace],
      "reset": [Function reset],
      "setParams": [Function setParams],
      "toggleDrawer": [Function toggleDrawer],
    },
    "addListener": [Function addListener],
    "closeDrawer": [Function anonymous],
    "dangerouslyGetParent": [Function anonymous],
    "dismiss": [Function anonymous],
    "dispatch": [Function anonymous],
    "getChildNavigation": [Function getChildNavigation],
    "getParam": [Function anonymous],
    "getScreenProps": [Function anonymous],
    "goBack": [Function anonymous],
    "isFocused": [Function isFocused],
    "navigate": [Function anonymous],
    "openDrawer": [Function anonymous],
    "pop": [Function anonymous],
    "popToTop": [Function anonymous],
    "push": [Function anonymous],
    "replace": [Function anonymous],
    "reset": [Function anonymous],
    "router": undefined,
    "setParams": [Function anonymous],
    "state": Object {
      "key": "id-1535028451888-41",
      "params": Object {
        "animationEnabled": false,
        "drawerImage": 2,
        "drawerPosition": "right",
        "headerMode": "none",
        "init": true,
        "panHandlers": null,
      },
      "routeName": "_ChallengeDetails",
    },
    "toggleDrawer": [Function anonymous],
  },
  "panHandlers": null,
  "screenProps": undefined,
}

I do not see challenge prop 😨

@daviscabral Any ideas where I can find the code that might be causing this within the source?

I noticed that with<EMAIL_ADDRESS>- Scenes are being rendered all together with the Stack. So, when you are really logging it - it has no params being passed to it yet, so probably, the lifecycle is wrong, and that might be probably the issue with all the recent opened tickets here. If someone here have time to help dig on that, I would appreciate.
This might be related to #3202, #3197, #3196, and a couple of others?

@daviscabral is this an issue with this library or react navigation? Maybe it's worth creating an issue in react-navigation if it is something to do with them. I'm need an app pushing out sometime today, but obviously I can't do that if navigation isn't working properly.

I need to investigate to be sure. Right now I am running late with work and might get back to it in the weekend.
What I usually do in these cases, where I have a deadline, is to fork the project I need, do my changes and install it direct from there with yarn, pointing the github repo.

@daviscabral hmm alright. My issue is that I need onStateChange which is in the latest releases. When does onStateChange get implemented into react-nativation? Maybe we could do a branch from flux's beta 27 and just introduce onStateChange into it until these issues are resolved?

I think you can fork the repo, make the changes and then use that fork. I don't think beta versions will be supported. At least I have no plans to work with that (it will cause one more version to give maintenance).

There is a ugly fix we can use until it's fixed ?

@tuxity Unfortunately I'm using the onStateChange on Router and in 4.0.0-beta.31 it doesn't have it yet. Any updates on a potential fix, @daviscabral?

Not yet - I'll try to hack something on that :+1:

@daviscabral master seems to have props working again. Perhaps the version bump for react-navigation resolved the issue?

@daviscabral Nevermind. This isn't resolved.
<TouchableOpacity
	style={_Challenges.container}
	onPress={() => Actions['ChallengeDetails'](
		{
			...props,
			challenge: challenges[i]
		}
	)}
>
    // ...
</TouchableOpacity>

👎

I switched back to 4.0.0-beta.31 and it's working again

That's because<EMAIL_ADDRESS>is used there - in the recent versions RNEF is using react-navigation@2 that has some breaking changes.

@lordenas As @daviscabral mentioned we need you to reproduce the issue based on Example project, not your project.

@aksonov We've confirmed that it's an bug with how React Native Router Flux communicates with the latest React Navigation versions

@dextermb Sorry, but I can't help you until you don't give me modified Example. So far I can't find the bug with passing props.

@aksonov, as I said, there is a problem in passing parameters.
loginpage.js
Action.Account_list({test: 'test'})
Account_list.js
console.log(this.props.test) = undefined
All this occurred after upgrading to version 4.0.2 (4.01 same problem). The props just are not transferred to the other component.

@aksonov Do you have a snack example making it easier for us to show examples?

No. PR is welcome to make Example project as Expo project.

@aksonov Seem like your app.json in the example doesn't even work with Expo without making changes to it.
Error: Missing app.json. See https://docs.expo.io/

From what I've noticed it's because you're missing required attributes.

Please re-read my sentence above again.
NO, we don't have Expo-compartible Example now. You are WELCOME to add PR and modify Example to make Expo-compartible

@aksonov Is there any documentation on how to run it without Expo? I'd rather try and get functionality working properly before converting the example to Expo

I found out a few things about the tabBar and props - but are mostly the way things works now with React Navigation.

@daviscabral Cool, I'll give it a go and let you know 💃

Do it please - just need that confirmed to proceed with the release.

@daviscabral I'll continue the discussion in the PR thread

Please check 4.0.3 release and create new ticket if any.

4.0.6 not working  either; any luck, @daviscabral @dextermb ?

Yes! I found the problem in 'Tab'.
Tabs are 'wrapped' by default - i.e. all children are wrapped by Stack with own nav bar. You may disable wrapping by using wrap={false} for Tabs and check passing props again.
<Scene key="Scene" tabs={true} wrap={false}> <Scene key="someTab" component={SomeTab} title="SomeTab" icon={TabIcon}/> <Scene key="Modal" component={Modal} title="Modal" hideNavBar direction="vertical"/> </Scene>
Here props are find when passing from someTab to Modal via Actions.Modal({someProp: theProp})

Latest version not working either - also tried with wraps={false}without luck


Agent error when using LetsEncrypt cert

I am having trouble registering a host/agent using certificates from letsencrypt.
I used the certbot to generate the certificates - and configured those into nginx - and browser is accepting the certificate with no warnings.
Rancher Version:
pre4-rc5
Docker Version:
OS and where are the hosts located? (cloud, bare metal, etc):
Ununtu 16.04
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher, Nginx ssl proxy
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Steps to Reproduce:
Results:
INFO: docker info: Total Memory: 7.784 GiB
INFO: docker info: Name: dev01.local.lan
INFO: docker info: ID: xxxxxxxxxx
INFO: docker info: Http Proxy:
INFO: docker info: Https Proxy:
INFO: docker info: No Proxy:
INFO: Attempting to connect to: https://xxxx.xxxxxxxxxx.dk:5001/v1
INFO: https://xxxx.xxxxxxxxxx:5001/v1 is accessible
Traceback (most recent call last):
File "./resolve_url.py", line 9, in
r = requests.get(url)
File "/usr/local/lib/python2.7/dist-packages/requests/api.py", line 70, in get
return request('get', url, params=params, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/api.py", line 56, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 475, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 596, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/adapters.py", line 497, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)
curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information
ERROR: returned
ERROR: --- START ---
ERROR: --- END ---
ERROR: Failed to load registration env from CATTLE_URL=https://xxxx.xxxxxxxxxx:5001/v1 ENV_URL=
ERROR: Please ensure the proper value for the Host Registration URL is set
Expected:
Agent registers with Rancher

Closing due to inactivity.

I have the same problem.

Usually this is due to incorrect proxy config (missing intermediate or wrong order), if you believe this is an issue in the agent, file a new issue with the used versions of all components, and the configurations so we can take a look and reproduce.


DisplayUtilityAssociations: AddAssociations is called twice during initialization

DisplayUtilityAssociations: AddAssociations is called twice during initialization
AddAssociations is called once in private async Task Initialize and then again in private void OnNavigationCompleted:
https://github.com/Esri/arcgis-runtime-samples-dotnet/blob/b6d103e48c8992769e999a84d7af93489c21ffc6/src/WPF/ArcGISRuntime.WPF.Viewer/Samples/UtilityNetwork/DisplayUtilityAssociations/DisplayUtilityAssociations.xaml.cs#L135
https://github.com/Esri/arcgis-runtime-samples-dotnet/blob/b6d103e48c8992769e999a84d7af93489c21ffc6/src/WPF/ArcGISRuntime.WPF.Viewer/Samples/UtilityNetwork/DisplayUtilityAssociations/DisplayUtilityAssociations.xaml.cs#L145

@ZackAllen @duffh


Intensity encoding function changed for Perseverance since Sol 511

Hi Kevin,
since Sol 511 I noticed a different intensity transfer function in use for the image data in the PNGs on https://mars.nasa.gov/mars2020/multimedia/raw-images which most likely need an adaption for the mars-raw-utils in case it isn't a bug in the original PNGs. The change is visible in Mastcam, Navcam, Hazcam.
Example, comparing the sundial calibration target at similar solar time on Sol 510 and 512 with identical clear sky light conditions:
mru m20-fetch -c MCZ_LEFT -s 510 -S CAM03014 -o /tmp
mru m20-fetch -c MCZ_LEFT -s 512 -S CAM03014 -o /tmp
mru calibrate -P m20_zcam_ilt -i /tmp/ZL0_0510_0712219006_707ECM_N0261222ZCAM03014_048085J01.png
mru calibrate -P m20_zcam_ilt -i /tmp/ZL0_0512_0712391417_394ECM_N0261222ZCAM03014_048085J01.png

Results uploaded:
https://areo.info/mars20/files/ZL0_0510_0712219006_707ECM_N0261222ZCAM03014_048085J01-rjcal-ilt.png
https://areo.info/mars20/files/ZL0_0512_0712391417_394ECM_N0261222ZCAM03014_048085J01-rjcal-ilt.png
From looking at the histograms in the original PNGs I assume the data has been converted to match the sRGB intensity function since Sol 511. Or the inverted camera-LUT1, the squareroot encoding has been applied. There is also a low chance that a different LUT already on the rover is applied, but from the appearance of the histogram I assume sRGB.
What do you think? Can you contact the Perseverance web team to ask them what happened?
Holger

I did notice this. At first I thought it might be a different sun angle causing blooming in the optics, but now I'm not so sure. I'll ask around and see what's up.

It's definitely a different encoding used now. I noticed it first on the Navcam full frame images on my own automated website https://areo.info/mars20 as those showed completely different colors due to the stronger effect with my color processing and non-linear intensity change to improve contrast. Then checked out the details and also Hazcam and Mastcam are all different starting with Sol 511. WATSON doesn't appear to be affected, but I haven't checked all details there yet.

Looks like there was a pipeline update around the same time as when this started which may be the culprit. I don't presently have access to the EDRs, so I'm not sure yet what the issue/change was.

Any news on this? Is it planned to stay that way? There is also a chance that the new web PNGs are the original Earth-received 8 bit files (ECM in the PDS). That would even increase the quality after decoding to 12 or 16 bit. But there is also a chance that by error an sRGB intensity function was applied as both are quite similar, though not identical.

I figure it's a difference in how they're computing the values needed to convert from the sensor values to the 8 bit PNG range.
The images have been posted in their 8 bit EDR format since the beginning. This is before any LUT conversion back to 12 bit (within a 16 bit buffer) or other calibration. Non-mission members don't generally see the calibrated stuff until it hits the PDS archive.

Thanks for the update! Good to hear that it was the Earth-received 8 bit data before. Most likely for the web-published PNGs then in addition linearly stretched to full intensity, but that's easy to compensate. The current format has the advantage not needing to guess the used 12-to-8 bit LUT of the 32 possible on the camera, but has the disadvantage that the quality (dynamic range) is reduced as the web PNGs are only 8 bit and the real EDR data 12 bit. As for most images after the first few sols LUT#2 is selected, the LUT-guessing problem doesn't really exist in practice.
If they switch the LUT in the next days for some time, then it will be an interesting experiment actually to keep it this way for some days, as it may be the case that some other LUT surprisingly increases the quality. I saw some hints for that in the first 2 Sol weeks. That's counterintuitive, but if you look at the images it's visible.

Have you heard any news on this? What was on the processing level changed? From your previous message I interpret it that now the fully companded images are shown but linearly scaled down from 12 to 8 bit? Fully-companded = 12 to 8 bit applied on rover and 8 to 12 bit applied after receiving on Earth.
But if that's the case: Why is the result still different when comparing it to previous sols? I only get a similar result when applying the sRGB gamma function and then the 8 to 12 iLUT.

With the new PDS raw data release of today I can confirm my previous assumption about the changes in the web-PNG production pipeline. The sRGB intensity curve is indeed now applied, that means gamma 2.2. I could confirm that by comparing the web-PNGs and raw camera JPGs (EJP files in the PDS) for the following 2 Navcam images from sol 508 and 511:
https://areo.info/mars20/ecams/0508/tn/NLF_0508_0712035900_230ECM_N0261222NCAM00501_01_295J_calib01_areo.info.jpg.html
https://areo.info/mars20/ecams/0511/tn/NLF_0511_0712320966_273ECM_N0261222NCAM00501_01_295J_calib01_areo.info.jpg.html
Results from my analysis about the JPL production pipeline for the web-PNGs on https://mars.nasa.gov/mars2020/multimedia/raw-images :

Sol 510 and before: read raw Navcam JPG (EJP data), cut off lowest 10% and highest 90% intensity, write PNG
Sol 511 and later: read raw Navcam JPG (EJP data), apply sRGB intensity curve (gamma 2.2), then cut off lowest 10% and highest 90% intensity, write PNG

I suspect just a bug in their processing pipeline. That can easily happen when reading linear RGB JPGs, like the Navcam-produced JPEGs on the rover are, with the imagemagick convert tool or also Python image loaders. For imagemagick that can be avoided by using for example convert INPUT -set colorspace RGB -colorspace RGB OUTPUT. That overwrites the default assumptions of sRGB and sets fixed to linear RGB.

OK, thank you. I just added some additional steps in the M20 navcam calibration to deal with it. Also adds a pair of calibration profiles that'll need to be copied into ~/.marsdata

Resolved in M20  pipeline


OpenSearch does not perform a rolling restart after a version update

I have two clusters with OpenSearch version 2.9.0 deployed via OpenSearch Operator. I tried updating sequentially from 2.9.0 to 2.10.0 and then from 2.10.0 to 2.11.0. I fixed the version in the opensearchclusters CRD and the update from 2.9.0 to 2.10.0 went through without problems, OpenSearch Operator itself did a rolling restart of all pods in the cluster. I have three types of node pools: hot, warm and masters, all three were sequentially updated starting with the last pod in the pool. However, I ran into a problem with the sequential update from 2.10.0 to 2.11.0. On both clusters it only updated a few pods from one node pool and then stopped. I waited quite a while, half an hour in the first case and 20 minutes in the second, the update never continued. So I had to manually restart the pods and they successfully showed version 2.11.0. I assume there is a problem with the update, but I don't know what logs to look at. Since events didn't show anything useful, and the logs of the operator itself don't contain anything at all.
Environment:

Azure K8s Service (AKS) version 1.26.6 with Ubuntu nodes version 22.04
OpenSearch Operator deployed by Helm chart version 2.4.0

Thank you for sharing those.
In this kind of issue it would be good to take a look into more details of the cluster and the issue, we recently solved a bug on rolling restart and there's also an open issue where we're discussing an invalid state due to a race condition, where operator requires cluster status green but to fix the cluster status we must proceed with the rolling restart.
Would you still have and are able to share more details, like logs and metrics, from cluster, operator and pods?

Yes, of course, I'll share any information you need.
The thing is, the update worked fine from version 2.9.0 to 2.10.0 and the cluster was in GREEN state. After that I started to update from 2.10.0 to 2.11.0.

Hi @kinseii.
During an upgrade there are two points that can provide useful information:

Operator logs (did you make sure to choose the operator-controller-manager container from the operator pod when getting logs?), these should have some information what the operator is doing and also if it thinks it cannot continue the upgrade
CR Status (kubectl describe opensearchcluster xxx will show at the end a componentstatus that reports a bit on the state the operator is in with regards to restarts and upgrades).

Can you provide both of these? Also, could you retry the upgrade to see if it happens again?

Hi everyone, the new version 2.11.1 came out today and I upgraded to it. Dashboards restarted, but OpenSearch itself did not.

K8s events:
service     2m55s       Normal    Killing                pod/opensearch-cluster-dashboards-5f6f8ddc78-4bvqn    Stopping container dashboards
service     2m55s       Normal    SuccessfulDelete       replicaset/opensearch-cluster-dashboards-5f6f8ddc78   Deleted pod: opensearch-cluster-dashboards-5f6f8ddc78-4bvqn
service     3m35s       Normal    Scheduled              pod/opensearch-cluster-dashboards-66795bfdb5-kzclt    Successfully assigned service/opensearch-cluster-dashboards-66795bfdb5-kzclt to aks-sd16adsv5p1-10131949-vmss00000q
service     3m35s       Normal    Pulling                pod/opensearch-cluster-dashboards-66795bfdb5-kzclt    Pulling image "docker.io/opensearchproject/opensearch-dashboards:2.11.1"
service     3m16s       Normal    Pulled                 pod/opensearch-cluster-dashboards-66795bfdb5-kzclt    Successfully pulled image "docker.io/opensearchproject/opensearch-dashboards:2.11.1" in 19.734829436s (19.734838103s including waiting)
service     3m16s       Normal    Created                pod/opensearch-cluster-dashboards-66795bfdb5-kzclt    Created container dashboards
service     3m15s       Normal    Started                pod/opensearch-cluster-dashboards-66795bfdb5-kzclt    Started container dashboards
service     3m36s       Normal    SuccessfulCreate       replicaset/opensearch-cluster-dashboards-66795bfdb5   Created pod: opensearch-cluster-dashboards-66795bfdb5-kzclt
service     3m36s       Normal    ScalingReplicaSet      deployment/opensearch-cluster-dashboards              Scaled up replica set opensearch-cluster-dashboards-66795bfdb5 to 1
service     2m55s       Normal    ScalingReplicaSet      deployment/opensearch-cluster-dashboards              Scaled down replica set opensearch-cluster-dashboards-5f6f8ddc78 to 0 from 1
service     6m41s       Normal    RollingRestart         opensearchcluster/opensearch-cluster                  Starting to rolling restart
```

I see that the operator wrote about rolling restart, but nothing happens, the pods are not recreated one by one.

I see that everything is working, I apologize for the false alarm, I'm closing the issue.
opensearch-cluster-dashboards-66795bfdb5-kzclt            1/1     Running   0               88m
opensearch-cluster-hot-nodes-0                            1/1     Running   0               27m
opensearch-cluster-hot-nodes-1                            1/1     Running   0               31m
opensearch-cluster-hot-nodes-2                            1/1     Running   0               33m
opensearch-cluster-masters-0                              1/1     Running   1 (7m41s ago)   35m
opensearch-cluster-masters-1                              1/1     Running   1 (23m ago)     37m
opensearch-cluster-masters-2                              1/1     Running   1 (8m33s ago)   41m
opensearch-cluster-warm-nodes-0                           1/1     Running   0               24m
opensearch-cluster-warm-nodes-1                           1/1     Running   0               30m
opensearch-cluster-warm-nodes-2                           1/1     Running   0               33m
opensearch-operator-controller-manager-6db98c48c4-zfdkk   2/2     Running   6 (156m ago)    2d13h


[bug]: restart tapd will reset  FedGlobalSyncConfig when with the --universe.public-access flag.

Start tapd with the --universe.public-access flag.
Modify the settings accordingly.
Restart tapd.
The FedGlobalSyncConfig will be reset to its initial values. And then tapd will cost a long time and cpu to sync assets from lightning labs's universe
To prevent this, I suggest implementing an initialization check in server.go.
	if s.cfg.UniversePublicAccess {
		err := s.cfg.UniverseFederation.SetAllowPublicAccess()
		if err != nil {
			return fmt.Errorf("unable to set public access "+
				"for universe federation: %w", err)
		}
	}

Thanks for the report

Restart tapd
When the tapd daemon is started for a second time (the restart), is the --universe.public-access flag being set?

yeah, --universe.public-access flag is being set.

Ran into this myself, pretty annoying.
Here's a suggestion on how to resolve this:

Separate the config for allowed actions to your own personal universe server vs how to sync with a remote universe server.
The existing args stay, these govern your own personal universe server. When you do --universe.public-access, this means that you let people both read from your server, and also insert new proofs into your server.

By default with this, you won't actively sync all records from a remote/default universe server.

* We add a new set of flags to govern how _sync_ works. The default is sync nothing. You can add `--universe.sync-all-assets` to indicate you want to attempt to sync any universe root you can find. Today we have `import`, and `export`. This adds a third option: `sync`.
* In the auto syncer, when we go to sync, we'll look at this flag to see if it should be done at all. If so, then we look at the global or local flags to determine _what_ to sync.


allow to not delete buffer

The autoclose is interesting, but I rather not have the content of quickfix lost on close, maybe an option to disable delete will be interesting

Thank you for your comment.
Do you want to enable/disable the autoclose function later? Or do you prefer commands such as :EnableQFC or :DisableQFC in the command line?
Instead of setting it initially, if you want to configure it later, I can prepare specific commands for that. What do you think?

@akabakass
Is the function in #8de0a0712a28d128a7aea4b8945f6c2bc87da13e in addCmd branch what you were looking for? I have added user commands that allow us to switch the enabled option at any time.

oh sorry i mis-explained, though this is neat to have ;)
when the autoclose happen, it will empty the quickfix list at the same time, but i'd like to keep the content of it instead. i was thinking something like this:
{
      timeout = 3000,   -- Timeout setting in milliseconds
      enabled = true, -- Enable/disable autoclose feature
      empty_list_on_close = false -- empty quickfix list when autoclose
}

please tell me if i'm not clear, english is not my language

I think I understand what you mean. You want the quickfix (qf) window to auto-close when the qf list is empty and the window loses focus, but to remain open when there are items in the qf list.
When I originally created this plugin, my goal was to auto-close the qf window regardless of whether its list was empty or not, because in my coding style, having the window remain open was an obstacle :<.
However, your suggestion is useful, and I will consider how to implement it. If you can implement this, I would look forward to your PR!

Nevermind, I think it was a bug and is fixed now, I don't see the problem anymore
Thx


instution appear twice on submission

When you click on add authors then "instutions" appear twice.

fixed with https://github.com/okulbilisim/ojs/commit/b26fa23162ac3777617060232ac2300537b50e3f


An error occurred while fetching inputs: TypeError: Cannot read properties of null (reading 'join')

Hello,
my homebridge log is full with that error:
An error occurred while fetching inputs: TypeError: Cannot read properties of null (reading 'join')
How to fix that?

@mensa84 Hello and thanks for reporting this! This error usually indicates that there is something wrong with the configuration of your TV. Are you able to perform actions on your TV and see the state via Home?

I see the correct state, but turning off or on does not work.
I am on Debian Linux. Must i install netifaces for newest release? Cause apt install netifaces does not work.

RemoteNow App from Hisense works without problems.

The newest release needs netifaces, yes: on Debian it should be available in the default repo:
apt install python3-netifaces

If you're unable to control the state of the TV, I can assume something is wrong in the configuration. Are you able to send command using the Python script directly?

You are right, thanks! The command line scripts also did not work anymore cause due to the update the ssl files were deleted from /usr/lib/node_modules/homebridge-hisense-tv-remotenow/.
Is this normal behavior? Where do you suggest to store that ssl files to not get deleted by an update?

@mensa84 unfortunately, yes, but it's out of our hands. When npm (the package manager that Homebridge uses to install plugins) finds a new version, the entire folder is deleted and replaced with the version that's on the repo.
You can put your certificates anywhere else, outside of the /usr/lib/node_modules folder. The important thing is that wherever you move them, they are still readable from the Homebridge user.
I'll add this to the README file.

I have created following subfolder in the homebridge directory:
/var/lib/homebridge/hisense-ssl
Do you think this is a good idea and will survive all updates?

Is /var/lib/homebridge the folder where also the config.json file of Homebridge is? In that case, yes.

Yes, it is that folder.

Then it should be fine, because updates of Homebridge usually don't override the config.json.


A694379226563213 transferring

Add tests for transferring
Depends on:

https://github.com/openprocurement/openregistry.lots.core/pull/51

Coverage decreased (-0.4%) to 97.933% when pulling 36fcd69e6326687747c7acf2cb945fc66fb0aabf on Scandie:a694379226563213_transferring into 849e46c52297a59dd672ce1fe26671ca4a62bb75 on openprocurement:master.


MAINT: Centralize creation of QApp

Currently this uses mkQApp from pyqtgraph, then sets icon, etc. And in #22 more Qt stuff is done regarding QSettings. Ideally we should use a single shared function in MNE-Python for creating a Qt application, deduplicating with
https://github.com/mne-tools/mne-python/blob/bdedc788b79f7b620167ba6358965ce312ec51be/mne/viz/backends/_pyvista.py#L90-L103
(NB: I think our other Qt application iEEG GUI gets this for free by using https://github.com/mne-tools/mne-python/blob/bdedc788b79f7b620167ba6358965ce312ec51be/mne/gui/_ieeg_locate_gui.py#L154-L155, but that doesn't really apply here)

I agree, something like _init_qt_app in mne.viz.utils, right?
For QSettings to work, the app-name and app-organization need to be set (the os-dependent stored file will then be named accordingly).
WDYT about:
name = 'MNE-Python'
organization = 'MNE'

Sounds good to me

Would there be a way to properly populate the menu bar on macOS too? By default, it just says "python", which is not very helpful. @cbrnr solved this in MNELAB but I believe it wasn't really trivial?

It is trivial, you need to install pyobjc-framework-Cocoa and set a value accordingly (https://github.com/cbrnr/mnelab/blob/main/mnelab/init.py#L21-L26).

It is trivial, you need to install pyobjc-framework-Cocoa and set a value accordingly

Thank you @cbrnr. Would it be ok if I copied here how you have done it?

Of course!


Add true mini-timer

The idea is to add a small borderless always-on-top window that is nothing more but the current timer. It could be used to quickly start/stop the timer, and enter basic information.
For editing the running time entry, the app would still open.
(A user suggested this recently, and it might also fulfil the need of other users to have the timer show in the task bar.)
The user should be able to drag the window around pretty much anywhere on it, and maybe should even be able to resize it to some degree (to make it very very small, if needed).
This is probably quite easy to do. I might do it just as an experiment to see if we like it.

Basic stuff is implemented on win-mini-timer.
Still missing/to be fixed:

[ ] save window size to database

[ ] add setting to context menu

[ ] save to database

[ ] snap to screen borders
[ ] enable main window shortcuts
[ ] fix context menu positioning (copy manual code from main window)
[ ] make main window not show on timer start (causes OnApp(true) event)

And possibly more.

All critical features are implemented.
Only things remaining are polishing. Creating new issue for that.


Improve documentation for Content Asist

Could someone please improve documentation/guide for how to use content assist.
I'm trying to use it with a language extension for Visual Studio Code.
I don't see that the guide page for syntactic content assist provides any useful information for how to use or implement it or even understand the API or underlying concepts.
Like for starters, what is the symbolTable (list of available symbol names.)
I've looked at the spec (test) file, and it just lists some random identifiers like foo and bar.
describe("The Official Content Assist Feature example Example", () => {
    const symbolTable = ["foo", "bar", "average"]

    context(
        "can perform content assist for simple statements parser (K > 1) for inputs:",
        () => {
            it('Text: "public "', () => {
                const inputText = "public "
                const suggestions = getContentAssistSuggestions(
                    inputText,
                    symbolTable
                )
                expect(suggestions)
                    .to.have.members(["static", "enum", "function"])
                    .and.to.have.lengthOf(3)
            })

The function doing the magic suggestions...
After some further research I notice in the example code at the top, it contains these hints

Examples:
"Public static " --> ["function"]
"Public sta" --> ["static"]
"call f" --> ["foo"] // assuming foo is in the symbol table.

Further down in the spec file, I finally see a more useful test which "links" the symbol table with the inputText and suggests the closest matching symbol. Sweet :)
Would love to see this documented in the guide!
            it('Text: "call aver"', () => {
                const inputText = "call aver"
                const suggestions = getContentAssistSuggestions(
                    inputText,
                    symbolTable
                )
                expect(suggestions)
                    .to.have.members(["average"])
                    .and.to.have.lengthOf(1)
            })

Cheers!

Yes I agree that a section demonstrating the actual API usage is missing.
Regarding the Symbol Table:
It is emphasized in the docs/example that Chevrotain only provides syntactic content assist.
These symbols are  a "simulation" of the available names in the current scope that could
be filtered to provide suggestions when the next possible Token is an Identifier.
Each compiler author would have to implement such a symbol table themselves depending
on their language scoping/visibility rules.
Perhaps another comment on the dummy symbol table is appropiate
and the missing doc section regarding usage could show a switch/case on the
suggested next tokens with special handling for Identifiers.


Can't resolve dependency

Getting "Could not find com.androidessence:recyclerviewcursoradapter:1.0.0." when compiling now. Looks like it's not hosted anymore :( Any chance you could throw it back up on jcenter? This adapter has been a lifesaver!

I can also just import it manually if you're over maintaining it :)

Ya.. I am facing the same issue.. :(

Sorry all! I am not sure why this happened. I have resubmit the jcenter request. In the mean time, you can also reference my maven repository in your build.gradle file and that should resolve the issue, because it is in my bintray account still:
    repositories {
        maven {
            url  "http://dl.bintray.com/androidessence/maven"
        }
    }

@SureshCS-50 @bblia
Just got an email from Jcenter, it should be good again, worked for me. Closing ticket, feel free to reopen if you're still seeing issues.

@AdamMc331 thank you!

No problem! So sorry I didn't see your original messenger in September, I'm glad bblia commented this morning to bring it to my attention. I'm glad this is working for you, and let me know if there are any other ways I can improve it!

after i commented I actually ended up just forking it locally, but if i ever end up making changes i'll definitely pull request! Thanks for writing this, it was a huge help.

Of course! I wrote it because I was in demand for it myself, and then it just got away from me. I haven't touched my other project in a while, so I never caught this issue hahaha.


Fatal Error

After installing and configuring the module, I got the below error on
yarn run dev or yarn run build
Nuxt v2.6.3
FATAL  The 'request' argument must be string. Received type undefined                                                                                20:57:54
at node_modules/esm/esm.js:1:220358
at Module. (node_modules/esm/esm.js:1:289859)
at Resolver.n [as esm] (node_modules/esm/esm.js:1:273820)
at Resolver.requireModule (node_modules/@nuxt/core/dist/core.js:624:31)
at ModuleContainer.addModule (node_modules/@nuxt/core/dist/core.js:164:36)
at promise.then (node_modules/@nuxt/utils/dist/utils.js:1790:43)

Hello! What is nuxt version are you using?

https://codesandbox.io/s/r1o71w59lq
Everything works

it turns out that Nuxt recaptcha-module causing the error error.

How did you fix this? @Dahdoul
I'm encountering same issue with other modules

@Ramarti try to delete node_modules and .nuxt and run yarn/npm  again.
for me I had to remove nuxt recaptcha entirely to be able to continue working on the project, I will install it later on and see if the problem was fixed.

The project works when I comment out that entry in the modules array of nuxt.config.js
Problem is, I do need this ( https://github.com/nuxt-community/nuxt-i18n ) to work now.
Seeing the same error in another module makes me think nuxt changed something in the way it adds modules and some modules have not updated yet, maybe?
Anyway, I hoped recaptcha-module fixed it so I can port it to nuxt-i18n or something.
I can't find that 'request' argument in requireModule in nuxt core, pretty lost

@Ramarti I tried to look for request too but with no hope, as you said it might be something changed in  nuxt core and modules need to update accordingly


channels in search should be sorted by activity

Summary
Search box for channels and private messages should show them using last activity order (like it is on desktop and web)
Right now alphabetical order is shown.
This is especially painful when you have old conversations with person with name starting with "A". I have several inactive users starting with A, so conversations with them are shown on the top of the list. Which makes me scroll a lot :)
Environment Information

Device Name: Iphone 13
OS Version: IOS 15.7
Mattermost App Version: 1.55.1
Mattermost Server Version: 7.2

Steps to reproduce

open mobile app on ios
tap on the "Find channel" input field

Expected behavior
Direct messages and channels are shown in "last activity" order.
Observed behavior (that appears unintentional)
Direct messages are shown in alphabetical order.
Possible fixes
If you can, link to the line of code that might be responsible for the problem

Hi @tmotyl, I'd encourage you to opt-in to our beta program to try the Mobile app v2.0 where we've resolved this:  https://mattermost.com/blog/mobile-beta-program-v2/

Thanks @esethna! the beta app works fine. No issues so far (ios)


RUMM-3194 add tracer sampling rate

What does this PR do?
Adds a sampling rate for local traces. The sampling will be applied automatically to the root span if it's not set manually on it.

Codecov Report

Merging #1393 (2edc280) into develop (a3f9c38) will decrease coverage by 0.04%.
The diff coverage is 90.00%.

@@             Coverage Diff             @@
##           develop    #1393      +/-   ##
===========================================
- Coverage    82.00%   81.96%   -0.04%
===========================================
  Files          363      363
  Lines        13015    13021       +6
  Branches      2188     2188
===========================================
  Hits         10672    10672
- Misses        1683     1684       +1
- Partials       660      665       +5

Impacted Files
Coverage Δ

...og/trace/common/sampling/RateByServiceSampler.java
56.52% <66.67%> (-4.35%)
:arrow_down:

...ava/com/datadog/trace/common/sampling/Sampler.java
28.57% <100.00%> (ø)

...otlin/com/datadog/android/tracing/AndroidTracer.kt
93.81% <100.00%> (+0.41%)
:arrow_up:

... and 13 files with indirect coverage changes


Adding missing release notes needed to have this PR merged

This PR adds the release notes required here

@remi-gelinas


Unpin protobuf3_8 in multiple places

Relates to #193370
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

4 packages failed to build:

python310Packages.elegy
python39Packages.elegy
rippled
rippled-validator-keys-tool

12 packages built:

emacsPackages.ac-mozc
emacsPackages.mozc
emacsPackages.mozc-cand-posframe
emacsPackages.mozc-im
emacsPackages.mozc-popup
emacsPackages.mozc-temp
ibus-engines.mozc
python310Packages.coqui-trainer
python310Packages.tensorboardx
python39Packages.coqui-trainer
python39Packages.tensorboardx
tts


autoform.omit doesn't seem to work

I have the following field in my schema:
  notes: {
    type: String,
    label: 'Admin Notes',
    optional: true,
    autoform: {
      omit: function(){
        return !_.contains(Meteor.user().roles, 'admin');
      }
    }
  }

I have checked that the omit function returns false for admin and true for everyone else but the field is still always visible to everyone, what could be the reason?

I can confirm this is still not working in v6.3.0. The function is executed, but the result seems to be ignored.


Update requests to 2.74.0

tough-cookie contains a vulnerability. request depend on tough-cookie, so we need request => 2.74.0 to get the fix. See https://nodesecurity.io/advisories/130.
It would be really good to merge this and release as soon as you can. Thanks.

[Current coverage][cc-pull] is 79.33% (diff: 100%)
[][cc-pull]

No coverage report found for master at add9424.

Powered by Codecov. Last update [add9424...78d5568][cc-compare]
[cc-base-branch]: https://codecov.io/gh/cainus/codecov.io/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/cainus/codecov.io/compare/add94246740ec9c46dfbc5b08623d9071562c103...78d5568d5ca7352edf6bbc5418448f84bb60fd9c?src=pr
[cc-pull]: https://codecov.io/gh/cainus/codecov.io/pull/35?src=pr

Any chance to get this merged?

Hey @holm this package is replaced by codecov/codecov-node and will be removed shortly. May I ask that you try the new package?


Run integration tests in CI

Run integration tests (make test-mysql) in our CI build, which we had previously not been doing
Also fixes our coverage reports, and updates README coverage badge to be Coveralls instead of Codecov.

Changes Unknown when pulling<PHONE_NUMBER>1a952551bc0b56701c0d378716a353 on ethantkoenig:ufw/ci into ** on unfoldingWord-dev:develop**.

Changes Unknown when pulling 8ca6602873d8cc0a8fd697d9059a81da28cf0b69 on ethantkoenig:ufw/ci into ** on unfoldingWord-dev:develop**.


Race condition between create_snapshot and read_logical_snp_obj

Hi!
In my state machine implementation, I'm always using the single latest snapshot. I've encountered the following case:
2021.05.05 21:35:46.899607 [ 1861 ] {} <Information> RaftInstance: creating a snapshot for index 1100
2021.05.05 21:35:46.899616 [ 1861 ] {} <Information> RaftInstance: create snapshot idx 1100 log_term 1
2021.05.05 21:35:46.899634 [ 1861 ] {} <Debug> KeeperStateMachine: Creating snapshot 1100
2021.05.05 21:35:46.899668 [ 1861 ] {} <Debug> KeeperStateMachine: In memory snapshot 1100 created, queueing task to flash to disk
2021.05.05 21:35:46.900040 [ 1861 ] {} <Information> RaftInstance: create snapshot idx 1100 log_term 1 done: 411 us elapsed
2021.05.05 21:35:46.922391 [ 1862 ] {} <Debug> RaftInstance: send snapshot peer 3, peer log idx: 465, my starting idx: 991, my log idx: 1104, last_snapshot_log_idx: 1000
2021.05.05 21:35:46.922406 [ 1862 ] {} <Debug> RaftInstance: previous sync_ctx exists 0x7f9eccdcf418, offset 1, snp idx 1000, user_ctx (nil)
2021.05.05 21:35:46.922417 [ 1862 ] {} <Debug> RaftInstance: peer: 3, obj_idx: 1, user_snp_ctx (nil)
2021.05.05 21:35:46.922428 [ 1862 ] {} <Debug> KeeperStateMachine: Reading snapshot 1000 obj_id 1
2021.05.05 21:35:46.947817 [ 1855 ] {} <Debug> KeeperStateMachine: Created persistent snapshot 1100 with path /home/robot-clickhouse/db/coordination/snapshots/snapshot_1100.bin
DB::Exception Required to read snapshot with last log index 1000, but our last log index is 1100, Stack trace (when copying this message, always include the lines below):

Thus, the leader server already finished creating 1100-idx snapshot, but was requested to read 1000-idx snapshot. What can we do in this case? Seems like the return code of read_logical_snp_obj is ignored in the library code.

https://github.com/eBay/NuRaft/pull/213
Realized that returning 0 is used for successful cases in example and test codes (the description was incorrect). You should return a negative number to inform the read failure.

Thanks.


⚠ Bofrost.nl has degraded performance

In 593d9d5, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1891 ms

Resolved: Bofrost.nl performance has improved in 254857e after 6 minutes.


Update EFCircularSlider.podspec and add initialization from storyboard with IB_DESIGNABLE

Fix issue #38

Can anyone merge this?

I have added initialization from storyboard with IB_DESIGNABLE.


Ambassador application - Gabor MARKON

Email
<EMAIL_ADDRESS>Bio
See my LinkedIn site: https://www.linkedin.com/in/gabor-markon-79133220/
Projects within OMP you would want to be an ambassador for
Mentorship Program - that's what I do already within my organization, but I am open to other directions as well
ZOWE - I suppose I am able to support in areas like Rexx and Java
List any other topics you would be able to speak about
Mainframe migration - why good, why bad
Why do you want to be an ambassador?
To support my company and the community to keep the mainframe alive on a long term.
Attach a headshot
[](url

)

Contact made.  Communication begun.

Hello Kip,
I am responsible for the Mainframe Academy training in our organization Deutsche Telekom / Hungary branch.
I'll complete this today, then make a one-week holiday. Then our students make a test, I'll evaluate this in a week, and then I am ready to communicate (3rd March week ca.). Thank you for your understanding!


Fix panics when stopping server

Two different panics could occur if in-flight writes or queries were running on the server when the server started to shutdown.  The problem was that lower level services were closed before the higher level ones were.  The cluster service was also not waiting for connections to complete before returning from Close.
Fixes #3848 #3881

+1, small nit.


Modelica2017 Added text for embedded targets

Too much technical detail?

You might want to introduce and use the abbreviation MCU (for microcontroller unit).


fix: Correct alert manager default definition

Description

Correcting alert manager default definition - indentation
update precommit version following pre-commit autoupdate

Motivation and Context

post https://github.com/terraform-aws-modules/terraform-aws-managed-service-prometheus/pull/3 , seeing same failures "Malformed Alertmanager definition" , using version 2.1.2

Breaking Changes

How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[ ] I have executed pre-commit run -a on my pull request

This PR is included in version 2.1.3 :tada:


Not updating after a dispaching

I've integrated Realm with Redux on my app. Each time I do an action I want to register in the database I call to an action with dispatch, save on Realm and return the new information to the reducer. It works correctly. I have already subscripted to the changes on the screen I want to the data has been update.
So, the problem is the next. I'm in a secondary view where I do a booking. In this view, the state updates correctly and the view changes too. But in the main view (where I've donde the subscription) the data doesn't update. The subscription callback is launched, I know it because I put a console.log and the redux store has the correct info, but when I set the new date state, the view doesn't re-render although the state has the correct data too.  I don't know why happens this.
const [bookings, setBookings] = useState(store.getState().booking.bookings);
const unsubscribe = store.subscribe(() => {
console.log('update');
setBookings(store.getState().booking.bookings);
});
I've done everything, with a UseEffect hook, without it.

The issue tracker here on GitHub is reserved for bug reports and feature requests. For usage questions (which is what I believe this is), please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!
Please feel free to reply if you think this issue was closed prematurely.


Problems when adding google account to gdrive

After being redirected to http://localhost:8085 and completing the setup locally, The message in the web server is:

(Success) You may now close this window.

But after several minutes the terminal returns
Error: Failed to get access token: error trying to connect: tcp connect error: Operation timed out (os error 110)
In the end, the account has not been added. What's the problem? Thanks.

some issue, please help @holtzermann17 @prasmussen

what OS are you on?

the only thing I can currently think of is an over-restricted firewall

@Christian-chen1206 Same issue, any new progresses?

I guess the problem is caused by the GFW, but I don't know why VPN is unhelpful locally.


[Feature Request] Button enbaled/disabled state for Card Buttons

Hi,
I have been extensively using cards and I noticed that once the conversation is finished, the buttons on the card still remain active. There should be a way for the developer using Bot Framework to disable/enable buttons through code or set an active time on the buttons for a particular Card.
My main issue occurs because I am using Imback with buttons, and once my user moves to another state, and still goes back to the conv and clicks on the previous card, I receive an imback message. It would have been great if I could disable the buttons on the prev card so as to avoid this.
Regards,
Rohan

This is a limitation of the channels - none of which currently support an active / inactive buttons states.  When they do, we will add that support to bot framework.   Some channels have recently added the ability to edit posts (i.e. Telegram & Facebook).  This allows you (among other things) to delete buttons. Work to support this is on our road map.
In the mean time, a number of channels support keyboards (i.e. Telegram, Kik, Facebook) which are buttons that disappear after they have been pressed.  On those channels you can use a keyboard instead of a button.

Hi Lars, I know this is an old post but do you know if this has been implemented in your road map?
The following statement:
"This is a limitation of the channels - none of which currently support an active / inactive buttons states. When they do, we will add that support to bot framework. Some channels have recently added the ability to edit posts (i.e. Telegram & Facebook). This allows you (among other things) to delete buttons. Work to support this is on our road map."


Retyped.dom MutationObserver API should be improved

Expected: constructor of MutationObserver should take callback method as a parameter.
Actual: MutationObserver required an instance of a class with Self method.
Workaround: create Action<X,Y>, cast to object, recast to that special class
Edit: moved to https://github.com/Retyped/Retyped/issues/51

Created #51


HIVE-28046: Using serdeConstants fields instead of string literals for 'columns' and 'columns.types'

Using serdeConstants fields instead of string literals for 'columns' and 'columns.types'
Why are the changes needed?
to improve the use of existing constants
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?
using existing tests

cc @ayushtkn

@mlorek Can we do this for all constants defined via serdeConstants.java?

@mlorek Thanks and please consider adding incremental commits on this PR. It helps you to differentiate the different serdeConstants and help us in reviewing it as well.


chore(4.4): release 1.7.0

:robot: I have created a release beep boop
1.7.0 (2022-05-06)
Bug Fixes

handle ALB edge case (4c4b51a)

Miscellaneous Chores

release 1.7.0 (7066ae2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/GluuFederation/cloud-native-edition/releases/tag/v1.7.0 :sunflower:


fix athenz-sia.env

Description

Specify default value for binary
Provide the URL where the default value is set
Adjust the order of environment variables to match config.go

Type of change

[ ] Bug fix
[ ] New feature
[ ] Refactoring (no functional changes, no api changes)
[x] Non-code changes (update documentation, pipeline, etc.)

Flags

[ ] Breaks backward compatibility
[ ] Requires a documentation update
[ ] Has untestable code

Related issue/PR
Delete this section if there are no issues or pull requests that relate to this pull request.

Fixes #issue
Closes #PR

Checklist

[ ] Followed the guidelines in the CONTRIBUTING document
[ ] Added prefix [skip ci]/[ci skip]/[no ci]/[skip actions]/[actions skip] in the PR title if necessary
[ ] Tested and linted the code
[ ] Commented the code
[ ] Made corresponding changes to the documentation
[ ] Passed all pipeline checking

Checklist for maintainer

Use Squash and merge
Double-confirm the merge message has prefix [skip ci]/[ci skip]/[no ci]/[skip actions]/[actions skip]
Delete the branch after merge

@mlajkim added in https://github.com/AthenZ/k8s-athenz-sia/pull/43/commits/e818143cfd58c52369021ef54d1614a4695419bc


electron-forge wont make a Darwin package and gets stuck. is it a mac only feature?

I've tried this with two different mac packagers. one for mas and the other for Darwin. yet for whatever reason whenever i try to package the project it installs the mac dependencies and then gets stuck on preparing to package application for arch: x64.
the command in question I am using is electron-forge package --platform=darwin. when I packaged for windows it worked surprisingly quickly and the packaged build was functional. but when I do the same for Darwin or mas it gets stuck with a log looking like this
√ Checking your system Downloading electron-v11.1.1-darwin-x64.zip: [=================================================] 100% ETA: 0.0 seconds / Preparing to Package Application for arch: x64
any idea what's going on?

Same issue here

There seems to be an issue on Windows, although it's not showing up when using Electron Packager directly. Not sure when I'll get to this but the workaround is to use WSL2 or a Linux VM for building macOS (darwin/mas) apps.


[Bug report]: Dropdown using default-option selects the wrong option.

Requirements before reporting

[X] No duplicated issue reported.
[X] I have read the contribution guidelines.
[X] I have checked the lastest version if the bug exist there. See all avaliable packages at npmJS.com
[X] I have made sure that the issue comes from SDDS packages by removing SDDS from my project as a test.
[X] I have followed the installation guide.

Package
@scania/components
Package versions
@scania/components 4.9.3
Browser
Edge (Chromium)
Framework
React
Version
React 18
Reproduction steps
Set default-option on the dropdown
See codebox for example:
https://codesandbox.io/s/tegel-dropdown-test-wqzyqo?file=/src/App.tsx
Code example
export default function App() {
  const data = `[
    {"label": "Denmark","value":"1384"},
    {"label": "Sweden","value":"4"}]`;
  return (
    <div className="App">
      {/* 1384 is Denmark, but Sweden is selected in the dropdown*/}
      <sdds-dropdown-filter data={data} default-option="1384" />
    </div>
  );
}

Screenshots

Expected behaviour
The dropdown should select the correct option.
Console errors

Contact information
<EMAIL_ADDRESS>AB#2427

It is due to this line:
https://github.com/scania-digital-design-system/sdds/blob/22fc47bf15f909f5fe4d9c8fb9e02b5af3dc5dd2/components/src/components/dropdown/dropdown.tsx#L115
Essentially you check if the value on the option is a substring of the option we want to set. And that is true for the above example. "1384".includes("4") === true

Den här verkar ha blivit löst, och kommer med i nästa release https://github.com/scania-digital-design-system/sdds/pull/617

Closed in https://github.com/scania-digital-design-system/sdds/releases/tag/%40scania%2Fcomponents%404.10.2


See: https://developer.mozilla.org/en-US/docs/Web/API/Document/createEvent

Fixed in d164526507887a0efa1bcd74d1e39ebcec219176


Add 11ty-feedback to starter projects

Hello!
I'd like to add this lil one to the starter projects page, as I think other folks may find it useful.
Thank you!

Thank you!


Update log4j to 2.13.3 fo stf

Updates log4j path to new 2.13.3 version
Related to https://github.com/AdoptOpenJDK/openjdk-systemtest/issues/347

Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

Test for systemtest.getDependency build : svt-jenkins / systemtest.getDependency/89/


Home Assistant not contactable after approx 24hrs using Hass.io on VirtualBox

Home Assistant release with the issue:
v0.100.4 (and preceeding v0.100.x versions)
Operating environment (HassOS/Generic):
HassOS v3.7
Supervisor logs:
Not applicable here
Description of problem:
Recently there have been several of us who are experiencing an issue where Home Asisstant becomes unreachable from the UI using Hass.io running on Oracle VirtualBox v6.0.14r133895 (qt5.6.2) which is the latest installable version at the time of writing this.
After doing a "host reboot" to make the Home Assistant UI available, in less than about 24 hours the same problem occurs. This was repeated for over 2 weeks, I then had time to work with the experts on Discord to discuss this problem further.
When HA crashes my UI is not available and the none of the automations etc trigger, it is totally offline. The Host VM is ok and you can access the prompt to login as root etc. Performing a "ha restart" fixes nothing, only a "host reboot" makes the system work again (if only for about 24 hours).
Tinkerer mentioned he had seen other people mentioning the same problem and pointed me to this thread:
https://community.home-assistant.io/t/hassio-unstable-needs-to-be-sent-to-an-asylum/158247
Working with Tommii on the Discord he talked through some commands to check the IP config of the HassOS VM, I had been using reserved IP address via DHCP. This showed that no networking info existed when it was in a failed state, so HassOS had dropped off the network.
He then suggested to set the IP address manually in HassOS which I did using the following commands:

nmcli c mod $(nmcli -g uuid c) ipv4.method manual ipv4.addresses "<IP_ADDRESS>/24" ipv4.gateway "<IP_ADDRESS>" ipv4.dns "<IP_ADDRESS>,<IP_ADDRESS>"
nmcli c up $(nmcli -g uuid c)

This so far has been fully succesful, my Home Assistant instance has been available via the UI for over 72 hours now. Feedback from the originator of the above thread was also the same (his crashed every 24hrs too) but now is stable. Also today a newbie added to the thread saying that this looks to have cured his problem too.
Not sure what the root cause of the IP Address being dropped if via DHCP from router etc, but changing it to set it manually in HassOS seems to have cured the issue.

Same thing here, using the docker image on an ubuntu server. The mentioned IP fix seems to have also helped mine.

Same, the IP command fixed the issue. I am the OP of the mentioned thread.  over 48hrs operational uptime. Before now I've have to execute a host reboot or just have VBox execute a reboot through its menus. It triggers a friendly reboot of the OS (injects the reboot command to the VMd OS). Either way the system would come back up and work for about a day. This coincides with my current lease time for DHCP addresses. 86400 seconds / 24 hours. The question is what is interfering with the re-acquisition of a lease from the DHCP server? The server itself is not at fault as no other devices drop off my network.
My network consists of Ubiquity controller adopted hardware, reserved IPs for each device on my network. Hassio gets its own IP as well.  The host machine is connected dual lan links. One to my home network and one into my IoT network, Hassio is bound through the IoT link. It gets its own IP through the VM software.

Uptime continues.

I am now at 2 weeks without a single fail since setting the IP address manually within HassOS


Feature Request

In the func-test-gen.js we can add the two more statements in the ignore list.
i.e.
      'ContinueStatement',
      'DebuggerStatement'

Thanks

good idea
please create a PR for this.

Created the pull request.

merged


Add test cases for Module in logic package

Codecov Report

Merging #114 (c261479) into master (8469347) will increase coverage by 1.68%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #114      +/-   ##
============================================
+ Coverage     60.61%   62.30%   +1.68%
- Complexity      591      607      +16
============================================
  Files           112      112
  Lines          2252     2252
  Branches        262      262
============================================
+ Hits           1365     1403      +38
+ Misses          807      768      -39
- Partials         80       81       +1

Impacted Files
Coverage Δ

...rc/main/java/seedu/address/model/ModelManager.java
77.50% <0.00%> (+3.75%)
:arrow_up:

...in/java/seedu/address/logic/parser/ParserUtil.java
48.48% <0.00%> (+4.04%)
:arrow_up:

.../address/logic/parser/ModuleViewCommandParser.java
90.00% <0.00%> (+90.00%)
:arrow_up:

...dress/logic/commands/module/ModuleViewCommand.java
100.00% <0.00%> (+100.00%)
:arrow_up:

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


Reference to 0.14.0 in 1.0.3 warning message

Using sbt.version = 1.0.3, launch sbt --info:
/opt/app # sbt --info
Picked up _JAVA_OPTIONS: -Duser.language=en -Duser.country=US -Duser.timezone=UTC
[info] Loading settings from plugins.sbt ...
[info] Loading project definition from /opt/app/project
[info] Loading settings from build.sbt ...
[info] Set current project to walmart (in build file:/opt/app/)
[warn] The `-` command is deprecated in favor of `onFailure` and will be removed in 0.14.0

Source code link: https://github.com/sbt/sbt/blob/1.x/main-command/src/main/scala/sbt/BasicCommandStrings.scala#L197

What the point here, remove the warning ?

That is weird to see a warning about the 0.14.0 while we are running the 1.0.3

Re: this warning message fix--
Do the docs need updating too? The current 1.x website says:

To set the logging level before any commands are executed on startup, use -- before the logging level.

If so I or someone can file an issue on the docs. As the original report on this issue states sbt --info now prints:

[warn] The `-` command is deprecated in favor of `onFailure` and will be removed

Btw, what should the docs say is the way to set the logging level before any commands are executed on startup? Running sbt 'set logLevel := Level.Warn' … changes the level too late after several [info] startup messages are printed out.


Magnet card always sends items to first joined player in range instead of player breaking the block

The magnet card always sends items to the first player who joined the server in range of the broken block instead of the player breaking the block.

this is rather difficult to do since I don't really have information on where the item is coming from
tho I think it would be feasible to make the items go to the closest player


Add Span#unwrap

With Span wrappers becoming more and more popular (for example https://github.com/opentracing-contrib/java-api-extensions). There is a growing need to be able to get access to the underlying Span implementation without type casts which fail if there is a hierarchy of span wrappers.

Coverage decreased (-0.1%) to 78.467% when pulling 87a120ebde9a18b34629aeeeee48eeb909a9c320 on felixbarny:unwrap into cdc9601709dee7332d5615369901f253645e4ee1 on opentracing:v0.31.0.

Coverage increased (+0.2%) to 78.832% when pulling f259b891ca753c0a6689573860c5db89b872747c on felixbarny:unwrap into cdc9601709dee7332d5615369901f253645e4ee1 on opentracing:v0.31.0.

SpanWrapper could be part of util

That kind of defeats the whole purpose of the PR. Because then it is still not possible to unwrap a plain Span to a specific one without type casts.
By the way, this is heavily inspired by JDBC wrappers: https://docs.oracle.com/javase/7/docs/api/java/sql/Wrapper.html

I know. :wink:
I'm also not a fan of the unwrapping of DataSources this way.
In my opinion unwrapping is not something that is of use for the general API; people have a Tracer and 'just use it'. For tracer implementors things are different and it would be very easy for them to create  an (internal) static utility method such as
static <T extends Span> T unwrap(Span span, Class<T> spanType) {
    return span instanceof SpanWrapper ? ((SpanWrapper) span).unwrap(spanType) : null;
}

The point of this PR should be (in my opinion) a standardized way to indicate that you can unwrap. For this the interface serves the purpose.
For me not mixing concerns and having a clean api outweighs typechecks any day.
Just my opinion of course. Curious what other think.

But how can we enforce then that each tracer's Span implements the SpanWrapper interface?

But how can we enforce then that each tracer's Span implements the SpanWrapper interface?

You can't unfortunately.
But we can add documentation to the util module with explanation why it's sensible to implement SpanWrapper when wrapping.

I don't think this adds significant value to the general API.  If the wrap fails, then it just returns null.    Not to mention, this will just encourage people to write code that is specific to a tracer implementation, rather than the OT api.  At that point, why pretend to use the OT api at all?  Just work directly with the tracer's concrete types all the way through.

I think this is a good improvement to the API. Other successful APIs, like JPA, have such methods and it's really handy to have them when you absolutely need to have access to an implementation-specific feature.

Not to mention, this will just encourage people to write code that is specific to a tracer implementation, rather than the OT api

I don't think it will encourage. People are already doing casts to get the underlying trace IDs.

I don't think it will encourage. People are already doing casts to get the underlying trace IDs.

Which points to the root cause: An omission of a general concept in the OpenTracing api: Trace ID's.
I still say: Let people typecast at their on risk but not facilitate this. Needing typecasts is usually a sign that a needed concept is still missing in the core API.
Providing an 'easy' unwrap will miss requests for such concepts and people will work around the API more than improving it. Issues such as this are a good thing and help improve the actual specification rather than help work around it.

Which points to the root cause: An omission of a general concept in the OpenTracing api: Trace ID's.

Trace IDs was just one example of why people are doing that today.

Needing typecasts is usually a sign that a needed concept is still missing in the core API.

It's very common for features to flow from implementations into the standard, like it has happened multiple times in the JPA world (from EclipseLink/Hibernate to JPA).
People will cast to the concrete implementation when they need, no matter if we provide a unwrap method or not. Providing this method will just make their code cleaner. Nothing more, nothing less.

I think it's useful, and especially if wrappers are used, otherwise there is no way to properly cast the object.

Now that we are moving on Trace Identifiers, we should consider adding unwrap as part of the same release. A couple thoughts:

We should probably move this to a cross-language discussion, since other language API's will probably need something similar.
Should we be unwrapping Tracers as well?
Even if we don't want unwrap "as-is", I feel we should not ship trace identifiers without some kind of solution for this issue.

Should we be unwrapping Tracers as well?

+1, it would help in MicroProfile-OpenTracing TCK and other use cases. The test deployment uses io.opentracing.Tracer which is casted to MockTracer in an endpoint which sends data back to the test.
Unwrap would be also helpful in GlobalTracer

Unwrap would be also helpful in GlobalTracer

...which was specifically designed to provide only the API, so people are not tempted to work around it.
I'm still :-1: on adding unwrap until I have found a use case that cannot be solved by a proper API extension

@pavolloffay I'm genuinely willing to be convinced.
When you say "you might have missed microprofile-opentracing use case altogether" do you mean your comment

it would help in MicroProfile-OpenTracing TCK

.. and the reference point 3 you mentioned:

The TCK mentions the use of Mock Tracer, but doesn't actually show how to use it (critical for the running file)

Probably I'm missing something, but from the above I still don't get what the use-case for unwrap is here..
I think @tylerbenson explained better than me when he wrote
https://github.com/opentracing/opentracing-java/pull/211#issuecomment-343639288:

I don't think this adds significant value to the general API. If the wrap fails, then it just returns null.  Not to mention, this will just encourage people to write code that is specific to a tracer implementation, rather than the OT api. At that point, why pretend to use the OT api at all? Just work directly with the tracer's concrete types all the way through.


Proposal: rely on duck typing to determine if input is a Jimp instance instead of comparing constructors

I think it would be great if we were able to instantiate Jimp image from another jimp-like object whose constructor is not necessary the same as constructor from the current instance.
And personally I think of one remarkable feature - bitmap object. It is a part of public API (lowlevel, but still public), was around for ever and unlikely to be changed in the foreseen future. It also contains all necessary data to make a copy of an image. So I would suggest adding a method that looks something like this
Jimp.isJimp = function(image) {
    if (image && image.constructor === Jimp) return true;

    return image && image.bitmap
        && typeof image.bitmap.width === 'number'
        && typeof image.bitmap.height === 'number'
        && Buffer.isBuffer(image.bitmap.data)
        && image.bitmap.data.length === image.bitmap.width * image.bitmap.height * 4;
}

and using it in the constructor instead of current check if ("object" == typeof arguments[0] && arguments[0].constructor == Jimp) {
Why?
So different modules could pass instances of Jimp around. Because otherwise we would have to encode image to something like PNG in one module just to decode it right away in another. Encoding/decoding takes time and wastes CPU cycles we don't want to waste.
It two or more modules in the project share same dependency – it would be rational thing to open/create and preprocess image in one module and send it as is to another in RAW format, if that other module known to accept Jimp instances as image sources. But the highter number of such packages used at the same time (think of something with modular architecture or a Gulp/Grunt-like toolchain) — the lower chances are that all of them will depend on the same version of Jimp.

Or rather it should just accept raw pixel data object as first argument to the constructor. It's a commonly used across different libraries and will make hooking alternative/new decoders little easier
var Jimp = require('jimp'),
    jpeg = require('jpeg-js'),
    fs = require('fs');

var jpegData = fs.readFileSync('grumpycat.jpg');
var rawImageData = jpeg.decode(jpegData, true);
var jimpImage1 = new Jimp(rawImageData);

// and then

var image2 = new Jimp(jimpImage1.bitmap);

closed via #514


Update dependency name format

use- instead of . in package and dependency naming:
https://pypi.org/project/google-cloud-pubsub/
This was causing issues with some package management tools [pipenv,
poetry]
Still needs to be tested, to see if we can still install from pypi with the new "name"

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6a82834). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #15   +/-   ##
=========================================
  Coverage          ?   45.45%
=========================================
  Files             ?        8
  Lines             ?      209
  Branches          ?       19
=========================================
  Hits              ?       95
  Misses            ?      112
  Partials          ?        2

Continue to review full report at Codecov.

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


New version: OttoZumkeller.QR-CodeReader version 1.1.0

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

2024-01-03 14:19:10.108 [FAIL] Installer failed security check. Url: https://github.com/ottozumkeller/QR-Code-Reader/releases/download/v1.1.0/QR-Code-Reader-1.1.0.msi Result: 0x80004005

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-03 14:19:10.108 [FAIL] Installer failed security check. Url: https://github.com/ottozumkeller/QR-Code-Reader/releases/download/v1.1.0/QR-Code-Reader-1.1.0.msi Result: 0x80004005

(Automated response - build 516.)

Hi @ottozumkeller,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 516.)

/AzurePipelines run

Automatic Validation ended with:

Exception during executable launch operation System.AggregateException: One or more errors occurred. (An error occurred trying to start process 'C:\Program Files\QR-Code Reader\reader.exe' with working directory 'D:\TOOLS'. The specified executable is not a valid application for this OS platform.)  ---> System.ComponentModel.Win32Exception (216): An error occurred trying to start process 'C:\Program Files\QR-Code Reader\reader.exe' with working directory 'D:\TOOLS'. The specified executable is not a valid application for this OS platform.    --- End of inner exception stack trace ---    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)

(Automated response - build 530.)

@wingetbot waivers Add Validation-Executable-Error


webUI: run output artifacts page crashes Chrome tab for some runs

wandb --version && python --version && uname

Weights and Biases version: 0.9.5
Python version: 3.6.10
Operating System: Win10
Browser: Google Chrome v.85.0.4183.83

Description
For some of my runs, the artifacts page refuses to load. It hangs and eventually crashes with memory error e.g.
https://app.wandb.ai/maria_korosteleva/Garments-Reconstruction/runs/veeany7a/artifacts?workspace=user-maria_korosteleva
There is also some Error in browser Console

There are runs, for which the page loads just fine: https://app.wandb.ai/maria_korosteleva/Garments-Reconstruction/runs/29iczuwn/artifacts?workspace=user-maria_korosteleva
What I did
It started to happen with the runs when I started to upload an additional artifact with multiple versions.
Previously, I had 3 artifacts created within a run, one of which added with many versions (checkpoints after every epoch), for the other two, only one new version is created per run => page loads fine
Now I have 4 artifacts, two of which are created with a number of versions => Page crashes

Hi Maria, thanks for filing this. @annirudh could you take a look

@maria-korosteleva thanks for sharing a link to a page that is working correctly. Could you please share a link to a page that crashes?

@cvphelps, the very first link is the one with the problem. Does it open correctly for you?

Hi @maria-korosteleva, thanks for the detailed bug report! I have a fix for the issue that we'll deploy ASAP. Once the fix is live, I'll circle back with you here.

@maria-korosteleva The issue should be fixed now. Sorry for any inconvenience this caused!


Leawind's Third Person x Crosshair Bobbing Compat

Similar to https://github.com/Exopandora/ShoulderSurfing/issues/161

The mod disables itself when not in 3rd person, see https://github.com/Krash220/CrosshairBobbingMod/blob/main/game/fabric1.16.2/src/main/java/krash220/xbob/game/api/Render.java#L28


Updated Pterodactyl Setup

Added new Pictures to have more examples.
Added a more like Step by Step tutorial.
Added also some notes about no go's.

Hi @Easylemon24,
Could you maybe move your Pull Request to our extension repository? (https://github.com/Paymenter/Extensions)


python311Packages.procmon-parser: init at 0.3.13

Description of changes
Parser to process monitor file formats
https://github.com/eronnen/procmon-parser/
Related to #81418

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.procmon-parser
python310Packages.procmon-parser.dist
python311Packages.procmon-parser
python311Packages.procmon-parser.dist


Add blur effect around switcher

Idea Description
Implement blur container with gradation around switcher
Reference images and links

Can I try this issue?🙋

Sure! Go ahead!


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/django-grappelli-feedstock#24.


[Docs] Translate Project page to Spanish

Current State:
The actual documentation is in english.
Desired State:
I want to translate this page:https://meshery.layer5.io/docs/project to spanish.

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

Awesome, please go!

https://github.com/layer5io/meshery/pull/1740


Which licence ?

Hi - before I start looking at this interesting project, how is it licensed ? I can't find any reference anywhere on the website or github home page
Thanks - from what I've seen on the demos it looks very good .

Hi,
Sorry, it was unclear (only in scripts / packages... files).
I updated README file to make it easy to find.

I give it for free to anyone and without asking anything in turn.

It is MIT license, so feel FREE :

to use
update
sell
anything you want.

And thank you for your feedback, i'm glad it helps.
Keep an eye on the drag drop version that I'm currently developing (not finished).
After that, I will make both version easier to integrate in any angular project (refactoring, modules, templates in templateCache...)

README to clearly show MIT license.
So I close this resolved issue opened for a good idea.

Thanks - I didn't want to go around poking in the source code until I knew which licence it was. I am keeping an eye on the drag and drop version - very interesting. Do you have a roadmap / time in mind ? What do you think is missing right now ?

I plan to finish drag and drop way this month (I had to write a lot of things from scratch so it just took much more time).
Then I take care the step way version.
It means refactor, making modules (right now you have to take a lot of html + dependencies to use it on your projects...).
It won't change the magic behind but change

maintainability (for me :smile: )
usability (for anyone using it so it will be :+1:  to use)

Missing features, are features that can added during easy form generator lifetime without impacting existing. It means :

new controls
new options for customization
in fact all you see in [angular formly](drag drop version) could be in easy form generator (it just makes angular formly a kid game to use).

If one day I had to make a huge patch (I hope not but I take into account this possibility), I would provide a way to migrate old version to new. You know like you, I dislike using something that one day complitely change, so I plan not make such bad experience to anyone (I'm an easy form generator user too).


[Feature Request]: Markdown and JSON Support

Is there an existing issue for the same feature request?

[X] I have checked the existing issues.

Is your feature request related to a problem?
Can you allow importation and importing of markdown documents?

Describe the feature you'd like
Can you allow importation and importing of markdown documents?
Describe implementation you've considered
No response
Documentation, adoption, use case
No response
Additional information
Can you allow importation and importing of markdown documents?

+1

+1

supported


Sorald sometimes adds imports when it really shouldn't

I'm trying to do another PR for verificatum/verificatum-vmn (commit 2e32b06), but am getting some really strange imports added:
$ sorald repair --stats-output-file 2142.json --rule-keys 2142 --original-files-path . --file-output-strategy IN_PLACE

This results in the following diff:
diff --git a/src/java/com/verificatum/protocol/hvzk/CCPoSW.java b/src/java/com/verificatum/protocol/hvzk/CCPoSW.java
index afe386d..1b40b7f 100644
--- a/src/java/com/verificatum/protocol/hvzk/CCPoSW.java
+++ b/src/java/com/verificatum/protocol/hvzk/CCPoSW.java
@@ -152,6 +152,7 @@ public final class CCPoSW extends ProtocolElGamal implements CCPoS {
             try {
                 commitmentExportThread.join();
             } catch (final InterruptedException ie) {
+                Thread.currentThread().interrupt();
             }
         }
     }
@@ -256,6 +257,7 @@ public final class CCPoSW extends ProtocolElGamal implements CCPoS {
             try {
                 commitmentExportThread.join();
             } catch (final InterruptedException ie) {
+                Thread.currentThread().interrupt();
             }
         }

diff --git a/src/java/com/verificatum/protocol/mixnet/ShufflerElGamalSession.java b/src/java/com/verificatum/protocol/mixnet/ShufflerElGamalSession.java
index 05aa99d..48183b3 100644
--- a/src/java/com/verificatum/protocol/mixnet/ShufflerElGamalSession.java
+++ b/src/java/com/verificatum/protocol/mixnet/ShufflerElGamalSession.java
@@ -25,6 +25,8 @@
  */

 package com.verificatum.protocol.mixnet;
+import static com.verificatum.protocol.elgamal.ProtocolElGamal.getCiphPGroup;
+import static com.verificatum.protocol.elgamal.ProtocolElGamal.getWidePublicKey;

 import java.io.File;

@@ -939,6 +941,7 @@ public final class ShufflerElGamalSession extends ProtocolElGamal {
                 nextOutputThread.join();
             } catch (final InterruptedException ie) {
                 throw new ProtocolError("Unable to join threads!", ie);
+                Thread.currentThread().interrupt();
             }
             nextOutputThread = null;
         }

Note the import static toward the bottom of the diff. Not only are those imports unrelated to the patch, they're also not supposed to be there as the methods in question are inherited from ProtocolElGamal. Needless to say, there's something wrong with how Sorald figures out what to import.

This is a bug in the import cleaner in Spoon. Working on a fix.

Fixed with #3798, just need the next beta. It can wait until Monday.

This was fixed with the new beta version of Spoon!


add password

Overview
Don't want to share half-baked analyses with the world. Add a password that needs to be entered correctly before app displays information.
Action Items

[ ] research possible ways to add password and not have anything shown until password is entered correctly

Resources/Instructions

would Google how others have done this, may need to translate to Python

I suppose you are talking about the Shiny app (that you want to translate into Python)?
In principle, this is not hard, but how you do this is entirely dependent on how you are implementing said application, and what framework you are using. So you need to figure that part out first before you can add a password.
That said, I also think adding a password may not be super necessary at this stage, either, unless you anticipate that the team will soon be working with confidential data. It's unlikely there is anyone who is both interested in this project's work, but not already accessing the work via the Slack or meetings. And the adverse impact of such a person looking at what is going on would be very minimal so long as we are only using publicly available data.


docs: changed the wrong numbering

Current Behaviour
In the last line of the readme, the link which is meant to take you to 05-secure-channel had been wrongly named as 04. Secure Channel.
Proposed Changes
Corrected the numbering by changing it from 04. Secure Channel to 05. Secure Channel.

Checks

[x] All commits in this Pull Request are signed.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor Licence Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the ockam-network/contributors repository.

@ade5h thank you for sending the PR!!
Please accept Ockam Contributor Licence Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the ockam-network/contributors repository.
Looking forward to merging your first contribution!

@mrinalwadhwa I just added my details to CONTRIBUTORS.csv. This is my first time contributing to such large Open Source project so kindly excuse my silly mistakes.

@ade5h you did great, thank you for taking time to fix this.
I will merge this shortly, congratulations on your first Ockam contribution 🎉

Thanks you 🙏

Thank you 🙏


scripts: coredump: Add register write handler to arm cortex-m gdbstubs.

When working with coredumps, it is useful to be able to modify base registers. Adding this capability allows implementing scripts to inspect backtrace of threads other than current the current thread.

Just curious, what kind of registers do you plan to write to?

Looks like this might be for understanding other threads in a core dump. I have been thinking about this same issue and I have proposed and am working on https://github.com/zephyrproject-rtos/zephyr/issues/74195.
I'm curious if you could share (and publish?) your scripts that would be setting the registers?

@dcpleung Looking at setting SP, PC, and LR which enables traveling the threads and getting their backtraces. The other core registers would be interesting in order to fully enable thread switching and inspection during runtime.