Automate increase and decrease to item repair

Added automation for the repair macro.
It will now check the new "repairValue" data point under actor.system.crafting to allow for customization of the amount of HP that can be repaired with the macro. The default is set to 5 as per the base repair action.
Crafter's Eyepiece has been updated with two new rules to add to repairValue and to add a flavor note about the updated repair numbers.
This should close #10958
(Apologies for the two closed PRs, I had some issues with them but it's all resolved now)

This looks could, but would you mind making it crafting.repair an object with a lone value field? Then we won't have regret later if there is other repair-related data we want to track.

@stwlam Made the requested change!


Parameter to ignore self-signed certs on the authority endpoint

When using the oidc-client module to test against an endpoint using self-signed or internally signed certs, I get a "Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID" response, is there a way to specify the CA or ignore the certs?

That's something you need to configure in the browser or your host OS. That's not something this library can change.


some functions are missing/not available

i am getting this error:

TypeError: jenkins.all_builds is not a function

so i decided to print the jenkins object like this
var jenkinsapi = require('jenkins-api');
var jenkins = jenkinsapi.init('https://${username}:${token}@my-jenkins-uri');
console.log(jenkins)
and from the follow output it seems that some functions are missing for some reason...

{ build: [Function: build],
stop_build: [Function: stop_build],
all_jobs: [Function: all_jobs],
all_jobs_in_view: [Function: all_jobs_in_view],
job_info: [Function: job_info],
last_build_info: [Function: last_build_info],
last_completed_build_info: [Function: last_completed_build_info],
build_info: [Function: build_info],
last_build_report: [Function: last_build_report],
get_config_xml: [Function: get_config_xml],
create_job: [Function: create_job],
update_job: [Function: update_job],
copy_job: [Function: copy_job],
delete_job: [Function: delete_job],
disable_job: [Function: disable_job],
enable_job: [Function: enable_job],
last_success: [Function: last_success],
last_result: [Function: last_result],
queue: [Function: queue],
computers: [Function: computers],
job_output: [Function: job_output] }

I am using node v6.11.1.
Any ideas?

i compared the local file main.js in node_modules/jenkins-api/lib/ folder with the one in the github repo and they are different. I copied and pasted the file from github repo and now it seems to be working BUT every time i install the jenkins-api with the command npm install jenkins-api the file goes back to previous state and it doesn't work. Also, in the package.json it seems that i have the latest version of jenkins-api:     "jenkins-api": "^0.2.8"
i would like to hear and know why does this happens.
Thanks

The npm version is ways out of date I think. I installed directly from the repo:
"dependencies": {
"jenkins-api": "github:jansepar/node-jenkins-api",
}

thanks
although i don't understand why npm is not automatically updated from GitHub repo, it seems installing directly from github repo is the way to go

@andreash92 Hay, thanks for the note. NPM holds what the original devs deployed as a stable version two years ago and I'm trying to do quite some upgrade (there were 13 PRs waiting) and testing before I publish the next version. Please be patient.

makes sense now, thanks for letting us know! keep up the good work

@andreash92, @chrisallmark the version 0.3.1 is out now ;)


WIP: Try explicit operator for macos fix

I do not currently have a local macOS environment to reproduce https://open.cdash.org/viewBuildError.php?buildid=7756812. Will attempt to use CI for experimenting with a fix.

@dzenanz I believe CI failed on this one, probably best to revert.

This is all in my fork.

A hard reset to the previous commit, then?

No, I merged it on purpose. I will take a crack at this now, and I thought I would start from the latest WIP.

Understood, I believe the WIP simply introduced an additional bug 😅 but it is up to you how you would like to proceed.


SBT Error

Hello when trying to run sbt fro cloned repository I get the following error:
The java installation you have is not up to date
requires at least version 1.6+, you have
version 11.0.7
pi@octopi:~/ss/step-daemon $ javac --version
javac 11.0.7
Dont have anything special on this Octopi, just a few plugin.

Interesting, that is definitely a bit weird... did you use the bundled SBT jar in the repo, or SBT installed on the system level?

Might also be able to try the octoprint plugin directly. Should use the bunbled SBT. havent tried in on octopi yet, but works fine for raspbian

I get the same issue...
$ git clone https://github.com/colinrgodsey/step-daemon.git
$ cd step-daemon
$ ./sbt clean server/assembly

The java installation you have is not up to date
requires at least version 1.6+, you have
version 11.0.7

Please go to http://www.java.com/getjava/ and download
a valid Java Runtime and install before running .

$ javac --version
javac 11.0.7

Editing the file sbt-files/sbt-launch-lib.bash to change the following works around the problem:
# Detect that we have java installed.
checkJava() {
  return

  local required_version="$1"
  # Now check to see if it's a good enough version
  if [[ "$java_version" == "" ]]; then
    echo
    echo No java installations was detected.
    echo Please go to http://www.java.com/getjava/ and download
    echo
    exit 1
  elif [[ ! "$java_version" > "$required_version" ]]; then
    echo
    echo The java installation you have is not up to date
    echo $script_name requires at least version $required_version+, you have
    echo version $java_version
    echo
    echo Please go to http://www.java.com/getjava/ and download
    echo a valid Java Runtime and install before running $script_name.
    echo
    exit 1
  fi
}

Also fixed in SBT here: https://github.com/sbt/sbt-native-packager/pull/1111/commits/28416776f62d7457cf90f93f71a7479a54430923

go everything rewritten in go no, much better build management


Unable to get trades from Karken API

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.
I'm submitting a ...
[X] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
Used CLI paperbot for Karken and chose pair USDUSDT
Expected result (what you hoped would happen)
Gekko Cli Instance was supposed to run paperbot normally.
Actual result (unexpected outcome)
Gekko Cli Instance was unable to get recent trades
2018-08-07 04:16:19 (DEBUG):	Requested USDT/USD trade data from Kraken ... 2018-08-07 04:16:20 (DEBUG):	No new trades.
Instance hasn't been able to get a single update. Although doing paper trading though UI works but unfortunately not with command line.
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)
Using Develop Branch

Can you post full logs?

closing for inactivity.


Support DSCP Marking on external interfaces for QoS purposes

Describe the feature request
Network Functions shall support both server side (ingress gateway) and client side (egress sidecar/gateway) DCSP marking for interfaces including provisioning. Customers who use 5G Core solutions need a mechanism to set DSCP marking on all external facing interfaces. So this becomes an important requirement for telco deployments. Similar request can be seen already on Contour which is being worked upon. Other socket options like TCP KeepAlive seems to be already supported in Contour.
Background
Differentiated services or DiffServ is a computer networking architecture that specifies a simple and scalable mechanism for classifying and managing network traffic. DiffServ uses a 6-bit differentiated services code point (DSCP) in the 8-bit differentiated services field (DS field) in the IP header for packet classification purposes.
EnvoyFilter based solution
Envoy proxy has already exposed socket option through its XDS API (for both listener and cluster). The envoy proxy listener socket option DSCP configuration can work for Istio ingress gateway scenario, as well as Istio egress sidecar/gateway scenario. However, EnvoyFilters are always complex to manage and maintain.
A sample EnvoyFilter for DSCP socket option modification for IPv4 and IPv6 are given below:
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: ingress-dscp-socketoptions
  namespace: istio-system
spec:
  workloadSelector:
    labels:
      app: istio-ingressgateway
  configPatches:
  - applyTo: LISTENER
    match:
      context: GATEWAY
      listener:
        portNumber: 8443
    patch:
      operation: MERGE
      value:
        socket_options:   #  this values need to be double checked!
        - level: 0        #  0 for IPPROTO_IP
          name: 1         #  1 for IP_TOS
          int_value: 64   #0x10 IPTOS_LOWDELAY  ==> 10000(00)=2^6=64  0x08 IPTOS_THROUGHPUT ==> 1000(00)=2^5=32
          state: STATE_LISTENING  #STATE_PREBIND is default, other 2 values are STATE_BOUND, STATE_LISTENING

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: ingress-dscp-socketoptions
  namespace: istio-system
spec:
  workloadSelector:
    labels:
      app: istio-ingressgateway
  configPatches:
  - applyTo: LISTENER
    match:
      context: GATEWAY
      listener:
        portNumber: 8443
    patch:
      operation: MERGE
      value:
        socket_options:   #  this values need to be double checked!
        - level: 41        #  41 for IPPROTO_IPv6
          name: 67         #  67 for IPV6_TCLASS
          int_value: 32    ##IPV6_TCLASS is 32, and DSCP is 0x20, 0x10 IPTOS_LOWDELAY  ==> 10000(00)=2^6=64  0x08 IPTOS_THROUGHPUT ==> 1000(00)=2^5=32
          state: STATE_LISTENING  #STATE_PREBIND is default, other 2 values are STATE_BOUND, STATE_LISTENING

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: egress-dscp-socketoptions
spec:
  configPatches:
  - applyTo: CLUSTER
    match:
      cluster:
        name: "outbound|443||traffic.foo.com"
    patch:
      operation: MERGE
      value:
        upstream_bind_config:
          source_address:
            address: "<IP_ADDRESS>"
            port_value: 0
          socket_options:
          - level: 0        #  0 for IPPROTO_IP
            name: 1         #  1 for IP_TOS
            int_value: 32  #IP_TOS is 72, and DSCP is 0x48
            state: STATE_PREBIND  #STATE_PREBIND is default, other 2 values are STATE_BOUND, STATE_LISTENING

Solution Proposal
It would be nice if DSCP socket options configuration is supported via standard istio APIs.
For gateways, https://istio.io/latest/docs/reference/config/networking/gateway/#Port seems to be the right place for adding the same. For egress sidecar, https://istio.io/latest/docs/reference/config/networking/destination-rule/#TrafficPolicy-PortTrafficPolicy can be enhanced to add DSCP marking.
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Looks reasonable requirement to me

There have been numerous times when we've had to modify socket options via EnvoyFilters. It'd be great to have this implemented, but the only concern I have is that you need to pass in flags/integers to set these options. I'd be fine with us passing integers rather than trying to enumerate all possible settings (near impossible).

Thanks for your feedback @hzxuzhonghu and @jacob-delgado ! @howardjohn would be good to know your feedback as well, before I start with the implementation.

