Enable hex printer in cargo-miri-test

Once https://github.com/rust-lang/rust/pull/52744 lands
We probably should also add memrchr to the main test suite, then.

It occurred to me that my patch would not be sufficient, and indeed...
error[E0080]: constant evaluation error: tried to access memory with alignment 1, but alignment 8 is required
   --> /home/r/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libcore/slice/memchr.rs:119:21
    |
119 |             let u = *(ptr.offset(offset as isize - 2 * usize_bytes as isize) as *const usize);
    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ tried to access memory with alignment 1, but alignment 8 is required
    |
note: inside call to `core::slice::memchr::memrchr`
   --> tests/run-pass-fullmir/memchr.rs:69:39
    |
69  |         assert_eq!(Some(pos - start), memrchr(needle, &data[start..]));
    |                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: inside call to `each_alignment_reversed`
   --> tests/run-pass-fullmir/memchr.rs:89:5
    |
89  |     each_alignment_reversed();
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

miri puts the entire slice into the first argument, leading memrchr to think that most of it is actually aligned.
I'll have to tweak the implementation some more.

Opened https://github.com/rust-lang/rust/pull/52854

Fixed by https://github.com/solson/miri/pull/423


custom JSON

hey, is there a way to pass a custom json to Choices? an item looks this way:
  id: 21,
  code: 1231
  name: 'Name'

Hi @cmnstmntmn,
Could you give me some more information as to what you are trying to achieve? I think you're refereeing to the setChoices() method, by let me know.
Thanks


When using the esp_HA_customized_light.c example, an error occurred, causing a restart，Hardware :esp32s3 (TZ-371)

Answers checklist.

