[Do not merge] PR to trigger a CI toolchain build

[Do not merge] PR to trigger a CI toolchain build

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain macOS Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain Linux Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain macOS Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain Linux Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain macOS Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain Linux Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain Linux Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain Linux Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain macOS Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain macOS Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please Build Toolchain macOS Platform

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please test

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please smoke test

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please smoke test

Please test with following pull request:
https://github.com/swiftlang/swift-testing/pull/825
@swift-ci Please test


Reloads files from the md5 list

Bug description
Hi! Suppose I deleted a certain number of files I do not need, I have an option "Keep deleted files on the md5 list" after a while I upload files by this tag and it downloads everything that I deleted
Steps to reproduce
Downloads>add>any tags>download>deleted any files>repeat download>deleted file uploaded
Expected behavior
I delete the file, it is in md5 list, the program no longer downloads it
System information

OS: win 7
Grabber version: 7.3.0

Additional context
On version 7.2.1 this bug is missing, he writes that "N files ignored"

What's "If a file already exists globally" set to?

UP! On the new version, everything is the same, I do not need deleted files, but he downloads them. How can I update the collection if it downloads everything that I don't need


Get inconsistent result from HuggingFace BLIP and local inference

Hi, thanks for your cool model:)
I faced with problem:
when i start the inference on HuggingFace i  have good results, but when i test BLIP on local machine i have some troubles.

But local inference gave me:
Beam Search-Vit base: A gray and white background with circles.
Nucleus sampling-Vit base: The gray background with circles is shown in this image.
Beam Search-Vit large: An image of a group of pyramids on a gray background.

Аnd so many times, this is just one example, maybe my image preprocessing is not correct and I am doing something wrong,
here is a code example of how I process the image and get the caption:
model_url_base = 'path_to_base_model'
model_url_large = 'path_to_large_model'
model_base = blip_decoder(pretrained=model_url_base, vit='base', image_size=100)
model_large = blip_decoder(pretrained=model_url_large, vit='large', image_size=100)
model_base.eval()
model_base = model_base.to(device)
model_large.eval()
model_large = model_large.to(device)
image_size = 100
transform = transforms.Compose([
transforms.ToPILImage(),
transforms.Resize((image_size, image_size), interpolation=InterpolationMode.BICUBIC),
transforms.ToTensor(),
transforms.Normalize((0.48145466, 0.4578275, 0.40821073), (0.26862954, 0.26130258, 0.27577711))
])
img = transform(sample).unsqueeze(0).to(device) # img is np.ndarray
caption_bs_base= model_base.generate(img, sample=False, num_beams=7, max_length=16, min_length=5)    #beam search
caption_ns_base = model_base.generate(img, sample=True, max_length=16, min_length=5)                               #nucleus sapling
caption_bs_large = model_large.generate(img, sample=False, num_beams=7, max_length=16, min_length=5)  #beam search
caption_ns_large = model_large.generate(img, sample=True, max_length=16, min_length=5)                              #nucleus sapling
I play around InterpolationMode and tried tried not doing transforms.Normalize, but it not help.
Can you help me, please? I totally confused.

You can see the code of the web demo at https://huggingface.co/spaces/Salesforce/BLIP/blob/main/app.py

@woctezuma
Thanks, it's pretty much the same as me, but I want to draw inferences with small 100-150 size images, but when I do image_size=384 everything works fine.
I would like to finally deal with the size of the image. If I understand correctly, we choose image_size according to the images we want to detect, or is it the Vit model hyperparameters that is chosen depending on the Vit base\large?
I didn't find an answer to my question in the source code

I imagine the BLIP decoder was trained with images of size 384.
https://github.com/salesforce/BLIP/blob/a176f1e9cc5a232d2cc6e21b77d2c7e18ceb3c37/models/blip.py#L78-L86

Thanks @woctezuma ! Yes the decoder is trained with image_size=384.


Removed unused variable.

The variable func gets re-declared and initialized before the first use (about 10 lines after this removed line). The first definition should not be used at all.

Thanks!


Adding spanish support

Hello @TorstenDittmann! I added es.json file and modified main.js, so Spanish should be now available, but I'm not completely sure that I enabled the app to detect Spanish locale, please check, it's nice to help to the development of the project. :grin: :+1:

Hey @fabiopolancoe 👋
Spanish translation was already done in a previous task in the dev branch and got just merged here https://github.com/TorstenDittmann/OmniaWrite/pull/133
Sorry, thanks for your work anyway :-)


allow also names (not only IPs) in configuration of 'listener.ssl.default'

There have already been discussions were the developers of vernemq explained why it is not possible to use <IP_ADDRESS> as IP for the default ssl listener which is ok. But for dynamic environments like docker deployments it would be useful to be able to use a name instead of an IP-address.
Environment

VerneMQ Version: 1.10.2
OS: Docker image vernemq/vernemq (29.03.2020)
Erlang/OTP version (if building from source): n/a
VerneMQ configuration (vernemq.conf) or the changes from the default
Cluster size/standalone: standalone

Docker configuration for the service 'vernemq' in my deployment:
  vernemq:
    image: vernemq/vernemq
    restart: unless-stopped
    hostname: vernemq-docker-prod
    user: root
    ports:
      - 1883:1883
      - 8883:8883
      - 18880:8888
    volumes:
      - ../letsencrypt/:/certs:ro
    environment:
      - DOCKER_VERNEMQ_ACCEPT_EULA=yes
      - DOCKER_VERNEMQ_ALLOW_ANONYMOUS=off
      - DOCKER_VERNEMQ_listener.ssl.certfile=/certs/live/SOMEDOMAIN/fullchain.pem
      - DOCKER_VERNEMQ_listener.ssl.keyfile=/certs/live/SOMEDOMAIN/privkey.pem
      - DOCKER_VERNEMQ_listener.ssl.cafile=/certs/live/SOMEDOMAIN/chain.pem
      - DOCKER_VERNEMQ_listener.ssl.default=<IP_ADDRESS>:8883
      - DOCKER_VERNEMQ_plugins.vmq_diversity=on
      - DOCKER_VERNEMQ_plugins.vmq_passwd=off
      - DOCKER_VERNEMQ_plugins.vmq_acl=off
      - DOCKER_VERNEMQ_vmq_diversity.auth_mongodb.enabled=on
      - DOCKER_VERNEMQ_VMQ_DIVERSITY.mongodb.host=mongo
      - DOCKER_VERNEMQ_VMQ_DIVERSITY.mongodb.port=27017
      - DOCKER_VERNEMQ_VMQ_DIVERSITY.mongodb.database=vernemq_auth
    networks:
      i40net:

Expected behavior
In my docker environment I can not ensure a specific IP-address for the running service so I would expect that the IP is detected automatically for SSL-MQTT (like it is already done for NON-SSL-MQTT) or that I can fill in a name (e.g. localhost, or the docker service name)
It should be possible to enter a name instead of an IP-address in the configuration e.g.:
      - DOCKER_VERNEMQ_listener.ssl.default=localhost:8883

Actual behaviour
Currently it is only possible to enter an IP. The problem can be reproduced by adding an name instead of an IP for the ssl default listener:
      - DOCKER_VERNEMQ_listener.ssl.default=localhost:8883

Best regards
Martin

Thansk @MartinEnders for opening this.
I'd like to get more input on this from the community. Is this needed in general? For Docker/K8 wouldn't you end up using discovery anyway?

I am having some problems related with this as well. Currently I am checking if I am not overlooking any (obvious) options. What I am trying to do: deploying the vernemq docker containers on AWS ECS (Fargate) behind a load balancer. This load balancer is configured to health check the container on HTTP listener of VerneMQ container (which I have tried to configure as "${IP}:8888/health"). The problem is that there is no way of knowing the container IP beforehand, and a default config of <IP_ADDRESS> does not work unfortunately:
15:26:04.828 [error] can't reconfigure http listener({0,0,0,0}, 8888) with Options [{max_connections,10000},{nr_of_acceptors,10},{config_mod,vmq_http_config},{config_fun,config},{proxy_protocol,false}] due to eaddrinuse
15:26:04.828 [error] Supervisor {<0.377.0>,ranch_listener_sup} had child ranch_acceptors_sup started with ranch_acceptors_sup:start_link({{0,0,0,0},8888}, ranch_tcp) at undefined exit with reason {listen_error,{{0,0,0,0},8888},eaddrinuse} in context start_error
15:26:04.827 [error] CRASH REPORT Process <0.379.0> with 0 neighbours exited with reason: {listen_error,{{0,0,0,0},8888},eaddrinuse} in ranch_acceptors_sup:listen_error/5 line 66
15:26:04.827 [error] Failed to start Ranch listener {{0,0,0,0},8888} in ranch_tcp:listen([{cacerts,'...'},{key,'...'},{cert,'...'},{ip,{0,0,0,0}},{port,8888},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}]) for reason eaddrinuse (address already in use)
15:26:04.827 [error] Failed to start Ranch listener {{0,0,0,0},8888} in ranch_tcp:listen([{cacerts,'...'},{key,'...'},{cert,'...'},{ip,{0,0,0,0}},{port,8888},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}]) for reason eaddrinuse (address already in use)

It seems that a solution for me would be to use the AWS Service discovery using a Route53 private DNS to create a (multivalue) DNS record for every container IP address, but as said above it is only possible to put in a IP address. Therefore it is impossible to have healthy containers for me currently.
I am not so familiar with K8s, but maybe you guys can shine some light on this if it would be different for K8s clusters.

Thansk @MartinEnders for opening this.
I'd like to get more input on this from the community. Is this needed in general? For Docker/K8 wouldn't you end up using discovery anyway?

Thank you for your response.
I'm running vernemq from docker-compose and there I did not found a solution to insert the ip of the container in the docker-compose file (I think the IP is like @MichelJansen91 mentioned not known at the creation process of the container).
For my use-case it would be great if I can set a DNS-Name for SSL or that the SSL-Interface is auto-detected the same way like the non SSL-Interface (or just <IP_ADDRESS> - but you explained in an other issue that this is not possible due to the cluster functionality vernemq provides, as far as I understood it)
My usecase: Run a single instance of vernemq with ssl in docker (docker-compose) - thats it :-)
I really like VerneMQ and would really appreciate if I could use SSL-functionality.
Best regards
Martin

@MartinEnders Are you going to use verne-mq in small or large scale? Because if it is just single container, you could simply try if <IP_ADDRESS> works (for me TCP traffic works that way currently, but I know there were some issues).
It is quite common to terminate SSL at a load balancer to simplify the configuration of other applications, and that way you are not dependent on the boot order to the containers (I assume that you also have a certbot container running in your compose setup).
As I said: I am also having problems to get several (dynamically scaling) containers to cluster up. It seems that DOCKER_VERNEMQ_DISCOVERY_NODE does support DNS names, but for some reason they don't cluster up yet, and I think that is because the load balancer thinks the nodes' status is UNHEALTHY. The health check listener (DOCKER_VERNEMQ_listener.http.default) does not work on <IP_ADDRESS> for me unfortunately.

