Effectively Zero Options

The 'Manual registration' workflow is the only viable workflow from the way this article reads. I have been struggling with consistency in AutoPilot for months now, and I am to understand that the device must not be currently on the internet when registered? The device must not have EVER been on the internet when registered? It is not clear. What this article describes is a scenario where a device must be in OOBE , and not connected to the Internet for Autopilot to work correctly. This leaves only one reasonably viable registration process, namely , the Partner side-loading through the portal before the hardware is received. I am I totally misunderstanding these options?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3243b015-5b5f-7a62-0d9d-767d729dc475
Version Independent ID: ff8c0509-c075-8528-823f-c195ff4d2382
Content: Adding devices
Content Source: windows/deployment/windows-autopilot/add-devices.md
Product: w10
GitHub Login: @greg-lindsay
Microsoft Alias: greg-lindsay

@officedocsbot assign @mypil

@PrinceMarkieD - Thank you for submitting feedback.
I will get this issue over to the Win10 ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Dear @PrinceMarkieD ,
The 'Manual registration' workflow is the only viable workflow from the way this article reads. - there are two options:

Registration by OEM: in the article "Ideally, this would be performed by the OEM, reseller, or distributor from which the devices were purchased"
Manual registration: the rest of the article focused on it.

The device must not have EVER been on the internet when registered? - yes, it must not have ever been connected to the internet, otherwise, device will download blank profile. In this case, to add device to autopilot, you need put it back to OOBE state.
This leaves only one reasonably viable registration process, namely , the Partner side-loading through the portal before the hardware is received. - no, you can still load it manually, after receiving (you may need to reimage device)
So, to make long story short:

in case OEM didn't uploaded deviceid to autopilot, you can do it manually
collect device id and upload it before connecting device to the internet
if you already connected it to internet - you need to restart OOBE

Thank you

Thank you so much for the verification. This functionality is congruent
with what I understood to be the default behavior of auto-pilot. I think
that the article confuses this unintentionally. If it were stated this way:
"Autopilot OOBE will only take effect for a device that is
SysPrepped/Generalized. So if a device is already in use, and has been on
the internet the device will have to have the Windows 10 OS re-installed
fresh."
This leaves the question of will the device respect an autopilot profile
that has been uploaded from an internet active OS, if that OS is placed
into "Reset This PC" scenario.?
I find this article interesting because coincidentally I have always fresh
installed my devices just because it is FAR faster than "Reset This PC". I
now wonder if that means my AP profile would eventually break?
Also I do the same thing with VMware Workstation VMs. I save the state at
OOBE, and rapidly test Autopilot profile by going back to the OOBE save
state, and restarting the computer. I use the Same Auto-pilot profile but i
effectively "Reset" the PC because the snapshot I return to is just before
the computer boots into OOBE for the first time.
I wonder if that is a mistake lab situation. I will lay it out the way you
did for clarity; the two ways i test AutoPilot.
Physical Devices (when testing AutoPilot Zero touch deployment)
Vanilla Windows 10 Ent installed to device with TPM2.0.

At the first language selection of OOBE, open Powershell.
*Rename the device so it gets into an Azure AD Group Dynamically (have not
found a more controllable dynamic method because ZTID is too broad)
*Use Auto-pilot script to save the CSV to the inserted WIn10 install USB.
Copy the CSV to technician station. Upload CSV to Intune etc etc.
Reboot the test device
*AutoPilot works.
* For subsequent provisioning test on PHYSICAL devices.
Re-install the Windows 10 OS to experience the AutoPilot OOBE again.

On Virtual Machines inside VMware Workstation on my Technician workstations
*Same process as above until you get to the "Reboot the Test Device" step.

Shutdown the test device, and grab a snapshot of the VM before starting
it up again to continue OOBE"
*AutoPilot works as long as you do not expect to use the TPM2.0 dependent
function of Zero-touch Self-Deployment Preview (couldn't think of the name
above.)
* For subsequent provisioning test "Roll back to the previous
snapshot" Delete the device from Intune.

Thank you for this good exchange, i know I am not the only person totally
confused by this article.
On Wed, Mar 27, 2019 at 7:43 AM MaratMussabekov<EMAIL_ADDRESS>wrote:

Dear @PrinceMarkieD https://github.com/PrinceMarkieD ,
The 'Manual registration' workflow is the only viable workflow from the
way this article reads. - there are two options:

Registration by OEM: in the article "Ideally, this would be
performed by the OEM, reseller, or distributor from which the devices were
purchased"
Manual registration: the rest of the article focused on it.

The device must not have EVER been on the internet when registered? -
yes, it must not have ever been connected to the internet, otherwise,
device will download blank profile. In this case, to add device to
autopilot, you need put it back to OOBE state.
This leaves only one reasonably viable registration process, namely , the
Partner side-loading through the portal before the hardware is received.

no, you can still load it manually, after receiving (you may need to
reimage device)

So, to make long story short:

in case OEM didn't uploaded deviceid to autopilot, you can do it
manually
collect device id and upload it before connecting device to the
internet
if you already connected it to internet - you need to restart OOBE

Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/2951#issuecomment-477135329,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aeitv4jXiSkLA8FSYUzSELL7bd5NpGCLks5va2eCgaJpZM4b3-t1
.

