"Undefined symbols for architecture x86_64" in Xcode 10

HI,
I'm testing an app that uses TPInAPPReceipt for MacOS with Xcode 10 beta, and getting an error "Undefined symbols for architecture x86_64", referencing TPInAPPReceipt when archiving my app, that I doesn't happen when running with a Debug configuration.
I've check Build Settings without finding anything to justify this error. Do you have any ideas?
Thanks

Found the problem and made a pull request.


Apollo 5.0: How to extract PCD files from a cyber record file?

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04): Ubuntu 16.04
Apollo installed from (source or binary): docker
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0): 5.0

Supporting materials (screenshots, command lines, code/script snippets):
I'm not quite sure how to extract binary PCD files from cyber record files with a lidar channel such as /apollo/sensor/lidar128/compensator/PointCloud2.
When searching the codebase, I found modules/localization/msf/local_tool/data_extraction/cyber_record_parser but this seems to give me the same error for any input I give it:

Another tool I found modules/perception/lidar/tools/exporter/msg_exporter requires some kind of config file of which I'm unsure of.
Any suggestions would be appreciated.

I just revisited the problem and noticed that
/apollo/bazel-bin/modules/localization/msf/local_tool/data_extraction/cyber_record_parser actually reads the arguments correctly, when all necessary arguments have been specified.
I now ran into my next problem as when I run the cyber_record_parser with my cyber record in the following way:
/apollo/bazel-bin/modules/localization/msf/local_tool/data_extraction/cyber_record_parser \
--bag_file /apollo/data/bag/newrecording/new_recording.record.00000 \
--out_folder /apollo/data/bag/output/ \
--cloud_topic /apollo/sensor/lidar128/compensator/PointCloud2

I get the following error message:
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1115 12:20:36.407627 24877 pcd_exporter.cc:44] []Compensated pcd callback.
[libprotobuf FATAL external/com_google_protobuf/src/google/protobuf/repeated_field.h:1482] CHECK failed: (index) < (current_size_):
terminate called after throwing an instance of 'google::protobuf::FatalException'
  what():  CHECK failed: (index) < (current_size_):
Aborted (core dumped)

Also, this is what cyber_recorder info outputs on my recording:
record_file:    ./data/bag/newrecording/new_recording.record.00000
version:        1.0
duration:       60.106406 Seconds
begin_time:     2019-10-11 17:28:15
end_time:       2019-10-11 17:29:15
size:           106389436 Bytes (101.460876 MB)
is_complete:    true
message_number: 602
channel_number: 1
channel_info:
                /apollo/sensor/lidar128/compensator/PointCloud2        602 messages: apollo.drivers.PointCloud

Here is the backtrace on the core using GDB:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/apollo/bazel-bin/modules/localization/msf/local_tool/data_extraction/cyber_rec'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007f14d345fc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56	../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x00007f14d345fc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007f14d3463028 in __GI_abort () at abort.c:89
#2  0x00007f14d3a68535 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007f14d3a666d6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007f14d3a66703 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007f14d3a66922 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007f14dda087f3 in google::protobuf::internal::LogMessage::Finish() ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libexternal_Scom_Ugoogle_Uprotobuf_Slibprotobuf_Ulite.so
#7  0x00007f14dda0882e in google::protobuf::internal::LogFinisher::operator=(google::protobuf::internal::LogMessage&) ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libexternal_Scom_Ugoogle_Uprotobuf_Slibprotobuf_Ulite.so
#8  0x00007f14ef323ef5 in google::protobuf::RepeatedPtrField<apollo::drivers::PointXYZIT>::TypeHandler::Type const& google::protobuf::internal::RepeatedPtrFieldBase::Get<google::protobuf::RepeatedPtrField<apollo::drivers::PointXYZIT>::TypeHandler>(int) const ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libmodules_Slocalization_Smsf_Slocal_Utool_Sdata_Uextraction_Slibdata_Uextraction.so
#9  0x00007f14ef322ff6 in google::protobuf::RepeatedPtrField<apollo::drivers::PointXYZIT>::Get(int) const ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libmodules_Slocalization_Smsf_Slocal_Utool_Sdata_Uextraction_Slibdata_Uextraction.so
#10 0x00007f14ef321e14 in apollo::drivers::PointCloud::point(int) const ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libmodules_Slocalization_Smsf_Slocal_Utool_Sdata_Uextraction_Slibdata_Uextraction.so
#11 0x00007f14ef3217f2 in apollo::localization::msf::PCDExporter::WritePcdFile(std::string const&, apollo::drivers::PointCloud const&) ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libmodules_Slocalization_Smsf_Slocal_Utool_Sdata_Uextraction_Slibdata_Uextraction.so
#12 0x00007f14ef321566 in apollo::localization::msf::PCDExporter::CompensatedPcdCallback(std::string const&) ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libmodules_Slocalization_Smsf_Slocal_Utool_Sdata_Uextraction_Slibdata_Uextraction.so
#13 0x000000000040f73a in main::{lambda(std::string const&)#1}::operator()(std::string const&) const ()
#14 0x0000000000410dfd in std::_Function_handler<void (std::string const&), main::{lambda(std::string const&)#1}>::_M_invoke(std::_Any_data const&, std::string const&) ()
#15 0x00007f14ef31cd27 in std::function<void (std::string const&)>::operator()(std::string const&) const ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libmodules_Slocalization_Smsf_Slocal_Utool_Sdata_Uextraction_Slibdata_Uextraction.so
#16 0x00007f14ef31b5a1 in apollo::localization::msf::CyberRecordReader::Read(std::string const&) ()
   from /home/user/.cache/bazel/_bazel_user/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-fastbuild/bin/modules/localization/msf/local_tool/data_extraction/../../../../../_solib_k8libmodules_Slocalization_Smsf_Slocal_Utool_Sdata_Uextraction_Slibdata_Uextraction.so
#17 0x00000000004104a4 in main ()

The function WritePcdFile uses the width/height or point size of the input message to calculate the point size of output cloud. Please help to check that they are set accurately.

After encountering the error a year ago, I found this issue was caused by LGSVL publishing pointcloud messages with width: 11520 and height:1, which was more than the actual number of points in the message (7670).
A workaround for this problem was also provided here: https://github.com/ApolloAuto/apollo/issues/11936

Hello @javangent  What you have provided here is inspiring. I am also working on extracting PCD files from a record file, but I am now using Apollo 6.0 (master branch). And I noticed that some files are not in the same location you mentioned here when you used Apollo 5.0.
Can you take a look at it and give me some guidance on how to extract under Apollo 6.0?
Many thanks!

Hi @GabrielZZZ
It seems your command contains backslashes ( \ ) even though your command is entirely on a single line (no newlines). Try removing the backslashes, it should fix the issue.
You could also alternatively change \ --bag_file to \--bag_file, but the first option would make more sense.


ui: alignment of o11y pages with other pages

https://github.com/cockroachdb/cockroach/pull/70034 --- Release note (ui change): Updating ui of o11y pages to match remaning pages (e.g. spacing, colors, font sizes)

Closing - no docs needed


Merge turbo crate into cargo workspace

Merge the turbo crate into Cargo workspace; fix the turbo crate build/tests on Windows; upgrade the Cargo dependencies and cargo clippy --fix.
This pull request is a part of https://github.com/vercel/turbo/pull/2359. The original PR will continue to fix cargo tests in turbotrace.

renaming the shim seems to require a lot of configuration changes; I'll send a separate pr for it if needed.


can't scroll through search

searching for "int", you get more an a page worth of search results.
If you click on the scrollbar next to the search results, the popup showing the search results goes away.
If you click back in the search box, your criteria is still there, but now NO search results show.
No errors show on the console during this test.

Note: using the scroll wheel DOES scroll the search results correctly.

@coke this is a known problem with the search-bar js. @2colours has pointed it out several times.
We have several conversations about search-bar, and extended search.
There were issues with search-bar in the original site, @Altai-man tried to solve some, I have tried to solve some. The code relies on a jQuery catcomplete plugin, which has been highly leveraged.
There is also a search-bar issue related to the data it uses.

@Altai-man No, the change to autoComplete.js was not carried through.
I think that the patch was not applied because the Categories were not styled.
The autoComplete.js file was included as a static file, but it was never used in core.js.
I could not immediately see how to apply autoComplete.
My first priority was to get something working as in your working site (which used catComplete), but we need a new search protocol.
I'll open a new search-bar discussion to bring all these threads together.

@coke this is a known problem with the search-bar js. @2colours has pointed it out several times.

Need something in the system for it to be known, which now we have.

I've opened a general discussion, so closing this issue

Please link to the discussion.

https://github.com/Raku/doc-website/discussions/127


Display local tax at step 1 of checkout

When purchasing a product tier item in an OCNZ hosted Collective, GST is applied. However, it is not displayed on step one and only appears on step three. This is misleading as it first shows the payment amount of $30 when it will really be $34.50.

Taxes are surfaced on step 3 because, for VAT, they depend on the contributing profile (whether it's an individual or an organization, where it's located, etc). We could do a simple exception for GST and guess the amount a bit earlier since it does not have such dependencies.

Maybe on step 1 it should just say the amount "+GST" or "+VAT" so it's
clear that will be added later?


Add support for fixed interval refill

In opposite to smooth refill which adds token as soon as possible, interval refill should regenerate tokens periodically.
Proposed API:
public static Refill fixedInterval(long tokens, Duration period) {
    // ...
}

public static Refill fixedInterval(Instant timeOfFirstRefill, long tokens, Duration period) {
     // ...
}

When this feature will be available?

Most likely in January 2018

I need this feature soon, can you try for oct end?

Yes, I can try, please hire me via upwork. I am agree to fixed price project 1000 US dollars.

@vtahlani do you still need in this feature?

Yes.
On Wed, Mar 28, 2018, 2:36 AM Vladimir Bukhtoyarov<EMAIL_ADDRESS>wrote:

@vtahlani https://github.com/vtahlani do you still need in this feature?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vladimir-bukhtoyarov/bucket4j/issues/39#issuecomment-376675432,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMtxyCp4kA9d2xQPXtwzrvrInEjOWqNaks5tiqnUgaJpZM4OCsV2
.

