west espressif install and update commands failing in zephyr 3.2.0

Hi,
I want to get espressif tools through west espressif install and update but these commands are not working in zephyr 3.2.0. getting below error,
usage: west espressif [-h] [-b BAUD] [-p PORT] [-e ELF] {monitor} west espressif: error: argument command: invalid choice: 'install' (choose from 'monitor')
Commands:
west update  (command successful)
west espressif install
west espressif update
I ran install.bat from "\zephyr-v3.2.0\modules\hal\espressif", but running into other errors.
west espressif install and update working partially in zephyr 3.1.0, it is installing only openocd-esp32, I somehow managed to get other tools as shown below

Environment :
OS: Windows
Toolchain Zephyr SDK 0.15.2 , espressif : esp-2020r3-8.4.0 (C:\Users<username>.espressif\tools\zephyr)
Zephyr version: 3.2.0

You should be using the Zephyr SDK for ESP32 as well for v3.2.0.

You should be using the Zephyr SDK for ESP32 as well for v3.2.0.
Thanks @henrikbrixandersen for your response!
I am able to use Zephyr SDK for ESP32.  I still have following queries,

In which case west espressif install should be used?
Why this command is not working in zephyr 3.2.0?


Featured Pages in Sections

I see that this wasn't clearly defined in the V2 Figma, but here is how Featured Pages in sections should look.
Currently:
Section http://mena.iogt.site/en/sections/emergency-information/covid-19-parenting/
Featured Page http://mena.iogt.site/en/sections/emergency-information/about-covid-19/myths/
Design

Desired:

But, where does the icon here come from?

But, where does the icon here come from?

The icon is a static default icon. It can be overridden by setting an icon in the referenced article.

Add the article image as in the second screenshot.
Ensure the entire area is clickable, not just the title text, as a link to the article.


WebServer optimizations

I just realized i messed something up. It compiles and runs but i'm not appending some strings properly, so it's unusable, don't merge 'till i've done 1-2 more commits.

Alright, everything works now


sparsifier active set

Replacing the sparsifying option with a sparsifying active set

@matbesancon once addressed, feel free to merge into my branch


Error trying to run a Runner twice

I'm just starting with Tensorforce, so it's possible there's something I'm missing in configuring my model, but when I create a Runner, I'm able to call .run() once, but I get an error if I try to do so again. Below is the code to reproduce this and the error message:
from tensorforce.agents import PPOAgent
from tensorforce.execution import Runner
from tensorforce.contrib.openai_gym import OpenAIGym

env_name = 'CartPole-v1'
env = OpenAIGym(env_name)

network_spec = [
    dict(type='dense', size=64, activation='tanh'),
    dict(type='dense', size=64, activation='tanh')
]

agent = PPOAgent(
    states_spec=env.states,
    actions_spec=env.actions,
    network_spec=network_spec,
    batch_size=4096,
    # BatchAgent
    keep_last_timestep=True,
    # PPOAgent
    step_optimizer=dict(
        type='adam',
        learning_rate=1e-3
    ),
    optimization_steps=10,
    # Model
    scope='ppo',
    discount=0.99,
    # DistributionModel
    distributions_spec=None,
    entropy_regularization=0.01,
    # PGModel
    baseline_mode=None,
    baseline=None,
    baseline_optimizer=None,
    gae_lambda=None,
    # PGLRModel
    likelihood_ratio_clipping=0.2,
    summary_spec=None,
    distributed_spec=None
)

runner = Runner(agent=agent, environment=env)

# seems to work fine
runner.run(episodes=100, max_episode_timesteps=200, episode_finished=lambda r: True)
# throws an error
runner.run(episodes=100, max_episode_timesteps=200, episode_finished=lambda r: True)

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-3-4cf820880e7c> in <module>()
      1 # Start learning
----> 2 runner.run(episodes=100, max_episode_timesteps=200, episode_finished=lambda r: True)

/anaconda3/lib/python3.6/site-packages/tensorforce/execution/runner.py in run(self, timesteps, episodes, max_episode_timesteps, deterministic, episode_finished)
     89         self.start_time = time.time()
     90
---> 91         self.agent.reset()
     92
     93         self.episode = self.agent.episode

/anaconda3/lib/python3.6/site-packages/tensorforce/agents/agent.py in reset(self)
    113         timestep counter, internal states, and resets preprocessors.
    114         """
--> 115         self.episode, self.timestep, self.next_internals = self.model.reset()
    116         self.current_internals = self.next_internals
    117

/anaconda3/lib/python3.6/site-packages/tensorforce/models/model.py in reset(self)
   1232         """
   1233         # TODO preprocessing reset call moved from agent
-> 1234         episode, timestep = self.monitored_session.run(fetches=(self.episode, self.timestep))
   1235         return episode, timestep, list(self.internals_init)
   1236