Dear @PrinceMarkieD ,
This leaves the question of will the device respect an autopilot profile that has been uploaded from an internet active OS, if that OS is placed into "Reset This PC" scenario.? - no, after "Reset This PC" you can collect device hash and upload it too, the same as after fresh installation (because from the OS perspective, resetting is the same as reinstallation). Also from the article "the only way to clear the stored profile is to re-install the OS, reimage the PC, or run sysprep /generalize /oobe. "
I now wonder if that means my AP profile would eventually break? - could you please clarify, what do you mean by "break"? you can reset and reinstall your PC, that doesn't affect your AP account as it is stored in the cloud
Also I do the same thing with VMware Workstation VMs. I save the state at OOBE, and rapidly test Autopilot profile by going back to the OOBE save state, and restarting the computer. I use the Same Auto-pilot profile but i effectively "Reset" the PC because the snapshot I return to is just before the computer boots into OOBE for the first time.  - and what the result? which issue do you experience?
Also, which information do you think should be added/rewritten in this article to make it less confusing?
Thank you

@PrinceMarkieD - From our understanding, the issue you raised has been answered by MaratMussabekov. If you feel it hasn't been answered, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close

Just make a flow chart that makes sense. If I gather the device hash from my pc RIGHT NOW, is it the same hash as if i gather it during the OOBE? You guys need to make it clear that people are expected to get this hash during a point when most normal users don't even know how to get to a command prompt.

Dear @PrinceMarkieD ,
If I gather the device hash from my pc RIGHT NOW, is it the same hash as if i gather it during the OOBE? - yes, it is the same. More details here Windows Autopilot FAQ
most normal users don't even know how to get to a command prompt - Could you please clarify?  Autopilot is a product designed to be administrated by IT Department, I am not sure which command that should be run by users you are talking about.
Thank you

Okay thank you. I think i can explain now what will make it more clear. Please make a step by step graphic, that explains to people who to reach the Autopilot OOBE. Starting from the Windows desktop. , and Starting with a Device that has never been powered on and connected to the internet. If you do this; it will not be confusing anymore. Thank you for this correspondence! this was amazing!
I have a new question now: Should i start a new thread?


cmd/compile: k8s scalability load test failure (latency regression) with unified IR