My main concern is that Gateway is merged. So defining listener properties in Gateway is not reliable. The best we can do is reject when there are conflicts. This makes it dangerous and hard to configure. For example, if I have 2 Gateways to start with that are merged. Then I apply DSCP to one of them... now suddenly it will be ignored and cause an outage. Its actually impossible to enable on existing Gateways safely when there are multiple since it cannot be done atomically.
IMO it is also pretty niche. I feel EnvoyFilter may still be most appropriate here.

Based on further discussions with @howardjohn @ramaraochavali  @jacob-delgado , it looks like EnvoyFilter itself would be the best way forward, as adding this to Gateway may cause additional complexities. We currently have issues on dynamic-updates of socket_options at listener level, but for that have raised issues in the envoy community.

F.Y.I.
PR for dynamic update of DSCP socket options: [WIP] listener: support update socket_options by soulxu · Pull Request #23189 · envoyproxy/envoy (github.com)


box_2 with Viz function set_tick_direction_spine_visibility

Current plot:

Plot with new function:

@anissa111 @michaelavs what is our plan with?


Assignment 1 Miyase Tekpinar

Introduction
Hi everyone,
I am Miyase, a PhD from bio-nanoscience departments (Applied Science). I am in my first year and I am looking for an apartment. In case I can find a pet friendly place, I WILL have two cats :D
Describe your research in 2-3 sentences to someone that is not from your field (please avoid abbreviations)
I am working on fluorescence microscopy data analysis where we use different methods specifically super resolution microscopy to answer interesting biological questions. My project focuses on the utilizing AI where the theoretical way of the analysis is not sufficient or not exist to extract information we are interested in.
My research entails the following aspects:

Research Aspect
Answer

Use/collect personal data (health data, interviews, surveys)
No

Use/collect experimental data (lab experiments, measurements with instruments)
Yes

Collaborate with industry
No

Write/develop software as the main output of the project
Yes

Use code (as in programming) for data analysis
Yes

Work with large data (images, simulation models)
Yes

Other:
N/A

Reflections on the importance of RDM videos
It was eye-opening, the example cases like stolen computers or burning building. The most likely case would be that you drop computer or spilling some liquids on it accidentally. Even fixing it is possible, it will take time and in that case it would be super handy to have every thing in a server or a cloud.

What would you like to learn during this course?
I would like to learn the ways/options to manage my data. But many times it is not your data but it is a team work. So it is also important to agree on this with you colleagues and so everyone will store their work in a reproducible way. It would be nice to know the strategies of data management for team work or how to explain this to colleagues.

Checklist assignments

[x] Assignment 1: creating a GitHub issue (before Class 1)
[x] Respond to the GitHub issue on 'data challenge'
[x] Assignment 2: Data Flow Map 1 (share a link in this issue before 17 May 13:00). Link:  https://docs.google.com/presentation/d/1MLh61qnrHwXBgdnxgDG0syGQkcdjwa3D/edit?usp=sharing&ouid=110108894326796208392&rtpof=true&sd=true
[ ] Provide feedback to at least one Assignment 2 from another participant
[x] Respond to the GitHub discussion on 'licenses'
[x] Respond to the GitHub discussion on 'folder structure'
[x] Respond to this GitHub issue with your readme file
[ ] Provide feedback to at least one readme file from another participant
[x] Assignment 3: Data Flow Map 2 (share a link in this issue before 31 May 13:00). Link:  https://docs.google.com/presentation/d/1OCAs3lVjtf8SPjl6SFS0_bcHk0tnAmEg/edit?usp=sharing&ouid=110108894326796208392&rtpof=true&sd=true
[ ] Provide feedback to at least one Assignment 3 from another participant
[x] Assignment 4: Data Management Plan (before Class 2)
[x] Respond to the GitHub discussion on 'Data Management Plans' if you have any questions (optional)
[x] Assignment 5: Data Flow Map 3: submit your slide (before Class 2)

Hi @Miytek! Thanks for handing in your assignment 2: well done!

Do you have any estimations for the image formats and sizes that you'll be generating for your simulated datasets?
You mention 'simulated' and that you're working with code in your assignment above: Where are you storing your analysis scripts? Note that you could use GitHub for this (unless the code is commercially sensitive, which I don't think is the case since I don't see a red flag for this in your assignment), or TU Delft's GitLab - which is more secure but makes it more difficult to collaborate with externals.
I highlighted the course for image analysis using Python to others, which may also be of interest to you: 'Image Processing with Python'. The eSciencecenter organises this workshop regularly if you can't make the one in June.
Regarding Q3: in principle if your data is on the project drive, it is already backed up at a different location by TU Delft ICT. If you want to take further precautions you can perhaps think of using OneDrive as a storage solution (up to 1 TB - pending on how large your images are). Others have mentioned in their assignment that the data repository where they want to share their data publicly also functions as a back up. More about that in the upcoming materials on FAIR, especially 'Realising FAIR: Data Publication'

Hope this helps!

Thanks very much for sharing your assignment 3 and for updating the public links @Miytek! It looks very clear, well done!
Documentation

Will you use any software/programmes to collect notes on your experiments? Other people have brought up using OneNote and Notepad ++ for these purposes, which might be interesting to check out.

Metadata:

I miss a bit of information/parameters that are important for your data collection.

File formats:

I had to check if .tiff files are an open format, because I think they are - but it is not directly called 'open' anywhere. In any case, this format is very widely used and can be opened by a wide range of programmes - so it is open enough. You can still convert images to PNG - but you will use a lot of information in this conversion progress. I would only do this conversion if it helps to reduce the file sizes and not too much information is lost in the process.

Access/Publication:

TU Delft expects you to share the underlying data/code of the PhD project - so unless there are any commercial/confidential restrictions on the data (which does not seem to be the case), you're expected to publicly share it using a data repository. This is indeed good to discuss with your supervisor!

@Miytek : I see you ticked the readme file box but I don't see a READme file shared here in your issue: do you have a link or the text available? Thanks!

Hi! Regarding your assignment 3:
Overall seems good! I like your data organization ideas!
Regarding your simulated dataset, what does 'huge pile' mean specifically?
Does your experimental dataset needs metadata as well?

Hi @Miytek! Please don't forget to provide others from the course with feedback on their Assignment 2, 3 and their READme: thanks!

Hi Miyase,
concerning your assignment 3, quick feedback:

data organisation: folder organisation makes sense and filenaming for a small amount of parameters seems also reasonable, but maybe you can write log-files (plain .txt, or .yaml, .json, .mat or so) into which you write all the parameters used, so you can load your input parameters as a struct variable that you can reuse somewhere or save more than just a few parameters.
I can really recommend github for version control, would also help if we want to reuse code in our lab or help each other with coding issues :)

Thanks very much @Miytek for rounding up the assignments!
Regarding your README:

This already looks very clear! I like how you explain all the contents clearly - well done!
for licence/restrictions of reuse you can already add your preferred licence (you mentioned CC BY-NC-SA 4.0 for data in the license thread). You can always update that information later if needed.
To link to publications I would use the DOI links: these are shorter and they do not break. So that would be https://doi.org/10.1371/journal.pone.0161602 for Girsault et al. 2016 and https://doi.org/10.1109/CVPR.2019.00223 for Krull et al. 2019 (you can just add https://doi.org/ before the numbers that start with the 10. to make it into a link if the publishers don't share the full link and just the DOI number).


concatResults function is wrong for temperature data

Hello!
When using the concatResults code as a reference I found that the code path for the temperature conversion looks quite wrong.
https://github.com/Infineon/TLI493D-W2BW/blob/master/src/Tli493d.cpp#L567-L574
upperByte contains Bit 11-4 and is not ambiguous
lowerByte only contains Bit 3 and 2 with two layouts which both don't work with the given code
Layout A) Bit 3&2 are in the LSBs so XXXX XX32
Layout B) They are in the MSBs still 32XX XXXX
The bit mask is 0xC0 = 0b1100 0000
1) value = (uint16_t)upperByte << 8;
2) value |= ((uint16_t)lowerByte & 0xC0) << 6;
3) value |= 0x06; //append bit 1 and 0
4) value >>= 4;

value's upper byte gets set to upperByte.
Masking lowerByte with 0xC0 will only keep the two MSB resulting in 0000 0000 or 3200 0000 depending on the given layout. Casting this to 16Bit and shifting 6 to the left results in either a value of 0 or 0032 0000 0000 0000. ORing this with value will do nothing or collide upperByte bits with lowerByte bits, which seems wrong.
ORing 0x06 = 0b0000 0110 to value
Right shifting of value by 4 makes step 3) irrelevant

I assume the correct version assuming lowerByte contains the temperature bits in its LSBs (layout A) should look like this:
value = (uint16_t)upperByte << 8;
value |= ((uint16_t)lowerByte & 0x03) << 6;
value >>= 4;

Assuming layout B:
value = (uint16_t)upperByte << 8;
value |= ((uint16_t)lowerByte & 0xC0) ;
value >>= 4;

I would do a PR, but I am not sure what your layout is, so I wanted to discuss this first.
Kind regards,
Riesi

Hi Riesi,
sorry for the late reply. You are totally right, I've already fixed this with a commit ~2 weeks ago.
I just forgot to reply to this issue, I'm very sorry.
The problem was the same in the "parent" library code, I've fixed it there as well: TLE493D-3DMagnetic-Sensor
Thank you very much for reporting this. I will close this issue for now, if there is anything else, feel free to reopen it.


After installing blank screen

After I installed the plugin, I see a bank screen. Also the admin panel is not accessible anymore. My fix was to manually delete the plugin and the website worked again as before.

Same here, after installing the plugin, the page returns:
This page isn’t working
 is currently unable to handle this request.
HTTP ERROR 500
On the http log it shows up as:
[Mon Jun 05 19:19:42.143513 2023] [proxy_fcgi:error] [pid 123456:tid<PHONE_NUMBER>12345] [client x.y.z.a:0] AH01071: Got error 'PHP message: PHP Fatal error:  Unparenthesized a ? b : c ? d : e is not supported. Use either (a ? b : c) ? d : e or a ? b : (c ? d : e) in /path/to/the/website/public_html/user/plugins/aboutme/aboutme.php on line 71'
As per the suggestion error I added parenthesis in the line 71:
return ($a['position'] < $b['position']) ? -1 : (($a['position'] == $b['position']) ? 0 : 1);
It seems to be a problem with PHP version

