text:
context question index bug fix

The index that corresponds to the question options was not incremented. This fixes it.

Looks good :)

authors: MattesMrzik salimbouch

repo: devonfw/IDEasy


text:
🛑 MTGChronicle is down

In ef5e72b, MTGChronicle (https://mtgchronicle.sean.hackclub.app/up) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MTGChronicle is back up in b35388b after 1 hour, 2 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
【提示优化】nasConfig没有配置时候，执行s nas执行，给出友好提示

现在的提示代码异常，比较费解

修复

authors: heimanba wss-git

repo: devsapp/fc


text:
⚠ Mobitopup has degraded performance

In 4c50265, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4314 ms

Resolved: Mobitopup performance has improved in 65d82ed.


text:
Consider allowing to configure class name prefixes for better usage alongside mapping frameworks

Our project is currently hindered using this plugin due to the following issue: backend model classes share identical names, leading to naming conflicts and the need to rely on package names for differentiation of the Classes.
To circumvent this issue, we've adopted a strategy of prefixing all model classes with "View". Since this seems currently not possible, I propose the addition of a feature that allows adding prefixes to the classes, such as "View", during the code generation phase.
I appreciate your consideration of this feature request and am hopeful for its inclusion in a future update of the graphqlcodegen plugin.

Hi @appreciated - This project is a thin wrapper over the core Netflix DGS codegen library.
Netflix uses Gradle thus no support for the maven community, and we built this maven port.
There are already open feature requests in the DGS framework repo. https://github.com/Netflix/dgs-codegen/issues/323
Can you engage with these to get it back on their radar. This is where the change/fix will need to be made.

authors: appreciated deweyjose

repo: deweyjose/graphqlcodegen


text:
Cannot read property subscribe of undefined

A customer has encountered a problem on dexie-cloud-addon. An exception is thrown: Uncaught TypeError: Cannor read property 'subscribe' of undefined.
at dbOnClosed (dexie-cloud-addon.js:2884)
at dexieCloud (dexie-cloud-addon.js:5844)
...

And the code on dexie-cloud-addon.js:2882 is as below.

the db.on.close is undefined.

Reason must be that the newest version of dexie isnt installed. Must install dexie@next to work with dexie-cloud-addon.

Yes, it works now. Thanks!

license_source: bigquery


text:
How to test headless with react/redux?

I'm writing a react app but I can't seem to set it up correctly, I've tried fake-indexeddb with jest/jsdom but some parts work and some don't.

Interesting. Saw you found your way of using fake-indexedDB with Dexie for unit testing in node in your last comment of issue #495. May be useful for other users too.
As for samples using Dexie with react, have a look at two react samples referred to from the Dexie samples page

If you use jest, simply mock the module:
jest.mock('dexie', () => {
    return class Dexie {
        open = () => Promise.resolve();
        version() {
            return {
                stores: jest.fn()
            };
        }
    };
});

This gives you control over anything you're testing.

authors: brielov dfahlander rolandjitsu


text:
Updating packages

Updating renv version with renv::upgrade()
Updating all other packages using renv::update()
Running automated tests locally (all passed), and updating the json files for shinytest

Currently failing in the deployment pipeline, leaving as draft until issue is resolved

source: gharchive/pull-request


text:
chore(package): update semantic-release to version 15.0.2

Closes #635

:tada: This PR is included in version 4.2.2 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

license: mit


text:
Conversion of 11g-ocm-use-sql-access-advisor.html Failed

The following command:
convert_web_page.py -rgvl /tmp/a.log /home/douglas/git-repositories/dfhawthorne.github.io/docs/home/11g-ocm/11g-ocm-performance-management/11g-ocm-use-sql-access-advisor.html

With:
Traceback (most recent call last):
  File "/home/douglas/bin/convert_web_page.py", line 784, in <module>
    uploaded_file_name = tag.a.string.strip()
AttributeError: 'NoneType' object has no attribute 'string'

Updated conversion script, scripts/convert_web_page.py, to get alternative source of uploaded file name if <A> tag is missing.
Also, the conversion script now only wraps text if the file name is the whole text for the tag.
Conversion is aborted if no wrapping is done


text:
Gold Image Configuration Files Being Created Unnecessarily

The output from orchestration/build_goldengate.yml shows:
TASK [Create Gold Image Configuration Files] **********************************************************************************************************************
changed: [victoria_root] => (item={'src_dir': 'Oracle Enterprise Linux/Oracle Enterprise Linux 6.5', 'dvd': 'V41362-01.iso', 'mp': 'OL6.5', 'vm_name': 'gold_ol6_5'})
changed: [victoria_root] => (item={'src_dir': 'Oracle Enterprise Linux/Oracle Enterprise Linux 7.7', 'dvd': 'V983339-01.iso', 'mp': 'OL7.7', 'vm_name': 'gold_ol7_7'})
changed: [victoria_root] => (item={'src_dir': 'Oracle Enterprise Linux/Oracle Enterprise Linux 8.1', 'dvd': 'V984216-01.iso', 'mp': 'OL8.1', 'vm_name': 'gold_ol8_1'})
changed: [victoria_root] => (item={'src_dir': 'Oracle Enterprise Linux/Oracle Enterprise Linux 9.1', 'dvd': 'OracleLinux-R9-U1-x86_64-dvd.iso', 'mp': 'OL9.1', 'vm_name': 'gold_ol9_1'})
changed: [victoria_root] => (item={'src_dir': 'Ubuntu', 'dvd': 'ubuntu-20.04.2-live-server-amd64.iso', 'mp': 'Ubuntu20.04', 'vm_name': 'gold_ub20_04'})
changed: [victoria_root] => (item={'src_dir': 'Ubuntu', 'dvd': 'ubuntu-22.04.2-live-server-amd64.iso', 'mp': 'Ubuntu22.04', 'vm_name': 'gold_ub22_04'})

even though the configuration files have not been changed.

The playbook is working as expected. The header changed because I was running the playbook from a new host, auburn:
# From:    /home/douglas/git-repositories/xen_server_farm/templates/gold_image_hvm.cfg.j2
# By:      douglas
# On:      auburn


text:
Trie.mo contains debugPrint expressions

These almost certainly shouldn't appear in production code. @matthewhammer, can you take a look?

👍

👍

These are commented out now.

authors: crusso matthewhammer

repo: dfinity/motoko-base


text:
Final submission ijcai 23 dfki bremen ai olympics competition

Pull request for the contribution "Athletic Intelligence Olympics challenge with Model-Based Reinforcement Learning".
Authors: Alberto Dalla Libera, Niccolo’ Turcato, Giulio Giacomuzzo, Ruggero Carli and Diego Romeres.

Hello @turcato-niccolo ,
Thank you very much for your pull request! Your code is clean and you provided all relevant files for you controller.
Regarding the pull request, I have the following remarks and questions:

.gitignore
You deleted the paths

leaderboard/simulation/acrobot/data/*
leaderboard/robustness/acrobot/data/*

Please leave them in there (Actually the paths for pendubot are missing). The leaderboard results will be computed with a dedicated workflow and stored in a separate repository dedicated to the leaderboard.

Dockerfile
You added the lines

RUN pip3 install numpy dill
RUN python3 -m pip install drake

please put the python dependencies in (src/python/setup.py)[https://github.com/dfki-ric-underactuated-lab/double_pendulum/blob/main/src/python/setup.py]. Did you have problems with numpy or drake? Both are already listed in the setup.py file.

leaderboard data
The leaderboard data does not need to be commited. The leaderboard results will be computed with a dedicated workflow and stored in a separate repository dedicated to the leaderboard. Please remove the result files

leaderboard/robustness/acrobot/data/*
leaderboard/simulation/acrobot/data/*
leaderboard/robustness/pendubot/data/*
leaderboard/simulation/pendubot/data/*

from the pull request. I am sorry, that was probably not so clear in the competition/repository rules.

Policy files
Consider storing your trained policies, i.e.

leaderboard/robustness/acrobot/policy_mcpilco_nostab.np
leaderboard/robustness/pendubot/policy_mcpilco_full.np
leaderboard/simulation/acrobot/policy_mcpilco_nostab.np
leaderboard/simulation/pendubot/policy_mcpilco_full.np

in the main data folder. I would suggest the structure
data/policies/<design_X.X>/<model_X.X>/<robot>/MC-PILCO/<your_policy>

similar to the stored trajectories in the same data folder. For the naming of design and model see here. <robot> would be either 'acrobot' or 'pendubot'. If you have multiple policies for the same design, model, robot and method you can create subfolders on the last level.

src/cpp/makefile
Did you have problems with the include paths?  The path

-I/usr/local/include

should stay there. If you want to add another path, e.g. -I/usr/local/include/eigen3 you can add that after the other include paths. Let me know if that causes a problem for you.

src/cpp/model/src/.idea
I am not sure what this folder is needed for. Can you explain the use of this folder? If not needed please delete from the pull request.

Would you be willing to also commit the scripts which you used for training the MC-PILCO policies? Would be nice to have them available for everybody.

Thanks again for the great submission!

Dear @fwiebe,
Thank you so much for the review!
I have addressed your requests:
-I added the leaderboard data paths to gitignore file.
-I moved the needed Python dependencies to setup.py.
-I removed the benchmark data.
-As you suggested, I moved MC-PILCO's policy files to the main data folder with the structure:
 data/policies/<design_X.X>/<model_X.X>/<robot>/MC-PILCO/<policy>
-I fixed the includes in the cpp makefile, it compiles in the docker.
-Removed .idea folder. Sorry about that. My editor inserted it and I didn't notice it.
-At the moment it is quite unpractical for us to integrate the training code into this repository. Moreover, MC-PILCO's code is mostly composed of custom libraries, which are still in development.
However, while fixing the code following your directives, I noticed a major bug in the calculate_leaderboard_score.py scripts (leaderboard folders).
The perf. score's weights in the script are not the same as indicated in: https://ijcai-23.dfki-bremen.de/competitions/ai_olympics/
I didn't notice this before, since I have always used the create_leaderboad.py script.
I suspect that the mismatch stated in the initial software review was due to this bug. I fixed it in this last commit.
I tested by adding:
  COPY . ./double_pendulum/
instead of
  RUN git clone https://github.com/dfki-ric-underactuated-lab/double_pendulum.git
in Dockerfile, to test the local branch.
Controllers work as expected and now calculate_leaderboard_score.py computes the correct scores, which are the ones we stated in the report.

Thank you @turcato-niccolo ,
the PR looks good and I will merge it now. And thanks for pointing out and fixing the wrong weights in the calculate_leaderboard_score.py scripts. The final ranking will be calculated with the correct weights :)

Dear @fwiebe,
Thank you so much for the review!
I have addressed your requests: -I added the leaderboard data paths to gitignore file. -I moved the needed Python dependencies to setup.py. -I removed the benchmark data. -As you suggested, I moved MC-PILCO's policy files to the main data folder with the structure:  data/policies/<design_X.X>/<model_X.X>/<robot>/MC-PILCO/<policy> -I fixed the includes in the cpp makefile, it compiles in the docker. -Removed .idea folder. Sorry about that. My editor inserted it and I didn't notice it. -At the moment it is quite unpractical for us to integrate the training code into this repository. Moreover, MC-PILCO's code is mostly composed of custom libraries, which are still in development.
However, while fixing the code following your directives, I noticed a major bug in the calculate_leaderboard_score.py scripts (leaderboard folders). The perf. score's weights in the script are not the same as indicated in: https://ijcai-23.dfki-bremen.de/competitions/ai_olympics/ I didn't notice this before, since I have always used the create_leaderboad.py script. I suspect that the mismatch stated in the initial software review was due to this bug. I fixed it in this last commit.
I tested by adding:  COPY . ./double_pendulum/ instead of  RUN git clone https://github.com/dfki-ric-underactuated-lab/double_pendulum.git in the Dockerfile, to test the local branch. I then restored the Dockerfile before committing changes. Controllers work as expected and now calculate_leaderboard_score.py computes the correct scores, which are the ones we stated in the report.

I forgot to mention that the code for the base version of MC-PILCO is publicly available at:
https://www.merl.com/research/license/MC-PILCO

authors: fwiebe turcato-niccolo


text:
Automatic download command is broken

https://dgraph.io/docs/deploy/download/#automatic-download
The command given here (curl https://get.dgraph.io -sSf | bash) gave an error. I think we can remove this section as the "Manual Download" is not that complicated.

Update. I think the issue is with binary asset.
I think we should filter out Beta, RC and etc from the Get Dgraph install line. It doesn't look a safe thing let users install it right away. We should Put as explicitly requested only.

Okay, this is temporarily fixed directly on the server. The fix needs review. See https://github.com/dgraph-io/Install-Dgraph/pull/28

We're dropping this (automatic download) in v22.0.0, right?

No, this one will be skipped cuz it is a RC. Not a official release. When it comes it will be picked by the script.

Hi @MichelDiz , the other day @matthewmcneely @meghalims and I, we were highly considering dropping this automatic download feature, since the manual download is not that complicated to do. Do you think we should keep this?

Yes, we should keep. Cuz it is better for manual testing, some users and customers uses it. It is not an expensive process to maintain. I see no strong reason to remove it.
A difficulty, I think, for example, having any instance (e.g. EC2) from scratch. Just to test Dgraph. I would have to install Docker, download the image. But if I don't want to use docker I would have to extract the binary from inside the container to the host OS. This add more complexity. Rather than simply running a script. See?
OR, I have to download the binary from Github. Which is exactly the same as this script right? but automated.
In the end, I just wanted to do a quick test. Where I can change parameters and have a more direct control of the execution. Instead of editing a Docker or Docker compose command.
I do this a lot, I don't use Docker all the time. Only when it's necessary. If I need to do something at lightning speed, I use this script. And many others use it too.

@MichelDiz Are you saying you use the auto download for Linux on amd64? Because we don't build for any other platforms, right?

Yes, I use Linux in virtual machine on my NAS, I use WSL and stuff. For me it is more comfortable to have this script. And if we get support for other operating systems again. That script would be useful.

We can decrease the frequency that this functionality appears in docs or on the main company website. But this kind of script is almost cultural among tech startups. And it's not expensive to maintain.

I see, I guess we thought a wget/curl and an unzip was easier to document than maintaining that script. @meghalims your call to make?

authors: MichelDiz kevinmingtarja matthewmcneely

repo: dgraph-io/Install-Dgraph


text:
Can't verify my jwt with public.key

Hi I tried to verify if some jwt coming from outside is valid:
func verifyBackendJWT(token string, keyData []byte) (bool, error) {
	key, _ := jwt.ParseRSAPublicKeyFromPEM(keyData)
	fmt.Println("verify", key)

	parts := strings.Split(token, ".")

	method := jwt.GetSigningMethod(jwt.SigningMethodRS256.Alg())
	err := method.Verify(strings.Join(parts[0:2], "."), parts[2], key)
	log.Println(err)
	if err != nil {
		return false, err
	}
	return true, nil
}

jwt.ParseRSAPublicKeyFromPEM returns without error so my public.key is valid.
method.verify always returns crypto/rsa: verification error
I'm sure that jwt are valid too beacuse they are used by a wide of microservices which verifies those token with the same public.key
Could you help me in someway?

@marcio199226 Hi.
Use to:
const (pubKeyPath = "./keys/public.key")

pubKey, err := ioutil.ReadFile(pubKeyPath)
token, err := jwt.Parse(parts[1], func(token *jwt.Token) (interface{}, error) {
    key, err := jwt.ParseRSAPublicKeyFromPEM(pubKey)
    if err != nil {
	return nil, err
    }

    if _, ok := token.Method.(*jwt.SigningMethodRSA); !ok {
        return nil, err
    }

    return key, nil
})

Where public.key:
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

repo: dgrijalva/jwt-go


text:
Main

Issue number #302
This pull request implements a comprehensive notification system for our platform. Key features include real-time notifications for users regarding updates such as new stations, changes in operating hours, and upcoming events. The system also allows users to manage their notification preferences through a user-friendly interface.
Key Features:
Real-Time Notifications: Users will receive updates instantly via Socket.io.
User Preferences: Users can customize the types and frequency of notifications they wish to receive.
Notification Center: A dedicated dashboard section where users can view past notifications.
Push Notifications: Mobile users can receive notifications even when the app is not open.
Email Notifications: Users can opt to receive important updates via email.
Instructions for Running the Application:

Backend Setup:
cd backend
npm install
Create a .env file based on the provided template and fill in your details.
Start the backend server:
npm run dev

Frontend Setup:
cd ../frontend
npm install
Start the frontend application:
npm start

Access the Application:
Open your web browser and navigate to http://localhost:3000 to view the frontend.

Note on the .env File:
In the structure of .env file(which is basically a sample .env file which is created in the backend directory). Please keep these points in mind-
-Replace , , and  with your actual MongoDB credentials.
-Fill in EMAIL_USER and EMAIL_PASS with your email account details.
-Make sure to keep your .env file out of version control
I know you’re familiar with these instructions, but I wanted to provide them to ensure a smooth setup and running of the application. If you encounter any issues or have questions, please don’t hesitate to reach out!
Thankyou!
Note- Request for Level 3 Designation for Notification System Implementation.
As I worked on this feature, I realized that it required substantial effort and dedication, involving:
-In-depth Research: I invested significant time understanding real-time notifications, user preferences, and integration with various services like MongoDB, Socket.io, and Nodemailer.
-Complex Development: The implementation encompassed multiple components, including the backend setup, database configurations, and a comprehensive frontend interface to ensure a seamless user experience.
Given the complexity and the substantial effort it took to deliver a robust notification system, I’d like to kindly ask for a reconsideration of my task level to level 3. This adjustment would better reflect the dedication and hard work I put into this feature, and I believe it aligns more closely with the level of effort involved.
I appreciate your understanding and support and look forward to your feedback.
Thankyou!
Type of Pull Request

[ ] Bug Fix
[X ] New Feature
[ ] Performance Improvement
[ ] Documentation Update
[ ] Code Refactoring
[ ] Security Enhancement
[ ] Other (Specify): _______________

Checklist for Contributor

[ X] I have reviewed my code before submission.
[ X] I have read and followed the project's Contribution Guidelines.
[ X] I have tested the code thoroughly.
[X ] I have attached related issue numbers, screenshots, or videos (if applicable).
[X ] I have added comments to my code where necessary for clarity.
[X ] I have checked the existing code base and my changes do not introduce any breaking changes.
[X ] My PR addresses only one issue; I have created separate PRs for other issues.
[X ] I have ensured that the PR does not include unrelated files.
[ X] I am mindful of the project's coding standards and best practices.

thanks for contributing @snehas-05

repo: dhairyagothi/StationGuide


text:
login and security

hi there
we use qemu-kvm, and happy with docker-machine with qemu in my notebook
we want to make kvm in our server, any idea to use this driver? we cant find how to login or use security to create a vm outside machine remotely

This driver isn't currently set up to support remote operations.  See #11
For now, you'll have to install machine and the driver on the server, and ssh to it to run the operations.

authors: dhiltgen fthamura

repo: dhiltgen/docker-machine-kvm


text:
a

![logos_stt-nf_single](https://cloud.githubusercontent.com/assets/13671268/23329120/a4239d30-fb63-11e6-8044-29e57e2ca743.jpg)

repo: dhimasanb/mahasiswa


text:
Dhis2 7092 UI improvements

Closes DHIS2-11674
(link)
Closes DHIS2-11678
(link)
Closes DHIS2-11680
(link)
Closes DHIS2-11681
(link)
Closes DHIS2-11682
(link)

Looks good just needs to be linted before merge


text:
feat: add support for Chrome Beta

I know there should be a better way to do this?

Thanks!


text:
u and v may be NaN from the beginning

At first, thanks for the great implementation.
I found that this initialization is somewhat critical:
https://github.com/dhruvramani/Transformers-RL/blob/fc3d8af2f9b2ffc055855c755a1c892e4ae359d2/layers.py#L256
It may occur that self.u and self.v will be initialized containing nan. Eventually, this leads to everything becoming nan.

Thanks for the PR!

authors: VanillaWhey dhruvramani

repo: dhruvramani/Transformers-RL


text:
Add option to email summary stats when finished

This resolves #10.

Coverage increased (+2.6%) to 38.55% when pulling 6908af50506055f4ada0462e665ae5de2ba45203 on improvement/add_option_to_email_summary_stats into 15095fc03413302583e5584bb0bdbb228f48a5fb on develop.

repo: dhs-ncats/cyhy-mailer


text:
Cannot install rshell

It appears setup.py is attempting to import rshell during installation, which fails (at least in my conda environment on ubuntu 22.04) presumably due to rshell being treated as an installed module name and not a relative path.
(esp32) coder ➜ ~/dev $ python --version
Python 3.12.7
(esp32) coder ➜ ~/dev $ uname -a
Linux f274a92d9fb5 6.8.0-48-generic #48~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct  7 11:24:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
(esp32) coder ➜ ~/dev $ pip install rshell
Collecting rshell
  Using cached rshell-0.0.34.tar.gz (48 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-xdjoq0y6/rshell_668fb8047ccf456cb27890b00925f999/setup.py", line 9, in <module>
          from rshell.version import __version__
      ModuleNotFoundError: No module named 'rshell'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

I can successfully install rshell=0.0.1, and then try to install a newer rshell. The error changes to indicate rshell was found, but rshell.version was not, verifying that setup.py is treating rshell as an installed module and not a relative path.

I fixed this in 0.0.35 so that setup.py now uses a different method to determine the version.

authors: cwharris dhylands

repo: dhylands/rshell


text:
fix(tabs): keypress events not working

Description
Added keypress functionality (Tab, <-, ->, Home, and End) to tabs component, now it is working the same as in https://vue.dialpad.design/?path=/story/components-tabs--default
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[x] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

@juliodialpad,
Much improved, and mostly behaves as expected. Two quick reactions:

keydown is more commonly used rather than keyup. For example: https://codepen.io/francisrupert/pen/poaQRpp
Hitting spacebar on focused tab works as expectedl, however hitting enter fails. It briefly shows, then closes.

@juliodialpad,
Much improved, and mostly behaves as expected. Two quick reactions:

keydown is more commonly used rather than keyup. For example: https://codepen.io/francisrupert/pen/poaQRpp
Hitting spacebar on focused tab works as expectedl, however hitting enter fails. It briefly shows, then closes.

Updated, nice catch, thanks!

authors: francisrupert juliodialpad

repo: dialpad/dialtone


text:
如果服务器宕机了，会对客户端有影响吗？

如果服务器宕机了，会对客户端有影响吗？
比如：1.造成客户端OOM
2.耗光TCP链接，造成业务服务不可用？

服务器宕机，会将上报通道切换到下一台备用通道里，不会造成客户端OOM。TCP链接，最多建立2个，不会耗光。

authors: MoneyHacker jialinsun

repo: dianping/cat


text:
feat(ci): push to docker hub

You will need to add the following environment variables in order for this to work:

DOCKERHUB_USERNAME: Your Docker Hub username
DOCKERHUB_TOKEN: Your token for pushing to Docker Hub

Closes #606.

You will also have to update trunk/.github/workflows/docker.yml

Done 👍 https://github.com/diced/zipline/pull/613/commits/fedd157785eaf24e061244965f366a197183fc3e

repo: diced/zipline


text:
path格式问题

如果一个path中带有查询参数，应该怎么定义呢？比如：/xxx/<id>/xxx?a=<a>&b=<b>，但是这样编译报错

定义 /xxx//xxx
不要在path里定义?的部分，这部分会自动解析的
然后可以在bundle里取出 id、a、b 三个参数

repo: didi/DRouter


text:
6月9号下午18点下载了master分支，打开Android代码后，编译报错

FAILURE: Build failed with an exception.

Where:
Initialization script '/private/var/folders/t3/b8smz48x00s_9dlcccbpv4qc0000gn/T/ijmapper.gradle'

What went wrong:
Could not compile initialization script '/private/var/folders/t3/b8smz48x00s_9dlcccbpv4qc0000gn/T/ijmapper.gradle'.

startup failed:
General error during conversion: Unsupported class file major version 61

java.lang.IllegalArgumentException: Unsupported class file major version 61
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:189)
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:170)
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:156)
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:277)
at org.codehaus.groovy.ast.decompiled.AsmDecompiler.parseClass(AsmDecompiler.java:81)
at org.codehaus.groovy.control.ClassNodeResolver.findDecompiled(ClassNodeResolver.java:251)
at org.codehaus.groovy.control.ClassNodeResolver.tryAsLoaderClassOrScript(ClassNodeResolver.java:189)
at org.codehaus.groovy.control.ClassNodeResolver.findClassNode(ClassNodeResolver.java:169)
at org.codehaus.groovy.control.ClassNodeResolver.resolveName(ClassNodeResolver.java:125)
at org.codehaus.groovy.ast.decompiled.AsmReferenceResolver.resolveClassNullable(AsmReferenceResolver.java:57)
at org.codehaus.groovy.ast.decompiled.AsmReferenceResolver.resolveClass(AsmReferenceResolver.java:44)
at org.codehaus.groovy.ast.decompiled.AsmReferenceResolver.resolveNonArrayType(AsmReferenceResolver.java:79)
at org.codehaus.groovy.ast.decompiled.AsmReferenceResolver.resolveType(AsmReferenceResolver.java:70)
at org.codehaus.groovy.ast.decompiled.MemberSignatureParser.createMethodNode(MemberSignatureParser.java:57)
at org.codehaus.groovy.ast.decompiled.DecompiledClassNode.lambda$createMethodNode$1(DecompiledClassNode.java:230)
at org.codehaus.groovy.ast.decompiled.DecompiledClassNode.createMethodNode(DecompiledClassNode.java:236)
at org.codehaus.groovy.ast.decompiled.DecompiledClassNode.lazyInitMembers(DecompiledClassNode.java:203)
at org.codehaus.groovy.ast.decompiled.DecompiledClassNode.getDeclaredMethods(DecompiledClassNode.java:122)
at org.codehaus.groovy.ast.ClassNode.tryFindPossibleMethod(ClassNode.java:1283)
at org.codehaus.groovy.control.StaticImportVisitor.transformMethodCallExpression(StaticImportVisitor.java:251)
at org.codehaus.groovy.control.StaticImportVisitor.transform(StaticImportVisitor.java:133)
at org.codehaus.groovy.ast.ClassCodeExpressionTransformer.visitExpressionStatement(ClassCodeExpressionTransformer.java:108)
at org.codehaus.groovy.ast.stmt.ExpressionStatement.visit(ExpressionStatement.java:40)
at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitClassCodeContainer(ClassCodeVisitorSupport.java:138)
at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitConstructorOrMethod(ClassCodeVisitorSupport.java:111)
at org.codehaus.groovy.ast.ClassCodeExpressionTransformer.visitConstructorOrMethod(ClassCodeExpressionTransformer.java:66)
at org.codehaus.groovy.control.StaticImportVisitor.visitConstructorOrMethod(StaticImportVisitor.java:108)
at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitConstructor(ClassCodeVisitorSupport.java:101)
at org.codehaus.groovy.ast.ClassNode.visitContents(ClassNode.java:1089)
at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitClass(ClassCodeVisitorSupport.java:52)
at org.codehaus.groovy.control.CompilationUnit.lambda$addPhaseOperations$3(CompilationUnit.java:209)
at org.codehaus.groovy.control.CompilationUnit$IPrimaryClassNodeOperation.doPhaseOperation(CompilationUnit.java:942)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:671)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:635)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:389)
at groovy.lang.GroovyClassLoader.lambda$parseClass$3(GroovyClassLoader.java:332)
at org.codehaus.groovy.runtime.memoize.StampedCommonCache.compute(StampedCommonCache.java:163)
at org.codehaus.groovy.runtime.memoize.StampedCommonCache.getAndPut(StampedCommonCache.java:154)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:330)
at org.gradle.groovy.scripts.internal.DefaultScriptCompilationHandler.compileScript(DefaultScriptCompilationHandler.java:139)
at org.gradle.groovy.scripts.internal.DefaultScriptCompilationHandler.compileToDir(DefaultScriptCompilationHandler.java:95)
at org.gradle.groovy.scripts.internal.BuildOperationBackedScriptCompilationHandler$2.run(BuildOperationBackedScriptCompilationHandler.java:54)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
at org.gradle.groovy.scripts.internal.BuildOperationBackedScriptCompilationHandler.compileToDir(BuildOperationBackedScriptCompilationHandler.java:51)
at org.gradle.groovy.scripts.internal.FileCacheBackedScriptClassCompiler$CompileToCrossBuildCacheAction.execute(FileCacheBackedScriptClassCompiler.java:190)
at org.gradle.groovy.scripts.internal.FileCacheBackedScriptClassCompiler$CompileToCrossBuildCacheAction.execute(FileCacheBackedScriptClassCompiler.java:170)
at org.gradle.groovy.scripts.internal.FileCacheBackedScriptClassCompiler$ProgressReportingInitializer.execute(FileCacheBackedScriptClassCompiler.java:211)
at org.gradle.groovy.scripts.internal.FileCacheBackedScriptClassCompiler$ProgressReportingInitializer.execute(FileCacheBackedScriptClassCompiler.java:194)
at org.gradle.cache.internal.DefaultPersistentDirectoryCache$Initializer.initialize(DefaultPersistentDirectoryCache.java:100)
at org.gradle.cache.internal.FixedSharedModeCrossProcessCacheAccess$1.run(FixedSharedModeCrossProcessCacheAccess.java:86)
at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.doWriteAction(DefaultFileLockManager.java:216)
at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.writeFile(DefaultFileLockManager.java:206)
at org.gradle.cache.internal.FixedSharedModeCrossProcessCacheAccess.open(FixedSharedModeCrossProcessCacheAccess.java:83)
at org.gradle.cache.internal.DefaultCacheAccess.open(DefaultCacheAccess.java:139)
at org.gradle.cache.internal.DefaultPersistentDirectoryStore.open(DefaultPersistentDirectoryStore.java:89)
at org.gradle.cache.internal.DefaultPersistentDirectoryStore.open(DefaultPersistentDirectoryStore.java:43)
at org.gradle.cache.internal.DefaultCacheFactory.doOpen(DefaultCacheFactory.java:103)
at org.gradle.cache.internal.DefaultCacheFactory.open(DefaultCacheFactory.java:68)
at org.gradle.cache.internal.DefaultCacheRepository$PersistentCacheBuilder.open(DefaultCacheRepository.java:126)
at org.gradle.groovy.scripts.internal.FileCacheBackedScriptClassCompiler.compile(FileCacheBackedScriptClassCompiler.java:116)
at org.gradle.groovy.scripts.internal.CrossBuildInMemoryCachingScriptClassCache.getOrCompile(CrossBuildInMemoryCachingScriptClassCache.java:50)
at org.gradle.groovy.scripts.internal.BuildScopeInMemoryCachingScriptClassCompiler.compile(BuildScopeInMemoryCachingScriptClassCompiler.java:50)
at org.gradle.groovy.scripts.DefaultScriptCompilerFactory$ScriptCompilerImpl.compile(DefaultScriptCompilerFactory.java:49)
at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:125)
at org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
at org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62)
at org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:43)
at org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62)
at org.gradle.configuration.DefaultInitScriptProcessor.process(DefaultInitScriptProcessor.java:50)
at org.gradle.initialization.InitScriptHandler$1.run(InitScriptHandler.java:56)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
at org.gradle.initialization.InitScriptHandler.executeScripts(InitScriptHandler.java:51)
at org.gradle.initialization.DefaultSettingsPreparer.prepareSettings(DefaultSettingsPreparer.java:33)
at org.gradle.initialization.BuildOperationFiringSettingsPreparer$LoadBuild.doLoadBuild(BuildOperationFiringSettingsPreparer.java:62)
at org.gradle.initialization.BuildOperationFiringSettingsPreparer$LoadBuild.run(BuildOperationFiringSettingsPreparer.java:57)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
at org.gradle.initialization.BuildOperationFiringSettingsPreparer.prepareSettings(BuildOperationFiringSettingsPreparer.java:45)
at org.gradle.initialization.DefaultGradleLauncher.prepareSettings(DefaultGradleLauncher.java:219)
at org.gradle.initialization.DefaultGradleLauncher.doClassicBuildStages(DefaultGradleLauncher.java:160)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:149)
at org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:125)
at org.gradle.internal.invocation.GradleBuildController$1.create(GradleBuildController.java:71)
at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:213)
at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:67)
at org.gradle.internal.invocation.GradleBuildController.run(GradleBuildController.java:56)
at org.gradle.tooling.internal.provider.runner.AbstractClientProvidedBuildActionRunner.runClientAction(AbstractClientProvidedBuildActionRunner.java:53)
at org.gradle.tooling.internal.provider.runner.ClientProvidedPhasedActionRunner.run(ClientProvidedPhasedActionRunner.java:47)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.launcher.exec.BuildOutcomeReportingBuildActionRunner.run(BuildOutcomeReportingBuildActionRunner.java:66)
at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)
at org.gradle.tooling.internal.provider.FileSystemWatchingBuildActionRunner.run(FileSystemWatchingBuildActionRunner.java:90)
at org.gradle.launcher.exec.BuildCompletionNotifyingBuildActionRunner.run(BuildCompletionNotifyingBuildActionRunner.java:41)
at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:49)
at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:44)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:44)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.lambda$execute$0(InProcessBuildActionExecuter.java:59)
at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:86)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:58)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30)
at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.lambda$execute$0(BuildTreeScopeLifecycleBuildActionExecuter.java:34)
at org.gradle.internal.buildtree.BuildTreeState.run(BuildTreeState.java:53)
at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.execute(BuildTreeScopeLifecycleBuildActionExecuter.java:33)
at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.execute(BuildTreeScopeLifecycleBuildActionExecuter.java:28)
at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:104)
at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:55)
at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:64)
at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:37)
at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.lambda$execute$0(SessionScopeLifecycleBuildActionExecuter.java:54)
at org.gradle.internal.session.BuildSessionState.run(BuildSessionState.java:67)
at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.execute(SessionScopeLifecycleBuildActionExecuter.java:50)
at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.execute(SessionScopeLifecycleBuildActionExecuter.java:36)
at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36)
at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25)
at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:59)
at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:31)
at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:58)
at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:42)
at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:47)
at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:31)
at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:65)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:39)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:29)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:35)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:78)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:75)
at org.gradle.util.Swapper.swap(Swapper.java:38)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:75)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:63)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:84)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:52)
at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:297)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
at java.base/java.lang.Thread.run(Unknown Source)
1 error

这种问题可以试试是不是java版本问题 切换到java8试试吧

这种问题可以试试是不是java版本问题 切换到java11试试吧

还真是，多谢了

authors: budaowengd wonTonx xin9ge

repo: didi/DoKit


text:
How to use zimic to intercept Supabase Auth?

Hi, @diego-aquino
I'm trying to use zimic with supabase.
scenario:
const supabaseInterceptor = createHttpInterceptor<{
	'/auth/v1/admin/users': {
		POST: {
			request: {
				body: { email: 'email@mail.com'; password: '123456' }
			}
			response: {
				200: { body: { user: { id: '123' } } }
			}
		}
	}
}>({
	worker,
	baseURL: 'http://localhost:8000'
})

My supabase environtment:
SUPABASE ENVS
SUPABASE_URL=http://localhost:8000
Details:
node: 20.10.0
honojs: 4.0.0
Error message:
ConnectionRefused: Unable to connect. Is the computer able to access the url?
path: "http://localhost:8000/auth/v1/admin/users"
Keep going! amazing work here!

Hi, @irvile! Thanks for the detailed description.
To confirm, did you start your worker? If you're using zimic in tests, you could add the following code to your test setup file:
beforeAll(async () => {
  await worker.start()
})

afterAll(async () => {
  await worker.stop()
})

Also, did you apply any mock responses to /auth/v1/admin/users? Creating the interceptor only declares the schema, so mocking endpoints is another step, using interceptor.post in your scenario:
const loginTracker = supabaseInterceptor
  .post('/auth/v1/admin/users')
  .respond({
    status: 200,
    body: { user: { id: '123' } },
  })

// Now, POST requests to /auth/v1/admin/users will be mocked!

Finally (more of a tip), the interceptor schema declares the types of the requests and responses the endpoint accepts. In your case, I believe the following format would be more general:
const supabaseInterceptor = createHttpInterceptor<{
  '/auth/v1/admin/users': {
    POST: {
      request: {
        body: { email: string; password: string }
      }
      response: {
        200: { body: { user: { id: string } } }
      }
    }
  }
}>({
  worker,
  baseURL: process.env.SUPABASE_URL,
})

I started the worker and tracker, but I still encountered a 'ConnectionRefused' error. Afterward, I will create a repository to reproduce this issue.

@irvile, as part of https://github.com/diego-aquino/zimic/issues/34, I'm creating example projects with popular setups. As of now, I've created Node.js, JSDOM, and browser using Jest and Vitest. The examples are current on my partial branch, if you'd like to take a look and compare to your project. I'll let you know when they are finished.
Investigating more about connection refused errors, one possible cause is that MSW (and Zimic by consequence) only applies mocks to the current process, which makes it hard to use in multi-process projects (e.g. a frontend test trying to apply mocks to a backend reaching an external service). I started planning a new feature and API primitives on https://github.com/diego-aquino/zimic/issues/75, which I'm calling "remote HTTP interceptors". I believe they could extend Zimic to multi-process cases, if yours is one of them. Let me know if you have any ideias about it!

Hi, @irvile!
Among other thins, v0.4 introduced remote interceptors and v0.5 improved the logs about unhandled requests. Take a look at the documentation to check if remote interceptors solve the problem you're facing.

Basic usage
Choosing between local and remote interceptors
Creating an HTTP interceptor

I'll close this issue for now. Feel free to re-open it if the problem persists!

authors: diego-aquino irvile

repo: diego-aquino/zimic


text:
mime.qp() docs show invalid encoding

doc/mime.html shows:
print((mime.qp("maçã")))
--> ma=E7=E3=

However, when I run that same command on a Mac, I get:
> print((mime.qp("maçã")))
ma=C3=A7=C3=A3

And furthermore, if I try and decode ma=E7=E3=, I don't get the original text:
> print((mime.unqp("ma=E7=E3")))
ma??

Somewhat related: The mime.unqp() function shows a call to qp() instead of unqp()

This ma=E7=E3= looks like the original string was in a single-byte encoding, probably latin1 (aḱa ISO-8859-1) or something. On the other hand this ma=C3=A7=C3=A3 could be escaped UTF-8. The input is different, so the output is different.
And this:
> print((mime.unqp("ma=E7=E3")))
ma??

probably gives you back the exact same bytes that were in the original string in the documentation, but your terminal doesn't know what to do with them, because it is configured for UTF-8 output.

@siffiejoe you sound like you know what you're talking about. Is it your opinion that these code examples are wrong or obsolete? Or is the issue that Lua behaves differently on DOS vs Unix, and the sources don't translate?

Maybe a bit old. Most Linux distributions (and apparently OSX) have switched to UTF-8 as default encoding, and Windows is still using its own code pages. Maybe a note near the example that the output may depend on the input encoding would be nice.

authors: drauschenbach siffiejoe

repo: diegonehab/luasocket


text:
[move-model] Represent Move attributes in the move-model.

Attributes weren't yet represented in the move-model. This PR adds a representation and extends the model builder to translate them from the expansion AST.
Motivation
Attributes in the model are needed for playing with EVM code generation, and possibly also Jazz.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
NA
Related PRs
NA

:broken_heart: Test Failed - ci-test

/land

authors: bors-libra wrwg

repo: diem/diem


text:
[test] see if this pushes data

Motivation
Test error messages from e2e tests.
Have you read the [Contributing Guidelines on pull requests]
Y
Test Plan
This is a test, hoping to see messages in slack with canary.
Related PRs
None

/canary

:sunny: Canary successful

/canary

:sunny: Canary successful

/canary

:sunny: Canary successful

/canary on the latest code clean up, see that it pushes to slack and then get it landed.

:broken_heart: Test Failed - ci-test-success

/land

authors: bors-libra rexhoffman


text:
[network] Add connection limit metrics

Now we have a metric every time there's a disconnect due to hitting the connection limit.

:broken_heart: Test Failed - ci-test-success

/land

:broken_heart: Test Failed - ci-test-success

/land we need to figure out what's wrong with cluster test

Seems like we already have our first candidate for backporting?

authors: JoshLind bors-libra davidiw gregnazario


text:
[RFC] [read-write-set] Standalone type definition for read-write-set analysis

Motivation
Create a standalone type defintion for read-writeset analysis as the first step to separating the analysis path out from the move-model framework. The PR has two commits:

Create a type definition in move-core-types for types with free variables and the conversion function from move-model internal types to this definition.
Create a type definition crate in language/tools/read-write-set/types for the standalone type definition of the inferred result for read-writeset.

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
TBD

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

LEC dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

LEC dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

LEC dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

:exclamation: Invalid command

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

LEC dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

LEC dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

LEC dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

For this version I exposed the constructor for Loader directly instead of exposing the accessor for Loader in Session. Using Session to access Loader might be a bit tricky because this requires us to handle those self holding struct that rust is notoriously bad at :(. How do you feel about this current approach @vgao1996 ? I can change to use Session but just curious to see your thoughts on lifetimes.

Using Session to access Loader might be a bit tricky because this requires us to handle those self holding struct that rust is notoriously bad at
@runtian-zhou I don't think is the case. A Session holds a &VMRuntime, and a VMRuntime holds a Loader, so effectively a Session holds a simple reference to a Loader. There shouldn't be any weird lifetimes to mess with. In other words, if you are able to implement fn loader(..) -> &Loader then you should be able to implement the APIs I suggested.

Now there is another question: should you implement the APIs for MoveVM orSession? I'd say either is fine.

Exposing these APIs through Session is more consistent with the other APIs we have today. It also allows you to make queries during execution.
However, since I'm currently trying to get rid of Session (or effectively make MoveVM a Session), it's not a big deal if you implement them on MoveVM -- MoveVM will take over the existing public APIs Session has with my change.

Overall I'd recommend you implement these APIs on Session instead of MoveVM, just in case my changes end up taking a long time to get accepted/committed.

LEC dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

release binaries dependency change summary:
target packages:
  A read-write-set-types 0.1.0 (workspace, path 'language/tools/read-write-set/types')
    * features: [none]

Fixed Sam's comments

/land

authors: bors-libra libra-action runtian-zhou vgao1996


text:
abi-read (#187)_92

Motivation
Initial step to support generating Ethereum ABI for Move
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI/CD tests are covered.

/canary

:sunny: Canary successful

/land

:broken_heart: Test Failed - ci-test

/canary

:sunny: Canary successful

/land

@sahithiacn :exclamation: Unable to run the provided command on a closed PR

/land

@sahithiacn :exclamation: Unable to run the provided command on a closed PR

/canary

@sahithiacn :exclamation: Unable to run the provided command on a closed PR

authors: bors-diem sahithiacn

repo: diem/move


text:
Allow options.exclude to be empty

I had scss in node_modules that I wanted to process, so I tried setting exclude to '', but that's falsey, so it defaulted back to 'node_modules/**'. This PR fixes it.

rollup-plugin-sass@0.9.2

authors: differui jakearchibald

repo: differui/rollup-plugin-sass


text:
Find JRE home directory even without org.gradle.java.home

After disabling the IDE plugin I got a bit further, but there seems to be also a problem with the deploy project.
It complains about at missing org.gradle.java.home property. I couldn't find any reference to that property in the repository, so I assume it's something internal. Is this something that has to be set explicitly?
10:10 $ ./gradlew eclipse --stacktrace

FAILURE: Build failed with an exception.

* Where:
Build file '/home/simon/repos/gradle_and_eclipse_rcp/deploy/build.gradle' line: 11

* What went wrong:
A problem occurred evaluating project ':deploy'.
> Could not create task of type 'PdeBuildTask'.

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.GradleScriptException: A problem occurred evaluating project ':deploy'.
        at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93)
        at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:177)
        at org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77)
        at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:182)
        at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:38)
        at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:25)
        at org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
        at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:55)
        at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:540)
        at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:93)
        at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:47)
        at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:35)
        at org.gradle.initialization.DefaultGradleLauncher$2.run(DefaultGradleLauncher.java:124)
        at org.gradle.internal.Factories$1.create(Factories.java:22)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:53)
        at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:121)
        at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
        at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:98)
        at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:92)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:63)
        at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:92)
        at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:83)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:99)
        at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
        at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:48)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30)
        at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:81)
        at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:46)
        at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:51)
        at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:28)
        at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
        at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:239)
        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:212)
        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:205)
        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
        at org.gradle.launcher.Main.doAction(Main.java:33)
        at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:55)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:36)
        at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
        at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30)
        at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129)
        at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Caused by: org.gradle.api.tasks.TaskInstantiationException: Could not create task of type 'PdeBuildTask'.
        at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:123)
        at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:118)
        at org.gradle.util.GUtil.uncheckedCall(GUtil.java:401)
        at org.gradle.api.internal.AbstractTask.injectIntoNewInstance(AbstractTask.java:176)
        at org.gradle.api.internal.project.taskfactory.TaskFactory.create(TaskFactory.java:118)
        at org.gradle.api.internal.project.taskfactory.TaskFactory.createTask(TaskFactory.java:77)
        at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory.createTask(AnnotationProcessingTaskFactory.java:101)
        at org.gradle.api.internal.project.taskfactory.DependencyAutoWireTaskFactory.createTask(DependencyAutoWireTaskFactory.java:39)
        at org.gradle.api.internal.tasks.DefaultTaskContainer.create(DefaultTaskContainer.java:62)
        at org.gradle.api.internal.project.AbstractProject.task(AbstractProject.java:943)
        at org.gradle.internal.metaobject.BeanDynamicObject$MetaClassAdapter.invokeMethod(BeanDynamicObject.java:374)
        at org.gradle.internal.metaobject.BeanDynamicObject.invokeMethod(BeanDynamicObject.java:169)
        at org.gradle.internal.metaobject.CompositeDynamicObject.invokeMethod(CompositeDynamicObject.java:96)
        at org.gradle.internal.metaobject.MixInClosurePropertiesAsMethodsDynamicObject.invokeMethod(MixInClosurePropertiesAsMethodsDynamicObject.java:30)
        at org.gradle.internal.metaobject.AbstractDynamicObject.invokeMethod(AbstractDynamicObject.java:163)
        at org.gradle.groovy.scripts.BasicScript.methodMissing(BasicScript.java:79)
        at build_axh9t715uizzgbjlx7ac8bu6c.run(/home/simon/repos/gradle_and_eclipse_rcp/deploy/build.gradle:11)
        at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:91)
        ... 50 more
Caused by: groovy.lang.MissingPropertyException: Could not get unknown property 'org.gradle.java.home' for project ':deploy' of type org.gradle.api.Project.
        at org.gradle.internal.metaobject.AbstractDynamicObject.getMissingProperty(AbstractDynamicObject.java:85)
        at org.gradle.internal.metaobject.AbstractDynamicObject.getProperty(AbstractDynamicObject.java:62)
        at org.gradle.api.internal.project.AbstractProject.property(AbstractProject.java:790)
        at com.diffplug.gradle.pde.JdkConfig.<init>(JdkConfig.java:33)
        at com.diffplug.gradle.pde.PdeBuildTask.<init>(PdeBuildTask.java:124)
        at com.diffplug.gradle.pde.PdeBuildTask_Decorated.<init>(Unknown Source)
        at org.gradle.api.internal.DependencyInjectingInstantiator.newInstance(DependencyInjectingInstantiator.java:56)
        at org.gradle.api.internal.ClassGeneratorBackedInstantiator.newInstance(ClassGeneratorBackedInstantiator.java:36)
        at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:121)
        ... 67 more

BUILD FAILED

Hmm...  A ton of stuff has been fixed, but I'm not sure if this has or not...
When running PDE build, you have to set the exact location of JRE (for rt.jar).  We obtain that using the JdkConfig class which gets it from the org.gradle.java.home property.  I've got it set on all my machines, but it looks like the docs make it optional.  I'm sure there's a way to get the home of the currently running java.
Btw, thanks very much for running QC on this example project :).  It's much improved now.

I think it should be fixed now, thanks to this commit:
https://github.com/diffplug/goomph/commit/26f5abcd2957d068226e0a7e2f4d40a8400eb442

Looks good. Thanks a lot!
I will try it out on the weekend.

I'm gonna close this for now.  Feel free to reopen if the issue hasn't been resolved :)

With the current version I still get the following exception:
[jh@jonathan-pc gradle_and_eclipse_rcp]$ ./gradlew --stacktrace ide

FAILURE: Build failed with an exception.

* Where:
Build file '/home/jh/IdeaProjects/gradle_and_eclipse_rcp/deploy/build.gradle' line: 13

* What went wrong:
A problem occurred evaluating project ':deploy'.
> Could not create task of type 'PdeBuildTask'.

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.GradleScriptException: A problem occurred evaluating project ':deploy'.
	at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93)
	at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:177)
	at org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77)
	at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:182)
	at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:38)
	at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:25)
	at org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:55)
	at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:540)
	at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:93)
	at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:47)
	at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:35)
	at org.gradle.initialization.DefaultGradleLauncher$2.run(DefaultGradleLauncher.java:124)
	at org.gradle.internal.Factories$1.create(Factories.java:22)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:53)
	at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:121)
	at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
	at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:98)
	at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:92)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:63)
	at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:92)
	at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:83)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:99)
	at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:48)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30)
	at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:81)
	at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:46)
	at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:51)
	at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:28)
	at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
	at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
	at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:239)
	at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:212)
	at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
	at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
	at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
	at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
	at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:205)
	at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
	at org.gradle.launcher.Main.doAction(Main.java:33)
	at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
	at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:55)
	at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:36)
	at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
	at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Caused by: org.gradle.api.tasks.TaskInstantiationException: Could not create task of type 'PdeBuildTask'.
	at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:123)
	at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:118)
	at org.gradle.util.GUtil.uncheckedCall(GUtil.java:401)
	at org.gradle.api.internal.AbstractTask.injectIntoNewInstance(AbstractTask.java:176)
	at org.gradle.api.internal.project.taskfactory.TaskFactory.create(TaskFactory.java:118)
	at org.gradle.api.internal.project.taskfactory.TaskFactory.createTask(TaskFactory.java:77)
	at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory.createTask(AnnotationProcessingTaskFactory.java:101)
	at org.gradle.api.internal.project.taskfactory.DependencyAutoWireTaskFactory.createTask(DependencyAutoWireTaskFactory.java:39)
	at org.gradle.api.internal.tasks.DefaultTaskContainer.create(DefaultTaskContainer.java:62)
	at org.gradle.api.internal.project.AbstractProject.task(AbstractProject.java:943)
	at org.gradle.internal.metaobject.BeanDynamicObject$MetaClassAdapter.invokeMethod(BeanDynamicObject.java:374)
	at org.gradle.internal.metaobject.BeanDynamicObject.invokeMethod(BeanDynamicObject.java:169)
	at org.gradle.internal.metaobject.CompositeDynamicObject.invokeMethod(CompositeDynamicObject.java:96)
	at org.gradle.internal.metaobject.MixInClosurePropertiesAsMethodsDynamicObject.invokeMethod(MixInClosurePropertiesAsMethodsDynamicObject.java:30)
	at org.gradle.internal.metaobject.AbstractDynamicObject.invokeMethod(AbstractDynamicObject.java:163)
	at org.gradle.groovy.scripts.BasicScript.methodMissing(BasicScript.java:79)
	at build_h1k6lxk3yjmxlt7bkjurox31.run(/home/jh/IdeaProjects/gradle_and_eclipse_rcp/deploy/build.gradle:13)
	at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:91)
	... 50 more
Caused by: groovy.lang.MissingPropertyException: Could not get unknown property 'org.gradle.java.home' for project ':deploy' of type org.gradle.api.Project.
	at org.gradle.internal.metaobject.AbstractDynamicObject.getMissingProperty(AbstractDynamicObject.java:85)
	at org.gradle.internal.metaobject.AbstractDynamicObject.getProperty(AbstractDynamicObject.java:62)
	at org.gradle.api.internal.project.AbstractProject.property(AbstractProject.java:790)
	at com.diffplug.gradle.pde.JdkConfig.<init>(JdkConfig.java:38)
	at com.diffplug.gradle.pde.PdeBuildTask.<init>(PdeBuildTask.java:116)
	at com.diffplug.gradle.pde.PdeBuildTask_Decorated.<init>(Unknown Source)
	at org.gradle.api.internal.DependencyInjectingInstantiator.newInstance(DependencyInjectingInstantiator.java:56)
	at org.gradle.api.internal.ClassGeneratorBackedInstantiator.newInstance(ClassGeneratorBackedInstantiator.java:36)
	at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:121)
	... 67 more

BUILD FAILED

Thanks for letting me know!  Should be fixed now.  Reopen if not.

authors: HaasJona nedtwigg stempler


text:
Feature/0.1/create seed.sql

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[ ] Bug Fix
[x] Optimization
[ ] Documentation Update

Description
Added a seed sql file to accelerate local testing, especially when testing data after local migration before pushing to prod
Related Tickets & Documents

Related Issue #
Closes .1 create a sql seed file

QA Instructions, Screenshots, Recordings
seed.sql is ran everytime local supabase db is started

Added/updated tests?

[ ] Yes
[x] No, and this is why: no code changes, this allows for a better local DX it's closer to a doc change
[ ] I need help with writing tests

[optional] Which Seattle Humane animal would you like to dedicate this PR to?
Lucy

this pr depends on #67

I fixed the generate types issue in your other PR, you can get the changes from there!

discussed further with @DillonOLeary on office hours, decided that we will adopt snaplet for seeding, I'll work on it after finishing my sprint-6 tasks
so this pr will not be merged until snaplet is implemented

@AdelBeit Before you make more progress on this PR, I think you should sync up with Sharrief. He's working on a similar change

solved by #71

authors: AdelBeit DillonOLeary

repo: digitalaidseattle/seattle-humane-app


text:
Initial

This is currently configured to use beta.authn.io, not a local authorization.io.  Once we have a working dev local wallet we can switch it.  The credential request flow completes successfully.
Moving this on to the UI department.
@JoshDunnDev It is my intention that this should be as close to developing with Bedrock as possible.  It has quasar etc.  I expect that you'll be able to add pages and adjust the CHAPI flows as necessary.

@dlongley I was wondering about https.  The CHAPI stuff does work as is however.  I've been using Firefox to test?
I was imagining that we might deploy this by terminating https nginx.

@mattcollier, well sounds like I will need to fix the bug sooner rather than later then.

@dlongley just tested with Chrome as well and it works fine.  As in... a credential request from the wallet work.

authors: dlongley mattcollier

repo: digitalbazaar/demo-issuer-integration


text:
OWF: ReferenceError: Property 'Buffer' doesn't exist, js engine: hermes

Describe the bug
While running the LCW app on a hardware Android device, I encounter the following error:
 ERROR  ReferenceError: Property 'Buffer' doesn't exist, js engine: hermes
 ERROR  Invariant Violation: "main" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called., js engine: hermes

Additionally, it seems that the Metro recognizes the device to be iOS, considering the value of the platform query parameter of the URL located at the path $.launchAsset.url at http://localhost:8081:
{
  "id": "0bdc1a2b-20ed-4cd0-a460-f8959804efa0",
  "createdAt": "2024-03-07T22:27:22.388Z",
  "runtimeVersion": "1.0.0",
  "launchAsset": {
    "key": "bundle",
    "contentType": "application/javascript",
    "url": "http://127.0.0.1:8081/index.bundle?platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app"
  },
  "assets": [],
  "metadata": {},
  "extra": {
    "eas": {},
    "expoClient": {
      "runtimeVersion": "1.0.0",
      "name": "Learner Credential Wallet",
      "slug": "learner-credential-wallet",
      "version": "1.0.0",
      "orientation": "portrait",
      "icon": "./app/assets/icon.png",
      "backgroundColor": "#1F2937",
      "splash": {
        "image": "./app/assets/splash.png",
        "resizeMode": "contain",
        "backgroundColor": "#1F2937",
        "imageUrl": "http://127.0.0.1:8081/assets/./app/assets/splash.png"
      },
      "updates": {
        "fallbackToCacheTimeout": 0
      },
      "assetBundlePatterns": [
        "**/*"
      ],
      "ios": {
        "supportsTablet": true,
        "bundleIdentifier": "edu.mit.eduwallet",
        "entitlements": {
          "com.apple.security.application-groups": [
            "group.edu.mit.eduwallet"
          ]
        },
        "associatedDomains": [
          "applinks:lcw.app/mobile"
        ],
        "infoPlist": {
          "CFBundleURLTypes": [
            {
              "CFBundleURLSchemes": [
                "dccrequest"
              ]
            }
          ],
          "NSCameraUsageDescription": "$(PRODUCT_NAME) needs access to your Camera to scan QR codes."
        }
      },
      "android": {
        "adaptiveIcon": {
          "foregroundImage": "./app/assets/adaptive-icon.png",
          "backgroundColor": "#1F2937",
          "foregroundImageUrl": "http://127.0.0.1:8081/assets/./app/assets/adaptive-icon.png"
        },
        "intentFilters": [
          {
            "action": "VIEW",
            "autoVerify": false,
            "data": [
              {
                "scheme": "dccrequest",
                "host": "request"
              },
              {
                "scheme": "dccrequest",
                "host": "present"
              }
            ],
            "category": [
              "BROWSABLE",
              "DEFAULT"
            ]
          }
        ],
        "package": "edu.wallet",
        "permissions": [
          "android.permission.CAMERA"
        ]
      },
      "web": {
        "favicon": "./app/assets/favicon.png"
      },
      "plugins": [
        [
          "react-native-vision-camera",
          {
            "cameraPermissionText": "$(PRODUCT_NAME) needs access to your Camera to scan QR codes.",
            "enableMicrophonePermission": false,
            "enableCodeScanner": true
          }
        ]
      ],
      "_internal": {
        "isDebug": false,
        "projectRoot": "/Users/.../learner-credential-wallet",
        "dynamicConfigPath": {},
        "staticConfigPath": "/Users/.../learner-credential-wallet/app.json",
        "packageJsonPath": "/Users/.../learner-credential-wallet/package.json",
        "pluginHistory": {
          "react-native-vision-camera": {
            "name": "react-native-vision-camera",
            "version": "3.9.1"
          }
        }
      },
      "sdkVersion": "50.0.0",
      "platforms": [
        "ios",
        "android"
      ],
      "iconUrl": "http://127.0.0.1:8081/assets/./app/assets/icon.png",
      "hostUri": "127.0.0.1:8081"
    },
    "expoGo": {
      "debuggerHost": "127.0.0.1:8081",
      "developer": {
        "tool": "expo-cli",
        "projectRoot": "/Users/.../learner-credential-wallet"
      },
      "packagerOpts": {
        "dev": true
      },
      "mainModuleName": "index",
      "__flipperHack": "React Native packager is running"
    },
    "scopeKey": "@anonymous/learner-credential-wallet-c93e2f75-6a43-4dad-9a1f-134a820203bb"
  }
}