@MichelJansen91 thank you very much 🥇 👍  it works now with <IP_ADDRESS> as ssl.default listener :
- DOCKER_VERNEMQ_listener.ssl.default=<IP_ADDRESS>:8883

This solved the problem for me. The issue can be closed from my side. @MichelJansen91 Should I close the issue or do you want to overtake it?
Oh boy, it seems that I completely misunderstood the issue #856 - I thought <IP_ADDRESS> should not be used as listener.
I think I am using verne-mq in small scale for a research project at my university (up to 200k Messages/Day).
Thank you for your advice to run a SSL termination load balancer.

I am happy that I could help you out @MartinEnders .
I still have an unresolved issue related with IP/DNS names for the listeners, so I would prefer you keep it open. Furthermore, you raised a good point so happy to hear if others in the community have the same problem and how they are solving that currently.

It seems that I made a few mistakes: the HTTP listener on 8888 is enabled by default and does not have to be reconfigured. The Health Check is now working correctly, but I am still having issues to get the nodes to cluster up using the service discovery. This issue can be closed, and I will make a new issue related to the service discovery.


Spearbit 43

Description

Fixes https://github.com/spearbit-audits/connext/issues/43
Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[x] Refactoring
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] Requires changes in customer code

High-level change(s) description - from the user's perspective

Rename slippageBoundary to destinationMinOut
Add originMinOut to xcall

Related Issue(s)
Fixes https://github.com/spearbit-audits/connext/issues/43
Related pull request(s)

@sanchaymittal @just-a-node this will require sdk changes because of the changes to call params and xcall args!


RN 0.66.2 | Android | Execution failed for task ':react-native-fbsdk-next:compileDebugJavaWithJavac'.