Same problem.
Thanks for the fix.

A new release has been drafted and should soon be picked up by Grav.


Simple example of using WebHook API with ASP.NET Core

Hi, wiz0u.
Can you provide simple example of using WebHook API with ASP.NET Core?
I don't know how to organize listening updates in the ASP.NET Core.
Thank you in advance!

Telegram MTProto protocol requires a permanent TCP connection with Telegram servers, so it's not compatible with a WebHook approach.
Of course, you can have a WTelegram.Client running as a BackgroundService in an ASP.NET webapp (see this example) but Telegram Client API won't call you back via WebHook. Only Bot API offers this kind of approach.
If I'm not clear, maybe this page explains it better: https://docs.telethon.dev/en/latest/concepts/botapi-vs-mtproto.html


Add Knative Eventing Kafka operator 0.6.0

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Have you tested an update to your Operator when deployed via OLM?

Your submission should not

[x] Modify more than one operator
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

@syedriko  @dmesser, @robszumski  I tested this operator on Openshift 4.1  as well as on  minikube (bonus)

The operator fails to deploy due to the missing  (and populated with Knative Eventing) knative-eventing namespace:
{"level":"info","ts":1560468060.7699637,"logger":"manifestival","msg":"Reading file","name":"deploy/crds/eventing_v1alpha1_knativeeventingkafka_cr.yaml"}
{"level":"info","ts":1560468060.7728634,"logger":"manifestival","msg":"Creating","name":"knative-eventing/knative-eventing-kafka","type":"eventing.knative.dev/v1alpha1, Kind=KnativeEventingKafka"}
{"level":"error","ts":1560468060.8266459,"logger":"cmd","msg":"","error":"namespaces \"knative-eventing\" not found","stacktrace":"github.com/openshift-knative/knative-kafka-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/syedriko/go/src/github.com/openshift-knative/knative-kafka-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/home/syedriko/go/src/github.com/openshift-knative/knative-kafka-operator/cmd/manager/main.go:108\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"}

This is actually expected, Knative Eventing is a prerequisite for Knative Kafka.

/test CVP

@J0zi or @aneeshkp  can you take a look here ?
It's sad that our release is stuck here, since a few dasy


Make viewport width adjustable for tabView

Use case

If there's a pageview design, with a smaller viewport fraction than 1, but also having swipeable tabs for quickly accessing a later page, currently a complex arrangement with a pageview and tabview and the controllers listening to each other and making sure the animations are in sync is required
Proposal
By simply making the viewport width an optional parameter on TabView, that defaults to 1, this sort of design is made much easier

Hi @Hari-07, Thanks for filing the issue. I am quite not sure I understand the proposal completely could you please share a sample code that explains your use case?

Consider a Design Like this:

With the current implementation, atleast to the best of my knowledge only way to do it is to either make my own tabbar, or use a tabbar and a pageview and write code to keep the controllers in sync. Since its not just a matter of indices and animations etc need to stay in sync it would require a non trivial amount of code
With the new change we can simply use a TabBar and TabBarView with a viewportFraction as a parameter.
I've written the code for it in https://gist.github.com/Hari-07/66ac2c2f68d18f28672f925536175c39
Pleas note that the ProposedImplementation in the gist will only work if you check out PR #98512

Thanks for the info @Hari-07, That looks like a valid proposal to me.
https://user-images.githubusercontent.com/31410839/154264794-190edbe7-8185-403d-bd78-7782dec06216.mov


Make diamond_square deterministic again

@roblabla is saying vanilla blocks generation is completely deterministic, including population.
Having the generation be deterministic is a good thing anyway.
Which means this Math.random() there should go way and use the seed https://github.com/mhsjlw/flying-squid/blob/master/src/lib/worldGenerations/diamond_square.js#L124

done in bb80bd7c44d777531af3db593b2df88a227daca1


[TODO] Remove hacktoberfest label when the event is over.

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
OAP server (apache/skywalking)
What happened
hacktoberfest label was added due to SkyWalking being involved in hacktoberfest 2022
What you expected to happen
Keep this open to track this label should be removed after the event finished.
How to reproduce
Nothing special
Anything else
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Oops my bad, I forgot to open this issue. Thanks.


Exercises-w1

Exercises
Name
Thijs Spijker
Class
Tech 1
GitHub username
iSirThijs
Bootcamp exercises
l1-looping-a-triangle.js
l1-fizzbuzz.js
l1-chessboard.js

Looking good! But, these are not all the exercises from the first week only from the first lesson.
Feel free to create a new issues once al the exercises from l1, l2 a& l3 are complete.


Feature/add visualization tutorial

This PR aims to add the visualization_tutorial.py based on the Visualization Tutorial, as was previously done for the Slicer4 Minute tutorial in fourMin_tutorial.py.

Maybe we can start using the Tutorial Repo? https://github.com/SlicerLatinAmerica/TestSlicerTutorials

Following @LuskasHusty suggestion, this PR will be closed. A new PR for the repository with tutorials already was created and can be checked here: https://github.com/SlicerLatinAmerica/TestSlicerTutorials/pull/1


[Docs] add the websites about geojson in map tutorial

https://visactor.com/vchart/guide/tutorial_docs/Chart_Types/Map
such as

https://geojson-maps.kyd.au/
https://mapshaper.org/

recommend this page
https://cloudcenter.tianditu.gov.cn/administrativeDivision

recommend this page cloudcenter.tianditu.gov.cn/administrativeDivision

Hi, I met this error code when I accessed it in Canada
418
Sorry, your request has been intercepted because it appears to be an attack.
Event ID:32-12-137-20240616033455-4e2eed13

If you are the webmaster, configure related parameters on the WAF console to allow your requests.


Identifier highlighting

Regular variables like foo are not highlighted any more specifically than source.julia. I don't know what the standard is for variables but if we could label them as identifier or variable or something that would be really useful.
The reason being that secret plugins, which may or may not exist, might want to highlight variables differently depending on whether they are defined or not.

Secret plugins -- looking forward to it!
I suppose we could do this. Wouldn't the  regex for a valid Julia variable name be the same as the regex for a value function name? I guess there are some symbols that are allowed to be function names, but now variable names (I'm thinking unicode operators like \dot[TAB] and \in[TAB]).

Matching against identifiers starting with unicode word characters, and containing only those, number characters and !, seems to work well. Could also check the source of Base.isidentifier in case that's not exact.

For reference:
is_id_start_char(c::Char) = ccall(:jl_id_start_char, Cint, (UInt32,), c) != 0
is_id_char(c::Char) = ccall(:jl_id_char, Cint, (UInt32,), c) != 0
function isidentifier(s::AbstractString)
    i = start(s)
    done(s, i) && return false
    (c, i) = next(s, i)
    is_id_start_char(c) || return false
    while !done(s, i)
        (c, i) = next(s, i)
        is_id_char(c) || return false
    end
    return true
end
isidentifier(s::Symbol) = isidentifier(string(s)

and the ccall functions (in src/flisp/julia_extensions.c):
DLLEXPORT int jl_id_start_char(uint32_t wc)
{
    if ((wc >= 'A' && wc <= 'Z') || (wc >= 'a' && wc <= 'z') || wc == '_')
        return 1;
    if (wc < 0xA1 || wc > 0x10ffff)
        return 0;
    const utf8proc_property_t *prop = utf8proc_get_property(wc);
    return is_wc_cat_id_start(wc, prop->category);
}

DLLEXPORT int jl_id_char(uint32_t wc)
{
    if ((wc >= 'A' && wc <= 'Z') || (wc >= 'a' && wc <= 'z') || wc == '_' ||
        (wc >= '0' && wc <= '9') || wc == '!')
        return 1;
    if (wc < 0xA1 || wc > 0x10ffff)
        return 0;
    const utf8proc_property_t *prop = utf8proc_get_property(wc);
    utf8proc_propval_t cat = prop->category;
    if (is_wc_cat_id_start(wc, cat)) return 1;
    if (cat == UTF8PROC_CATEGORY_MN || cat == UTF8PROC_CATEGORY_MC ||
        cat == UTF8PROC_CATEGORY_ND || cat == UTF8PROC_CATEGORY_PC ||
        cat == UTF8PROC_CATEGORY_SK || cat == UTF8PROC_CATEGORY_ME ||
        cat == UTF8PROC_CATEGORY_NO ||
        // primes (single, double, triple, their reverses, and quadruple)
        (wc >= 0x2032 && wc <= 0x2037) || (wc == 0x2057) ||
        // Other_ID_Continue
        wc == 0x0387 || wc == 0x19da || (wc >= 0x1369 && wc <= 0x1371))
        return 1;
    return 0;
}


Merge upstream

Merge from AnacondaRecipes

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The build section contained an unexpected subsection name. no_error_overlinking is not a valid subsection name.

For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.

@conda-forge-admin please rerender

@conda-forge-admin please rerender

@conda-forge-admin, please rerender

@mariusvniekerk do you know why the openjdk package is not working and we need the yum packages?

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.


Allow zero byte client ids and extract server assigned id from connack

From spec: A Server MAY allow a Client to supply a ClientID that has a length of zero bytes, however if it does so the Server MUST treat this as a special case and assign a unique ClientID to that Client [MQTT-3.1.3-6]. It MUST then process the CONNECT packet as if the Client had provided that unique ClientID, and MUST return the Assigned Client Identifier in the CONNACK packet

#59


Poor File Explorer Design in Studio Code

Issue Type: Performance Issue
Hello
I use Visual Studio Code to code all the files of my Web site. And it's quite a great software.
But your file explorer is a real nuisance. Akward and clumsy. Why did you reinvent the wheel ? It is done perfectly for Visual Studio 2019 (that I use to develope C++ application). But the wheel in Visal Studio code is turning square. I often use Windows Explorer besides for files handling. It's a pity, isn't it !
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z)
OS version: Windows_NT x64 10.0.18362

/needsMoreInfo
Please provide actual details what is wrong and what improvements you would expect.


No way in 6.x to build our own JSON and use LowLevel client to Index

NEST/Elasticsearch.Net version: 6.1
Elasticsearch version: 6.x
Description of the problem including expected versus actual behavior:
Steps to reproduce:

New Nuget packages installed & New elastic installed clean