To Reproduce
Steps to reproduce the behavior:

Clone LCW repo
Run npm i --legacy-peer-deps
Run npm run prebuild:android
Run npm start in one terminal window
Run npm run android in another window
Observe error

Expected behavior
App should launch on Android device without issue.
Smartphone:

Device: Galaxy S10

Hello,
I tried to reproduce this given the above steps, but for me the app builds and runs fine.
So unfortunately, this is not actionable for me at this point.
With regard to launchAsset, I'm not sure what the field is exactly, but I don't think it's a problem - I see the same stuff when I go to http://localhost:8081/ and the app works for me. Metro doesn't perform any device detection afaik, it just serves what you ask it to serve.

@kezike Not sure what happened, but I can no longer replicate this issue on my end either. Is this still happening for you? If not, we can close this issue.

@dmitrizagidulin Just reproduced this on a fresh install. Re-assigning to @vonovak .

Update: fix in demo branch, not in store yet.

Quick fix still needed before merging PR, then can be moved to Done after main gets deployed to app store: https://github.com/digitalcredentials/learner-credential-wallet/pull/599/files

Deployed to both Google Play and App Store (release 2.1.0-build80), closing ticket.

authors: alexfigtree kezike vonovak


text:
HIX calculation for pages with no real text

Describe the Bug