Kubernetes runs a nightly load test built with Go tip. Recently there was a regression in latency that caused various thresholds to be exceeded.
(See the "gathering measurements step," though that on its own isn't very descriptive.)
The team has narrowed the culprit down to
833367e98a internal/buildcfg: enable unified IR by default

It's unclear at this time what the issue is. We're currently waiting on more metrics to investigate this more thoroughly.
CC @mdempsky

Assigning to myself for now to gather more information.

Just to confirm, this is an issue with run-time code being slower? Like it's not a problem with the compiler having slowed down too much?
One thing that comes to mind is inlining is somewhat (inlining cost analysis, because IR has changed; which function bodies are available to inline, because export data format has changed).

Nope, it's about code at runtime. Now that I'm looking at some of the graphs, it actually looks more like occasional stalls than a uniform slowdown, though I think there is some smaller uniform impact on tail latencies as well in between those stalls as well (unclear if they're related yet).
Here's what the API call latency looks like over time (note the threshold for the first graph is 1 second):

And here's some GC-related statistics (note the breaks in the graphs that line up with the spikes):

Kubernetes reports this is fixed since 6a801d3.


question-answer data generation: a new flow and other updates

Implement the flow to generate quetion-answer pairs from descriptive text files.
Add more comments to example jupyter notebooks
Manage openai key with python-dotenv
Manage package dependencies with poetry. NOTE: Download the en_core_web_sm model manually since
it is not in pypl.
Improve the file structure for question-answer generation.

LGTM!


Specify dates presented on stats page

What you want
Ability to specify the interval in which the data is collected an the statistics page.
Show metrics resolved on day a week to see differences on weekends.
Why you want it
Useful for viewing developments in data, problematic times.

Hello:
I'm not sure I understand perfectly the feature you request but I think that it's what I need too:
In France (and apparently in other countries), the auto-measurement process requires to take several measures during 3 consecutive days (3 measures each morning, 3 measures each evening).
What would be really useful in the app would be the ability to get the average blood pressure information for these 3 days only (and maybe a special report to view and export only the measures of these 3 days and the related average figures).
If it's another request than this one, I can create another issue.
Thanks in advance!

@tb06 this results in 3 features actually ;) but don't worry I can handle it.
The way I understand this,

you want to be able to fully specify the range in which data is queried (created #97)
you want to have the data-range selection on the stats page as well as on the export page (this issue)
you want PDF export (#30)

If I got anything wrong, feel free to correct me.
1 and 2 can be done relatively quickly and will be in the next release, while 3 might take some more time.

@tb06 this results in 3 features actually ;) but don't worry I can handle it.
The way I understand this,
1. you want to be able to fully specify the range in which data is queried (created [manual data range option #97](https://github.com/NobodyForNothing/blood-pressure-monitor-fl/issues/97))

2. you want to have the data-range selection on the stats page as well as on the export page (this issue)

3. you want PDF export ([Exports for other use #30](https://github.com/NobodyForNothing/blood-pressure-monitor-fl/issues/30))

If I got anything wrong, feel free to correct me.
1 and 2 can be done relatively quickly and will be in the next release, while 3 might take some more time.

Hello @NobodyForNothing:
You're perfectly right, thanks a lot!
Thomas.


form.js addInlineField creates incorrect id for new nested elements

The problem appears with rendering new nested elements for MongoEngine.
When you create a new nested element for another new element (not yet saved) form.js puts an extra "-" in the id and this results in the parent element saved empty (the nested elements fail).
For example I use mapping for some elements with a Mongo field like this:
ListField(ListField(StringField())).
I solved this problem by adding additional check that elID exists (it doesn't exist yet for the new parent element):
https://github.com/ngr/flask-admin/commit/36d4b33bae4f45b4af131a32737edadbfcea2e81
Is this OK and should I create a pull request?

The fix is in the pull request:
https://github.com/flask-admin/flask-admin/pull/1102


Added Shell Sort [Javascript]

Fixes #290
By submitting this pull request I confirm I've read and complied with the below declarations.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the coding guidelines for this project.
[x] My code follows the skeleton code structure.
[x] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.

@mohitkyadav Add comments to functon about params and return values.


The potential for Sound speed estimation and Phase aberration correction ?

I'm curious about why REFoCUS can help Sound speed estimation and Phase aberration correction ...(。≖ˇェˇ≖｡)
I'm not expert at Sound speed estimation and Phase aberration correction but I know that these two are very important for the quality of the medical ultrasound image. REFoCUS is not hard to understand, and could be more attractive if its relation with Sound speed estimation/Phase aberration correction is more clear.  :)

REFoCUS can recover the single element transmission information from the transmit sequence. This helps by allowing us to correct for phase aberrations on both transmit and receive by applying those corrections on an element-wise basis. The single element transmit also has a broad profile that allows us to perform sound speed tomography using measured phase aberrations.


Dockerized

Added a simple Dockerfile and docker-compose file to allow for quick and easy deployment w/ docker and httpd.

Install docker

Install docker-compose (optional)

From LODmilla-frontend dir, execute:

Using docker
sudo docker build -t lodmilla-frontend .
sudo docker run -p 9999:80 -dit --name lodmilla-frontend lodmilla-frontend

Using docker-compose
sudo docker-compose up --build -d

Open http://localhost:9999/lodmilla/ in a browser.

For additional information on using docker w/ httpd: https://github.com/docker-library/docs/tree/master/httpd

@micsik Thanks for reviewing. I was just experimenting w/ that SPARQL endpoint and didn't mean to include it in this branch - glad you caught it. The PR is back to just the docker files.


table column formatting is not saved in notebook

hence cannot be saved or shared.
also, need API control over the table options settings.
at worst you could have a function to add this information where it is being returned
# python computes regular dataframe df, then as last line of cell:
beaker.columnFormat(df, {'col name': 'format xyz', ...})

or perhaps store the formatting dict in the data frame, could we subclass?
is there a way to store the formatting so it survives evaluation?

in pandas looks like you can set precision and date formatting for the whole dataframe, not per column.
but we could import and preserve: http://pandas.pydata.org/pandas-docs/stable/options.html

this was done eventually
https://github.com/twosigma/beaker-notebook/issues/3685


Integration

Platform and Workloads tested step by step from local. Please merge, so can test end to end.

/gcbrun


Missing Options

Hello,
i have set up the USB connecting for my switch because i got problems while using PokerCore with sysbotbase, But when i connect now via USB, some options like Bulldozer and Map Dropper aren`t available anymore.

Greetings.

USB-botbase has a very slow speed while accessing a large amount of data.
For example, the map data takes over 2 minutes just to load. Writing to the memory also takes very long to finish.
It creates many problems when the writing process takes too long and could corrupt your save files if it is interrupted in the middle.
That is why those functions that could write a large amount of data have been disabled.
Unless there is a faster implementation of USB-botbase, there is no way to fix it at the moment.

Thank you for you reply!Alright, then I’ll try sysbot again.Greetings.Von meinem iPhone gesendetAm 20.03.2024 um 14:38 schrieb MyShiLingStar @.***>:
USB-botbase has a very slow speed while accessing a large amount of data.
For example, the map data takes over 2 minutes just to load. Writing to the memory also takes very long to finish.
It creates many problems when the writing process takes too long and could corrupt your save files if it is interrupted in the middle.
That is why those functions that could write a large amount of data have been disabled.
Unless there is a faster implementation of USB-botbase, there is no way to fix it at the moment.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


chore: update electron-debug

Overview
update electron-debug version to v3.2.0.
the latest version is v4.0.0 but the requirements are node v18( ✅) and electron v30 (❌)
I think the next Electron update will be in the next release at the earliest.

Test Plan and Hands on Testing
run make teardown-js && make setup-js then make -C app dev
check you can open chrome dev tools without clicking toggle dev tools a couple of times.

Changelog

Review requests

Risk assessment
low

same, thanks @koji!


AMBARI-23945. Infra Solr migration: REQUESTSTATUS response content ty…

…pe is xml instead of json
What changes were proposed in this pull request?
with solr 5 the default response content type is xml, so the REQUESTSTATUS command can fail when we are reading the response object.
How was this patch tested?
manually
please review @zeroflag @fimugdha

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3064/
Test PASSed.


[Parquet][C++][Python] Bump the default format version from 2.4 -> 2.6

Describe the enhancement requested
Parquet format version 2.6 introduces the NanoSecond time unit for Time and Timestamp logical types.
Component(s)
Parquet

I found that our implemention already supports Timestamp:
/// \brief Allowed for physical type INT64.
class PARQUET_EXPORT TimestampLogicalType : public LogicalType {
 public:
  static std::shared_ptr<const LogicalType> Make(bool is_adjusted_to_utc,
                                                 LogicalType::TimeUnit::unit time_unit,
                                                 bool is_from_converted_type = false,
                                                 bool force_set_converted_type = false);
  bool is_adjusted_to_utc() const;
  LogicalType::TimeUnit::unit time_unit() const;

  /// \brief If true, will not set LogicalType in Thrift metadata
  bool is_from_converted_type() const;

  /// \brief If true, will set ConvertedType for micros and millis
  /// resolution in legacy ConvertedType Thrift metadata
  bool force_set_converted_type() const;

 private:
  TimestampLogicalType() = default;
};

And timeunit has NANO
  struct TimeUnit {
    enum unit { UNKNOWN = 0, MILLIS = 1, MICROS, NANOS };
  };

Do we already supports them?
/cc @wgtmac

Have you tried:
::parquet::WriterProperties::Builder()
                                            .version(ParquetVersion::PARQUET_2_6)
                                            ->build();

Yes, we indeed already support that version, but we default to 2.4 at the moment. I edited the title that the issue is about changing the default version.
The default in C++:
https://github.com/apache/arrow/blob/6d2df074e624a6a4462a1539be8dadf19cf39df4/cpp/src/parquet/properties.h#L207-L221
And similarly in the Python bindings the default is also "2.4".

It seems that parquet-cpp has implemented features (e.g. modular encryption and BYTE_STREAM_SPLIT encoding) beyond version 2.6. We probably need to update supported versions and manage features based on the version.
https://github.com/apache/parquet-format/blob/master/CHANGES.md

It seems that parquet-cpp has implemented features (e.g. modular encryption and BYTE_STREAM_SPLIT encoding) beyond version 2.6. We probably need to update supported versions and manage features based on the version.
https://github.com/apache/parquet-format/blob/master/CHANGES.md

We can open issue about this, I can take time to fix it.

Ok, so parquet-mr implemented nanosecond precision timestamps in 2018: https://github.com/apache/parquet-mr/pull/519
while we did so in 2018 (basic support) and 2019 (Arrow roundtrip):
https://github.com/apache/arrow/pull/4185
https://github.com/apache/arrow/pull/4421
I think this makes it ok to bump the default to 2.6.


Issue 258: Add index hints for select and update

Close https://github.com/uptrace/bun/issues/258

@vmihailenco Hello! I added some functionality, could you check it plz? And I have a question:
Index hints is supporting only for MySQL. What I should do for other databases?

:+1:

What I should do for other databases?

Just ignore the hints when they are not supported.

Please also add some tests to https://github.com/uptrace/bun/blob/master/internal/dbtest/query_test.go

@vmihailenco I want to add ForceIndex and IgnoreIndex, is it ok if I do it in this PR?

@vmihailenco Fuuh, I added support for all index hints (use, ignore, force)

Is there a specific reason why UseIndex discard previous indexes? For example, the following behavior is surprising and inconsistent so we need a good reason/explanation why it is done so:
q.Table("one").Table("two") // generates FROM one, two

q.UseIndex("one").UseIndex("two") // generates USE INDEX (two)

@vmihailenco Yeah, it was a bug. Fixed

Thanks for your work :+1: This is good enough so I am merging this, but please consider https://github.com/uptrace/bun/pull/577#discussion_r909249720


EF core 3 global query filter cannot translate contain expression

In the EF Core version 2.2 i can create a query filter with contain as the filtering expression, in the version 3.0 it will throw exception that showing it cannot be translated.
Steps to reproduce
In the db context class create an entity with query filter
protected override void OnModelCreating(ModelBuilder modelBuilder)
        {

            base.OnModelCreating(modelBuilder);
modelBuilder.Entity<Company>().HasQueryFilter(c =>
          _companyCodes.Contains(c.Code));
}

The filter will always produce exception:
The LINQ expression 'Where<Company>(     source: DbSet<Company>,      predicate: (c) => (Unhandled parameter: __ef_filter__p_0) || (Unhandled parameter: __ef_filter___companyCodes_1).Contains(c.Code))' could not be translated. Either rewrite the query in a form that can be translated, or switch to client evaluation explicitly by inserting a call to either AsEnumerable(), AsAsyncEnumerable(), ToList(), or ToListAsync(). See https://go.microsoft.com/fwlink/?linkid=2101038 for more information.
As it is located in the queryfilter i cannot use asasyncenumberable or to list, how to mitigate this issue in ef 3 ?
Further technical details
EF Core version: 3.0
Database provider:  Microsoft.EntityFrameworkCore.SqlServer
Target framework:  .NET Core 3.0
Operating system: Windows 10
IDE: Visual Studio 2019 16.3.5

What is the type of _companyCodes?

The companyCode is guid.

Could be duplicate of #17342
Can you try running with 3.1-preview1 package?

Hi smith, already and got same result.

@dimz87 - can you share a small repro code which demonstrate the issue?

@dimz87 - can you share a small repro code which demonstrate the issue?

Sorry, i have clarify my comment, pleas see my comment


[release-4.13] bump github.com/containers/buildah to v1.29.2

Bump github.com/containers/buildah from v1.29.0 to v1.29.2.

/test e2e-aws-ovn-proxy


adding configs + testing on ztls

related to:

https://github.com/projectdiscovery/nuclei/issues/2805#event-7933132142

Not planned - Fastdialer shouldn't enforce any settings


Record "described" activities

Record that a user has added the weather to an activity and add a new function to return a list of these activities

Merged and deployed.


Rejected by App Store

The first time I submitted my app which contains JSPatch to app store and last week I found it was rejected. The reply indicates that,

During review, your app installed or launched executable code, which is a violation of the App Store Review Guidelines. Specifically, your app uses the itms-services URL scheme to install an application.

I appealed the rejection by pointing out "The only exception to the foregoing is scripts and code downloaded and run by Apple's built-in WebKit framework or JavascriptCore, provided that such scripts and code do not change the primary purpose of the Application", as the Agreement says. And unfortunately they rejected me again by specifically saying,

Your app contains an SDK designed to update the app outside of the App Store process. It would be appropriate to remove this SDK before resubmitting for review.

I don't have any other similar libs except JSPatch. It seems not allowed by App Store. I'm still looking for efficient ways to appeal and I hope this risk of being rejected could be warned in Readme or somewhere.

Hi, seems that your first rejection is not cause by JSPatch, is some
feature that "uses the itms-services URL scheme to install an application.".
Maybe after your reply, the AppStore Reviewer realize that your App has
ability to update the App and they reject it.
Lot's of Apps like has been using JSPatch and they successfully pass the
review, maybe you can try to remove JSPatch this version, and add back in
the next version.
On Tue, Sep 15, 2015 at 3:41 PM, Qin Yubo<EMAIL_ADDRESS>wrote:

The first time I submitted my app which contains JSPatch to app store and
last week I found it was rejected. The reply indicates that,
During review, your app installed or launched executable code, which is a
violation of the App Store Review Guidelines. Specifically, your app uses
the itms-services URL scheme to install an application.
I appealed the rejection by pointing out "The only exception to the
foregoing is scripts and code downloaded and run by Apple's built-in WebKit
framework or JavascriptCore, provided that such scripts and code do not
change the primary purpose of the Application", as the Agreement says. And
unfortunately they rejected me again by specifically saying,
Your app contains an SDK designed to update the app outside of the App
Store process. It would be appropriate to remove this SDK before
resubmitting for review.
I don't have any other similar libs except JSPatch. It seems not allowed
by App Store. I'm still looking for efficient ways to appeal and I hope
this risk of being rejected could be warned in Readme or somewhere.
—
Reply to this email directly or view it on GitHub
https://github.com/bang590/JSPatch/issues/111.

Seems that your first rejection is not cause by JSPatch, is some
feature that "uses the itms-services URL scheme to install an application". Maybe your App contain a webview or link to install Enterprise Edition App?
For the second rejection, I don't quite sure is it means JSPatch, lot's of Apps like has been using JSPatch and they successfully pass the review, maybe you can try to remove JSPatch this version, and add back in the next version. Before that you should solved the "itms-services" issue first.

Well I think the mentioned 'itms-services URL scheme' refers to the mechanism of using JSPatch to execute javascript from server. What I was appealing is that it's not intendedly used for 'update outside of the App Store process'. I do know JSPatch is completely comply with Apple's requirements 'cause at least Facebook uses much more JS that it. The only problem seems to be how to argue with Apple.
Happy to hear there're precedents using JSPatch on sale. But also you reminds me that the rejection may have something to do with the fact that what I submitted was the initial version of the app. I've removed JSPatch waiting to see if it could be approved.


Added new commands.

added 'git rm --cached ' and 'git checkout  -- file'

Hey @ScarletPixie all contributions are welcome feel free to suggest something if you want.


College of Medicine Effort Integration: Rounding error

Errors in COM Effort (ume_faculty_effort):
Nicole found that the years (Event_Date) are rounding to 2020 instead of the actual year (2023). Also the hours (UME_CALCULATED_TEACHING_WHILE_NON_BILLING_EFFORT__HRS_) are rounding to an integer value instead of the exact value.

These bugs are related to #36


inconsistent simp behaviour

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Checked that your issue isn't already filed.

Specifially, check out the wishlist, open RFCs,
or feature requests.

Reduced the issue to a self-contained, reproducible test case.

Description
I can produce a goal for which

simp {single_pass := tt} fails with 'simplify tactic failed to simplify', whereas
simp {max_steps := 20} fails with 'simplify failed, maximum number of steps exceeded'

(and similarly for any value of max_steps).
I would hope that

simp doesn't loop in this example, and
single_pass can be used to diagnose the looping.

Steps to Reproduce
Run the code at https://gist.github.com/semorrison/f304a72c70bd705b7b454311f40f0104.
Versions
Lean (version 3.2.1, commit f55d10bb5095, DEBUG)

(I'm seeing this problem all across my library today.)

This is not a bug. max_steps limit the number of nodes that are visited by simp.
simp {max_steps := 2000}

will also return simplify tactic failed to simplify.

The counter num_steps is incremented in the simplifier main loop.
https://github.com/leanprover/lean/blob/master/src/library/tactic/simplify.cpp#L645

Thanks. Sorry, I was confused.


Allow developers to rename GameObjects with MRTK

Overview
With MRTK in the scene and possibly with SceneSystem enable for service facades, developers were not able to F2 or right click and rename any gameobject in a scene.
This was caused by two operations happening repeatedly while in editor.

MRTK static class would call hierarchyChanged callback and auto-update the name of every MRTK instance. This name update would cause hierarchyChanged to be called again resulting in a never ending sort of recursive operation.

ServiceFacadeHandler would update all gameobjects every editorapplication.update. Not only was this excessive but it would cause the heirachy to change when trying to rename another GameObject.

Both of these operations have been refactored to only execute when an actual change has occurred.
Changes

Fixes: #5062

Verification
Tested service facade in editor and MRTK gameobject in editor to rename another GameObject
All tests passed

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run


Issue: the Lives counter won't go down and the timer will get stuck at 0:00 when the stage restarts

Hello, i'd like to point out that if sonic get's crushed/fall into a pit/etc. the lives count won't drain by 1 and the timer will freeze at 0:00

While the DevControl object is active in a level, the player cannot lose lives; this makes it easier to diagnose problems. By default, DevControl is active in all available levels in the template.
Also, DemoZone2 does not have a ZoneTimeLimit object, and so the timer will not count up in that level. This is meant to demonstrate the modularity of the object system in the template.
Please let me know if you are still experiences these issues even in spite of the above.


Xcode 14.3 beta 2 fails to build SwiftUIBackports - iOS 14 API used

Have you read the Contributing Guidelines?
General Information

Project version:
1.15.0

Platform/OS version:
iOS 15+ (not entirely relevant to this)

IDE version:
Xcode 14.3 beta 2

Any related GitHub issues:

Describe the bug
When attempting to build a project which imports SwiftUIBackports in Xcode 14.3 beta 2, the compiler fails on the file Toolbar.swift with the error Namespace is only available in iOS 14.0 or newer.
The same error doesn't happen in Xcode 14.2, but I'm not sure why that is. Accessing the same Toolbar.swift file and Cmd+right clicking the Namespace property wrapper shows that it was introduced in iOS 14, and the file shouldn't have been successfully building while the package targets iOS 13+.
Steps to reproduce
Add SwiftUIBackports as a dependency to a project targeting any version of iOS with SwiftUI, and attempt to build in Xcode 14.3 beta 2.
Expected behavior
SwiftUIBackports to build correctly
Screenshots
If applicable, add screenshots, gifs, or videos to help explain your problem.

Additional context
In the generated header for Namespace, it's attributed like this:
@available(iOS 14.0, macOS 11.0, tvOS 14.0, watchOS 7.0, *)
@frozen @propertyWrapper public struct Namespace : DynamicProperty {

So I'm really confused as to how it built/worked before 😅

Great point! That shouldn't be there actually! Wow, no idea what's happened here. Thank you!

Closed with #44

Thanks for fixing @rhysm94 – Now available in v1.15.1

No problem @shaps80, glad to help!


HADOOP-17036. TestFTPFileSystem failing as ftp server dir already exists

Fixes a regression causing unit tests to fail as ftp server dir already exists

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
39m 53s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m  7s
trunk passed

+1 :green_heart:
compile
27m  5s
trunk passed

+1 :green_heart:
checkstyle
0m 55s
trunk passed

+1 :green_heart:
mvnsite
1m 39s
trunk passed

+1 :green_heart:
shadedclient
20m 35s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 20s
trunk passed

+0 :ok:
spotbugs
3m 10s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m  6s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 23s
the patch passed

+1 :green_heart:
compile
22m 10s
the patch passed

+1 :green_heart:
javac
22m 10s
the patch passed

+1 :green_heart:
checkstyle
0m 45s
the patch passed

+1 :green_heart:
mvnsite
1m 36s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
16m 11s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  3s
the patch passed

+1 :green_heart:
findbugs
3m 33s
the patch passed

_ Other Tests _

-1 :x:
unit
12m 10s
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m 26s
The patch does not generate ASF License warnings.

187m 18s

Reason
Tests

Failed junit tests
hadoop.ipc.TestRPC

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2009

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 9ea060ff3a82 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 4c53fb9ce10

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/1/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/1/testReport/

Max. process+thread count
2861 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

the following test fails now
java.lang.AssertionError: Expected exactly one metric for name RpcServerExceptionNumOps expected:<1> but was:<0>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:645)
	at org.apache.hadoop.test.MetricsAsserts.checkCaptured(MetricsAsserts.java:278)
	at org.apache.hadoop.test.MetricsAsserts.getLongCounter(MetricsAsserts.java:237)
	at org.apache.hadoop.test.MetricsAsserts.assertCounter(MetricsAsserts.java:231)
	at org.apache.hadoop.ipc.TestRPC.testCallsInternal(TestRPC.java:510)
	at org.apache.hadoop.ipc.TestRPC.testCalls(TestRPC.java:428)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 11s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
21m 25s
trunk passed

+1 :green_heart:
compile
18m  1s
trunk passed

+1 :green_heart:
checkstyle
0m 45s
trunk passed

+1 :green_heart:
mvnsite
1m 21s
trunk passed

+1 :green_heart:
shadedclient
17m 35s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 56s
trunk passed

+0 :ok:
spotbugs
2m  9s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m  6s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 49s
the patch passed

+1 :green_heart:
compile
17m 20s
the patch passed

+1 :green_heart:
javac
17m 20s
the patch passed

+1 :green_heart:
checkstyle
0m 44s
the patch passed

+1 :green_heart:
mvnsite
1m 22s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
15m 32s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 55s
the patch passed

+1 :green_heart:
findbugs
2m 15s
the patch passed

_ Other Tests _

-1 :x:
unit
9m  9s
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 45s
The patch does not generate ASF License warnings.

113m 15s

Reason
Tests

Failed junit tests
hadoop.security.TestRaceWhenRelogin

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2009

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 55abdb811bc0 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 743c2e9071f

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/2/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/2/testReport/

Max. process+thread count
2196 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/2/console

versions
git=2.17.1 maven=3.6.0 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
20m 52s
trunk passed

+1 :green_heart:
compile
18m  1s
trunk passed

+1 :green_heart:
checkstyle
0m 48s
trunk passed

+1 :green_heart:
mvnsite
1m 30s
trunk passed

+1 :green_heart:
shadedclient
16m  4s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 58s
trunk passed

+0 :ok:
spotbugs
2m  9s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m  7s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 54s
the patch passed

+1 :green_heart:
compile
19m 49s
the patch passed

+1 :green_heart:
javac
19m 49s
the patch passed

+1 :green_heart:
checkstyle
0m 57s
the patch passed

+1 :green_heart:
mvnsite
1m 45s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
18m 31s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  5s
the patch passed

+1 :green_heart:
findbugs
2m 51s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
10m 48s
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 53s
The patch does not generate ASF License warnings.

119m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2009

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 60e079b5e251 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 1958cb7c2be

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/3/testReport/

Max. process+thread count
3092 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2009/3/console

versions
git=2.17.1 maven=3.6.0 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

+1, merged.
thanks for a timely followup!


Sensor Detected Incorrectly

I have an MA10320 sensor which is being detected as MA10120, so it thinks the External Temperature Probe is at 71C while the Humidity is Unknown. In fact it is the other way around, the Humidity is 71% but the external temperature is unknown as the probe is not connected.
Sensor Type MA10120 is only temperature, so if Humidity is present it must be MA10320 type sensor.

Thank you for feedback. I've fixed the problem. Could you please check it.

Changes made have fixed the issue. Humidity is now being displayed correctly.


MediaPipe Object Detection crashes  on Android emulators if API > 30

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
Yes
OS Platform and Distribution
Android 11, 12, 13
Mobile device if the issue happens on mobile device
Emulated Pixel 5
Browser and version if the issue happens on browser
No response
Programming Language and version
Kotlin
MediaPipe version
implementation 'com.google.mediapipe:tasks-vision:latest.release'
Bazel version
No response
Solution
Object Detection
Android Studio, NDK, SDK versions (if issue is related to building in Android environment)
No response
Xcode & Tulsi version (if issue is related to building for iOS)
No response
Describe the actual behavior
Fatal exception if API level > 30
Describe the expected behaviour
To work as it does on API level 30
Standalone code/steps you may have used to try to get what you need
D/AndroidRuntime( 7815): Shutting down VM
E/AndroidRuntime( 7815): FATAL EXCEPTION: main
E/AndroidRuntime( 7815): Process: se.ndssoft.mycamx_example, PID: 7815
E/AndroidRuntime( 7815): java.lang.UnsatisfiedLinkError: dlopen failed: library "libmediapipe_tasks_vision_jni.so" not found
E/AndroidRuntime( 7815):        at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
E/AndroidRuntime( 7815):        at java.lang.Runtime.loadLibrary0(Runtime.java:998)
E/AndroidRuntime( 7815):        at java.lang.System.loadLibrary(System.java:1656)
E/AndroidRuntime( 7815):        at com.google.mediapipe.tasks.vision.core.BaseVisionTaskApi.<clinit>(BaseVisionTaskApi.java:37)
E/AndroidRuntime( 7815):        at com.google.mediapipe.tasks.vision.objectdetector.ObjectDetector.createFromOptions(ObjectDetector.java:174)
E/AndroidRuntime( 7815):        at se.ndssoft.mycamx.MycamxPlugin.startCamera$lambda-5(MycamxPlugin.kt:168)

MycamxPlugin.kt:168 follows
objectDetector = ObjectDetector.createFromOptions(mContext, options)

Other info / Complete Logs
My app works on a real Samsung Galaxy S10e, an emulated Pixel 5 API 30 and an emulated Nexus 5 API 30. But it crashes on Pixel 5 API 31 and Nexus 5 API 33 with the message dlopen failed: library "libmediapipe_tasks_vision_jni.so" not found

The medipipe/examples/objectdetection app also crashes when run on an emulator with API > 30. It seems that x86 images are OK, but with x86_64 images mediapipe crashes because libmediapipe_tasks_vision_jni.so cannot be found.

Hi @schmidt-sebastian,
It appears to be similar to the issue https://github.com/google/mediapipe/issues/5100, which has already been reported and is causing crashes on Android emulators. Could you please investigate this issue as well?
Thank you!!!

f I look at the APK file, both debug and release, there is a
libmediapipe_tasks_vision_jni.so for x86, arm64-v8a, and arme-abiv7a, but
not for x86_64. Have you for some reason not compiled MediaPipe for this
architecture??
This bug stops me from releasing my new app since I cannot test it
properly. I would be grateful if you fix this asap.
Den mån 12 feb. 2024 kl 09:36 skrev kuaashish @.***>:

Hi @schmidt-sebastian https://github.com/schmidt-sebastian,
It appears to be similar to the issue #5100
https://github.com/google/mediapipe/issues/5100, which has already been
reported and is causing crashes on Android emulators. Could you please
investigate this issue as well?
Thank you!!!
—
Reply to this email directly, view it on GitHub
https://github.com/google/mediapipe/issues/5134#issuecomment-1938235840,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEN5JJLXELYQBNRYKM46OOTYTHIBJAVCNFSM6AAAAABDC2CDX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZYGIZTKOBUGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@schmidt-sebastian When can you look at this?

Hi @BoHellgren,
We have identified that using an emulator to run this program might not be ideal due to hardware limitations and the program's reliance on specific hardware features for optimal performance. Using a physical device is highly recommended for the best experience and functionality.
Because, Machine learning programs often require direct interaction with real-world hardware resources to function effectively. Emulators, while valuable for development and testing, may not provide the necessary hardware capabilities for this program to run smoothly.  Unfortunately, due to limitations, We can not do much about this issue.
Thank you!!

I agree that testing ML apps in an emulator has its problems. For example, to test your Object Detection sample program, one has to use Extended Controls to mount an image on a wall in the emulated apartment, and then use mouse and QWERASDF keys to move the emulated camera to face the wall with the photo. This does not mean that testing on emulators is useless. On the contrary, unless you have a lot of physical devices, emulators are the only way to test that your app runs on all API levels. Testing on Google Test Lab is not an alternative for ML apps, since you then don't have any control of the camera whatsoever.
I am convinced that you can make MediaPipe run on emulators if you want to, and I urge you to fix this. I think many developers will say no thanks to MediaPipe if they hear that you only support testing on real devices.

Unfortunately, due to limitations, We can not do much about this issue.

@kuaashish
When added via gradle mediapipe literally provides x86 library and does not provide x86_64.
It would crash on a real hardware x64 device. This crash is not due emulator limitations, this is due the missing jni library, lol.
Have you even read the issue, or did you just generated your response using ChatGPT?

Hi @schmidt-sebastian,
Could you please have look into this issue?
Thank you!!

@kuaashish
There are real devices with x86_64 architecture, such as the ASUS ZenFone Series and Lenovo K900. Do you have plans to support these devices?
Additionally, the absence of libmediapipe_tasks_vision_jni.so for x86_64 can result in rejection when publishing to the Google Play Store. What solutions do you suggest for this issue?


Store uploaded images in database

Currently images aren't stored in the database

@PrimalPimmy @osBins can I work on this?

yes, In chat app there should be a image uploader features should be there so I work on it to add this features in you project.


Bugfixes

Update PythonUwpSdkNotFound dialog error message.
Add extra null check
Revert packages guids to match the guids in Dev15.

@zooba  - I tested this fix in the vspreview branch.  There's something wrong with the bcb2 branch.  I can't deploy to the PI for some reason.  I'll look into that later.


Failed in installing pizzly

I tried to install pizzly based on the instructions:
cmake ..
-- The CXX compiler identification is GNU 4.9.4
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8")
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /DataProcess/softwares/pizzly/build
make
Scanning dependencies of target pizzly
[ 50%] Building CXX object CMakeFiles/pizzly.dir/main.cpp.o
[100%] Linking CXX executable pizzly
[100%] Built target pizzly
sudo make install
make: *** Can't create object “install”.  Stop.
So, how couldn't I install pizzly ?

I didn't make an install rule, will fix.
To install it just copy it to /usr/local/bin or any directory that is in your path. You can

OK, thank you very much.

It might be helpful to update the documentation since it still says to run make install, which doesn't work for latest stable release: 96368ca642ed72297ac31e99d0fd77227dd23419


Reinstated deprecated JsArray and JsObject List based constructors for backwards compatibility

I saw that sbt-web was using spray-client 1.3 but spray-json 1.2, so I upgraded it to use spray-json 1.3.  This unfortunately has broken very sbt web plugin that uses JsArray.apply and JsObject.apply, which is a lot of them - they don't do anything complex with spray-json, but they do construct AST.  This change should make the spray-json 1.3 JsValue APIs binary compatible with 1.2, which I think is a good idea anyway given the centrality of the JsValue AST APIs, but would also really help me out.

Note, the only method that actually needs to be reinstated for binary compatibility I think is the JsArray List constructor, but for source compatibility the apply methods are needed.  If you'd rather just reinstate the constructor, I'd be happy with that.

Thanks, James!
This is something that we should have thought of directly with the upgrade to 1.3.0.

I guess you need a quick minor release then?

If possible, that would be really great, thanks! :)

Ok, James. We'll see what we can do.
Thanks again!

Hey @sirthias, any chance of a release soon?

Hey @sirthias, any chance of a release soon?


Update database_sampler.py

Fix https://github.com/open-mmlab/OpenPCDet/issues/702

self.use_shared_memory = sampler_cfg.get('USE_SHARED_MEMORY', False)
needs to be set before executing
with open(str(db_info_path), 'rb') as f:

Thank you!
Could you explain more on how to solving the issue by changing the order of self.use_shared_memory =xxx?

Unfortunately, I do not have the stack trace anymore, but for some conda environment I was using, I also saw this error https://github.com/open-mmlab/OpenPCDet/issues/702.
I suspect it could e.g. be due to some specific python version.
This line
https://github.com/open-mmlab/OpenPCDet/blob/4f0e1f02fe89eeba34a47251620067c8c06a0296/pcdet/datasets/augmentor/database_sampler.py#L25
wanted to access self.use_shared_memory in line
https://github.com/open-mmlab/OpenPCDet/blob/4f0e1f02fe89eeba34a47251620067c8c06a0296/pcdet/datasets/augmentor/database_sampler.py#L59
but since it was not initialized yet, the code crashed with
AttributeError: 'DataBaseSampler' object has no attribute 'use_shared_memory'


feature flag for environment

It would be helpful if you could pick which cloudctl to bind to via some form of feature flagging.
Possibly using https://github.com/spotify/openfeature-swift-sdk ?

Closed as part of https://github.com/subconsciousnetwork/subconscious/pull/814