Provide ConnectionSettings (if relevant):
Provide DebugInformation (if relevant):

Describe the feature:
In the old version (5), we were able to build our own JSON at about 10x the speed of serialization & deserialization. For this reason, we were using the LowLevel features to do something to the effect of this:
        var doc = BuildJsonDoc(record);
        Client.LowLevel.Index<dynamic>(IndexName, TypeName, record.Id.ToString(), doc);

Our "Record" type is extremely complex and does not belong, in whole, within elastic. As such, building the Json from the relevant pieces and parts is fast. The structure of our Record type is also significantly dynamic, in that we do not know 90% of the fields ahead of time. We parse them out of an array of other objects.
For elastic performance sake, simply importing a similar array structure is horrible. Thus, our method of stripping down our "Record" saves both 10x on import and about 6x on search performance.
Basically, we'd just like to have the version 6.x of Client.LowLevel, that removes the "Type" requirement (not used in 6.x), and allows the doc indexing to work properly.

@onspring-technologies is the issue slower serialization/deserialization is 6.x compared to 5.x? Can you share the connection settings  and client configuration you're using?

No, the issue is that the absolute fastest way to create the object we want to store in elastic is to simply build the Json with a Json builder. Creating a dynamic object and serializing it is much slower.

So I understand correctly, a custom type you have i.e. Record serializes/deserializes faster than dynamic?

No. We are building json from scratch, because our document is insanely simple, and much much faster serializing anything, especially the Record object, which has too much info. So, we simplify and only pull relevant, searchable data.  We build json from scratch, because it's faster than making that simple document as a dynamic object first, then serializing

We build json from scratch, because it's faster than making that simple document as a dynamic object first, then serializing

Serializing a JSON string or byte array of JSON would be much faster than serializing a dynamic type with JSON.Net, which would need to reflect over properties. I'm not sure what Json.NET does in the way of caching for dynamic types; it could be that no contracts for the dynamic structure are cached after first invocation and therefore reflection is happening on each call.
Do you have a small but complete reproducible example that demonstrates what you're seeing, and what you're doing instead?

I'm just trying to fully understand what the issue is. It seemed based on the original description that the issue was related to serialization performance, but you're saying that's not the case?

We just want to keep using the insert function on the low level client but sending it the string json document with the index name and Id.

The type parameter won't be going away in NEST/Elasticsearch.Net 6.x, since removing it now would break backwards binary compatibility for the client in a major version. If you don't care what the value for type is, you can use "doc" in Elasticsearch 6.0.x and 6.1.x or "_doc" in Elasticsearch 6.2.x + for the document type

You can send a raw JSON string in pretty much the same way as in 5.x
var client = new ElasticClient();
var json = "{ \"field\": \"value\" }";
client.LowLevel.Index<BytesResponse>("index", "type", json);

string implicitly converts to PostData and serializes with
https://github.com/elastic/elasticsearch-net/blob/96dff79b75eecf46cb5db927060166bda979edd7/src/Elasticsearch.Net/Transport/PostData.cs#L93-L94
I think we can forgo writing to a MemoryStream then copying to the request stream though, when DisableDirectStreaming is false (the default).

 Ensure that both Elasticsearch.Net and NEST are both version 6.1.0

        var doc = GetIndexRecordJson(app, record); // doc is a stringbuilder
        Client.LowLevel.Index<dynamic>(IndexName, app.Id.ToString(), record.Id.ToString(), doc);

We're getting "cannot convert from string to" errors. If we try to solve by adding a "null" in after the doc, we get an "implicit reference conversion" issue.

Don't use dynamic as response type use DynamicResponse.
See https://www.elastic.co/guide/en/elasticsearch/client/net-api/master/elasticsearch-net-breaking-changes.html#_response_types

Tested and verified that DynamicReponse worked.

@onspring-technologies Great! Are you happy for us to close this issue?

Go for it!


Expose frame's length

Expose the length of the frame as it might be needed before sending or receiving frames.
Reference: https://github.com/Lukasa/hyper/pull/135

Thanks @jdecuyper! I'm going to add a test for this just to make sure it behaves correctly. =D


A couple of questions...

lfs_config.block_cycles : Is this supposed to be the number of write/erase cycles for a block? Why does example have such a low value then? Any guidance for setting this value (use prog/erase limit from part data sheet; use 50% of limit / ???)?
lfs_config.sync : What is the purpose of this function? How should it be implemented? Is it just a "write"?
lfs_config.nnn_size : Any guidance for setting these values?
Thanks for the help!

Good questions, let me answer them backwards

lfs_config.nnn_size : Any guidance for setting these values?

These mostly depend on the hardware and RAM you have available.
You generally want these to be as small as your storage can handle:

read_size
prog_size
block_size

And you want these to be as large as you have RAM for

cache_size
lookahead_size

For now the best resource is probably to search through the existing issues on github. I have a TODO item to add a more thorough document, which I realize I am severely behind on, but it is what it is.

lfs_config.sync : What is the purpose of this function? How should it be implemented? Is it just a "write"?

lfs_config.sync says "hey any writes I sent you really need to be written now!". In more complex block devices there can be layers of caching/reordering that avoid going all the way to disk until it's needed. On SD/eMMC this caching often even exists in special buffers on the storage itself. But if power gets cut unexpectedly, the data in these buffers can be lost.
So generally lfs_config.sync is used to flush buffers at every layer. LittleFS calls sync when it needs to ensure the device state is consistent, such as in lfs_file_sync, lfs_file_close, or most other metadata tampering functions.
I you're porting LittleFS to a raw block device, you can safely define lfs_config.sync to return 0. Though it would be worth reading through your devices datasheet to make sure there is no SYNC command required for consistency during power-loss.

lfs_config.block_cycles : Is this supposed to be the number of write/erase cycles for a block? Why does example have such a low value then? Any guidance for setting this value (use prog/erase limit from part data sheet; use 50% of limit / ???)?

Ah no! 50% is a terrible idea. This is probably on me for choosing such an ambiguous name/having insufficient documentation.
block_cycles defines the number of cycles until a metadata block is moved. The more a metadata block is moved, the more distributed the wear.
Unfortunately, due to LittleFS design, moving metadata blocks is fairly expensive, so larger numbers means fewer dependent blocks must be written (and interestingly lower wear).
So 50% is a bad idea because littlefs would only move the metadata block after fully wearing the block %50 of its total lifetime. It would be better to choose a number around 10, 100 or 1000 cycles to minimize the wear to the blocks while also minimizing the number of metadata relocations.
Unfortunately I don't have much more info than that. The question of what is the best block_cycles is sort of unanswered. I know it's >2 and <n*erase_limit, but I haven't been able to test for what the optimal value would be.

Thanks for the reply.
I am using a SPI NOR device (MX25L3233F).
When you say:

You generally want these to be as small as your storage can handle:
read_size
prog_size
block_size

do you mean as small as the device can handle? The only "fixed" value seems to be the .block_size of 4096. I believe I can read/program a byte, but that seems bad. Just as using the block size of 4096 for read/prog seems wasteful of the RAM I have available. The example uses 16 for .read_size and .prog_size. Should they match the block size? or pick something that uses an amount of RAM I can live with (I presume powers of 2 are best)?

And you want these to be as large as you have RAM for
cache_size
lookahead_size

Again, using a block_size seems wasteful. Should these equal what is used for the read/prog size or be larger/smaller?
Thanks again!

I think some of the confusion is that only some of these fields have related RAM buffers. read_size/prog_size/block_size aren't used to allocate memory, they are only used to determine what the device is capable of. cache_size/lookahead_size on the other hand do use RAM buffers, so there is a trade-off between performance and memory, though they quickly have diminishing returns.

I believe I can read/program a byte, but that seems bad.

Setting read_size/prog_size to a byte is correct. This is usually the case on NOR flash, it gets weirder on larger storage (NAND, eMMC, etc)
This tells LittleFS that it must read/write in multiples of that size. The key word there being "multiples". So if read_size = 1 byte, LittleFS may write 61 bytes depending on how much data is available. If read_size = 64 bytes, LittleFS will have to pad the data up to 64 bytes so that the driver can handle it.
If you have a loop like this in your driver you can batch together multiple bytes into single program commands to reduce bus overhead to the device:
https://github.com/ARMmbed/mbed-os/blob/master/storage/blockdevice/COMPONENT_SPIF/source/SPIFBlockDevice.cpp#L268
Usually these reads/writes are limited to the cache_size, but this isn't always the case, sometimes LittleFS can bypass the cache.

Just as using the block size of 4096 for read/prog seems wasteful of the RAM I have available.

LittleFS doesn't need to allocate a buffer for the block_size. This number just tells LittleFS what unit to use for the blocks on the storage. This number can get quite large (~64KiB on NAND), so by necessity all flash filesystems must operate on smaller units inside the block.

I presume powers of 2 are best

LittleFS doesn't actual need powers of 2, but it needs read/prog sizes to be factors of the block size, which gets complicated if you don't use powers of 2. But sometimes it can be useful, if you wanted to sneak ECC or hashes between pages on a block.

Again, using a block_size seems wasteful. Should these equal what is used for the read/prog size or be larger/smaller?

This is a trade-off of performance vs memory, so it depends on your application. Last I checked Mbed OS defaults to 64 bytes, but this could be increased if your application is disk heavy:
https://github.com/ARMmbed/mbed-os/blob/master/storage/filesystem/littlefsv2/mbed_lib.json#L16
There are diminishing returns though, at some point throwing more RAM at the problem won't speed things up.
There are maximums, where more RAM just goes unused (actually should LittleFS assert on these?)

cache_size <= block_size, only a single block can be cached at the time of writing
lookahead_size <= block_count / 8, lookahead_size stores a bit per block

But the actual values you should use depend on your application + device + RAM. So the only real answer would be to test and see what you can get away with on your system.


[WIP] enable point range

Signed-off-by: AerysNan<EMAIL_ADDRESS>What have you changed?
Please explain in detail what the changes are in this PR and why they are needed:
Add is_point field to KeyRange struct so that when KeyRange contains only one key, less network traffic is introduced and there is no need to run is_prefix_next.
What is the type of the changes?

Improvement (a change which is an improvement to an existing feature)

How is the PR tested?