Pages with only html tags in its content are not handled as empty pages, and HIX calculation/refresh is activated and it fails to retriev HIX value.
Steps to Reproduce

Opne a new page
Insert per "View -> Source code" html tags (example below)
Click the HIX update button or save the page
See the error in the box "Text understandability"

Expected Behavior

Such a page is handled as empty page (and show "There is no page content")
or
Manage to fetch HIX value
Actual Behavior

HIX retrieving is activ but fails.
Additional Information

See this similar bug too #2916
Exmple1:

Exmaple2:

Error like HIX benchmark API call failed: <HTTPError 400: 'Bad Request'> was not observed but Failed to retrieve the hix score for <PageTranslation (.........)>

Traceback

Solution from the issue grooming: do not send the text to TextLab if the page doesn not contain real text.

repo: digitalfabrik/integreat-cms


text:
fix incorrect test data

The length field of the payload for the Run test wasn't accurate (it was 0x74, the data provided was 0x7A).  Since the test previously wasn't sending any subsequent messages, it went unnoticed that it left unread bytes on the pipe that the next read would pick up thinking it was reading the next header when it wasn't.  In addition, the data itself needs to conform to XDR's 4 byte block size.
Adding the Connect/Disconnect calls to the mock libvirt is just a way to trigger the code to encounter the unexpected extra bytes on the pipe.