[X] I have read the documentation ESP Zigbee SDK Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) and ESP Zigbee libs (esp-zboss-lib and esp-zigbee-lib) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1
esp-zigbee-lib version.
1.0.0
esp-zboss-lib version.
1.0.0
Espressif SoC revision.
ESP32-S3
What is the expected behavior?
esp_zb_cluster_list_update_basic_cluster(esp_zb_cluster_list, esp_zb_basic_cluster_create(NULL), ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_identify_cluster(esp_zb_cluster_list, esp_zb_identify_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_groups_cluster(esp_zb_cluster_list, esp_zb_groups_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_scenes_cluster(esp_zb_cluster_list, esp_zb_scenes_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_on_off_cluster(esp_zb_cluster_list, esp_zb_on_off_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
What is the actual behavior?
The esp32s3 ran for less than a minute and then restarted
annotation： esp_zb_cluster_list_add_on_off_cluster(esp_zb_cluster_list, esp_zb_on_off_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
will normalize
Steps to reproduce.

on esp32h2  , run  /examples/esp_zigbee_customized_devices/customized_client
on esp32s3  , run  /examples/esp_zigbee_customized_devices/customized_server
esp32s3 The esp32s3 ran for less than a minute and then restarted

More Information.
I have trace enabled, but my debug log has the following print:
I (9060) ZBOSS: macsplit/zb_macsplit_proto.c:361 rx body byte 0x33 received_bytes 51
I (9070) ZBOSS: macsplit/zb_macsplit_proto.c:361 rx body byte 0x2d received_bytes 52
I (9080) ZBOSS: macsplit/zb_macsplit_proto.c:361 rx body byte 0x31 received_bytes 53
I (9090) ZBOSS: macsplit/zb_macsplit_proto.c:361 rx body byte 0x30 received_bytes 54
I (9100) ZBOSS: macsplit/zb_macsplit_proto.c:361 rx body byte 0x2d received_bytes 55
I (9110) ZBOSS: macsplit/zb_macsplit_proto.c:361 rx body byte 0x33 received_bytes 56
I (9120) ZBOSS: macsplit/zb_macsplit_host.c:171 >radio boot indication
I (9120) ZBOSS: macsplit/zb_macsplit_host.c:173 boot indication
I (9130) ZBOSS: macsplit/zb_macsplit_host.c:213 Unexpected zb_mlme_dev_reset_conf - seems, device is asserted
I (9140) ZBOSS: common/zb_error_indication.c:93 >> zb_error_raise severity 254, err_code -2561
I (9150) ZBOSS: common/zb_error_indication.c:59 Error is not handled: severity 254, err_code -2561
I (9160) ZBOSS: common/zb_debug.c:64 Assertion failed /home/xieqinan/ESP/esp-zboss/components/zboss_stack/zboss/common/zb_error_indication.c:81
abort() was called at PC 0x4201a79f on core 0
0x4201a79f: zb_assert at ??:?
Backtrace: 0x403759da:0x3fca5a30 0x4037b22d:0x3fca5a50 0x40380e0e:0x3fca5a70 0x4201a79f:0x3fca5ae0 0x420713af:0x3fca5b10 0x42071403:0x3fca5b40 0x42068815:0x3fca5b70 0x42021a2a:0x3fca5c20 0x42054b5b:0x3fca5c70 0x4200f7d3:0x3fca5c90 0x4200b63a:0x3fca5cb0 0x4037dad1:0x3fca5cf0
0x403759da: panic_abort at C:/Espressif/frameworks/esp-idf-v5.1.1/components/esp_system/panic.c:452
....
emm...
....
I don't know what to do next, my log happened on esp32s3, using rcp mode to communicate with esph2, please give me some tips, so that I know how to deal with it, OK?

@teleger

2. on esp32s3  , run  /examples/esp_zigbee_customized_devices/customized_server

Please use another ESP32H2 to run customized_server example,  because the ESP32S3 does not support IEEE802154.

@teleger

on esp32s3  , run  /examples/esp_zigbee_customized_devices/customized_server

Please use another ESP32H2 to run customized_server example, because the ESP32S3 does not support IEEE802154.

i am use h2 + s3 board, run uart rsp mode , code run s3?

@teleger，
You can use the ESP32S3 + ESP32H2 to support Zigbee by referring to the gateway example in the ESP-Zigbee SDK repository. Before doing so, please make sure to read the README.md file in the example.

@teleger，
You can use the ESP32S3 + ESP32H2 to support Zigbee by referring to the gateway example in the ESP-Zigbee SDK repository. Before doing so, please make sure to read the README.md file in the example.

on the esp32h2 board:
run  : /examples/esp_zigbee_HA_sample/HA_on_off_light
on the esp32s3 + esp32h2 board:
run : /examples/esp_zigbee_HA_sample/HA_on_off_switch
is  OK
however,I want to use this example,
/examples/esp_zigbee_customized_devices   client and server folder;
The situation described above arises.
You can run the code on the hardware I'm talking about, and if you run it and it doesn't happen, then I'll close the problem. If there is a problem, can you take a look? Or is the current code not going to run on the hardware I'm talking about?

@teleger ,
The /examples/esp_zigbee_customized_devices/customized_client is designed specifically for the Zigbee end device running on ESP32H2 and will work fine. Expecting it to run on ESP32S3+H2 is impractical and wasteful.


Add limit-width option

When working on very narrow windows I noticed that if the buffer name
was too long, it would cause a floating window that would overflow out
of the pane it was representing. This may be desirable for some, but I'd
rather limit it to the width of the buffer.
That is what the new limit-width option provides; when enabled, should
the buffer text not fit in the available width, it will truncate it to
do so.
I can see future expansions to this if you think they are appropriate:

don't truncate the text, but have it wrap over multiple lines
allow the user to customise more how the buffer name is truncated -
custom replacements, perhaps?

Please let me know what you think, and if this is something you're happy
to land. Thanks!

Here's an example of the truncation in action:

I like this PR.
Happy to merge as is.
Im not sure if wrapping the text. A replace function can be cool, but also wanted to keep this plugin just very stupid, as there seems to be  https://github.com/b0o/incline.nvim If people really want to customize things.

Sounds good to me! Thanks
On Sat, 20 Aug 2022, 10:51 Louis DeLosSantos, @.***>
wrote:

I like this PR.
Happy to merge as is.
Im not sure if wrapping the text. A replace function can be cool, but also
wanted to keep this plugin just very stupid, as there seems to be
https://github.com/b0o/incline.nvim If people really want to customize
things.
—
Reply to this email directly, view it on GitHub
https://github.com/ldelossa/buffertag/pull/7#issuecomment-1221376055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABPFVWG24QXXHV7QBRFHLDV2ELJBANCNFSM57DQYIAA
.
You are receiving this because you authored the thread.Message ID:
@.***>


FixIT+ transcripts reverting back to original status

Describe the bug
Hi,
One of the Kansas transcribers has noted an issue when she edits transcripts in the FixIT+. She is currently an admin, but has noticed that after she edits a transcript, upon going back and checking the transcript in question, some (not all) of the lines have changed back to a previous edit, and not what she had input.
It should be noted that other Kansas transcribers haven't reported a similar issue; I'm not sure if it's something about her system, poor timing (maybe she was editing at the same time as another admin-Kansas transcriber), or something else!
We're also kind of wondering if it's something she's doing, although I wouldn't be sure how...
In short, we're not 100% sure what the issue is, or if there even is an issue, but it would be great if someone can give this a look into!
To Reproduce
Steps to reproduce the behavior:
Not sure how to reproduce the error, since I haven't experienced it myself. I guess edit a couple lines as admin and see what happens.
Expected behavior
I would expect the transcript to retain the admin person's edits!
Screenshots
Desktop (please complete the following information):

Browser: Chrome

Hi there,
Sorry, I'm actually the Kansas transcriber with this problem! Any help you all might be able to provide would be fantastic.
Here's some background info in case this is useful - I have been working on the Kansas files for a couple of months just on my own, but just got Admin status recently. Basically, there are a handful of "completed" transcripts that were done partially by me and partially by another volunteer. These few have errors throughout that need to be fixed for the transcript to be usable. I assumed with Admin status I could just hop on there, make the correction, and the file would be ready to go. Again, keep in mind that all the files I'm talking about in this case are ones that are fully "dark green" and technically completed.
Unfortunately, I'm running into a strange problem. I spent several hours working on corrections to a couple of files, which I will link. But when I went back to review them, only about half of my changes had saved. The others had, seemingly in a random pattern, reverted back to incorrect text.
On this particular file (Artsnotes '88), the top half was originally completed by someone else and has quite a few errors. As you can see in the first few lines, there is a female interviewee whose name is supposed to be spelled Ossie E. Tranbarger. But it was originally spelled ?Aussie Trenbergar? (question marks included) and variations thereof. When I try to correct all instances of this misspelling, along with many other errors throughout the document, only some changes will stick. I've run into the same problem on the other correction files as well.
LINK:
https://fixitplus.americanarchive.org/transcripts/cpb-aacip_836e5cb7520
OK, I'm really grasping at straws here, so please ignore this part if it makes no sense.
Here is my amateur guess as to what's happening. As you know, there is an algorithm in the software that "selects" the best transcript provided by volunteers by rating it. The algorithm judges lines that have more punctuation and capital letters and ellipses as "better."
Now obviously this algorithm is not useful at all in the editing stage, as presumably the editor/admin (in this case me) knows exactly where he wants to remove or place punctuation and capitals, etc. Although I do have Admin access, the system seems to be somehow still rating my corrections and deciding whether or not to save them based on this algorithm.
From what I understand from other software, sometimes this problem can be solved by increasing the "Hierarchy Number" assigned to a particular user. For example, if I was coded as a "5", perhaps a "4" designation would grant me permission to override this algorithm completely in my edits as needed. As for now, I'm unable to make any further corrections to these files, as they simply don't save.
Just as an FYI, I tried to make sure this wasn't something on my end - I tried switching browsers, flagging the line first and reloading the page before making my corrections, deleting the entire word first, deleting the entire line, etc. Nothing made any difference. Occasionally, a change would "stick" for say 20 minutes, and then disappear.
Since presumably everyone here has admin status, please feel free to go to the linked file above to see/experiment with what I'm struggling with. If it would be easier to talk offline, that's no problem either. I'm Marian on the Admin list, btw.
Thank you so much for your help, please let me know what other information I can provide. Naturally if it's something I'm inadvertently doing myself, I'll be hideously embarrassed for wasting your time, but still grateful to be able to move forward on these files! :)
Thanks again!
Marian S.


[GSSoC '23] | Cycle Detection in LinkedList

Task description : -
Given the head of a linked list, determine if the linked list has a cycle in it. There is a cycle in a linked list if there is some node that can be reached again by continuously following the next pointer. Internally, pos is used to denote the index of the node that the tail's next pointer is connected to. Just so you know, pos is not passed as a parameter.
Return true if there is a cycle in the linked list. Otherwise, return false.
Please assign this issue to me @aaryahjolia !!

Can you assigned this issue to me?

Can I have this issue, will make the full documentation with Question links from various platform, In detail explanation of Algorithm used.
For reference you can visit my profile I am trying to do daily Leetcoding, with my JOB.

Hi, I am Contributor for GSSOC'23. Can this issue be assigned to me. I will do the code section with proper documentation with markdown file. For markdown reference can visit my profile.
Regards,
Vivek Kumar


which-function-mode support

Currently,

BeforeAfter

🚢 Shipped with MELPA package release version 🏷 0.2.0.


python-versions 3.10.2 release is missing windows files

Description
Whilst https://github.com/actions/python-versions/releases/tag/3.10.2-121429 added Python 3.10.2, it only has the darwin and linux files, nothing for win32.  As a consequence https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json does not, of course, have win32 entries.
Thus no GitHub workflows for Python on Windows can use 3.10.2.
Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[X] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://github.com/EDCD/EDMarketConnector/actions/runs/1796797978
Is it regression?
No response
Expected behavior
That something like the following work in a GitHub Workflow:
    steps:
      - uses<EMAIL_ADDRESS>      - uses<EMAIL_ADDRESS>        with:
          python-version: "3.10.2"
          architecture: "x86"

Actual behavior
Run<EMAIL_ADDRESS>Version 3.10.2 was not found in the local cache
Error: Version 3.10.2 with arch x86 not found
The list of all available versions can be found here<EMAIL_ADDRESS>(raw)](https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json)

Repro steps
1.Set up a GitHub workflow including the example in 'Expected behaviour'.
2. Run it.
3. See it fail.

Hi @Athanasius .
Thank you for your report. We will take a look at this.

@Athanasius the new version has been generated for windows as well
https://github.com/actions/python-versions/releases/tag/3.10.2-1805098134

@Athanasius the new version has been generated for windows as well<EMAIL_ADDRESS>(release)

Yes, this is working for us now, thanks!


Prepare 0.8.2 release

What kind of change does this PR introduce?

Since this makes it easier to install through pip, it's worth releasing on PyPI.

Does this PR introduce a breaking change?
Other information:

An update ~2 weeks ago releave the -beta, so no need to bump versions for this one.


Support for publishing changelogs to gitlab

Hi,
I have a project on gitlab and have been trying out python-semantic-release. I have managed to use python-semantic-release to bump version and create tag on remote repository.
semantic-release publish

Current version: 1.4.0
Creating new version..
Current version: 1.4.0
Bumping with a minor version to 1.5.0.
Missing token: cannot post changelog
New release published

However, the changelog is not pushed. Based on, [semantic-release] (https://github.com/semantic-release/semantic-release/blob/master/docs/usage/ci-configuration.md#ci-configuration) documentation I have tried setting environment variables GL_TOKEN and GITLAB_TOKEN. However,  these do not seem to be recognised.
What is the environment variable required for gitlab repositories? Is publishing changelog only possible for github repositories?
Kind regards
dcs3spp

Publishing of changelog is only implemented for github. PR for gitlab support is more than welcome.

Hello!
At Sewan we also have this need. We will develop this features and create a PR for you on this topic form : https://github.com/Azraeht/python-semantic-release

I will be working on this in https://github.com/SewanDevs/python-semantic-release.
I will try to make the library more compliant with gitlab in general. For example, the method vcs_helpres.push_new_version contains github specific code. This could be moved in the Github class in hvcs.py.

@dcs3spp just opened a pull request. This will allow the publishing of changelogs on gitlab.com and Gitlab CE (probably EE too, but I did not test it on EE).
Once this is released, you will need to set a gitlab token as GL_TOKEN, change the hvcs configuration key and if you are on a hosted gitlab instance (not gitlab.com), you will need to set CI_SERVER_HOST unless you are in a gitlab ci environment where it is automatically set.
This is normally described in the updated documentation.


*** Build Failed with status: 65.

This is the first time I use Injection For Xcode. When I injection source, it build failed.
Please help me. Thanks !
** BUILD FAILED **
The following build commands failed:
Ld build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle normal x86_64
(1 failure)
*** Build Failed with status: 65. You may need to open and edit the bundle project to resolve issues with either header include paths or Frameworks the bundle links against. ***
at /Users/hnp/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/common.pm line 57.
main::error('Build Failed with status: 65. You may need to open and edit t...') called at /Users/hnp/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/injectSource.pl line 461
*** Bundle build failed ***

The error message should be just before the text above. I’ll need that before I know what the problem is.

Full error message below. Thanks !

Connection from: /Users/hnp/Library/Developer/CoreSimulator/Devices/E8D0A505-CB87-4645-84CD-8A4CEF53CC12/data/Containers/Data/Application/944C526E-324B-41A8-BDFA-6EEF3DFC3432 x86_64 (148)
buidRoot: /Users/hnp/Library/Developer/Xcode/DerivedData/ShipMe-hadbackklizmcqfsucftcuyskdvh/Build
logDir: /Users/hnp/Library/Developer/Xcode/DerivedData/ShipMe-hadbackklizmcqfsucftcuyskdvh/Logs/Build

        1.09 real         0.15 user         0.50 sys
ls: .framework: No such file or directory

Building iOSInjectionProject/InjectionBundle.xcodeproj
"/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild"  -configuration Debug -arch x86_64 -sdk iphonesimulator

2016-04-02 22:33:54.777 xcodebuild[7919:217313] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XVim.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-02 22:33:54.785 xcodebuild[7919:217313] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-02 22:33:54.789 xcodebuild[7919:217313] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/RealmBrowser.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-02 22:33:54.795 xcodebuild[7919:217313] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/OMColorSense.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-02 22:33:54.797 xcodebuild[7919:217313] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Lin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-02 22:33:54.800 xcodebuild[7919:217313] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FuzzyAutocomplete.xcplugin' not present in DVTPlugInCompatibilityUUIDs
Build settings from command line:
    ARCHS = x86_64
    SDKROOT = iphonesimulator9.3

=== BUILD TARGET InjectionBundle OF PROJECT InjectionBundle WITH CONFIGURATION Debug ===

Check dependencies

CompileC build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/BundleContents.o BundleContents.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
    cd /Users/hnp/AppProjects/shipme/iOSInjectionProject
    export LANG=en_US.US-ASCII
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch x86_64 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu99 -fobjc-arc -fmodules -gmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/var/folders/8w/smwgnvk17jgbgw88tt016glh0000gn/C/org.llvm.clang/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in-framework-module -Werror=non-modular-include-in-framework-module -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wmissing-prototypes -Wno-implicit-atomic-properties -Wno-arc-repeated-use-of-weak -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wno-undeclared-selector -Wno-deprecated-implementations -DDEBUG=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mios-simulator-version-min=9.1 -g -Wno-sign-conversion -fobjc-abi-version=2 -fobjc-legacy-dispatch -iquote /Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/InjectionBundle-generated-files.hmap -I/Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/InjectionBundle-own-target-headers.hmap -I/Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/InjectionBundle-all-target-headers.hmap -iquote /Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/InjectionBundle-project-headers.hmap -iquote.. -I/Users/hnp/AppProjects/shipme/iOSInjectionProject/build/Debug-iphonesimulator/include -I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk/usr/include/libxml2 -I/Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/DerivedSources/x86_64 -I/Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/DerivedSources -F/Users/hnp/AppProjects/shipme/iOSInjectionProject/build/Debug-iphonesimulator -include /var/folders/8w/smwgnvk17jgbgw88tt016glh0000gn/C/com.apple.DeveloperTools/7.3-7D175/Xcode/SharedPrecompiledHeaders/InjectionBundle-Prefix-asggasgyyzwyatgevmemjwnrloqo/InjectionBundle-Prefix.pch -MMD -MT dependencies -MF /Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/BundleContents.d --serialize-diagnostics /Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/BundleContents.dia -c /Users/hnp/AppProjects/shipme/iOSInjectionProject/BundleContents.m -o /Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/BundleContents.o

Ld build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle normal x86_64
    cd /Users/hnp/AppProjects/shipme/iOSInjectionProject
    export IPHONEOS_DEPLOYMENT_TARGET=9.1
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch x86_64 -bundle -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk -L/Users/hnp/AppProjects/shipme/iOSInjectionProject/build/Debug-iphonesimulator -F/Users/hnp/AppProjects/shipme/iOSInjectionProject/build/Debug-iphonesimulator -filelist /Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/InjectionBundle.LinkFileList -mios-simulator-version-min=9.1 -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 x86_64/injecting_class.o -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphonesimulator -F/Users/hnp/Library/Developer/Xcode/DerivedData/ShipMe-hadbackklizmcqfsucftcuyskdvh/Build/Products/Debug-iphonesimulator -F/Users/hnp/Library/Developer/Xcode/DerivedData/ShipMe-hadbackklizmcqfsucftcuyskdvh/Build/Products/Debug-iphonesimulator/ShipMe.app/Frameworks -undefined dynamic_lookup -fobjc-arc -fobjc-link-runtime -framework UIKit -framework QuartzCore -framework OpenGLES -framework Foundation -framework CoreGraphics -Xlinker -dependency_info -Xlinker /Users/hnp/AppProjects/shipme/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/InjectionBundle_dependency_info.dat -o /Users/hnp/AppProjects/shipme/iOSInjectionProject/build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle
ld: warning: -undefined dynamic_lookup is deprecated on iOS
ld: framework not found GoogleMaps for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

* BUILD FAILED

The following build commands failed:
	Ld build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle normal x86_64
(1 failure)

* Build Failed with status: 65. You may need to open and edit the bundle project to resolve issues with either header include paths or Frameworks the bundle links against.

 at /Users/hnp/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/common.pm line 57.
	main::error('Build Failed with status: 65. You may need to open and edit t...') called at /Users/hnp/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/injectSource.pl line 461
 Bundle build failed ***

Full error message below. Thanks !
/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/Objects-normal/x86_64/CLoginViewController.dia -c /Users/hnp/AppProjects/MyObjectProject/MyObjectProject/ViewController/CLoginViewController.m -o iOSInjectionProject/x86_64/injecting_class.o
1.09 real         0.15 user         0.50 sys
ls: *.framework: No such file or directory
    Building iOSInjectionProject/InjectionBundle.xcodeproj
    "/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild"  -configuration Debug -arch x86_64 -sdk iphonesimulator

    Ld build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle normal x86_64
    cd /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject
    export IPHONEOS_DEPLOYMENT_TARGET=9.1
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch x86_64 -bundle -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk -L/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/Debug-iphonesimulator -F/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/Debug-iphonesimulator -filelist /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/InjectionBundle.LinkFileList -mios-simulator-version-min=9.1 -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 x86_64/injecting_class.o -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphonesimulator -F/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Products/Debug-iphonesimulator -F/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Products/Debug-iphonesimulator/MyObjectProject.app/Frameworks -undefined dynamic_lookup -fobjc-arc -fobjc-link-runtime -framework UIKit -framework QuartzCore -framework OpenGLES -framework Foundation -framework CoreGraphics -Xlinker -dependency_info -Xlinker /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/InjectionBundle_dependency_info.dat -o /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle
    ld: warning: -undefined dynamic_lookup is deprecated on iOS
    ld: framework not found GoogleMaps for architecture x86_64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

    ** BUILD FAILED **

    The following build commands failed:
    Ld build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle normal x86_64
    (1 failure)

    *** Build Failed with status: 65. You may need to open and edit the bundle project to resolve issues with either header include paths or Frameworks the bundle links against. ***

    at /Users/hnp/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/common.pm line 57.
    main::error('Build Failed with status: 65. You may need to open and edit t...') called at /Users/hnp/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/injectSource.pl line 461
    *** Bundle build failed ***

    buidRoot: /Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build
    logDir: /Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Logs/Build

    Learnt compile:     /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch x86_64 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu99 -fobjc-arc -fmodules -gmodules -fmodules-cache-path=/Users/hnp/Library/Developer/Xcode/DerivedData/ModuleCache -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/Users/hnp/Library/Developer/Xcode/DerivedData/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in-framework-module -Werror=non-modular-include-in-framework-module -Wno-trigraphs -fpascal-strings -O0 -fno-common -Wno-missing-field-initializers -Wno-missing-prototypes -Werror=return-type -Wunreachable-code -Wno-implicit-atomic-properties -Werror=deprecated-objc-isa-usage -Werror=objc-root-class -Wno-arc-repeated-use-of-weak -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wconditional-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wno-deprecated-implementations -DDEBUG=1 -DCOCOAPODS=1 -DOVERCOAT_SUPPORT_URL_CONNECTION=1 -DOVERCOAT_SUPPORT_URL_SESSION=1 -DOVERCOAT_SUPPORT_REACTIVE_COCOA=1 -DOBJC_OLD_DISPATCH_PROTOTYPES=0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mios-simulator-version-min=7.0 -g -Wno-sign-conversion -fobjc-abi-version=2 -fobjc-legacy-dispatch -iquote /Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/MyObjectProject-generated-files.hmap -I/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/MyObjectProject-own-target-headers.hmap -I/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/MyObjectProject-all-target-headers.hmap -iquote /Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/MyObjectProject-project-headers.hmap -I/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Products/Debug-iphonesimulator/include -I/Users/hnp/AppProjects/MyObjectProject/Pods/Google/Headers -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/AFNetworking -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/ActionSheetPicker-3.0 -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Bolts -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/DZNEmptyDataSet -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/EAIntroView -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/EARestrictedScrollView -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/FBSDKCoreKit -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/FBSDKLoginKit -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Google -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleAnalytics -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleInterchangeUtilities -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleMaps -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleNetworkingUtilities -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleSymbolUtilities -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleUtilities -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/HCSStarRatingView -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/HexColors -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/INTULocationManager -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/IQActionSheetPickerView -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Mantle -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/NSDate+Helper -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Overcoat -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Raygun4iOS -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Reachability -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/ReactiveCocoa -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Realm -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/SVProgressHUD -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/SocketRocket -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/TPKeyboardAvoiding -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/TSMessages -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Toast -I/Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/iOS-Slide-Menu -I/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/DerivedSources/x86_64 -I/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/DerivedSources -F/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Products/Debug-iphonesimulator -F/Users/hnp/AppProjects/MyObjectProject/Pods/GoogleMaps/Frameworks -F/Users/hnp/AppProjects/MyObjectProject/Pods/Raygun4iOS -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/AFNetworking -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/ActionSheetPicker-3.0 -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Bolts -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/DZNEmptyDataSet -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/EAIntroView -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/EARestrictedScrollView -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/FBSDKCoreKit -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/FBSDKLoginKit -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Google -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleAnalytics -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleInterchangeUtilities -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleMaps -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleNetworkingUtilities -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleSymbolUtilities -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/GoogleUtilities -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/HCSStarRatingView -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/HexColors -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/INTULocationManager -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/IQActionSheetPickerView -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Mantle -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/NSDate+Helper -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Overcoat -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Raygun4iOS -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Reachability -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/ReactiveCocoa -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Realm -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/SVProgressHUD -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/SocketRocket -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/TPKeyboardAvoiding -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/TSMessages -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/Toast -isystem /Users/hnp/AppProjects/MyObjectProject/Pods/Headers/Public/iOS-Slide-Menu -include /Users/hnp/AppProjects/MyObjectProject/MyObjectProject/MyObjectProject-Prefix.pch -MMD -MT dependencies -MF /Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/Objects-normal/x86_64/CLoginViewController.d --serialize-diagnostics /Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Intermediates/MyObjectProject.build/Debug-iphonesimulator/MyObjectProject.build/Objects-normal/x86_64/CLoginViewController.dia -c /Users/hnp/AppProjects/MyObjectProject/MyObjectProject/ViewController/CLoginViewController.m -o iOSInjectionProject/x86_64/injecting_class.o
    0.19 real         0.13 user         0.05 sys
    ls: *.framework: No such file or directory

    Building iOSInjectionProject/InjectionBundle.xcodeproj
    "/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild"  -configuration Debug -arch x86_64 -sdk iphonesimulator

    2016-04-02 22:37:20.844 xcodebuild[7990:219539] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XVim.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    2016-04-02 22:37:20.847 xcodebuild[7990:219539] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    2016-04-02 22:37:20.848 xcodebuild[7990:219539] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/RealmBrowser.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    2016-04-02 22:37:20.849 xcodebuild[7990:219539] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/OMColorSense.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    2016-04-02 22:37:20.850 xcodebuild[7990:219539] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Lin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    2016-04-02 22:37:20.851 xcodebuild[7990:219539] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FuzzyAutocomplete.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    Build settings from command line:
    ARCHS = x86_64
    SDKROOT = iphonesimulator9.3

    === BUILD TARGET InjectionBundle OF PROJECT InjectionBundle WITH CONFIGURATION Debug ===

    Check dependencies

    CompileC build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/BundleContents.o BundleContents.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
    cd /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject
    export LANG=en_US.US-ASCII
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch x86_64 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu99 -fobjc-arc -fmodules -gmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/var/folders/8w/smwgnvk17jgbgw88tt016glh0000gn/C/org.llvm.clang/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in-framework-module -Werror=non-modular-include-in-framework-module -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wmissing-prototypes -Wno-implicit-atomic-properties -Wno-arc-repeated-use-of-weak -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wno-undeclared-selector -Wno-deprecated-implementations -DDEBUG=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mios-simulator-version-min=9.1 -g -Wno-sign-conversion -fobjc-abi-version=2 -fobjc-legacy-dispatch -iquote /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/InjectionBundle-generated-files.hmap -I/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/InjectionBundle-own-target-headers.hmap -I/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/InjectionBundle-all-target-headers.hmap -iquote /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/InjectionBundle-project-headers.hmap -iquote.. -I/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/Debug-iphonesimulator/include -I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk/usr/include/libxml2 -I/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/DerivedSources/x86_64 -I/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/DerivedSources -F/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/Debug-iphonesimulator -include /var/folders/8w/smwgnvk17jgbgw88tt016glh0000gn/C/com.apple.DeveloperTools/7.3-7D175/Xcode/SharedPrecompiledHeaders/InjectionBundle-Prefix-asggasgyyzwyatgevmemjwnrloqo/InjectionBundle-Prefix.pch -MMD -MT dependencies -MF /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/BundleContents.d --serialize-diagnostics /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/BundleContents.dia -c /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/BundleContents.m -o /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/BundleContents.o

    Ld build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle normal x86_64
    cd /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject
    export IPHONEOS_DEPLOYMENT_TARGET=9.1
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch x86_64 -bundle -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk -L/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/Debug-iphonesimulator -F/Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/Debug-iphonesimulator -filelist /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/InjectionBundle.LinkFileList -mios-simulator-version-min=9.1 -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 x86_64/injecting_class.o -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphonesimulator -F/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Products/Debug-iphonesimulator -F/Users/hnp/Library/Developer/Xcode/DerivedData/MyObjectProject-hadbackklizmcqfsucftcuyskdvh/Build/Products/Debug-iphonesimulator/MyObjectProject.app/Frameworks -undefined dynamic_lookup -fobjc-arc -fobjc-link-runtime -framework UIKit -framework QuartzCore -framework OpenGLES -framework Foundation -framework CoreGraphics -Xlinker -dependency_info -Xlinker /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/InjectionBundle.build/Debug-iphonesimulator/InjectionBundle.build/Objects-normal/x86_64/InjectionBundle_dependency_info.dat -o /Users/hnp/AppProjects/MyObjectProject/iOSInjectionProject/build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle
    ld: warning: -undefined dynamic_lookup is deprecated on iOS
    ld: framework not found GoogleMaps for architecture x86_64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

    ** BUILD FAILED **

    The following build commands failed:
    Ld build/Debug-iphonesimulator/InjectionBundle.bundle/InjectionBundle normal x86_64
    (1 failure)

    *** Build Failed with status: 65. You may need to open and edit the bundle project to resolve issues with either header include paths or Frameworks the bundle links against. ***

    at /Users/hnp/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/common.pm line 57.
    main::error('Build Failed with status: 65. You may need to open and edit t...') called at /Users/hnp/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/injectSource.pl line 461
    *** Bundle build failed ***

Problem is "ld: framework not found GoogleMaps for architecture x86_64”. You need to set the framework search path of your iOSInjectionProject “Project/Injection Plugin/Open BundleProject” to include the directory where this framework can be found.

Thanks !


[WGPU] Allow for depth buffer in web target

Currently depth textures are not supported on web. This PR takes steps to allow a depth stencil. I'm expecting that I'll have to rename some parts and I might have to shift some things around. For example, I'm not sure if the depth texture option should be in WebOptions, as it is currently in the PR, or in WgpuConfiguration. Another consideration is if I should be moving this logic into some higher abstraction layer or not. Either way, would love feedback! cc @Wumpf

@Wumpf thanks for mentoring on this PR!!! :)


Also use clang flags for ast command. Fixes #650

Fixes #650

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable


add indicesAndValues builtin function

close: #2967

Pull Request Test Coverage Report for Build 97722

0 of 0   changed or added relevant lines in 0 files are covered.
17 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 78.168%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Expressions/BuiltInFunctions.cs
17
92.6%

Totals

Change from base Build 97633:
-0.2%

Covered Lines:
17029

Relevant Lines:
21785

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3


added debug signature to recognizers

recognizers were not capturing file location when instantiated via code, updated constructors to do appropriate goo.

Approved from an adaptive point of view.
@cleemullins In terms of tests, the debugging classes are satellite classes and Tom is adding one more class to which the debugging is satellite to (there are already many). both the recognizers and the debug support have tests separately, so I'm not too concerned about this. If you feel we still need something specific here feel free to discuss with Tom, just chiming in and setting some context.


Added @serverless-guru/prettier-plugin-import-order and updated Prettier config

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#529  👈
#528
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


Shutdown 0 not waiting for active connection to complete

We are trying to shutdown server with 0 and wait active connection to be terminate.
but as soon as Shutdown function get called the server is get terminated.
we should increment connWaitGroup  using .Add(1) and once the connection terminate we should use .Done() function so that the connWaitGroup.wait() funciton wil be wait until the active connection(s) is closed.

@maurice2k  https://github.com/maurice2k/tcpserver/pull/2


refactor(transformer): use identifier_reference_with_reference_id builder method

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#7056  👈
#7055
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


uORB: More timing tests.

This is a WIP branch which will feature a number of uORB timing tests for a systems paper. Non-intrusive during runtime.

Applied


Add specific "render" endpoints

Hi,
In this PR, I propose the adding of 2 "render" endpoint to detect the following dynamic rendering engines:

Rendertron
Prerender

Information are based on this blog post.
Thanks a lot in advance 😃

Not sure what I feel using www.perdu.com as the site... Maybe say Google or Bing?

Good suggestion, I change it now 😃

It's changed to google address 😃

Is there a reason not to use example.com?

no, it is just to ensure that when the test on the url is made, the server (in case of internet access) will reach the target.

Thank you!

You are welcome :)


Dataset Preparation

If I wants to prepare a new dataset for LBA task, what should I do to deal with my data?
I prepared protein pdb files with corresponding ligand sdf files for this task.
And I see atom3d/atom3d/datasets/lba/process_pdbbind.py that generate three files of format (sdf, cif, cif). But in prepare_lmdb.py need file with formats: (sdf, pdb, pdb) correspondingly.
In my kind of view, I should first transform my dataset to generate (ligand, pocket, protein) fileset with process_pdbbind.py and then use prepare_lmdb.py to generate final hdf5 file for further loading by LMDBDataset. But it's clearly that now I cannot do in that way.
There also exists multiple scripts like create_hdf5.py that seems to be another way to generate hdf5 lmdb file.
So HOW should I do in depth to prepare?
I'm feeling super confusing on preparing new dataset and doing specific task with atom3d.

Hi, thank you for your interest! With version 0.2.0, we have refactored all the datasets from HDF5 format to LMDB format. Please see the links on the website at https://www.atom3d.ai/lba.html to download the processed datasets. For documentation on working with the LMDB datasets, please see https://atom3d.readthedocs.io/en/latest/.

I was trying to make a lmdb file from an xyz file, but I keep receiving this error:
File "$DIR/python3.7/site-packages/Bio/PDB/Atom.py", line 96, in init
assert not element or element == element.upper(), element
AssertionError: Si
But I assume that Si is a proper atom. How can I fix this issue?


[Linux] terminal does not open

From dev tools console, here is the error:
  ERR ioctl(2) failed.: Error: ioctl(2) failed.
    at UnixTerminal.resize (/usr/share/code/resources/app/node_modules.asar/node-pty/lib/unixTerminal.js:213:13)
    at e.resize (file:///usr/share/code/resources/app/out/vs/workbench/workbench.main.js:2917:541)
    at e.setDimensions (file:///usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3494:241)
    at file:///usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3656:385
    at <anonymous>

Version: 1.30.1
Commit: dea8705087adb1b5e5ae1d9123278e178656186a
Date: 2018-12-18T18:07:32.870Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Linux x64 4.15.0-42-generic

Steps to Reproduce:

Terminal > New Terminal

Does this issue occur when all extensions are disabled?: Yes

If it helps, my default shell is zsh

Some questions:

Can you share your settings.json?
Does the terminal flash when it opens?
Is that the only error in the console?

@Tyriar

settings.json
// Place your settings in this file to overwrite the default settings
{
    "files.autoSave": "afterDelay",
    "workbench.statusBar.visible": true,
    "editor.wrappingIndent": "indent",
    "python.formatting.provider": "yapf",
    "editor.wordWrap": "bounded",
    "editor.wordWrapColumn": 120,
    "editor.rulers": [
        80,
        100
    ],
    "workbench.iconTheme": "material-icon-theme",
    "editor.multiCursorModifier": "ctrlCmd",
    "editor.snippetSuggestions": "top",
    "editor.formatOnPaste": true,
    "telemetry.enableTelemetry": false,
    "files.exclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/CVS": true,
        "**/.DS_Store": true,
        "**/*.pyc": true,
        ".idea/": true
    },
    "diffEditor.ignoreTrimWhitespace": true,
    "explorer.confirmDelete": false,
    "update.channel": "none",
    "reason.codelens.enabled": true,
    "files.insertFinalNewline": true,
    "files.trimFinalNewlines": true,
    "files.trimTrailingWhitespace": true,
    "editor.minimap.enabled": false,
    "breadcrumbs.enabled": false,
    "editor.renderWhitespace": "none",
    "editor.mouseWheelZoom": true,
    "editor.fontSize": 15,
    "editor.suggestSelection": "recentlyUsed",
    "editor.quickSuggestionsDelay": 50,
    "workbench.colorTheme": "One Dark Pro Vivid",
    "explorer.confirmDragAndDrop": false
}

Does the terminal flash when it opens?
Yes terminal does flash briefly as if attempting to run the initial user config stuff like my .zshrc and whatever else zsh might need to start
Is that the only error in the console?
Also yes, that is the only error in the console.

I decided to change the default integrated shell which is ran when I open the terminal. I changed the shell to /bin/bash, and now the terminal opens and actually loads. However, I am still getting that error in the developer console.

From this new shell, I tried manually running /bin/zsh, and nothing happened - the process simply exited. So I decided to trace the command using strace, and here is a file containing the output.

Hi,
any news/solutions/workaround on this problem ? I've the same error, and can't execute my python Tasks anymore :(
[2019-05-17 13:42:27.393] [renderer1] [error] ioctl(2) failed.: Error: ioctl(2) failed.
    at UnixTerminal.resize (/mnt/disk/applications/code/resources/app/node_modules.asar/node-pty/lib/unixTerminal.js:216:13)
    at d.resize (file:///mnt/disk/applications/code/resources/app/out/vs/workbench/workbench.main.js:2684:270)
    at C.setDimensions (file:///mnt/disk/applications/code/resources/app/out/vs/workbench/workbench.main.js:3819:56)
    at _processManager._processManager.ptyProcessReady.then (file:///mnt/disk/applications/code/resources/app/out/vs/workbench/workbench.main.js:3666:840)

My infos:
Version: 1.34.0
Commit: a622c65b2c713c890fcf4fbf07cf34049d5fe758
Date: 2019-05-15T21:55:35.507Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 5.0.10-200.fc29.x86_64

Hi @smac89 !
did you find a workaround about this issue ? if yes please let me know how ;)
Thanks!

After https://github.com/microsoft/vscode/pull/73597 gets merged the Insiders build will log the reason ioctl failed which should help here.

@maty974 It's been a while since I posted this issue. I am now using VSCodium on Arch Linux and this problem is no longer present.
I was initially using the official VSCode and was running Ubuntu

Hi @Tyriar , I will post more log when this build will be ready thanks!

@smac89 , I've tested VScodium but got the same error :(
And finally I've found what was causing the issue! I was using LD_LIBRARY_PATH that was set to a custom lib path in my tasks.json for running Python code, and it seems that one or more lib was interferring with system one.
Removed this LD_LIBRARY_PATH fixed the bug.....
@Tyriar, I don't know if this will help in the #73597
Anyway thanks for your help guys

Closing as logging is improved which should help diagnose future issues.


Alertmanager: Change timestamp label to .StartsAt

notification-controller posted all outgoing Alertmanager alerts with "timestamp" label, effectively preventing grouping alerts related to the same resource and forcing users to configure a separate alert receiver with send_resolved: false.
This changes it to instead set "startsAt", which was previously set (automatically by Alertmanager) to alert posting time. "endsAt" remains unset, as we have no way of figuring that out but the reconciliation interval of the resource that generated the alert, which can currently only be found out by making a Kubernetes API round-trip.
Note that this requires users to adapt alert templates that relied on .Labels.Timestamp.
Fixes #793.

@stefanprodan sorry for taking a while to update this. I've expanded the docs on this.
While we're at it, I also updated fmt.Stringer / json.Marshaler implementations of AlertManagerTime to use value receiver types instead of pointers, because this is what Go stdlib docs tell us to do:

Programs using times should typically store and pass them as values, not pointers. That is, time variables and struct fields should be of type time.Time, not *time.Time.


Osbuild-composer job fail inside container

I tried running osbuild-composer inside a privileged container with all capabilities and the job fails without further explanation.
This is the Dockerfile I use:
FROM docker.io/library/fedora:31

RUN dnf install -y osbuild-composer osbuild composer-cli cockpit-composer && \
    systemctl enable osbuild-composer.socket

EXPOSE 9090

CMD [ "/sbin/init" ]

To build it, I go to the directory with the Dockerfile and run podman build -t osbuild .
This is how I run the container then:
podman run --name osbuild --rm --privileged --cap-add=ALL -it -v /dev:/dev -v /lib/modules:/lib/modules osbuild

and then I exec into it using podman exec -it osbuild /bin/bash
Inside I start osbuild-compsoer systemctl start osbuild-composer.socket create a simple blueprint using an example from weldr.io
name = "base"
description = "A base system with bash"
version = "0.0.1"

[[packages]]
name = "bash"
version = "*"

I upload the BP and run composer-cli compose start base ext4-filesystem
When looking at the journal this is what I see:
Mar 09 15:12:04 b38bdc772def osbuild-worker[62]: Running job 86446c72-f62a-46ef-8bb4-e565c530e677
Mar 09 15:12:04 b38bdc772def systemd[1]: Started Container osbuild-buildroot-r5jpdn5n.
Mar 09 15:13:12 b38bdc772def systemd[1]: osbuild-buildroot-r5jpdn5n.scope: Succeeded.
Mar 09 15:13:12 b38bdc772def systemd[1]: osbuild-buildroot-r5jpdn5n.scope: Consumed 38.156s CPU time.
Mar 09 15:13:15 b38bdc772def systemd[1]: Started Container osbuild-buildroot-o320dxud.
Mar 09 15:14:36 b38bdc772def systemd[1]: osbuild-buildroot-o320dxud.scope: Succeeded.
Mar 09 15:14:36 b38bdc772def systemd[1]: osbuild-buildroot-o320dxud.scope: Consumed 1min 607ms CPU time.
Mar 09 15:14:36 b38bdc772def systemd[1]: Started Container osbuild-buildroot-5bcr1u.
Mar 09 15:14:37 b38bdc772def systemd[1]: osbuild-buildroot-5bcr1u.scope: Succeeded.
Mar 09 15:14:37 b38bdc772def systemd[1]: Started Container osbuild-buildroot-pvjyaj6t.
Mar 09 15:14:37 b38bdc772def systemd[1]: osbuild-buildroot-pvjyaj6t.scope: Succeeded.
Mar 09 15:14:38 b38bdc772def systemd[1]: Started Container osbuild-buildroot-89f82iyp.
Mar 09 15:14:38 b38bdc772def systemd[1]: osbuild-buildroot-89f82iyp.scope: Succeeded.
Mar 09 15:14:38 b38bdc772def systemd[1]: Started Container osbuild-buildroot-3ipqvpxt.
Mar 09 15:14:39 b38bdc772def systemd[1]: osbuild-buildroot-3ipqvpxt.scope: Succeeded.
Mar 09 15:14:40 b38bdc772def osbuild-worker[62]: 2020/03/09 15:14:40   Job failed: exit status 1
Mar 09 15:14:40 b38bdc772def osbuild-worker[62]: Waiting for a new job...

If I compare that to a log where it's running on a VM it fails just before the end:
The log from a VM:
Mar 09 12:33:53 localhost.localdomain osbuild-worker[8812]: Waiting for a new job...
Mar 09 12:35:53 localhost.localdomain osbuild-worker[8812]: Running job 9d8255f4-cb4f-4ac5-b551-d12ce6177e7f
Mar 09 12:35:53 localhost.localdomain systemd[1]: Started Container osbuild-buildroot-0v4fbd2p.
Mar 09 12:36:57 localhost.localdomain systemd[1]: osbuild-buildroot-0v4fbd2p.scope: Succeeded.
Mar 09 12:36:57 localhost.localdomain systemd[1]: osbuild-buildroot-0v4fbd2p.scope: Consumed 36.318s CPU time.
Mar 09 12:37:00 localhost.localdomain systemd[1]: Started Container osbuild-buildroot-0v8ie3m6.
Mar 09 12:38:15 localhost.localdomain systemd[1]: osbuild-buildroot-0v8ie3m6.scope: Succeeded.
Mar 09 12:38:15 localhost.localdomain systemd[1]: osbuild-buildroot-0v8ie3m6.scope: Consumed 55.880s CPU time.
Mar 09 12:38:15 localhost.localdomain systemd[1]: Started Container osbuild-buildroot-5ntg37sh.
Mar 09 12:38:16 localhost.localdomain systemd[1]: osbuild-buildroot-5ntg37sh.scope: Succeeded.
Mar 09 12:38:16 localhost.localdomain systemd[1]: Started Container osbuild-buildroot-wagyo1py.
Mar 09 12:38:16 localhost.localdomain systemd[1]: osbuild-buildroot-wagyo1py.scope: Succeeded.
Mar 09 12:38:16 localhost.localdomain systemd[1]: Started Container osbuild-buildroot-uay2lrzl.
Mar 09 12:38:17 localhost.localdomain systemd[1]: osbuild-buildroot-uay2lrzl.scope: Succeeded.
Mar 09 12:38:17 localhost.localdomain systemd[1]: Started Container osbuild-buildroot-1zcrd9e9.
Mar 09 12:38:24 localhost.localdomain systemd[1]: osbuild-buildroot-1zcrd9e9.scope: Succeeded.
Mar 09 12:38:24 localhost.localdomain systemd[1]: osbuild-buildroot-1zcrd9e9.scope: Consumed 6.948s CPU time.
Mar 09 12:38:27 localhost.localdomain systemd[1]: Started Container osbuild-buildroot-ldlganyd.
Mar 09 12:38:27 localhost.localdomain kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Mar 09 12:38:31 localhost.localdomain systemd[1]: osbuild-buildroot-ldlganyd.scope: Succeeded.
Mar 09 12:38:31 localhost.localdomain systemd[1]: osbuild-buildroot-ldlganyd.scope: Consumed 2.965s CPU time.
Mar 09 12:38:43 localhost.localdomain osbuild-worker[8812]: Waiting for a new job...

Looking at /var/lib/osbuild-composer/outputs/$UUID/0/result.json I see this at the end:
      "name": "org.osbuild.selinux",
      "options": {
        "file_contexts": "etc/selinux/targeted/contexts/files/file_contexts"
      },
      "success": false,
      "output": "[/usr/lib/tmpfiles.d/journal-nocow.conf:26] Failed to resolve specifier: uninitialized /etc detected, skipping\nAll rules containing unresolvable specifiers will be skipped.\nsetfiles: Could not set context for /run/osbuild/tree:  Operation not supported\nTraceback (most recent call last):\n  File \"/run/osbuild/lib/stages/org.osbuild.selinux\", line 43, in <module>\n    r = main(args[\"tree\"], args[\"options\"])\n  File \"/run/osbuild/lib/stages/org.osbuild.selinux\", line 39, in main\n    subprocess.run([\"setfiles\", \"-F\", \"-r\", f\"{tree}\", f\"{file_contexts}\", f\"{tree}\"], check=True)\n  File \"/usr/lib64/python3.7/subprocess.py\", line 487, in run\n    output=stdout, stderr=stderr)\nsubprocess.CalledProcessError: Command '['setfiles', '-F', '-r', '/run/osbuild/tree', '/run/osbuild/tree/etc/selinux/targeted/contexts/files/file_contexts', '/run/osbuild/tree']' returned non-zero exit status 255.\n"
    }
  ],
  "assembler": null,
  "success": false
}

I can see a selinux fail, but I don't know what that means. Can anyone tell me what seems to be the problem or where else to look?

podman run --name osbuild --rm --privileged --cap-add=ALL -it -v /dev:/dev -v /lib/modules:/lib/modules osbuild

Note that giving a container access to /dev defeats the point of using containers, because it now has access to all of the host's hardware. It is fine to use during development, but I wouldn't want to suggest in any way that this is an acceptable way to run it in production. (This is only for osbuild-worker. osbuild-composer can be run inside a container.)
Sorry, I don't know what could be causing the selinux error you're seeing :(

Note that giving a container access to /dev defeats the point of using containers, because it now has access to all of the host's hardware. It is fine to use during development, but I wouldn't want to suggest in any way that this is an acceptable way to run it in production.

I agree, my ultimate goal was to limit the access the container has to the host system as much as possible and see if I could get to an acceptable state. This is just a test to see if it's even possible to run the osbuild-worker inside container in any way :)

As @ondrejbudai mentioned, this is most likely caused by missing xattr support in overlayfs, which is used in the containers. You may make this work by mounting /var/tmp and possibly other filesystem from the host to give non-overlayfs-backed filesystems for us to use. This is a useful exercise in order to find out exactly what is required by osbuild-worker, but most likely it will not be all that useful to test it in this way, as it will be significantly different from the setup we'd use in production.

As @ondrejbudai mentioned, this is most likely caused by missing xattr support in overlayfs, which is used in the containers.
Yes that helped, thank you @ondrejbudai . I got a finished build when I create a /var/tmp/shared_tmp and mount it. The final command looks like this:

podman run --name osbuild --rm --privileged --cap-add=ALL -it -v /dev:/dev -v /lib/modules:/lib/modules -v  /var/tmp/shared_tmp:/var/tmp osbuild

I will now try to remove as many of the privileges as possible.

It's cool to see that osbuild actually can be run in a container. However, I would like to stress what was needed to achieve it:

privileged container
all capabilities
shared /dev
extra-mounted /var/tmp to overcome limitations of podman and overlayfs (I don't know the exact reason why xattrs don't work in this setup)

This has two big implications:

The container has full access to the host machine and therefore it's not safe as one might expect.
The setup is really weird and does not reflect how we recommend to use the software (bare metal/VM without any kind of containerization). Therefore, it might have unexpected issues.

My recommendation
Do not run osbuild in a container. The software was not designed to be able to run inside a container and it might break in unexpected ways.
However, it should be totally possible to run osbuild-composer in a container. Keep in mind that you must disable the local worker in this setup and run a remote one on a VM/bare metal.
Closing remarks
I would like to thank you, @jrusz, for your contribution to the container debate. It's surely very beneficial and interesting to see what is required to get osbuild running in a container.
Let's have this issue open for now for anyone who wants to contribute to the discussion.

@jrusz @ondrejbudai thanks for working through this! I agree with Ondrej's conclusion, but nevertheless, this is very useful to know!

Thanks for this effort!
If we could get a list of specific features we need from the kernel, overlayfs, podman etc. that would be really great because we would have a starting point for a discussion with upstream communities of these projects. Or rather a starting point for our own investigation before we contact others.
So far I can see:

support for xattr in podman containers
loopback devices independent of the whole /dev

But I'd nice to investigate which capabilities are needed.

FTR, in our discussions with the kernel developers it became clear that independent/namespaced /dev would be quite a major undertaking (even just the loopback part), and there was not full buyin from all the relevant maintainers that this is something we want at all. So we shouldn't hold our breaths for that.

I have some update. I got it working without privileged container running this:
podman run --name osbuild --rm -it --device=/dev/loop0:/dev/loop0 --device=/dev/loop-control:/dev/loop-control --device=/root/fakedev/tun:/dev/net/tun -v /root/tmp:/var/tmp --cap-add=SYS_ADMIN --cap-add=NET_ADMIN --cap-add=AUDIT_CONTROL osbuild

I created the /dev/net/tun using mknod on the host device. I tried the same for loop-control and loop0 but that didn't work right away for some reason. Also I need setenforce 0 on the host machine and it's being run as root user.
I think that it will have to be run under root user because osbuild-worker is running as root anyway, but I believe we can limit what the container can and can't do quite a bit.

Thanks for the update!
What's your plan going forward? As mentioned earlier, I think this is interesting information to have, but for actual testing I don't think it makes sense to use containers, even if they work (too different from real system).
We don't have a good story yet though, but we should work on making it easier to test in VMs.

for actual testing I don't think it makes sense to use containers, even if they work (too different from real system).

So even if it runs in a container that has access limited to the loop devices in /dev and some acceptable privileges you still think it won't be of any use? I thought that the current issue is that the container was privileged and it was not safe to run.
My plan was to limit this as much as possible and then ask on podman mailing list what problems can it cause on the host system, if any and then ask you here if it could be used for testing as a faster alternative to VMs. But if you believe it's too different from running in a VM then I guess there's no point in continuing in this effort.

There are some quite fundamental issues with this, so I would not recommend going down this route.
The problem is that we are allocating loop devices dynamically, from a shared namespace. If you have no other users of the loopback namespace when you run your test, then we will end up using /dev/loop0, so your setup will work. However, if someone else is already using /dev/loop0, we will end up with /dev/loop1 (or something else), so you need to pass the right one in to the container.
The only way to make this reliable if you can somehow guarantee that nobody else on the system will be using loopback devices while your tests are running, and that you only ever run one test at once. The reason is that even if you pass in /dev/loop0 and nobody is using it at the time, you are not able to reserve it, so somebody else might come and grab it before you get to the point in the tests where we try to actually use it (and we would then fail).
It might be fine to make such assumptions on your local machine just to try things out quickly, but we should have a more reliably recommended way of running our tests.

I guess it's fine to use a container for developing automated tests. If there are some issues with them in the container, it will be caught by the CI, which will run the tests on a proper VM. However, I think the official repository shouldn't mention this option because it isn't the recommended nor supported way of running osbuild due to all the issues mentioned here.
For doing anything else in the container apart from developing automated tests: If an error occurs, there's always a question: Is it caused by a bug or is it caused by the environment for which osbuild was not designed? Personally, I would very much dislike the uncertainty.
I appreciate all your work, it gave us very interesting results which may be very useful for us at some point (honestly, why the hell do you need root to build an image? Fundamentally, it's just copying of bits to the right places...). However, for now, we cannot recommend/support running osbuild in a container because of all the limitations. :slightly_frowning_face:

I guess there's not much else to say here, I understand that osbuild is intended to be used in a VM and not in container and that this is not the way to go even if it kinda works.


DOC-7380: Remove some tech debt around remote include branch names

Fixes DOC-7380

Sorry for the late review, I missed this somehow. LGTM


Fixed #31982 -- Made HttpResponse.set_cookie() cast max_age argument to an integer.

https://code.djangoproject.com/ticket/31982

@hramezani Thanks :+1:
I pushed minor edits to tests.


[BUG]  加载chatglm模型报错：'NoneType' object has no attribute 'message_types_by_name'

问题描述 / Problem Description
加载chatglm模型报错：'NoneType' object has no attribute 'message_types_by_name'，导致加载模型失败
复现问题的步骤 / Steps to Reproduce
执行 python webui.py或重新加载模型时报错（见最后一行）：
Explicitly passing a revision is encouraged when loading a model with custom code to ensure no malicious code has been contributed in a newer revision.
Explicitly passing a revision is encouraged when loading a configuration with custom code to ensure no malicious code has been contributed in a newer revision.
Explicitly passing a revision is encouraged when loading a model with custom code to ensure no malicious code has been contributed in a newer revision.
Downloading (…)/modeling_chatglm.py: 100%|███████████████████████████████████████████████████| 59.4k/59.4k [00:00<00:00, 493kB/s]
Downloading (…)main/quantization.py: 100%|███████████████████████████████████████████████████| 31.0k/31.0k [00:00<00:00, 215kB/s]
ERROR 2023-05-17 18:34:56,154-1d: 'NoneType' object has no attribute 'message_types_by_name'
环境信息 / Environment Information

langchain-ChatGLM 版本/commit 号：commit a5417e1
是否使用 Docker 部署（是/否）：否
使用的模型（ChatGLM-6B / ClueAI/ChatYuan-large-v2 等）：ChatGLM-6B（v1.1.0或v0.1.0都报错）
使用的 Embedding 模型（GanymedeNil/text2vec-large-chinese 等）：任何
操作系统及版本 / Operating system and version: Ubuntu Linux 18_04 LTS
Python 版本 / Python version: 3.10.9
其他相关环境信息 / Other relevant environment information: CUDA

same problem here, fixed by update protobuf to 3.19.6
Traceback (most recent call last):
File "/mnt/workspace/langchain-ChatGLM/webui.py", line 7, in
from transformers.modeling_utils import PreTrainedModel
File "/usr/local/lib/python3.10/dist-packages/transformers/modeling_utils.py", line 83, in
from accelerate import version as accelerate_version
File "/usr/local/lib/python3.10/dist-packages/accelerate/init.py", line 3, in
from .accelerator import Accelerator
File "/usr/local/lib/python3.10/dist-packages/accelerate/accelerator.py", line 37, in
from .tracking import LOGGER_TYPE_TO_CLASS, GeneralTracker, filter_trackers
File "/usr/local/lib/python3.10/dist-packages/accelerate/tracking.py", line 42, in
from torch.utils import tensorboard
File "/usr/local/lib/python3.10/dist-packages/torch/utils/tensorboard/init.py", line 12, in
from .writer import FileWriter, SummaryWriter  # noqa: F401
File "/usr/local/lib/python3.10/dist-packages/torch/utils/tensorboard/writer.py", line 9, in
from tensorboard.compat.proto.event_pb2 import SessionLog
File "/usr/local/lib/python3.10/dist-packages/tensorboard/compat/proto/event_pb2.py", line 16, in
from tensorboard.compat.proto import summary_pb2 as tensorboard_dot_compat_dot_proto_dot_summary__pb2
File "/usr/local/lib/python3.10/dist-packages/tensorboard/compat/proto/summary_pb2.py", line 16, in
from tensorboard.compat.proto import histogram_pb2 as tensorboard_dot_compat_dot_proto_dot_histogram__pb2
File "/usr/local/lib/python3.10/dist-packages/tensorboard/compat/proto/histogram_pb2.py", line 21, in
_HISTOGRAMPROTO = DESCRIPTOR.message_types_by_name['HistogramProto']
AttributeError: 'NoneType' object has no attribute 'message_types_by_name'

dude, you are so nice! thats works for me, thank you

+1

Thanks, it works for me.

更新protobuf版本解决问题
pip install --upgrade protobuf==3.19.6