/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/monitored_session.py in run(self, fetches, feed_dict, options, run_metadata)
    534       Same as `tf.Session.run()`.
    535     """
--> 536     return self._sess.run(fetches,
    537                           feed_dict=feed_dict,
    538                           options=options,

AttributeError: 'NoneType' object has no attribute 'run'

It seems like the Tensorflow session is lost after the first run? If this is the expected behavior, what do I need to do in order to start the Runner again?

@neighthan ensure you're on #master's HEAD (instead of pip's 3.5.1). This commit should fix that https://github.com/reinforceio/tensorforce/commit/f0876f55e2cfb0af789479237bed7d8fe66df515. It's not yet merged to #memory, only on #master.

pip uninstall tensorforce
git clone https://github.com/reinforceio/tensorforce.git
cd tensorforce && pip install -e .

Thanks @lefnire, that fixed it (and another issue I was getting as well with resetting the Runner's environment; presumably also related to the environment needing to be closed).


Non native build

Non native build is done  with platform and arch flags in manifest
{
"arch": {
"platform": "arm64",
"arch": "aarch64"
},

Doesn't handle iso/image creation for non-amd64 build yet

@kmoore134 @beanpole135 Please let me know what you think now and if I need any more cleanup.
Also let me know if you want me to redo this entire commit history again with out removing and re-adding the delete_tmp_manifest. Functional no different just dirties commit history a little


Check for tests completed + passing

We have Jenkins and Travis integrations with GH for that. The indicators in GH interface are good enough imo.


Install bash completions in /usr/share

With a classic cmake install prefix '/usr', bash completions were installed in /usr/etc/bash_completion.d/ which even before bash-completion 1.9 was incorrect.
Since v1.9 all completions are to be installed in /usr/share/bash-completion/completions
See: http://anonscm.debian.org/cgit/bash-completion/bash-completion.git/tree/CHANGES#n324
Change the completions install path accordingly

Coverage remained the same at 70.01% when pulling eaf356f30e937ac081e2ce235e13b65d19591757 on krocard:correct_completions_install into 597148e60866d5027b49503360aceb9838a0d547 on 01org:master.

Coverage remained the same at 70.01% when pulling eaf356f30e937ac081e2ce235e13b65d19591757 on krocard:correct_completions_install into 597148e60866d5027b49503360aceb9838a0d547 on 01org:master.

:+1: @dawagner @gdenneul @Makohoek @clero

:+1:


TSW 71902 gracefully fail on vCPU quota limits

There are 8 cases when going through this code that are captured:
3682 - existing deploy, same region [3 cores]
3099 - existing deploy, new region [3 cores]
3814 - new deploy, existing domain, existing rg, entered # [3 cores]
new deploy, new domain, existing rg, entered # [6 cores]
3824 - new deploy, existing domain, existing rg, entered name [3 cores]
new deploy, new domain, existing rg, entered name [6 cores]
3851 - new deploy, new domain, new rg [6 cores]
new deploy, existing domain, new rg [3 cores]
The locations are placed to preempt the creation of empty resource groups in Azure.

Looks reasonable with a minor question. I'll let others do a fine-tuned review. Thanks for double checking the core counts with me.

Canadaeast is currently fully occupied with offline VMs for testing purposes.


p4_constraints] EntryMeetsConstraint replaced with ReasonEntryViolates constraint for actionable debug messages

Build Results:
divya@f02d501eaa83:/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
INFO: Analyzed 221 targets (0 packages loaded, 0 targets configured).
INFO: Found 221 targets...
INFO: Elapsed time: 0.279s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
Test Results:
divya@f02d501eaa83:/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS ...
INFO: Analyzed 221 targets (0 packages loaded, 0 targets configured).
INFO: Found 143 targets and 78 test targets...
INFO: Elapsed time: 0.273s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
//gutil:collections_test                                        (cached) PASSED in 0.2s
//gutil:io_test                                                 (cached) PASSED in 0.2s
//gutil:proto_matchers_test                                     (cached) PASSED in 0.3s
//gutil:proto_test                                              (cached) PASSED in 0.2s
//gutil:status_matchers_test                                    (cached) PASSED in 0.2s
//gutil:table_entry_key_test                                    (cached) PASSED in 0.0s
//p4_pdpi:ir_tools_test                                         (cached) PASSED in 0.3s
//p4_pdpi/netaddr:ipv4_address_and_network_address_test         (cached) PASSED in 0.2s
//p4_pdpi/netaddr:ipv6_address_test                             (cached) PASSED in 0.2s
//p4_pdpi/netaddr:mac_address_test                              (cached) PASSED in 0.2s
//p4_pdpi/string_encodings:bit_string_test                      (cached) PASSED in 0.2s
//p4_pdpi/string_encodings:byte_string_test                     (cached) PASSED in 0.2s
//p4_pdpi/string_encodings:decimal_string_test                  (cached) PASSED in 0.1s
//p4_pdpi/string_encodings:decimal_string_test_runner           (cached) PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test                      (cached) PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test_runner               (cached) PASSED in 0.0s
//p4_pdpi/string_encodings:readable_byte_string_test            (cached) PASSED in 0.2s
//p4_pdpi/testing:helper_function_test                          (cached) PASSED in 0.3s
//p4_pdpi/testing:info_test                                     (cached) PASSED in 0.1s
//p4_pdpi/testing:info_test_runner                              (cached) PASSED in 0.0s
//p4_pdpi/testing:main_pd_test                                  (cached) PASSED in 0.0s
//p4_pdpi/testing:mock_p4_runtime_server_test                   (cached) PASSED in 0.3s
//p4_pdpi/testing:packet_io_test                                (cached) PASSED in 0.1s
//p4_pdpi/testing:packet_io_test_runner                         (cached) PASSED in 0.1s
//p4_pdpi/testing:rpc_test                                      (cached) PASSED in 0.1s
//p4_pdpi/testing:rpc_test_runner                               (cached) PASSED in 0.0s
//p4_pdpi/testing:sequencing_test                               (cached) PASSED in 0.1s
//p4_pdpi/testing:sequencing_test_runner                        (cached) PASSED in 0.1s
//p4_pdpi/testing:table_entry_gunit_test                        (cached) PASSED in 0.4s
//p4_pdpi/testing:table_entry_test                              (cached) PASSED in 0.1s
//p4_pdpi/testing:table_entry_test_runner                       (cached) PASSED in 0.1s
//p4_pdpi/utils:annotation_parser_test                          (cached) PASSED in 0.2s
//p4_pdpi/utils:ir_test                                         (cached) PASSED in 0.3s
//p4rt_app/event_monitoring:app_state_db_port_table_event_test  (cached) PASSED in 0.5s
//p4rt_app/event_monitoring:config_db_node_cfg_table_event_test (cached) PASSED in 0.5s
//p4rt_app/event_monitoring:config_db_port_table_event_test     (cached) PASSED in 0.5s
//p4rt_app/event_monitoring:state_verification_events_test      (cached) PASSED in 0.5s
//p4rt_app/p4runtime:ir_translation_test                        (cached) PASSED in 0.4s
//p4rt_app/p4runtime:p4info_verification_schema_test            (cached) PASSED in 0.4s
//p4rt_app/p4runtime:p4info_verification_test                   (cached) PASSED in 0.4s
//p4rt_app/p4runtime:packetio_helpers_test                      (cached) PASSED in 0.5s
//p4rt_app/sonic:app_db_acl_def_table_manager_test              (cached) PASSED in 0.4s
//p4rt_app/sonic:app_db_manager_test                            (cached) PASSED in 0.4s
//p4rt_app/sonic:app_db_to_pdpi_ir_translator_test              (cached) PASSED in 0.4s
//p4rt_app/sonic:packetio_impl_test                             (cached) PASSED in 0.3s
//p4rt_app/sonic:packetio_port_test                             (cached) PASSED in 0.3s
//p4rt_app/sonic:response_handler_test                          (cached) PASSED in 0.4s
//p4rt_app/sonic:state_verification_test                        (cached) PASSED in 0.2s
//p4rt_app/sonic:vrf_entry_translation_test                     (cached) PASSED in 0.4s
//p4rt_app/sonic/adapters:fake_sonic_db_table_test              (cached) PASSED in 0.0s
//p4rt_app/tests:acl_table_test                                 (cached) PASSED in 0.7s
//p4rt_app/tests:action_set_test                                (cached) PASSED in 0.5s
//p4rt_app/tests:api_access_test                                (cached) PASSED in 0.5s
//p4rt_app/tests:arbitration_test                               (cached) PASSED in 0.6s
//p4rt_app/tests:fixed_l3_tables_test                           (cached) PASSED in 1.5s
//p4rt_app/tests:forwarding_pipeline_config_test                (cached) PASSED in 2.0s
//p4rt_app/tests:grpc_behavior_test                             (cached) PASSED in 5.0s
//p4rt_app/tests:p4_constraints_test                            (cached) PASSED in 0.1s
//p4rt_app/tests:p4_constraints_test_runner                     (cached) PASSED in 0.1s
//p4rt_app/tests:p4_programs_test                               (cached) PASSED in 0.8s
//p4rt_app/tests:packetio_test                                  (cached) PASSED in 2.9s
//p4rt_app/tests:port_name_and_id_test                          (cached) PASSED in 0.7s
//p4rt_app/tests:response_path_test                             (cached) PASSED in 1.2s
//p4rt_app/tests:role_test                                      (cached) PASSED in 0.6s
//p4rt_app/tests:state_verification_test                        (cached) PASSED in 0.7s
//p4rt_app/tests/lib:app_db_entry_builder_test                  (cached) PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                        (cached) PASSED in 0.0s
//p4rt_app/utils:table_utility_test                             (cached) PASSED in 0.3s
//sai_p4/instantiations/google:clos_stage_test                  (cached) PASSED in 0.2s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test (cached) PASSED in 0.0s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test (cached) PASSED in 0.0s
//sai_p4/instantiations/google:sai_p4info_fetcher_test          (cached) PASSED in 0.3s
//sai_p4/instantiations/google:sai_p4info_test                  (cached) PASSED in 0.5s
//sai_p4/instantiations/google:sai_pd_proto_test                (cached) PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                 (cached) PASSED in 0.2s
//sai_p4/instantiations/google:union_p4info_up_to_date_test     (cached) PASSED in 0.0s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test       (cached) PASSED in 0.1s
//sai_p4/tools:p4info_tools_test                                (cached) PASSED in 0.3s
Executed 0 out of 78 tests: 78 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line optioINFO: Build completed successfully, 1 total action
divya@f02d501eaa83:/sonic/src/sonic-p4rt/sonic-pins$

Co-authored-by: Srikishen Pondicherry Shanmugam<EMAIL_ADDRESS>


Raven enables the immutable String feature of Ruby 2.3

In our application we use a dlog as a logger (https://rubygems.org/gems/dlog/versions/0.2.3).
dlog will force UTF-8 encoding before logging anything.
Raven uses the frozen String feature of Ruby 2.3, i.e. there is a comment # frozen_string_literal: true at the beginning of e.g. the raven/logger. This then throws another error in d_log: can't modify frozen String, once Raven tries to log anything.
I am wondering how to approach this. Of course I could try to get rid of dlog, but I'm not sure whether this behaviour of Raven is intentional, since I assume that you'd like to keep it as flexible and unintrusive as possible.
The comment seems to have been added in a commit with Rubocop changes.
Were these changes intentional?

The changes were intentional.
I can download dlog and try to replicate, but just know this is going to be a "back-burner" issue. dlog is clearly doing something unusual, since Raven works just fine with frozen string literals in most other installs.

Alright, thanks a lot for the quick feedback!
I'll close this issue since it was an intentional decision on your side. Just be aware that other Gems might run into similar issues, if they are trying to change immutable Strings passed from Raven.


Spelling corrections and better abbreviations

Spelling correction on line 201. "ARMOR CLASS", "Hit Point Maximum" and "EXPERIENCE POINTS" shortened to better fit the layout.

Thank you for making these changes. If there are other changes or if these changes aren't able to properly convey what they need to, please let me know. I am able to modify the sheet design specifically for each language, so I can fix it for PT. I hadn't done it yet, because I've been getting ready for a vacation and am out all this week. I can make style changes for the sheet next week.

The phrases I abbreviated were the only causing problems with the layout, I believe that there will be no more such problems, but it is good to know that you can change the layout to suit the language :)


Invoke-Webrequest hangs on query to certain websites

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
I have tested from a fresh install of Powershell 7.2.4 over multiple devices and different network locations.
when you execute for example:
(invoke-webrequest -Uri 'https://www.adidas.co.uk' -UseBasicParsing).Content
The command never times out or errors.
When executing the same command from a powerhsell 5 session from the same host it executes straight away.
Expected behavior
PS>(invoke-webrequest -Uri 'https://www.adidas.co.uk' -UseBasicParsing).Content
[{"id":"FY9121","product_type":"inline","model_number":"LRY83","name":"Ultraboost 4.0 DNA Shoes","meta_data":{"canonical":"//www.adidas.co.uk/ultraboost-4.0-dna-shoes/FY9121.html","description":"Shop for Black Ultraboost 4.0 DNA Shoes at adidas.co.uk! Free Shipping Options & 60 Day Returns at the official adidas online store.","keywords":"Ultraboost 4.0 DNA Shoes","page_title":"adidas Ultraboost 4.0 DNA Shoes - Black | adidas UK","site_name":"adidas United Kingdom"},"view_list":[{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/584670fb39cd4f1aa70fac5500914ec4_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_01_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","imageStyle":"Standard","view":"Side Lateral Center View","usageTerms":"eCommerce","sortOrder":"1","subjects":[]}},{"type":"other","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/4df6a4c2c1a6459eb8a1ac5500915c8e_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_02_standard_hover.jpg","metadata":{"asset_usage":["pdp","plp"],"asset_category":"Photography","imageStyle":"Standard","view":"Top Portrait View","usageTerms":"eCommerce","sortOrder":"2","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/8906fe0c2b3b48af9486ac55009162ba_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_03_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","imageStyle":"Standard","view":"Bottom View","usageTerms":"eCommerce","sortOrder":"3","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/8c1fa86309c94e6594beac55009169ab_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_04_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","imageStyle":"Standard","view":"Front Lateral Top View","usageTerms":"eCommerce","sortOrder":"4","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/fa18004da1a6423ea5baac5500916ee7_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_05_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","imageStyle":"Standard","view":"Back Lateral Top View","usageTerms":"eCommerce","sortOrder":"5","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/6c139f6f7d0c41ca9665ac5500915688_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_06_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","imageStyle":"Standard","view":"Side Medial Center View","usageTerms":"eCommerce","sortOrder":"6","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c034ac46762e41249835ac5500918632_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_09_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","imageStyle":"Standard","view":"Mirrored Pair View","usageTerms":"eCommerce","sortOrder":"7","subjects":[]}},{"type":"detail","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c20c760dd12a467e9b18ac55009176f1_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_41_detail.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","imageStyle":"Standard","view":"Detail View 1","usageTerms":"eCommerce","sortOrder":"8","subjects":[]}},{"type":"detail","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/7b48f23d7de9472cb583ac5500917c31_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121_42_detail.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","imageStyle":"Standard","view":"Detail View 2","usageTerms":"eCommerce","sortOrder":"9","subjects":[]}}],"dynamic_background_assets":[{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/584670fb39cd4f1aa70fac5500914ec4_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db01_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Side Lateral Center View","usage_terms":"eCommerce","sort_order":"1","subjects":[]}},{"type":"other","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/4df6a4c2c1a6459eb8a1ac5500915c8e_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db02_standard_hover.jpg","metadata":{"asset_usage":["pdp","plp"],"asset_category":"Photography","image_style":"Standard","view":"Top Portrait View","usage_terms":"eCommerce","sort_order":"2","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/8906fe0c2b3b48af9486ac55009162ba_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db03_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Bottom View","usage_terms":"eCommerce","sort_order":"3","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/8c1fa86309c94e6594beac55009169ab_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db04_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Front Lateral Top View","usage_terms":"eCommerce","sort_order":"4","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/fa18004da1a6423ea5baac5500916ee7_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db05_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Back Lateral Top View","usage_terms":"eCommerce","sort_order":"5","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/6c139f6f7d0c41ca9665ac5500915688_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db06_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Side Medial Center View","usage_terms":"eCommerce","sort_order":"6","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c034ac46762e41249835ac5500918632_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db09_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Mirrored Pair View","usage_terms":"eCommerce","sort_order":"7","subjects":[]}},{"type":"detail","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c20c760dd12a467e9b18ac55009176f1_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db41_detail.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Detail View 1","usage_terms":"eCommerce","sort_order":"8","subjects":[]}},{"type":"detail","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/7b48f23d7de9472cb583ac5500917c31_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db42_detail.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Detail View 2","usage_terms":"eCommerce","sort_order":"9","subjects":[]}}],"confirmed_dynamic_background_assets":[{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/584670fb39cd4f1aa70fac5500914ec4_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db01_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Side Lateral Center View","usage_terms":"eCommerce","sort_order":"1","subjects":[]}},{"type":"other","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/4df6a4c2c1a6459eb8a1ac5500915c8e_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db02_standard_hover.jpg","metadata":{"asset_usage":["pdp","plp"],"asset_category":"Photography","image_style":"Standard","view":"Top Portrait View","usage_terms":"eCommerce","sort_order":"2","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/8906fe0c2b3b48af9486ac55009162ba_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db03_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Bottom View","usage_terms":"eCommerce","sort_order":"3","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/8c1fa86309c94e6594beac55009169ab_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db04_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Front Lateral Top View","usage_terms":"eCommerce","sort_order":"4","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/fa18004da1a6423ea5baac5500916ee7_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db05_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Back Lateral Top View","usage_terms":"eCommerce","sort_order":"5","subjects":[]}},{"type":"standard","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/6c139f6f7d0c41ca9665ac5500915688_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db06_standard.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Side Medial Center View","usage_terms":"eCommerce","sort_order":"6","subjects":[]}},{"type":"detail","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c20c760dd12a467e9b18ac55009176f1_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db41_detail.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Detail View 1","usage_terms":"eCommerce","sort_order":"7","subjects":[]}},{"type":"detail","source":"CLOUDINARY","image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/7b48f23d7de9472cb583ac5500917c31_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9121_db42_detail.jpg","metadata":{"asset_usage":["pdp"],"asset_category":"Photography","image_style":"Standard","view":"Detail View 2","usage_terms":"eCommerce","sort_order":"8","subjects":[]}}],"attribute_list":{"sale":false,"brand":"Sportswear","color":"Core Black / Core Black / Active Red","gender":"U","outlet":false,"sport":["Lifestyle"],"closure":["Laces"],"surface":["Street"],"category":"Shoes","sportSub":["Ultraboost","Parley"],"size_fit_bar":{"value":"ftw_1","markerCount":5,"selectedMarkerIndex":0},"collection":["Gifts","Lifestyle Running"],"search_color":"Black","base_material":["Textile Upper"],"productType":["Trainers","Lifestyle Trainers"],"personalizable":false,"isCnCRestricted":false,"key_category_code":"00157","productLineStyle":["UltraBoost DNA"],"mandatory_personalization":false,"sustainability_ethics_compliance_ids":["Sustainable","Primeblue"],"customizable":false,"search_color_raw":"Black","is_orderable":true,"isWaitingRoomProduct":false,"isInPreview":false,"specialLaunch":false,"special_launch_type":"NONE","sizeTypes":{},"is_flash":false,"size_chart_link":"/on/demandware.store/Sites-adidas-GB-Site/en_GB/Page-Include?cid=size-chart-size-shoes"},"breadcrumb_list":[{"text":"Sportswear","link":"/sportswear"},{"text":"Shoes","link":"/sportswear-shoes"}],"pricing_information":{"currentPrice":140,"standard_price":140,"standard_price_no_vat":116.67},"product_description":{"title":"Ultraboost 4.0 DNA Shoes","text":"A young legend. The adidas Ultraboost debuted in 2015, and it became a go-to far beyond the realm of running. These shoes have a soft knit upper that offers ventilation where you need it most. They ride on our original tooling, with a Boost midsole for comfort you need to feel to believe.","subtitle":"Ultraboost shoes for everyday comfort.","usps":["Sock-like fit","Lace closure","adidas Primeknit upper","Lightweight feel","Midfoot cage and supportive heel counter","Boost midsole","Weight: 312 g (size UK 8.5)","Midsole drop: 10 mm (heel: 22 mm / forefoot: 12 mm)","Continental Rubber","Primeblue"],"wash_care_instructions":{"care_instructions":[]},"product_highlights":[{"copy":"This product is made with Primeblue, a high-performance recycled material made in part with Parley Ocean Plastic.","headline":"Primeblue","image_reference":null},{"copy":"The incredible energy return of adidas Boost is created by fusing together energy capsules, giving you the power to keep your feet moving.","headline":"Can't stop. Won't stop.","image_reference":null},{"copy":"Precision-made, seamless zones combine strength and performance with smooth comfort to ensure distraction-free movement.","headline":"adidas Primeknit","image_reference":null},{"copy":"Ultraboost DNA carries the genetic information of one of our most popular performance runners, but it's born for the street.","headline":"Ultraboost DNA","image_reference":null}],"description_assets":{"image_url":"https://assets.adidas.com/images/w_600,f_auto,q_auto/8c1fa86309c94e6594beac55009169ab_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9121.jpg","video_url":null,"poster_url":null}},"recommendationsEnabled":true,"product_link_list":[{"type":"color-variation","productId":"FY9120","name":"Ultraboost 4.0 DNA Shoes","url":"/ultraboost-4.0-dna-shoes/FY9120.html","image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/b56f062b132c400ab494ac67011578a5_9366/Ultraboost_4.0_DNA_Shoes_White_FY9120_01_standard.jpg","altImage":"https://assets.adidas.com/images/w_600,f_auto,q_auto/b56f062b132c400ab494ac67011578a5_9366/Ultraboost_4.0_DNA_Shoes_White_FY9120_01_standard.jpg","dynamic_background_image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/b56f062b132c400ab494ac67011578a5_faec/Ultraboost_4.0_DNA_Shoes_White_FY9120_db01_standard.jpg","confirmed_dynamic_background_image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/b56f062b132c400ab494ac67011578a5_faec/Ultraboost_4.0_DNA_Shoes_White_FY9120_db01_standard.jpg","pricing_information":{"standard_price":140},"search_color":"White","default_color":"Cloud White / Cloud White / Core Black","source":"CLOUDINARY","available_skus":11},{"type":"color-variation","productId":"FY9318","name":"Ultraboost 4.0 DNA Shoes","url":"/ultraboost-4.0-dna-shoes/FY9318.html","image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c79a34cb2e4a4bbe81c8ac1e011ac76c_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9318_01_standard.jpg","altImage":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c79a34cb2e4a4bbe81c8ac1e011ac76c_9366/Ultraboost_4.0_DNA_Shoes_Black_FY9318_01_standard.jpg","dynamic_background_image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c79a34cb2e4a4bbe81c8ac1e011ac76c_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9318_db01_standard.jpg","confirmed_dynamic_background_image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/c79a34cb2e4a4bbe81c8ac1e011ac76c_faec/Ultraboost_4.0_DNA_Shoes_Black_FY9318_db01_standard.jpg","pricing_information":{"standard_price":140},"search_color":"Black","default_color":"Core Black / Core Black / Cloud White","source":"CLOUDINARY","available_skus":13},{"type":"color-variation","productId":"FY9319","name":"Ultraboost 4.0 DNA Shoes","url":"/ultraboost-4.0-dna-shoes/FY9319.html","image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/5370778f2e99474fbf2fac550092a0b6_9366/Ultraboost_4.0_DNA_Shoes_Grey_FY9319_01_standard.jpg","altImage":"https://assets.adidas.com/images/w_600,f_auto,q_auto/5370778f2e99474fbf2fac550092a0b6_9366/Ultraboost_4.0_DNA_Shoes_Grey_FY9319_01_standard.jpg","dynamic_background_image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/5370778f2e99474fbf2fac550092a0b6_faec/Ultraboost_4.0_DNA_Shoes_Grey_FY9319_db01_standard.jpg","pricing_information":{"standard_price":140},"search_color":"Grey","default_color":"Grey Three / Grey Three / Core Black","source":"CLOUDINARY","available_skus":14},{"type":"color-variation","productId":"GW2289","name":"Ultraboost 4.0 DNA Shoes","url":"/ultraboost-4.0-dna-shoes/GW2289.html","image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/08cb85d987914b2581a5acb800c38695_9366/Ultraboost_4.0_DNA_Shoes_Black_GW2289_01_standard.jpg","altImage":"https://assets.adidas.com/images/w_600,f_auto,q_auto/08cb85d987914b2581a5acb800c38695_9366/Ultraboost_4.0_DNA_Shoes_Black_GW2289_01_standard.jpg","dynamic_background_image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/08cb85d987914b2581a5acb800c38695_faec/Ultraboost_4.0_DNA_Shoes_Black_GW2289_db01_standard.jpg","pricing_information":{"standard_price":140,"sale_price":84},"search_color":"Black","default_color":"Core Black / Core Black / Grey Six","source":"CLOUDINARY","available_skus":2},{"type":"color-variation","productId":"GY0284","name":"Ultraboost 4 DNA Shoes","url":"/ultraboost-4-dna-shoes/GY0284.html","image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/2a793942e01843ef8718ae0800b10315_9366/Ultraboost_4_DNA_Shoes_Grey_GY0284_01_standard.jpg","altImage":"https://assets.adidas.com/images/w_600,f_auto,q_auto/2a793942e01843ef8718ae0800b10315_9366/Ultraboost_4_DNA_Shoes_Grey_GY0284_01_standard.jpg","pricing_information":{"standard_price":140},"search_color":"Grey","default_color":"Halo Silver / Halo Silver / Almost Lime","source":"CLOUDINARY","available_skus":6},{"type":"color-variation","productId":"GY0285","name":"Ultraboost 4 DNA Shoes","url":"/ultraboost-4-dna-shoes/GY0285.html","image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/fdf9c05fabc949038345ae0800a506ba_9366/Ultraboost_4_DNA_Shoes_White_GY0285_01_standard.jpg","altImage":"https://assets.adidas.com/images/w_600,f_auto,q_auto/fdf9c05fabc949038345ae0800a506ba_9366/Ultraboost_4_DNA_Shoes_White_GY0285_01_standard.jpg","pricing_information":{"standard_price":140},"search_color":"White","default_color":"White Tint / White Tint / Vivid Red","source":"CLOUDINARY","available_skus":11},{"type":"color-variation","productId":"GY8542","name":"Ultraboost 4.0 DNA Shoes","url":"/ultraboost-4.0-dna-shoes/GY8542.html","image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/2ca903b83d7449cc9373adbe00b2ff45_9366/Ultraboost_4.0_DNA_Shoes_Black_GY8542_01_standard.jpg","altImage":"https://assets.adidas.com/images/w_600,f_auto,q_auto/2ca903b83d7449cc9373adbe00b2ff45_9366/Ultraboost_4.0_DNA_Shoes_Black_GY8542_01_standard.jpg","pricing_information":{"standard_price":140,"sale_price":84},"search_color":"Black","default_color":"Core Black / Matte Gold / Carbon","source":"CLOUDINARY","available_skus":1},{"type":"color-variation","productId":"H05246","name":"Ultraboost 4.0 DNA Shoes","url":"/ultraboost-4.0-dna-shoes/H05246.html","image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/0373de8b037844e5a2caac5a01601d5a_9366/Ultraboost_4.0_DNA_Shoes_Blue_H05246_01_standard.jpg","altImage":"https://assets.adidas.com/images/w_600,f_auto,q_auto/0373de8b037844e5a2caac5a01601d5a_9366/Ultraboost_4.0_DNA_Shoes_Blue_H05246_01_standard.jpg","dynamic_background_image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/0373de8b037844e5a2caac5a01601d5a_faec/Ultraboost_4.0_DNA_Shoes_Blue_H05246_db01_standard.jpg","confirmed_dynamic_background_image":"https://assets.adidas.com/images/w_600,f_auto,q_auto/0373de8b037844e5a2caac5a01601d5a_faec/Ultraboost_4.0_DNA_Shoes_Blue_H05246_db01_standard.jpg","pricing_information":{"standard_price":140},"search_color":"Blue","default_color":"Crew Navy / Crew Navy / Cloud White","source":"CLOUDINARY","available_skus":1}]}]

Actual behavior
PS>(invoke-webrequest -Uri 'https://www.adidas.co.uk' -UseBasicParsing).Content
_ (Just hangs until you break out)

Error details
No response
Environment data
PS> $PSVersiontable
Name                           Value
----                           -----
PSVersion                      7.2.4
PSEdition                      Core
GitCommitId                    7.2.4
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

I get a response back with just a -Headers @{ Accept = 'text/html' } and nothing else.
I'm curious though that the OP's Expected Behaviour is a JSON response blob. I don't know why that would be being returned, even in 5.1. I can only get a normal HTML response back from this web address, as I would expect since it appears to be a website index page.

Possibly if the accept has all those bits in it needs accept-encoding and accept-language as well.

I get a response back with just a -Headers @{ Accept = 'text/html' } and nothing else. I'd wager this server for some reason doesn't have a default fallback as to what kind of response to provide when no headers are present.
I'm curious though that the OP's Expected Behaviour is a JSON response blob. I don't know why that would be being returned, even in 5.1. I can only get a normal HTML response back from this web address, as I would expect since it appears to be a website index page.

Sorry I had posted the wrong expected response now corrected it to HTML.

So it seems that this behaviour is expected from running in a powershell 7 environment and not to be compared to what happens in Powershell 5. @jhoneill. Thanks for the tip on header construction by monitoring in Edge. I will now close this issue.


Models do not update when changed to a different state.

So I tried it, and the mod is not crashing which is great. Only issue is that changing a helmet to hidden for example, will make the hair show but not hide the helmet. Haven't seen any reports of this with the other versions of the mod.
I'm not a Skyrim modder so I probably won't be able to fix this unless it's just some load order or config issue.

It appears that RDF is still incompatible. Could be a new incompatibility introduced by the 1.5 patch. I'd have to set up an updated Skyrim profile to test this.


Feature/lef 270 list organizations sites

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:


Task Status Color  - Completed/Pending/Overdue

Hi,
I am currently implementing this Gantt chart and I must say its truly elegant.
Thanks for doing this is angular.
Now what I am trying to achieve is  :
I want to have different color sections within a single task so as to differentiate between the various task status (i.e. pending/completed/overdue).
This image would explain everything

Now one thing I would be doing for sure is that I would change the "task due date" to the current date.
After this would come painful CSS gradient world part that I always try and resist.
Anyways I would have to tweak it because its a requirement.
So suggestions are most welcome. I would be thankful if the community could help me on that.
Thanks & Regards

Hi
i want to implement some similar kind of functionality.
What i want to do is i have two dates for each interaction for E.g. some "start-date"  and some"end date" i want to display the colored line from this "start-date" to "end-date" and all the columns coming i n between those two dates in that particular row. Please help me to resolve this. I dont want resize option and draw option for the task enabled. Please help me to resolve this.

I have posted the snapshot in issue no 542

Plz help me to resolve this

Plz post your code which you have used to display your task in the colored line

i am not sure if i still have the access to the required code.
let me chack and get back to you
On Thu, Dec 10, 2015 at 3:50 PM, amitchandavale<EMAIL_ADDRESS>wrote:

Hi
i want to implement some similar kind of functionality.
What i want to do is i have two dates for each interaction for E.g. some
"start-date" and some"end date" i want to display the colored line from
this "start-date" to "end-date" and all the columns coming i n between
those two dates in that particular row. Please help me to resolve this. I
dont want resize option and draw option for the task enabled. Please help
me to resolve this.
—
Reply to this email directly or view it on GitHub
https://github.com/angular-gantt/angular-gantt/issues/31#issuecomment-163567520
.

ya it will be gr8!

@ankurmalhotra89:plz share the code that you have used to display your tasks as colored line

Could you please remind me this weekend.  I'm out of town right now.  Will
surely get it for you.
Thanks
On 14 Dec 2015 17:47, "amitchandavale"<EMAIL_ADDRESS>wrote:

@ankurmalhotra89 https://github.com/ankurmalhotra89:plz share the code
that you have used to display your tasks as colored line
—
Reply to this email directly or view it on GitHub
https://github.com/angular-gantt/angular-gantt/issues/31#issuecomment-164422964
.

Yes sure i will remind you!

@ankurmalhotra89:plz share the code that you have used to display your tasks as colored line

@ankurmalhotra89:plz share the code that you have used to display your tasks as colored line

could you please provide me your email address
On Mon, Dec 28, 2015 at 12:29 PM, amitchandavale<EMAIL_ADDRESS>wrote:

@ankurmalhotra89 https://github.com/ankurmalhotra89:plz share the code
that you have used to display your tasks as colored line
—
Reply to this email directly or view it on GitHub
https://github.com/angular-gantt/angular-gantt/issues/31#issuecomment-167496712
.

Could you please provide me the email address
On 30 Dec 2015 00:30, "Ankur Malhotra"<EMAIL_ADDRESS>wrote:

could you please provide me your email address
On Mon, Dec 28, 2015 at 12:29 PM, amitchandavale<EMAIL_ADDRESS>
wrote:

@ankurmalhotra89 https://github.com/ankurmalhotra89:plz share the code
that you have used to display your tasks as colored line
—
Reply to this email directly or view it on GitHub
https://github.com/angular-gantt/angular-gantt/issues/31#issuecomment-167496712
.

Hello there,
How did you succeed to change the text color in white of your task ?
Thanks


Nonlinear function blocks in Modelica.Blocks should use homotopy for initialization

Reported by fcasella on 8 Mar 2013 15:25 UTC
The Modelica.Blocks.Nonlinear.Limiter model contains the following code:
  if initial() and not limitsAtInit then
     y = u;
     assert(u >= uMin - 0.01*abs(uMin) and
            u <= uMax + 0.01*abs(uMax),
           "Limiter: During initialization the limits have been ignored.\n"+
           "However, the result is that the input u is not within the required limits:\n"+
           "  u = " + String(u) + ", uMin = " + String(uMin) + ", uMax = " + String(uMax));
  else
     y = smooth(0,if u > uMax then uMax else if u < uMin then uMin else u);

this helps the convergence of the nonlinear solver at initialization by not taking into account of the nonlinearities, if they are actually inactive at initialization; otherwise, a slightly messy situation ensues (-> when the simulation starts, the found initial solution is no longer a consistent solution of the dynamic problem).
A cleaner implementation in Modelica >= 3.2 would be:
y = homotopy(
  actual = smooth(0,if u > uMax then uMax else if u < uMin then uMin else u),
  simplified = y);

Similar arguments hold for VariableLimiter and DeadZone.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1012

Modified by fcasella on 11 Mar 2013 13:42 UTC

Comment by otter on 28 Mar 2013 11:19 UTC
This is a good idea. However, before introducing it in MSL, one or more concrete test cases are needed where this can be evaluated that it works as expected.

Modified by otter on 18 Apr 2013 15:15 UTC

Modified by beutlich on 6 Oct 2015 21:13 UTC

Comment by otter on 11 Dec 2015 14:07 UTC
Fixed in 995e959be2aaa3f2fc8f6c367b2d849522f59b98 as suggested.

Changelog modified by otter on 11 Dec 2015 14:07 UTC
Numerics improved for the Nonlinear blocks Limiter, VariableLimiter, DeadZone by using the homotopy operator


Timesheet - 21/04/2021 - Chrisha Canete

Task 1
Reviewing the finalization of Newsletter
Proof of Work
-https://docs.google.com/document/d/1Ra9ZtjDc8IbX_7KQZhevCf3eflaZ34azeXNiCz2KOeY/edit#heading=h.pcjxhunkqvkm
Time Spent
.5 hour

Task 2
talk to Bojan for socail media posting the hiring and make the Infographic design Template
Proof of Work

https://docs.google.com/document/d/1C7r2M9vZWVBbcy8CyRzsOt0WxyB-bazeHHdhORMpmDI/edit

Time Spent
.5 hour

Task 3
Paying Core Team for April 17, 2021
Proof of Work
-https://docs.google.com/spreadsheets/d/1C4rfwWjwylXiT_u-CdpZoauj2_iBhjkdFo_KWlEF5dM/edit#gid=0
Time Spent
1 hour

Total Time Spent
2 hours
Account Number
7053f27870d388b0bca4149fe72765172c3e6d1b4ffc7cd0149a296cbefe8f57

Approved


Updated READMEs on releasing, maintaining, admins and security.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Beginning of standardizing processes across the org for branching, admins, maintainers. Added security.
Issues Resolved
Partly #95.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@CEHENKLE could I get a review for this please?

start gradle check


Add back id param to webview service worker path

The id search param is used in service-worker.js, but seems forgot in this commit. This cause webview load failed sometime on web target (run yarn web).
Param used here:
https://github.com/microsoft/vscode/blob/4d5ca3a392f2f74d23a4bf2dc5476b1744f6de51/src/vs/workbench/contrib/webview/browser/pre/service-worker.js#L379-L386
https://github.com/microsoft/vscode/blob/4d5ca3a392f2f74d23a4bf2dc5476b1744f6de51/src/vs/workbench/contrib/webview/browser/pre/service-worker.js#L336

Anyone here? 😴

I don't think this explanation is correct. client is the webpage, not the service worker. The service worker's url is only used here: https://github.com/microsoft/vscode/blob/93a2a2fa12dd3ae0629eec01c05a28cb60ac1c4b/src/vs/workbench/contrib/webview/browser/pre/service-worker.js#L18


Spawn not working

The map no longer shows any pokemon spawning and pokestops no longer showing tasks.

Hello! I think you will need to get in contact with your map admin, as this is just the repository for the code that's used all around the world.


[SPARK-7424] [ML] ML ClassificationModel should add metadata to output column

What changes were proposed in this pull request?
ML ClassificationModel should add metadata to output column from label column if present, or create a nominal attribute to output the number of labels.
How was this patch tested?
Will add test case soon.
cc @jkbradley @mengxr

Test build #54530 has started for PR 12066 at commit 7a1139b.

Test build #54530 has finished for PR 12066 at commit 7a1139b.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54530/
Test FAILed.

Merged build finished. Test FAILed.

Test build #54531 has started for PR 12066 at commit f793b08.

Test build #54531 has finished for PR 12066 at commit f793b08.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54531/
Test PASSed.

One more thing: Can you please add a unit test?  Btw, I know you're working on a lot of issues, so please say if you'd like help with any.

Test build #56702 has started for PR 12066 at commit 5301a96.

Test build #56703 has started for PR 12066 at commit 5907c56.

@jkbradley Thanks for your comments, please see my inline reply to your concerns.
I have add test case. Because there are no attributes were stored in label column metadata of PredictionModel currently, I only made changes for ClassificationModel in this PR. Any thoughts, please let me know.

Test build #56703 has finished for PR 12066 at commit 5907c56.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56703/
Test FAILed.

Test build #56702 has finished for PR 12066 at commit 5301a96.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56702/
Test FAILed.

Test build #56874 has started for PR 12066 at commit 204f4f7.

Test build #56874 has finished for PR 12066 at commit 204f4f7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56874/
Test PASSed.

@jkbradley Thanks for your comments, please see my inline reply to your concerns. Because there are no attributes were stored in label column metadata of PredictionModel currently, I only made changes for ClassificationModel in this PR. Any thoughts, please let me know.
I have add one test case for NaiveBayesModel. If needed, I can add test for other classification model.

Thanks, I just responded above.  I agree only classification, not regression, needs to be handled in this PR.

Thanks for your comments, please see my inline replies.

Responded above.  It sounds like we're agreed now?

Yes, we have reached a consensus. Thanks.
I will update this PR soon.

Test build #57243 has started for PR 12066 at commit d4ffc6a.

Test build #57244 has started for PR 12066 at commit d5c5689.

Test build #57243 has finished for PR 12066 at commit d4ffc6a.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57243/
Test FAILed.

Test build #57244 has finished for PR 12066 at commit d5c5689.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57244/
Test FAILed.

Test build #57251 has started for PR 12066 at commit 486d5ab.

Test build #57251 has finished for PR 12066 at commit 486d5ab.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57251/
Test PASSed.

@jkbradley This is ready for another pass. Thanks!

Thanks!  Done with pass

Test build #57323 has started for PR 12066 at commit bb3578b.

Test build #57324 has started for PR 12066 at commit 94f16e8.

Test build #57324 has finished for PR 12066 at commit 94f16e8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57324/
Test PASSed.

Test build #57323 has finished for PR 12066 at commit bb3578b.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57323/
Test PASSed.

@jkbradley Addressed most comments except two. Please see my inline replies and let me know whether it make sense. Thanks.

Thanks!  I replied above & just noted 2 items which remain.

@jkbradley Thanks for your comments. I will update this PR soon.

Test build #57639 has started for PR 12066 at commit 449f824.

Test build #57639 has finished for PR 12066 at commit 449f824.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57639/
Test PASSed.

@jkbradley Addressed your comments about passing numClasses to generatePredictionMetadata. This PR is ready for reviewing now. Thanks!

Test build #58982 has started for PR 12066 at commit 449f824.

Test build #58982 has finished for PR 12066 at commit 449f824.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58982/
Test FAILed.

Build finished. Test FAILed.

@yanboliang Are you still working on this ?

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1349/
Test PASSed.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2322/
Test PASSed.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3692/
Test PASSed.

Hey @yanboliang I think improved metadata on the pipeline would be great, but if this abonded I get it if so do you want to close this PR and switch the JIRA back to open so someone else can take a crack at it? If you're still working on it that's cool too.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4678/
Test PASSed.

I still this is important, but if you're not working on it @yanboliang would you be OK closing it so someone else can take this over?

@holdenk Sorry for late response, I'm really busy recently. Sure, I'll close this now. Feel free to take over it. Thanks.


Error fix sub_window.rs example code

just an error fix for lines 301 to 304, the piet-common package doesnt wanna work with this one

Can you describe the error in more detail? What error are you seeing and what are you doing to trigger it.


Extend macro to append additional uses.

Proof of concept implementation of #8.
I haven't tested both exports / imports, and it should be possible to support renames.

Wasn't obvious how to do renames, so given a library exports this trait:
// publishing crate
#[gat]
pub trait LendingIterator {
    type Item<'next> where Self : 'next;
    // ..
}

// LendingIterator and LendingIteratorඞData are exported

then a consumer crate can rename the import like so:
// either of:
#[gat(Item)]
use library::LendingIterator as LendingIteratorRenamed;
#[gat(Item)]
use library::{LendingIterator as LendingIteratorRenamed};

// produces:
use library::LendingIterator as LendingIteratorRenamed;
use library::{LendingIteratorඞData as LendingIteratorRenamedඞData};

It also works with multiple lent items -- added that in tests

By the way, I had also considered a complementary / additional approach, to optionally get the user not to have to provide the (g) associated types, using an internal ad-hoc generated macro that would take care of remembering that info. But since properly scoped pub macros are not really a thing, my approach would break if eponymous #[gat]-annotated pub traits ended up defined in the same crate 😬…
But for the sake of it, here is what the idea was about:
#[gat]
trait LendingIterator {

would, on top of the LendingIterator trait (and friends), generate a LendingIterator! "import assistant" macro.
Then, #[gat] use …::LendingIterator would become:
…::LendingIterator! {
    use …::LendingIterator
}

which, in turn, would become:
#[gat(Item, …)]
use …::LendingIterator;

Thoughts?

Thoughts?

I certainly find it valuable to reduce the effort on the users' end; I actually misinterpreted your message the first time and thought the #[gat] on top of the impl Trait for .. would magically figure out how to use path::to::TraitඞData -- which would be exciting, but at that point we can't resolve the module path :sweat_smile:.

this would also need to resolve the path to #[gat]

I think this part may be able to be resolved, since #[gat] is already in the calling scope; the part that I think of a solution for is:

properly scoped pub macros are not really a thing


egressip-ipam-operator new version 1.0.0

New Submissions

[ ] Has you operator nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

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

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

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

Operator Metadata should contain

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

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

/ok-to-test

/ok-to-test

@J0zi @mvalarh the step that is failing seems to be the deployment on OCP, no additional error message is provided. Deployment works for me can you help me understand what the issue is?

@J0zi @mvalarh the step that is failing seems to be the deployment on OCP, no additional error message is provided. Deployment works for me can you help me understand what the issue is?

/test all


Build artifacts expire, we should create github releases instead

Everything is in issue title. Here's an example of expired artifacts:
https://github.com/GabLeRoux/macos-crossover-wine-cloud-builder/actions/runs/1104195381
They are listed, but cannot be downloaded anymore:

possible action to use:
https://github.com/actions/create-release

Yes artifacts have I think a 2 month? life before expiring.
I had considered being this up but I think we’d need to check how brew provided libraries are getting linked as brew isn’t exactly known to keep things stable.

I just tried something on a similar project which builds an older open source game on a mac and I managed to automate releases creation (we need to first move the artifact out of the mac and then create a release from the downloaded artifact). Here's a draft pr I tried between two tests execution at my day job 😅:
https://github.com/shoogle/OpenArena-legacy/pull/2

@dasmy & @GabLeRoux any thoughts?

I might be wrong, but I feel that it's mainly a matter of creating a github release when pipeline succeeds on main branch. This can be done with the example I shared above.
I don't think we must support all versions or all latest versions. I don't want any pressure on that project. Providing a release would definitely solve the expiration of builds problem.
When I started this project, my main objective was to get a binary without having to install and build everything from my laptop. It was just a fun weekend project and I consider it already succeeded the objectives.
If we think about it with iterations, the main problem I wanted to solve in current issue is the expiration. Maintenance and making sure we always have the latest version is a different issue imho.

I’ll expand on my concern with provided releases.

Once compiled wine will have backend in library paths these may be pointing to the actual path and not brews /usr/local/opt paths this can cause issues later when a libraries version gets bumped making the embedded path now invalid.
Also need to ensure anyone using the release have installed the needed runtime libraries or ship them within the package.

I agree with @Gcenx that there are severe difficulties to be expected. Currently, a user of the artifacts needs to have the very same versions of the runtime dependencies installed via brew which were present at build time on the CI server.
Thus, for providing usable release packages we would need to

identify all runtime-dependencies and prepare an installation of all these packages in our release folder (see https://github.com/Homebrew/brew/blob/664d0c67d5947605c914c4c56ebcfaa80cb6eca0/docs/Installation.md#untar-anywhere for warnings against that)
inside this folder patch all binaries with install_name_tool to have proper relative rpath entires (similar to https://github.com/GabLeRoux/macos-crossover-wine-cloud-builder/blob/f7d2bd4685d6e5da0a79b44a5e6c18a3b96bbfb2/.github/workflows/build_monolithic.yml#L369)
do the same for crossover, so that during execution it does not use the system brew but the brew libs we are shipping.

If I did not forget anything serious, I think this could be doable and the final release packages would profit from this. Still, it would be challenging and a bit of work...

@dasmy I’d ignore what brew says about a none default install location as we’d be fixing up the installed library's install_name after the fact.
When installing brew into a custom location there bottles lightly won’t work forcing source compiles that they don’t support.
Still brew doesn’t recommend this proposed setup, it recommends not relying on brew provided libraries.


[Win] ERR_UNSUPPORTED_ESM_URL_SCHEME

Related to v5.0.0-beta.0 (it correctly works with v4.0.0-beta.10)
import { load } from 'ts-import'
await load('./a.mts', { compiledJsExtension: '.cjs' })

Result
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
    at new NodeError (node:internal/errors:399:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:964:11)
    at defaultResolve (node:internal/modules/esm/resolve:1040:3)
    at nextResolve (node:internal/modules/esm/hooks:654:28)
    at resolve$1 (file:///C:/<PROJECT_PATH>/.pnp.loader.mjs:1960:14)
    at nextResolve (node:internal/modules/esm/hooks:654:28)
    at Hooks.resolve (node:internal/modules/esm/hooks:309:30)
    at ESMLoader.resolve (node:internal/modules/esm/loader:312:26)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:172:38)
    at ESMLoader.import (node:internal/modules/esm/loader:276:22) {
  type: 'Error',
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Also running into this issue, any workarounds for windows in the meantime?

With yarn berry can be created a patch.
Maybe url.pathToFileURL is needed as parameter of the aynch import.

Same issue on my side, any workarround?

Help!

@rtritto

Maybe url.pathToFileURL is needed as parameter of the dynamic async import.

Unfortunately, combining with cwd makes passed file url change from /Users/<user>/my-project/file.ts to /Users/<user>/my-project/file:/Users/<user>/my-project/file.ts.

Simple solution is to change both cases of
const loaded = await import(jsPath);

to
import * as path from 'node:path';
const loaded = await import(url.pathToFileURL(jsPath));


Removed json-smart in the JDBC driver

Signed-off-by: Guian Gumpac<EMAIL_ADDRESS>Description
Removed json-smart in the jdbc driver as it introduces a CVE (CVE-2021-31684).
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks for the changes! So json-smart is useless actually?

Seems like it. Builds and passes all tests without it.


Volmorpher

Hi @pravsripad ,
I will open pull requests to slowly merge my changes with the master branch.
The changes to jumeg volmorpher are basically only formatting. More substantial changes will follow later.

@ckiefer0 It can be merged if there are no further updates to volume morpher. Is it possible to include a short example showing the volume morphing on sample data?

So, I'll merge this as formatting related PR.
Further on, I'd suggest splitting it based on functionality, so volmorpher PR includes only volume morphing related changes and so on. Some suggestions for changes to volmorphing,

include example based on sample data
plotting routines in volmorpher can be moved to jumeg_plot.py since the volmorpher script is already too big


Not able to convert geojson files when the schema is not inferrable

Hi,
I am experiencing this issue with gpq:
gpq: error: failed to create schema after reading 39 features

Based on https://github.com/planetlabs/gpq/issues/142 the answer is clear: there are no non null values in any of the features for one of the columns.
Indeed, if I edit the file and add just one everything works fine.
The problem is that unlike in the linked issue it is not possible for me to increase the amount of rows scanned because all the rows have nulls, and this is a case that is pretty common with the files I am dealing with.
While this strict behaviour is understandableby default, is is preventing me from adopting the tool. The ogr2ogr behaviour is maybe questionable (in my case the incriminating column is being added as a string instead of an int), it at least produces an output that is usable.
So perhaps an option to --drop-non-inferrable-columns, or --import-ambiguous-columns-as-strings  would be a useful escape hatch for gpq users.
(pre-processing json is of course an option too but more invovled)

I agree that there should be a way to handle this.  OGR will encode these “unknown” types as JSON strings.
In your case, I imagine you would want an optional integer type.  The challenge is coming up with syntax for the command line args that is convenient and flexible.  Referring to a secondary file with schema or other complex options might be nicer.

Being able to specify the schema would be nice for a perfect output yes. I think even just optionally treating unknown fields as strings or dropping non inferable columns altogether would be a nice improvement though (and acceptable for my personal use case)


refactor(html): update html-validate and fix warnings

Updated html-validate to the latest and fixed a new error in confirm.html, which was using a redundant for attribute.
I also fixed the layers.html warnings by using Bootstrap's recommended nav tabs pattern.

I really dislike that Bootstrap's examples include the use of <label for="...">. Thanks for ditching that.

I really dislike that Bootstrap's examples include the use of <label for="...">. Thanks for ditching that.


Add details about key generation for update capsules

@krystian-hebel, done in https://github.com/Dasharo/docs/pull/885/commits/f97a4be31c9c8f3a5f80f0f4d4542055d128e92b.  Also did a rebase.


Non-linear overlay ads break the big play button

Non-linear overlay display ads, when closed by the user, break the big play button functionality.

Once the ads is closed by the user, the content can no longer be controlled using the big play button:

Play and pausing can then only be controled by the main control strip at the bottom of the player:

Sorry, not sure what button we're talking about here. Do you have an example page where I can see this happening?

Yup, but you have to be lucky enough to catch a non-linear ad. Not sure how to force them. If you see one, close it, and then try and use the big on screen play button.
https://www.destinationtips.com/videos/12-things-not-thailand/

I caught one on video. Notice the clicks/ taps on the video. I first close the non-leaner banner and then try and pause the video by clicking the screen. It's perhaps some kind of CSS layer thing. The non-linear ad after being close disrupts the big button CSS. I think…
https://www.dropbox.com/s/pom1zu8qnz473sg/screencast 2018-07-13 15-42-28.mp4?dl=0

Looks like some kind of issue with the videojs skin that you're using, which I'm not familiar with. Do you see the issue if you put your ad tag into one of our samples?

OK, thanks, taking a closer look at skin…

This issue looks like it was related to the videojs skin. I will be closing the issue.

is Exoplayer posible to play non-linear ads play  or not ?

Hello @ravishankar518 ,
The video.js-ima plugin is specific to HTML5/web playback while ExoPlayer is an Android player.
That being said, ExoPlayer + IMA should be able to play non-linear ads on Android.
IMA also offers the ExoPlayer IMA extension which offers a quick way to start with ExoPlayer and IMA.


Full-width images

Hi. I have a problem.
In my mailings there are blocks with images that should be the full width of the template, but there are left/right paddings in Outlook.
What am I doing wrong?
Code:
mj-attributes section
<mj-class name="content-blocks" padding="10px 20px" /> <mj-class name="no-padding" padding="0" />
mj-body section
<mj-section mj-class="content-blocks" background-color="#F0ECE9"></mj-section> <mj-section>           <mj-column>             <mj-image src="line-empty-top.png" mj-class="no-padding" />           </mj-column> </mj-section>
Screenshot:

Hi @KoalaMontana
You have a padding on your section cf :  name="content-blocks" padding="10px 20px"
Remove it to make the image go full-width

@iRyusa paddings were defined for the previous section with class "content-blocks". Section with image don't have any classes or paddings and display incorrect only in Outlook.

My bad, without indentation it was unclear for me
Can you upload the full snippet on https://mjml.io/try-it-live please ?

@iRyusa thanks for help.
https://mjml.io/try-it-live/rJFxo5KdW

I'm unable to reproduce with this snippet as you can see here every outlook are fine https://litmus.com/checklist/emails/public/c3c9c60

Could you try to test this version https://mjml.io/try-it-live/Bkd3FsF_- ?

Looks to work when removing mj-wrapper, I think you can remove it safely because it has no purpose on your design ?

Hi @KoalaMontana
Is this good for you now ? 👍

@iRyusa yes, it works. Thank you.


feat: remove unnecessary Result in Relocatable.add signature

method was never failing

Codecov Report

Merging #520 (2a2c009) into main (b99f77f) will increase coverage by 0.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #520      +/-   ##
==========================================
+ Coverage   92.00%   92.10%   +0.10%
==========================================
  Files          47       48       +1
  Lines        3152     3192      +40
==========================================
+ Hits         2900     2940      +40
  Misses        252      252

Impacted Files
Coverage Δ

...uiltin_hint_processor/cairo_keccak/keccak_hints.rs
87.50% <100.00%> (ø)

src/types/relocatable.rs
91.89% <100.00%> (ø)

src/cairo_run.rs
78.43% <0.00%> (-0.42%)
:arrow_down:

src/main.rs
5.00% <0.00%> (-0.27%)
:arrow_down:

src/vm/runners/builtin_runner/mod.rs
87.50% <0.00%> (ø)

src/vm/vm_core.rs
92.20% <0.00%> (+0.32%)
:arrow_up:

src/vm/runners/cairo_runner.rs
95.30% <0.00%> (+0.67%)
:arrow_up:

src/vm/vm_memory/memory_segments.rs
97.18% <0.00%> (+1.43%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@Oppen can you fix the CI. or merge despite of it?


daemon RPC API is missing generateblocks

generateblocks a niche API that is poorly documented, but the type of people using this library are typically running tests on their own code and need this method.
Example:
Start monerod in test mode:
monerod --detach --regtest --offline --fixed-difficulty=1 --rpc-bind-ip <IP_ADDRESS> --rpc-bind-port 18081

Request:
curl http://<IP_ADDRESS>:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"generateblocks","params":{
"amount_of_blocks":1,
"wallet_address":"42eTJxqsYwsSpFCRUp19vPAXNruqAUqnFMY2XN198643Ukrera958dY4qbRdoaoCVffhbC7ro4nzVBMw1E8ip7LAKG3SrsU"}' -H 'Content-Type: application/json'

Response:
{
  "id": "0",
  "jsonrpc": "2.0",
  "result": {
    "blocks": ["49b712db7760e3728586f8434ee8bc8d7b3d410dac6bb6e98bf5845c83b917e4"],
    "height": 9783,
    "status": "OK",
    "untrusted": false
  }
}

C++ reference:
https://github.com/monero-project/monero/blob/v<IP_ADDRESS>/src/rpc/core_rpc_server_commands_defs.h#L1076-L1107
The prev_block and starting_nonce are not important. I've never seen them documented anywhere, nor have I seen code that passed non-default values to those fields.  Here's another point of reference:
https://github.com/cirocosta/go-monero/blob/v0.0.5/pkg/rpc/daemon/jsonrpc.go#L153-L159

I added  prev_block and  starting_nonce even if it's unused since they might get used somewhere in the near future so it's best to follow the implementation

Thanks for all the work!  Yeah, I wasn't suggesting that those 2 fields shouldn't be added.  I just didn't think you would have information on how to document them.  I opened a ticket against the monero documentation for it:
https://github.com/monero-project/monero-site/issues/2026
Maybe one of the daemon authors will have a suggestion on how to document those fields.


can not be used on 32bit pfsense

Have you considered catering for 32bit pfsense with this script?
Being that the UniFi software is written in java, I cannot see a reason why this could not be adapted to be architecture independent.
I don't have enough knowledge to be able to so it myself however.

Agreed that an architecture check would be nice in the install script.
It might be as simple as changing the package source URL in the beginning of the script:
#FreeBSD package source:
FREEBSD_PACKAGE_URL="http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/"
Change to:
FREEBSD_PACKAGE_URL="http://pkg.freebsd.org/freebsd:10:x86:32/latest/All/"

Just spun up a 32bit VM and made some changes to the install script.  It works!   I did not test it thoroughly.  Sending Pull Request.

cheers...... i will have play and see how it goes

tried running your latest commit on the pull request but got a syntax error.

That latest commit is a work in progress.  Admittedly I am new to the pull request workflow.
Try the previous commit:
https://github.com/gozoinks/unifi-pfsense/pull/37/commits/f0cd38a257d8cfc4b4514dea02923d4f4337ba44

RE: pulls requests - you are ahead of me, as yet i have not been able to fully get my head around the workflow of git.
I ran a quick install test last night on the previous commit in a VM and it works like a charm. I am yet to evaluate the actual usage of UniFi in this manner yet (need to isolate my existing unifi ap's and test with the spare i have.
It does look promising however.
Great work.

Thanks for the feedback.  Let me us know how it works.

Just curious on the status of this issue, it looks like some changes were committed and then reverted. I'm running an i386 based Pfsense box on 2.3.2. Currently getting 'pkg: wrong architecture: FreeBSD:10:amd64 instead of FreeBSD:10:i386'

There has been one pass at detecting the appropriate architecture. There is
no doubt a way to do it, but I don't have an immediate solution. It may or
may not be complicated by having to manually declare all the dependencies.
If we can grab the system architecture and set a variable that builds the
appropriate package source string, this should be straightforward. Pull
requests welcome!
On Fri, Jul 29, 2016 at 6:10 AM, SaltyDH<EMAIL_ADDRESS>wrote:

Just curious on the status of this issue, it looks like some changes were
committed and then reverted. I'm running an i386 based Pfsense box on
2.3.2. Currently getting 'pkg: wrong architecture: FreeBSD:10:amd64 instead
of FreeBSD:10:i386'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gozoinks/unifi-pfsense/issues/36#issuecomment-236154689,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABn_sAWNSKp_an23Eg-ouu1C9Wc04umwks5qad-ogaJpZM4IuDxh
.

--
j

Hi Guys, I will send a pull request shortly for the OS detection update.  I had it completed before, but muddled up the commits.

Just finished doing a basic test of the 32bit version of the install script.  Unifi installed and I was able to configure it.  I presently have no APs to test it with.  Hopefully someone can test #44

Thanks for taking a look at this. The deps correctly resolved to 32bit versions.
However, I still received the following error:
Installing kbproto-1.0.7...
pkg: wrong architecture: FreeBSD:10:amd64 instead of FreeBSD:10:i386

Install log here: https://gist.github.com/SaltyDH/35a1627428704fa4ab62469a8e31bcaf#file-gistfile1-txt
Hope it helps

Second time's the charm! Ran the install command a second time and everything went through. I've been able to discover my UnFi AP AC Pro device, just trying to adopt and configure it now.

Thanks for the test.  I reran the install script again on my fresh 32bit VM and it ran again without the kbproto wrong architecture error.  Odd.  It even reports it was attempting to install the correct version:
ailed to install the following 1 package(s): http://pkg.freebsd.org/freebsd:10:x86:**32**/latest/All/kbproto-1.0.7.txz

I have seen package downloads get corrupted, and packages fail to install.

I believe this issue has been addressed and can now be closed.


05/27/20 Update

Finished AddNew Plant, Rendering Plant Data based on user, created user edit page.

Looks great!


API: Separate max transactions param from max block txns param

Summary
In #1241 we started using the MaxTransactionsLimit parameter to limit the number of transactions returned in the /v2/block API. That caused users who expected to receive the whole block to start getting errors when blocks with high numbers of txns were requested.
In order to enable users to set this limit but also enable those who would like to retrieve the entire block at once, I've set this limit to unlimited by default.
Since the MaxTransactionsLimit parameter was also previously being used in the /v2/transactions endpoint, I've separated the param to a new config option which will only control transactions returned in blocks.

Looks like I missed this one for the hotfix. Do you think we should bring it to develop?

Looks like I missed this one for the hotfix. Do you think we should bring it to develop?

I think it's a good change. I think it's not a big deal that we left this out since we fixed the block endpoint's memory consumption issues.


ruff-lsp: 0.0.42 -> 0.0.45

Description of changes
Changelog: https://github.com/astral-sh/ruff-lsp/releases/tag/v0.0.45
cc @figsoda @kalekseev

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[ ] 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.

Result of nixpkgs-review pr 266606 run on x86_64-linux 1

2 packages built:

ruff-lsp
ruff-lsp.dist

Result of nixpkgs-review pr 266606 run on aarch64-darwin 1

2 packages built:

ruff-lsp
ruff-lsp.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/getting-ruff-working-in-nvim/35305/2


TypeError: Cannot read properties of null (reading 'clear')

When running with the Tension Pool Module, I receive the following error:
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'clear')  PolyBuilder.ts:8
    at Y.clear (PolyBuilder.ts:8)
    at ControlIcon.draw (foundry.js:35392)

  | draw | @ | foundry.js:35392
  | async function (async) |   |
  | draw | @ | foundry.js:35389
  | ControlIcon | @ | foundry.js:35381
  | _drawControlIcon | @ | foundry.js:42964
  | draw | @ | foundry.js:42942
  | (anonymous) | @ | foundry.js:19710
  | map | @ | collection.mjs:145
  | draw | @ | foundry.js:19709
  | async function (async) |   |
  | draw | @ | foundry.js:19691
  | draw | @ | foundry.js:17676
  | async function (async) |   |
  | draw | @ | foundry.js:17671
  | 🎁call_wrapped | @ | libWrapper-wrapper.js:467
  | wrapper | @ | patch.js:17
  | 🎁call_wrapper | @ | libWrapper-wrapper.js:576
  | 🎁Canvas.prototype.draw#0 | @ | libWrapper-wrapper.js:164
  | view | @ | foundry.js:15619
  | initializeCanvas | @ | foundry.js:4514
  | async function (async) |   |
  | initializeCanvas | @ | foundry.js:4509
  | setupGame | @ | foundry.js:4388
  | async function (async) |   |
  | setupGame | @ | foundry.js:4375
  | _initializeGameView | @ | foundry.js:5213
  | _initializeView | @ | foundry.js:5189
  | initialize | @ | foundry.js:4286
  | async function (async) |   |
  | initialize | @ | foundry.js:4280
  | 🎁call_wrapped | @ | libWrapper-wrapper.js:467
  | 🎁libWrapperInit | @ | libWrapper-api.js:698
  | async function (async) |   |
  | 🎁libWrapperInit | @ | libWrapper-api.js:688
  | 🎁Game.prototype.initialize#0 | @ | libWrapper-wrapper.js:162
  | window.addEventListener.once | @ | foundry.js:53613
  | async function (async) |   |
  | window.addEventListener.once | @ | foundry.js:53612

  Foundry: 0.8.9
  System: dnd5e version 1.4.3
User:
  Role: GAMEMASTER
Settings:
  Disable_Canvas: Disabled
  Max_FPS: 60
  Token_Drag_Vision: Disabled
  Soft_Shadows: Enabled
  Token_Vision_Animation: Enabled
  Light_Source_Animation: Enabled
  Zoomed_Texture_Antialiasing: Enabled
  Animate_Roll_Tables: Disabled
Scene:
  Walls: 204
  Lights: 1
  Tokens: 14
  Tiles: 0
  Sounds: 0
  Drawings: 1
  Notes: 10
  Dimensions: 4800 x 6600
  Background: 4800 x 6976
  Foreground: 0 x 0
WebGL:
  Context: WebGL2RenderingContext
  GL_Vendor: WebKit
  Renderer: WebKit WebGL
  Unmasked_Renderer: ANGLE (NVIDIA, NVIDIA GeForce GTX 1080 Ti Direct3D11 vs_5_0 ps_5_0, D3D11-<IP_ADDRESS>41)
  WebGL_Version: WebGL 2.0 (OpenGL ES 3.0 Chromium)
  MAX_TEXTURE_SIZE: 16384
  MAX_RENDERBUFFER: 16384
Database:
  Actors: 265
  Items: 309
  Scenes: 75
  Journals: 941
  Tables: 86
  Chat: 252
  Macros: 415
Data_Sizes:
  Actors: 15.31 MB
  Items: 1.41 MB
  Scenes: 6.37 MB
  Journals: 6.93 MB
  Tables: 1.34 MB
  Chat: 254.75 KB
  Macros: 753.9 KB
Browser:
  Platform: Win32
  Vendor: Google Inc.
  Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36
Memory:
  Heap_Limit: 4 GB
  Heap_Total: 257.94 MB
  Heap_Used: 215.71 MB
Modules:
  Total: 373
  Enabled: 9
Active_Modules:
  _chatcommands: Library: Chat Commands v1.3.3
  debug-report: Debug Report Generator v0.0.2
  dice-so-nice: Dice So Nice! v4.1.5
  find-the-culprit: Find the culprit v1.4.0
  lib-wrapper: libWrapper v<IP_ADDRESS>
  perfect-vision: Perfect Vision v2.10.1
  socketlib: socketlib v1.0.9
  tension-pool: Tension Pool v0052
  forge-vtt: The Forge v1.10

Not caused by PV. See #SDoehren/tension-pool#20.

Not caused by PV. See SDoehren/tension-pool#20.

Well this in interesting because I had everything working just fine then I added this module and nothing else changed and now none of my scenes load and thats the error I get

@Wicked1667 This is a very old issue: a lot has changed since then. Please open a new issue.

Don't worry about it I actually did a little bit of my own investigating
and found out that it's actually something wrong with foundry rendering
something because I made a copy of one of my other worlds and tried
installing the model into that world and it didn't give me any errors
On Wed, Apr 5, 2023, 15:20 dev7355608 @.***> wrote:

@Wicked1667 https://github.com/Wicked1667 This is a very old issue: a
lot has changed since then. Please open a new issue.
—
Reply to this email directly, view it on GitHub
https://github.com/dev7355608/perfect-vision/issues/136#issuecomment-1497998618,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIOUMYYYNDLUOU25DXUQZ7LW7XAZVANCNFSM5EWU2HAQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Scrips in citus-tutorials are not documented

In citus-tutorial package, we have 3 scripts and two of them are not used/mentioned in the docs: start-example-citus-cluster and insert-live-wikipedia-edits. We may use them in a tutorial or update the package to prevent confusion.

@ozgune , @aamederen , now that we have a new tutorial, should we close this issue?

@samay-sharma I think so. AFAIS #291 removes the citus-tutorial package altogher.

Sounds good. Closing


Adds core.sync.event2.Event2

Checking whether the Event object is in initialized state every time then any of its methods are called is waste of CPU resources
I propose to intruduce new event struct which provides RAII interface and methods doesn't poisoned by if (m_initalized) checks

Is there a reason why there should be a completely new file event2.d for this. Why not append the additional type to event.d. You are allowed to have two types inside one file.
Also the name Event2 is kind of ambiguous. People will ask, why is there two versions of Event? A better name is EventS or EventStruct so that it is more obvious what it is about.

Yeah, and they're both structs too...

Yeah, and they're both structs too...

Just too used that everything are classes outwards. Then another name like EventNoInitCheck or something.

@IgorDeepakM

Is there a reason why there should be a completely new file event2.d for this? Why not append the additional type to event.d. You are allowed to have two types inside one file.

Yes, I can change this without any problems

Also the name Event2 is kind of ambiguous. People will ask, why are there two versions of Event? A better name is EventS or EventStruct so that it is more obvious what it is about.

Agree
@adamdruppe Which name do you like best?
@adamdruppe

Yeah, and they're both structs too...

Do you mean that they should be a classes? To avoid copying, makes sense
But I thought that such changes should not be made because events are involved in garbage collection, and I think it may cause some kind of endless loop

Yeah, and they're both structs too...

Just too used that everything are classes outwards. Then another name like EventNoInitCheck or something.

EventWait?

Another question is if we really need the old one. Why wouldn't it be initialized? That would be if the OS primitives fails to be created but one can argue if that is a fatal error.
For the other primitives like mutex and semaphores, there no such checks and if they fail there is usually an assert or Error is being thrown.

I think the original one is how it is because D doesn't have any kind of default constructor, so you might forget to initialize it. Maybe just @disable this(); on that would be ok to make it work.

Another question is if we really need the old one.

For backward compatibility with D: old Event isn't fails if struct isn't initialized and such behaviour could been used somehere

setIfInitialized is a new thing anyway. It was called set until... some time last year. Very recent.

Yes, I renamed it: https://github.com/dlang/dmd/pull/15800

I actually meant remove Event and replace it with EventAwaiter (named just Event). Then the code inside the opend repo that uses setIfInitialized needs to be changed to set.

I actually meant remove Event and replace it with EventAwaiter (named just Event).

This can lead to hard to find errors in a code that relies on possibility of not initializing an Event

Then the code inside the opend repo that uses setIfInitialized needs to be changed to set.

Here is no such code


Question possibility to create salesOrder with lines in one request?

If this is possible I would love to see some documentation on it, also if it is possible to set shippingAddress.
As for all e-commerce systems there is always an invoice and shipping address but I only see invoice now.

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

ID: ab8727c9-7b8e-2c83-680f-7f5c8a4ec22c
Version Independent ID: dc43f5e7-d5d9-48e7-b74d-460b5a70150e
Content: Create salesOrderLines - Dynamics NAV
Content Source: dynamics-nav/fin-graph/api/dynamics_create_salesorderline.md
Service: dynamics365-financials
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

You will need to add salesOrderLines to a request body to create a salesOrder with lines in one request.
Content-type: application/json
POST /api/beta/companies({companyId})/salesOrders
Content-type: application/json
{
"customerId":"{customerId}",
"salesOrderLines": [
{
"quantity":  1,
"itemId":"{itemId}"
}
]
}
Shipping address on sales orders was added in API v1.0. This field is missing in API version beta. You can see all the fields for salesOrder in the $metadata.
POST /api/v1.0/companies({companyId})/salesOrders
Content-type: application/json
{
"customerId":"{customerId}",
"shippingPostalAddress": {
"countryLetterCode":"US",
"postalCode":"1",
"city":"A",
"state":"B",
"street":"C"
}
}


Add support for Python 3.7

Codecov Report

Merging #75 into master will not change coverage.
The diff coverage is 94.11%.

@@           Coverage Diff           @@
##           master      #75   +/-   ##
=======================================
  Coverage   94.81%   94.81%
=======================================
  Files          31       31
  Lines        2857     2857
=======================================
  Hits         2709     2709
  Misses        148      148

Impacted Files
Coverage Δ

stix2validator/enums.py
93.89% <100%> (ø)
:arrow_up:

stix2validator/shoulds.py
94.67% <100%> (ø)
:arrow_up:

stix2validator/musts.py
94.32% <87.5%> (ø)
: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 024fd25...2a4b98e. Read the comment docs.


New types - DisabledRule and RuleToggle

Description
New types - DisabledRule and RuleToggle
Type of change

New feature (non-breaking change which adds functionality)

Testing steps
N/A

Codecov Report

Merging #185 (6c9b763) into master (49ac6d0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #185   +/-   ##
=======================================
  Coverage   90.84%   90.84%
=======================================
  Files          21       21
  Lines         808      808
=======================================
  Hits          734      734
  Misses         62       62
  Partials       12       12

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 49ac6d0...6c9b763. Read the comment docs.


Provide prefix mapping through the environment

There should be a way to provide prefix mappings through the environment, rather than having to always put it into the Tarql mapping. That is simply for convenience if you have lots of mappings in a project. You could load them using the “background knowledge” mechanism proposed in #33, where the mappings should be expressed as VANN mappings (e.g., in a form compatible with http://prefix.cc/popular/all.file.vann).

Or using the PROLOGUE feature I proposed for SPARQL 1.2.


cell type-aware embedding

Description of feature
Dear DRVI team,
This is a great tool and am enjoying using it a lot. I am just wondering if there are any plans to incorporate cell-type awareness into the model, similar to SCANVI and MRVI?
Many thanks

Dear Bo,
We're delighted to hear that you're enjoying it.
Incorporating supervised information, such as cell types, is indeed an interesting idea. However, DRVI is fundamentally designed for unsupervised discovery in single-cell omics. One of its key strengths is its ability to remain unbiased with respect to potentially imperfect supervised annotations, allowing DRVI to uncover patterns and insights that go beyond existing annotations.
Extending the model to incorporate supervised information is a lower priority than other directions outlined in the discussions section of the paper. Users often incorporate cell-type information to improve integration performance —when the integration performance is measured by the same annotations— introducing a circular logic that we aim to avoid. We’re always open to revisiting our priorities based on compelling use cases. Do you have a reasonable example or scenario where embedding such supervised information could significantly enhance users' analyses? We'd love to hear your perspective.


Add meta event reporting

This PR adds support for reporting 'meta events' - detailed lifecycle information about a tracer and its spans - to the Go tracer. It can be enabled via the MetaEventLogging flag in options. This option is not suitable for production environments as it generates a significant amount of spans.

@MatthewDolan We could, but we don't implement the DevMode flag in Thrift so this one would be kinda hacky.

Yeah, I agree with @MatthewDolan that it feels like Thrift should be removed independently. I can open a separate PR to do that as a first step.

Nah, I can open one real quick @iredelmeier

@iredelmeier @MatthewDolan see #189

@iredelmeier @MatthewDolan @jmacd The separate thrift PR has been merged and this one is clean for review.