@vtahlani  I have a little time frame to implement new release 3.2, #12 and #65 already implemented, you have the good chance that "fixed interval refill" will be included to 3.2, to achieve this you need to describe how do you plan to use this feature from business point of view. In other words I expect the descriptions of use-cases, which can be added to javadocs and wiki-pages.

Also as tokens get refilled in milliseconds then in a minute I would be serving more request than my limit.

This is because the token-bucket allows local burst by design. You can not avoid the burst, independently of smoot or interval refill style. For example:

Having 100 tokens per minute limit.
You decided to refresh limit each 1 minute.
In time 1 second before refreash bucket is full. User acquires all 100 token within this second. So bucket is empty.
After second, bucket is full again because of interval refill.
User come again and consume a next 100 tokens for next second.
In conclusion user consumed 200 tokens for 2 seconds.
Redefine contract as 50 tokens per 30 second, would be single possible way to provide guarantee that user will be unable to consume more then 100 tokens per 1 minute, and stay in same time in token-bucket model which takes minimal memory footprint and does not store each event independently from each other.
Also

I also faced another challenge what should be the value for X-RateLimit-Reset when should i say it would be rest.

It is interesting option, thanks for pointing out. I will add support for this for this option to the method tryConsumeAndReturnRemaining, it will work for both, smooth and interval refill.

The proposed API to specifying interval refill:
// 1000 tokens per minute, refill happens with one second interval
Bandwidth limit = Bandwidth.simple(1000, Duration.ofMinutes(1)).refilInterval(Duration.ofSecond(1))

Bucket bucket = Bucket4j.builder()
    .addBandwith(limit)
    .build();

I am not sure that refilInterval is best  name for method(resilience4j uses limitRefreshPeriod), feel free to propose more suitable.

will be released soon

@vtahlani I have created dedicated issue #68 for X-RateLimit-Reset header

if i change duration to one minute then refill would happen after one minute, right?

right

Now in every one minute i would be able to consume only 1000 toke, right?

In general case no, see my previous comment that describes the burst.

released https://github.com/vladimir-bukhtoyarov/bucket4j/releases/tag/4.0.0


Test grpc 1.64.0

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

2.671     The user requested protobuf==5.26.1
2.671     grpcio-status 1.64.0 depends on protobuf<6.0dev and >=5.26.1
2.671     googleapis-common-protos 1.56.4 depends on protobuf<5.0.0dev and >=3.15.0

But the lasted released googleapis-common-protos still require protobuf <5.0.0.dev0.
https://github.com/googleapis/python-api-common-protos/blob/v1.63.0/setup.py

grpcio-status 1.63.0 depends on protobuf<6.0dev and >=5.26.1

1.63.0 also need protobuf >=5.26.1, so we can't upgrade grpc now, close this one


初始化数据报错

