[Bug] Improve Query / API Timeout error

Description
When a query / API times out, the message is to check your internet connection
Steps to reproduce the behaviour:

create a query
set the timeout to 10 ms
execute the query
See the error

The error should say "QueryName took longer than 10ms to execute"

i would like to work on this

@rohitgeddam go for it!

@rohitgeddam : You can experiment with the following :
In file NewActionServiceImpl, function executeAction, we use the following :
.timeout(Duration.ofMillis(timeoutDuration))
Instead of the above, we should add our own fallback like below :
.timeout(Duration.ofMillis(timeoutDuration), Mono.error(new AppsmithException(AppsmithError.PLUGIN_EXECUTION_TIMEOUT)))
Please edit the PLUGIN_EXECUTION_TIMEOUT error to include the name of the query and pass the name as a parameter in the above Mono.error call.
In GlobalExceptionHandler, PLUGIN_EXECUTION_TIMEOUT is being handled separately.
I am hoping this change would solve this issue.
Let me know if you hit any roadblocks or have any other doubts I can help with.
Good luck!

@rohitgeddam Since you haven't raised a PR in 6 days, I'm unassigning this issue. I'm sure you're busy elsewhere. Please do come back to this project whenever you have time again.

@trishaanand I see that the executionMono is mapping another type of Exception into an AppsmithPluginException. Since the timeout throws its own error, can we simply map that into an exception as well? This would be in place of using a fallback.

@nidhi-nair : That sounds fair. Let's throw an AppsmithPluginException in this case as well.


Is there a way to manually set SERVERLESS_ALIAS?

I am not using the sls alias plugin, but am deploying to a fixed alias (using this for serverless-plugin-canary-deployments).
How can I get the warmup plugin to use that alias? Ideally, this would be a setting on the plugin itself, or it would work with the canary plugin to figure that out.
Setting SERVERLESS_ALIAS on the provider level didn't work.