Unit test
Integration test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No.
Does this PR affect tidb-ansible?
No.
Refer to a related PR or issue link (optional)
pingcap/tidb#13944
pingcap/kvproto#508
Benchmark result if necessary (optional)
TODO.

Closed since no further updates.


Removed excessive tests.

It's connected with PR #2623. Excessive test methods were removed from GroupReduceITCase. There are appropriate targeted unit tests in KryoCollectionsSerializerTest class.

You removed the tests you introduced in #2623. If there were any tests in KryoCollectionsSerializerTest which test Arrays.asList(..) they would have failed prior merging #2623. Could you add a unit test for Arrays.asList(..)?

I removed a method from ITCase only. There is testJavaArraysAsList method in KryoCollectionsSerializerTest class to check it. Yep, before merging #2623, they have not been successful.

Done.


Clarify ResourceManager errors for startup crashes

(Ignore the blend mode commit sorry - do not merge this first until #92 has been merged plskthx)
This should create less confusion when something crashes on startup.

The Resource Manager has since been overhauled, so this pull request is no longer applicable.


Specify API endpoint explicitly; collapse changes

The docs currently omit mentioning the most foundational requirement for calling an API: its primary endpoint. I have tried to rectify this in a generic way (not much style, because I don't all the Docker documentation conventions).
Also, I have allowed that the long changes section be collapsible using the example from https://github.com/docker/docker.github.io/blob/master/compose/compose-file/compose-file-v3.md

I thought https://docs.docker.com/registry/spec/api/ was no longer linked to this repo but when I click on Edit this page (top right corner) I get redirected to this repo.
We should probably break the relationship between the two. @milosgajdos @thaJeztah WDYT?
Also, DockerHub details don't belong here IMO.

We should probably break the relationship between the two. @milosgajdos @thaJeztah WDYT?
Also, DockerHub details don't belong here IMO.

Yeah, agreed, these references must go 👍

Yes, I was confused as to why I was directed to modify docs on a non-Docker owned repo. So this is a PR to the completely incorrect repo, yes?

@mavaddat, that's correct. I'm not sure where is the right repository for this though (if there is one). You mention that "I was directed to modify docs on a non-Docker owned repo". Can you share from where that was?

@joaodrp I think there was a PR by @thaJeztah that cleans up the docs and removes all old references 🤔

Thanks for the ping; yes, that PR is moving the docs back into this repository; we may then still be including the docs at docs.docker.com (consuming it from the source in this repository).
But: while I understand where @mavaddat is coming from, I don't think we should describe the endpoints in context of a specific registry (Docker Hub in this case); it's the documentation of a spec, and not documentation for Docker Hub. This project  - and the documentation - is about an implementation of the specification, and allows users to run their own registry, in which case documenting the endpoints with URLs matching Docker Hub's URLs wouldn't be helpful.
Perhaps it could make sense to have documentation at docs.docker.com that's specific to Docker Hub (although it would basically mean "prefix https://registry-1.docker.io/ to all endpoints), and there have been requests for more documentation for Docker Hub's APIs (see https://github.com/docker/roadmap/issues/20) - given those are primarily for Docker Hub -specific APIs (not for the registry)

You mention that "I was directed to modify docs on a non-Docker owned repo". Can you share from where that was?

Yes, it is this one (distribution/distribution). I just meant that when I clicked "Edit on GitHub" for the docs on https://docs.docker.com/registry/spec/api/, I am sent here.

I used the passive voice "directed to modify" to diffuse my responsibility for this misdirected PR.


Spelling fixes

I was nosying at https://github.com/thephpleague/omnipay-sagepay/pull/156 & realised
it was full of as-yet-unfixed spelling fixes. This PR just has the ones in the
tests directory from that PR

Thank you  - sorry been so busy for so long.


Extension should look for templates relatively or by setting.

I'm using Webpack to build my theme so I have the liquid files inside a /src/static directory. I keep these static files in the same directory structure as they will be built as.
{% comment %} Inside theme.liquid {% endcomment %}
{% section 'header' %}

So theme-check extension checks my code automatically and gives me  a MissingTemplate.
Since this file is located at src/static/layout I would like theme check to look in src/static/sections/header.liquid
If that is not possible maybe a base url setting for the extension for which theme check will be ran in.

I have the same issue.
It seems that the extension is built to only be compatible with flat theme structures.

I guess we could add a .theme-check.yml and set the root to either the '/dist' folder or '/src/static'

This seems broken when editing a theme from within a VSCode Workspace with many directories. I have my root: . in theme-check.yml but the root it goes to is seemingly the first directory in the workspace. If I open just the theme directory in a new VSCode window it works.


Better handling of key parameter for protected interfaces

Interfaces that only appear in the list when passing an API key implicitly require an API key to access too, but this isn't documented

May be fixed by #40


Gradient checkpointing seems to conflict with Keras batch norm

I tried this out but get an Error when computing the gradients with the provided function using manually selected checkpoints. I get three different errors at the same time, and am not sure what of my graph is actually causing them, so I would appreciate some hints so that I could come up with a minimal non-working example. I currently use TF1.13.1 and especially the tf.keras.layers.BatchNormalization (just saying this because it pops up along the Error message). Is there any hope that this would be an easy fix?
Traceback (most recent call last):
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/ops/gradients_impl.py", line 415, in _MaybeCompile
    xla_compile = op.get_attr("_XlaCompile")
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 2413, in get_attr
    raise ValueError(str(e))
ValueError: Operation 'optimizer/head/convolve_batch_activate_20/batch_normalization_v1_21/cond/ReadVariableOp_1/Switch' has no attr named '_XlaCompile'.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 455, in _apply_op_helper
    as_ref=input_arg.is_ref)
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1240, in internal_convert_n_to_tensor
    ctx=ctx))
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1175, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 977, in _TensorTensorConversionFunction
    (dtype.name, t.dtype.name, str(t)))
ValueError: Tensor conversion requested dtype float32 for Tensor with dtype resource: 'Tensor("optimizer/gradients/optimizer/head/convolve_batch_activate_20/batch_normalization_v1_21/cond/ReadVariableOp_1/Switch
_grad/Switch_1:1", shape=(), dtype=resource)'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "./src/sadt.py", line 544, in <module>
    with SpaceAndDeformableTimeNetwork(cfg, datasets) as exp:
  File "/lhome/davidj2/code/sync/space_and_deformable_time/src/xxsflow/experiments/base_experiment.py", line 42, in __enter__
    self.build_graph()
  File "./src/sadt.py", line 298, in build_graph
    self.optimizer_op = self.optimizer
  File "/lhome/davidj2/code/sync/space_and_deformable_time/src/xxsflow/utils.py", line 388, in wrapped_function
    setattr(self, attribute, function(self))
  File "./src/sadt.py", line 267, in optimizer
    grads = grads = tf.gradients(self.loss, tf.trainable_variables())
  File "/lhome/davidj2/code/sync/space_and_deformable_time/packages/gradient_checkpointing/memory_saving_gradients.py", line 40, in gradients_collection
    return gradients(ys, xs, grad_ys, checkpoints='collection', **kwargs)
  File "/lhome/davidj2/code/sync/space_and_deformable_time/packages/gradient_checkpointing/memory_saving_gradients.py", line 227, in gradients
    dv = tf_gradients(ys=copied_ys, xs=boundary+xs, grad_ys=grad_ys, **kwargs)
  File "/lhome/davidj2/code/sync/space_and_deformable_time/packages/gradient_checkpointing/memory_saving_gradients.py", line 27, in tf_gradients
    return tf_gradient_function(ys, *args, **kwargs)
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/ops/gradients_impl.py", line 664, in gradients
    unconnected_gradients)
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/ops/gradients_impl.py", line 965, in _GradientsHelper
    lambda: grad_fn(op, *out_grads))
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/ops/gradients_impl.py", line 420, in _MaybeCompile
    return grad_fn()  # Exit early
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/ops/gradients_impl.py", line 965, in <lambda>
    lambda: grad_fn(op, *out_grads))
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/ops/control_flow_grad.py", line 88, in _SwitchGrad
    return merge([false_grad, true_grad])[0], None
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/ops/control_flow_ops.py", line 466, in merge
    return gen_control_flow_ops.merge(inputs, name)
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/ops/gen_control_flow_ops.py", line 418, in merge
    "Merge", inputs=inputs, name=name)
  File "/lhome/davidj2/code/sync/space_and_deformable_time/.venv/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 483, in _apply_op_helper
    raise TypeError("%s that don't all match." % prefix)
TypeError: Tensors in list passed to 'inputs' of 'Merge' Op have types [float32, resource] that don't all match.

It seems like a combination of switch (generated by tf.cond) and resource variables. One thing to try could be to add more things to exclude into the list here:
https://github.com/cybertronai/gradient-checkpointing/blob/master/memory_saving_gradients.py#L85

Currently that list filters by op name, a better thing may be to filter by op type. IE, exclude anything like ReadVariableOp, Switch and Merge. If you figure this out, a pull request would be appreciated!

Thanks for your insight, I will definitely give it a shoot on the weekend.
Yesterday I also tried to come up with a minimal working example for my use case, but somehow I am not able to. Maybe I am still not fully understanding what is going on in TF or I am doing something wrong, so if you maybe just could answer my question here:
I have a layer with comparatively small input and output tensors but large intermediate tensors, which are kept in memory for backpropagation. This is what I tried recreating in my minimal example (see code below). I also attached an image of the graph. What I am not understanding is, that even with a high number of layers (n=128) I do not run out of memory for the gradient computation. The forward pass should be fine for any number of n given enough time, as it can safely delete the intermediate representations directly, however I thought TF would keep the intermediate tensors for backpropagation of the gradients? What am I missing?
import shutil
import os.path as osp
import numpy as np
import tensorflow as tf

def massive_layer(t):
    with tf.name_scope('massive_layer'):
        upsample = tf.tile(t[None, None, None], [32, 1024, 1024])
        upsample = upsample + tf.reduce_mean(upsample)
        reduce = tf.reduce_mean(upsample * 0.5)
        return reduce

var = tf.Variable(np.random.normal(size=()), dtype=tf.float32)
d = var
n = 3
for i in range(n):
    d = massive_layer(d)
grads = tf.gradients(d, var)[0]