QUANTAXIS> save all
QUANTAXIS>> Selecting the Best Server IP of TDX
USING DEFAULT STOCK IP
USING DEFAULT FUTURE IP
QUANTAXIS>> === The BEST SERVER ===
stock_ip <IP_ADDRESS> future_ip <IP_ADDRESS>
Traceback (most recent call last):
File "/opt/conda/bin/quantaxis", line 8, in
sys.exit(QA_cmd())
File "/opt/conda/lib/python3.8/site-packages/QUANTAXIS/QACmd/init.py", line 686, in QA_cmd
cli.cmdloop()
File "/opt/conda/lib/python3.8/cmd.py", line 138, in cmdloop
stop = self.onecmd(line)
File "/opt/conda/lib/python3.8/cmd.py", line 217, in onecmd
return func(arg)
File "/opt/conda/lib/python3.8/site-packages/QUANTAXIS/QACmd/init.py", line 350, in do_save
QA_SU_save_stock_day('tdx')
File "/opt/conda/lib/python3.8/site-packages/QUANTAXIS/QAUtil/init.py", line 169, in wrapper
func(*args, **kwargs)
File "/opt/conda/lib/python3.8/site-packages/QUANTAXIS/QASU/main.py", line 222, in QA_SU_save_stock_day
engine.QA_SU_save_stock_day(client=client)
File "/opt/conda/lib/python3.8/site-packages/QUANTAXIS/QASU/save_tdx.py", line 196, in QA_SU_save_stock_day
stock_list = QA_fetch_get_stock_list().code.unique().tolist()
File "/opt/conda/lib/python3.8/site-packages/retrying.py", line 49, in wrapped_f
return Retrying(*dargs, **dkw).call(f, *args, **kw)
File "/opt/conda/lib/python3.8/site-packages/retrying.py", line 212, in call
raise attempt.get()
File "/opt/conda/lib/python3.8/site-packages/retrying.py", line 247, in get
six.reraise(self.value[0], self.value[1], self.value[2])
File "/opt/conda/lib/python3.8/site-packages/six.py", line 703, in reraise
raise value
File "/opt/conda/lib/python3.8/site-packages/retrying.py", line 200, in call
attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
File "/opt/conda/lib/python3.8/site-packages/QUANTAXIS/QAFetch/QATdx.py", line 724, in QA_fetch_get_stock_list
return pd.concat([sz, sh], sort=False).query(
File "/opt/conda/lib/python3.8/site-packages/pandas/core/frame.py", line 3699, in assign
data[k] = com.apply_if_callable(v, data)
File "/opt/conda/lib/python3.8/site-packages/pandas/core/frame.py", line 3044, in setitem
self._set_item(key, value)
File "/opt/conda/lib/python3.8/site-packages/pandas/core/frame.py", line 3120, in _set_item
value = self._sanitize_column(key, value)
File "/opt/conda/lib/python3.8/site-packages/pandas/core/frame.py", line 3745, in _sanitize_column
value = reindexer(value)
File "/opt/conda/lib/python3.8/site-packages/pandas/core/frame.py", line 3736, in reindexer
raise err
File "/opt/conda/lib/python3.8/site-packages/pandas/core/frame.py", line 3731, in reindexer
value = value.reindex(self.index)._values
File "/opt/conda/lib/python3.8/site-packages/pandas/core/series.py", line 4412, in reindex
return super().reindex(index=index, **kwargs)
File "/opt/conda/lib/python3.8/site-packages/pandas/core/generic.py", line 4463, in reindex
return self._reindex_axes(
File "/opt/conda/lib/python3.8/site-packages/pandas/core/generic.py", line 4478, in _reindex_axes
new_index, indexer = ax.reindex(
File "/opt/conda/lib/python3.8/site-packages/pandas/core/indexes/multi.py", line 2319, in reindex
raise ValueError("cannot handle a non-unique multi-index!")
ValueError: cannot handle a non-unique multi-index!

I'm encountering the same problem, someone has any ideas?

遇见同样的问题了 解决啦吗

解决了
Tushare内置的pytdx版本和QUANTAXIS使用的pytdx 版本不同, 请重新安装pytdx以解决此问题 pip uninstall pytdx pip install pytdx-1.72r2-py3-none-any.whl
在 2023-05-10 22:41:26，"tangul" @.***> 写道：
"cannot handle a non-unique multi-index!"
同样遇到这个问题，请问解决了吗
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


nodenext compatiblity

Checklist

[ ] run npm run test and npm run benchmark
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

@mcollina
@Eomm
@L2jLiga
@fox1t
@climba03003


Create scenarios (feature file and steps) for Cancel order

As a creator of this service
I need to create scenarios in the feature and steps files
So that I can perform BDD testing
Assumption

The UI already contains Cancel order functionality that can be tested

Acceptance Criteria

Given the scenarios for Cancel Order have been added
When I test Cancel Order functionality on UI
The test runs and passes

Hey team! Please add your planning poker estimate with Zenhub @even1111112 @PepperandSummer @un-poco @yjhsieh2022


[bug] How do I disable CSP

Describe the bug
I'm running windows.I need to manipulate the DOM of a different source iframe inside the html.
@https://github.com/tauri-apps/tauri-docs/issues/26
I'm using the scheme here.
{
  "tauri": {
    "windows": [
      {
        "fullscreen": false,
        "resizable": true,
        "title": "title",
        "width": 800,
        "height": 600,
        "additionalBrowserArgs": "--disable-web-security"
      }
    ]
  }
}

But the command line displays an error:
 failed to create webview: WebView2 error: WindowsError(Error { code: 0x8007139F, message: The state of the group or resource is not the correct state to perform the requested operation。 })
I know it's not safe.
But my scenario does require disabling CSP.
What should I do?
Reproduction
No response
Expected behavior
No response
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 124.0.2478.97
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.77.2 (25ef9e3d8 2024-04-09)
    ✔ cargo: 1.77.2 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.20.2
    - pnpm: 8.15.7
    - yarn: 1.22.22
    - npm: 10.5.0

[-] Packages
    - tauri [RUST]: 1.6.5
    - tauri-build [RUST]: 1.5.2
    - wry [RUST]: 0.24.9
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.5.5 (outdated, latest: 1.5.6)
    - @tauri-apps/cli [NPM]: 1.5.14

[-] App
    - build-type: bundle
    - CSP: default-src 'self'; img-src 'self' asset: https://asset.localhost;
    - distDir: ../dist
    - devPath: ../dist
    - framework: React
    - bundler: Vite

Stack trace
No response
Additional context
No response

https://tauri.app/v1/api/config/#securityconfig.csp


Update read_camtrap_dp() so it can read Camtrap DP 0.1.6 and 1.0-rc.1

For camtraptor v0.20 we envision read_camtrap_dp() to be able to read legacy Agouti exports (Camtrap DP 0.1.6) and new Agouti exports (Camtrap DP 1.0-rc.1) without affecting the other functions (i.e. non-breaking change).
To do this, read_camtrap_dp() should:

[x] Detect the version in package$profile
[ ] Ignore or deprecate the media flag (debatable)

The required changes are listed below.
profile

[x] contributor$role: author/maintainer are deprecated in 1.0-rc.1, some new roles are added. Ok to leave as is.
[x] organizations: deprecated in 1.0-rc.1. Ok if missing.
[x] project$animalTypes: deprecated in 1.0-rc.1. Ok if missing.
[x] project$individualAnimals: new in 1.0-rc.1. Ok to leave in.
[x] project$classificationLevel: renamed to observationLevel in 1.0-rc.1. Convert to old name.
[x] project$sequenceInterval: deprecated in 1.0-rc.1. Ok if missing.
[x] coordinatePrecision: new in 1.0-rc.1. Ok to leave in.
[x] taxonomic[x]$kingdom, etc: new in 1.0-rc.1. Ok to leave in.
[x] platform: deprecated in 1.0-rc.1. Look for first element in sources and assign title as platform$title
[x] rightsHolder: deprecated in 1.0-rc.1. Look for first contributor with role rightsHolder and assign title as rightsHolder
[x] relatedIdentifiers: new in 1.0-rc.1. Ok to leave in.
[x] references: new in 1.0-rc.1 (moved from project$references, but was never populated for Agouti). Ok to leave in.

$data$deployments

[x] deploymentID: same
[x] locationID: same
[x] locationName: same
[x] longitude: order switched
[x] latitude: order switched
[x] coordinateUncertainty: same
[x] start: rename from eventStart
[x] end: rename from eventEnd
[x] setupBy: same
[x] cameraID: same
[x] cameraModel: same
[x] cameraInterval: rename from cameraDelay
[x] cameraHeight: same
[x] cameraTilt: same
[x] cameraHeading: same
[x] detectionDistance: new, ignore
[x] timestampIssues: same
[x] baitUse: convert from boolean baitUse
[x] session: deprecated, leave empty
[x] array: deprecated, leave empty
[x] featureType: same
[x] habitat: same
[x] tags: rename from deploymentTags
[x] comments: rename from deploymentComments
[x] _id: deprecated, leave empty

$data$media

[x] mediaID: same
[x] deploymentID: same
[ ] sequenceID: deprecated, leave empty? Not sure if this will break things.
[x] captureMethod: same
[x] timestamp: same
[x] filePath: same
[x] filePublic: new term, ignore
[x] fileName: same
[x] fileMediatype: same
[x] exifData: same
[x] favourite: rename from favorite
[x] comments: rename from mediaComments
[x] _id: deprecated, leave empty

$data$observations

[x] Filter on observationLevel = event
[x] observationID: same
[x] deploymentID: same
[x] sequenceID: rename from eventID
[x] mediaID: same
[x] timestamp: rename from eventStart
[x] eventEnd: new term, ignore
[x] observationLevel: new term, ignore
[x] observationType: same
[x] cameraSetup: rename from cameraSetupType
[x] taxonID: same
[x] scientificName: same
[x] count: same
[x] countNew: deprecated, leave empty
[x] lifeStage: same
[x] sex: same
[x] behaviour: rename from behavior
[x] individualID: same
[x] classificationMethod: same
[x] classifiedBy: same
[x] classificationTimestamp: same
[x] classificationConfidence: rename from classificationProbability
[x] comments: rename from observationComments
[x] _id: deprecated, leave empty
[x] speed: rename from individualSpeed
[ ] radius: cannot be supported before we use the new 1.0 model
[ ] angle: cannot be supported before we use the new 1.0 model

I would both ignore AND deprecate media arg (flag). Done in 7bd21068a1cc379d97a88000795da81c730a4e50

After discussion with @peterdesmet, we will:

support only camtrap-dp packages formatted using versions 0.1.6 and 0.6. Other versions are not supported and an informative message will be returned
won't load media-observations as extra slot of package$data as it could be very misleading for the users. It will make things more difficult for us to test the package as pkg$data will not contain the same number of slots. Notice that we still make use of media-observations for populating the fields radius and angle in observations.

The factor value to use for baitUse field will be defined based on values dep.tags and boolean dep.baitUse:

dep.baitUse
dep.tags
baitUse

TRUE
no bait related tags
other

TRUE
bait related tag NOT among the ones allowed
other

TRUE
bait related tag among the ones allowed
bait related tag

FALSE
ignored
none

NA
ignored
NA

@peterdesmet: about individualPosition and individualAngle, you wrote:

radius: cannot be supported before we use the new 1.0 model
angle: cannot be supported before we use the new 1.0 model

We provided a patch to read not-in-schema terms speed, radius and angle present in Agouti exports (#185) following v0.1.6. So, I wonder if we can at the moment still support radius and angle by renaming from individualPositionRadius- Angle even if they are not really make sense for event-based observations?

Decided to still leave media argument as in version v1.0-rc-1 we can still bypass media table to get (event-based) observations.

Decided with @peterdesmet to map "new" field deploymentGroups to "old" field session. This shouldn't have a significant impact at the moment.

Notice that get_record_table() uses sequenceID in media. So, we cannot leave it empty. Added via workflow proposed by @peterdesmet in https://github.com/tdwg/camtrap-dp/pull/314.

If you retain them, will that effect tests?

The only affected test was the one where I check the column names. I run all package functions locally without any issue. Notice that I didn't write new tests for each test. I wrote "only" a lot of new tests for checking that the output of read_camtrap_dp() is as expected, and so very similar to the old one.

If the bbox columns are the only ones we add, I would ignore them at this stage as they are not part of 0.1.6. Doesn’t feel right to make an exception for just these.

Decided with @peterdesmet to remove bounding box related columns as they could be confusing for the user at this stage.

Agreed with @peterdesmet: do not add taxonRank from taxonomic slot (new term in 1.0-rc.1) while building .data$observations.
In this way, the only difference among the columns of .$data$observations is the 2 vs 3 letters to indicate vernacular language, e.g. vernacularName.eng vs vernacularName.en.

I see in https://github.com/tdwg/camtrap-dp/blob/ef261578d956e1d3ece78ead760e0bd2d4df81c8/camtrap-dp-profile.json#L231C16-L245 that taxonRank is a not required field in taxonomic element in v0.1.6 already and so it is must NOT be removed! The fact that the example datapackage we were using (mica) didn' contain it should not allow us to remove it.

Contrarely to taxonRank, we shouldn't add higher taxonomic classification fields (kingdom, phylum, etc.) as they are not valid in v0.1.6.

Solved by #223


Switch from URL to pieces

Env vars can't contain :, as is required by a URL. A full URL, even as a quoted string, doesn't seem to make it as a set env var.
Switching to pieces (host/username/password) bypasses this issue.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

Looks like the newer PRs supersede this.

@camallen

ENV vars can contain : chars, the caeasr database URL contains one

Yeah, I know, but they don't load into a secret from an env file without enclosing quotes. The problem is that the DATABASE_URL var isn't loading into the pod.

I don't think we should split these out, they should be left as the URL version.

Why?

Also - you'll need a db config *_standby setup for the read replica for envs and the code that reads from replica, https://github.com/kenn/standby#install

Why? Staging has no replica and no separate readonly user.


Runtime TypeError: Cannot read property 'call' of undefined at webpack_require

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
When I try to run my project with webpack-dev-server I get runtime error Cannot read property 'call' of undefined at __webpack_require__
If the current behavior is a bug, please provide the steps to reproduce.
Using this output configuration (which was working previously):
  output: {
    path: path.join(__dirname, 'dist'),
    filename: '[name].[chunkhash].js',
    publicPath: '/',
    sourceMapFilename: '[file].map',
    chunkFilename: '[id].chunk.js'
  }

When I run webpack-dev-server using this command:
cross-env NODE_ENV=development webpack-dev-server --progress -d --inline --host <IP_ADDRESS>

I get a bunch of runtime errors that look like this:
vendor.356edb7e8753d46064d8.js:55 Uncaught (in promise) TypeError: Cannot read property 'call' of undefined
    at __webpack_require__ (vendor.356edb7e8753d46064d8.js:55)
    at <anonymous>

If I remove the chunkFilename:
  output: {
    path: path.join(__dirname, 'dist'),
    filename: '[name].[chunkhash].js',
    publicPath: '/',
    sourceMapFilename: '[file].map',
    // chunkFilename: '[id].chunk.js'
  }

Then it runs fine.
The entire config is here: https://gist.github.com/aaronbeall/b286eb3f2ff93bed37289f0fefbb3d3c

What is the expected behavior?
No error.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

<EMAIL_ADDRESS><EMAIL_ADDRESS>node v8.6.0
OSX 10.11.6

I try not to combine chunkhash with something like HotModulesReplacement plugin or webpack-dev-server. In general, I try to use chunkhash only in Production. Also, we are told not to use those plugins in Production.
Chunkhash, from what I understand, is not updating correctly (on purpose or not, I don't know) when its content is changing. For safety, I consider it as being a constant, computed once and then never updated.

@aaronbeall children: true for CommonsChunkPlugin solve you problem?

@evilebottnawi Thanks for reply... well currently I children: true in my second CommonsChunkPlugin instance:
  new webpack.optimize.CommonsChunkPlugin({
    name: 'vendor',
    minChunks(module, count) {
      return module.resource && module.resource.indexOf('node_modules') !== -1
    }
  }),
  new webpack.optimize.CommonsChunkPlugin({
    children: true,
    async: true,
    minChunks: 2
  })

To be honest I have no idea if this is a good or terrible idea, we initially used the vendor chunk then later added the async chunk to support dynamic route module loading. This was working until recently, afaik.

removing dynamic imports fixed my issue

I made migration from require to import(), and got same problem

I've started to get this error fairly frequently after migrating to webpack 4.

Constantly get this error when using dynamic imports. Even after updating Webpack to latest version (currently 4.3.0). Someone solved this problem (without removing dynamic imports)?

I don't have a general answer, but I have a few answers that are specific to my case that may help others debug.
This happened to me twice, and each time was because of what was likely a misconfiguration rather than a bug in Webpack itself (as far as I can tell so far). Specifically, it seems to have happened because of a mismatch between modules expected to be loaded by a chunk file, and the modules actually in that chunk file. I'm also still a bit rusty with terminology, so let me know if any of this doesn't make sense.

I have a custom server implementation that uses webpack-dev-middleware. I was inadvertently not re-building one of my entrypoints, but was still serving it statically (so, an old version of the file was being served). Additionally, the generated chunks were just named [chunkId].js (i.e. 1.js, 2.js, etc). This meant that it was requesting chunks by module ID that existed on disk, but were referring to different dependencies. Hence, a chunk would load, but the modules that were loaded from this chunk were not what was expected. The fix for this was to rebuild the entry points that I had accidentally stopped building.

I have multiple configs that all build to the same directory and chunks were overwriting each other across different builds because their names collided. This was fixed by naming the chunks based onchunkHash rather than by module name. Doing this would also probably make the problem I had above more obvious, since the names of the requested chunks would likely be different from the actual chunk files hosted by the server.

Not sure if that's useful or not, but I figure it may help someone else debug.

It would be great if someone could post a small reproducible example using webpack 4. Best put this example into a github repository together with instructions how to get to the problem.

I just sunk 3 hours into this issue. Removing dynamic import did fix my issue.
I'm still on webpack 3.11.0. This issue started happening after I upgraded from react 16.2 to 16.3 (with all the context API stuff.)
My code structure looks like this. I have a component UploaderToolbar that contains multiple buttons, clicking on the instagram one will open up a InstagramPicker, which goes to download and display the photos via an array of PhotoThumbnail components.
InstagramPicker is dynamically loaded, through a thin wrapper called HMLoadable, using react-loader 5.3.1.
// `uploader_toolbar.jsx`
const InstagramPicker = HMLodable({
  loader: () =>
     import(/* webpackChunkName: "instagram-picker" */ "./instagram_picker")
});

// `instagram_picker.jsx`
import PhotoThumbnail from "app-components/photo_thumbnail";

When the UploaderToolbar is imported on a page where PhotoThumbnail is already imported, it works just fine. Otherwise, it'd crash on this line: https://github.com/jamiebuilds/react-loadable/blob/v5.3.1/src/index.js#L199 and here is a screenshot.

Once again, please provide a small reproducible example.

Not sure if that helps anybody, but I was getting the same error when changing the path of a dynamic import without shutting down and restarting the dev server.
I'd import('./foo'), but after I moved ./foo to ./bar/foo and changed the import to be import('./bar/foo') webpack would throw with Cannot read property 'call' of undefined at __webpack_require__.
Module ./foo is wrapped with hot from react-hot-loader.
Restarting the dev server fixed the issue.
Some other info:
<EMAIL_ADDRESS>node dev server using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

The same problem when i run build with osx,bug it works well when i run dev.
and when i run build with window,it doesn't have the problem.

Same problem here with webpack 4 when building assets in production mode.
When starting webpack-dev-server error was disappear.
PS. With webpack 3 works just fine.

I have the same problem use require.ensure.  like @maciej-gurban Restarting the dev server is ok.
Description of my problem：
I have to router component, like:
require.ensure([], (require)=>{
  cb(null, require('./a').default)
},'abc')

require.ensure([], (require)=>{
  cb(null, require('./b').default)
},'abc') // the same before chuck name

First started is OK！！！！，but i change：
require.ensure([], (require)=>{
  cb(null, require('./b').default)
},'ccc') // change this

have problem: Cannot read property 'call' of undefined at __webpack_require__.
Do not change anything，Just started is OK！！！！

I had the same issue when using dynamic imports, in production mode only.
When you look at the function that executes module:
    function __webpack_require__(moduleId) {
        // Check if module is in cache
        if (installedModules[moduleId]) {
            return installedModules[moduleId].exports;
        }
        // Create a new module (and put it into the cache)
        var module = installedModules[moduleId] = {
            i: moduleId,
            l: false,
            exports: {}
        };
        // Execute the module function
        modules[moduleId].call(module.exports, module, module.exports, __webpack_require__);
        // Flag the module as loaded
        module.l = true;
        // Return the exports of the module
        return module.exports;
    }

In my case the moduleId 373 that I was importing dynamically did exist in installedModules (with l: false) but did not exist in modules.
When the same code was run without production mode, the module names were strings because I use the NamedModulesPlugin and this situation did not happen.
This gave me a hint that there's some bug related to module naming. Then I tried HashedModuleIdsPlugin and it worked fine.
So, for me the fix was to use HashedModuleIdsPlugin in production and NamedModulesPlugin in dev.

Same thing: production mode, dynamic imports – doesn't work.
For me, using HashedModuleIdsPlugin doesn't work, sadly.

I have the same issue, only in production builds. However, the problem disappeared when disabling my ad-blocker (Easy AdBlock)

I have some problem. I find out that problem in my css loader ExtractTextPlugin.
I set allChunks: true and this fix my problem.
By some reason separate css chunks are not supported.
PS:
you can debug your problem if you set
optimization: {
    namedModules: true,
    namedChunks: true
}

In that case you can SEE which module is failed to load.

Tks @vrozaev , I got this problem too using Webpack 4, react-loadable and ExtractTextPlugin.
Found a same case and solved here react-loadable Chunks loaded but code not executed
Install babel-plugin-syntax-dynamic-import and set allChunks: true fixed my problem.

Were there any updates to the reproduction of this issue since then? I too have the issue appear as soon as I switch to "production" mode (v4.25.1).
I don't have any environment specific rules in my webpack config file. So switching to production mode should be affecting some dependencies or default configuration.

@ooflorent any update on this after having a Webpack4 reproducible example provided?
I have just migrated from Webpack 3 to 4, and have the same problem, two identical webpack configs, and if I change mode from 'development' to 'production' every thing breaks. I have dynamic imports for my vue components, and if I remove them, it goes back to working again.

On webpack 4, remove new webpack.optimize.LimitChunkCountPlugin({maxChunks: 10}) fixed my problem.

After npm install and npm install<EMAIL_ADDRESS>! Solved my problem!

Was facing this same issue after we upgraded from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>Went back down to 3.2.1 and everything worked again.

@tonyanziano future webpack version can be incompatibility with 3.2.1 due internal bugs, you still should upgrade

Upgrading from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>was also a breaking change for us, apparently because of https://github.com/webpack/webpack-dev-server/commit/b31cbaaf49417eb4adf8949cd87c36ca82653b25. After seeing this error and (way too much) investigating, we seem to have fixed the issue by adding ''webpack-dev-server/client?http://localhost:3100' to our entry array.

@evilebottnawi what's the difference, how many bugs in the current version, if the newer version doesn't work at all?
By the way, rollback to 3.2.1 solved problem for me, thanks, @zoro00000000

Please open issue in dev server repo with reproducible test repo, also we fix many issues in master branch, please try, feel free to report any problem, release was in Monday

Commenting chunkFilename and downgrading to<EMAIL_ADDRESS>worked for me too.
Cheers @tonyanziano and @aaronbeall

Solved in<EMAIL_ADDRESS>

evilebottnawi Latest webpack-dev-server version is 3.7.2 now. Do you mean<EMAIL_ADDRESS>?

@vkurlyan yep

@vkurlyan @evilebottnawi still happening for me in<EMAIL_ADDRESS>

@douglas-treadwell please create minimum reproducible test repo, problem only with webpack-dev-server? if yes please open issue in webpack-dev-server, thanks!

I got different error messages when trying to use dynamic expressions in import(), like:
import(/* webpackChunkName: "conf-" */`./components/formengine/configs/${config}.js`).then(config => { }

Either it couldnt find a chunk or call undefined. For me a quick fix was to change the webpackChunkName to something new and rebuild but the thing that solved it permanentaly was adding contenthash like below.
output: {
  filename: '[name].[contenthash].js'
}

Problem was the same as most with webpack-dev-server, tried rolling back from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>and still didn't work until I updated webpack from<EMAIL_ADDRESS>to most recent<EMAIL_ADDRESS>

I got a same problem when I just use the ESM to import a function from a js file.And the problem only show up when I use the devServer(Its fine with bundler file).I try to updated my webpack from v4.0.0 to v4.14.0, nothing change.But when I updated webpack to the most recent version 4.41.1,the bug is gone,So I think this bug already fixed in lastest version.

One more possible reason to get this error: I was using legacy extract-text-webpack-plugin instead of mini-css-extract-plugin.

Tks @vrozaev , I got this problem too using Webpack 4, react-loadable and ExtractTextPlugin.
Found a same case and solved here react-loadable Chunks loaded but code not executed
Install babel-plugin-syntax-dynamic-import and set allChunks: true fixed my problem.

This helps me, but only use https://babeljs.io/docs/en/babel-plugin-syntax-dynamic-import

I got the same problem, and believe or not i solved the problem changing the name of the folder containing the component where i got the problem.

Maybe it's due to caching? If it happens again, try to remove the babel and webpack caches (wherever those are)

I am facing the same issue  with webpack 4.3.0 and webpack dev server 3.11.0

You can also try to set unique output.jsonpFunction function name.

Somebody can create reproducible test repo?

@evilebottnawi
I can't reproduce this issue when creating my own Webpack configuration. The only time I can get a consistent reproduction is when using Gatsby with loadable components which will give "WebpackError: TypeError: Cannot read property 'call' of undefined." I've been trying to reverse engineer their webpack config to solve this but I've been unsuccessful.
I created a minimal repository using Gatsby to hopefully help you diagnose the problem. It doesn't seem like anyone has been able to provide reproduction of the issue with a minimal project so I believe this minimal Gatsby project is as good as we have for now. I left some details in the README.

In my TODO

Reproduced, WIP

Without loadable, it output, so error don't lie, nothing to call :smile: :
UnhandledPromiseRejectionWarning: Error: Cannot find module '../modules/module-one'

Something wrong with resolving, I think better place for it is Gatsby repo, there are a lot of additional stuff from gatsby

if you're using webpack 3 and babel 6 install babel-plugin-syntax-dynamic-import and set the plugin on babelrc.
if you're using webpack 4+ and babel 7 https://babeljs.io/docs/en/babel-plugin-syntax-dynamic-import
if you're using ExtractTextPlugin set allChunks: true in the pluging configs
That solved the issue for me

follow step by step this solution for fix this problem, working with me using webpack 4
1.STEP ONE
output: {
library: '[name]',
umdNamedDefine: false
}
optimization: {
concatenateModules: false,
providedExports: false,
usedExports: false
}

STEP TWO
remove symlink and caheWithContenxt

STEP THREE
remove old project name in heroku, after remove old project create new project name

Extract from all additional chunks too (by default it extracts only from the initial chunk(s))
When using CommonsChunkPlugin and there are extracted chunks (from ExtractTextPlugin.extract ) in the commons chunk, allChunks must be set to true

ExtractTextPlugin was deprecated, please migrate on mini-css-extract-plugin, I want to close this issue, if you faced with the same issue using webpack@4/webpack@5 and mini-css-extract-plugin or without the plugin, please open new issue with reproducible test repo, a lot of

Same issue I have faced and comment of @vrozaev helped me. I have added
optimization: {
    namedModules: true,
    namedChunks: true
}

in webpack. After adding I have shown the file name that contains the problematic code.

Thanks @vrozaev

I had a similiar issue 'Cannot read property 'call' of undefined at __webpack_require__'.
I was writing a Plugin for Shopware6 and had to import some node modules when this error appears at production compilation. But not at dev compilation.
First i had to change all import to require. Like @hannadrehman allready mentioned 3 years ago.
Additional i had to add the following optimization statement:
optimization: {
	splitChunks: {
		cacheGroups: {
			'runtime-vendor': {
				chunks: 'all',
				name: 'vendors-node',
				test: join(__dirname, 'node_modules')
			}
		},
		minSize: 0
	}
}

Do you use webpack v5? If yes, please create reproducible test repo, maybe we can improve our errors and improve DX


[CARBONDATA-1211] Implicit Column Fix

Projection on implicit column is failing with garbage values when vector read is enabled.
Select getTupleId as tupleId from table;

Can one of the admins verify this patch?

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2632/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/541/

LGTM


implementation of the issue #242

gh-242

Coverage increased (+0.4%) to 37.842% when pulling 620ff36b7fa50845cbdafa58956561d4f0071374 on fedys:issue-242 into 143852c47e93381fd0fa7e956a548b7f560647b5 on cross-solution:develop.

For Options handling please consider using AbstractOptions via OptionsAbstractFactory (Example: Orders/module-options).

For newly created classes and/or methods a @since tag would be nice. Using the NEXT minor release version number (would be 0.26 currently). That's mainly cosmetic sugar that helps track modifications at a glance without invoking the VCS mechanisms (at github .e.g.)

@TiSiE : works as expected. Can be merged

Coverage increased (+0.4%) to 37.836% when pulling 2c52a4e0047975bf536445a36cd1b7db0b3361a4 on fedys:issue-242 into 143852c47e93381fd0fa7e956a548b7f560647b5 on cross-solution:develop.


Add support for automatically skipping over fifo files

Fixes issue #1083

Codecov Report

Merging #1084 into develop will increase coverage by 0.17%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop    #1084      +/-   ##
===========================================
+ Coverage     84.7%   84.87%   +0.17%
===========================================
  Files           40       41       +1
  Lines         3596     3617      +21
  Branches       653      654       +1
===========================================
+ Hits          3046     3070      +24
+ Misses         413      412       -1
+ Partials       137      135       -2

Impacted Files
Coverage Δ

isort/main.py
64.16% <100%> (+0.91%)
:arrow_up:

tests/test_main.py
100% <100%> (ø)

isort/wrap_modes.py
97.11% <0%> (+2.88%)
:arrow_up:

Continue to review full report at Codecov.

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


[bilibili] interface.bilibili.com_v_cdn_play -5003 checksum error

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.08.19. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.08.19

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -g --write-pages --proxy socks5://<IP_ADDRESS>:8124/ --verbose http://www.bilibili.com/video/av5904451/
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-g', '--write-pages', '--proxy', 'socks5://<IP_ADDRESS>:8124/', '--verbose', 'http://www.bilibili.com/video/av5904451/']
[debug] Encodings: locale cp950, fs mbcs, out cp950, pref cp950
[debug] youtube-dl version 2016.08.19
[debug] Python version 3.4.4 - Windows-XP-5.1.2600-SP3
[debug] exe versions: avconv v12_dev0-3086-g0638b99, ffmpeg N-81311-g16ea0bc
[debug] Proxy map: {'http': 'socks5://<IP_ADDRESS>:8124/', 'https': 'socks5://<IP_ADDRESS>:8124/'}
ERROR: No videos found!; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\YoutubeDL.py", line 691, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\common.py", line 347, inextract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\bilibili.py", line 122, in _real_extract
youtube_dl.utils.ExtractorError: No videos found!; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
...
<end of log>

in 9586632_http_-_interface.bilibili.com_v_cdn_play.dump:
<?xml version="1.0" encoding="UTF-8"?>
<video>
	<code>-5003</code>
	<result>checksum error</result>
</video>

Description of your issue, suggested solution and other information
Don't know if bilibili is updated their xml request format, and bilibili video ID av5904451 requires Taiwan Proxy for getting URLs, but --geo-verification-proxy doesn't work.

Duplicate of #10375.


Define repo as repository at least once in the readme

At least once in the readme file, we should say something like "repository (repo)" so that we are clear on our definitions.

I'm going to pick this one up and work on it.


[iOS] googleMapId is not working on iOS devices

Summary
When I try to apply Cloud Styling to my application - nothing happens on iOS devices. However, on Android - everything works fine
Reproducible sample code
<MapView
  googleMapId="MY_MAP_ID"
  // other props
</MapView>

Steps to reproduce

Obtain/Create Custom Google Map Styling in Google Cloud Console;
Create Map ID in Map Management tab;
Associate Custom Map Styling with created Map ID;
Copy Map ID and pass it to the MapView component via googleMapId prop;

Expected result
iOS Google Map is styles accordingly to the Google Cloud config
Actual result
iOS Google Map remains the same after passing googleMapId
React Native Maps Version
1.20.1
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.76.3
What version of Expo are you using?
Not using Expo
Device(s)
iPhone 15 Pro
Additional information
No response

I'm running into the same issue, somehow react-google-map is not injecting/passing mapid value to AIRGoogleMap. If directly hardcode the mapid in the AIRGoogleMap file then it works.

@v-andreichuk thanks for reporting this, it's part of the missing support for react-native Fabric / new arch.
please checkout
https://github.com/react-native-maps/react-native-maps/issues/5250
I will keep this open because it might get missed while doing the migration and it needs to be tested separately


feat: implenent basic SFT pipeline based on synthetic data generator

This is just an idea for how to make distilabel crazy-user-friendly. In this example, an SFT pipeline is abstracted away to make it easy to use. Like this:
from distilabel.presets import SFTPipeline

pipeline = InstructionResponsePipeline()

distiset = pipeline.run()

Maybe we could do this for other core tasks like: DPO, classification, retrieval

@burtenshaw what pipelines do you intend to create?

SFT
DPO
Classification

Should we also have individual components like completion generation (if you only want an additional completion), instruction generation (which can be done with magpie and inheriting with only_instruction=True), preference (without generating from scratch)?

@burtenshaw what pipelines do you intend to create?

SFT
DPO
Classification

@burtenshaw In this PR, I plan to just implement SFT and share that. But I think we could move on to DPO and classification straight after.

Should we also have individual components like completion generation (if you only want an additional completion), instruction generation (which can be done with magpie and inheriting with only_instruction=True), preference (without generating instruction/completions from scratch)?
I can imagine people doing these things in steps and reviewing the quality of the generations in between before racking up costs with a complete pipeline.

I agree that this is useful to more basic users. But this is also potentially complex. I don't want to end up abstracting the Magpie API in multiple ways, because the user could just use a proper pipeline. I would prefer to get feedback first.

@burtenshaw what pipelines do you intend to create?

SFT
DPO
Classification

@burtenshaw In this PR, I plan to just implement SFT and share that. But I think we could move on to DPO and classification straight after.

Should we also have individual components like completion generation (if you only want an additional completion), instruction generation (which can be done with magpie and inheriting with only_instruction=True), preference (without generating instruction/completions from scratch)?
I can imagine people doing these things in steps and reviewing the quality of the generations in between before racking up costs with a complete pipeline.

I agree that this is useful to more basic users. But this is also potentially complex. I don't want to end up abstracting the Magpie API in multiple ways, because the user could just use a proper pipeline. I would prefer to get feedback first.

Sure, sounds fair, I just wanted to see what your thoughts were surrounding the features.

@sdiazlor

I like the idea! Just let some small notes. If you can test it and generate a sample dataset that we can link in the docs that would be perfect

Here's a dataset: https://huggingface.co/datasets/argilla/distilabel-sft-easy


always emit success and failure so monitors recover

as it is, when monitoring chef.run.failure, monitors never recover and just go from alert -> no data and require manual intervention to recover
sending a zero failure counter on success means that these monitors will recover when chef runs succeed

Thanks @devonbleak, this is was definitely an oversight on our part.
Unfortunately the tests are failing since most (all?) of the VCR cassettes have to be updated. I'll work on that and try to better document the required steps.

Fixed in #89. Closing


Cannot run demo app with Android Studio 3.6.3

Issue Type

[x] Bug
[x] Build system related

Description and/or steps/code to reproduce the problem
I had no problem with Android Studio 3.5.3.
When I upgraded to AS 3.6.3, I could not run the demo app anymore.
(same problem with other 3.6.x versions)
I have the following message in the Run tab:
04/24 08:56:17: Launching 'OpenStreetMapViewer' on samsung SM-G360F.
Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: No outputs for the main artifact of variant: debug

I tried to upgrade the gradle version as suggested by AS:

To take advantage of the latest features, improvements, and security fixes, we strongly recommend that you update the Android Gradle plugin from the current version 2.2.0 to version 3.6.3 and Gradle to version 5.6.4. Release notes  Android plugin 3.2.0 and higher now support building the Android App Bundle—a new upload format that defers APK generation and signing to compatible app stores, such as Google Play. With app bundles, you no longer have to build, sign, and manage multiple APKs, and users get smaller, more optimized downloads. Learn more

But then I had other problems.

So more specifically, you can no longer build the demo app using android studio because of an update you chose to install and/or changes you made. The demo app, downloaded off the play store probably works just fine.
 I'm not sure who keeps promoting this practice but it should stop.
  Build reproducibility is poor at best

Unfortunately I still have the same error message after the git&gradle commands.
04/25 18:12:16: Launching 'OpenStreetMapViewer' on samsung SM-G360F.
Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: No outputs for the main artifact of variant: debug
Timed out waiting for process (org.osmdroid) to appear on samsung-sm_g360f-5545b037.

Obviously I'm not the only one with an issue switching from AS 3.5.x to 3.6.x. (not specifically for osmdroid):

https://stackoverflow.com/questions/60484690/android-studio-3-6-issue-apkprovisionexception-no-outputs-for-the-main-artifa
https://stackoverflow.com/questions/60417572/apkprovisionexception-after-upgrading-to-android-studio-3-6
https://stackoverflow.com/questions/60493101/unable-to-determine-application-id-com-android-tools-idea-run-apkprovisionexcep
https://stackoverflow.com/questions/60411205/project-with-external-module-issue-in-android-studio-3-6

But with my very limited understanding of the build process, that doesn't help.

does this work for you?
compile via command line gradle build
install app via command line adb install adb install OpenStreetMapViewer\build\outputs\apk\OpenStreetMapViewer-6.1.7-SNAPSHOT-debug.apk
launch app on device
attach debugger via android studio. It's run > Attach debugger to android process

by the way, what problem are you trying to solve?

OK so i just upgraded. Pro tip, don't upgrade AS until this is resolved.

https://developer.android.com/studio/archive
3.5.3 works, i'd recommend getting that version to solve whatever problem is it you are trying to do.
i'm willing to bet AS is doing something funky and trying to detect something from our build script, which is out of the ordinary and it's screwing up somewhere which causes the process automation to fail.

I had to switch to MacBook Pro and AS 4.
Doesn't work either, with this message:
Server returned HTTP response code: 403 for URL: http://services.gradle.org/distributions/gradle-2.14-bin.zip

Try https
On Wed, Jun 24, 2020, 6:13 AM monsieurtanuki<EMAIL_ADDRESS>wrote:

I had to switch to MacBook Pro and AS 4.
Doesn't work either, with this message:
Server returned HTTP response code: 403 for URL: http://services.gradle.org/distributions/gradle-2.14-bin.zip
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/1560#issuecomment-648730678,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPCIGPCYBZPWDJYSPFCJJDRYHGVZANCNFSM4MP3GSMQ
.

@spyhunter99 Thanks, https was indeed useful, but now I'm stuck with
failed to find target with hash string 'Google Inc.:Google APIs:23' in: /Users/zzzz/Library/Android/sdk

should be fixed now


Some (small) improvements to VAL3

Good evening all together,
my name is Johannes and I´m an software engineer at Staubli (Germany).
I have not much experience with ROS yet but I´m very familiar with VAL3. I had a look at the code and found some small improvements to make the VAL3 code more stable:

[ ] check all return values of libInterface:libLoad in start(). In case of error: popUpMsg("...")
[ ] instead of taskKill("ros_server~") I would call stop() and then
[ ] Kill all tasks in stop()
[ ] Check for overruns in the synchronous tasks
[ ] Check if tasks are really started in start()

These changes could be done very fast and without much effort.
Even more effort need some other things I would recommend:

[ ] Create a task manager to check the state of the tasks and eventually start them again. Until now, if someone kills a tasks on the SP2 it is gone and not automatically restarted. This is not ideal for production.
[ ] Init all variables (especially) bools to a specific state. When someone saves the application on the SP2 and starts it again there is no guarantee that the variables have default values any more.

You are much more experienced then me and I´m open to discussions about my points above. If you agree to some of them, I would make the changes in my branch and then PR it here.
I would also like to improve the driver from VAL3 side if there are any topics I can help you!
Thanks for your great work,
Johannes

Hi, thanks for reaching out.
Yes, we would be very much interested in the improvements you suggest.
Everything which will improve the user experience is always welcome.
There is some discussion around other possible improvements in #32, where @enginkarlidag explains what kind of changes they've made in their fork.
@marshallpowell97 is from Staubli USA, we should try to coordinate with him as well.

If you agree to some of them, I would make the changes in my branch and then PR it here.

please open PRs. They will allow us to focus the discussion and review the changes. There is always a chance things won't get merged as-is, but that wouldn't be a problem. That's exactly what PRs are for.

You are much more experienced then me and I´m open to discussions about my points above.

Personally I could not claim to be more experienced, at least not on the VAL 3 / Staubli side.
So we're happy to have you here :+1:

@JohannesFriedrich: friendly ping?

@JohannesFriedrich?

Thanks for the reminder. I found some time today to program the changes, see #39
I´ve tested it on CS8C and CS9 in SRS on the emulator and works well.
Feedback very welcome!

Could you please explain what a overrun is and what should be done if it happens?
Great to see your improvements!

@simonschmeisser
From the VAL3 manual:

If the execution of a VAL 3 synchronous task takes longer than the specified period, the current cycle ends normally, but the next cycle is canceled. This overrun error is signaled to the VAL 3 application by setting the Boolean variable specified for this purpose at the task creation to "true". At the beginning of each cycle this Boolean variable thus shows whether the previous sequencing was carried out entirely or not.

If you have a synchronous task which receives/sends data in the given cycle time and is not able to do so, it´s critical to know if the task could receive/send the data, e.g. if you want to control an external axis.


In Snake mode, structure in HELM format does not open via Paste from clipboard

Steps to Reproduce

Switch to the Macro mode (Remote mode) – the Snake mode
Open the Console
Load via the Paste from clipboard, selecting HELM type: PEPTIDE1{C.[Apm].D.[dC].E}|PEPTIDE2{F.[D-gGlu].G.[D-Orn].I}$PEPTIDE1,PEPTIDE2,2:R3-2:R3|PEPTIDE2,PEPTIDE1,4:R3-4:R3$$$V2.0
Click on the “Add to Canvas” button

Actual behavior
The bug is reproduced with a new error, which appears after clicking the "Close" button:
Blocked aria-hidden on a  element because the element that just received focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden. <button class="MuiButtonBase-root e1oaegu30 ejign8b1 css-i5kpl3" tabindex="0" type="button" title="Structure will be loaded as fragment and added to Clipboard" role="button" data-testid="add-to-canvas-button">…flex

localhost-1724424078470.log
https://github.com/user-attachments/assets/3dfd00a7-d4b5-4008-a9c0-0264b4299ff5
Expected behavior
There are no errors on the canvas and in the Console. The structure in the HELM format opens in the Remote mode
Desktop (please complete the following information):

OS: Windows 10 Pro (version 22H2) x64
Browser: Сhrome
Version: (126.0.6478.127) x64

Ketcher version
2.24.0-rc.3, Build at 2024-07-14; 20:40:06
Original bug: https://github.com/epam/ketcher/issues/4977
Issue found while testing https://github.com/epam/ketcher/issues/5132

Tested. Bug fixed.

Desktop:

OS: Windows 11
Browser Chrome
Version 128.0.6613.120 (Official Build) (64-bit)

Ketcher version
[Version 2.28.0-rc.1]
Indigo version
[Version 1.27.0-rc.1]


SVG preview inaccurate color respresentations

Microsoft PowerToys version
v0.61.0
Running as admin

[X] Yes

Area(s) with issue?
ColorPicker, SVG Preview, SVG Thumbnail
Steps to reproduce

Create SVG with green background (HEX 149911), and white text on top.
Preview SVG within file explorer
use color picker to pick the background color from the preview
color picker gets result that is not the original color defined in the SVG (in my case ~HEX d29b22). - When the SVG is opened, of course the correct color gets displayed again.

✔ Expected Behavior
I expect the SVG preview to display the colors defined in the SVG. So that quickly reusing a color used within an SVG is possible. And i don't have to open up the SVG.
❌ Actual Behavior
Color displayed is different to the color defined in the SVG file.
Other Software
Windows Explorer (Windows 10 build 19044.1826)

Do you happen to use any color correction or red tint? Color Picker can't "see through" that.

A screenshot would also help

Hi Jay,
No I don't have any color correction being used. Especially as it does pick up the color correctly when the file is opened up.
Here are some screenshots of the issue:

This is the SVG opened with Internet Explorer (IE, Chrome, Firefox and Adobe Illustrator all display it the same)

This is the same SVG in File Explorer's Preview pane, and as you can see the color reported by the color picker is not the same hex code

Thumbnail has the same issue as the preview pane.

FWD @martinchrzan

I see your screenshots, but when I download your first screenshot and test it on my pc, it all returns the same, correct value. Care to share your original file?

Oh yes, abosolutely, here you go

:

I hope that displays correctly, if not I can also zip it up and send it once more

Thanks for the image. Did some test myself and I have even different results. Have a look at my recording on YouTube.
I see the SVG thumbnail preview has uneven color, looks as if it uses JPEG compression.
 while the PNG preview (your screenshot that I saved) has a smooth color.
@martinchrzan @Aaron-Junker do you know if that conclusion is correct?

I don't know if the different results might have something to do with windows color scheme? As I'm using Dark mode, yet from your screenshot it appears you're using Light mode.

I don't know if the different results might have something to do with windows color scheme?

Nah, this is about the colors inside the image. It's an unwanted artefact. You can enlarge the area by scrolling the mouse wheel.

Goeie keuze voor standaardtaal :)

Tsja, Nederlands hè :P

Could it alternatively be that the preview and thumbnail operate on a different color space?? file might be 10 bit color range, where the preview might only be 8 bit or something?

Tsja, Nederlands hè :P
Gotta say i prefer english for my devices tho... But anyways

whoops, didn't know that was a button, thought it was only a dropdown, sorrey


[ASCII-2428] Multiple tagger implementations

What does this PR do?
This PR updates the tagger component to use the latest standard for components.
The PR is quite extensive, but ultimately, there should not be any behavior change. Still, I split it into separate commits to make it easier for reviewers to understand.

create local tagger implmentation f0df5fa
create remote tagger implmentation 554bc16
create noop tagger implmentation cdf7d9d
create dual tagger implementation f4b6d0b
move subpackages from comp/tagger/taggerimpl folder to comp/core/tagger 9f716f8
use the new tagger implementation on the cmd entry points f90e0c4
delete old tagger files https://github.com/DataDog/datadog-agent/pull/30584/commits/632e849b926c4e10e469fe3e7a0113bc57c856ca
update import path and function names https://github.com/DataDog/datadog-agent/pull/30584/commits/80cb6c5e160c5131efa604c0f1cd548a357dc1ca

A note about the dual tagger
Sometimes, a subprocess or the core agent wants to use either the local or remote implementation. For those use cases, we create the dual implementation. Based on the parameters, it decides at runtime which implementation to use.
Motivation
The primary motivation is to be able for sub-processes that use the remote tagger only to import and the remote tagger implementation. The biggest gain is that the remote tagger no longer requires a workloadmeta component to function, nor do the container packages.
This is particularly important to the Otel team. Which wants to implement its own OCB. RFC
Disclaimer about the gains When splitting the different tagger implementations. I spoke with @davidor, and we realized that removing the container packages won't be that straightforward, as I explain in more detail in the paragraphs below.
Table with tagger functions implemented by the different tagger implementation

Function
Local Tagger
Remote Tagger

Start()
✅
✅

Stop()
✅
✅

ReplayTagger()
✅
❌

GetTaggerTelemetryStore()
✅
✅

LegacyTag()
✅
✅

Tag()
✅
✅

AccumulateTagsFor()
✅
✅

Standard()
✅
✅

List()
✅
✅

GetEntity()
✅
✅

Subscribe()
✅
✅

GetEntityHash()
✅
✅

AgentTags()
✅
✅

GlobalTags()
✅
✅

SetNewCaptureTagger()
✅
❌

ResetCaptureTagger()
✅
❌

EnrichTags()
✅
✅

ChecksCardinality()
✅
✅

DogstatsdCardinality()
✅
✅

Why do the remote tagger and the local tagger implement all methods identically
Previously, the tagger had a TaggerClient struct that encapsulated the different implementations and implemented the different tagger functions. This made it so all tagger implementations behave the same. In this PR, I wanted to preserve the same functionality, but we should revisit this since the remote tagger is a read-only tagger that gets the tags from the core agent that executes the local tagger.
Why does the tagger require the container packages?
The AgentTags and the EnrichTags functions from the tagger require the container package to get their own container ID and to get the container ID from the pod.
Since the fetching of that information is inside the tagger component, we must include all the container packages.
Not all tagger users might run in a container environment or want to use the default container lookup process. One solution is to provide the container ID as part of the function arguments of the AgentTags and EnrichTags functions. To avoid changing more stuff in the PR, I decided to hold on to that change first to hear people's thoughts and avoid increasing the size of this PR.
Another solution would be to create separate interface for the remote tagger.
type RemoteTagger interface {
    Tag()
    LegacyTag()
    ....
}

Which includes only read method. That way sub-processes that only need the remote tagger could use the read-only remote tagger interface
Why does system-probe/windows build add that many imports? +161
The system probe directly created a remote tagger. Previously, this tagger did not implement all the tagger methods, but that is no longer the case, as mentioned in the section above. We probably need to figure out how to solve this issue so that the system probe does not include all the container packages.
The UMS team has already considered adding the remote tagger to the system probe (https://github.com/DataDog/datadog-agent/pull/30852), adding the same number of imports.
Why does system-probe/windows build add that many imports? +161
TL;DR
This PR does not modify how the different tagger implementations behave but adds more packages to the system-probe/Windows build. Still, this moves us closer to fully decoupling the tagger implementations, as each is now a separate package. Let's use this PR to start conversations with the different teams about the expected behavior of a remote tagger and how to overcome the container package issue. We can still merge this PR if the system-probe package imports are not an issue and continue iterating forward to solve the problems with the container package.
Describe how to test/QA your changes
All unit tests are updated.
Possible Drawbacks / Trade-offs
Additional Notes

Is it expected that there are +160 dependencies for the agent on Windows amd64 ? (source)

/merge


xfce.xfce4-volumed-pulse: 0.2.3 -> 0.2.4

https://gitlab.xfce.org/apps/xfce4-volumed-pulse/-/compare/xfce4-volumed-pulse-0.2.3...xfce4-volumed-pulse-0.2.4
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg eval


What can this bot do?

I don't know. ;) But with the Telegram client and Node.js server our hands're unleashed!
Here'll be the features:

[ ] can translate voice-messages to plain text

It will be the bridge between telegram-client and something more abstract

It'll be Python!


[DOC] ml-framework page example request doesn't work

What do you want to do?

[X] Request a change to existing documentation

Tell us about your request. Provide a summary of the request and all versions that are affected.
https://opensearch.org/docs/latest/ml-commons-plugin/ml-framework/ -
The example request here doesn't seem to work. It's missing the model_content_hash_value key.

Regarding that, it's not mentioned anywhere. When registering a model via URL, you'll have to pass that value and it's the sha256 checksum of the model zipfile. You'll want to provide instructions on how to calculate that and make it part of the call.
For comparison, the example call to register a model from the API reference page for machine learning works proper-like.
https://opensearch.org/docs/latest/ml-commons-plugin/api/

Looks like you're working on the same problem under the other issue (5591), @kolchfa-aws , so assigning to you so you can close them both. Thanks.

@nateynateynate Did you have to calculate the hash code and if so, do you have instructions on how to do it?

Actually, never mind. Found the command.


ReqwestClient shouldn't wrap reqwest::Client in Arc

reqwest::Client is already a thin wrapper over an Arc. ReqwestClient shouldn't add another one on top of it.

Thanks for reporting!


BLOB Image properties

Hello,
Please implement images as in:
https://documentation.devexpress.com/#eXpressAppFramework/CustomDocument113545

Hi, we need to research possibility of enhancing this functionality


1204: SSO Spike

Ticket
Resolves 1204
Changes
Integrates pilot-specific SSO with test Azure credentials.
Context for reviewers
Currently WIP. Integrates SSO with a combination of Devise, Omniauth, and an Azure AD Omniauth adapter gem.
Testing

Provide evidence that the code works as expected. Explain what was done for testing and the results of the test plan. Include screenshots, GIF demos, shell commands or output to help show the changes working as expected. ProTip: you can drag and drop or paste images into this textbox.

Is there documentation for local dev that should be updated? Can a dev sign in locally?


Add tag for 2.0

Sorry to be pedantic, but could you add the 2.0.0 release as a tag? Just for reference sake if nothing else. Thanks.

Done.
@sebmck Can you use https://gist.github.com/sindresorhus/8435329 or something to do releases? That way this never happens.

@sindresorhus Sure, sorry!

No worries. It's very easy to forget (hence tooling) :)


Custom permission nodes are not working

Custom permission nodes are not working since last patch. (jobs reborn 4.15.2)
Server Type (Spigot/Paperspigot/etc):
Paper version git-Paper-45 (MC: 1.15.1) (Implementing API version 1.15.1-R0.1-SNAPSHOT)
Previous version: git-Paper-32 (MC: 1.15.1)
Relevant plugins (Delete if this isn't needed):
LuckPerms

Which permission nodes are not working?

I'm guessing, but probably related to this from Zrips Discord:
    # permissions granted for joining class
    permissions:
      # example node
      aaaaaatest.node:
        # true to give, false to revoke
        value: true
        # minimum level needed to grant permission. Use 0 for all levels
        level: 0
      aaaaaatest.node2:
        value: true
        # Permission granted when reaching level 10
        level: 10
    # Permissions granted when particular conditions are meet

The above was posted by in the 💬-help~2 channel within JobsReborn.
They mentioned using their own custom permission nodes in their configuration but ever since JobsReborn 4.15.2 they have stopped working.

https://github.com/Zrips/Jobs/issues/150 See my comment

Then why does it have the settings? You should take it out if it doesn't work.

Well, if something doesn't work, it doesn't have to be deleted; So far, I can tell you that if anyone has an idea to fix this, we are waiting for the PR to open it or maybe @Zrips will try to fix it.

I hope for the best. I think the function is really important. :)

Is this the issue ? when I updated jobs it changed my permission nodes
from
      mcmmo.perks.xp.10percentboost.alchemy:
        value: true
        level: 25

to
      mcmmo:
        perks:
          xp:
            10percentboost:
              alchemy:
                value: true
                level: 25

@Blackyvk Temporary fix: https://github.com/Zrips/Jobs/commit/118b6d84594bf7f4b70b26acf4f023712ef1e23f

it did not work, I compiled and tried but perms still changed
I tested version  4.15.1 and perms dont change, so something after that version broke it.

it did not work, I compiled and tried but perms still changed
I tested version 4.15.1 and perms dont change, so something after that version broke it.

You should use "_" mark for permission name section instead of "." dots.
Eg
permissions:
    some_perm:

Someone found a fix for this?

Seems to be this works correctly.
Correct usage:
permissions:
  fly:
    value: true
    permission: essentials.fly
    level: 2


Add rust 2018 keywords to sanitization list

I added async, await and try from this list:
https://rust-lang-nursery.github.io/edition-guide/rust-2018/module-system/raw-identifiers.html#new-keywords

bors r+

Build passed, merged manually.


PHP onbuild image is missing

Hi,
The onbuild image is missing, so working with the php-grpc-client container as documented won't work. The files are missing.
Scott

Wh00ps! You are 100% correct. Let me test the image, make sure it builds, and I'll get that uploaded early next week.

Thanks for replying.
It would also be cool, if the README.md would also cover the Greeter example, maybe also asking the user, if they want to test the client properly, to fire up the Node server.
Also, is the "localhost:50051" the correct setting in the client for working with the Node server? I am having trouble making a connection at all.
If I can ever get a connection working, I'd be glad to offer up a PR to improve the docs.
 I've been turning circles for a few days now. The only differences I have is I am using php-fpm and nginx. Despite that, I've also tried the apache version.
This is what I have up till now.
https://github.com/skooppaos/grpc-php-demo
Scott

So I'm going to restrict my response to this bug to the initially reported issue - but suggest you follow the quickstart in the mean time.
http://www.grpc.io/docs/quickstart/php.html
If you are having wider issues outside of this repository, I suggest contacting the mailing list or gitter, which can be found on the community page: http://www.grpc.io/community/

The quickstart is not aimed at a Docker installation, but rather a local install, which sort of defeats the purpose of microservices. And you have to admit, gRPC is supposed to work with Docker from the start as the containerization platform for microservices. It's what Kubernetes uses.
I've gotten a bit further and now know, the PHP container can communicate with the node container. However, I can't tell if the call to the node server is working properly or if the message reply isn't getting through. I'm going to dig deeper.
Maybe the onbuild version might help me too, because maybe I am building the PHP container wrong. So, if you could fix that, it would be another angle of attack for me.
Scott

Okay - there is now a php-onbuild image.
https://hub.docker.com/r/grpc/php/tags/
@nathanielmanistaatgoogle , @nicolasnoble I feel this issue can be closed now.
@smolinari - Personally, I wouldn't use these images for production builds - I'd use them for development build / CI / CD systems (see my thoughts) - there is little reason to have the full development toolchain in your Docker image. As we get more releases for gRPC, I will likely file a PR to remove the on-build images, because as I can see, they are confusing for this reason (and update the README, so this is more clear)

Thanks for fixing the missing image. I'll close the issue.
For sure these images aren't "finished". They are a start.
As for Java, you can use a pre-built Java images in the dockerfile (if the repo is a trusted source) and just go from there. There is no reason not to have a finished Java gRPC containers set up.
In general too and I am sure you know this, I've found it is easier to work with volumes, because then the developer can change files locally and have them also change in the container immediately. This saves the effort of continually having to build the container and run it, in order to get any changes into it.  Also, using docker-compose allows the developer to develop with a number of "services" at one time with fewer commands to get them all "up" and running to work with them  (my repo demonstrates them both).
In fact, it would make a lot more sense and sell gRPC better to have a client and server container setup with each language in a docker compose file, demonstrating hello world. In other words, it would be cool to just docker-compose up -d within each languages version and then go to either a console or a browser and to call on the client to get the "hello world" message from the server. Right now, the PHP container does nothing except respond with the client object. What everyone needs is a working gRPC message from the server in the response from the client. 😄
Scott


Minimum size of empty pane is fairly big

This is a follow up on PR #21334, where I made the comment below. We decided to address it at a later time in order to merge the PR.

One thing I noticed when I recorded the video in https://github.com/spyder-ide/spyder/issues/21145#issuecomment-1652476933 is that the minimum size of an empty pane is quite big, certainly larger than when the pane is not empty. It is not possible to make the Variable Explorer pane any smaller at the start of the video, when the pane is empty,

Originally posted by @jitseniesen in https://github.com/spyder-ide/spyder/issues/21134#issuecomment-1653457013

An easy (though perhaps too simple) solution is to set the minimum size of the picture in an empty pane to 1x1. This allows the pane to be roughly twice as small, as shown in the video.
https://github.com/spyder-ide/spyder/assets/7941918/1bea6ad5-6179-4161-ad9a-bb67ab1fd104
For comparison, below is the current situation. The empty panes take up twice as much vertical space as the console and it is not possible to shrink the empty panes.
https://github.com/spyder-ide/spyder/assets/7941918/0f1d07da-6e52-4a70-b18a-b1a4f102ff06
I can prepare a PR (it's a one-line change) if we like this approach.

That's an interesting suggestion but I'm not so sure about its UX because the image doesn't shrink automatically when the pane's height is decreased, it's collapsed on the top instead.
Another possible solution could be to add a new option to Preferences > Application > Panes called Show message on empty panes (enabled by default) and use that option in all plugins that show those messages to decide if they should do it at startup.

@ccordoba12 wrote:

That's an interesting suggestion but I'm not so sure about its UX because the image doesn't shrink automatically when the pane's height is decreased, it's collapsed on the top instead.

Shrinking the image should be possible but it will be more than one line of code. I'll think about how to achieve this.

Another possible solution could be to add a new option to Preferences > Application > Panes called Show message on empty panes (enabled by default) and use that option in all plugins that show those messages to decide if they should do it at startup.

I don't think that addresses my main concern (which I may well have never explained). Suppose that there are no plots, so the Plots pane is empty, but there are some variables. If the Variable Explorer pane is visible and the Plots pane is "behind" it, then the empty Plots pane constrains how much the user can shrink the Variable Explorer pane. The result is that the user can't shrink the Variable Explorer pane as much as they would expect. I think most users would not realize that the reason for this is the empty Plots pane (it took me a while to figure this out).
If you do know the reason, then you can just close the empty Plots pane to resolve the issue, so having a new option is not absolutely necessary. I also think that the text is quite nice to have so I don't want to hide it. The picture on the other hand is eye candy, it looks good but it does not convey any information. I don't like it that a non-functional UI element prevents the user from doing what they want to do (shrinking the pane).
However, this is only a real issue for small window sizes (less than around 800 pixels in height), or if the user increases the size of the font and other UI elements (as you would do for a presentation). So arguably it is not critical for the Spyder 6 release.

Shrinking the image should be possible but it will be more than one line of code. I'll think about how to achieve this.

A possibility that occurs to me is to add a method to PaneEmptyWidget that works in resizeEvent and descreases the rescale factor of the image when there's no vertical space available (I don't know how to detect the last part, but the other things should be doable).

I don't think that addresses my main concern (which I may well have never explained). Suppose that there are no plots, so the Plots pane is empty, but there are some variables. If the Variable Explorer pane is visible and the Plots pane is "behind" it, then the empty Plots pane constrains how much the user can shrink the Variable Explorer pane. The result is that the user can't shrink the Variable Explorer pane as much as they would expect. I think most users would not realize that the reason for this is the empty Plots pane (it took me a while to figure this out).

Ok, I understand your point of view better now. Then we could follow your proposed solution for 6.0 and improve it in a later release.

Hi, I posted https://github.com/spyder-ide/spyder/issues/22586. Agreed that its the same issue as discussed here, but I wanted to bring a little more heat to it. Its effectively the same as @jitseniesen comment, but for me, kind of reversed in that I often want to make the upper pane smaller so I can see more of the console or command history. Not being able to do this is a pretty big UX issue IMO. I'm curious why this has become an issue - resizing worked fine in previous versions (in 5.4.3 at least).

Not being able to do this is a pretty big UX issue IMO.

I wouldn't say big, but annoying for sure.

Per some of the comments above, why can't the panes just be empty, as they are in 5.4.3?

Because there's a lot of empty space in Spyder and it's not easy for newbies to understand how it can be filled.


Replace MongoDB with Postgres for Imminence

Updates Imminence to use PG+PostGIS rather than MongoDB.
Related PRS:
https://github.com/alphagov/imminence/pull/766
Trello:
https://trello.com/c/R6Lb3vYa/1611-move-imminence-away-from-mongodb-onto-postgres

We're now on PG in production, so this PR's time has come.


Deprecate be_same_time_as and custom have_attributes matchers

For have_attributes, see https://github.com/ManageIQ/manageiq/pull/11474 and other places where we've wasted time trying to figure out why RSpec's composable matchers don't work here.
For be_same_time_as, as don't need it now that we no longer support SQL Server. The original reasoning for this matcher was to coordinate varying precision between Ruby, Postgres, SQL Server. Now we don't support SQL Server so it really doesn't matter.
expect(time_value_under_test).to be_within(0.1).of(expected_time_value)
expect(time_value_under_test.to be_same_time_as(expected_time_value.precision(1)

expect(a_thing).to receive(:a_method_with_start_time).with(a_value_within(0.1).of(start_time))
expect(a_thing).to receive(:a_method_with_start_time).with(be_same_time_as(start_time.precision(1))

Obligatory "Sorry, Keenan" comment to be seen when he tracks this PR down after seeing the deprecations on Travis.

LGTM, a sentence about why we originally had this (it didn't exist... there was no way to compare times with varying subsecond precision)... then sql server had didn't precision that we had to deal with blah blah blah... and how we don't need this anymore because 🔥 🗑  sqlserver 🔥 🗑

@jrafanie Added to PR description and commit message.

@Fryguy you had lots of comments so I'll let you review the changes and merge

Obligatory "Sorry, Keenan" comment to be seen when he tracks this PR down after seeing the deprecations on Travis.

@chrisarcand I notice you didn't say @kbrock in your comment. I'm guessing as to not attract my attention.

@chrisarcand we should have placed wagers on how long until @kbrock fines this PR.  15 days is impressive.


Remove flash of unstyled content

When adding links, Shadow DOM have to properly load the stylesheet before using it. By directly getting the document stylesheets, the flash of unstyled content disappears.

This would throw for cross-origin <link>s.

Seems way better now, with correct cross-origin requests. The idea is to wait the styles are loaded before painting. Nice thing, when using a bundler like vite (which inject the CSS in style nodes), there's no wait for it.
What do you think?

@ghivert and I discussed this on discord: closing this because it's fixed on main now, thanks!


Focused and Launcher modules attempt to render unknown image types.

Describe the bug
Possibly due to flatpak'd versions of Spotify and Discord (and otherwise icon-missing applications), apps that don't properly have an icon do not get verified, and an error is printed.
To Reproduce
Steps to reproduce the behavior:

Use launcher or focused with show_icon
Have an app that either doesn't have an icon or otherwise isn't in the correct location
Launch ironbar, observe errors upon loading icons for the app.

Expected behavior
Either a warning and/or discarding or sanitizing of related items
System information:

Distro: Arch
Compositor: Hyprland
Ironbar version: Ironbar version 0.12.1 via ironbar --version on aur/ironbar-git

Configuration
https://f.cloudninja.pw/ironbar_config.json
Screenshot

Will improve the error handling around this to try and rule out some of the non-errors, reduce missing images to warnings, and avoid printing the full stack.

When focusing an app for which it cannot find an icon (though Anyrun does find the icon), ironbar does indeed just print a warning, however it still renders the icon for the last focused app.
For example, if I move focus from Firefox to Supersonic (AUR package supersonic-desktop), ironbar fails to find Supersonic's icon and instead renders Firefox's icon.

Thanks for reporting. I've opened an issue to track that and should get it sorted soon.


Update of node_modules

https://github.com/cloudflare/doca/issues/19
This PR doesn't add, remove or change any features. However, it updates most of the doca project dependencies. The biggest change is the migration to Webpack2 (released today!).
It was necessary to update and release new versions of

json-schema-loader
json-schema-example-loader

since the API for loaders is slightly different (this.inputValue was removed). It's a minor change but I bumped their major versions, so it's clear that the update of both is needed for doca v0.1.0 (this PR). Also, both loaders are still compatible with webpack1. The only requirement is to use a matching major version since they are chained.
There are also a lot of "typo fixes" since some new eslint rules were introduced. That applies for both doca CLI itself and doca/app.
Once this PR is merged, I will update our internal cf-api and publish this package.

I'm going to leave this for @toekneestuck as I don't know webpack and can't make heads or tails of this :-)