Force merging because the zombie Travis CI is still lurking.

repo: digitalocean/go-libvirt


text:
Structured import of VMs/Devices e.g. with JSON

Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation
Environment

Python version:  3.5.2
NetBox version:  v2.2-beta1

Description
Use case: I want to import VMs.  I have an existing table of VMs with their IPv4 and IPv6 addresses.
Using CSV import, this would be a three-step affair:

Import VMs with just their names + cluster
Import interfaces (not yet supported, see #1492 and #822)
Import IP addresses (not yet supported for VMs, see #1500)

Importing Devices requires steps 1 and 3, if the Device Type has been properly configured to create the interfaces.
So I am suggesting some sort of structured import which can create the related items at once, e.g.
{"name":"unifi","platform":"Ubuntu 16.04","interfaces":[
  {"name":"eth0","mac":"54:00:00:28:56:1c","addresses":[
    {"address":"192.0.2.30/24","primary":True},
    {"address":"2001:db8::30/64","primary":True}
  ]}
]}

(If this were done for Device, then any interfaces which had been pre-created from the Device Type would be updated rather than created)
This sort of import could be done via the API.  However as far as I can tell, the API doesn't support transactions, so the importer application would have to explicitly track changes and roll them back on error.

The CSV-formatted bulk import functions work with only one type of object at a time and are provided for convenience. Any bulk operations requiring more complex logic will need to be performed via the REST API (or directly via the CLI shell). As with most APIs, you'll need to handle errors on the client side accordingly.

authors: candlerb jeremystretch

repo: digitalocean/netbox


text:
manage.py migrate fails

Issue type
[ ] Feature request
[X] Bug report
[ ] Documentation

Environment

Python version:  3.4.5
NetBox version:  2.1.5 / 2.2-beta2

Description
I am stepping through the readme and I receive the following when running python manage.py migrate
Running migrations:
Applying dcim.0008_device_remove_primary_ip...Traceback (most recent call last):
File "/usr/lib/python3.4/site-packages/django/db/backends/utils.py", line 65, in execute
return self.cursor.execute(sql, params)
psycopg2.ProgrammingError: syntax error at or near "ORDER"
LINE 3:                 indexname, array_agg(attname ORDER BY rnum),...
^
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/usr/lib/python3.4/site-packages/django/core/management/init.py", line 364, in execute_from_command_line
utility.execute()
File "/usr/lib/python3.4/site-packages/django/core/management/init.py", line 356, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python3.4/site-packages/django/core/management/base.py", line 283, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/lib/python3.4/site-packages/django/core/management/base.py", line 330, in execute
output = self.handle(*args, **options)
File "/usr/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 204, in handle
fake_initial=fake_initial,
File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 115, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 145, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 244, in apply_migration
state = migration.apply(state, schema_editor)
File "/usr/lib/python3.4/site-packages/django/db/migrations/migration.py", line 129, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "/usr/lib/python3.4/site-packages/django/db/migrations/operations/fields.py", line 155, in database_forwards
schema_editor.remove_field(from_model, from_model._meta.get_field(self.name))
File "/usr/lib/python3.4/site-packages/django/db/backends/base/schema.py", line 463, in remove_field
fk_names = self._constraint_names(model, [field.column], foreign_key=True)
File "/usr/lib/python3.4/site-packages/django/db/backends/base/schema.py", line 989, in _constraint_names
constraints = self.connection.introspection.get_constraints(cursor, model._meta.db_table)
File "/usr/lib/python3.4/site-packages/django/db/backends/postgresql/introspection.py", line 233, in get_constraints
""", [table_name])
File "/usr/lib/python3.4/site-packages/django/db/backends/utils.py", line 65, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/python3.4/site-packages/django/db/utils.py", line 94, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/lib/python3.4/site-packages/django/utils/six.py", line 685, in reraise
raise value.with_traceback(tb)
File "/usr/lib/python3.4/site-packages/django/db/backends/utils.py", line 65, in execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: syntax error at or near "ORDER"
LINE 3:                 indexname, array_agg(attname ORDER BY rnum),...

Thank you for your interest in NetBox. GitHub issues are intended for reporting bugs and requesting features, and must be submitted using the template provided here. For general discussion, questions, or assistance with installation issues, please post to our mailing list.

authors: jcv- jeremystretch


text:
Missing information by exporting (IP-addresse, custom fields)

Issue type
[ ] Feature request
[x] Bug report
[ ] Documentation

Environment

Python version:  3.5.3-1
NetBox version:  2.2.2

Description
The problem is, that I can create virtual machines, add interfaces and assign IP-addresses. When I export the virtual machines, the Interfaces and the IP-addresses are missing. By exporting, I am loosing these informations.
I got the same problem on custom fields, they are not exported either.
I have no idea, if this is a bug or a missing feature. Do you think, there is anything I could do about it?

One way to solve problem is using export templates.
http://netbox.readthedocs.io/en/stable/data-model/extras/#export-templates

The built-in CSV export functionality includes only the type of object being exported, which is sufficient for many cases. As @PeepOks pointed out, you can easily create custom export templates to extend this functionality and export objects in whatever format you like.

authors: PeepOks hansapils jeremystretch


text:
Move Netty and ModbusTcpCodec into package "tcp" to fix split packages

Regarding the issue #82 I made a quick PR. I'm not sure if you are open to moving the two classes but if so this is a quick fix.

See https://github.com/digitalpetri/modbus/pull/84 instead

A full fix, appreciated!

authors: kevinherron unverbraucht

repo: digitalpetri/modbus


text:
Allow for undefined vars in parser

@emord @czue much better

seems legit to me but i don't feel like I know enough about this to merge. will let @snopoke take a quick peek

authors: benrudolph czue

repo: dimagi/commcarehq-ansible


text:
🛑 android-9.0.0_r61 is down

In 9c24ebe, android-9.0.0_r61 (http://aospxref.com/android-9.0.0_r61/) was down:

HTTP code: 404
Response time: 163 ms

Resolved: android-9.0.0_r61 is back up in 59628f0 after 8 minutes.

repo: dimenspace/aosp-uptime