Hi @abadyan-vonage ,
What do you mean with Setting SERVERLESS_ALIAS on the provider level?
Setting an environment variable called SERVERLESS_ALIAS should work
(see https://github.com/FidelLimited/serverless-plugin-warmup/blob/master/src/index.js#L327)
So something like SERVERLESS_ALIAS=my_alias sls deploy should work. Wasn't that the case?

I tried setting the env var as part of the serverless.yml. I don't have direct access to env vars of the warmup lambda, so tried doing on the provider level:
provider:
  name: aws
  runtime: python3.6
  stage: ${opt:stage, 'dev'}
  region: ${opt:region, 'us-east-1'}
  deploymentBucket:
     ...
  vpc:
     ...
  environment:
    SERVERLESS_ALIAS: myAlias

That's not how you set the alias in serverles.
The environment field in the provider section contains the environment variables that will be passed to your lambdas, not the ones used for deployment.
You need to have the SERVERLESS_ALIAS variable set in your machine from where you run the serverless commands.
So you have to options:

export SERVERLESS_ALIAS=my_alias so the alias env var is set on the machine
SERVERLESS_ALIAS=my_alias sls deploy so the alias env var is set when the serverless command is run.

Let me know if that helps.

@juanjoDiaz So setting the variable in the SERVERLESS_ALIAS=my_alias sls deploy form did make the warmup plugin warmup the correct alias during deployment (using prewarm: true) but the warmup lambda still doesn't get it as an env var leading to all consequent calls to still go to $LATEST.

Sorry for the delay.
4.6.3-rc.1 should fix this issue so the env variable injected by the sls alias plugin is automatically used by the warmup function and the prewarming without the need of using a local env variable or adding it to the serverless.yaml file.
Could you try and let me know?

@juanjoDiaz thanks for the fix!
I am not using the alias plugin so would like to just pass in the env var manually. Where should it be defined with the new change you have made?

In an env variable in serverless.yaml.
You can use the global environment setting so it's passed to all lambdas as you did on https://github.com/FidelLimited/serverless-plugin-warmup/issues/161#issuecomment-503461441.
Or if you want to pass it only to the plugin you can do:
provider:
  name: aws
  runtime: python3.6
  stage: ${opt:stage, 'dev'}
  region: ${opt:region, 'us-east-1'}
  deploymentBucket:
     ...
  vpc:
     ...
  custom:
    warmup:
      environment:
        SERVERLESS_ALIAS: myAlias

Thanks @juanjoDiaz, I can confirm this has been resolved with the new version.


Room limits

I want to thank all the unit tests that helped me through these troublesome times. I owe them the honour of bringing you all this PR today.

GitHub pls let me review

GitHub pls let me review


Fix missing path for MacOS After Effects 2024 in autofind.js

Error: you should provide a proper path to After Effects' "aerender" binary
    at init (/snapshot/nexrender/packages/nexrender-core/src/index.js)
    at start (/snapshot/nexrender/packages/nexrender-worker/src/index.js)
    at Object.<anonymous> (/snapshot/nexrender/packages/nexrender-worker/src/bin.js)
    at Module._compile (pkg/prelude/bootstrap.js:1926:22)
    at Module._extensions..js (node:internal/modules/cjs/loader:1166:10)
    at Module.load (node:internal/modules/cjs/loader:988:32)
    at Module._load (node:internal/modules/cjs/loader:834:12)
    at Function.runMain (pkg/prelude/bootstrap.js:1979:12)
    at node:internal/main/run_main_module:17:47

I've added 'After Effects 2024' to darwin.
When start nexrender on MacOS, an error message appears.
I noticed that 'After Effects 2024' is missing from the array.

Oh, it does indeed. Thanks for the fix!


[TEST] Use octez node to bootstrap

@bkontur @adonagy Now we don't use Tezedge data directly in indexers tests. Please have a look and merge it.


docker.client.strategy should be able to read from the classpath (#3887)

What's the reasoning behind this?
The strategy is deliberately not read as a classpath config setting, because it's entirely possible for different developers on the same team to have different Docker setups.
If this setting can be read from the classpath, there's a risk that one developer on a team may cause problems for other team members...

The reason is that our continuous integration pipeline is built by our operation and maintenance personnel, they only support pulling code and executing mvn clean test ..., the only thing we can modify is the parameters of mvn, so we have no way to modify the environment The strategy is configured by means of variables or user directories.
For team development, not all developers have their own local Docker environment, and even if the Docker environment is installed locally, they do not have network access (Great Wall of China). So we have a public remote Docker server, which can access the external registry and quickly pull images. The team can use this server to achieve a common environment. At the same time, we hope to use it to solve the shortcomings of our current pipeline.
This is no problem, if we set the priority of the configuration file, just like Spring Boot.

The reason is that our continuous integration pipeline is built by our operation and maintenance personnel, they only support pulling code and executing mvn clean test ..., the only thing we can modify is the parameters of mvn, so we have no way to modify the environment The strategy is configured by means of variables or user directories.
For team development, not all developers have their own local Docker environment, and even if the Docker environment is installed locally, they do not have network access (Great Wall of China). So we have a public remote Docker server, which can access the external registry and quickly pull images. The team can use this server to achieve a common environment. At the same time, we hope to use it to solve the shortcomings of our current pipeline.
This is no problem, if we set the priority of the configuration file, just like Spring Boot.

@jizhuozhi

the only thing we can modify is the parameters of mvn, so we have no way to modify the environment

FYI Surefire allows setting the environment variables: http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#environmentVariables

For team development, not all developers have their own local Docker environment, and even if the Docker environment is installed locally, they do not have network access (Great Wall of China)

Testcontainers will try to use all available strategies, and that field is just the "cached" value, to avoid having to test all strategies again. Just make sure that your strategy is properly registered with the SPI. This way, developers with local Docker will use the default strategy, but those who are using your remote Docker will fallback to your custom strategy.
Also, you don't need a custom strategy for it, you can just set DOCKER_HOST and other variables.

@bsideup

FYI Surefire allows setting the environment variables: http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#environmentVariables

Thanks, it's working for me.

Also, you don't need a custom strategy for it, you can just set DOCKER_HOST and other variables.

It's right, my original requirement just using environment variables or configuration files to setup DOCKER_HOST!

@jizhuozhi you can also create a $HOME/.docker-java.properties file and set the properties here:
https://github.com/docker-java/docker-java/blob/master/docs/getting_started.md#properties-docker-javaproperties
Since it looks like there are good alternatives, I suggest we close this PR. WDYT?

@bsideup of cause


Single WSL2 localhost port can't be accessed from Windows side

Environment
Windows build number: 10.0.19041.0
Your Distribution version: Ubuntu 20.04
Whether the issue is on WSL 2 and/or WSL 1: Linux version 4.19.84-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Nov 13 11:44:37 UTC 2019

Steps to reproduce

Create and start a new create-react-app app:

npx create-react-app my-app
cd my-app
npm start

Try to access it from the browser using the localhost address: localhost:3000
-> The browser can't connect
Re-start the app by specifying a different port PORT=3001 npm start
-> The browser can connect

Further details
I expect that this is due to specific configuration on my machine, but I don't know what is wrong. I disabled Windows Firewall and it still doesn't work.  Accessing the react app through the ip address + port works as expected. Restarting Windows and WSL 2 (multiple times) did not help.
I assume that this issue is similar to issues #5497 and #5298, but I can access servers that are running on different ports (e.g. 5000, 8080, 3001, etc.).
Any workaround would be appreciated. If possible I would like to not need to get into the insider program again, I am hoping I can stay on the stable 2004 version.

Open PowerShell and post the output of:
netsh int ipv4 show excludedportrange protocol=tcp
netsh int ipv4 show dynamicport tcp

C:\Users\pjura> netsh int ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
      5357        5357
     50000       50059     *
     55651       55750
     55751       55850
     55991       56090
     56091       56190

* - Administered port exclusions.

C:\Users\pjura> netsh int ipv4 show dynamicport tcp

Protocol tcp Dynamic Port Range
---------------------------------
Start Port      : 49152
Number of Ports : 16384

thanks, tcp dinamic assignation is not the problem then.
Try HOST=<IP_ADDRESS> npm start and see if localhost:3000 works

No, sadly HOST=<IP_ADDRESS> npm start does not work.

In Resource Monitor -> Network tab- > Listening ports can you see if there is an exe listening on port 3000?

Thanks for helping!
Yes it listing a process, although I have neither anything open with port 3000 or 3100. I also can't find any firewall rule which restricts port 3000 🤔
This is a screenshot of the resource monitor view: https://imgur.com/8qTO4Q6

Some service is using both ports. To know the service on the same Resource Monitor go to CPU tab -> Services, order by PID and look for PID 4248.

What Ono said. Or from powershell, using TCP port 5040 as example, which is the Connected Device Platform Service
PS C:\> (Get-WmiObject -Class Win32_Service | where ProcessId -eq (Get-Process -Id (Get-NetTCPConnection -LocalPort 5040).OwningProcess).Id).Name

Thanks a lot for the help. 👍 🙏
It appears that the IP Helper service was the culprit and after disabling it the port worked again. I assume this did not have anything to do with WSL 2 then, therefore I'm closing the issue.

What Ono said. Or from powershell, using TCP port 5040 as example, which is the Connected Device Platform Service
PS C:\> (Get-WmiObject -Class Win32_Service | where ProcessId -eq (Get-Process -Id (Get-NetTCPConnection -LocalPort 5040).OwningProcess).Id).Name

Thanks a million for this!

Just in case it happened to someone else and there were no such ports open during in-windows inspection, but inside WSL port was listened: it helped me simply to restart WSL by wsl --shutdown {name} and starting it then again.

Just in case it happened to someone else and there were no such ports open during in-windows inspection, but inside WSL port was listened: it helped me simply to restart WSL by wsl --shutdown {name} and starting it then again.

Restarting WSL was also the solution that I needed! The PS command is still very useful for troubleshooting this though!

wsl --shutdown

This solved my issue, thank you

wsl --shutdown

This solved my issue, thank you

IP Helper service
Turning off IP helper was the solution for me!

Ive tried a bunch of other things, but I had to disable IP Helper service to be able to access my stack on localhost:4200 on windows 11, wsl2. weird that this seems to be the issue, i dont think I had this problem with win 10 or running natively on ubuntu.
I wonder if there is some conflict here with the service that needs a more serious look at.

This worked for me
https://superuser.com/a/1671709/28261

In my case, my port is not allowed. After I add a new rule allowing the port in window firewall, it works. https://pureinfotech.com/open-port-firewall-windows-10/


Configurable Runtime

Description

Adds Runtime and LocalRuntime to make the runtime configurable.
yew::platform::time for timer support.
Adds SSR Benchmark (Benchmark will only work if master has benchmark binary present).

Checklist

[x] I have reviewed my own code
[ ] I have added tests

Sample: https://github.com/yewstack/yew/runs/7166129506?check_suite_focus=true#step:7:386
This benchmark will continue to fail until master has a benchmark present.

I found this pull request is too big to review and contains multiple somewhat independent changes, so I have decided to spilt it into multiple pull requests.

This is now self-contained enough to be reviewed on its own, I assume?

Yes.

I have updated the examples to process requests within Yew Runtime instead of the default tokio runtime.
This allows the application to be rendered on the same thread as the request is processed.
This increases performance significantly for ServerRenderer under certain environment where switching between threads is expensive (e.g.: in VM).

Can you also explain/document why this is needed? Is it to allow future support for other runtimes?

This allows users to set their own number of threads.
num_cpus usually detects the correct threads to spawn.
But sometimes users may want to control this themselves.

Also, how does it tie with https://github.com/yewstack/yew/issues/2839?

This exposes Runtime and LocalHandle as a public type.
Which means that now ServerRenderer uses public API for spawning tasks.


Add in last 4 methods from Valve wiki, also redo entire test suite in mocha

Hello,
I added the last 4 methods from the valve wiki, completing #9. While doing these methods I also undertook a whole remake of the test suite mainly because I found it a little annoying, I think it's a major improvement over the old tests, but if you want I can remove it.
The diff is quite large because I added 2 dev dependencies and 1 normal dependency but here are the important things to note:

Last 4 methods added from valve wiki
Deleted old tests, also renamed folder from tests to test (because mocha runs the 'test' folder by default)
Added newtests.js which has all the new tests in mocha, you can run them using npm install to install the extra modules then npm test to run the script.
I added one normal dependency, the qs library for string parsing. It has pretty much the same functionality as the other module, except it has support for parsing arrays with indices such as array[0]=something&array[1]=something which I needed for one of the methods I added.
I also cleaned up some random non-functioning or just odd code that I found, mostly removing random brackets and solidifying the object validations for each method.

And I do apologise for not making the commits well structured, I was moving a little bit between computers so had to commit at odd times.
That's about it; if this gets merged I will probably make a new PR in the following days with the remaining methods from the TF2 wiki.

Vincent

EDIT: I just realised I need to update the docs, I'll do that ASAP (today or tomorrow)

This is awesome.  biggest thing i think is adding node_modules to the gitignore, that'll make the merge a lot easier - I'll take a look at merging it in asap :)

I added it to the gitignore, but the diff still shows all the old files. Should I make a separate PR so you can view the diff nicely?

Nevermind, I just had to remove the files from my local cache then push those changes. Diff looks fine now

Awesome, I'll merge this later today.  I'll make sure to remove your API key, but you will probably want to go invalidate that in steam since its leaked in this commit.

Oh haha, thanks for the heads up. I thought I added it to gitignore... weird. Anyway, thanks


Propel ignores tabletype when generating migrations

I get this problem with symfony, but I think it's related to Propel itself.
When generating a migration, tables are created with ENGINE=MyISAM even if  setting is propel.mysql.tableType = InnoDB

I have an ongoing solution in the vendor_migration branch in my clone. Will update here.

@fzaninotto could you PR your work in your vendor_migration branch?


[WIP] GitReleaseManager Addin for Cake

GitReleaseManager commands that will be included in this first release of GitReleaseManager support

[x] Create
[x] AddAsset
[x] Close
[x] Publish
[x] Export
[x] Documentation

NOTE: Only the commands that apply an action will be included in this release, as these are the most likely commands that are needed within a build script.
GitReleaseManager commands which are unlikely to be implemented in this PR:

Init
Showconfig

@patriksvensson  @devlead ok, I "think" that this is ready for review as well.
There is an issue with the AddAssets Command, but this looks like it is a bug in GitReleaseManager itself, and I don't think that it should hold up the merge.

@gep13 This looks good to me :+1:
@devlead Any comments?

@patriksvensson @gep13 this looks solid to me, get branch is up-to-date with the base branch and remove WIP.

Done and done :+1:

Merged, thanks @gep13 :+1:

Sweet!


New_version

This pull request making problems

AI Code Review is in progress (usually takes <10 minutes unless it's a very large PR).


Search for files in /data partition too

Why would that be an interesting directory?

Why would that be an interesting directory?

For production server directories not following partitions /var and /opt, most of the new partitions other than root are named with /data. We use mostly GCP servers, and since only root directories are cloned, we created new /data partitions to install more applications.
I had already scanned for log4j libraries using the find command, and when this script did not flag those libraries, I tried to read it and thus, came to know that it skips the /data partition. I am also planning to give a command-line option to select extra directories to scan.

yes, please add it as a commandline option instead


Can't run genomics example

Running DeepExplainer  example with genomics data results in following:

TypeError                                 Traceback (most recent call last)
 in ()
14 seqs_to_explain = onehot_data[[0,3,9]] #these three are positive for task 0
15 dinuc_shuff_explainer = shap.DeepExplainer((keras_model.input, keras_model.output[:,0]), shuffle_several_times)
---> 16 raw_shap_explanations = dinuc_shuff_explainer.shap_values(seqs_to_explain)
17
18 #project the importance at each position onto the base that's actually present
1 frames
/usr/local/lib/python3.6/dist-packages/shap/explainers/deep/deep_tf.py in shap_values(self, X, ranked_outputs, output_rank_order, check_additivity)
316             else:
317                 model_output = self.model(X)
--> 318             for l in range(len(self.expected_value)):
319                 if not self.multi_input:
320                     diffs = model_output[:, l] - self.expected_value[l] - output_phis[l].sum(axis=tuple(range(1, output_phis[l].ndim)))
TypeError: object of type 'NoneType' has no len()

I'm having this issue on Colab with tf 1.15.2 and on Jupyter with tf 1.13.1 and Python 3.6.6.
With tf 2.3.0 on Colab there's different issue:

NameError                                 Traceback (most recent call last)
 in ()
13
14 seqs_to_explain = onehot_data[[0,3,9]] #these three are positive for task 0
---> 15 dinuc_shuff_explainer = shap.DeepExplainer((keras_model.input, keras_model.output[:,0]), shuffle_several_times)
16 raw_shap_explanations = dinuc_shuff_explainer.shap_values(seqs_to_explain)
17
1 frames
/usr/local/lib/python3.6/dist-packages/shap/explainers/deep/deep_tf.py in init(self, model, data, session, learning_phase_flags)
105             if type(model) is tuple or type(model) is list:
106                 assert len(model) == 2, "When a tuple is passed it must be of the form (inputs, outputs)"
--> 107                 self.model = Model(model[0], model[1])
108             else:
109                 self.model = model
NameError: name 'Model' is not defined

Would appreciate any tips!

Try setting check_additivity=False

I have the same NameError. Did you ever figure out how to solve this?

It was fixed in #1407. You could pip install git+https://github.com/slundberg/shap to install from master branch, or wait till the next version release.

Thank you. I now get an error for DeepLIFT "cannot import name 'traverse_edges'"

Hi! I know this has been sitting for a while, but I wanted to run this example myself today and managed to find the final fixes to reproduce the original results.
I've put together a Colab Notebook here that works start-to-finish. Please feel free to drop me a message if you have any questions!


How to download low resolution video from vimeo and dailymotion. e.g.1280X720?

Hi,
I am trying by using following query , but getting error
youtube-dl   -v  -f hls-480-3  http://www.dailymotion.com/video/x5xx3z4 -o   E:/xampp/htdocs/videoconverter/aa7F.mp4
thanks,

http://proxy-11.sg1.dailymotion.com/sec(d3135bb81ef763592236deccdda53304)/video/800/303/359303008_mp4_h264_aac_fhd_2.m3u8#cell=sg1&hls_heuristic=1&hls_startFragPrefetch=1

Carefully read new issue template and provide all requested information.


[MCControler] Update main robot name

This PR allows to rename the main robot declared in mc_rtc.yaml as the one named in a controller configuration in robots

Hi @antodld
If I understand correctly, what you are trying to do is:

If the value of MainRobot is a loadable module then you treat it as before
Otherwise you look into every loaded controller configurations to find if it's configured under the robots entry and you use the module entry in there to load the robot

So for example:
MainRobot: MyJVRC
robots:
  MyJVRC:
    module: JVRC1

would load JVRC1 as the main robot but rename it ``MyJVRCinstead of the default ofjvrc1`
This poses at least one problem, say you have a controller that supports multiple robots and you wish to rename a few, so you would have something like:
MainRobot: MyJVRC # sometimes you switch to MyHRP4CR
robots:
  MyJVRC:
    module: JVRC1
   MyHRP4CR:
     module: HRP4CR

with this configuration and your patch, both modules are always loaded
I would suggest to write a patch that allows this syntax:
MainRobot:
  name: MyName
   module: MyModule

To solve this I suggest to add a std::optional<std::string> main_robot_module_name entry into the global configuration and treat config("MainRobot")("module") as config("MainRobot")

Hello @gergondet
The behavior described in your multi-robot example is the desired one.
With this PR, whatever the main robot you chose in your mc_rtc.yaml configuration file (whether MyJVRC1 or MyHRP4CR), the controller will always have 2 robots loaded with the same name, in opposition to the current state where the robot loaded in MainRobot is always named after its robot module.

the controller will always have 2 robots loaded with the same name

Just to clarify, that's two robots at the same time at all times right?
With the syntax I proposed you can get the same effect:
MainRobot:
  name: MyJVRC
  module: JVRC1
robots:
  MyJVRC:
    module: JVRC1
  MyHRP4CR
    module: HRP4CR

Would get you the same robots as:
MainRobot:
  name: MyHRP4CR
  module: HRP4CR
robots:
  MyJVRC:
    module: JVRC1
  MyHRP4CR
    module: HRP4CR


Alert on high latencies

https://github.com/openshift-scale/cerberus/pull/64 will enable us to get the time taken by various Cerberus checks which are basically calls to the Kube/OpenShift API server. We need to establish limits on the latency for each check after which Cerberus will start logging about the observed high latencies.
Requests tend to take more time on a large scale cluster ( 250 - 2000 nodes ) but we need to establish the thresholds after which Cerberus should start alerting. This will help the user in tuning the cluster in addition to the explaining the reason for Cerberus taking more time to finish the checks in each iteration.

@yashashreesuresh @paigerube14 @mffiedler @jtaleric Thoughts?


AmiGO does not display the current definition of biological_process

While working with a student today (@giacomodecolle), I discovered that AmiGO does not display the current definition of biological_process (GO:0008150).  The current definition of biological process resulted from a discussion here as implemented by this PR on February 27, 2023.
Oddly enough, QuickGO does display the current definition of biological process (GO:0008150), and the term history shows that definition was changed on 2023-03-06.
At the bottom of the AmiGO page, it states "Last file loaded on 2023-10-10."  Perhaps this refers to the annotations and not the ontology, although I always thought it referred to both.  Nevertheless, it is of some concern that AmiGO is displaying an old definition of biological_process, and perhaps of other terms in BP.
Thanks, Alex
(in the old days, I would be concerned that this is a browser cache issue, but the old definition is shown on three different browsers on my computer, and on my student's computer, so it seems rather unlikely to be an issue on the client side)

@pgaudet I’ll be able to dig more into this when I get back, but these are unlikely to be amigo issues. My best guess at this point is that these are to either due to the ontology build (and how things get “materialized”) or the pipeline interaction with the ontology build. On Nov 22, 2023, at 04:58, pgaudet @.***> wrote:
@kltm Any idea why this has not been updated? This changed was merged back in March 2023.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Definition in "go-edit.obo":
A biological process is the execution of a genetically-encoded biological module or program. It consists of all the steps required to achieve the specific biological objective of the module. A biological process is accomplished by a particular set of molecular functions carried out by specific gene products (or macromolecular complexes), often in a highly regulated manner and in a particular temporal sequence.
We still have the release on skyhook, so I can see "/release/ontology/go-basic.obo":
A biological process is the execution of a genetically-encoded biological module or program. It consists of all the steps required to achieve the specific biological objective of the module. A biological process is accomplished by a particular set of molecular functions carried out by specific gene products (or macromolecular complexes), often in a highly regulated manner and in a particular temporal sequence.
Then looking at the definition in AmiGO:
A biological process represents a specific objective that the organism is genetically programmed to achieve. Biological processes are often described by their outcome or ending state, e.g., the biological process of cell division results in the creation of two daughter cells (a divided cell) from a single parent cell. A biological process is accomplished by a particular set of molecular functions carried out by specific gene products (or macromolecular complexes), often in a highly regulated manner and in a particular temporal sequence.
Which is wrong.
The index builder uses skyhook "/release/ontology/extensions/go-gaf.owl". That's based on (correct me if I'm wrong @balhoff ) go-gaf-edit.ofn, which pulls in http://purl.obolibrary.org/obo/go/extensions/go-plus.owl, which resolves to:
sjcarbon@moiraine:/tmp/foo$:) http --headers http://purl.obolibrary.org/obo/go/extensions/go-plus.owl
HTTP/1.1 302 Found
CF-Cache-Status: DYNAMIC
CF-RAY: 82ced5cdb9d967fa-SJC
Connection: keep-alive
Content-Type: text/html; charset=iso-8859-1
Date: Tue, 28 Nov 2023 01:28:36 GMT
Location: http://current.geneontology.org/ontology/extensions/go-plus.owl
Server: cloudflare
Transfer-Encoding: chunked

So that's obviously going to cause weird lag issues.
I think this is then
https://github.com/geneontology/pipeline/issues/162
https://github.com/geneontology/go-ontology/issues/18870
Any thoughts here @balhoff ?

Actually, go-gaf.owl has both definitions! :-( So this is an ontology build problem. I bet this is leaking in from an import.

Hopefully will be fixed by https://github.com/geneontology/go-ontology/pull/26510.

@balhoff

@kltm when go-gaf.owl is built, it uses a catalog XML that locates http://purl.obolibrary.org/obo/go/extensions/go-plus.owl in the local file, instead of downloading it from the web. Also, the version on the web contains the new definition.

Ah, I didn't realize that was implemented. Re-reading the external ticket, it's apparent that I was referring to a different file.

Hopefully will be fixed by geneontology/go-ontology#26510.

Great! We can take a look at how this goes on snapshot.

@balhoff Just to clarify, looking at your https://github.com/geneontology/go-ontology/pull/26510, was there a change to the imports/build to make sure that we're not getting old ontology information in there? Eyeballing it, it just looked like a file update, rather than a build change.

This was it:

Or is it that gorel itself contains (contained) extraneous info that was basically clobbering out the updated/correct/recent info?

But you are right that I did not make a build change to prevent this in the future. gorel is slated for obsoletion, but this is not complete.

Okay, that makes sense.
To clarify, that's like https://github.com/geneontology/go-ontology/issues/25140 and https://github.com/geneontology/go-ontology/issues/19497?


x/crypto/bcrypt: use base64.NoPadding

Fixes golang/go#35810

Fixes golang/go#35810

https://www.cryptocaptrades.com

This PR (HEAD: 8add495) has been imported to Gerrit for code review.
Please visit https://go-review.googlesource.com/c/crypto/+/356469 to see it.
Tip: You can toggle comments from me using the comments slash command (e.g. /comments off) See the Wiki page for more info

https://www.cryptocaptrades.com

This PR (HEAD: 8add495) has been imported to Gerrit for code review.
Please visit https://go-review.googlesource.com/c/crypto/+/356469 to see it.
Tip: You can toggle comments from me using the comments slash command (e.g. /comments off) See the Wiki page for more info

Message from Ian Lance Taylor:
Patch Set 1:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/356469. After addressing review feedback, remember to publish your drafts!

https://www.cryptocaptrades.com

gopherbot

https://www.cryptocaptrades.com

This PR (HEAD: 88fceb2) has been imported to Gerrit for code review.
Please visit https://go-review.googlesource.com/c/crypto/+/356469 to see it.
Tip: You can toggle comments from me using the comments slash command (e.g. /comments off) See the Wiki page for more info

https://www.cryptocaptrades.com

Message from Alexander Yastrebov:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/356469. After addressing review feedback, remember to publish your drafts!

https://www.cryptocaptrades.com

Message from Ian Lance Taylor:
Patch Set 2: Run-TryBot+1
Please don’t reply on this GitHub thread. Visit golang.org/cl/356469. After addressing review feedback, remember to publish your drafts!

https://www.cryptocaptrades.com

Message from Go Bot:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/356469. After addressing review feedback, remember to publish your drafts!

https://www.cryptocaptrades.com

Message from Go Bot:
Patch Set 2: TryBot-Result+1
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/356469. After addressing review feedback, remember to publish your drafts!

https://www.cryptocaptrades.com


Update Magic Connect Connector to use Magic Connect's Modal UI

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Update Magic Connect Connector to use the Magic Connect Modal.

What is the current behavior? (You can also link to an open issue here)

Currently, Magic Connect Connector uses the same modal UI as the one for Magic Auth Connector
As mentioned here: https://github.com/EveripediaNetwork/wagmi-magic-connector/issues/48

What is the new behavior (if this is a feature change)?

The updated behavior now connects with Magic Connect's modal by using await this.magic.wallet.connectWithUI().

Other information:

Thanks for contributing ! looking really impressive. we will review this and merge as soon as possible.

Merged ! this should be reflected in<EMAIL_ADDRESS>


Something wrong in the latest version of Google

[图片]
if there is many switches,  something wrong  has happened in the latest version of Google.page would be out of order.
you can mail to<EMAIL_ADDRESS>


Introduce Team to GitHub

Introduce team to GitHub

Hello Team!

Hello my name is Craig A, I am currently a college student who is studying Computer and informations sciences! Besides programming I like photography cheers!

Hey welcome! What's your profile on GitHub? We're getting the team started
there.
Best,
Brent
On Tuesday, July 12, 2016, Craig<EMAIL_ADDRESS>wrote:

Hello my name is Craig A, I am currently a college student who is studying
Computer and informations sciences! Besides programming I like photography
cheers!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/BeehiveNGO/Beta/issues/3#issuecomment-232196583, or mute
the thread
https://github.com/notifications/unsubscribe/AMSHKaw2PSLR7yc0wt2qH3B8y26c4kYOks5qVA_1gaJpZM4JILAW
.

Profile on github? This is my profile.

Sorry am on my mobile, will send you invite later today to repo
On Tuesday, July 12, 2016, Craig<EMAIL_ADDRESS>wrote:

Profile on github? This is my profile.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/BeehiveNGO/Beta/issues/3#issuecomment-232199688, or mute
the thread
https://github.com/notifications/unsubscribe/AMSHKUcsmD2SnyD5xmHtz1CKIo8Qb1XHks5qVBMqgaJpZM4JILAW
.

Hey cool, I didn't realize comments thread to email. I started a Contribute repo, check it out and feel free to add some issues there to help us set it up


ament_black: 0.2.2-2 in 'iron/distribution.yaml' [bloom]

Increasing version of package(s) in repository ament_black to 0.2.2-2:

upstream repository: https://github.com/botsandus/ament_black.git
release repository: https://github.com/botsandus/ament_black-release.git
distro file: iron/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.2.2-1

ament_black
* Nacho/fix ci tests (#5 <https://github.com/botsandus/ament_black/issues/5>)
  * Add missing test dependency
  * pre-commit
  * Add pre-commit workflow
  * Add CLI test to make sure the package has been properly installed
  * Remove ament hooks
  * Add missing apt-python dependency
  Not sure if it's necessary ...
  * Fix CI pre-commit
  The CI error was fixed in: https://github.com/psf/black/issues/2964
  Thus, we need black >22.3.0
* Contributors: Ignacio Vizzo

ament_cmake_black
* Nacho/fix ci tests (#5 <https://github.com/botsandus/ament_black/issues/5>)
  * Add missing test dependency
  * pre-commit
  * Add pre-commit workflow
  * Add CLI test to make sure the package has been properly installed
  * Remove ament hooks
  * Add missing apt-python dependency
  Not sure if it's necessary ...
  * Fix CI pre-commit
  The CI error was fixed in: https://github.com/psf/black/issues/2964
  Thus, we need black >22.3.0
* Contributors: Ignacio Vizzo

Guys, how can I locally test this? I'm running the tests in a completely isolated docker environment with this package is the only one there, colcon build and colcon test are passing...
What I'm doing wrong?
Thanks in advance!

Hi @nachovizzo, you can run the tests that CI is running on your local machine by following https://github.com/ros/rosdistro/blob/master/CONTRIBUTING.md#unit-testing, is that what you wanted to test?

@quarkytale, thanks for the fast reply.
Not really,  the package tests that the build farm would run. For example, I missed adding ament_xmllint in the pcakage.xml and the test failed, but locally was working (I prefer the CI behavior). But would like to reproduce this locally
(Stacktrace
ImportError while importing test module '/tmp/ws/src/ament_black/ament_black/test/test_xmllint.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
test/test_xmllint.py:16: in <module>
    from ament_xmllint.main import main
E   ModuleNotFoundError: No module named 'ament_xmllint'

NOTE: This test-issue was address in https://github.com/botsandus/ament_black/pull/5/commits/22b53a09666847f3406192eafa52668ab5dd7312 But I'm still waiting on the ros farm to agree on this

Before we move further, need to get https://github.com/ros/rosdistro/pull/38736#issuecomment-1758714607 addressed.

I would like to merge https://github.com/ros/rosdistro/pull/38754 before letting this go further ;)

Before we move further, need to get #38736 (comment) addressed.

Done: https://github.com/ros/rosdistro/pull/38736#issuecomment-1759301547, I would like to proceed with #38754

If you're adding that new dependency then you're should rerun Bloom after tagging a new release. Which will render this pr irrelevant.
In general when you compile in your local workspace you get all the system dependencies that you have on your system. If you want to test your dependency declaration you need to use a stripped down environment that only installs what your package asks for. This is what ci does, but in general it's too high an overhead for day to day development for most users. The ci solution isn't perfect, it still only creates one environment per repo so peer/neighboring packages can mask missing dependencies. But the individual final builds catch that the first time you release and maintainers rarely get caught by that again. So it's not worth the effort of spending potentially N times extra on the ci time for full isolation, and developers would prefer the faster response time.

@tfoote, thanks a lot for the info! Re-opening a new PR with a new bumped version ;)


Enable Federated Auth

Enabled federated auth by default in the eng sys template.

This PR should also remove the tests.yml lines where it's currently set to true: https://github.com/search?q=repo%3AAzure%2Fazure-sdk-for-java UseFederatedAuth&type=code

This PR should also remove the tests.yml lines where it's currently set to true: https://github.com/search?q=repo%3AAzure%2Fazure-sdk-for-java UseFederatedAuth&type=code

Thanks,
Will be easier to do that per service in a follow up PR post validating their pipelines are picking up the global property.
Merging this now, will enforce it on any areas where it isn't enforced.

API change check
API changes are not detected in this pull request.

/check - enforcer override

/check-enforcer override


About combining with pnm

Hi,
Firstly, thanks for the great work.
I just wonder if adai is suitable for combining together with positive-negative momentum which is another work of you. From my understanding of these two, it is ok to replace the original momentum with pnm in adai. Do you have any suggestions or experiences?
Thanks for the reply.

Hi julightzhong10,
Sorry for my late reply!
I did not notice this issue before.
I am not sure it is a good idea to combine Adai and Positive-Negative Momentum (PNM).
And I do not know the theoretical convergence guarantee of the fusing variant of Adai + PNM.
In my mind, they have total different theoretical mechanisms.
However, I do think it is possible to combine Adai and Adam. Their adaptivity can co-work well.
Best wishes


Toolbar: left instead of top

On the side would allow for more vertical space which is needed on widescreen displays.
Can't use whide labels for the elements of the toolbar but could use icons instead.

See also #5

This is also a good idea because most sketches are square shaped.


Debug mode

It would be awesome to throw the global network object into a debug mode that would spill out detailed logs of all network requests
Net.setup({
    debug : true
});

What do you think about this going into the constructor?

I suppose you would want to be able to call setup from the console.

For now I am going to just make setup available. But adding it to the constructor method would be trivial so it can be done later depending on how you want to design it.
Net.setup({
    debug: true
})


Assertion failure when programmatically resizing a window when ekWINDOW_RESIZE is not set.

The window_size implementation currently performs this cassert:
    cassert(window->flags & ekWINDOW_RESIZE);

I want to be able to create a window which cannot be resized by the end-user (i.e. they cannot drag the edges of the window frame to resize it) but I still need to be able to set the window size programmatically, so removing this assert altogether would allow this.
Alternatively, perhaps there could be a way to remove the ekWINDOW_RESIZE flag after creating it and setting the size, to disallow resizing by the user, but I assume that would be more difficult to implement.

Not really. This guard is there to prevent misuse of the SDK.
When you create a non-resizable window (e.g. DialogBox), the final size will be determined by the child elements. The steps to follow are:

Create Layout(s) and components.
Set the initial size of certain views (e.g. textview_size()).
Set margins and borders.
Set the width/height of certain columns/rows of the layout.

Ultimately, it's a bottom-up strategy. Here https://nappgui.com/en/gui/layout.html you have more info.
When you create resizable windows the steps are the same but, in addition, you have to define how the columns/rows of the layout will be resized (by default proportionally). layout_hexpand() and others. In this scenario, it makes sense to do a window_size() because layouts know how to handle size changes imposed by the parent window.

I think I understand, but in my case, all i have is a window, a panel, a layout, and a view. How should I set the size of the non-resizable window? Calling view_size seems to have no effect.

It must work
/*---------------------------------------------------------------------------*/

static void i_OnDraw(App *app, Event *e)
{
    const EvDraw *p = event_params(e, EvDraw);
    draw_clear(p->ctx, kCOLOR_BLUE);
}

/*---------------------------------------------------------------------------*/

static Panel *i_panel(App *app)
{
    Panel *panel = panel_create();
    Layout *layout = layout_create(1, 1);
    View *view = view_create();
    view_size(view, s2df(300, 200));
    view_OnDraw(view, listener(app, i_OnDraw, App));
    layout_view(layout, view, 0, 0);
    panel_layout(panel, layout);
    return panel;
}

I see, there is a hidden rule in the API.
This doesn't work, the window will have the wrong size:
	layout_view(...);
	panel_layout(...);
	window_panel(...);
	view_size(...);

But this does work:
	layout_view(...);
	view_size(...);
	panel_layout(...);
	window_panel(...);

So I assume it is not possible to change the view size at runtime, and have the window automatically resize itself to accommodate it.

Effectively. When you call to window_panel() the SDK recursively calculates the final position and sizes of all children. Once the window have been composed, any external change requires a window_update().
You have shortcuts to update content:
window_update()
layout_update()
panel_update()
all of them have the same effect: Recompute the window and children dimensions.

Its a good point to improve the documentation

I see, thank you for the help!


Upgrade to latest version on operator-sdk

Describe the solution you'd like
Upgrade the code to support the latest operator-sdk.
Describe alternatives you've considered
Stick with the old and create more technical debt.
What version of eunomia are you using?
eunomia version: 0.0.x

@seanmalloy this is not part of a milestone and we're using a very outdated version of the operator. I'm using a much newer version locally and it seems to be working fine. Not sure if this could also be the root cause for the build problems on PR #243 .

@Smiley73 first we need to upgrade to Go 1.13, see #246. After that we can upgrade to that latest version of the operator-sdk.
From my perspective we need to ...

Build out more test automation and get more bugs fixed
Update to Go 1.13
Update to latest version of operator-sdk

@seanmalloy I'm using 1.13 & a later operator-sdk at home for eunomia. I think you're overestimating the effort to do this. I've not experienced any issues.

The project has been upgraded to Go 1.13. We also now have a proper test matrix in Travis CI for testing against multiple k8s and OpenShift versions.
We are now all clear to upgrade to a newer version of operator-sdk. I added this issue to the near-term milestone. If someone has bandwidth to pick this up that would be great.


chore: Fixes limit check inside BodyBuffer.Write

Address https://github.com/corazawaf/coraza/pull/587#discussion_r1087071590. Took me a bit.
The initial change was made in order to allow Write to write up to the limit (included). But, in order to achieve this, it is enough to change the check between br.length and its future value, not the first check br.length == br.options.Limit that raises an error trying to write when br.length  is already reached.
Thank you @jcchavezs

Maybe a test covering this case so next person who touches this and thinks it could be better to have > instead  gets its back covered?


Robot wifi credentials cannot be set from the app

overview
Users should be able to configure their WiFi credentials from the app
behavior
Current behavior: In order to set WiFi credentials, you have to ssh into the robot and modify a file
Desired behavior: The user should be able to set up WiFi credentials from the app, after connecting to the robot with the USB cable.

I have (a wildly deprecated) starter branch for this in the UI.  Happy to resurrect this work to get something testable for connect.

Similar comment to the one I left in #528: I'd collected the following acceptance criteria for this story:

API should provide an endpoint to set WiFi credentials
App should provide interface for UI to send WiFi credentials to that endpoint
API should provide interface type for a given connection

e.g. in /health, the API could add interface: 'wired' or 'wireless' or similar depending on which interface the request came in on
This is a nice to have; app can probably infer this based on current connectivity strategy

App should differentiate between wireless and wired robots

Related: app should order robots based on priority of: currently connected, wired, wireless

Closing in favor of tickets above


Number of users reduce after running for 1min

Description of issue
I start a new locust test, set user number 10, swarm 5; after 1min, the user number reduce to 0, but RPS is stable.
Expected behavior
stable test
Actual behavior

Environment settings

OS: Windows
Python version: 3.7
Locust version: 0.11.1

Steps to reproduce (for bug reports)
Any websit to test, set user 10, swarm 5
class PressureTest(TaskSet):

    def setup(self):
        global headers
        headers = [{"Content-Type": "application/json"}]

    @task(100)
    def test1(self):
        query = {}
        with self.client.get('https://www.baidu.com', headers=headers, params=query, verify=False, catch_response=True) as resp:
            if resp.status_code == 200:
                if b'b' not in resp.content:
                    resp.failure('Error: wrong response --  ' + resp.content.decode('utf-8'))
                else:
                    resp.success()
            else:
                resp.failure('Error: wrong status code -- ' + str(resp.status_code))

class ApiTest(HttpLocust):
    host = ''
    task_set = PressureTest
    min_wait = 300
    max_wait = 500
    stop_timeout = 60

please provide example code

Misunderstanding "stop_timeout", it's not the time to assert failure when response time exceed it.


Terminal resize cursor still appears even though terminal window is closed

I really liked the update of VSCode where terminal can be aligned vertically. But, even after the terminal is closed, still if we hover mouse over the place where the boundary of terminal was, we could see resize window cursor. This isn't causing any disturbances but noticed it. Can be the minor bug but can't really look over it.

This is fixed in latest vscode. Please get the latest vscode where this is fixed. THanks


when the isarlink has uniqueindex

Steps to Reproduce
Please describe exactly how to reproduce the problem you are running into.
int id = Isar.autoIncrement;
@Index(unique: true)
String memId = ''
@Index()
String gid = '';
UserInfoEntity ui = UserInfoEntity();
final userInfoLink = IsarLink();
int id = Isar.autoIncrement;
@Index(unique: true)
String uid = '';
String name= '';

Provide a few simple lines of code to show your problem.

when i use
await isar.writeTxn((isar) async{
for (var element in data) {
element.userInfoLink.value = element.ui;
}
await isar.chatGroupMemberEntitys.putAll(
data,
replaceOnConflict: true,
saveLinks: true
);
}).then((value){
  logger.d(value);
}, onError: (e){
  logger.d(e);
});

i will throw the error
IsarError: There was an error but it could not be loaded from IsarCore.
i think isar should like object box let the replaceOnConflict to @Index(replaceOnConflict: true)
Version

Platform: iOS, Android, Mac, Windows, Linux, Web
Flutter version: [e.g. 2.10.5]
Isar version: [e.g. 2.5.0]
Isar Generator version: [e.g. 2.5.0]

I am not sure but I think replaceOnConflict will be removed starting with Isar 3.0.

Yes, this issue should be fixed in 3.0


Update year in copyright notices

Two commits:

Automatically update the copyright year in the docbuild (appears e.g. at the bottom of the readthedocs page)
Update all copyright notices in the code to 2024 and reactivate the test that checks this (was deactivated in 03b259a)

Testing the copyright is not a legitimate "test" - the program still runs perfectly fine, it doesn't break just because we have a new year - but the copyright test does.
If anything, we might add a linting rather than a test, that checks on modified/new files that the copyright line is there and "up to date".
Ideally, we should have a github action that auto-formats the code to unify style, and in that process also adds a copyright notice if needed. I guess that should be part of #230

That is true for all of test_consistencies.py though, right? None of those checks indicate that the code doesnt run anymore?
Either way, I will remove the change to the test and only keep the changed year in this PR


RDMO export with image included

He there
I wanted to use rdmo and the render_to_format function returning a dmp PDF which follows our own branding including images. So far I created a view and an html template in our Django project also embedding our logo (using static content in: /static/images/logo.png). Rendering the template as html works fine. Tossing that html into the render_to_format function I see pandoc failing for the embedded image not being found as it treats the static image path as absolute path on the filesytem (so it starting from root. when I put the image there it works). Do you have any suggestions or ideas on how to best deal with it to make pandoc find the image served in the context of django static files?
Best Claas

I think it would also be super useful if I could pass a custom latex template to pandoc through a parameter in your render to format function. That way we gain a lot of flexibility adjusting the style of the output format? What do you think?

I added the requested feature to this branch: https://github.com/rdmorganiser/rdmo/tree/export_with_image
With the changes Pandoc is able to find static files and export them into documents. In the view these files are referenced by their standard url so that they can be rendered in the browser as well. You could write something like this into your view:
<img src="/static/my_own_logo.png">

Nice thanks!


Bug CMD_ARGV

Hi.
I got a bug report about PODBot s1lentq/ReGameDLL_CS/issues/96, but this bug also refers to yapb.
Example:
void ClientCommand(edict_t *pEntity)
{
	const char *pcmd = CMD_ARGV(0);
	const char *parg1 = CMD_ARGV(1);

	// expected
	// pcmd == menuselect
	// parg1 == 5

	// but got the result
	// pcmd == 5
	// parg1 == 5

...........

As we can see, calling CMD_ARGV(1), a pointer to a string pcmd changing, that is very wrong.
Yapb does replacement Cmd_Argv on own and uses a one temporary buffer.

Hi. Ty for report.
Should be fixed current rev.


Drivers: Unable to deactivate drivers in bulk

Setup

Rancher version: v2.9-head
Rancher UI Extensions:
Browser type & version: Any

Describe the bug
User is unable to deactivate cluster/node drivers in bulk.
To Reproduce

login to Rancher as an admin
go to the Cluster Management page
click 'Drivers' tab in the side nav
click Cluster/Node Drivers tab
select two or more active drivers
click deactivate
notice only one of the drivers selected were deactivated

Result
User is unable to deactivate cluster/node drivers in bulk.
Expected Result
User is able to deactivate cluster/node drivers in bulk.
Screenshots
https://github.com/rancher/dashboard/assets/127343932/2552b278-0256-4060-8f65-ab1938848e34
Additional context
We are currently skipping the associated e2e tests in kontainer-drivers.spec.ts and node-drivers.spec.ts. Please enable them once this issue has been resolved by removing .skip.

Once there's a possible fix, there's an E2E to reenable to try it out.

e2e tests are sufficient. moving to done


Can't call domain services using domain.entity.service() pattern

I used to be able to do:
light.master_bedroom.turn_on(brightness=254, color_temp=275)

but now I get errors:
AttributeError: 'StateVal' object has no attribute 'turn_on'
2021-02-26 16:06:29 ERROR (MainThread) [custom_components.pyscript.file.daytime.turnOnDayLights] Exception in <file.daytime.turnOnDayLights> line 9:
            light.master_bedroom.turn_on(brightness=254, color_temp=275)
            ^
AttributeError: 'StateVal' object has no attribute 'turn_on'

I recently upgraded my core version to core-2021.3.0b1; might have something to do with this?

On startup, pyscript calls async_get_all_descriptions() to get all the service descriptions, and it populates the dictionary State.service2args with all the services that have an entity_id keyword argument.  Assuming you have allow_all_imports and hass_is_global both set, you can check what services it knows about:
from custom_components.pyscript.state import State
State.service2args["light"]

Does that include an entry State.service2args["light"] and State.service2args["light"]["turn_on"]?
If not, you can call async_get_all_descriptions() to see what it returns for "light":
from homeassistant.helpers.service import async_get_all_descriptions
async_get_all_descriptions(hass)["light"]

I'm having the same issue, and I suspect it was the last pyscript release but haven't been able to dig in yet. Will run some tests based on your comment and will report back what I find

I created an input_number:
input_number:
  x1:
    initial: 100
    min: 0
    max: 1000

and I confirmed that things like input_number.x1.increment() and input_number.x1.set_value(50) work ok.
Perhaps there is now some race condition where the lights.turn_on service is not registered before pyscript calls async_get_all_descriptions()?  It should be called when the EVENT_HOMEASSISTANT_STARTED is fired, but perhaps something is broken now.  It is also called on pyscript.reload.
You could also call it manually from Jupyter with:
from custom_components.pyscript.state import State
State.get_service_params()

Does it now work after you do that?
Also, in looking at the code I noticed that pyscript fails to update State.service2args when a new service is defined with an entity_id parameter, so pyscript services don't support these virtual methods.  I need to fix that.

I misspoke about it being tied to 1.3.0. When I downgraded, I saw my pyscript services in Dev Tools so I assumed everything was ok. But the next time an automation ran that called one of those services, it failed, so I'm guessing there was a change that's coming in the next release that's causing this behavior as I am still running on 2021.3.0beta2.
Running that command in Jupyter did not resolve the issue:
Exception in <file.climate.set_temperature> line 47: climate.thermostat.set_temperature(temperature=float(temp)) ^ AttributeError: 'StateVal' object has no attribute 'set_temperature'

@raman325  - does the simple input_number test work or fail for you?
Unfortunately I don't have good internet access for the next day (or potentially 3 days).  I don't think I can upgrade to 2021.3.0beta2 until I have better internet.

I successfully upgraded hass; the input_number test fails for me now.  Onto debugging...

Hmmm, the return value of async_get_all_descriptions() does not include any entity_id fields, so pyscript doesn't consider it a valid virtual method.

ah, I know what's going on. The latest release introduces a new key to service calls called target. Now, in addition to specifying the entity_id in the service data dictionary, you would specify it under target. This has resulted in service schemas changing
Here are some references:

https://developers.home-assistant.io/docs/dev_101_services#service-descriptions
https://developers.home-assistant.io/docs/documenting/yaml-style-guide/#service-targets

Yes, your explanation sounds right.  It looks like entity services are now a different thing, so we need to figure out how to enumerate them (or ideally just check a single one on demand, which would be better than caching them all at startup).

Wow you are fast, I logged in this morning to try to figure this out and wondered how you had already had a check for the target key.
One thing that came to mind is that it would be nice if we could use target (when this is included, there is a nicer UI available to pick entities) and selector (also enhances the UI) in service descriptions. It looks like it should just work if the docstring is yaml, but something to think about if you want to support it using non YAML docstrings.

Here's what it looks like in Dev Tools when you specify selectors in the service description btw:

Release 1.3.1 with this fix.

Thank you for your work on this amazing project! Really makes automating fun.


feat: user should be able to resend confirmation

Description

Created validator for  resending confirmation email,
Created resend confirmation email method in the auth controller
Created resend confirmation route
Wrote unit test for validator,  and controller

Finishes #14
How Has This Been Tested?

In your terminal, run git clone https://github.com/BuildForSDG/SmeVest-Backend.git
Run cd SmeVest-Backend
Run git fetch origin ft-resend-confirm
Run git checkout origin/ft-resend-confirm
Run yarn install
create a .env file in the root directory then add details as seen in .env-example file
Run yarn run test to run unit tests
Run yarn run start:dev to start the development server
To test with postman use http://localhost:4000/api/v1/auth/emails/confirm/resend with appropriate parameters,

Sample request:

{
	"email"<EMAIL_ADDRESS>}

Sample success response :

{
   "status": 200,
   "message": "Email confirmation resent successfully"
}

Screenshots (if applicable, else remove this line / section)
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added necessary inline code documentation
[x] I have added tests that prove my fix is effective and that this feature works
[x] New and existing unit tests pass locally with my changes

I was wondering if we will be sending mail to a not registered account

No, there will be an error response of user not found if the user is not registered


sitemap.xml not working since v1.2 !

@peter-mw
The xml sitemap at mydomain.com/sitemap.xml seems to have stopped working since v1.2. Version 1.1.x correctly output the pages urls and lastmod dates, etc, however the output from v1.2.3 doesn't:
<sitemapindex> <sitemap> <loc>http://mydomain.com/mw-latest/sitemap.xml/categories</loc> </sitemap> <sitemap> <loc>http://mydomain.com/mw-latest/sitemap.xml/products</loc> </sitemap> <sitemap> <loc>http://mydomain.com/mw-latest/sitemap.xml/posts</loc> </sitemap> <sitemap> <loc>http://mydomain.com/mw-latest/sitemap.xml/tags</loc> </sitemap> <sitemap> <loc>http://mydomain.com/mw-latest/sitemap.xml/pages</loc> </sitemap> </sitemapindex>
The url http://mydomain.com/mw-latest/sitemap.xml/pages gives the empty result below:
<urlset> </urlset>
Version 1.2.5 dev gives the following error:
Illuminate\Database\QueryException SQLSTATE[42S22]: Column not found: 1054 Unknown column 'reserved' in 'where clause' (SQL: select * from jobswherereserved is null and (attempts< 10 orattemptsis null) limit 10)
If I add a tinyint 'attempts' field to jobs table I get the same output as for v1.2.3 above.

The error seems to be fixed in 1.2.6 dev, however the categories don't seem to be working correctly eg https://mwdemo.ezyweb.uk/sitemap.xml/categories outputs 4 listings with the same url https://mwdemo.ezyweb.uk/shop/ where as the categories setup are:
Shop > Women
Shop > Women > Bags
Shop > Men
Shop > Men > Shoes
Also the Pages url is showing Posts not Pages eg  https://mwdemo.ezyweb.uk/sitemap.xml/pages
It would be nice if eg not posts exist then the top level url did not show - maybe that's already coded?

Using the New World template with v1.2.9, sitemap.xml/categories still outputs 4 listings with the same shop url, and sitemap.xml/pages shows blog posts not pages. This needs fixing for SEO.

No change in v1.2.10
/sitemap.xml/categories not working
/sitemap.xml/pages not working

thanks for report we will check


oculante: 0.7.5 -> 0.7.6

Diff: https://github.com/woelper/oculante/compare/0.7.5...0.7.6
Changelog: https://github.com/woelper/oculante/blob/0.7.6/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

closing in favor of #256343, @colemickens beat me to it


Add instances to mmorph

cps transformers were added to transformers package. See https://hub.darcs.net/ross/transformers/patch/b6743fad9f5ce8a9e13f15320f7d2752330084e2

Hmm... not possible to add instance to mmorph now that the constructors are hidden
This commit https://github.com/Gabriel439/Haskell-MMorph-Library/commit/e9577ec36f21cfe9175b8f57cddccd6a72affafc errors:
/Users/louis/repo/hs/Haskell-MMorph-Library/src/Control/Monad/Morph.hs:166:19: error:
    • Could not deduce (Functor n) arising from a use of ‘W''.writerT’
      from the context: Monad m
        bound by the type signature for:
                   hoist :: forall (m :: * -> *) (n :: * -> *) b.
                            Monad m =>
                            (forall a. m a -> n a) -> W''.WriterT w m b -> W''.WriterT w n b
        at src/Control/Monad/Morph.hs:166:5-9
      Possible fix:
        add (Functor n) to the context of
          the type signature for:
            hoist :: forall (m :: * -> *) (n :: * -> *) b.
                     Monad m =>
                     (forall a. m a -> n a) -> W''.WriterT w m b -> W''.WriterT w n b
    • In the expression: W''.writerT (nat (W''.runWriterT m))
      In an equation for ‘hoist’:
          hoist nat m = W''.writerT (nat (W''.runWriterT m))
      In the instance declaration for ‘MFunctor (W''.WriterT w)’
    |
166 |     hoist nat m = W''.writerT (nat (W''.runWriterT m))
    |                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/louis/repo/hs/Haskell-MMorph-Library/src/Control/Monad/Morph.hs:149:19: error:
    • Could not deduce (Functor n) arising from a use of ‘RWS''.rwsT’
      from the context: Monad m
        bound by the type signature for:
                   hoist :: forall (m :: * -> *) (n :: * -> *) b.
                            Monad m =>
                            (forall a. m a -> n a)
                            -> RWS''.RWST r w s m b -> RWS''.RWST r w s n b
        at src/Control/Monad/Morph.hs:149:5-9
      Possible fix:
        add (Functor n) to the context of
          the type signature for:
            hoist :: forall (m :: * -> *) (n :: * -> *) b.


Azure Resource Group Deployment Task - Allow wildcards in template location when using linked artifacts

Hi guys,
Currently when using the "Linked artifact" option in the ARM Template deploy task, the path to the template json file must be absolute, resulting in an error if you try to use pattern matching to find the json file.
It would be great if you could use wildcard folder/file matching that is available in almost every other task in this library, when trying to create build/release templates it is much easier to use pattern matching rather than variables for artifact folder name + relative path etc.
Obviously this wouldn't work with URL links, but since we have access to the filesystem for linked artifacts, I don't see any issue in allowing this sort of pattern matching, especially if the Azure App Service Deploy task can get away with it for finding a zip file.
Cheers,
Richard

@duckwaffle thank you for the feedback. We have made this update to the task (https://github.com/Microsoft/vsts-tasks/pull/4671); you'll be seeing it in production in the next three weeks. :)

@ds-ms cool! Thanks for the update 👍


Bug fix

How does moving the moderator check after the banned check fix bugs?

The function isModerator takes the user as an argument and when it is called it checks for the user roles
roles = [role.id for role in member.roles]
Since the user is banned from the server, checking their roles will give out an error so we have to check whether the user is banned or not before checking whether they have the mod role or not


Implement transaction class

We might need to create a class Transaction that help hold each transaction and we simply print out transactions on each card.
We use the class constructor to parse the transaction message, so all main() function need to do are:

to parse response.text
find out HTML tags that hold card transactions
feed each transaction to the class constructor of Transaction class.
print out the card transactions in a formatted way

Maybe some existing HTML parser will help:

https://www.crummy.com/software/BeautifulSoup/bs4/doc/
https://docs.python.org/2.7/library/htmlparser.html?highlight=html

I believe htmlparser is enough. We can use that one to extract transactions through tag searching.

Addressed in https://github.com/chinghanyu/BHNVGCBalanceChecker/pull/10


TensorflowConversion Data Types

I am seeing some test failures on CI unrelated to this - https://github.com/eclipse/deeplearning4j/issues/8748
As far as I can tell those issues are unrelated to these changes and these test modifications are passing. So I'll merge this now.


Support an ambiguously typed property validator

Description
It would be useful to be able to define an ambiguously types property validator.  The use case being a required property whose type is dependent/inferred from another property on the document.  Currently type is a required property on a property validator, and the only way to allow an ambiguously typed property is to omit defining it at all and instead mark the parent object validator with allowUnknownProperties.  This leaves no means by which to mark the field in question as required, and the resulting sync function will accept objects lacking that property.
Examples
Consider an example where dynamic type on a property validator is not sufficient:
suggestions: {
  type: 'array',
  required: true,
  arrayElementsValidator: {
    type: 'object',
    required: true,
    propertyValidators: {
      // Name of the field the suggestion is intended for.  Field name should imply expected value type.
      suggestedField: {
        type: 'enum',
        predefinedValues: [ 'accountNumber', 'taxIds' ],
        required: true
      },
      // Value of the suggestion
      suggestedValue: {
        type: function(doc, oldDoc, value, oldValue) {
          // no simple way to access the sibling property suggestedField, which implies type
        },
        required: true
      }
    }
  }
}

This use case would be satisfied if the dynamic type constraint function of a property validator had access to the stack of properties being validated (and therefor providing access to sibling and even parent object properties)

I believe this specific use case can be handled by the current version of synctos by instead defining the nested propertyValidators property as a function. For example:
suggestions: {
  type: 'array',
  required: true,
  arrayElementsValidator: {
    type: 'object',
    required: true,
    propertyValidators: function(doc, oldDoc, value, oldValue) {
      return {
        // Name of the field the suggestion is intended for.  Field name should imply expected value type.
        suggestedField: {
          type: 'enum',
          predefinedValues: [ 'accountNumber', 'taxIds' ],
          required: true
        },
        // Value of the suggestion
        suggestedValue: {
          type: value.suggestedField === 'accountNumber' ? 'string' : 'array',
          required: true
        }
      };
    }
  }
}

That does indeed cover my use case


(SPIKE) Customize YAML serialization

In Ruby 2.3, a change was introduced to how Hash is seralized as
YAML. If Puppet resources are derived from Hash instead of the
usual Puppet::Type, they will now try to serialize data that was
previously not serialized (including Provider instances).
In particular, use of the ACL module fails on Ruby 2.3 to properly
serialize corrective changes YAML because Puppet::Type::Acl::Ace
derives from Hash.
While changes to the ACL module can be made to either implement
encode_with directly OR to instead derive from something other
than Hash, this may not handle any other such instances within the
Puppet ecosystem.
NOTE: other options are currently being explored to address this

Previous YAML for an ACE looked like this in Ruby 2.2 and lower:
--- !ruby/hash:Puppet::Type::Acl::Ace {}

With this change YAML for an ACE looks like this on Ruby 2.3:
---
- !ruby/object:Puppet::Type::Acl::Ace
  identity: Administrators
  hash:
  id: S-1-5-32-544

  mask:
    rights:
    - :full
    perm_type: :allow
    child_types: :all
    affects: :all
    is_inherited: false

CLA signed by all contributors.

This is not really PUP-7381 but rather closely related.

I think we can close this.


Mapping values must be quoted if not a boolean

Orb version:
0.1.2

What happened:
set-parameters step fails reading map with json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
The offending command is the  convert_mapping(m) function's use of json.loads against the 3rd value in MAPPING - which only works when its a boolean.
 def convert_mapping(m):
                      return [m[1], json.loads(m[2])]

Expected behavior:
use a tool that can read unquoted strings (valid yaml) or document the caveat that the 3rd value in mapping must be valid JSON.

Additional Information:
workflows:
  build_deploy:
    jobs:
      - path-filtering/filter:
          base-revision: master
          config-path: .circleci/continue-config.yml
          mapping: |
            module-a/.* module-a true  # this works
            module-b/.* module-b bananas # this fails

It is no hint or debug output as to what is wrong, and at first glance seems identical to the orb's example.
The issue is that the true is a boolean and bananas is a string, and so in JSON rules which differ than the yaml we're writing it in require strings in double-quotes specifically (single quotes will also fail)

double-quoting the value works, not single quotes.  So this is a docs/education issues.

Thanks for reporting this. I just ran into this and it was confusing as well.
I'd call this a bug, not a docs/education issue since I don't see why a string should need to be quoted in yaml. Does that make sense?

I'm marking this documentation issue, as well as the enhancement.


Fix webpack when using browser_wasi_shim as dependency

CommonJS style exports were previously used in index.js despite being an ESM module. Switching to the ESM export syntax fixes webpack.
Fixes #12

@brandonchinn178 @bhelx could you please take a look?

Yeah, it definitely should not be mixed. We should go one way or the other. It can be tricky to get something to work in both module formats without a build step though. Typically what I do is use esbuild and provide different entries for CJS and ESM. Will this work for both @brandonchinn178 ?

@brandonchinn178 thanks for explaining. I'm okay with merging if it unblocks you.

It's the annoying state of the JS ecosystem, but that's what it is.

I don't know a ton about JS but this is my interpretation as well. There isn't currently a way I've found to make a universal module without some kind of build step. I've found esbuild to be a pretty simple dependency to use that isn't as massive as webpack. I can also work on the build step, but I know @bjorn3 was hoping to avoid that so I'd so I leave it to him to make the final call.

Also, I didn't want to make another issue for this, but could you also remove the console.log calls, or at least put them behind a debug flag?

Done

Looks great! Although you could make it even more concise:

Neat.

I can also work on the build step, but I know @bjorn3 was hoping to avoid that so I'd so I leave it to him to make the final call.

I'm fine with having a build step for the module published on npm. I just want to be able to do local development without requiring any build step.

Thanks @brandonchinn178 !

I'm fine with having a build step for the module published on npm. I just want to be able to do local development without requiring any build step.

@bjorn3 I'll see if i can figure this out. In my experience once you add a build step it takes over, but I'll test it out.

Should I merge this and publish a new release or should I wait on this build step getting added?

I think you're good to merge. I can pin on the previous version or send a follow up if it causes a problem.

Published as v0.2.3

Local development should be unaffected. The build step should just add more files, not change any of the existing ones, so you should be able to work on it as usual.
Thanks for the quick turnaround!


vieb: 3.4.0 -> 4.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/vieb/versions.
meta.description for vieb is: "Vim Inspired Electron Browser"
meta.homepage for vieb is: "https://vieb.dev/"
meta.changelog for vieb is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 4.0.0 with grep in /nix/store/mfn7x48njh8d10jcirp8dxanly7ii00f-vieb-4.0.0

directory tree listing: https://gist.github.com/8bd49f79aa1cf1a673513be97027e662

du listing: https://gist.github.com/7e517d43a8cd2bf656c0fc3e8c0fa636

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
vieb

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

vieb

Maintainer pings
cc @gebner for testing.

App threw an error during load
Error: Cannot find module 'hazardous'
Require stack:
- /nix/store/mfn7x48njh8d10jcirp8dxanly7ii00f-vieb-4.0.0/libexec/vieb/deps/vieb/app/index.js
- /nix/store/hvblhk8q5vgjcqmidsfzwpfy667plwxp-electron-11.3.0/lib/electron/resources/default_app.asar/main.js
-
    at Module._resolveFilename (internal/modules/cjs/loader.js:972:15)
    at Function.n._resolveFilename (electron/js2c/browser_init.js:249:921)
    at Module._load (internal/modules/cjs/loader.js:848:27)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12738)
    at Module.require (internal/modules/cjs/loader.js:1032:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/nix/store/mfn7x48njh8d10jcirp8dxanly7ii00f-vieb-4.0.0/libexec/vieb/deps/vieb/app/index.js:21:1)
    at Module._compile (internal/modules/cjs/loader.js:1152:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1173:10)
    at Module.load (internal/modules/cjs/loader.js:992:32)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot find module 'hazardous'
Require stack:
- /nix/store/mfn7x48njh8d10jcirp8dxanly7ii00f-vieb-4.0.0/libexec/vieb/deps/vieb/app/index.js
- /nix/store/hvblhk8q5vgjcqmidsfzwpfy667plwxp-electron-11.3.0/lib/electron/resources/default_app.asar/main.js
-
    at Module._resolveFilename (internal/modules/cjs/loader.js:972:15)
    at Function.n._resolveFilename (electron/js2c/browser_init.js:249:921)
    at Module._load (internal/modules/cjs/loader.js:848:27)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12738)
    at Module.require (internal/modules/cjs/loader.js:1032:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/nix/store/mfn7x48njh8d10jcirp8dxanly7ii00f-vieb-4.0.0/libexec/vieb/deps/vieb/app/index.js:21:1)
    at Module._compile (internal/modules/cjs/loader.js:1152:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1173:10)
    at Module.load (internal/modules/cjs/loader.js:992:32)

Requires update to yarn and package.json files.


Linux tunneler help

Some notes that we could fold-in to https://openziti.github.io/ziti/clients/tunneler.html#linux
ziti-edge-tunnel

C-SDK tunneler aka "tunneler SDK"
a bit more advanced and less user-friendly than ziti-tunnel but has a superior approach to built-in DNS
is more performant than ziti-tunnel
run mode uses tun device IP routes to intercept service traffic and answer DNS via resolvectl
Future development will probably land first in the tunneler SDK
Experimental Docker container exists: netfoundry/ziti-edge-tunnel
systemd install

# transparent install procedure for ziti-edge-tunnel

# where to install the executable binary
❯ ZITI_EDGE_TUNNEL_BIN_DIR=/usr/local/bin

# where to look at startup for enrolled identity JSON config files
❯ ZITI_EDGE_TUNNEL_ID_DIR=~/.ziti-edge-tunnel

# create the identity directory
❯ mkdir -pvm0700 $ZITI_EDGE_TUNNEL_ID_DIR

# create a systemd service
❯ cat <<ZITI_SERVICE | sudo tee /usr/lib/systemd/system/ziti-edge-tunnel.service
[Unit]
Description=Ziti Edge Tunnel
After=network.target
ConditionDirectoryNotEmpty=$ZITI_EDGE_TUNNEL_ID_DIR

[Service]
User=root
ExecStart=${ZITI_EDGE_TUNNEL_BIN_DIR}/ziti-edge-tunnel run --verbose 4 --identity-dir $ZITI_EDGE_TUNNEL_ID_DIR
Restart=always
RestartSec=2
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target
ZITI_SERVICE

# load the new systemd config
❯ sudo systemctl daemon-reload

# download some version of ziti-edge-tunnel
❯ curl -sSLf https://raw.githubusercontent.com/openziti/ziti-tunnel-sdk-c/main/docker/fetch-github-releases.sh | ZITI_VERSION=0.17.7 bash -x /dev/stdin ziti-edge-tunnel

# install in a directory that is in the executable search PATH
❯ sudo mv -v ./ziti-edge-tunnel ${ZITI_EDGE_TUNNEL_BIN_DIR}/

# verify the installed version
❯ sudo ziti-edge-tunnel version

# use a downloaded enrollment token to generate an identity
❯ sudo ziti-edge-tunnel enroll --jwt ~/Downloads/linuxTunneler1.jwt --identity ${ZITI_EDGE_TUNNEL_ID_DIR}/linuxTunneler1.json

# start the daemon
❯ sudo systemctl start ziti-edge-tunnel.service

# view the logs
❯ sudo journalctl -lfu ziti-edge-tunnel.service

ziti-tunnel

the first Linux tunneler
Go-SDK tunneler
has useful modes proxy and host in addition to tproxy (IPtables intercepts)
works fairly well today in Docker: netfoundry/ziti-tunnel

Consider adding some sanity checks to the systemd unit file like ConditionDirectoryNotEmpty
Additionally, should we be steering users to the XDG Base Directory Specification?

@sabedevops Good stuff. I added that unit conditional and XDG_DATA_HOME looks like something we should use with the (eventual) install package for this service unit, unless you see a specific way we could apply it in this manual install procedure.

For the purposes of this script, this can be done generically like this:
[ ! -z "$XDG_DATA_HOME" ] && ZITI_EDGE_TUNNEL_ID_DIR="$XDG_DATA_HOME/ziti-edge-tunnel" || ZITI_EDGE_TUNNEL_ID="$HOME/.ziti-edge-tunnel"
This may not align with current documentation and user expectations, so it may be worth ignoring at this time.
Also, please be advised the approach in this script is not bulletproof, since things like Kerberized NFS homedirs with root squashing will cause the service to fail due to permissions.  Nonetheless, it's a great start @qrkourier

@dovholuknf Based on today's conversation about the older and newer Linux tunnelers we should refactor this document to position the preferred tunneler as such, and document the dwindling-few unique capabilities of the non-preferred tunneler ziti-tunnel. You may assign this issue to me. :+1:


Additional function implementations

Implementations of additional functions.
Adjustment of the functionalities allowing the good functioning of the conversion from csv to json

Hi @JuliaSprenger , when you can, here are the changes:
Removal of the Record ID field
Removal of the {} in the choices
Removal of conditional fields

Hi @killianrochet Does this PR also deal with the duplicated names issue, e.g. Comments onComments on the Experiment?

@killianrochet I don't really understand what do you mean by that ..?

Hi @killianrochet I think the test might be failing because this branch might not contain the latest changes from main. Can you make sure this branch is up to date with main?

Thanks for the improvements. Looks good to me! Merging now :)


Create pythonpackage.yml

Coverage decreased (-0.1%) to 87.782% when pulling bbf9ded2463c4ef0a505ac895f99dc7d3e8fc1dc on quantophred:github-actions into bbf922102c923f1a91b68dc934479686daded50f on quantopian:master.


Add a column for company blurb

It'd be nice to easily check what the company is all about.

I think this would make the table too bulky. Closing for now.


[T4A7][T15-A1] Neo Wei Jie, Esmond

Ready for review.

@zeticous
Some comments added. Please ack & close the PR after reading comments.


How to use dependencycheck.properties with CLI module

After some research on the documentation, and in the code, I found some mention of dependencycheck.properties .
How to use this file with CLI ?
Can I add the file in my project ( at root of my scan ) ? ( if no, I think it can be a good idea )
Else, How to specify ANALYZER_NODE_AUDIT_URL to CLI ? ( because I'm locked by NPM, before the end of the test ... And for my dependency install, I'm using a custom registry, verdaccio, integrating the node audit API )

Ok, so finally, I've found the correct argument -P  --propertyfile, and my error come from verdaccio ( just proxying request to node audit API ... so blocked too )


Get dbc.CardGroup smaller

Can someone create a PR where this dbc.CardGroup get smaller maybe 0.7*h? Maybe with some CSS magic? I can't...

https://github.com/EinEinfach/CaSSAndRA/pull/52


python3Packages.mediapipe: init at 0.8.6

Motivation for this change
Package Google's mediapipe image processing library. This uses the pre-built wheel versions. I attempted to try building from source, but the build system is a custom mix of setup.py and Bazel. I tried basing it on buildBazelPackage but it didn't seem to cover this use case. It may be something to look into in the future, as the wheel is potentially missing features such GPU support.
Things done

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 132275 at 32078e67 run on x86_64-linux 1

2 packages failed to build:

python38Packages.mediapipe
python39Packages.mediapipe

1 suggestion:

warning: unused-argument
Unused argument: pkgs.
Near pkgs/development/python-modules/mediapipe/default.nix:1:16:
  |
1 | { lib, stdenv, pkgs, buildPythonPackage, fetchPypi, autoPatchelfHook
  |                ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

@jonringer that was my first attempt, but the build system is such a complex mish-mash of python and bazel that I couldn't get it to work. Perhaps someone more familiar with hazel could take another look

Closed as stale


Transfer the autosave status/interval byte to user storage rather than within the NBS file

Describe the enhancement you'd like
One thing I noticed when debugging a partially corrupt NBS file (not the program's fault, don't worry lol) is that the autosave status is stored in the file. Since it's already deprecated and unused, this would be a great opportunity to remove it entirely for NBS v6. Also, if the byte(s) were ever to be re-used in the future, it could cause a conflict with the user's own autosave setting, and could raise the question of which should take priority.
I realize this should probably be in the NBS v6 discussion #402, but given this is such a minor change it felt more appropriate to make a feature request for this.

Hi, thanks for your suggestion!
The reason auto-save and auto-save interval were not removed from the format, although deprecated, is to avoid changing the internal song format structure as much as possible, unless it is absolutely necessary. When adding a new feature, one has no choice but to add a new field somewhere. But it causes no harm to keep a feature that's no longer used.
If anything, it should make it easier for parsers to implement full version range compatibility, since 1) it avoids one more conditional if statement to not encode the information based on the version, and 2) their internal representation can keep track of the auto-save value for the purpose of saving the song in older version, even if the song in question comes from a recent version. Although the field is deprecated in modern versions, songs can export the user's global auto-save setting, so that, should the song ever be saved in an older version, the behavior they had set up the moment the file was saved will be preserved in earlier versions of the program.
It also makes the documentation simpler to mark the field as deprecated rather than, somehow, indicating that it is simply absent. Additions to a specification are somewhat "permanent", i.e. once you add it, there's no going back — we'll always carry the burden of having to maintain information regarding that choice, whether it's to tell it was deprecated or removed.
On the other hand, I agree keeping unused information around can litter the file and make the song's structure confusing, so I'll consider adding this topic to the NBS version 6 proposal when the time comes. Thanks again for your careful consideration! :)

And just to clarify, the auto-save and auto-save duration settings are already stored in user preferences – the values written to the file are just redundance.


Make a change_mac.sh

Try to experiment with a user interface (dmenu, zenity, etc.)

Done! And it actually works!


Scrolling on each matrix rather than as a set

I've tried the AnimateText.ino and the example in README.md and they both do the same thing - the entire text scrolls on each matrix, rather than scrolling across 4 matrices.
So I end up with Demo...Demo...Demo...Demo
rather than D...e...m...o
Any ideas?
Using NodeMCU v1.0 (Amica and Doit.am) and a Wifi-Witty, Arduino 1.6.6 and 1.6.7

¿Have you changed "#define NUMBER_OF_DEVICES 1"?

with me its the same...
 the entire text scrolls on each matrix, rather than scrolling across 4 matrices.
how to change? code improvement?

Turns out this is the same issue I just commented on in #7, where with these boards with 4 modules, they're aligned 90º off, so the scrolling effect doesn't work right. We need something like the "vertical" parameter from this python library https://github.com/rm-hull/max7219

yes, seems you are right.
i did a test with python. it worked there
https://github.com/rm-hull/max7219/issues/28
but it would be wonderfull, it it would work with this lib here and the ESP8266.. :smile:

Yep, as explained in http://frightanic.com/iot/max7219-library-nodemcu-making/ (my site) you want that rotate option for the 4-in-1 modules and also an invert (upside down) option if you daisy-chain manually.

Team, if fixed this for 1x4 module mentioned above @ozett and @marcelstoer The modified changed are here: https://github.com/adityarao/MAX7219LedMatrix/
The only change required was to rotate the matrix as below in the LedMatrix::commit()  as below:
void LedMatrix::commit() {
byte index = B0000001;
byte col;
if(deviceOrientation == HORIZONTAL) {
    for (col = 0; col < myNumberOfDevices * 8; col++) {
        sendByte(col / 8, col % 8 + 1, cols[col]);
    }
} else if(deviceOrientation == VERTICAL){ // orient the device vertically
    for (col = 0; col < myNumberOfDevices * 8; col++) {
        xcols[col] = 0;
    }
    // little inefficient, can be enhanced, rotate the matrix !
    for (col = 0; col < myNumberOfDevices * 8; col++) {

        for(byte bits = 0; bits < 8; bits++)
          xcols[col] |= ((cols[bits + 8*(col/8)] & (index << (col%8))) ?
                                 (B10000000 >> bits) : 0);
        sendByte(col / 8, col % 8 + 1, xcols[col]);
    }
}

}


Print some message when player provides invalid input

Somthing like "Invalid input. Available options are rock, paper or scissors".

All is done.


licecap

Project description
Simple animated screen captures
Metadata

homepage URL: https://www.cockos.com/licecap/
source URL:

https://www-dev.cockos.com/licecap/licecap.git
https://www.github.com/justinfrankel/licecap.git (official mirror)

license: gpl  ("LICEcap is GPL free software, each download package includes the source.")
platforms: darwin (and maybe windows someday ;)

Oops, this is a dupe of #158436


feat(anim): additional animation events

adds additional animation events, also incorporating new interface methods
fixes issue https://github.com/aurelia/templating/issues/111

looks good !


Import and replicate needs support for optional regeneration of UUID's

Import currently offers an option to regenerate UUID's in the imported module.  This is currently not implemented.  Similar functionality is needed for Replicate, so that same functionality should hook into Import when it is available.

In the oscal documents we have three scenarios

Declaration of uuid's as an attribute e.g. field name is 'uuid'
Reference to another uuid as an attribute where the name contains uuid but is not uuid.
e.g. 'party-uuid'
Note: we need to validate this.
Objects where instead of an array a key:value method where the key is a UUID.
May contain both declarations and references and we need to validate this

Logic to regenerate UUIDs would be as follows.

Identify all declarations in the code according to (1) and (3)
Create a map of old:new uuids and update the declarations
Identify references to uuids and update to the new uuid using the map from step (2).


Script failed to scan birthdays

Script failed to scan birthdays.
Error message: eyJlcnJvciI6IlJlbW92ZWQgaW5maW5pdGUgc2NhbiBsb2NrIiwidHlwZSI6IlNDQU5fRVJST1JfR0VORVJBTCJ9

The issue is solved in https://github.com/zagushka/birthday-calendar-extractor/pull/94


Giant screen search icon shown before API reference gets loaded

Go to https://docs.apify.com/api/v2 you'll see:

before the actual page loads for dark mode.
For light mode, it seems there's a few seconds delay for the search bar in the top right corner.
Reported on Slack https://apify.slack.com/archives/C0L33UM7Z/p1725367049323899

this one is probably relevant and also states a workaround https://github.com/rohit-gohri/redocusaurus/issues/215


Try to use the builtin math token

Redo of #115 since CI doesn't run properly on forks.

#deploy

#deploy

Unfortunately, there's quite a bit of breakage compared to the current (admittedly, extremely hairy) approach: https://leanprover-community.github.io/mathlib_docs_demo/latex.html

I'm closing this for now, feel free to re-open if you manage to get this approach working though!