shutil.rmtree(osp.join('/tmp', 'custom_gradients_testtb'), ignore_errors=True)
tb_saver = tf.summary.FileWriter(osp.join(
    '/tmp', 'custom_gradients_testtb',
))

with tf.Session() as s:
    s.run(tf.global_variables_initializer())
    tb_saver.add_graph(s.graph)
    print(s.run(d))
    print(s.run([d, grads]))

TF only stores activations if you request gradients, if you don't request them in your session.run, it'll  discard activations

I know. Still even when requesting the gradients (see last line of code example) it is not running out of memory for arbitrary sizes.

TensorFlow can store input of the grad function instead of output, ie it does this for ReLU. Not sure if that's the case for tile, but your input is quite input. Try stacking a couple of layers on top of each other

i have the same problem using tensorflow 1.15 and 1.14.
it all behaves pretty weird between versions. eg installing it via pip does not work (i think this is due how conda handles cuda).
To reproduce:
use densenet from keras applications and train a classifier.
Setup a)
conda install tensorflow-gpu=1
conda install keras-gpu
this works while gradient_memory only gives sth between 3-4 memory increase (OOM with batch size 4 for my image size, while 1 works without memgrad)
Setup b)
if you not install keras and switch all imports to tensorflow.keras you get the error reported by op. if you change
import memory_saving_gradients as gc
from tensorflow.python.ops import gradients as tf_gradients
tf_gradients.gradients = gc.gradients_speed

to
import tensorflow as tf
import memory_saving_gradients
# monkey patch tf.gradients to point to our custom version, with automatic checkpoint selection
tf.__dict__["gradients"] = memory_saving_gradients.gradients_speed

No errors, but there is no effect on memory size. This probably means it is not used

@yaroslavvb could you have a look and see what could be done (don't want to switch back to original keras since they will stop updating in april 2020)

@shsshs sorry, haven't kept up with TF backend changes (mostly stay in PyTorch-land nowadays), I'll be happy to merge any PR's that fix it though

It seems that change the word “/read” to “/Read” in line 90 and line92 works.
Testing on tensorflow.python.keras.applications.InceptionV3, TF1.14.
    fwd_ops = [op for op in fwd_ops if not '/Read' in op.name]
    ts_all = ge.filter_ts(fwd_ops, True) # get the tensors
    ts_all = [t for t in ts_all if '/Read' not in t.name]


The "path" argument must be of type string?!?

Hi!
I just installed the module via yarn. Now i'm getting the following error when importing the component into my component:
... node_modules/react-kronos/dist/bundle.js: The "path" argument must be of type string
What gives?

Gotta be honest, I have no idea. But a quick google search for "yarn the path argument must be of type string" reveals a bunch of seemingly related issues. Maybe one of them contains a solution that works.


Multiple component select in designer

Describe the desired feature
Allow the developer to shift+click to select multiple components, and filter the properties list such that you can set common properties of the selected components.
Give an example of how this feature would be used
Consider an app with multiple buttons that all need to look the same. Right now, one way to do this is to put the buttons in a list and set their properties using a for each loop, but this means that the designer doesn't reflect what the app looks like. Alternatively, a developer can go button by button changing the values, which is cumbersome in case one ever wants to change the design slightly.
Why doesn't the current App Inventor system address this use case?
It's possible to make UI elements all look the same, but it is very tedious. Either you must go component by component adjusting the properties, or you need to use a for each loop in blocks (so the designer doesn't reflect the actual design).
Why is this feature beneficial to App Inventor's educational mission?
We often see students wanting to make complex UIs with a consistent visual presentation. Making it easier to customize the app UI may reduce discouragement students face when trying to make something complicated and realizing just how hard it is.

Fixed via #1891


Restore intersphinx in docs config

#21 removed the interphinx extension because it was failing with miss-configured external references.  The task is

restore using intersphinx
fix the URLs for any inventories we need

Is it because the event-model docs were moved to its repo's branch https://github.com/bluesky/event-model/tree/gh-pages?


Add to doc a section highlighting the functionality or lack there of across the interfaces

From our review for the Journal of Open Source Software, openjournals/joss-reviews#5236, it was recommended that we add details discussing the similarities and differences across the interfaces.

The best place to do this is most likely on the "languages" landing page, no? https://roualdes.github.io/bridgestan/latest/languages.html
Something like

All language interfaces expose the same core functionality from the C API [link]. Additional "quality of life" features such as the ability to download BridgeStan's source code automatically or compile models from inside the language (rather than manually calling make) are available on a best-effort basis. If you are missing these features in your favorite language, we would welcome a contribution!

Ya, I like that.

I like it, too and it's exactly what I think we should write in our doc.
For the article, I'd try to stay a bit more formal in tone than "we would welcome a contribution!"   Given the space limitation, I suggest just dropping that last sentence, or at most, replacing it with some hint we might add more in the future.


Fix/power netlisting

@854768750 @Lastdayends Hack to propagate global power names down the hierarchy.
Fixes some of the issues in vco_dtype_12_hierarchical_res
Known issues are now:

[ ] Resistors causes multiple width and min length errors.
[x] Power net opens are reported on sub-hierarchies (because power is not routed until the top layer.)

I don’t think I’m going to fix that problem. Fix the shorts first. It is hard to tell what is happening if there are shorts.
From: 854768750<EMAIL_ADDRESS>Sent: Tuesday, April 7, 2020 10:17 AM
To: ALIGN-analoglayout/ALIGN-public<EMAIL_ADDRESS>Cc: Burns, Steven M<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ALIGN-analoglayout/ALIGN-public] Fix/power netlisting (#400)
@stevenmburnshttps://github.com/stevenmburns
Thank you. Power net open report is solved.
Another problem is, when two metals are short, minspace error of the two metals is also reported. Should minspace be reported?
SHORT CONNECTPAIR M2 ([18204, 68, 19316, 100], 'op<7>') ([19292, 68, 19364, 100], 'on<8>')
DRC ERROR MinSpace violation on M2: op<7>[18204, 68, 19316, 100] x on<8>[19292, 68, 19476, 100]
[p1]https://user-images.githubusercontent.com/28666144/78698071-5a7a2200-78c7-11ea-8ee7-ea5e9489acf4.PNG
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/ALIGN-analoglayout/ALIGN-public/pull/400#issuecomment-610507396, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AALRI7SLXOLSMZUIMDQY5KTRLNNYFANCNFSM4MCQ2ZZQ.

I don’t think I’m going to fix that problem. Fix the shorts first. It is hard to tell what is happening if there are shorts.

I know why this is happening. I didn't test for overlap in the original minspace test. Its a one-line change so I went ahead and fixed it. It only eliminates 2 MinSpace Errors. There are still hundreds of shorts and DRC errors to fix.

@parijatm
Thank you for updating this.
Yishuang

@parijatm Can you approve this PR? If there are shorts in the design, I don't know how to split up the rectangles to say this part of the wire is attached to net A and this part is attached to net B. If you do it wrong, then there may be DRCs because of the way you break it up into two nets. I think we should just ignore DRCs until we resolve the shorts (which really shouldn't be happening.)


Escaping titles is not working as expected

I think I was wrong in how I am trying to store titles in the DB. There are a lot of & and " that are not being displayed as I would want. This is a bug.

I think I resolved this with the latest commit.


duplicate code refactoring

Duplicate code found in 2 classes. Refactored the code.

Hey @prabh27 , thanks for the input here, but I think we are going to keep it as-is for the moment.
In our opinion it is easier to understand what is happening this way. The ZkDataMigration classes are for one-time changes in zookeeper (think database migrations). So, having one class per migration helps us completely separate what is happening and in what order (migrationNumber) without having to dig through other classes


fix: rename flash Object class to FlashObject to avoid transpilation issues

fixes #341

Change makes sense to me 👍


Eclipse issue with sdk jar

My eclipse does not like the classpath that this plugin generates.
I get this error within eclipse
The App Engine SDK '/Users/gunnar/.gradle/caches/modules-2/files-2.1/com.google.appengine/appengine-api-1.0-sdk/1.9.19/188d623cac7193f2f46f44dc7b76f3ba2342a09f/appengine-api-1.0-sdk-1.9.19.jar' on the project's build path is not valid (SDK location '/Users/gunnar/.gradle/caches/modules-2/files-2.1/com.google.appengine/appengine-api-1.0-sdk/1.9.19/188d623cac7193f2f46f44dc7b76f3ba2342a09f/appengine-api-1.0-sdk-1.9.19.jar' is not a directory) davinci     Unknown Google App Engine Problem

A cure anyone?

Are you using gradle with the appengine tooling in eclipse?  I'm not completely sure what the interactions there are.  It appears it's trying to find your sdk directory and it's configured to that sdk-api jar.

Yes we are using "Google Plugin for Eclipse" in eclipse. We are also using the eclipse gradle plugin.
We want to use gradle as build system but still be able to work in eclipse. Is this a problem?

It's not clear to me the implications of using both together. The Google Plugin for Eclipse (GPE) expects to use the Eclipse builder for everything.  What parts of GPE do you need that cannot be replicated by gradle?

None I guess except that we have some people here that are used to do it that way. Perhaps they will have to do it the gradle way.

The biggest thing GPE and Cloud Tools for Eclipse have is hot swap, not just for Java files, but also for JSP files.  This is key to having a very fast, iterative, development cycle and is really helpful when making small, iterative changes and reloading the web page to see the change.
The hot swap in Gradle doesn't appear to be able to deal with JSP files (which is where a majority of front-end, visual code will go where a developer may be more likely to want to do a "change -> Save -> Refresh the page" cycle...  hope this helps clarify why this would be helpful to have these tools work together.
I think with Cloud Tools for Eclipse, it may be easier than with the deprecated Google Plugin for Eclipse, because the CT4E file structure now matches the Maven/Gradle default structure...


remove the default random listening address

Remove the default random listening address, listen to no addresses by default.
Cc https://github.com/rs-ipfs/rust-ipfs/issues/356

Hmm, the conformance tests need to be adjusted too, either at http config level when profile = test or in index.js.

In the end the ipfs-http config file needed to be enhanced with the random listening address; the format is compatible with the go-ipfs config file.

bors r+


Add proper DVC support

Save/load files with DVC.
Question: should this be part of core or should we make it a plugin to facilitate creation of other storage extensions?

I think we addressed this, but this may be revisited due to attempts to have better integrations. Need to rethink this.