Hi,
installed successfully & configured properly but the build failed with the following error:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-fbsdk-next:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':react-native-fbsdk-next:debugCompileCl
   > Failed to transform legacy-support-v4-1.0.0.jar (androidx.legacy:legacy-support-v4:tegory=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.us
      > Could not find legacy-support-v4-1.0.0.jar (androidx.legacy:legacy-support-v4:1.
        Searched in the following locations:
            https://dl.google.com/dl/android/maven2/androidx/legacy/legacy-support-v4/1.
   > Failed to transform legacy-support-core-utils-1.0.0.jar (androidx.legacy:legacy-supr, org.gradle.category=library, org.gradle.libraryelements=jar, org.gradle.status=releas
      > Could not find legacy-support-core-utils-1.0.0.jar (androidx.legacy:legacy-suppo
        Searched in the following locations:
            https://dl.google.com/dl/android/maven2/androidx/legacy/legacy-support-core-
   > Failed to transform cardview-1.0.0.jar (androidx.cardview:cardview:1.0.0) to match
org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-api}.
      > Could not find cardview-1.0.0.jar (androidx.cardview:cardview:1.0.0).
        Searched in the following locations:
            https://dl.google.com/dl/android/maven2/androidx/cardview/cardview/1.0.0/car

Solutions I tried: 🔢

I thought that it's a linking issue, so I did manually linking , SAME.
I tried all possible codes in build.gradle; gives extra errors.
I added to app/build.gradle:
implementation 'androidx.legacy:legacy-support-v4:1.0.0'
implementation 'androidx.cardview:cardview:1.0.0-rc02'
implementation 'androidx.legacy:legacy-support-core-utils:1.0.0-rc02'
gives no effect.
also added to build.gradle of the lib, no effect.
tried to downgrade the lib version, SAME.
it works properly with RN 0.63, but there is no chance to downgrade RN 🗡!

Environment
"react": "17.0.2",
"react-native": "0.66.2",
"react-native-fbsdk-next": "^6.2.0",
classpath('com.android.tools.build:gradle:4.1.2')
distributionUrl=https://services.gradle.org/distributions/gradle-6.9-all.zip
--
Any Clarification or explanation to what is happening!
Any possible solution?!
Thanks.

I would not add those specific dependencies to build.gradle, I think that goes farther down the wrong path.
Usually this is either a local network failure where gradle cannot download something, or an incorrect set of repository definitions for gradle
Our example builds, and should build for you. Please try building the example here and if it works then you know you have some sort of project-specific issue, where the solution will be found in the difference between your project and the example project
Having it work with RN63 but not whatever you were on first is suspicious. You do not mention which versions you tried in between current and 63. Perhaps you still need jcenter() in your build. Examining the diffs here points at that https://react-native-community.github.io/upgrade-helper/?from=0.63.4&to=0.66.0

the current RN is 0.66
I tried to build the example you mentioned on my computer, same weird error!

Yet it builds fine in CI https://github.com/thebergamo/react-native-fbsdk-next/actions/workflows/ci.yml
something is wrong on your local network or computer somehow - you're trying everything I can think of. This must be frustrating
npx react-native-clean-project perhaps ? That is very thorough but is also a vague possible solution unfortunately
With no ability to reproduce the failure (it builds in all my environments and CI) I can't help further, apologies

We are also on react-native 0.66.2 but not facing this issue, I've noticed your version of com.android.tools.build:gradle is different from us, we are using com.android.tools.build:gradle:4.2.2
I've tried downgrading the version to com.android.tools.build:gradle:4.1.2 to match your environment and it built failed, but the error message is different from yours.
Maybe you can try upgrade it to 4.2.2 and see if it works or not
android/build.gradle
dependencies {
-     classpath('com.android.tools.build:gradle:4.1.2')
+     classpath('com.android.tools.build:gradle:4.2.2')

@rnike
I've tried upgrading already!
no effect!

to reproduce:
init new project -> installed the lib on fresh land!
same error 👎🏻

Yet it builds fine in CI https://github.com/thebergamo/react-native-fbsdk-next/actions/workflows/ci.yml

This is not just any old reproduction, the great thing about the CI is that every version of every thing is specified and visible. That is, it is completely reproducible. I have no idea what is wrong in your build environment + project unfortunately. All I know is that there is a fully transparent working build to pattern off


Fix bug: transpose(scalar|1d) should return a clone

Fixes https://github.com/tensorflow/tfjs/issues/278

This change is

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


Enhanced select's isn't firing model updates

Describe the bug
Very impressed with this project - it's been hugely helpful in my Material/Vue integration and learning path!
I'm trying to use the Enhanced select (as per https://github.com/material-components/material-components-web/tree/master/packages/mdc-select#enhanced-select). It appears that it's supported in this binding, if undocumented (https://github.com/matsp/material-components-vue/blob/master/components/select/Select.vue#L12) - not sure if this implies that the binding is incomplete for this feature, or if I'm just writing the wrong incantations. When I use the enhanced model, I have to use <m-list-item /> tags to make the menu render correctly, but these don't appear to be firing model update events (I'm using the Vue debug extension in Chrome to inspect this).
If you're able to offer any guidance on where I'm going wrong, or an indicator if this is expected behaviour and needs a patch to Select.vue to support, I'd be very grateful! I'm relatively new to Vue, but happy to attempt a PR if it's the latter.
To Reproduce
      <m-form-field>
        <m-select enhanced v-model="modelField" id="selectName">
          <m-list-item
            v-for="option in [{text: 'None', value: 'NONE'},
                              {text: 'Primary', value: 'primary-value'},
                              {text: 'Secondary', value: 'secondary-value'},
                              {text: 'Tertiary', value: 'tertiary-value'}]"
            :name="option.value"
            :data-value="option.value">
            {{ option.text }}
          </m-list-item>
          <m-floating-label slot="label">Caption</m-floating-label>
          <m-line-ripple slot="line"></m-line-ripple>
        </m-select>
      </m-form-field>

Expected behavior
When the user clicks an element in the menu, the model field modelField should update.
Desktop (please complete the following information):

OS: Ubuntu 18.04.2
Browser Chrome
Version 73.0.3683.103 (Official Build) (64-bit)

Thank you for your reporting. The issue will be fixed here. https://github.com/matsp/material-components-vue/pull/232

Whoops, my bad - I checked issues but not open PRs.
Thank you for such a prompt response, Jiajun. Keep up the excellent work!
For anyone stumbling across this issue in the meantime, I've made a temporary patch to my code (to save me from rebuilding material-components-vue) to add a click binding to each m-list-item to update the model:
          <m-list-item
            v-for="option in [{text: 'None', value: 'NONE'},
                              {text: 'Primary', value: 'primary-value'},
                              {text: 'Secondary', value: 'secondary-value'},
                              {text: 'Tertiary', value: 'tertiary-value'}]"
            :name="option.value"
            :data-value="option.value"
            @click="modelField = option.value">
            {{ option.text }}
          </m-list-item>

I look forward to replacing this when #232 is merged and released.

fixed in v1.0.0

Great to see the fix merged so fast, thanks folks! I'm unable to get this to work still, however, after updating my version of material-components-vue from npm. I can see the MDCSelect is updating its state correctly (I have added the name prop so that I get a hidden <input />, which has the correct value as I select options from the list). However, the <m-select />'s $attrs.value that is shown in the Vue devtools never changes to reflect this (and consequently the v-model isn't updated accordingly).
I'm probably missing something obvious, so my apologies for bugging you!

@tychenjiajun Can you have a look at this?

@MajorError @matsp My bad. Looking at it.

@MajorError Check the codepen here https://codepen.io/chankcccc/pen/QRGjZa . It seems to be working well.

@MajorError It seems like a building issue. I'll open a new issue describing it.

Thanks, @tychenjiajun - you're right that it seems to work in the codepen above. I'm trying to compare what I've got and what's in the pen, to see at what point I can make the two converge!

fixed in v1.0.2

That's outstanding work chaps - thank you so much for everything!
Confirmed as working in my environment too.

@MajorError  And now you can also add event handler for change event to get the selected index.
Due to huge daily workload, docs in most components are outdated. We'll be grateful if you could help :)


T34276 external tags alt

https://phabricator.endlessm.com/T34276

Oh gosh, of course, didn't occur to me of course we would want the same tag to apply to more than one node 😊
The semantics of the original make more sense to me, then, but this is a bit more lean. The through table this generates is effectively the same as the original TaggedContent model, and I think Django should attach some helpful reverse references to ContentNode itself this way. At any rate, I'm happy either way here - having the tag name unique makes it much clearer why it is the way it is :)

I went ahead and merged #486, so we can close this one.


syntax error in Python 3.4

# pip3 install threefive
Downloading/unpacking threefive
  Downloading threefive-2.1.79-py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): bitn>=0.0.27 in /usr/local/lib/python3.4/dist-packages (from threefive)
Installing collected packages: threefive
*** Error compiling '/tmp/pip-build-a1bjun2e/threefive/threefive/segmentation.py'...
  File "/tmp/pip-build-a1bjun2e/threefive/threefive/segmentation.py", line 137
    return f'{upid_map[upid_type][0]}:{upid_id}'
                                               ^
SyntaxError: invalid syntax

Successfully installed threefive
Cleaning up...

This is because f strings. I think youll need python 3.5 or greater.

Vlad is correct, I love  the f strings. Is there a reason you need to use python3.4?

I apologize, I should have made the python requirement more clear.
I believe there are only three lines that have f strings.
`
$ grep -n "f'" threefive/*.py
threefive/segmentation.py:137:                return f'{upid_map[upid_type][0]}:{upid_id}'
threefive/segmentation.py:176:        return f'{pre}{middle[2:6]}{post}'
threefive/segmentation.py:199:        return f'10.{pre}/{post[2:6]}-{post[6:10]}-{post[10:14]}-{post[14:18]}-T'
'                                                                             `

Python recently dropped support for python3.5,
and Vlad updated setup.py to reflect the 3.6 requirement.
I'm closing this issue.

Thanks for clarifying the required Python version in setup and documentation!


shared/config/expand: introduce module to expand shell-style variables

Please do not disable revive.

it was only the rule complaining about expand/ExpandFoo

@karasz amended to use expand.FromFoo instead of expand.ExpandFoo as requested


Bugfix/home page typo

look at it

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

slkfjsdlfjjd


FindItem function will match service name with another service name if it is a substring

We have found that if you have a service called ACME Map Service and run this, it will not check for an exact match and could pick up services with that as a substring.
For Example...
When findItem is called and looks for service name ACME Map Service it will also find...
Alternative ACME Map Service and ACME Map Service Backup in the results array.  We found that the results order can change as people manually update/replace the service.
As the code only pulls the id at index 0 out without testing for a match it can pull out the id for wrong service and overwrite the wrong one.
We have modified the findItem function as follows to fix this:
def findItem(self, findType):
        #
        # Find the itemID of whats being updated
        #
        searchURL = self.http + "/search"
        #print("--Search URL: " + searchURL)

        query_dict = {'f': 'json',
                      'token': self.token,
                      'q': 'title:\"'+ self.serviceName + '\" AND owner:\"' + self.username + '\" AND type:\"' + findType + '\"'}

        #searchURLwithParams = searchURL + '?' + urllib.urlencode(query_dict)
        #resp = requests.get(searchURLwithParams)

        #jsonResponse = resp.json()

        jsonResponse = sendAGOLReq(searchURL, query_dict)

        if jsonResponse['total'] == 0:
            print "\nCould not find a service to update. Check the service name in the settings.ini"
            logging.info('*********** Failed - Could not find service to update ************************')
            sys.exit()
        else:
            ############### FIXED CODE #########################
            resultList = jsonResponse['results']
            #filter for correct service name... this could probably be written better!
            for it in resultList:
                itemTitle = it["title"]
                if itemTitle == self.serviceName:
                    print("found {} : {}").format(findType, it["id"])
                    return it["id"]
                else:
                    pass
           ############## END FIX #############################

I have seen this is a fork from khibma so I have raise the issue there... https://github.com/khibma/update-hosted-feature-service/issues/12


Merge 4.034 branch into main to pickup split packaging

Checklist

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

This merges stuff I did in the 4.034 branch last Spring that splits verilator_bin_dbg into it's own verilator-debug package.  That will make it much faster and smaller to install the verilator package in the common case.
I also had added --disable-partial-static to the configure cmdline.  I reference an upstream commit with the details of what was being statically linked.  Until we also package licenses for those statically linked libraries, we should disable it.
Somehow, this also removes the python matrix from the packages.  I don't completely understand why, but I'm not complaining, I wasn't intending to add the matrix of python versions.

@timkpaine , you might want to take a gander at this before we merge. It changes quite a few things.

@timkpaine if you have a chance to look through this, I'd like to merge it.   It's cool if you don't have time.  I'll interpret silence as meaning that you're busy.


Add CONTRIBUTING.md

add contributing guidelines

coding style
rules
formatting

Reference: https://github.com/pytorch/vision/blob/master/CONTRIBUTING.md

which formatter guys @rubentea16 @juannat95  flake8 atau pycodestyle ?

and using pydocstyle for docstring?

which formatter guys @rubentea16 @juannat95 flake8 atau pycodestyle ?

pycodestyle sama pydocstyle sih


feat: support running individual cucumber feature tests

Had to take move the feature tests out of the testify suite to support running each individually.

Also don’t log user access tokens.

Can you document how to run the individual tests in docs/developer/integration-tests.md ?


Qq

Expected Behavior
Link to the documentation or explain the expected outcome of following the documentation.
Actual Behavior
Explain what actually happens when you follow the documentation.
Section that requires update
Provide a link to the page that needs an update and be specific about which section requires the update.
Additional information
Any other details or screenshots you think are relevant.

This issue appears to have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions.


Inline process.env variable references directly when installing.

Changes
Inline process.env property references directly when installing, as discussed in https://github.com/pikapkg/snowpack/discussions/1000.
Testing
Existing tests seem to provide sufficient coverage for this change.
I assume the react-related changes in the snapshots are due to modules getting tree-shaken away thanks to inlining NODE_ENV.

This change is

perfect timing too, I think this may be related to https://github.com/pikapkg/snowpack/discussions/1026#discussioncomment-77358


RR-465 use the DPS homepage search component for prisoner search

Description
Use the DPS homepage search component for prisoner search.
https://github.com/ministryofjustice/hmpps-digital-prison-services/blob/main/server/views/partials/homepage/search.njk
https://github.com/ministryofjustice/hmpps-digital-prison-services/blob/main/assets/scss/pages/_homepage.scss#L60-L102
This fixes 2/3 of accessibility raised from the audit.
https://dsdmoj.atlassian.net/browse/RR-465

Will confirm with design team about the minor spacing changes before merging this 👍🏻

This has been signed off by design (see JIRA comment)


Support Sdkman as installation supplier

Add initial support for SDKMAN to establish a structure. It is yet to be discussed whether this code lives in core or will be moved out into a plugin. This is part of #13871

Addressed comments and rebased
@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.


source_id registration of AWI-CM

label = AWI-CM 1.0
source_id = AWI-CM-1-0
institution_id = AWI
release_year = 2017
aerosol = None
atmosphere = ECHAM6.3.02p4 (384*192 grid points, T127L95, 95 levels, top level 80000 m)
atmospheric_chemistry = None
land_ice = None
land_surface = JSBACH 3.10
ocean = FESOM 1.4 (unstructured grid in the horizontal with 830305 wet nodes, 46 vertical levels; top grid cell 0-5 m)
ocean_biogeochemistry = None
sea_ice = FESOM 1.4

@tsemmler05 those changes have been updated, please take a look at CMIP6_source_id.html
There are some fields that require further information from you before we close this issue, these include (values between # symbols require replacement):
atmosphere: ECHAM6.3.02p4 (#XXX x XXX# T127L95; #XX# levels; top level 80000 m)
ocean: FESOM 1.4 (unstructured grid in the horizontal with 830305 wet nodes; 46 levels; top grid cell #X-X# m)
land_surface: JSBACH (#WHICH VERSION#)

@tsemmler05 can you provide the information noted above so we can update and close this issue?

O.k., now the additional information is saved.

@tsemmler05 if you check the current information for AWI-CM-1-0 here you'll see that we still need to update the details noted above. Can you please provide these?

Dear Paul!
All this information I have already provided several days ago directly in Github.
Regards,
Tido.
Am 04.02.2017 um 10:45 schrieb Paul J. Durack:

@tsemmler05 if you check the current information for AWI-CM-1-0 here you'll see that we still need to update the details noted above. Can you please provide these?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Maybe you did not see it because I have just edited the original entry (which still occurs at 17 days ago).

@tsemmler05 those changes have now been updated, please take a look at CMIP6_source_id.html and double check the final entries

@tsemmler05 we've amended the information that we're collecting about models and require some additional information from you. The values below need some revision or new information - I've noted ### some text ### below where I have revised the format between the # symbols, or a ### marker where web links to the information sources for new fields that we require additional information from you:
"AWI-CM-1-0":{
  "activity_participation":[
    "" ### See activity list at https://github.com/WCRP-CMIP/CMIP6_CVs/blob/master/CMIP6_activity_id.json
  ],
  "atmosphere":"ECHAM6.3.02p4 (T127L95; ###384 x 192 longitude/latitude###; 95 levels; top level 80 km)",
  "nominal_resolution_atmos":"", ### See Appendix 2 in https://goo.gl/v1drZl
  "nominal_resolution_landIce":"", ### See Appendix 2 in https://goo.gl/v1drZl
  "nominal_resolution_ocean":"", ### See Appendix 2 in https://goo.gl/v1drZl
},

{
"activity_id":[
"CMIP DECK",
"CORDEX",
"HighResMIP",
"OMIP",
"PMIP",
"ScenarioMIP",
"SIMIP",
"VIAAB"
],
"version_metadata":{
"author":"Tido Semmler<EMAIL_ADDRESS>"creation_date":"Wed Mar 29 11:00:52 2017 +0200",
"institution_id":"AWI",
"latest_tag_point":"1.1 (394)",
"repository_root":"https://swrepo1.awi.de/svn/awi-cm",
"repository_UUID":"4630c9d9-8ccb-0410-a7f8-f558f457bccd"
}
}

"atmosphere":"ECHAM6.3.02p4 (T127L95; ### grid = “native atmosphere T127 gaussian grid (128x256 latxlon)” ###; 95 levels; top level 80 km)",

@tsemmler05 this is what I have ascertained from your entries above (and the existing registered fields), please copy and update in a new comment below to correct any issues you see:
source_id['AWI-CM-1-0']['activity_participation'] = ['CMIP',
                                                     'CORDEX',
                                                     'HighResMIP',
                                                     'OMIP',
                                                     'PMIP',
                                                     'SIMIP',
                                                     'ScenarioMIP',
                                                     'VIACSAB']
source_id['AWI-CM-1-0']['atmosphere'] = 'ECHAM6.3.02p4 (T127L95 native atmosphere T127 gaussian grid; 384 x 192 longitude/latitude; 95 levels; top level 80 km)'
source_id['AWI-CM-1-0']['nominal_resolution_atmos'] = ['100 km']
source_id['AWI-CM-1-0']['nominal_resolution_landIce'] = ['none']
source_id['AWI-CM-1-0']['nominal_resolution_ocean'] = ['25 km']
source_id['AWI-CM-1-0']['ocean'] = 'FESOM 1.4 (unstructured grid in the horizontal with 830305 wet nodes; 46 levels; top grid cell 0-5 m)'

source_id['AWI-CM-1-0']['activity_participation'] = ['CMIP',
'CORDEX',
'HighResMIP',
'OMIP',
'PMIP',
'SIMIP',
'ScenarioMIP',
'VIACSAB']
source_id['AWI-CM-1-0']['atmosphere'] = 'ECHAM6.3.02p4 (T127L95 native atmosphere T127 gaussian grid; 384 x 192 longitude/latitude; 95 levels; top level 80 km)'
source_id['AWI-CM-1-0']['nominal_resolution_atmos'] = ['100 km']
source_id['AWI-CM-1-0']['nominal_resolution_landIce'] = ['none']
source_id['AWI-CM-1-0']['nominal_resolution_ocean'] = ['25 km']
source_id['AWI-CM-1-0']['ocean'] = 'FESOM 1.4 (unstructured grid in the horizontal with 830305 wet nodes; 46 levels; top grid cell 0-5 m)'

@tsemmler05 thanks for this, we have included some new fields as well which will also need updating - I have guessed at these and noted this with ### text below - please confirm these are correct and I will update the registration:
activity_participation = ['CMIP',
                                        'CORDEX',
                                        'HighResMIP',
                                        'OMIP',
                                        'PMIP',
                                        'SIMIP',
                                        'ScenarioMIP',
                                        'VIACSAB']
aerosol = None
atmosphere = 'ECHAM6.3.02p4 (T127L95 native atmosphere T127 gaussian grid; 384 x 192 longitude/latitude; 95 levels; top level 80 km)'
atmospheric_chemistry = None
institution_id = AWI
label = AWI-CM 1.0
label_extended = AWI-CM 1.0
land_ice = None
land_surface = JSBACH 3.10
nominal_resolution_aerosol = 'None'
nominal_resolution_atmos = '100 km'
nominal_resolution_atmosChem = 'None'
nominal_resolution_land = 100 km' ### Is this correct?
nominal_resolution_landIce = 'None'
nominal_resolution_ocean = '25 km'
nominal_resolution_ocnBgChem = 'None'
nominal_resolution_seaIce = '25 km' ### Is this correct?
ocean = 'FESOM 1.4 (unstructured grid in the horizontal with 830305 wet nodes; 46 levels; top grid cell 0-5 m)'
ocean_biogeochemistry = None
release_year = 2017
sea_ice = FESOM 1.4
source_id = AWI-CM-1-0

Yes, thanks for adding the extra entries, I can confirm that these are correct.

@tsemmler05 thanks, please take a peek at CMIP6_source_id.html and let me know if any other tweaks are required

Looks good!


Route works only on top of controller. Why?

Hello,
I have the following routes on a controller:
[GET("Users")]
public virtual ActionResult Index(Int32 p = 1)

[GET("Users/New")]
public virtual ActionResult New()

[POST("Users"), ValidateAntiForgeryToken]
public virtual ActionResult Create(UserNewModel model)

[GET("Users/{id}")]
public virtual ActionResult Show(Int32 id)

[GET("Users/{id}/Edit")]
public virtual ActionResult Edit(Int32 id)

[PUT("Users/{id}"), ValidateAntiForgeryToken]
public virtual ActionResult Update(Int32 id, UserEditModel model)

[GET("Users/{id}/Delete")]
public virtual ActionResult Delete(Int32 id)

[DELETE("Users/{id}"), ValidateAntiForgeryToken]
public virtual ActionResult Destroy(Int32 id)

[GET("Users/SignIn")]
public virtual ActionResult SignIn()

[POST("Users/SignIn"), ValidateAntiForgeryToken]
public virtual ActionResult SignIn(UserSignInModel model)

When I try to access Users/SignIn I get a 404 error.
If I move this action to the top in the controller then it works fine.
But I don't see why.
Any idea?
Thank You,
Miguel

GET("Users/{id}") matches the url "/Users/SignIn". Maybe you are returning a 404 in the Show method?
In any case, the order matters here so that Users/SignIn is tested before Users/{id}. You can also use a regex constraint on that id param if you must, if you can constrain it to digits or some other known pattern.
Hope this helps. Let me know if it's something else.
On Feb 10, 2012, at 10:01 AM, shapper wrote:

Hello,
I have the following routes on a controller:
[GET("Users")]
public virtual ActionResult Index(Int32 p = 1)
[GET("Users/New")]
public virtual ActionResult New()
[POST("Users"), ValidateAntiForgeryToken]
public virtual ActionResult Create(UserNewModel model)
[GET("Users/{id}")]
public virtual ActionResult Show(Int32 id)
[GET("Users/{id}/Edit")]
public virtual ActionResult Edit(Int32 id)
[PUT("Users/{id}"), ValidateAntiForgeryToken]
public virtual ActionResult Update(Int32 id, UserEditModel model)
[GET("Users/{id}/Delete")]
public virtual ActionResult Delete(Int32 id)
[DELETE("Users/{id}"), ValidateAntiForgeryToken]
public virtual ActionResult Destroy(Int32 id)
[GET("Users/SignIn")]
public virtual ActionResult SignIn()
[POST("Users/SignIn"), ValidateAntiForgeryToken]
public virtual ActionResult SignIn(UserSignInModel model)
When I try to access Users/SignIn I get a 404 error.
If I move this action to the top in the controller then it works fine.
But I don't see why.
Any idea?
Thank You,
Miguel

Reply to this email directly or view it on GitHub:
https://github.com/mccalltd/AttributeRouting/issues/44

Nice, it was exactly that. I just added:
RegexRouteConstraint("id", @"^[0-9]+$")
Do you advice to always add a RegexRouteConstraint when ID is known to be INT.
And a side question:
I have a RoutePrefix on a controller.
Can I make one of the actions to not have that RoutePrefix?
I tried to add RoutePrefix to actions but it is not allowed.
Thank You,
Miguel

I bet you could figure out a way. See the configuration page in the wiki. You can apply constraints globally to route params by supping a key (to match the route param name) and a constraint to apply  (can be anything you want, just has to implement IRouteConstraint).
To make an action ignore prefixes, use the IsAbsoluteUrl property on the route, like so: [GET("abc", IsAbsoluteUrl = true)]
t
On Feb 10, 2012, at 10:15 AM, shapper wrote:

Nice, it was exactly that. I just added:
RegexRouteConstraint("id", @"^[0-9]+$")
Do you advice to always add a RegexRouteConstraint when ID is known to be INT.
And a side question:
I have a RoutePrefix on a controller.
Can I make one of the actions to not have that RoutePrefix?
I tried to add RoutePrefix to actions but it is not allowed.
Thank You,
Miguel

Reply to this email directly or view it on GitHub:
https://github.com/mccalltd/AttributeRouting/issues/44#issuecomment-3909833

Yes, I was able to solve it ...
I have been using AttributeRouting for the past 2 months and it is great.
And all situations seem to have a solution. Only localization is missing.
Now I am more familiar with AR so I added a few suggestions about localization here:
https://github.com/mccalltd/AttributeRouting/issues/20
What do you think? I have no idea if that is possible but ...


Add a mock up of an overall search page

Presented to Working Group and asked for feedback. None received so closing for the time being.


setData没有生效

使用nextjs，先初始化了MindMap
    useEffect(() => {
        mindMapRef.current = new MindMap({
            el: document.getElementById('mindMapContainer'),
            data: {
                "data": {
                    "text": "根节点"
                },
                "children": []
            }
        });
    }, [])

然后设置了更新，并且检查了节点数据
    useEffect(() => {
        if (mindMapRef.current && jsonInfo) {
            debugger
            mindMapRef.current.setData({ data: { text: "test1" } });
            let temp = mindMapRef.current.getData()
            console.log("检查数据", temp)
            // });
        } else {
            console.log("mindMapRef.current is null");
        }
    }, [jsonInfo])

发现检查数据里面数据其实改变了，但是页面并没有重新被渲染。
是我用法错了吗

Hello, we tried to solve the issue.
This is what we did:
Modified the Edit.vue component to properly handle data changes and trigger a re-render of the mind map. Added a new method to update the mind map data and render, and modified the setData method to use this new method.
You can review changes in this commit: https://github.com/mnmnk43434/wanglin2-mind-map-1040/commit/ecb7816d4ffbd02085aef9661416cf8dbd2e089d.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.

我用的是不依赖框架的版本，也就是simple-mind-map，并且用的是react

sry，my bad coding  qaq


Add optional sortsupport methods to the PostgreSQL GiST indices

What does this implement/fix? Explain your changes.
I finally found some time to resume working on (and mostly completed) my RDKit UGM sprints project. I am still running tests and I'm afraid support for bfp data could/should be eventually disabled by default. On the other hand, based on some (very) preliminary data, there might be some useful performance improvement for substructure searches.
PostgreSQL 14 introduced support for pre-sorting the data when building GiST indices. This means that if a suitable comparator function is defined, instead of using the penalty and picksplit functions to insert the a new entry starting from the root node, the destination leaf node can be determined upfront, and the index tree is then updated bottom-up following the direct insertion of the new entry into the corresponding leaf node.
In general, pre-sorting is expected to reduce the create and reindex execution time and allow the construction of more compact indices. In the case of the RDKit GiST indices I think the penalty and picksplit implementation were always a problematic part of the index implementation, and I was therefore hopeful that pre-sorting could result in a better distribution of the data across the index tree.
The difficult part in applying pre-sorting to the indexed bit strings is that the implemented linear ordering should preserve the locality in the original search space (items that are close to each other when ordered left-to-right across the leaf nodes, should be also close to each other according to the search criteria; for geometric and low-dimensionality indices this topic has a direct and very interesting connection to that of space-filling curves).
Gray codes are binary encodings where consecutive bitstrings by definition differ in the value for one single bit, and may be therefore assumed to be somewhat similar to each other. Because implementing a comparator function for the "binary reflected gray code" looked relatively easy, I decided to explore this option for the bfp and mol indices.
Apparently, this worked well for substructure searches, in my first tests the index construction is only marginally faster, but queries look faster (40 to 5 % depending on the selectivity - "unfortunately" it's fast queries becoming even faster, but there's a small benefit for low selectivity queries too).
For the bfp index I didn't run any exhaustive tests, but the index construction is for some reason 2x slower and the few search queries I tested didn't perform very differently with pre-sorting enabled. I suspect this may be due to how the binary reflected gray code orders the strings in a way that tends to conflict with criteria that would be instead very useful to similarity queries. Monotonic (or almost monotonic) gray codes exist that sort the bitstrings in increasing weight/popcount order. For this reason, I think a monotonic gray code would probably work better for similarity queries, but implementing a suitable comparator function looks much more challenging (and I also have a couple other topics I'd like to explore re similarity searches).
Any other comments?

In summary, I think at present the main outcome from this exercise is that the gmol_penalty and gmol_picksplit function don't do a really great job at distributing the entries in the search tree in a way that is ideal to support the substructure search queries, and ordering the data according to a binary reflected gray code might work better. Similarly to the bfp/similarity search case, it's possible that other variants (e.g. a long-run gray code) could work better, but implementing a corresponding comparator looks challenging).

Gray code at Wikipedia
Alternative Gray codes

sorry, are there any known issues affecting the Ubuntu_x64_cartridge build? it looks like it failed at installing the cartridge files with "Permission denied" errors, and consequently failed all tests, but I was comparing this behavior with a different recent PR, and in that case it similarly failed at installing the cartridge and the tests still passed, which is even more surprising to me.

@rvianello Hi Riccardo, I have just checked the logs.
If you go through the linux_build_catrdige.yml file you will see that the first failure (due to insufficient privileges at the make install) stage is indeed expected since the normal user cannot write to /usr:
2023-04-23T17:36:25.5941407Z =====================================================================
2023-04-23T17:36:25.5941766Z PostgreSQL cartridge installation failed:
2023-04-23T17:36:25.5942101Z =====================================================================
2023-04-23T17:36:25.5942499Z + test -n ''
2023-04-23T17:36:25.5942951Z + cp /home/vsts/work/1/s/build/Code/PgSQL/rdkit/rdkit--4.3.1.sql /usr/share/postgresql/12/extension
2023-04-23T17:36:25.5943548Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit--4.3.1.sql': Permission denied
2023-04-23T17:36:25.5943967Z + cp /home/vsts/work/1/s/Code/PgSQL/rdkit/rdkit.control /usr/share/postgresql/12/extension
2023-04-23T17:36:25.5944442Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit.control': Permission denied
2023-04-23T17:36:25.5945568Z + cp /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--3.8--4.0.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.0--4.0.1.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.0.1--4.1.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.1--4.1.1.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.1.1--4.2.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.2.0--4.3.0.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.3.0--4.3.1.sql /usr/share/postgresql/12/extension
2023-04-23T17:36:25.5947800Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit--3.8--4.0.sql': Permission denied
2023-04-23T17:36:25.5948382Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit--4.0--4.0.1.sql': Permission denied
2023-04-23T17:36:25.5948895Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit--4.0.1--4.1.sql': Permission denied
2023-04-23T17:36:25.5949397Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit--4.1--4.1.1.sql': Permission denied
2023-04-23T17:36:25.5949909Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit--4.1.1--4.2.sql': Permission denied
2023-04-23T17:36:25.5950422Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit--4.2.0--4.3.0.sql': Permission denied
2023-04-23T17:36:25.5950928Z cp: cannot create regular file '/usr/share/postgresql/12/extension/rdkit--4.3.0--4.3.1.sql': Permission denied
2023-04-23T17:36:25.5951324Z + cp /home/vsts/work/1/s/build/Code/PgSQL/rdkit/librdkit.so /usr/lib/postgresql/12/lib/rdkit.so
2023-04-23T17:36:25.5951815Z cp: cannot create regular file '/usr/lib/postgresql/12/lib/rdkit.so': Permission denied
2023-04-23T17:36:25.5952079Z
2023-04-23T17:36:25.5952392Z =====================================================================
2023-04-23T17:36:25.5952881Z This might be due to insufficient privileges.
2023-04-23T17:36:25.5953243Z Check /home/vsts/work/1/s/build/Code/PgSQL/rdkit/pgsql_install.sh
2023-04-23T17:36:25.5953573Z for correctness of installation paths. If everything is OK, gain
2023-04-23T17:36:25.5953918Z administrator privileges, stop the PostgreSQL service, run
2023-04-23T17:36:25.5954258Z /home/vsts/work/1/s/build/Code/PgSQL/rdkit/pgsql_install.sh
2023-04-23T17:36:25.5954583Z to install the PostgreSQL RDKit cartridge, then start again
2023-04-23T17:36:25.5954895Z the PostgreSQL service.
2023-04-23T17:36:25.5955206Z =====================================================================

However, the subsequent sudo sh ./Code/PgSQL/rdkit/pgsql_install.sh succeeds:
2023-04-23T17:36:25.6015935Z + test -n
2023-04-23T17:36:25.6019745Z + cp /home/vsts/work/1/s/build/Code/PgSQL/rdkit/rdkit--4.3.1.sql /usr/share/postgresql/12/extension
2023-04-23T17:36:25.6035967Z + cp /home/vsts/work/1/s/Code/PgSQL/rdkit/rdkit.control /usr/share/postgresql/12/extension
2023-04-23T17:36:25.6054465Z + cp /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--3.8--4.0.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.0--4.0.1.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.0.1--4.1.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.1--4.1.1.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.1.1--4.2.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.2.0--4.3.0.sql /home/vsts/work/1/s/build/Code/PgSQL/rdkit/update_sql/rdkit--4.3.0--4.3.1.sql /usr/share/postgresql/12/extension
2023-04-23T17:36:25.6072604Z + cp /home/vsts/work/1/s/build/Code/PgSQL/rdkit/librdkit.so /usr/lib/postgresql/12/lib/rdkit.so
2023-04-23T17:36:25.6230272Z ##[section]Finishing: Build

So /usr/lib/postgresql/12/lib/rdkit.so is correctly installed.
Then the tests start:
2023-04-23T17:36:26.1606921Z ##[section]Starting: Run tests

and fail, which is probably due to something wrong in this cartridge build.
In the recent PR that you checked you have probably been misled by the first installation failure (which is indeed expected).
The fact that all tests passed means that the built cartridge was fully functional.
I hope this makes sense to you.

I suspect something went wrong either in the cmake configuration step, or in the setup of the build environment. I'm not familiar with Ubuntu, but if I understand correctly, in the setup step postgres 14 is uninstalled and replaced by postgres 12. On the other hand, cmake reports -- Found PostgreSQL: /usr/lib/x86_64-linux-gnu/libpq.so (found version "15.2").
At line 50 of the tests ouput I find one line reading: +ERROR:  invalid function number 11, must be between 1 and 9 that seems to confirm that the code was built against postgres 12, but with the sortsupport method enabled. The inconsistency was probably caused by cmake finding postgres 15.2.

@rvianello Indeed, it looks like
    sudo apt-get remove postgresql-14 postgresql-client-14
    sudo apt-get remove postgresql postgresql-common postgresql-client-common
    sudo apt purge postgresql-14 postgresql-client-14
    sudo apt purge postgresql postgresql-common postgresql-client-common

did not remove PostgreSQL 15.2 from the system.
My guess is that the above worked when Ubuntu shipped with PostgreSQL 14.
Could you try replacing -14 with -15 in .azure-pipelines/linux_build_cartridge.yml in your PR? That might fix it.

@ptosco Ah, I see, thanks for the suggestion. I'll try this later today.

@ptosco I briefly tested the changes and then reverted them. It looks like PostgreSQL 15 is not initially present and version 14 is actually removed. Maybe some other package should be pinned when version 12 is installed?

@rvianello I see. Incidentally it looks like the attempt to remove postgresql is ineffective:
Package 'postgresql' is not installed, so not removed

Assuming that PostgreSQL 15 is pulled in as dependency of something else, I would then suggest to explicitly instruct CMake to target PostgreSQL 12 by adding relevant CMake switches:
        -D PostgreSQL_INCLUDE_DIR=/usr/include/postgresql/12 \
        -D PostgreSQL_TYPE_INCLUDE_DIR=/usr/include/postgresql/12/server \
        -D PostgreSQL_LIBRARY=/usr/lib/postgresql/12/lib/libpq.so \

@ptosco adding libpq5 to the list of removed/purged packages eventually worked.
I'll push another commit (skipping the downgrade to postgresql 12) to actually exercise the modified code.

@rvianello is this ready to be reviewed?

@greglandrum yes, thank you, I think it is now ready to be reviewed. I repeated my tests with a larger database, which confirmed my earlier results. There should be a performance improvement for substructure search queries, but I by default disabled the pre-sorting support for the bfp gist index, where the implemented sorting criteria is not effective.
I mainly added these cmake options to help with testing, I can eventually remove them again (and cleanup some of the related code) if you prefer to keep the overall build-time configuration simple.
Also, the CI so far only tested this branch with postgres 12, which is a useful sanity check, but it didn't actually exercise the new code. I don't know if it may be possible to install the missing dev packages for postgres 14, or if there was a different reason for  downgrading it to version 12.

Also, the CI so far only tested this branch with postgres 12, which is a useful sanity check, but it didn't actually exercise the new code. I don't know if it may be possible to install the missing dev packages for postgres 14, or if there was a different reason for downgrading it to version 12.

It's definitely worth doing a bit of exploration to see if we can get the CI to run v14. How about we wait until after this is merged and do that in a separate PR?

Sounds good to me, thanks.


Create/Focus Space doesn't work (no error, no effect)

@EDIT:
Fixed as of 10-03-2024 in commit f16eba3
As @cockytrumpet mentioned:

It now works after updating from HEAD and running:
sudo yabai --uninstall-sa
sudo yabai --load-sa
pkill -x Dock

Hey, I have a problem with yabai -m space --create. The command does execute with no errors, however no space is created. I've read the instructions on how to create a space, I went through multiple Github issues related to spaces:

https://github.com/koekeishiya/yabai/issues/2115
https://github.com/koekeishiya/yabai/issues/763
https://github.com/koekeishiya/yabai/issues/1282
https://github.com/koekeishiya/yabai/issues/787

Someone had pointed out in one of the issue that he had similar problem when using yabai with only one (builtin) display.
I went through uninstalling/installing scripting additions multiple times, but nothing works. Does anyone else has the same problem? I don't experience any other issue as of now (after installing yabai from HEAD), but only that one, which is critical to me.
CSR protection is disabled:

MacOS Version: Sonoma 14.4
On screenshot below you can see I am executing the command multiple times on the right window, and then querying for spaces, but only one is created.

Update:
I went and created multiple desktops manually by pressing CTRL + ARROW_UP and "+" button to the right.

Now I can see them as spaces, running yabai -m query --spaces:

However running yabai -m space --focues <id> bears now effect also:

Moving windows between displays/spaces using: yabai -m window --space 3 works just fine, but yabai -m space --focus 3 bears no effect.

I have this same problem, also after installing from HEAD!

scripting addon configured
SIP is enabled
skhd running

It now works after updating from HEAD and running:
sudo yabai --uninstall-sa
sudo yabai --load-sa
pkill -x Dock

Fixed now - details in @cockytrumpet solution 🖖 🚀


Wrong error code when there is no SNMP community

@Torsten Sorger
The script will fail if no SNMP communities exist on the BigIP (exit code 5 - Failure to run snmpwalk).
@jaikumar_f5
Hi Leo,
Was testing this on couple of servers, noticed when there is no SNMP community strings configured, the error that should be captured is e_no_snmp_community(4), but the error getting capture is e_running_snmpwalk(5).
Because irrespective of get_snmp_community() success or not, run_snmpwalk() is getting always triggered. Then "Failure to run snmpwalk" error is coming up.
Would you want to update it to get "There is no SNMP community setup" when there's no SNMP community configured and stop further processing.

Fixed in version 1.1.0.

When I ran the script it produced a .txt file vs .html.  I renamed the file and ensured that it was in the same folder as the tablefilter.js; however it comes out as text in a browser.  The data is present, just not formatted correctly for HTML viewing
/jeff

You need to run the script twice, before and after. 3 files will be produced, 2 txt and one html. The line you post is from the txt file.
If you still have problems, please open a new issue, and I will have a look.


Introduction - Jamil

My Introduction Jamil
A small heads up before you begin typing, never mention your name in combination with your HvA student number in public.
Name
Jamil Djabarkhan
Class
VID2
About me
A visual designer
Goals
improve my css skills and combine it with my visual skills
Skill level
beginner
GitHub username
https://github.com/jamilvice
GitHub repository
https://github.com/jamilvice/web-animatie

🎉 Thanks Jamil!


Cannot typecheck js without using ts-node

Version
v2.8.1
Reproduction link
https://codesandbox.io/s/codesandbox-nuxt-ddhzb
Steps to reproduce

create a new nuxt project
add a tsconfig.json file
nuxt is asking to install ts-node

What is expected ?
I create a tsconfig file and can use typechecking in javascript with jsdoc comments, e.g.
/**
 * @type {string}
 */
let x = 2; // gives a typescript warning

What is actually happening?
it forces me to install ts-node even though the files are just javascript

This bug report is available on Nuxt community (#c9459)

Hi @SimonSiefke, we're aware of this issue, it will be fixed in 2.9 with the externalization of TypeScript support. You'll be able to use tsconfig.json without being forcing to install dependencies.


[KCC] Upload the ready-to-use test-cli for solutions test

As we discussed in #651, I'm uploading the test-cli to remove the dependency on Go.

In general we should avoid committing binary files. Could this be put in a GCS bucket instead?

In general we should avoid committing binary files. Could this be put in a GCS bucket instead?

Yeah, makes sense. Will do.


[SUGGESTION] Consider utilizing "Universal Silicon Labs Flasher" from Nabu Casa / Home Assistant

@NilsBohr suggest consider having Elelabs Firmware Update Utility depend on "Universal Silicon Labs Flasher" from Nabu Casa:
https://github.com/NabuCasa/universal-silabs-flasher
"Universal Silicon Labs Flasher" is being developed by a few Home Assistant's developers who are employed by Nabu Casa.
https://www.nabucasa.com/about/

Note! universal-silabs-flasher has not yet implemented support for reset into bootloader command via Spinel + HDLCLite protocol, that is currently work in progress by puddly, see -> https://github.com/NabuCasa/universal-silabs-flasher/pull/13

Also note that older Silicon Labs chips with Ember Bootloader need patch for EBL parsing -> https://github.com/NabuCasa/universal-silabs-flasher/pull/11

FYI, the forks by darkxst and mercenaruss offers improved support for other adapters:
https://github.com/darkxst/multipan_flasher
https://github.com/mercenaruss/zigstar_addons/tree/main/zigstar-silabs-flasher

@NilsBohr FYI, support for EBL parsing merged into upstream universal-silabs-flasher -> https://github.com/NabuCasa/universal-silabs-flasher/pull/11


Adding dns.setCustom and ns.getInfo

I need these calls so I added them. Was surprisingly easy. Thanks!

Looks good to me. Thanks!


+CONFIG_CRYPTO_NULL=m
+CONFIG_CRYPTO_GCM=m
+CONFIG_CRYPTO_SEQIV=m
+CONFIG_CRYPTO_CTR=m
+CONFIG_CRYPTO_CTS=m
+CONFIG_CRYPTO_XTS=m
+CONFIG_CRYPTO_GHASH=m
+CONFIG_CRYPTO_DRBG_MENU=m
+CONFIG_CRYPTO_DRBG=m
+CONFIG_CRYPTO_JITTERENTROPY=m
+CONFIG_XXHASH=m
+CONFIG_ZSTD_DECOMPRESS=m
+CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
+CONFIG_LOCK_TORTURE_TEST=m
+CONFIG_RBTREE_TEST=m
+CONFIG_INTERVAL_TREE_TEST=m
+CONFIG_PERCPU_TEST=m
+CONFIG_ASYNC_RAID6_TEST=m
+CONFIG_TEST_HEXDUMP=m
+CONFIG_TEST_STRING_HELPERS=m
+CONFIG_TEST_KSTRTOX=m
+CONFIG_TEST_PRINTF=m
+CONFIG_UNWINDER_ORC=y


Schema-abiding smart constructors / setters

Hello 👋🏼
Great work on this library.
I was curious / had a potential feature request. Has there been any exploration into generating smart constructors / setters that would allow a schema-abiding Value to be constructed? Would be nice if it could also guarantee all fields / leaves had been populated.
Thanks again for this library.

Hello! No, theres been no explorartion of any sort like that. What would the API look like? If you're just talking about a conversion Aeson.Value -> Maybe (Object schema), you could just do Aeson.parseMaybe parseJSON. We could certainly make a helper for that, but otherwise, I'm not sure what a smart constructor would entail

Thanks for the quick response.
I'm not really sure what a builder for a schema-abiding Value would look like either. But one idea could be something like ...
Given this schema:
type PersonSchema = [schema|
  {
    person: {
      name: Name,
      age: Age
    }
}
|]

We could define some paths we want to set w/ values.
schemaBuilderPerson :: Proxy '[ '("person.name", Name), '("person.age", Age) ]
schemaBuilderPerson = Proxy

In order to ensure we could encode a Schema statically, we'd need some type family to check the paths against the type level Person Schema defined above. The type family should also check if some paths haven't been specified as well (reported as errors). If valid, an empty anonymous record / HList / or empty aeson Object could be returned.
validate
  :: (ValidSchema builder schema)
  => SchemaBuilder builder
  -> Proxy schema
  -> ValidSchemaBuilder schema builder
validate = ValidSchemaBuilder mempty

Once the valid function returns a ValidSchemaBuilder schema builder, the builder portion of the ValidSchemaBuilder schema builder can be deconstructed. set would have the effect of peeling off a type in the type level list, but also populating the anonymous record / HList / object.
setPersonSchema :: Name -> Age -> ValidSchemaBuilder PersonSchema '[]
  -- ^ the act of calling `set` removes a path in the type-level path list of `ValidSchemaBuilder`.
setPersonSchema name age
  = ValidSchemaBuilder $ mempty
  & set (Proxy @ "person.name") name
  & set (Proxy @ "person.age") age

And then finally we can encode  constructed Value into bytes.
validSchemaBuilderToJSON :: ValidSchemaBuilder schema '[] -> Value

I haven't really fully fleshed out this idea, but I think the above is possible.

Interesting! Yes, that certainly looks possible, but I'm not sure we need that many new concepts. It should be possible to do something like
type PersonSchema = [schema| { person: { name: Name, age: Age } } |]

-- buildObject :: [SomeField] -> Maybe (Object PersonSchema)
buildObject
  [ field @'["person", "name"] "Alice"
  , field @'["person", "age"] 20
  ]

data SomeField = forall path a. SomeField (Field path a)
data Field path a = Field
  { path :: [String] -- value-representation of type level 'path'
  , value :: a
  }

field :: forall path a. All KnownSymbol path => a -> Field path a

I'd certainly be open to a PR of that sort
Note: somewhat related to #2.

@brandonchinn178 In your example, is the "person" type save?
If I made a typo
buildObject
  [ field @'["person2", "name"] "Alice"
  , field @'["person", "age"] 20
  ]

Would it error?

No, it wouldn't error in my example, it would return Nothing at runtime, as the object it builds up would have a person key and a person2 key, which doesnt match the PersonSchema schema.
Rereading the thread, I guess my example didn't really answer the original question. In general, this problem could be solved in two ways:

Additive - a schema starts empty and an hlist is built up
Subtractive - schema defines its full schema and all the paths, and the paths hlist is picked off (what OP was considering)

Solution (2) / OP's example could be implemented, but I don't see how the example would prevent someone from specifying a PathsSchema that doesnt match PersonSchema.
So I think (1) would be better. It could be done with something like
data PartialObject paths = UnsafePartialObject [([String], Dynamic)]

set ::
  forall path a paths.
  (ToJSON a, AllKnownSymbol path) =>
  a
  -> PartialObject paths
  -> PartialObject (path ': paths)
set a (UnsafePartialObject paths) =
  UnsafePartialObject $ (getPath @path, toDyn a) : paths

class AllKnownSymbol path where
  getPath :: [String]
instance AllKnownSymbol [] where
  getPath = []
instance
  ( KnownSymbol s
  , AllKnownSymbol ss
  ) => AllKnownSymbol (s ': ss) where
  getPath = knownSym s : getPath @ss

validate ::
  forall schema paths.
  Matches schema paths =>
  PartialObject paths
  -> Object schema
validate (UnsafePartialObject paths) = UnsafeObject (foldr insertPath Map.empty paths)
  where
    insertPath :: ([String], Dynamic) -> Map Text Dynamic -> Map Text Dynamic
    insertPath = _

The hard part here is defining the type family Matches schema paths. It might get fairly hairy, but I'm not sure.


Option --tar_file_name dropbox:///path doesn't seem to work properlky

In the submission I use
--tar_file_name dropbox:///home/vito/sbndcode_v09_59_00_e20_prof.tar --use-cvmfs-dropbox

the tarball is uploaded to RCDS, but jobs try to get it as local tarball.
In the stderr I get
...
 checking prefix / -> /
Exception:Path dropbox:///home/vito/sbndcode_v09_59_00_e20_prof.tar did not match in configuration
at:Tue Sep 27 21:57:41 2022

tar (child): .unwind_1/sbndcode_v09_59_00_e20_prof.tar: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
...

and the simple.sh script has
# -f files for input

# --tar_file_name for input

    # RCDS unpacked tarfile

      INPUT_TAR_FILE=/cvmfs/fifeuser2.opensciencegrid.org/sw/sbnd/18bd649a28f4ea976629004c83334d341442d36ca802c7f93fe6a14154b24d30
      export INPUT_TAR_FILE

      # tarfile to transfer and unpack
    mkdir .unwind_1

    ${JSB_TMP}/ifdh.sh cp dropbox:///home/vito/sbndcode_v09_59_00_e20_prof.tar .unwind_1/sbndcode_v09_59_00_e20_prof.tar
    tar --directory .unwind_1 -xzvf .unwind_1/sbndcode_v09_59_00_e20_prof.tar

      INPUT_TAR_FILE_1=`pwd`/.unwind_1
      export INPUT_TAR_FILE_1

Hm... that's weird.  The "dropbox:" string shouldn't be getting through to the simple.sh script at all, it should have been converted to a /cvmfs path...
ah..., there we go.  It was putting the converted path and the dropbox: path in.. .sigh.
         if tfn.startswith("dropbox:"):
            # move it to dropbox area, pretend they gave us plain path
            path = tarfile_in_dropbox(args, tfn[8:])
            if path:
                res.append(path)
            else:
                res.append(tfn.replace("dropbox:", ""))

        res.append(tfn)

in the if path: bit it should be setting tfn to the value, not appending the value, so the append following will put it in the result.

Ack! forgot to start a branch; pushed this on master.

Okay, fixed master. made a drobpox_fix branch..

There is still a back compatibility issue for this option against jobsub_client.
In jobsub_client the env var INPUT_TAR_FILE was set as ${CONDOR_DIR_INPUT}/mytar (this was a synlink),
but in jobsub_lite the env var INPUT_TAR_FILE is set directly to the RCDS path.
In fife_utils/fife_wrap to setup the user code from the tarball we look for the code in folders proovided this way
d = os.environ.get("INPUT_TAR_DIR_LOCAL",os.path.dirname(os.environ.get("INPUT_TAR_FILE", "/tmp/x")))

specifically os.path.dirname(os.environ.get("INPUT_TAR_FILE", "/tmp/x")) strips on dir level and we can't reach the user code.

I'm now setting INPUT_TAR_DIR_LOCAL for the rcds directory, which does not get the last component truncated.
I also included a loop to wait for it to appear, like the one in the old jobsub.

I submitted some test jobs and now tarballs are handled properly.
Thanks to get this fixed!


[Bug] Calculation of AWS Lambda estimate using cloud usage API is incorrect

From the file aws/src/lib/Lambda.ts:
return filteredResults.map((resultByDate) => {
      const timestampField = resultByDate[0]
      const wattsField = resultByDate[1]
      const timestamp = new Date(timestampField.value.substr(0, 10))
      const wattHours =
        Number.parseFloat(wattsField.value) * AWS_CLOUD_CONSTANTS.getPUE()
      const co2e = estimateCo2(
        wattHours,
        region,
        AWS_EMISSIONS_FACTORS_METRIC_TON_PER_KWH,
      )
      return {
        timestamp,
        kilowattHours: wattHours,
        co2e,
      }
    })

The number of watt hours are being reported as kilowatt hours.
I.e. the results for the AWS Lambda emissions are off by a factor of 1000.
I started looking at this because the estimates for the emissions of my team's AWS Lambda instances seemed impossibly high, and much, much higher than other services.
Of course, you could then say that the variable above is simply called wattHours even though it is actually kilowatt hours. But looking at the way this variable is calculated it seems to me to be watt hours, not kilowatt hours.
This is the way the watt hours are being extracted from Cloudwatch:
  private runQuery = async (
    start: Date,
    end: Date,
    groupNames: string[],
  ): Promise<string> => {
    const averageWatts =
      AWS_CLOUD_CONSTANTS.MIN_WATTS_AVG +
      (AWS_CLOUD_CONSTANTS.AVG_CPU_UTILIZATION_2020 / 100) *
        (AWS_CLOUD_CONSTANTS.MAX_WATTS_AVG - AWS_CLOUD_CONSTANTS.MIN_WATTS_AVG)

    const query = `
            filter @type = "REPORT"
            | fields datefloor(@timestamp, 1d) as Date, @duration/1000 as DurationInS, @memorySize/1000000 as MemorySetInMB, ${averageWatts} * DurationInS/3600 * MemorySetInMB/1792 as wattsPerFunction
            | stats sum(wattsPerFunction) as Watts by Date
            | sort Date asc`

    const params = {
      startTime: start.getTime(),
      endTime: end.getTime(),
      queryString: query,
      logGroupNames: groupNames,
    }

    const queryData = await this.serviceWrapper.startCloudWatchLogsQuery(params)

    return queryData.queryId
  }

Am I going crazy or is what is calculated here just watt hours, not kilowatt hours?
We are taking the average watts (W), multiplying by duration in hours (h) and the number of vCPUs (as estimated by looking at the memory usage). Nowhere is it divided by 1000 to actually be kWh.
So in other words, the results when estimating AWS Lambda emissions using the cloud usage API method is incorrect by a factor of a 1000.

This has been resolved here: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/commit/4d8653221ea5472ef59d7772cb7b4648a9ca8640.
Closing this issue!


Creating accounts (3/4)Error: Request failed with status code 403

Hello how to deal with this problem of 403?
Creating accounts (3/4)Error: Request failed with status code 403
at createError (D:\Downloads\duolingo-super\node_modules\axios\lib\core\createError.js:16:15)
at settle (D:\Downloads\duolingo-super\node_modules\axios\lib\core\settle.js:17:12)
at IncomingMessage.handleStreamEnd (D:\Downloads\duolingo-super\node_modules\axios\lib\adapters\http.js:322:11)
at IncomingMessage.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
config: {
transitional: {
silentJSONParsing: true,
forcedJSONParsing: true,
clarifyTimeoutError: false
},
adapter: [Function: httpAdapter],
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',

Usually just rerunning the command works for me.

Ill look into it once I am home

Okay thanks, I restarted the run and it still didn't work

我回家后会调查它，我会添加更好的错误消息和错误处理

Hello! Is your side working properly?

我回家后会调查它，我会添加更好的错误消息和错误处理

Hello! Is your side working properly?

No, it is not. I am trying to fix it right now.

Should I just make it use the browser (puppeteer) ?

Captcha bypass doesnt work ill make it use a browser

验证码绕过不起作用使其使用浏览器

Is there any way to solve it?

验证码绕过不起作用使其使用浏览器

Is there any way to solve it?

You would need to use a browser (puppeteer) to do the registering.
If anyone does that i would merge the pull request


Fix the exception from HelixHelper.getEnabledInstancesWithTag() when instance config does not exist

When cannot find instance config, Helix throw an exception instead of returning null
Catch the exception and log an error, then continue to check the next instance
This exception might happen when instance are not correctly dropped.

Codecov Report

Merging #1772 into master will increase coverage by 0.01%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master    #1772      +/-   ##
==========================================
+ Coverage   65.85%   65.87%   +0.01%
==========================================
  Files         865      865
  Lines       41941    41941
  Branches     5522     5521       -1
==========================================
+ Hits        27621    27629       +8
- Misses      12447    12453       +6
+ Partials     1873     1859      -14

Impacted Files
Coverage Δ

...linkedin/pinot/common/utils/helix/HelixHelper.java
53.33% <60%> (+0.66%)
:arrow_up:

...pinot/controller/validation/ValidationManager.java
73.27% <0%> (-6.46%)
:arrow_down:

...not/core/query/pruner/DataSchemaSegmentPruner.java
53.65% <0%> (-4.88%)
:arrow_down:

...y/aggregation/function/AvgAggregationFunction.java
92% <0%> (-4%)
:arrow_down:

...m/linkedin/pinot/common/metrics/MetricsHelper.java
68.83% <0%> (-2.6%)
:arrow_down:

...not/broker/requesthandler/RangeMergeOptimizer.java
88.7% <0%> (-1.62%)
:arrow_down:

...lix/core/realtime/PinotRealtimeSegmentManager.java
71.18% <0%> (-1.13%)
:arrow_down:

.../pinot/core/common/datatable/DataTableBuilder.java
91.06% <0%> (-1.12%)
:arrow_down:

...manager/realtime/LLRealtimeSegmentDataManager.java
69.36% <0%> (-0.78%)
:arrow_down:

.../pinot/core/segment/index/SegmentMetadataImpl.java
77.4% <0%> (-0.67%)
:arrow_down:

... and 16 more

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 7fa026f...1af85fb. Read the comment docs.


history/data/directors.js needs data from most recent board elections

history/data/directors.js provides data for the timeline of directors at http://apache.org/history/directors.html. The timeline stops before the most recent (2021) board elections.

This has been fixed a while ago, directors.js has data until 2024 and the timeline at https://apache.org/history/directors.html is correct.


Should do something with C preprocessor lines

When editing a file with CPP, it gets confused where the #if starts and gives me one of these (via shm/test-exe):
structured-haskell-mode: Parse error: Last statement in a do-block must be an expression

Or one of these:
structured-haskell-mode: Parse error: #

I'm not sure what a good solution actually is though...

Not likely to get round to this.


1.3.3 errors - RxJs imports causing errors (can't be found in dist)

Using the devtools as stated, v1.3.3 with 1.3.2 @ngrx/store. It seems to be pointing to node_modules within it's own dist folder?
I believe it's coming from the store/devtools file here:
https://github.com/ngrx/devtools/blob/master/src/store/devtools.ts#L4-L8
ERROR in<EMAIL_ADDRESS>[1] Module not found: Error: Cannot resolve module 'rxjs/add/operator/let' in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/store/dist
[1]<EMAIL_ADDRESS>2:0-32
[1]
[1] ERROR in<EMAIL_ADDRESS>[1] Module not found: Error: Cannot resolve module 'rxjs/add/operator/let' in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/devtools/dist/store
[1]<EMAIL_ADDRESS>3:0-32
[1]
[1] ERROR in<EMAIL_ADDRESS>[1] Module not found: Error: Cannot resolve module 'rxjs/add/observable/merge' in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/devtools/dist/monitors/dock-monitor
[1]<EMAIL_ADDRESS>11:0-36

Detailed error from Chrome console:
<EMAIL_ADDRESS>Module not found: Error: Cannot resolve module 'rxjs/add/operator/let' in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/store/dist
resolve module rxjs/add/operator/let in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/store/dist
  looking for modules in /Users/mp/GitHub/ngrx-rest-app/node_modules
    resolve 'file' or 'directory' add/operator/let in /Users/mp/GitHub/ngrx-rest-app/node_modules/rxjs

Same issue with 1.4.0 version:
<EMAIL_ADDRESS>is missing.
No store-backend.js resource under @ngrx/devtools under node_modules.

Any workaround?

This should be fixed in v2. Re-open if you can still reproduce.
Thanks!


Show number of replies to a squeak in action bar

This can be queried from the database.

https://github.com/squeaknode/squeaknode/pull/2144


Fix TextureRegion margin bug

Bugsquad edit : Fixed bug introduced in #27122
Forgot to apply zoom to margins when fixing/improving zooming issue of TextureRegion editor

Thanks!

Cherry-picked for 3.1.1.


cmd/go: modernize the output of 'go help packages'

Go version
go version go1.23-20240626-RC01 cl/646990413 +5a18e79687 X:fieldtrack,boringcrypto linux/amd64
Output of go env in your module/workspace:
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/usr/local/google/home/mtp/.cache/go-build'
GOENV='/usr/local/google/home/mtp/.config/go/env'
GOEXE=''
GOEXPERIMENT='fieldtrack,boringcrypto'
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/usr/local/google/home/mtp/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/usr/local/google/home/mtp/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib/google-golang'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/lib/google-golang/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23-20240626-RC01 cl/646990413 +5a18e79687 X:fieldtrack,boringcrypto'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/usr/local/google/home/mtp/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build2230501016=/tmp/go-build -gno-record-gcc-switches'

What did you do?
Run: go help packages.
What did you see happen?
The command output:
Many commands apply to a set of packages:

	go <action> [packages]

Usually, [packages] is a list of import paths.

An import path that is a rooted path or that begins with
a . or .. element is interpreted as a file system path and
denotes the package in that directory.

Otherwise, the import path P denotes the package found in
the directory DIR/src/P for some DIR listed in the GOPATH
environment variable (For more details see: 'go help gopath').

If no import paths are given, the action applies to the
package in the current directory.

There are four reserved names for paths that should not be used
for packages to be built with the go tool:

- "main" denotes the top-level package in a stand-alone executable.

- "all" expands to all packages in the main module (or workspace modules) and
their dependencies, including dependencies needed by tests of any of those. In
GOPATH mode, "all" expands to all packages found in all the GOPATH trees.

- "std" is like all but expands to just the packages in the standard
Go library.

- "cmd" expands to the Go repository's commands and their
internal libraries.

Package names that correspond to complete import paths found in the standard
library can be used as patterns without further qualification. For instance,
"fmt" refers to the standard library's package fmt, but "http" alone for
package http could not be used to refer to import path "net/http". Instead,
the complete pattern "net/http" must be used.

Import paths beginning with "cmd/" only match source code in
the Go repository.

An import path is a pattern if it includes one or more "..." wildcards,
each of which can match any string, including the empty string and
strings containing slashes. Such a pattern expands to all package
directories found in the GOPATH trees with names matching the
patterns.

To make common patterns more convenient, there are two special cases.
First, /... at the end of the pattern can match an empty string,
so that net/... matches both net and packages in its subdirectories, like net/http.
Second, any slash-separated pattern element containing a wildcard never
participates in a match of the "vendor" element in the path of a vendored
package, so that ./... does not match packages in subdirectories of
./vendor or ./mycode/vendor, but ./vendor/... and ./mycode/vendor/... do.
Note, however, that a directory named vendor that itself contains code
is not a vendored package: cmd/vendor would be a command named vendor,
and the pattern cmd/... matches it.
See golang.org/s/go15vendor for more about vendoring.

An import path can also name a package to be downloaded from
a remote repository. Run 'go help importpath' for details.

Every package in a program must have a unique import path.
By convention, this is arranged by starting each path with a
unique prefix that belongs to you. For example, paths used
internally at Google all begin with 'google', and paths
denoting remote repositories begin with the path to the code,
such as 'github.com/user/repo'. Package patterns should include this prefix.
For instance, a package called 'http' residing under 'github.com/user/repo',
would be addressed with the fully-qualified pattern:
'github.com/user/repo/http'.

Packages in a program need not have unique package names,
but there are two reserved package names with special meaning.
The name main indicates a command, not a library.
Commands are built into binaries and cannot be imported.
The name documentation indicates documentation for
a non-Go program in the directory. Files in package documentation
are ignored by the go command.

As a special case, if the package list is a list of .go files from a
single directory, the command is applied to a single synthesized
package made up of exactly those files, ignoring any build constraints
in those files and ignoring any other files in the directory.

Directory and file names that begin with "." or "_" are ignored
by the go tool, as are directories named "testdata".

What did you expect to see?
While working on #69653, @robpike and I noted that the output of go help packages appears to be in need of modernization.  A couple of key points regarding the output:

It lacks coverage of the module concept (see Gerrit review log at https://go-review.googlesource.com/c/go/+/616257 for the precise commentary on what was confusing).
The quotation style is internally inconsistent and inconsistent with some of the other long-form help outputs (e.g., go help testflag).
There are a few elements that are not quoted that should be for visual clarity.

Overall, the information feels correct for mid-2010s vintage Go but less so for today's version, so a fresh pair of eyes would help considerably.
I would be happy to contribute a secondary review of any changes to this documentation or contribute nos. 2–3.  I feel less comfortable to address Rob's commentary on the modules aspect myself.

Related Issues and Documentation

Command go > Package lists and patterns
Command go > Package lists and patterns
cmd/go: go help packages is out of date #57655
cmd/go: clarify package argument in 'go help run' summary #41830
cmd/go: TestScript/mod_outside fails at HEAD when run after make.bash #56889 (closed)
cmd/go: tests fail when GOROOT is stale #48698 (closed)
cmd/go: go list should set Package.Root to the module root directory, not GOPATH #46119 (closed)
Package build > type Package 				¶
Command go > List packages or modules
Command go > List packages or modules

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


Get helix-scripts/ up to date on on-premise machines

Our on-premise machines are not all running the current helix-scripts/ version, as shown in

Under the covers, this inconsistency could hide compliance issues because the current helix-scripts/ content may be incompatible w/ the artefacts we should be using on these machines. Updating the on-premise artefacts is however a separate problem (tactically but not strategically part of #368).
Only a subset of the held-back machines (all or most of those using the 20230628.1 version) are intentionally in that state. Others are unable to download the latest configurations e.g. osx.13.arm64.m2.perf and windows.10.amd64.19h1.tiger.perf[.open] machines are getting 403 responses.
See https://helixagentlogs.blob.core.windows.net/agent-logs/osx.13.arm64.m2.perf/dci-macm2-build-048/2023-07-14T18.19.29Z.log for example:
2023-07-14T19:05:13.415Z	ERROR  	run_client.py	scriptutil(88)	check_for_updates	Error trying to update scripts / config : Traceback (most recent call last):
  File "/private/etc/helix/scripts/helix/scriptutil.py", line 61, in check_for_updates
    self._replace_helix_settings()
  File "/private/etc/helix/scripts/helix/scriptutil.py", line 125, in _replace_helix_settings
    self._download_to(self.settings_uri, settings_path)
  File "/private/etc/helix/scripts/helix/scriptutil.py", line 148, in _download_to
    raise Exception("Failed to download '{}', the status code was {}.".format(str(uri).split("?")[0], response.status_code))
Exception: Failed to download 'https://helixosconfig.blob.core.windows.net/configuration/osx.13.arm64.m2.perf.zip', the status code was 403.

One likely root cause of the 403 problem (thanx @ilyas1974 and @garath for talking this through) is that the machines did not get new client settings before the contained SAS token expired. Unfortunately, the SAS token is in the client settings JSON file (which is in the Zip the above traceback was trying to download).
We may find other problems impacting the automation that regularly moves to the latest helix-scripts/ version.
First order of business is to turn the snapshot above into a list of impacted queues and machines. Second is to look for trends e.g. perhaps confirm the 403 problem is all we need to fix.

Release Note Category

[ ] Feature changes/additions
[x] Bug fixes
[x] Internal Infrastructure Improvements

Release Note Description
Found and resolved issues causing our on-premise machines to continue running old versions of our Helix client Python wheels.

HeartbeatExport
| where ingestion_time() > ago(3d)
| where LastHeartbeat > ago(1h)
| where ScriptVersion == "20230628.1"
| summarize max(ScriptVersion) by Queue
| order by max_ScriptVersion, Queue

shows exactly what we expect after last week's rollout reversion for some on-premise machines:

Queue name
Script version

ubuntu.1804.amd64.tiger.perf.open
20230628.1

ubuntu.1804.amd64.tiger.perf
20230628.1

osx.13.arm64.open
20230628.1

osx.13.arm64
20230628.1

HeartbeatExport
| where ingestion_time() > ago(3d)
| where LastHeartbeat > ago(1h)
| where ScriptVersion != "20230711.2" and ScriptVersion != "20230628.1" and ScriptVersion != "unset"
| summarize max(ScriptVersion) by Queue, Machine
| order by max_ScriptVersion asc, Queue asc, Machine asc

on the other hand, shows almost machines that aren't running the current helix-scripts/ version for some reason (likely not intentionally).
 Right now, I'm focusing on #368.

Let's take in this "sections"

20230127.1

All systems are set to be retired per https://portal.microsofticm.com/imp/v3/incidents/details/405548854/home
Can be disregarded for the purposes of any investigation.

20230131.7 and 20230307.1

We moved off these particular systems but never removed them from the heartbeat table. I have corrected this.

20230531.2

Need to investigate what changes we deployed around 5/31 to cause these systems not to get updates.

20230628.1

Similar to 20230531.2 - PERF and macOS , need to investigate why this class of system is not taking updates.

Let's take in this "sections"

20230127.1

All systems are set to be retired per https://portal.microsofticm.com/imp/v3/incidents/details/405548854/home
Can be disregarded for the purposes of any investigation.

20230131.7 and 20230307.1

We moved off these particular systems but never removed them from the heartbeat table. I have corrected this.

I didn't see anything w/ ScriptVersion 20230131.7 or 20230307.1 but wouldn't be surprised if your queries were more correct than mine.
For these and the to-be-retired systems using 20230127.1, why do they continue heart-beating❔ Note the | where LastHeartbeat > ago(1h) in my query.

20230531.2

Need to investigate what changes we deployed around 5/31 to cause these systems not to get updates.

👍

20230628.1

Similar to 20230531.2 - PERF and macOS , need to investigate why this class of system is not taking updates.

These are the systems we reverted to the previous helix-scripts/ version because their installed artefacts could not use the latest Python wheels. This category is entirely expected and should be fixed once we resolve #368.

/btw it was a few of the machines reporting ScriptVersion 20230531.2 where I noticed the 403 errors in the agent logs. Your suspicion about the configuration download SAS token expiring before the machines updated may explain that. But, it's oddly consistent — seemingly (from a brief glance at the machine counts) affecting all machines in a few queues.

I have a feeling that because of their "ago" the first two groups of systems (ScriptVersion 20230131.7 or 20230307.1) are older than what we keep in Kusto. The heart beat table doesn't delete anything we've designated as "on premises" so they can and will stick around.

RE: ScriptVersion 20230127.1 - Retirements. I did not place a high priority of getting the systems retired as we were going through the re-org at the time. Typically we do try and remove systems we plan on retiring from Helix within a relatively short period of time.

ScriptVersion 20230531.2 is indeed an experienced SAS token (left over from the secret rotation ~6/5. The main reason it hasn't been addressed is because the SAS token in question only effected Helix updates to the systems - customer workloads continue to run without issue.

Resolved the script version issues on all systems expect those with version 20230531.2.
Currently working on them.
https://portal.microsofticm.com/imp/v3/incidents/details/408185319/home for the Ubuntu based systems.

All but 12 of the systems have been resolved.
I have created https://portal.microsofticm.com/imp/v3/incidents/details/411459136/home to have DDFUN address these remaining systems.

All systems have not been updated.


Reproducible Builds

Your app was just added at IzzyOnDroid – as a reproducible build even, congrats! And be welcome to pick a badge and link to it e.g. from your Readme here :smile:
At IzzyOnDroid we support Reproducible Builds (see: Reproducible Builds, special client support and more at IzzyOnDroid). I was able to successfully generate an APK from your repo here, and even get it reproducible – but that required some manual steps which need to be repeated for each new release – because you set versionCode from a variable that cannot be reproduced. Could you please make that a static number, or at least use something that can be reproduced at any time (so no, something based on build timestamps would make it worse)?
Thanks in advance!

Hi, thanks for adding my app!
Will this fix the issue https://github.com/nikashitsa/polar-alert-android/commit/00e5f143be82349d69c344b3827abf27b7e076f2 ?

thanks for adding my app!

Gladly!

Will this fix the issue https://github.com/nikashitsa/polar-alert-android/commit/00e5f143be82349d69c344b3827abf27b7e076f2 ?

Thanks! And yes, I'd say it should (actually, that was one of the things coming to mind for me as well). Does git rev-list --count HEAD count up to the currently checked-out commit – or to the latest commit in the repo? I know rev-list works up the parent commits, but am a little confused by the HEAD currently… (checks notes) Ah: HEAD resolves to the currently checked-out commit hash. Well, then I'd again say: Yes – and Thanks! The next release will show I guess :wink:


Don’t spam console

Description

Whenever there’s a database error, it always constantly spams my console, maybe remove that and replace it with something like this LuckPerms Database Is Offline! or something.
Proposed behaviour

This could work by changing it to something like this LuckPerms Database Is Offline!.

IMO, I dont see any benefit in thig change. The errors shown is important for debugging and shouldn't be cut to a single line so people can ignore them.

The "spam" in your console contains valuable information about what the problem is, and likely also hints what to do to fix it. I don't know why you would want to remove that... :)