X11GLXDrawableFactory - Could not initialize shared resources for X11GraphicsDevice

When I try to run the jMAVSim, I run into the following error. I am using Ubuntu 16.04. Please help!
`medhijk@asimov:~/Firmware$ make posix jmavsim
[2/2] cd /home/medhijk/Firmware/build/...hijk/Firmware/build/posix_sitl_default
args: /home/medhijk/Firmware/build/posix_sitl_default/px4 posix-configs/SITL/init/ekf2 none jmavsim none /home/medhijk/Firmware /home/medhijk/Firmware/build/posix_sitl_default
SITL ARGS
sitl_bin: /home/medhijk/Firmware/build/posix_sitl_default/px4
rcS_dir: posix-configs/SITL/init/ekf2
debugger: none
program: jmavsim
model: none
src_path: /home/medhijk/Firmware
build_path: /home/medhijk/Firmware/build/posix_sitl_default
empty model, setting iris as default
SITL COMMAND: /home/medhijk/Firmware/build/posix_sitl_default/px4 /home/medhijk/Firmware /home/medhijk/Firmware/posix-configs/SITL/init/ekf2/iris
data path: /home/medhijk/Firmware
commands file: /home/medhijk/Firmware/posix-configs/SITL/init/ekf2/iris
250 WARNING: setRealtimeSched failed (not run as root?)
| ___ \ \ \ / / / |
| |/ / \ V / / /| |
| __/ / \ / /| |
| | / /^\ \ ___ |
| / / |/
px4 starting.
INFO [dataman] Unknown restart, data manager file 'rootfs/fs/microsd/dataman' size is 11405132 bytes
INFO [simulator] Waiting for initial data on UDP port 14560. Please start the flight simulator to proceed..
Buildfile: /home/medhijk/Firmware/Tools/jMAVSim/build.xml
make_dirs:
compile:
create_run_jar:
copy_res:
BUILD SUCCESSFUL
Total time: 1 second
Options parsed, starting Sim.
Starting GUI...
3D [dev] 1.6.0-pre12-daily-experimental daily
com.jogamp.opengl.GLException: X11GLXDrawableFactory - Could not initialize shared resources for X11GraphicsDevice[type .x11, connection :0, unitID 0, handle 0x0, owner false, ResourceToolkitLock[obj 0x4bab7e41, isOwner false, <37eca4c6, 580b55d5>[count 0, qsz 0, owner ]]]
at jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:326)
at jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:297)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:688)
at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:580)
at jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:297)
... 2 more
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)
Caused by: java.lang.InternalError: XXX0 profile[1]: GL3bc -> profileImpl GL4bc !!! not mapped
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2047)
at com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1917)
at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1866)
at com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1835)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:79)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:229)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:215)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2272)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:1020)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:1049)
at com.jogamp.opengl.GLProfile.getMaxFixedFunc(GLProfile.java:802)
at javax.media.j3d.JoglPipeline.initialize(JoglPipeline.java:132)
at javax.media.j3d.Pipeline.createPipeline(Pipeline.java:92)
at javax.media.j3d.MasterControl.loadLibraries(MasterControl.java:837)
at javax.media.j3d.VirtualUniverse.(VirtualUniverse.java:274)
at me.drton.jmavsim.Visualizer3D.(Visualizer3D.java:154)
at me.drton.jmavsim.Simulator.(Simulator.java:157)
at me.drton.jmavsim.Simulator.main(Simulator.java:678)
... 5 more
X11Util.Display: Shutdown (JVM shutdown: true, open (no close attempt): 1/1, reusable (open, marked uncloseable): 0, pending (open in creation order): 1)
X11Util: Open X11 Display Connections: 1
X11Util: Open[0]: NamedX11Display[:0, 0x7fec7400d080, refCount 1, unCloseable false]
Options parsed, starting Sim.
Starting GUI...
3D [dev] 1.6.0-pre12-daily-experimental daily
com.jogamp.opengl.GLException: X11GLXDrawableFactory - Could not initialize shared resources for X11GraphicsDevice[type .x11, connection :0, unitID 0, handle 0x0, owner false, ResourceToolkitLock[obj 0x218d7dcf, isOwner false, <6b69ecc8, 5534c0e8>[count 0, qsz 0, owner ]]]
at jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:326)
at jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:297)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:688)
at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:580)
at jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:297)
... 2 more
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)
Caused by: java.lang.InternalError: XXX0 profile[1]: GL3bc -> profileImpl GL4bc !!! not mapped
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2047)
at com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1917)
at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1866)
at com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1835)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:79)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:229)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:215)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2272)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:1020)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:1049)
at com.jogamp.opengl.GLProfile.getMaxFixedFunc(GLProfile.java:802)
at javax.media.j3d.JoglPipeline.initialize(JoglPipeline.java:132)
at javax.media.j3d.Pipeline.createPipeline(Pipeline.java:92)
at javax.media.j3d.MasterControl.loadLibraries(MasterControl.java:837)
at javax.media.j3d.VirtualUniverse.(VirtualUniverse.java:274)
at me.drton.jmavsim.Visualizer3D.(Visualizer3D.java:154)
at me.drton.jmavsim.Simulator.(Simulator.java:157)
at me.drton.jmavsim.Simulator.main(Simulator.java:678)
... 5 more
X11Util.Display: Shutdown (JVM shutdown: true, open (no close attempt): 1/1, reusable (open, marked uncloseable): 0, pending (open in creation order): 1)
X11Util: Open X11 Display Connections: 1
X11Util: Open[0]: NamedX11Display[:0, 0x7fae2400b210, refCount 1, unCloseable false]`

I don't know the cause, but have you set up the developer environment as covered in https://dev.px4.io/en/setup/dev_env_linux.html ?

@hamishwilee : Yes, I am pretty sure I followed those instructions to set up the development environment in linux. I may be wrong but I think it has something to do with display and I am not sure where to fix it

I just ran the instructions from scratch on a clean Ubuntu 16.04 (running in VirtualBox VM on windows) using ubuntu_sim_common_deps.sh (https://dev.px4.io/en/setup/dev_env_linux_ubuntu.html). All just worked.
I don't know why this would fail for you sorry!

i have the same problem, any solution

@malikaoudjif Again, id you run the script in ubuntu 16.04 "clean"? Perhaps post the whole build log to a gist and link here?

please read my comment: https://github.com/DrTon/jMAVSim/issues/42
I have solve it. Maybe file a PR for you.

@hamishwillee Hi, what's your mean of clean Ubuntu 16.04, I run it in VMwrae on windows. I open it, update and upgrade, the using ubuntu_sim_common_deps.sh, but there is the same error. Somebody said that it might be caused by the version of opengl, which should be 3.1 or higher, but it was 3.0 now? Thanks

@aogrcs I have no idea. BUt it looks like @Cody-Chen might: https://github.com/PX4/Firmware/issues/9283#issuecomment-383273485

Hi @hamishwillee Thanks
I thought the error might be caused by using make in the directory Firmware not the /src/Firmware.
I did make in the directory Firmware which I cloned, there was the error; but I used the shell and did make,  it worked.

@aogrcs Definitely not the location of firmware. I would have guessed something to do with opengl. Did you have to do anything other than standard build instructions and  make posix jmavsim to get this to work?

@hamishwillee I will test it for complete new image, If I got result, I would post it. Thanks

THanks. I tried this some time ago and it didn't work - would be great if this had somehow fixed itself.

Hi @hamishwillee I did the test. I used a clean Ubuntu 16.04 64, after installing it I did not use update or upgrade. Then I run ubuntu_sim_common_deps.sh, got the Firmware clone. In the directory, "make posix_sitl_default jmavsim" worked except to install pyyaml manually. I also got Firmware using git and it also worked, so the location of the Firmware did not make the problem. I think I made mistake before. Thanks

@aogrcs  when you clone FW and make posix for sitl jmavsim, it works but after you upgrade 16.04, for me it doesn't work again with the same error. I removed my graphics card from pciex slot and used onboard graphics adapter and it worked again. It has got something to do between a new package which is updated for the display and the graphics card adapter. It has got nothing to do with the PX4 firmware I think.

@metinburak Hi, could you give more information about your error?

I have the same issue on my thinkpad where I just installed Ubuntu 20.04
I can start the simulator by setting "MESA_LOADER_DRIVER_OVERRIDE=i965"
So my command line is:

MESA_LOADER_DRIVER_OVERRIDE=i965 ./Tools/jmavsim_run.sh -q -d /dev/ttyACM0 -b 921600 -r 250 -o

I found this fix here: https://www.mathworks.com/matlabcentral/answers/342906-could-not-initialize-shared-resources-for-x11graphicsdevice

Had the same issue on my Thinkpad, and the solution of @PimoGithub worked for me as well:
MESA_LOADER_DRIVER_OVERRIDE=i965 make px4_sitl jmavsim

Probably latest Linux distros switched the Intel driver architecture to Iris https://linuxreviews.org/Intel_Iris
And the old java graphics library jmavsim uses is not properly supported anymore. Just a guess.


Flutter 3.0 compile warning

../../../appdev/flutter/.pub-cache/hosted/pub.dartlang.org/flustars-2.0.1/lib/src/widget_util.dart:26:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.

'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('../../../appdev/flutter/packages/flutter/lib/src/widgets/binding.dart').
WidgetsBinding.instance?.addPostFrameCallback((Duration timeStamp) {
^
../../../appdev/flutter/.pub-cache/hosted/pub.dartlang.org/flustars-2.0.1/lib/src/widget_util.dart:44:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('../../../appdev/flutter/packages/flutter/lib/src/widgets/binding.dart').
WidgetsBinding.instance?.addPostFrameCallback((Duration timeStamp) {

@Sky24n +1

@Sky24n +1

flustars_flutter3: ^3.0.0

flustars_flutter3: ^3.0.0


update check_json_path

issue: https://github.com/appscode/searchlight/issues/166

Codecov Report

Merging #310 into master will decrease coverage by 0.4%.
The diff coverage is 30.95%.

@@            Coverage Diff             @@
##           master     #310      +/-   ##
==========================================
- Coverage   31.03%   30.62%   -0.41%
==========================================
  Files           8        9       +1
  Lines         435      542     +107
==========================================
+ Hits          135      166      +31
- Misses        287      353      +66
- Partials       13       23      +10

Impacted Files
Coverage Δ

plugins/check_json_path/lib.go
28.97% <30.95%> (ø)

Continue to review full report at Codecov.

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


Write cronjob or something to periodically check qfRound.endDate and make them inactive if time passed

@maryjaf
Now you can test it, if it passes more than 10 minutes from and active qfRound out job will deactivate that qfRound


x/tools/gopls: acquire on destroyed generation in UpgradeMod

Information about the case in which this happened (I'm not able to reproduce it).
To be fair, the module I was working from was in a very bad state (a lot of Saving 'go.mod': Getting code actions from ''Go Nightly'' (configure). pop-ups.)
The change I made to bring this about was change the go.mod from:
module mod5.com

go 1.14

require (
	github.com/cockroachdb/apd/v2 v2.0.1
)

replace (
	github.com/cockroachdb/apd/v2 v2.0.1 => /Users/rstambler/code/src/golang.org/x/tools
)

to
module mod5.com

go 1.14

require (
	github.com/cockroachdb/apd/v2 v2.0.1
)

mod5.zip
gopls.log

/cc @heschik
Not sure if there's anything that can be done at this point, but wanted to let you know that I saw this.


(selenium-gecko-driver) Migrate package to new repository

Description
This pull request adds and updates the selenium-gecko-package which is maintained by @hansnull.
The package has been made an embedded package which we prefer to use when possible, as well as certain metadata items is updated to the correct locations.
Maintainer was asked for permission to move this package to this repository.
Motivation and Context
The selenium gecko package is something we/I consider to be an important package for quite alot of people, and thus makes sense to be hosted in this repository and to be made an automatic package.
How Has this Been Tested?
As there is very minor changes to the installation, no testing have been done on this part.
The updating of the package have been tested locally.
Screenshot (if appropriate, usually isn't needed):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

Original Location

Original Repository
[ ] No PR to remove the package is opened, I am leaving this to the author to decide whether to remove just the package, or to remove the repository.
[ ] The migration guidelines have been followed (only partially)

fixes #1857

:white_check_mark: Package verification completed without issues. PR is now pending human review

@hansnull this is the PR I mentioned through email I would open to migrate the package.
I would appreciate it if you would have the time to look over the changes in the PR and give a thumbs up or down on whether you agree with the changes.
Do note that the description is automatically imported from the Readme, and the iconUrl and packageSourceUrl are also automatically updated (which is why I didn't update those).

:x: Package verification failed, please review the Appveyor Logs and the provided Artifacts before requesting a human reviewer to take a look.

:white_check_mark: Package verification completed without issues. PR is now pending human review

Modified maintainers to enable builds from this repository.


[Identity] Blockers for msal-node + cache adoption

Package Name: azure/identity
Package Version: 1.2 beta

This is a meta issue covering the currently known issues of @azure/msal-node. This is largely for tracking purposes.

[x] Bug: Services that use 'family of client id' results are currently unsupported. This impacts at least KeyVault and potentially others
[x] Bug: Filter of scopes is not working properly, causing tokens to fail to be retrieved from the cache
[x] Bug: msal-node does not publicly expose all the necessary types for calling into the API
[ ] Feature request: I've asked that the authority be part of the account information returned from a successful authentication. This would allow us to unify the structure under AuthenticationRecord

Closing this as the blockers are now fixed as of last week


Restore logic for --local-url-access=no accidentally deleted by #10158 (#13412)

This code was originally added in #12759 and seems to have been deleted accidentally in #10158 (probably a merge error).  This fixes test/module/webpage/local-urls-disabled which is currently failing across the board.

/me will take a look.

Still looking... (bear with me)

@zackw Hmm, care to rebase this on the latest master?

@ariya Sure thing!  I also folded in #12842 which just added more test cases.

LGTM
/cc @ariya

I will push the button at 2015-08-20 13:00:00 +0000 (i.e. tomorrow morning at nine AM US/Eastern) unless someone objects before then.

@zackw Go for it! Thanks.

Hello!
You have a new message, please read http://www.hilltopturfandlandscapes.com/prior.php?ldv
<EMAIL_ADDRESS>


[diskless] adding example and clarification

Hello BB'Team,
I add example and clarification which are reported by less experienced users.
Regards,
@hmeAtos

Good ideo @btravouillon
Done.

Hello
Is this PR now ok so I can review it ?

There are 2 pending items:

5120M is not a blocker to me, even if I still think 5G is more user-friendly.
I can't approve until the rendering of the list in the rst file is fixed.

I'm taking care of it.

16 commits: please squash before merge.


Add Whisper, Vicuna, and tinyllama tests

Tests "migraphx_models__whisper-tiny-encoder" and "migraphx_models__whisper-tiny-decoder" are uploaded and added to alt_e2eshark


fix the bugs due to refactoring code

Some functions which originally belonged to TFJobController are now changed to JobController  when last time refactoring the code #767 .
This is also the root cause for issue #774

This change is

/assign @gaocegege
Would you help me to have a look?
Thanks!

Coverage remained the same at 57.957% when pulling 78170263c31de3047a5114f7ac1b90d09bbcbf34 on ChanYiLin:master into 44c5382ffdb126848a8f11ef141a679001a53ef8 on kubeflow:master.

Coverage remained the same at 57.957% when pulling 78170263c31de3047a5114f7ac1b90d09bbcbf34 on ChanYiLin:master into 44c5382ffdb126848a8f11ef141a679001a53ef8 on kubeflow:master.

After taking a second look, TFJobController has embedded field jobcontroller.JobController as defined here, so i think it is ok now.
But i'm just wondering why not rename TFJobController to TFController as we have renamed the folder to tfcontroller, and move controller_pod/service/status.go files into jobcontroller folder.
FYI @johnugeorge @gaocegege

Oh, its my fault, I got it. lol
we can just close this PR, thanks

@ChanYiLin I didn't understand this PR. Did you find any issues?

@ScorpioCPH
Agree with you regarding the renaming. I will raise a PR for it
Wrt to moving controller_pod/service/status.go files into jobcontroller folder ,  I found that most of the code in status.go is specific to v1alpha2.TFJob and hence kept it in TFController folder.  Do you have other ideas?

@johnugeorge
I opened this issue because I was reading the source code and saw the issue #774 .
My original idea was that because of the refactoring code, some functions like GetPodsForJob() was moved to jobController and thus,
pods, err := tc.GetPodsForJob(tfjob) in tfcontroller.go L336 should be
tc.JobController .GetPodsForJob(tfjob)
but I was wrong at the end, since we've already embedded jobcontroller.JobController in TFJobController type struct, so this issue is not really a problem.
I suggest we can close this issue, and open another issue to discuss the naming problem
cc @ScorpioCPH

Closing PR as changes are not required
/close


SecondCloneSucceedsWithMissingTrees: Attempt 2

The previous approach to this test relied on deleting packfiles from the shared object cache. That failed on Windows because the .idx files have restrictive permissions that cause the delete to fail.
Instead, use the loose object downloads to hydrate the commit and root tree for the WellKnownBranch and then do a clone pointing at that branch. This should trigger the failure case.
Resolves #330

I can only run the functional tests through PR builds, so I'm adding a commit that takes the fix out to verify the test fails.

Ok. I finally got a failed test for the right reason:
Cannot clone @ /GVFS.FT/test/a30714a88c364624a9ad
Error: Could not complete checkout of branch: FunctionalTests/20170602, fatal: unable to read tree 47334ac02e57e3ae53cf4f272a8764fcaa98c57b

Trying again with the fix to ensure it passes.


Out-of-date RAM power consumption assumption

CodeCarbon version: 2.8.0
Python version: 3.12.7
Operating System: Linux-6.12.1-arch1-1-x86 64-with-glibc2.40

Description
In the documentation, under "RAM" in the "Power Usage" section, CodeCarbon states that it uses 3 W per 8 GB based on this source: https://www.crucial.com/support/articles-faq-memory/how-much-power-does-memory-use. However, the source recommends using 5 W per module.
What I Did
I checked the page on the Wayback Machine, and if you go back to April 15, 2024, it shows that it recommends 3 W per 8 GB of DDR3 or DDR4 memory. The next entry on July 25, 2024 updated it, indicating they changed their recommendations anywhere between the aforementioned dates.

Thanks, we will have a look to this in #717 . It means we have to find a way to count the number of module.
I will close this issue. Please comment in #717 if you want to add something else.


500: Server error  SqliteError: ROLLBACK - cannot rollback - no transaction is active

hi. my disk was full where i store mediatracker files. i didnt know and pulled the latest update through docker compose. and now it give this error when i try to access it.

500: Server error
SqliteError: ROLLBACK - cannot rollback - no transaction is active

the logs shows these:
`$ docker logs mediatracker
PUID: 1000
PGID: 1000
info:  Creating config directory at /home/abc/.mediatracker
Can't take lock to run migrations: update knex_migrations_lock set is_locked = 1 where is_locked = 0 - database or disk is full
If you are sure migrations are not running you can release the lock manually by running 'knex migrate:unlock'
SqliteError: ROLLBACK - cannot rollback - no transaction is active
at Client_BetterSQLite3._query (/app/node_modules/knex/lib/dialects/better-sqlite3/index.js:39:38)
at executeQuery (/app/node_modules/knex/lib/execution/internal/query-executioner.js:37:17)
at Client_BetterSQLite3.query (/app/node_modules/knex/lib/client.js:146:12)
at /app/node_modules/knex/lib/execution/transaction.js:363:24
at new Promise ()
at Client_BetterSQLite3.trxClient.query (/app/node_modules/knex/lib/execution/transaction.js:358:12)
at Transaction_Sqlite.query (/app/node_modules/knex/lib/execution/transaction.js:159:8)
at Transaction_Sqlite.rollback (/app/node_modules/knex/lib/execution/transaction.js:135:25)
at Function.transactor.rollback (/app/node_modules/knex/lib/execution/transaction.js:315:42)
at /app/node_modules/knex/lib/execution/transaction.js:231:35
starting server at http://bc395c4de930:7481
`
i made free space in disk now & restarted the container, even force recreated but getting same error.
before clearing space the container health was "starting"
now it says its healthy but gives the same error.
please guide me how to fix these issue?
thank you

i restarted the system and run docker again and its working now.