2024-10-15 21:00:47.105437 [INFO] evse_security:E  :: Module evse_security initialized [3600ms]
2024-10-15 21:00:47.098469 [INFO] token_validator  :: Module token_validator initialized [3490ms]

2024-10-15 21:00:47.120089 [INFO] iso15118_charge  :: TCP server on eth1 is listening on port [fe80::122c:797c:de49:474a%3]:61341

2024-10-15 21:00:47.120978 [INFO] iso15118_charge  :: TLS server on eth1 is listening on port [fe80::122c:797c:de49:474a%3]:641092024-10-15 21:00:47.108623 [INFO] token_provider:  :: Module token_provider initialized [3500ms]

2024-10-15 21:00:47.121292 [INFO] iso15118_charge  :: SDP socket setup succeeded
2024-10-15 21:00:47.124899 [INFO] iso15118_charge  :: Module iso15118_charger initialized [3529ms]
2024-10-15 21:00:47.162707 [INFO] yeti_driver_1:M  :: Initializing MMWBSP
2024-10-15 21:00:47.163305 [INFO] yeti_driver_1:M  :: log message before the new connector hardcoding
2024-10-15 21:00:47.163458 [INFO] yeti_driver_1:M  :: FILE WITH HARDCODED CONNECTOR TYPE!
2024-10-15 21:00:47.164208 [INFO] yeti_driver_1:M  :: Module yeti_driver_1 initialized [3500ms]
2024-10-15 21:00:47.200673 [INFO] api:API          :: Module api initialized [3825ms]
2024-10-15 21:00:47.256126 [INFO] slac:EvseSlac    :: Module slac initialized [3648ms]
2024-10-15 21:00:47.584714 [INFO] connector_1:Evs  :: Module connector_1 initialized [4112ms]
2024-10-15 21:00:49.067936 [INFO] manager          :: 🚙🚙🚙 All modules are initialized. EVerest up and running [6838ms] 🚙🚙🚙
sh: 1: echo: echo: I/O error
cobsDecode: Garbage detected
2024-10-15 21:00:49.169164 [INFO] slac:EvseSlac    :: Starting the SLAC state machine
2024-10-15 21:00:49.170590 [INFO] slac:EvseSlac    :: Qualcomm PLC Device Attributes:
  HW Platform: QCA7000
  SW Platform: MAC
  Firmware:
  Build date: 1.2.5-0
  ZC signal: Missing
  Line frequency: 50Hz
2024-10-15 21:00:49.270996 [INFO] slac:EvseSlac    :: Entered Reset state
2024-10-15 21:00:49.271259 [INFO] slac:EvseSlac    :: New NMK key: 43:37:4E:58:39:41:41:52:4D:4C:30:59:34:4E:47:50
2024-10-15 21:00:49.271811 [INFO] slac:EvseSlac    :: Received CM_SET_KEY_CNF
2024-10-15 21:00:49.272551 [INFO] slac:EvseSlac    :: Entered Idle state
2024-10-15 21:00:49.517694 [INFO] connector_1:Evs  :: Max AC hardware capabilities: 6A/3ph
2024-10-15 21:00:49.577299 [INFO] connector_1:Evs  :: AC HLC mode enabled.

2024-10-15 21:00:49.632972 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 0.000000, we get 0.000000
2024-10-15 21:00:49.683111 [INFO] connector_1:Evs  :: 🌀🌀🌀 Ready to start charging 🌀🌀🌀

2024-10-15 21:00:49.843083 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 0.000000, we get 0.000000
2024-10-15 21:00:59.603321 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 21:00:59.704037 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 21:00:59.804667 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 21:00:59.905352 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 21:01:00.006025 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 21:01:00.106656 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 21:01:00.207342 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 21:01:00.307978 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 21:01:00.408608 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.

Yay! I knew it had worked for me! Such a weird issue, and so annoying
Now it's time to go to the lab and plug it in?!!

Now it's time to go to the lab and plug it in?!!

I think we are tracking that as a separate issue, so once you have checked over the configs, and confirmed that it consistently runs, we can go ahead and close this one (finally!!)

I will also point out that this only works if we disable the energy manager, which results in a max current of 0.
Not sure if this will be a problem.
2024-10-15 23:09:56.883206 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 0.000000, we get 0.000000
2024-10-15 23:09:56.925627 [INFO] connector_1:Evs  :: 🌀🌀🌀 Ready to start charging 🌀🌀🌀

2024-10-15 23:09:57.009075 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 0.000000, we get 0.000000
2024-10-15 23:10:06.898035 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-15 23:10:06.998978 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.

In the SIL, if I enable the energy manager, it still crashes. @Abby-Wheelis can you confirm that this is true even on hardware?
Will spend a time-bounded effort tonight to see if I can get the energy manager to stop crashing so that we can try to actually send a real current value.

ok so the energy manager thing is weird. It looks like everything crashes ~ 10 seconds after the manager starts
I enabled debug logging in build/dist/etc/everest/default_logging.cfg and added several sleep statements to the main energy manager loop.
new_sleep_statements.patch
If none of the sleep statements are in place, the energy manager crashes after 999 runs
no_sleeps.log
$ grep "Run energy optimizer" /tmp/no_sleeps.log | wc -l
     999

If all the sleep statements are in place, the energy manager crashes after a single run
all_sleeps.log
$ grep "Run energy optimizer" /tmp/all_sleeps.log | wc -l
       1

In both cases, the crash occurred after around 10 seconds
$ head -n1 /tmp/no_sleeps.log
2024-10-16 00:40:36.868416 [INFO] manager          ::   ________      __                _
$ tail -n1 /tmp/no_sleeps.log
2024-10-16 00:40:42.411856 [CRIT] manager         int boot(const boost::program_options::variables_map&) :: Exiting manager.

$ head -n1 /tmp/all_sleeps.log
2024-10-16 00:52:21.105189 [INFO] manager          ::   ________      __                _
$ tail -n1 /tmp/all_sleeps.log
2024-10-16 00:52:33.012974 [CRIT] manager         int boot(const boost::program_options::variables_map&) :: Exiting manager.

So I suspect this is related to some kind of threading/timing issue and not a particular issue with the code.
Note also that the optimizer doesn't actually return any values; in the no_sleep case, it consistently returns a vector of length 0. Can we just hack this to set the energy limit once and disable the thread? that would be the most surgical change...

Looking at logs from a prior successful SIL run (non-cross-compiled), I can see that the optimizer returns a vector with a single value

2024-07-17 22:26:45.186727 [INFO] energy_manager:  ::                                NO TRADE
2024-07-17 22:26:45.186918 [INFO] energy_manager:  :: Sending enfored limits (import) to :evse_manager_1 {
"ac_max_current_A": 32.0
}
2024-07-17 22:26:45.186986 [INFO] energy_manager:  :: returning optimized values vector of length 1
2024-07-17 22:26:45.187077 [INFO] energy_manager:  :: evse_manager_1 Enforce limits 32A -9999W

let's try to return that value and see how it goes.

After the changes, I see
2024-10-16 01:40:09.569465 [INFO] energy_manager:  :: about to init globals again
2024-10-16 01:40:09.570124 [INFO] energy_manager:  :: about to lock the energy mutex
2024-10-16 01:40:09.570222 [INFO] energy_manager:  :: launched the mutex
2024-10-16 01:40:09.570526 [INFO] energy_manager:  :: returning optimized values vector of length 1
2024-10-16 01:40:09.570684 [INFO] energy_manager:  :: ran optimizer in the ready loop, got values 1
2024-10-16 01:40:09.570825 [INFO] energy_manager:  :: my_fake_uuid Enforce limits 32A -9999W

And then a crash
Will fix the UUID to evse_manager_1, but the issue is clearly not with the values returned but with the thread. Trying to set the values once and not launching the thread at all...

In the SIL, if I enable the energy manager, it still crashes. @Abby-Wheelis can you confirm that this is true even on hardware?

Yes, I can confirm that the energy_manager also seems to crash shortly after startup, I restored

 this
-  energy_manager:
-    connections:
-      energy_trunk:
-        - implementation_id: energy_grid
-          module_id: grid_connection_point
-    module: EnergyManager

And then ran, seeing lots of logs that I added, and a crash from energy_manager

 logs:
$ sudo /mnt/user_data/opt/everest/bin/manager --conf /mnt/user_data/opt/everest/etc/everest/config-sil-no-crash.yaml
sudo: unable to resolve host umwcdbde: Name or service not known
2024-10-16 16:20:42.204488 [INFO] manager          ::   ________      __                _
2024-10-16 16:20:42.204978 [INFO] manager          ::  |  ____\ \    / /               | |
2024-10-16 16:20:42.205069 [INFO] manager          ::  | |__   \ \  / /__ _ __ ___  ___| |_
2024-10-16 16:20:42.205347 [INFO] manager          ::  |  __|   \ \/ / _ \ '__/ _ \/ __| __|
2024-10-16 16:20:42.205478 [INFO] manager          ::  | |____   \  /  __/ | |  __/\__ \ |_
2024-10-16 16:20:42.205605 [INFO] manager          ::  |______|   \/ \___|_|  \___||___/\__|
2024-10-16 16:20:42.205777 [INFO] manager          ::
2024-10-16 16:20:42.205919 [INFO] manager          :: Using MQTT broker localhost:1883
2024-10-16 16:20:42.206048 [INFO] manager          :: Telemetry enabled
2024-10-16 16:20:42.225010 [INFO] everest_ctrl     :: Launching controller service on port 8849
2024-10-16 16:20:42.290588 [INFO] manager          :: Loading config file at: /mnt/user_data/opt/everest/etc/everest/config-sil-no-crash.yaml
2024-10-16 16:20:43.257814 [INFO] manager          :: Config loading completed in 1048ms
2024-10-16 16:20:46.946623 [INFO] energy_manager:  :: Module energy_manager initialized [3481ms]
2024-10-16 16:20:47.294016 [INFO] token_validator  :: Module token_validator initialized [3603ms]
2024-10-16 16:20:47.457844 [INFO] auth:Auth        :: Module auth initialized [4108ms]
2024-10-16 16:20:47.478470 [INFO] api:API          :: INIT API module
2024-10-16 16:20:47.508750 [INFO] token_provider:  :: Module token_provider initialized [3970ms]
2024-10-16 16:20:47.534440 [INFO] grid_connection  :: Module grid_connection_point initialized [4043ms]
2024-10-16 16:20:47.591294 [INFO] api:API          :: Module api initialized [4224ms]
2024-10-16 16:20:47.667752 [INFO] yeti_driver_1:M  :: Initializing MMWBSP

2024-10-16 16:20:47.676306 [INFO] yeti_driver_1:M  :: log message before the new connector hardcoding
2024-10-16 16:20:47.676629 [INFO] yeti_driver_1:M  :: FILE WITH HARDCODED CONNECTOR TYPE!
2024-10-16 16:20:47.676107 [INFO] iso15118_charge  :: TCP server on eth1 is listening on port [fe80::fbba:70d9:9849:a121%3]:61341

2024-10-16 16:20:47.677077 [INFO] iso15118_charge  :: TLS server on eth1 is listening on port [fe80::fbba:70d9:9849:a121%3]:64109

2024-10-16 16:20:47.677619 [INFO] iso15118_charge  :: SDP socket setup succeeded
2024-10-16 16:20:47.678083 [INFO] yeti_driver_1:M  :: Module yeti_driver_1 initialized [3925ms]
2024-10-16 16:20:47.679090 [INFO] iso15118_charge  :: Module iso15118_charger initialized [4048ms]
2024-10-16 16:20:47.743297 [INFO] evse_security:E  :: Module evse_security initialized [4162ms]
2024-10-16 16:20:47.835952 [INFO] slac:EvseSlac    :: Module slac initialized [4159ms]
2024-10-16 16:20:48.041326 [INFO] connector_1:Evs  :: Module connector_1 initialized [4598ms]
2024-10-16 16:20:49.157922 [INFO] manager          :: 🚙🚙🚙 All modules are initialized. EVerest up and running [6984ms] 🚙🚙🚙
2024-10-16 16:20:49.160513 [INFO] energy_manager:  :: NEW LOG STATEMENT
sh: 1: echo: echo: I/O error
2024-10-16 16:20:49.188471 [INFO] energy_manager:  :: returning optimized values vector of length 0
2024-10-16 16:20:49.204564 [INFO] slac:EvseSlac    :: Starting the SLAC state machine
2024-10-16 16:20:49.206176 [INFO] slac:EvseSlac    :: Qualcomm PLC Device Attributes:
  HW Platform: QCA7000
  SW Platform: MAC
  Firmware:
  Build date: 1.2.5-0
  ZC signal: Missing
  Line frequency: 50Hz
2024-10-16 16:20:49.306508 [INFO] slac:EvseSlac    :: Entered Reset state
2024-10-16 16:20:49.306791 [INFO] slac:EvseSlac    :: New NMK key: 49:30:45:4E:59:58:41:44:46:54:53:41:39:5A:48:37
2024-10-16 16:20:49.307355 [INFO] slac:EvseSlac    :: Received CM_SET_KEY_CNF
2024-10-16 16:20:49.307785 [INFO] slac:EvseSlac    :: Entered Idle state
2024-10-16 16:20:49.592767 [INFO] connector_1:Evs  :: Max AC hardware capabilities: 6A/3ph
2024-10-16 16:20:49.755591 [INFO] connector_1:Evs  :: AC HLC mode enabled.

2024-10-16 16:20:49.808876 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 0.000000, we get 0.000000
2024-10-16 16:20:49.857819 [INFO] connector_1:Evs  :: 🌀🌀🌀 Ready to start charging 🌀🌀🌀

2024-10-16 16:20:50.011078 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 0.000000, we get 0.000000
2024-10-16 16:20:50.454433 [CRIT] manager         int boot(const boost::program_options::variables_map&) :: Module energy_manager (pid: 1593) exited with status: 139.

Bump up the validity to 3600,000 (just in case it is milliseconds) -- did not get fixed

Set the limits in the loop without calling the optimizer - does not crash, but we are still getting the `Power budget expired, falling back to 0.` message. Note that this is more of an indication of how the problem is with the mutex
        while(true) {
            std::vector<types::energy::EnforcedLimits> optimized_values;
            optimized_values.reserve(1);
            EVLOG_info << "about to init globals again";
            globals.init(date::utc_clock::now(), config.schedule_interval_duration, config.schedule_total_dur
                         config.slice_ampere, config.slice_watt, config.debug, energy_flow_request);
            // auto optimized_values = run_optimizer(energy_flow_request);
            // EVLOG_info << "ran optimizer in the ready loop, got values " << optimized_values.size();
            if (optimized_values.size() == 0) {
                types::energy::EnforcedLimits l;
                l.uuid = "evse_manager_1";
                l.valid_until =
                        Everest::Date::to_rfc3339(globals.start_time + std::chrono::seconds(3600000));
                types::energy::LimitsRes r;
                r.ac_max_current_A = 32;
                l.limits_root_side = r;
                optimized_values.push_back(l);
            }

            enforce_limits(optimized_values);
            EVLOG_info << "enforced limits with " << optimized_values.size();
        }

generates
2024-10-16 18:15:51.891699 [INFO] energy_manager:  :: enforced limits with 1
2024-10-16 18:15:51.891839 [INFO] energy_manager:  :: about to init globals again
2024-10-16 18:15:51.892061 [INFO] energy_manager:  :: evse_manager_1 Enforce limits 32A -9999W
2024-10-16 18:15:51.976614 [INFO] energy_manager:  :: enforced limits with 1
2024-10-16 18:15:51.976697 [INFO] energy_manager:  :: about to init globals again
2024-10-16 18:15:51.976861 [INFO] energy_manager:  :: evse_manager_1 Enforce limits 32A -9999W
2024-10-16 18:15:51.982200 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-16 18:15:52.063449 [INFO] energy_manager:  :: enforced limits with 1
2024-10-16 18:15:52.063567 [INFO] energy_manager:  :: about to init globals again
2024-10-16 18:15:52.063797 [INFO] energy_manager:  :: evse_manager_1 Enforce limits 32A -9999W
2024-10-16 18:15:52.083250 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.
2024-10-16 18:15:52.183896 [WARN] connector_1:Evs bool module::Charger::power_available() :: Power budget expired, falling back to 0.

So we do need to muck around with the iso15118_charger code to stop the power budget from expiring...

Found those logs in `modules/EvseManager/Charger.cpp`
// returns whether power is actually available from EnergyManager
// i.e. max_current is in valid range
bool Charger::power_available() {
    if (shared_context.max_current_valid_until < date::utc_clock::now()) {
        EVLOG_warning << "Power budget expired, falling back to 0.";
        if (shared_context.max_current > 0.) {
            shared_context.max_current = 0.;
            signal_max_current(shared_context.max_current);
        }
    }
    return (get_max_current_internal() > 5.9);
}

max_current_valid_until is set in Charger::set_max_current(float c, std::chrono::time_point<date::utc_clock> validUntil), which is called from ../modules/EvseManager/EvseManager.cpp (charger->set_max_current(0.0F, date::utc_clock::now() + std::chrono::seconds(10));)
    //  start with a limit of 0 amps. We will get a budget from EnergyManager that is locally limited by hw
    //  caps.
    charger->set_max_current(0.0F, date::utc_clock::now() + std::chrono::seconds(10));

So that is where the original (expiring) limit comes from. Why aren't we getting any values from the EnergyManager?
Aha! It looks like handle_enforce_limits can be called from EnergyNode or EvseManager
# grep -r handle_enforce_limits ../modules
../modules/EvseManager/energy_grid/energyImpl.hpp:    virtual void handle_enforce_limits(types::energy::EnforcedLimits& value) override;
../modules/EvseManager/energy_grid/energyImpl.cpp:void energyImpl::handle_enforce_limits(types::energy::EnforcedLimits& value) {
../modules/EnergyNode/energy_grid/energyImpl.hpp:    virtual void handle_enforce_limits(types::energy::EnforcedLimits& value) override;
../modules/EnergyNode/energy_grid/energyImpl.cpp:void energyImpl::handle_enforce_limits(types::energy::EnforcedLimits& value) {

And both of them check to see if the response is "for them"
    // is it for me?
    if (value.uuid == energy_flow_request.uuid) {

Let's see if that is why they are ignoring the limit...

Bingo!
2024-10-16 19:14:59.070561 [INFO] energy_manager:  :: enforced limits with 1
2024-10-16 19:14:59.070646 [INFO] energy_manager:  :: about to init globals again
2024-10-16 19:14:59.070853 [INFO] energy_manager:  :: evse_manager_1 Enforce limits 32A -9999W
2024-10-16 19:14:59.112087 [ERRO] grid_connection virtual void module::energy_grid::energyImpl::handle_enforce_limits(types::energy::EnforcedLimits&) :: In EnergyNode: for UUID of grid_connection_point, received limit of {
    "limits_root_side": {
        "ac_max_current_A": 32.0
    },
    "uuid": "evse_manager_1",
    "valid_until": "2024-11-27T11:14:59.070Z"
}
2024-10-16 19:14:59.154161 [ERRO] connector_1:Evs virtual void module::energy_grid::energyImpl::handle_enforce_limits(types::energy::EnforcedLimits&) :: EvseManager: for connector_1, received limit of {
    "limits_root_side": {
        "ac_max_current_A": 32.0
    },
    "uuid": "evse_manager_1",
    "valid_until": "2024-11-27T11:14:59.070Z"
}

Changed the UUID to match and everything seems to work now
2024-10-16 19:21:07.974365 [INFO] energy_manager:  :: enforced limits with 1
2024-10-16 19:21:07.974448 [INFO] energy_manager:  :: about to init globals again
2024-10-16 19:21:07.974649 [INFO] energy_manager:  :: connector_1 Enforce limits 32A -9999W
2024-10-16 19:21:08.015554 [ERRO] grid_connection virtual void module::energy_grid::energyImpl::handle_enforce_limits(types::energy::EnforcedLimits&) :: In EnergyNode: for UUID of grid_connection_point, received limit of {
    "limits_root_side": {
        "ac_max_current_A": 32.0
    },
    "uuid": "connector_1",
    "valid_until": "2024-11-27T11:21:07.974Z"
}
2024-10-16 19:21:08.032377 [ERRO] connector_1:Evs virtual void module::energy_grid::energyImpl::handle_enforce_limits(types::energy::EnforcedLimits&) :: EvseManager: for connector_1, received limit of {
    "limits_root_side": {
        "ac_max_current_A": 32.0
    },
    "uuid": "connector_1",
    "valid_until": "2024-11-27T11:21:07.974Z"
}

2024-10-16 19:21:08.034156 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 32.000000, we get 32.000000

@Abby-Wheelis can you also apply this additional patch and re-enable the energy manager?
Change the while(true) loop in modules/EnergyManager/EnergyManager.cpp to
        while(true) {
            std::vector<types::energy::EnforcedLimits> optimized_values;
            optimized_values.reserve(1);
            EVLOG_info << "new round of optimization launched";
            globals.init(date::utc_clock::now(), config.schedule_interval_duration, config.schedule_total_durat
                         config.slice_ampere, config.slice_watt, config.debug, energy_flow_request);
            // auto optimized_values = run_optimizer(energy_flow_request);
            // EVLOG_info << "ran optimizer in the ready loop, got values " << optimized_values.size();
            if (optimized_values.size() == 0) {
                types::energy::EnforcedLimits l;
                l.uuid = "connector_1";
                l.valid_until =
                        Everest::Date::to_rfc3339(globals.start_time + std::chrono::seconds(config.update_interval * 10));
                types::energy::LimitsRes r;
                r.ac_max_current_A = 32;
                l.limits_root_side = r;
                optimized_values.push_back(l);
            }

            enforce_limits(optimized_values);
            EVLOG_info << "enforced limits with " << optimized_values.size();
            {
                std::unique_lock<std::mutex> lock(mainloop_sleep_mutex);
                mainloop_sleep_condvar.wait_for(lock, std::chrono::seconds(config.update_interval));
            }
        }

I have also attached the expected logs. Once you confirm that this works, we can close this issue and move to #75

I see you are running into a lot of issues, but I do not understand what problem you are solving here? The umwc yocto image comes with an sdk that can be used to cross compile Everest and install it under /var/everest and it just works.

Why do you want to hardcode the uuid? This is definitely wrong.

@corneliusclaussen our current plan for the CharIN milestone is to experiment with plugging in and yocto builds in parallel.
I encourage you to look at the milestone tasks (https://github.com/EVerest/everest-demo/milestone/1), this is just one of them 😄 Let us know if you have any feedback on our plans!

Concretely, for plugging in, on the uMWC, we are running the release from Mar/Apr 2024 + the hacks that AFS gave me for the OCPP managed charging in June + the hacks that I put in during CharIN week on raspbian.

This is already so hacky that a hardcoded uuid is the least of our problems. We are not going to submit this - it is throwaway code to allow us to make progress. I did think about changing it to energy_flow_request.uuid but felt like I had spent enough time on this already.
This will allow us to make progress in plugging the uMWC into an EV/EV simulator at NREL and debugging the electrical components. At CharIN, I got everything to build and run on the last day, but the charge session was not initiated (apparently because we didn't send the 5% PWM) and I wasn't sure how to debug in the 30 minutes that I had.

In parallel, we are working on rolling forward to the most recent release, which has the correct, non-hacky implementation of managed charging from AFS

We will indeed use Yocto after we roll forward
This will let move from a working system to a working system and help us isolate whether the issues that we see are due to hardware or software.

Iirc all you want to do is cross compile Everest and run it on the umwc, that's why I don't understand why you are running into so many issues. I think it is a combination of a very old Debian image and a very old Everest version with lots of changes.

Yup. Note that the first issue that I ran into was the SSL version - everest had rolled forward to SSL3, but debian (or at least the toolchain) had only SSL1 installed - 90% of my hacks were related to rolling back to the older version of SSL.
https://github.com/EVerest/everest-demo/issues/51#issuecomment-2166696592 and onwards.
I am still not sure what is causing this most recent error with the run_optimizer - I did not change it in June, and was able to start up properly. But now, it is crashing consistently, both in SIL and in hardware. We are not going to spend additional time investigating since it is so old and the code is so hacky.
I think that part of it was also a little bit of "too many cooks" - AFS made the smart charging changes; I did the initial cross-compile, and then tried to hand it off to @Abby-Wheelis  and @faizanmir21 who are on-site and can access the EV lab, but don't have a lot of experience with EVerest.
But going forward, as we update to a more recent version, we will use yocto, and hopefully it will be simpler.
@catarial has already been able to compile the most recent version of everest on a pi zero, and is working on the yocto build next.
We will be tracking the work required to get the yocto build to work in #76 Fingers crossed that it will be smooth sailing!

@Abby-Wheelis can you also apply this additional patch and re-enable the energy manager?

I made this patch (was there another patch I needed to make too? It looks like most of the other work was logging/troubleshooting) and restored the manager, and it no longer seems to be crashing.

I have also attached the expected logs.

Are these the logs you were talking about?

Changed the UUID to match and everything seems to work now

 If so, then I believe that is what I am seeing, after initialization I am seeing a loop of messages:
2024-10-16 22:26:51.075596 [INFO] connector_1:Evs  :: 🌀🌀🌀 Ready to start charging 🌀🌀🌀

2024-10-16 22:26:51.224352 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 0.000000, we get 0.000000
2024-10-16 22:26:52.020574 [INFO] energy_manager:  :: new round of optimization launched

2024-10-16 22:26:52.087538 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 32.000000, we get 32.000000
2024-10-16 22:26:52.139143 [INFO] energy_manager:  :: enforced limits with 1
2024-10-16 22:26:53.139522 [INFO] energy_manager:  :: new round of optimization launched

2024-10-16 22:26:53.157806 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 32.000000, we get 32.000000
2024-10-16 22:26:53.210145 [INFO] energy_manager:  :: enforced limits with 1
2024-10-16 22:26:54.210580 [INFO] energy_manager:  :: new round of optimization launched

2024-10-16 22:26:54.228634 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: In ISO15118 charger impl, after updating AC max current to 32.000000, we get 32.000000
2024-10-16 22:26:54.279238 [INFO] energy_manager:  :: enforced limits with 1
2024-10-16 22:26:55.279616 [INFO] energy_manager:  :: new round of optimization launched

No, only this patch.
All looks good. I am closing this.
Further updates on creating a custom version of EVerest using the new yocto method will be tracked in #76
Further updates on plugging this custom version into a hardware simulator/EV will be tracked in #75
Hopefully rolling forward will be smoother.
One task down, four to go!


nvidiaLegacy304: fix build

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/37768 (dead link on debian.org)
Fixes https://github.com/NixOS/nixpkgs/issues/33395 (nvidia-setings in 32-bit only app in 304 version)

Thanks! I've changed your patch -- instead of fixing #33395 in a NixOS module we now force i686 build for the package itself. I've also taken this opportunity to cleanup NVIDIA a little (drop old 173 driver and tighten platforms).


Calling unknown method: yii\mongodb\ActiveQuery::createCommand()

What steps will reproduce the problem?
On saving/update a model at unique validation
What's expected?
validate uniqueness of a row before inserting
What do you get instead?
Unknown Method – yii\base\UnknownMethodException
Calling unknown method: yii\mongodb\ActiveQuery::createCommand()
Additional info
validation rukes are as follow
[['content'],'unique','targetAttribute'=>['content','created_by'],'message'=>'Seem you already a contact with this email address'],           [['guid'],'unique','targetAttribute'=>['guid','created_by'],'message'=>'Seem you already a contact

Q
A

Yii version

Yii MongoDB version

MongoDB server version

PHP version

Operating system

Please provide full error stack-trace

@klimov-paul it is a BC break in framework code, see https://github.com/yiisoft/yii2/issues/13485

I see.
The issue will tracked at  yiisoft/yii2#13485 then.


Rename 'PLabel' form v1.Partition to 'Name'

Signed-off-by: David Cassany<EMAIL_ADDRESS>

Lets admit it, having this v1.Partition.PLabel and v1.Partition.Label attributes was not a good idea of mine. PLabel is suposed to stand for the partition label and, at least in installer code, it is used only to feed parted on GPT (there is no such a think for MBR).
Using Name and assume this is the static name (not configurable in any way) can be useful to identify partitions regardless of any crazy label the user decides to use. This meant to be only used internally.


Use System.nanoTime() when building Duration objects

Favor System.nanoTime() to System.currentTimeMillis() because
System.currentTimeMillis() is not monotonic.

Fixes #3599.  I grepped the codebase for all uses of System.currentTimeMillis().

Thanks for taking this on! Can you also check for instances that indirectly derive from a non-monotonic clock? For example, line 149 in QueryStateMachine is not safe because it subtracts two values derived from DateTime.now(): elapsedTime = new Duration(endTime.get().getMillis() - createTime.getMillis(), MILLISECONDS);

Please remove the leading "*" and extra field "Testing" from your commit message.

@electrum yep, sure thing!
Sorry I didn't give this attention over the past week. I was busy with other stuff but now I've freed up and should provide an update soon.

Rebased on master and addressed @electrum's commit message comments.
I did a more thorough investigation this time, manually going through all the ways in which you can build a Duration object: nanosSince(), succinctNanos(), succinctDuration() and new Duration(). For each usage I ensured that the origin of the arguments could be traced back to a monotonically increasing clock. I didn't find any blatantly wrong usage other than the changes included in this PR. I paid particular attention to the following classes: QueryStateMachine, QueryStats, StageStateMachine, StageStats, TaskContext, TaskStats, PipelineContext, PipelineStats, DriverContext, DriverStats and OperatorContext. If there are other classes that you know might be susceptible to this problem, I'd be happy to go and check.
The only other dubious calculation of elapsed time I found was in OperatorContext.recordGeneratedInput(). Maybe we can add a check to set readNanos to zero if we ever get passed a negative value? I examined the current usages of the method and it seems that all calculations are done safely.

I made that minor change and merge it. Thanks!


Libtrust status?

Hi,
Wanted to check if libtrust is still actively maintained and if new PRs are accepted? Or have you migrated this activity to any other repo? Thanks.

It is still maintained, if you have bug fixes please submit a PR. If you have a feature request, please open up an issue or proposal PR.  Expect some interfaces to change and additional functionality which better defines libtrust's purpose apart from a set of primitives and helper functions.

thanks for the info


feat: add support to a few more specific StorageErrors for the Write API

OFFSET_OUT_OF_RANGE
OFFSET_ALREADY_EXISTS
STREAM_NOT_FOUND
Towards b/220198094

Converting this to draft as we realized that there are backend changes needed (https://b.corp.google.com/issues/220198094#comment7) before proceeding.

The exception backend change is fully rolled out.


Viscose

I will close the issue as not actionable. Please add a meaningful description and title and I will re-open the issue.


Property "$strapi" was accessed during render but is not defined on instance / 'entities' does not exist in type 'StrapiOptions'.

Version
@nuxtjs/strapi: 0.3.4
nuxt: latest
IDE: PhpStorm
Reproduction/Steps to reproduce
completely empty and new nuxt3 project
What is actually happening?'
Hey, as soon as I want to set up a new nuxt3 project with strapi I get the following error:
TS2345: Argument of type '{ buildModules: string[]; strapi: { url: string; }; }' is not assignable to parameter of type 'NuxtConfig'.   Object literal may only specify known properties, and 'strapi' does not exist in type 'NuxtConfig'.
I actually did it the same way as in the "example", except that I specified "'@nuxtjs/strapi'" instead of "module", as it also says in the doc.
nuxt.config.ts

Could fix the IDE error with this:
`import type { StrapiOptions } from '@nuxtjs/strapi';
declare module '@nuxt/schema' {
interface NuxtConfig {
strapi?: StrapiOptions;
}
interface NuxtOptions {
strapi?: StrapiOptions;
}
}`
But the startup error remains:

Hi Jannik
You need to use the edge channel version of the @nuxtjs/strapi package at the moment.
Version 0.3.4 is not compatible with Nuxt3.

Hi Jannik
You need to use the edge channel version of the @nuxtjs/strapi package at the moment. Version 0.3.4 is not compatible with Nuxt3.
https://github.com/nuxt-community/strapi-module/blob/dev/docs/pages/2.setup.md#edge-channel

Nice, the errors are all gone so far, however I don't know what else it needs to recognize $strapi now:

I have now added ConfigSchema in my nuxt-schmea-shim.d.ts, where now comes the following error:
Also, entities is not recognized. I will probably switch to the native strapi-sdk for now.

In Nuxt3 there is no $strapi.
You can access the methods trough composables which are explained here https://github.com/nuxt-community/strapi-module/blob/dev/docs/pages/3.usage.md
The methods are either in useStrapiAuth() or in useStrapi{3|4}(), depending on the Strapi version you are using.

In Nuxt3 there is no $strapi.
You can access the methods trough composables which are explained here https://github.com/nuxt-community/strapi-module/blob/dev/docs/pages/3.usage.md
The methods are either in useStrapiAuth() or in useStrapi{3|4}(), depending on the Strapi version you are using. All the strapi module composables are automatically imported.
Regarding the config:
The edge package should be in the package.json devDependencies as such: "@nuxtjs/strapi": "npm:@nuxtjs/strapi-edge@latest"
The module then needs to be in the buildModules section in nuxt.config.ts buildModules: ['@nuxtjs/strapi']
These are the default options:
  strapi: {
    url: process.env.STRAPI_URL || 'http://localhost:1337',
    prefix: '/api',
    version: 'v4',
  },

If the rest of your Nuxt3 setup is correct then the strapi module will work.

he also does not find the method

In Nuxt3 there is no $strapi.
You can access the methods trough composables which are explained here https://github.com/nuxt-community/strapi-module/blob/dev/docs/pages/3.usage.md
The methods are either in useStrapiAuth() or in useStrapi{3|4}(), depending on the Strapi version you are using. All the strapi module composables are automatically imported.
Regarding the config:
The edge package should be in the package.json devDependencies as such: "@nuxtjs/strapi": "npm:@nuxtjs/strapi-edge@latest"
The module then needs to be in the buildModules section in nuxt.config.ts buildModules: ['@nuxtjs/strapi']
These are the default options:
  strapi: {
    url: process.env.STRAPI_URL || 'http://localhost:1337',
    prefix: '/api',
    version: 'v4',
  },

If the rest of your Nuxt3 setup is correct then the strapi module will work.

he also does not find the method

oh this is a bug from my ide, got it fixed. Thanks for everything :)


*: promote db size metric to "'etcd" namespace

etcd_debugging_mvcc_db_total_size_in_bytes will still be kept for backward compatibilities.
etcd_debugging_mvcc_db_total_size_in_use_in_bytes was never released, so just renaming it to etcd_mvcc_db_total_size_in_use_in_bytes.
ref. https://github.com/coreos/etcd/issues/9438

lgtm


Redirect /vertaisohjatut campaign URL

LIIKUNTA-683.
Also fix a type issue that came up when a build was called.

TestCafe result is success for https://liikunta-pr743.dev.hel.ninja :laughing::tada::tada::tada:


fix url:  //xx.comok

//xx.com is a url

There is a better repo to use: https://github.com/patrykcieszkowski/node-bbcode


Update Plugin Artifacts Links for v0.136.6

Automated changes by create-pull-request GitHub action

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add support for revision-delete log actions

We already show various log actions (block, page deletion etc.). It'd be nice to also add a subscription for revision deletion and other visibility changes.
Sample:

Regular page deletion (already handled):
12:46 rc-pmtpa: [[Special:Log/delete]] delete * Krinkle *  deleted "[[MediaWiki:ArquivarPEs.js]]": Test

Revision deletion / visibility change (not yet handled):
12:46 rc-pmtpa: [[Special:Log/delete]] revision * Krinkle *  Krinkle changed visibility of a revision on page [[Main Page]]: content hidden and edit summary hidden

Code:

/src/CVNBot/RCReader.cs#L344-L347

We'll need to figure a way to parse the log summary from the localisation messages so that #cvn-sw, for example, shows all changes in the same language (e.g. English).
We'll also want inclusion of this event to be configurable as #cvn-sw might not actually want to include this in order to reduce noise.

Originally requested by Moira2 (#cvn-wp-nl / #wikipedia-nl).

The question is why. I have no idea why this would be useful to patrollers. It's never come up and the only reason I suggested it is because it showed up in logs as unhandled event. Let's decline this for now.


(feature) Redirect unauthorised users to static page

We now have a static page for unauthorised users, we should redirect to that when the user doesn’t have the correct permissions.

 Hiring staff who aren't authorised shouldn't get stuck


[Feature] Add option tags and parse state

Basically, it would be nice to have a feature that lets us attach tags to something, similarly to how the -x option works in Clang:
tag<"-x", "Set the file type", std::string>,
positional<"files", "The files to compile", tagged<std::string, "-x">,

Example:
foo -x t1 bar baz -x t2 quux foobar

Content of "files":
{"foo", ""},
{"bar", "t1"},
{"baz", "t1"},
{"quux", "t2"},
{"foobar", "t2"},

Better idea: have an option type that can be specified multiple times, but only the last one counts, and a ref<> option type that takes the current value (or an empty optional if unset) of another option at parse time.

ref<> was implemented a few weeks back


Release/v0.18.2106 including fixes for AutoSubstitution

This PR contains the changes in
https://github.com/microsoft/qsharp-runtime/pull/743
https://github.com/microsoft/qsharp-runtime/pull/742
as well as some edits to make it all work on top of it (fixing https://github.com/microsoft/qsharp-runtime/issues/741)

/azp run


How to use identity server with asp.net

How to use your identity server with asp.net. I already have my project and I want to know how to implement your identity server project on my asp.net core web application. Kindly briefly explain how to do that. I already saw readme but it cant understandable.
Thanks,
Waiting for your replay...

Did you try use dot net new template? This operation generates whole project under solution. You can move this projects under your solution which is already exist.

Did you try use dot net new template? This operation generates whole project under solution. You can move this projects under your solution which is already exist.
Hi sir,
I am a beginner. I don't know much about Docker and Asp.net. With dot net new template command I got the whole project. But I don't know which file I need to include in my solution. I am having asp.net core web application project on my computer. I want to use your Identity Server for my project. Kindly explain more clearly with my requirements. This would be used for everyone who needs this requirement. Thanks in advance. Waiting for your reply....

Here are some materials from the IdentityServer4 Documentation:

User authentication: http://docs.identityserver.io/en/stable/topics/signin.html
Api protection: http://docs.identityserver.io/en/stable/topics/apis.html

The only one thing you have to care about is changing the URL of the Authority property to your STS server. Besides, to take advantage of this project, you have to install the dot net core project template via:
dotnet new -i Skoruba.IdentityServer4.Admin.Templates::1.0.0-rc1-update2

Afterward, create a new skoruba.is4admin project with this command:
dotnet new skoruba.is4admin --name MyProject --title MyProject --adminemail<EMAIL_ADDRESS>--adminpassword "Pa$$word123" --adminrole MyRole --adminclientid MyClientId --adminclientsecret MyClientSecret --dockersupport true

While the project is created successfully, you can open Visual Studio to compile it. There will be three C# projects at least in the Identity server admin solution. (If you're using the last build of this project, you will get 13 C# projects in the solution project in total). The step to run the project:

Modify ConnectionStrings in the appsettings.json of these C# projects.

Skoruba.IdentityServer4.Admin
Skoruba.IdentityServer4.Admin
Skoruba.IdentityServer4.STS.Identity

Open your command line prompt, and chroot to Skoruba.IdentityServer4.Admin and type dotnet run /seed to seed database

Compile the Identity server admin solution in Visual Studio

Mouse right-click on these C# projects in sequence, then left-click on Debug > Start a new instance:

Skoruba.IdentityServer4.STS.Identity
Skoruba.IdentityServer4.Admin
Skoruba.IdentityServer4.Admin.Api

ref: https://github.com/skoruba/IdentityServer4.Admin#installation-via-dotnet-new-template

Open your web browser, type http://localhost:9000, and press enter. You will see a login page of the identity server.

Type the admin password you assigned while creating Identity server admin project with the dot net template command, then the admin website will say hi to you!

Hope it helps!

Thank you. It worked for me. And one more doubt, can I add custom field in the role and how to get custom field values.

Thank you. It worked for me. And one more doubt, can I add custom field in the role and how to get custom field values.

You should use Role claims.


Refactored 21 lines occurring 3 times in process.go

Greetings,
I've refactored 21 lines occurring 3 times in process.go.
This is my first ever commit and PR about something in Go, and I must admit, I've never written a single line of a Go code before. If something is horribly wrong, then I'm so sorry.
Thanks

@utkarshmani1997 Hi, I've signed the commit and pushed it again. Thanks.


Can't logout

(See gif)

Nothing shows up in console.

The account settings link doesn't seem to be working for me either.

This was on Chrome.  I'm still testing a little.

try https://user.patricbrc.org/logout

This is fixed and available on production now. Safari has a little bit different issue, but it is tracked by another ticket. So, I am closing this one.


Style/TrailingCommaInArguments shouldn't care about heterogenous args

With this config:
Style/TrailingCommaInArguments:
  EnforcedStyleForMultiline: comma

We feel that both of these should be acceptable:
foo(
  a, b,
  c
)

and
foo(
  a, b,
  c,
)

But this is not even valid ruby syntax.

@faucct fixed

@ptarjan  @faucct @bbatsov  Seems like this issue has been fixed?
I couldn't reproduce it with current rubocop version:
rubocop -V
0.49.1 (using Parser <IP_ADDRESS>, running on ruby 2.3.0 x86_64-darwin16)

Should we close this issue?

@smakagon: Looks like I can still reproduce this using the second example, and the configuration provided:
# offense.rb
foo(
  a, b,
  c,
)

# .rubocop.yml
Style/TrailingCommaInArguments:
  EnforcedStyleForMultiline: comma

Offenses:

offense.rb:3:4: C: Style/TrailingCommaInArguments: Avoid comma after the last parameter of a method call, unless each item is on its own line.
  c,
   ^

@Drenmi thanks, good point. Yes, the second example is still reproducible.
I wanted to go through existing issues and clean those a little bit. Because I'm sure we could reduce number of open issues.

I wanted to go through existing issues and clean those a little bit. Because I'm sure we could reduce number of open issues.

Yes, and there are a lot of important additions and and low hanging fruit buried in the issues. 😊

@ptarjan seems like there is a config option called consistent_comma which covers exact your case:
# good if EnforcedStyleForMultiline is consistent_comma
method(
  1, 2,
  3,
)

# good if EnforcedStyleForMultiline is comma or consistent_comma
method(
  1,
  2,
)

Let me know if that helps so we can close the issue.

If I remember correctly consistent_comma fails in other ways. Does it pass
both of my examples?
On Sun, Jul 2, 2017 at 11:22 PM Sergii Makagon<EMAIL_ADDRESS>wrote:

@ptarjan https://github.com/ptarjan seems like there is a config option
called consistent_comma which covers exact your case:
good if EnforcedStyleForMultiline is consistent_comma
method(
1, 2,
3,
)
good if EnforcedStyleForMultiline is comma or consistent_comma
method(
1,
2,
)
Let me know if that helps so we can close the issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bbatsov/rubocop/issues/2847#issuecomment-312494720,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACcz6Yay8pSjmRH-FfGIuP398BPlWW8ks5sJ6eegaJpZM4Hauh4
.

Yes, with consistent_comma it would require you to to add comma at the end of last argument for this example:
foo(
  a, b,
  c
)

But it makes sense since it says EnforcedStyleForMultiline, so comma for multiline arguments is enforced. If you don't need it, you can use it with no_comma argument.

I think the general goal I had with this issue (sorry it has been a while
since I opened it) is that I'd like to enforce trailing commas when every
arg is on its own line, but once people start mixing single arg and multi
arg lines then I don't want to enforce it.
This condition comes up often with functions that take some positional args
and then an optional arg hash. Usually people put the positional args all
on one line and then the hash with each key and value on their own line. In
that case we don't want to force the trailing comma since the closing paren
will hug the ending and a comma just gets in the way.
On Mon, Jul 3, 2017 at 10:13 AM Sergii Makagon<EMAIL_ADDRESS>wrote:

Yes, with consistent_comma it would require you to to add comma at the
end of last argument for this example:
foo(
a, b,
c
)
But it makes sense since it says EnforcedStyleForMultiline, so comma for
multiline arguments is enforced. If you don't need it, you can use it with
no_comma argument.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bbatsov/rubocop/issues/2847#issuecomment-312528953,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACcz2ySEa9s866_h_fHueYI_ULTNNkLks5sKEBBgaJpZM4Hauh4
.

There hasn't been much activity on this ticket and our Core Team is spread too thin on so many tasks, so I'll just close it for the sake of having a cleaner lists of tasks to focus on. We'd gladly review a PR, but it's unlikely that'd we're going to tackle this ourselves in the foreseeable future.


Cant see TeamDrive content?

Cant seem to find/select or view TeamDrive or SharedDrive folders :/

duplicate of #10


addUnique not working with object value

Hi
I can't make my cloud function working with addUnique:
myVal = {"a":"A","b":"B"};
myClass.addUnique("myArrayfield", myVal);
It gives me bad request response.
It only works if myVal is a string but I want to save a JSON object. Furthermore, if I try to stringify, it adds symbols in my expression.

was it working with parse.com?

Yes it was working before migration

I'm having this issue as well.  The error I'm getting is {"code":107,"message":"bad atom: [object Object]"}


Cosmetics: Refactor hightlight and overriden typos

Brief description
Fix code typos.
Note that this includes changes to variable names and actual styling names and thus is more involved than just some typos being fixed in code comments.
I'm also making this a separate PR so we can discuss and it's clearer that we are debating whether it's worth refactoring things like this in the code base.
Testing notes
⚠ These code changes should still be tested. ⚠

I've committed your requested change. Thanks @iLLiCiTiT
FYI, I haven't tested the code.


Color_guess

🎮 Game Request
Game logic and basic description
The game logic for "Color Guess" is as follows:
The game presents the player with a set of color options displayed as buttons.
One of the colors is randomly chosen as the target color.
The RGB values of the target color are displayed at the top.
The player needs to guess the correct color by clicking on one of the color buttons.
If the player selects the correct color, a success message is displayed.
If the player selects the wrong color, a try again message is displayed.
The player can click the "New Colors" button to reset the game and generate a new set of colors.
Point down the features
Game points
Here are the features of the "Color Guess" game:
Random Color Generation: The game generates a random target color for the player to guess. The RGB values of the target color are displayed at the top.
Color Buttons: The game presents the player with a set of color options displayed as buttons. The number of color options can be customized.
Guessing the Correct Color: The player needs to click on one of the color buttons to guess the correct color. If the selected color matches the target color, the player wins the game.
Play Again: After the player wins or loses the game, they can click the "Play Again" button to reset the game and generate a new set of colors to guess.
Responsive Design: The game interface can be designed to be responsive, allowing more challenging as the player needs to identify the correct color among a larger range of options.
Responsive Design: The game interface can be designed to be responsive, allowing it to adapt to different screen sizes and devices for an optimal playing experience.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @prachisingh1008! 🙂
It seems like you are not following proper guidelines !! 👀
Read documentation properly !!🙏
If you have any queries reach out to us on Discord🕹 .

Hey @prachisingh1008 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

assign it to me


Penzai as a training framework

Hello, thank you for a great framework!
I am currently considering penzai for building model trainer, as an alternative to frameworks like Flax. Would be there any possible limitations for penzai for this purpose? For example, using NamedArray would incur zero overheads? I think they are, but I want to be sure before proceeding with development.
Thank you!

Glad you like Penzai! As long as you run your code under jax.jit, I don't think there will be any overhead to using Penzai relative to frameworks like Flax.
(That said, Penzai's neural network standard library is pretty small right now, and focused on readability. So it may not have the same optimizations that some other frameworks support out of the box.)
If you do run into any issues with training models using Penzai, please let us know!


Prepare for versioning of the docs

I want to make sure these items are addressed before splitting the 2.5 docs from the other docs. https://rancher.atlassian.net/wiki/spaces/EN/pages/711393348/2.5+Documentation+Updates+excluding+feature+docs

Need to also raise issue on rancherlabs/website repo about adding a dropdown menu to allow a user to select a product version when reading the docs.


Update ResponsiveDrawer.js

Should provide theme props in useStyles.

[x] I have followed (at least) the PR section of the contributing guide.

useStyles doesn't need to be called with the theme. It gets injected via context.

@eps1lon Thanks for the quick review! Could you explain this then when using typescript?

Our closed issues have a similar case. You're probably using strictNullChecks: false. If not please open a new issue and fill out the template.


feat(config): add declareComponent option

I suggest to introduce a declareComponent option to the SpectatorOptions, usecase would be if the component i want to test is already declared in a module together with it's dependecies. This benefits the reusability of already existing modules and simplifies setting up tests for components. Example:
@NgModule({
  declarations:[TheComponent, SubComponent],
  exports:[TheComponent],
  imports: [SomeModule, AnotherModule]
})
export class TheComponentModule {}

With declareComponent option:
const createHost = createHostComponentFactory({
    component: TheComponent,
    imports: [TheComponentModule],
    declareComponent: false
});

Without declareComponent option:
const createHost = createHostComponentFactory({
    component: TheComponent,
    declarations:[SubComponent],
    imports: [SomeModule, AnotherModule]
});

You mean if you want to test the component as an integration test? Than it make sense. I know this feature from the angular playground and there it saves really a lot of time!!! So I would like to see this improvement in spectator!!

Thanks, please add dummy tests (with host and without a host) that test that it works as expected.


Is it possible to support old version of UI5

Some projects are running version 1.38 of UI5 which will be supported for a long time (up to 2027 according to version overview.
However, it seems that it does not work with WDI5 (probably because of the missing OPA helpers).
Is there a strategy to handle old versions of UI5 ?
If not, is the minimum version documented ?
What are the alternatives ?

Interested in the same question!

Hi,
for identifying the UI5 Controls we use the Record Replay API which is only available since 1.60. Below that, there should actually be an error in the terminal that the UI5 version is to low. I also had a quick look in the documentation and it seems like we are missing this prerequisite. Thanks for pointing that out!
Unfortunately I can not give you an answer to the rest of your questions. Maybe @vobu or someone else can help you here.

for UI5 < 1.60, we'd have to come up with a different client-side mechanism for retrieving a UI5 control and proxying it from browser- to Node-scope. Certainly doable, but quite an effort. As the separation of concern is clear here ("support UI5 < 1.60"), I see this very well suited for an external contribution. Anyone jumping to the occasion? 😄

started an exemplary (albeit statistically probably invalid 😝) poll: https://twitter.com/wdi5/status/1552199429364617217?s=21&t=3CAvEgHO0ZGjivVzMI5o-Q

Could we bring the missing code from a higher version of UI5 to version 1.38, what would it means from a licensing point of view ? Should we ask UI5 to add it ?


Add support for different Storage Backend during local development

Is your feature request related to a problem? Please describe.
I would like to use a S3 Compatible Storage Backend during local development and configure it using config.toml.
Describe the solution you'd like
I would like to be able to specify the following env variables to the storage api server:

STORAGE_BACKEND=s3

#######################################
# S3 Backend
#######################################
STORAGE_S3_BUCKET=supa-storage-bucket
STORAGE_S3_MAX_SOCKETS=200
STORAGE_S3_ENDPOINT=http://<IP_ADDRESS>:9230
STORAGE_S3_FORCE_PATH_STYLE=true
STORAGE_S3_REGION=local

# unsure if these are right but don't think connection is being made to minio anyway
AWS_ACCESS_KEY_ID=minioadmin
AWS_SECRET_ACCESS_KEY=minioadmin

Though, separate I wonder if it possible to have a more general API to pass/pipe in whatever environment variables are specified in the config.toml for the particular service so it is easier to try out individual feature changes without forking the CLI.
Describe alternatives you've considered
My original problem is the file storage backend is not performant for range requests on large files please see my original discussion in the storage repo (https://github.com/supabase/storage/discussions/540).

I managed to connect the minIO docker instance by adding environment variables field to the storage struct.
// pkg/config/config.io
storage struct {
...
EnvironmentVariables map[string]string    `toml:"env_environment_variables,omitempty"`
}

and then modified start.go so the environment variables are passed to the container
for key, value := range utils.Config.Storage.EnvironmentVariables {
   envVars = append(envVars, fmt.Sprintf("%s=%s", key, value))
}

happy to put in a pull request along these lines, and would this approach be worth extending for other services ?


Adding a back button for the sidebar and more

Title and Issue number

Title :Adding a back button for the sidebar and more and adding more info for the detail section in the company section
Issue No. : #744
Code Stack : HTNL, CSS, JS
Close #744

Video (mandatory)

This is the website before changes
https://github.com/apu52/METAVERSE/assets/144688422/5733cfab-b708-447b-853d-0dfd86244906
This is the website after changes to the website
https://github.com/apu52/METAVERSE/assets/144688422/d91000b4-4fc3-4dc9-8f7a-753a422e1396
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md
[X] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?

I am contributing under GSSoC 2024.

That back button will only work if the hamburger is required to open the sidebar or else it will be static.

That back button will only work if the hamburger is required to open the sidebar or else it will be static.

okk


Fix push command when looking up for the branch

If running the push command against a repository where no asset were uploaded yet (hence no branch created) and the local filesystem scan resulted in finding no asset then the command failed since no branch was ever created and the delete portion relied on it
fix #372

This is exactly what I was doing! I started Mojito webapp, created repo and pushed asset for the first time. Thank you for fixing it!


pull request for e2e test at 01/09/2017 22:26:14

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add hideSelectionFromResult property

Add a property that allows the user to hide or display the selected item(s) in the result list. This functionality can be used for both single and multi select boxes. It was tested with inline options, data source, array data and tag array.
By default, the hideSelectionFromResult boolean property is undefined and leaves the expected behavior intact: the selected item from a single select box is visible inside the result list while the selected items from a multi select box are hidden from the result list. This default behavior can be overriden by setting the hideSelectionFromResult property to true or false.
Related issues:
#1267 - Select a tag multiple times
#1538 - Ability to hide currently selected value in dropdown

Does this still works on the latest version? I cant find that option.

Nevermind, I just saw it was reverted. Is there an alternative way to achieve the same?

This should work in the latest version and give the same effect.
.select2-results__option[aria-selected=true] {
  display: none;
}

@kevin-brown thank you :+1:

This doesn't fix everything (for me at least).
I seems like the hidden options are still being selected, so if I select the option "Bear", then type "B" in the search, the first option might seem as "Beetle" but it will not be selected by default, because "Bear" is selected even if not visible.


[terra-form-select] Add maxHeight prop to field components

Bug Report
maxHeight Property is missing in SingleSelectField, MultiSelectField, SearchSelectField, TagSelectField
Description
Max height  is available as property in all forms of select components but not available in components that are in combination with field like SingleSelectField, MultiSelectField, SearchSelectField, TagSelectField
Possible Solution
Add maxHeight to props of above mentioned components similar to how it is supported in multiSelect component.

@saigorantla maxHeight can be added to the field components by using the selectAttrs prop. Any attributes spread through this property will be applied to the Select.

I can help with this


Add API to return list of tags from a repo

Add a new route that takes a repo as a path/query (tbd) parameter and returns the list of tags. This can precede 'analyze repo' action on the client to give the end user visibility into the tags that will be added to anchore-engine for analysis. The response can also be used by the client to selectively add tags to anchore-engine instead of analyzing the entire repo which could come for large repos with only a small subset of interesting tags

Closed by cae59df


Mapping Error in BasicAer

'OPENQASM 2.0;\ninclude "qelib1.inc";\nqreg q0[5];\ncreg c0[3];\nx q0[4];\nmeasure q0[1] -> c0[0];\nmeasure q0[3] -> c0[1];\nmeasure q0[4] -> c0[2];\n'
The above qasm should give all shots in 100, but they are all in 000. Only happens in BasicAer, not in Aer.
Informations

Qiskit Terra version: 0.7
Python version: 3.6
Operating system:

What is the current behavior?
Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

I confirm there is a bug
qr = QuantumRegister(5)
cr = ClassicalRegister(3)
circuit = QuantumCircuit(qr, cr)
circuit.x(qr[4])
circuit.measure(qr[1], cr[0])
circuit.measure(qr[3], cr[1])
circuit.measure(qr[4], cr[2])

backend = BasicAer.get_backend('qasm_simulator')
job = execute(circuit, backend)
result = job.result()
counts1 = result.get_counts()
print(counts1)

gives the outcome david is saying.

@chriseclectic can you have a look at this.

The bug is in the BasicAer python simulator. Specifically it is occurring in the _add_sample_measure function, which is responsible for finding a probability distribution from the statevector and sampling from that. This function cannot handle the case where only a subset of the total qubits are measured.


Please help to solve this issue

I am getting this error
[INFO DRT-0195] Start 64th optimization iteration.
    Completing 10% with 46 violations.
    elapsed time = 00:00:00, memory = 3713.43 (MB).
    Completing 20% with 46 violations.
    elapsed time = 00:00:00, memory = 3713.43 (MB).
    Completing 30% with 46 violations.
    elapsed time = 00:00:00, memory = 3713.43 (MB).
    Completing 40% with 46 violations.
    elapsed time = 00:00:00, memory = 3713.43 (MB).
    Completing 50% with 46 violations.
    elapsed time = 00:00:00, memory = 3713.43 (MB).
    Completing 60% with 44 violations.
    elapsed time = 00:00:01, memory = 3713.43 (MB).
    Completing 70% with 44 violations.
    elapsed time = 00:00:01, memory = 3713.43 (MB).
    Completing 80% with 44 violations.
    elapsed time = 00:05:11, memory = 3713.43 (MB).
    Completing 90% with 44 violations.
    elapsed time = 00:05:11, memory = 3713.43 (MB).
    Completing 100% with 44 violations.
    elapsed time = 00:05:42, memory = 3713.43 (MB).
[INFO DRT-0199]   Number of violations = 44.
[INFO DRT-0267] cpu time = 00:05:42, elapsed time = 00:05:42, memory = 3713.43 (MB), peak = 3834.52 (MB)
Total wire length = 4865255 um.
Total wire length on LAYER li1 = 11643 um.
Total wire length on LAYER met1 = 1992831 um.
Total wire length on LAYER met2 = 2235038 um.
Total wire length on LAYER met3 = 524288 um.
Total wire length on LAYER met4 = 87389 um.
Total wire length on LAYER met5 = 14064 um.
Total number of vias = 1030743.
Up-via summary (total 1030743):.

--------------------------
 FR_MASTERSLICE          0
            li1     502701
           met1     490342
           met2      31526
           met3       5975
           met4        199
--------------------------
                   1030743

[INFO DRT-0198] Complete detail routing.
Total wire length = 4865255 um.
Total wire length on LAYER li1 = 11643 um.
Total wire length on LAYER met1 = 1992831 um.
Total wire length on LAYER met2 = 2235038 um.
Total wire length on LAYER met3 = 524288 um.
Total wire length on LAYER met4 = 87389 um.
Total wire length on LAYER met5 = 14064 um.
Total number of vias = 1030743.
Up-via summary (total 1030743):.

--------------------------
 FR_MASTERSLICE          0
            li1     502701
           met1     490342
           met2      31526
           met3       5975
           met4        199
--------------------------
                   1030743

[INFO DRT-0267] cpu time = 07:14:00, elapsed time = 04:48:39, memory = 3713.43 (MB), peak = 3834.52 (MB)

[INFO DRT-0180] Post processing.
Saving to /openLANE_flow/designs/radix4_mdf/runs/18-11_17-56/results/routing/23-radix4_mdf.def
[ERROR]: There are violations in the design after detailed routing.
[ERROR]: Total Number of violations is 44
[INFO]: Calculating Runtime From the Start...
[INFO]: flow failed for radix4_mdf/18-11_17-56 in 5h7m8s
[INFO]: Generating Final Summary Report...
[INFO]: Design Name: radix4_mdf
Run Directory: /openLANE_flow/designs/radix4_mdf/runs/18-11_17-56
Source not found.
----------------------------------------

LVS Summary:
Source: /openLANE_flow/designs/radix4_mdf/runs/18-11_17-56/results/lvs/radix4_mdf.lvs_parsed.gds.log
Source not found.
----------------------------------------

Antenna Summary:
No antenna report found.
[INFO]: check full report here: /openLANE_flow/designs/radix4_mdf/runs/18-11_17-56/reports/final_summary_report.csv
[INFO]: Saving Runtime Environment
[ERROR]: Flow Failed.

This is my config file
# User config
set ::env(DESIGN_NAME) radix4_mdf

# Change if needed
set ::env(VERILOG_FILES) [glob $::env(DESIGN_DIR)/src/*.v]

# Fill this
#set ::env(CLOCK_NET) " "

set ::env(DESIGN_IS_CORE) "0"

set ::env(CLOCK_PERIOD) "30.0"
set ::env(CLOCK_PORT) "clk"

set ::env(DIODE_INSERTION_STRATEGY) "4"
set ::env(FP_CORE_UTIL) "30"
set ::env(CELL_PAD) "2"
set ::env(PL_BASIC_PLACEMENT) "0"
set ::env(DIODE_PADDING) "0"
set ::env(DIODE_INSERTION_STRATEGY) "4"

set filename $::env(DESIGN_DIR)/$::env(PDK)_$::env(STD_CELL_LIBRARY)_config.tcl
if { [file exists $filename] == 1} {
	source $filename
}

Without a test case not much can be said.

@maliberty
Which test case I was missing.?

How can this problem be reproduced?  The log file is insufficient.

@maliberty
Could you please tell me which test cases in need to add sir.?
Are these ..?
set ::env(DIE_AREA) "0.0 0.0 6937.49 6948.21"
set ::env(CORE_AREA) "5.52 10.88 6931.70 6935.04"

Or some other I need to add..?

You can try increasing the die & core area yourself or follow https://github.com/The-OpenROAD-Project/OpenLane/blob/master/docs/source/for_developers/using_or_issue.md to generate a test case

@sumanthnimmakayala
Read and fill the issue template properly with all details and open the issue again.
Its important to know which OpenLane version currently you're working.


Unable to update new clients

Issue Description:
When I install steam on a new computer and run the first update I get an error
"Steam needs to be online to update.  Please confirm your network connection and try again"
When I switch DNS servers to my upsteamdns server it downloads fine and finishes updating.
Docker Run Command:
docker run --name lancache-dns --detach -p <IP_ADDRESS>:53:53/udp -e STEAMCACHE_IP=<IP_ADDRESS> -e UPSTREAM_DNS=<IP_ADDRESS> lancachenet/lancache-dns:latest

Docker Container Output:
This is the last entry for that machine
see the 302 error like a redirect

[03/Sep/2019:16:34:11 +0100] "GET /client/steam_win32.zip.vz.045e3bdc708594750f8858698fa37ba56f23ee19_1207028 HTTP/1.1" 302 0 "-" "Valve/Steam HTTP Client 1.0" "MISS" "client-download.steampowered.com" "-"

I am affected aswell from this problem first came up about 5 Months ago while trying to start a freshly installed steamgame, because steam nagged about an needed steam update which it did not get upon steam restart, until i disabled DNS Redirection to steamcache.
Problem could be that the requested source is not  located on the normal Donwload services of steam but on its own server which gets promoted via the 302 redirect. best would to be to disable the caching of client-download*.steampowered.com, as this cannot be done from docker config side

302 isn't an error, it's just a redirect response code? I've not heard any other issues with cached updates. I suspect that you may have a corrupted file in your cache somewhere. Are there any other log entries for steam_win32.zip?


Feature docker

Add github action such as mega-linter and pushing docker image to registry

mega-linter

Wow, looks good, thank you!


[bugfix]  there is an duplicate refresh task after creating new mater…

…ialized view. #8651
[bugfix]  there is an duplicate refresh task after creating new materialized view. #8651
What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #8651
Problem Summary(Required) ：

When taskType is PERIODICAL, task will run once created successfully.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zengqingdong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@ABingHuang PTAL


runtime: apparent deadlock in image/gif test on linux-ppc64-buildlet

There was a timeout in the image/gif test, but from the symptoms it looks more like a runtime bug to me: one of the threads is idle on runtime.futex via runtime.mcall, and the the other one says goroutine running on other thread; stack unavailable.
That combination of symptoms is similar to #32327, although the path from runtime.mcall to runtime.futex differs.
https://build.golang.org/log/e08f0037958f84cf1b1fe6b9f80c8208d332104c
SIGQUIT: quit
PC=0x6be3c m=0 sigcode=0

goroutine 0 [idle]:
runtime.futex(0x2ad150, 0x8000000002, 0x0, 0x0, 0x12000, 0x46d40, 0x46704, 0xc00035e780, 0x46d7c, 0xc0000384c8, ...)
	/tmp/workdir-host-linux-ppc64-osu/go/src/runtime/sys_linux_ppc64x.s:472 +0x1c
runtime.futexsleep(0x2ad150, 0x200046708, 0xffffffffffffffff)
	/tmp/workdir-host-linux-ppc64-osu/go/src/runtime/os_linux.go:44 +0x3c
runtime.lock(0x2ad150)
	/tmp/workdir-host-linux-ppc64-osu/go/src/runtime/lock_futex.go:102 +0x1bc
runtime.exitsyscall0(0xc000076180)
	/tmp/workdir-host-linux-ppc64-osu/go/src/runtime/proc.go:3119 +0x7c
runtime.mcall(0xc000076180)
	/tmp/workdir-host-linux-ppc64-osu/go/src/runtime/asm_ppc64x.s:202 +0x58

goroutine 1 [chan receive, 3 minutes]:
testing.(*T).Run(0xc0000acd00, 0x18dbfc, 0x1b, 0x193748, 0x100000000000349)
	/tmp/workdir-host-linux-ppc64-osu/go/src/testing/testing.go:961 +0x304
testing.runTests.func1(0xc0000ac000)
	/tmp/workdir-host-linux-ppc64-osu/go/src/testing/testing.go:1207 +0x78
testing.tRunner(0xc0000ac000, 0xc000058d48)
	/tmp/workdir-host-linux-ppc64-osu/go/src/testing/testing.go:909 +0xc8
testing.runTests(0xc00008c080, 0x2a7dc0, 0x18, 0x18, 0x0)
	/tmp/workdir-host-linux-ppc64-osu/go/src/testing/testing.go:1205 +0x27c
testing.(*M).Run(0xc0000a8000, 0x0)
	/tmp/workdir-host-linux-ppc64-osu/go/src/testing/testing.go:1122 +0x158
main.main()
	_testmain.go:96 +0x130

goroutine 30 [running]:
	goroutine running on other thread; stack unavailable
created by testing.(*T).Run
	/tmp/workdir-host-linux-ppc64-osu/go/src/testing/testing.go:960 +0x2e8

r0   0xdd	r1   0x3fffd047b228
r2   0x8000000000	r3   0x2ad150
r4   0x80	r5   0x2
r6   0x0	r7   0x0
r8   0x0	r9   0x0
r10  0x0	r11  0x0
r12  0x0	r13  0x0
r14  0x1a0b0	r15  0xc000030e78
r16  0x0	r17  0xc000025900
r18  0x0	r19  0x1b4782
r20  0xc000020010	r21  0x2ad840
r22  0x0	r23  0x0
r24  0x8	r25  0x3fff8b55a520
r26  0x3fff8b55a578	r27  0x73
r28  0x72	r29  0x1
r30  0x2ad2a0	r31  0x19bbc
pc   0x6be3c	ctr  0x0
link 0x3a62c	xer  0x0
ccr  0x54400002	trap 0xc00
*** Test killed with quit: ran too long (4m0s).
FAIL	image/gif	240.002s

CC @laboger @aclements @mknyszek @randall77

One more today (linux-ppc64-buildlet): https://build.golang.org/log/c6b2fbeb285314f08b608b6448f2e967415876cc
@dmitshur @toothrot: could you help with either a gomote token or distro information?

I was not aware the builder machines only had 2 processors each. I will try and see if that helps to reproduce the problem (ours have at least 16, some many more).
So that means the default value for the test parallelism should be 2, but I've seen failure logs where there are many more than 2 goroutine stacks running tests. I guess that should be OK but I did not expect that.

I have not been able to reproduce this one with GOMAXPROCS=2. It would help to know what is on the stack that is unavailable, is there any way to get that information?

It would help to know what is on the stack that is unavailable, is there any way to get that information?

@aclements, @ianlancetaylor: any tips on coaxing the runtime into providing more stacks?

You can probably get more stacks by running with GOTRACEBACK=crash.

I don't think we've seen this since the move to Docker with a more recent kernel.

Thanks. Closing on the theory that this was a kernel bug.


Bug Fix Needed

Please ensure version 3.1 is deployed as 3.0 has a bad cookie expiration bug that needs to be fixed.

@kenmckell - Tomorrow, I will copy this over to the repo on git.corp.adobe.com. The repo on github.com is a mirror but will get overwritten next time we make changes to the former.

D’oh!   Should have done this on the corp github.  Thanks! 😊
Ken McKell  |  Senior Consultant  |  Adobe Inc.  |  T<PHONE_NUMBER>  |  C<PHONE_NUMBER>  |<EMAIL_ADDRESS>|  Lehi, Utah (Mountain Time)
From: MicaPete @.>
Sent: Thursday, September 22, 2022 4:22 PM
To: AdobeDocs/analytics.en @.>
Cc: Ken McKell @.>; Mention @.>
Subject: Re: [AdobeDocs/analytics.en] Bug Fix Needed (PR #242)
EXTERNAL: Use caution when clicking on links or opening attachments.
@kenmckellhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkenmckell&data=05|01|kmckell%40adobe.com|20991d97449f48a73d2508da9ce8d9a2|fa7b1b5a7b34438794aed2c178decee1|0|0|637994821152902067|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=j%2BmwaUZ%2FuIflsfj5GxmfSvR3%2FmbNx6vPDa%2B4Nj94Ozc%3D&reserved=0 - Tomorrow, I will copy this over to the repo on git.corp.adobe.com. The repo on github.com is a mirror but will get overwritten next time we make changes to the former.
—
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAdobeDocs%2Fanalytics.en%2Fpull%2F242%23issuecomment-1255616157&data=05|01|kmckell%40adobe.com|20991d97449f48a73d2508da9ce8d9a2|fa7b1b5a7b34438794aed2c178decee1|0|0|637994821152902067|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=32jTP7N90diXJWBvpBbUtAgHeDW1akm6ZMKrG50vCCU%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM3AM24MWACOXTRZ5IY2I7TV7TLX7ANCNFSM6AAAAAAQTPIZUY&data=05|01|kmckell%40adobe.com|20991d97449f48a73d2508da9ce8d9a2|fa7b1b5a7b34438794aed2c178decee1|0|0|637994821152902067|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=nFOxSqiErpOezhQZ2r47b7Gr5qmkgfggsM6i5XooVLo%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@kenmckell
https://experienceleague.adobe.com/docs/analytics/implementation/vars/plugins/getvalonce.html

Thanks!! 😊
Ken McKell  |  Senior Consultant  |  Adobe Inc.  |  T<PHONE_NUMBER>  |  C<PHONE_NUMBER>  |<EMAIL_ADDRESS>|  Lehi, Utah (Mountain Time)
From: MicaPete @.>
Sent: Friday, September 23, 2022 4:15 PM
To: AdobeDocs/analytics.en @.>
Cc: Ken McKell @.>; Mention @.>
Subject: Re: [AdobeDocs/analytics.en] Bug Fix Needed (PR #242)
EXTERNAL: Use caution when clicking on links or opening attachments.
@kenmckellhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkenmckell&data=05|01|kmckell%40adobe.com|e9b16cca386f436bb84508da9db10c31|fa7b1b5a7b34438794aed2c178decee1|0|0|637995680983113660|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=hMD9P8lnP6EK%2F7MaVmd8iW7s0%2BwdTgvE58OMSVjPW1M%3D&reserved=0
https://experienceleague.adobe.com/docs/analytics/implementation/vars/plugins/getvalonce.htmlhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fexperienceleague.adobe.com%2Fdocs%2Fanalytics%2Fimplementation%2Fvars%2Fplugins%2Fgetvalonce.html&data=05|01|kmckell%40adobe.com|e9b16cca386f436bb84508da9db10c31|fa7b1b5a7b34438794aed2c178decee1|0|0|637995680983113660|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=SrtiO5qYtKfk5%2BPZTsZBLrFHVvtnHS30Y2PD506rABg%3D&reserved=0
—
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAdobeDocs%2Fanalytics.en%2Fpull%2F242%23issuecomment-1256726236&data=05|01|kmckell%40adobe.com|e9b16cca386f436bb84508da9db10c31|fa7b1b5a7b34438794aed2c178decee1|0|0|637995680983113660|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=LfIjIzcdaJbZ89NWPFveSzJzCbQt01DmGmOyNhAVqhE%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM3AM27E6FHCYS2DW5WMHKLV7YTWBANCNFSM6AAAAAAQTPIZUY&data=05|01|kmckell%40adobe.com|e9b16cca386f436bb84508da9db10c31|fa7b1b5a7b34438794aed2c178decee1|0|0|637995680983113660|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=kiezXjL4KDWSc8RkyOVoWk960SurYRocP%2FbLNfXbl8I%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


psgeo.js should be refactored as an object, not set of functions

Will be done when I find a suitable time.

I have an idea, maybe two:
Geolocation is an independent concept. Userinterface is another. Now, currently these are implemented as functions in random places (e.g. "update stats pane" is NOT the correct location for geolocation code). So, I wholeheartedly support this issue to be addressed.
May I suggest, that

we put geolocation code in geolocation.js and objectify this this stuff (considered also lib, but this is such a separate thing - more than a collection of helper functions)
we also move button creation and creation/update of info/stats panes into userinterface.js and objectify this stuff

Some work has been done - mainly moving settings (psgeoDomainDefaults and psgeoSources) into a settings object.
This required quite a lot of changes in many places (typically in the init* functions).
Geolocation has not yet been addressed.
Work continues.

There's a function calling tree now, with comments: structure.md
It's now perfect, but it does five some sort of an overview of the functions in psgeo.js


Automated cherry pick of #6321: Remove unexpected AltName after rename interface (#6321)

Cherry pick of #6321 on release-1.15.
#6321: Remove unexpected AltName after rename interface (#6321)
For details on the cherry pick process, see the cherry pick requests page.

/skip-all


Migrations is now specifying the db type in 1.1, whereas in 1.0.1 it didn't

I've upgraded my EF Core to the recent 1.1 release. My system uses different databases, including SQLite and SQL Server, so I'm using very generic code everywhere, and I've never had portability problems.
I have some entity with the following config:
builder.HasKey(b => b.Id);
builder.Property(b => b.Id).IsRequired().ValueGeneratedOnAdd();

I needed to regenerate my context. The 1.0.1 migration had this:
.Annotation("Autoincrement", true)

And the 1.1 migration suddenly generated this:
.Annotation("Sqlite:Autoincrement", true)

Does this mean that now the context can only run on SQLite?
That would be disappointing, as it is less functional than the old version. Maybe there's a config option buried somewhere that controls this behavior?

I believe it was a bug 1.01 where it didn't emit the type before

@denisz1 That annotation was always SQLite-specific; it just wasn't following the naming convention for provider-specific annotations in the previous release.
While the overall approach for migrations is to keep them as database provider-agnostic as possible it is still the case that when a migration is scaffolded it is done so for a specific database provider and may contain both model elements and annotations that are intended to work with only that provider. Generally annotations for a different provider are ignored, which means if two providers need different annotations, then you can have all annotations present. You will need to do some hand-editing for this to work. You can also add conditional code in the migration using the ActiveProvider property so that you can do different things on different providers. Again, you will have to hand-edit if you need to use this.

@ajcvickers Thanks for the clarification.
At some point it would be great if the docs mention this in the "advanced" section, or something like that.


bug: default.lazy = false but plugins with the "keys" option defined are still lazy loaded

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.8.0
Operating system/version
Red Hat 8.10
Describe the bug
I have defined defaults.lazy = false, but when defining keys for my plugins, they still get lazy loaded :
        {'lewis6991/gitsigns.nvim',
                opts = {},
                keys = {},
        },

If I remove the keys then they get loaded directly, as expected because of the lazy option being false.
Steps To Reproduce

Define defaults.lazy = false in the lazy config
Import a plugin and define the keys variable

Expected Behavior
When defaults.lazy = false, all plugins should be loaded when opening nvim
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    -- add any other plugins here
  },
})

this is completely expected
keys is something to lazyload plugins which obviously overrides the defaults


WIP DatePicker enhancements

Describe the changes you have made to improve this project

Add DatePickerHelper with new attached properties. This allows us to handle this button separately to another clear button.

DropDownButtonContent
DropDownButtonContentTemplate
DropDownButtonFontFamily
DropDownButtonFontSize

Use new DatePicker helper for DateTimePicker and TimePicker

Unit test
-/-
Closed Issues
Closes #3656

Hi @punker76 ,
Thinking further I think this Helper class could be used for ComboBox DropDownButton etc in the future. So maybe we should call it more general like DropDownHelper.
Happy coding
Tim


ARROW-13604 [Java]: Remove deprecation annotations for APIs representing unsupported operations

Some APIs representing unsupported operations should not be annotated deprecated, unless the overriden APIs are deprecated in the super classes/interfaces.
According to the discussion in https://github.com/apache/arrow/pull/10864#issuecomment-895707729, we open a separate issue for this.

Sorry, instead of removing the deprecated flag, it might be better to document why they are marked deprecated.

SGTM. Documents added. Thanks.
After more thoughts, I think some API should be deprecated completely (that is, the API in the interface and all implementations should be deprecated.)
This is because, the APIs no longer reflect the current design.
Do you agree?

+1 Thanks, I think this makes sense.  Lets wait one release and then we can delete the methods marked as being removed.
CC @laurentgo


Can't build 1709 Nano Server Images

Environment
VSTS

Agent - Hosted or Private:
Hosted

Issue Description
I'm trying to build a Windows Nano Server 1709 image, which fails because the underlying agent is not on 1709.
When will the hosted VSTS agents be updated so that we can build 1709 images?
Error logs
container 376e29b291aa290ebdff35b4eaa136595fc6d168a63bddc5ef0436955018aeaf encountered an error during CreateContainer: failure in a Windows system call: The operating system of the container does not match the operating system of the host. (0xc0370101) extra info: {"SystemType":"Container","Name":"376e29b291aa290ebdff35b4eaa136595fc6d168a63bddc5ef0436955018aeaf","Owner":"docker","VolumePath":"\\\\?\\Volume{8c532bb7-b8d6-11e7-a98e-000d3ad0bf62}","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\docker\\windowsfilter\\376e29b291aa290ebdff35b4eaa136595fc6d168a63bddc5ef0436955018aeaf","Layers":[{"ID":"edf18442-d0d5-5666-ad3b-f1da335d7ee1","Path":"C:\\ProgramData\\docker\\windowsfilter\\8176c946554686556e471bd8e61c9bcf66e2c1afe64b282c92311a5dda7d2a19"},{"ID":"ce3684a5-d7b9-5142-b4bc-850b4a528e47","Path":"C:\\ProgramData\\docker\\windowsfilter\\198b115847b18df970d90b8f853a2dd6fa28273ab2c7a2a7490761caf5eb9849"},{"ID":"60cfd27f-fb57-532a-a0f5-3a5d81c51ce7","Path":"C:\\ProgramData\\docker\\windowsfil...
C:\Program Files\Docker\docker.exe failed with return code: 1

The Hosted VS2017 image is primarily for running VS2017 builds. Since 1709 is a server core, we cannot install VS on it. So, there is no plan at this point to support another pool of VSTS agents with 1709. You should be able to set up a private agent on 1709.

This is also not an issue with one of the tasks in this repo (what these issues are tracking).

@bryanmacfarlane @chrisrpatterson what is the recommended way to build 1709 based images with VSTS CI pipeline then?


Don't show "Phone -" on 500 page if no location

Our root domain has no location set, so we don't have contact information to show users.
Right now, it will say Phone — but then not have a phone number.
Instead, we should omit the Contact output entirely if there is no contact info.
Screenshots

before
after

when there is a location ('vancouver' in the URL string), there is a phone number.
When there is no location, there is no phone number to call.

This PR removes the Phone — line in the second screenshot.

I know! This is a great case for them! 😢

Anyway, we can test on staging 😉

Works now!
https://rescheduler-dev.cds-snc.ca/500


etag package can not be found

Could not find package matching<EMAIL_ADDRESS>"etag": {
      "version": "1.8.1",
      "resolved": "https://registry.npmjs.org/etag/-/etag-1.8.1.tgz",
      "integrity": "sha1-Qa4u62XvpiJorr/qg6x9eSmbCIc=",
      "dev": true
    },

{
  "name": "prerender-test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "prerender": "^5.3.1"
  }
}

And also in another project:
Could not find package matching<EMAIL_ADDRESS>

Very odd. I'll work on this one first...

They definitely work from the website, which would seem to indicate it is an auditjs client side problem.

<EMAIL_ADDRESS><EMAIL_ADDRESS>

I was able to reproduce the ETag issue
[49/69] cookie-signature 1.0.6   No known vulnerabilities against package/version...
[50/69] encodeurl 1.0.2   No known vulnerabilities against package/version...
[51/69] escape-html 1.0.3   No known vulnerabilities against package/version...
Could not find package matching<EMAIL_ADDRESS>[52/69] finalhandler 1.1.1   No known vulnerabilities against package/version...
[53/69] parseurl 1.3.2   No known vulnerabilities against package/version...
[54/69] statuses 1.4.0   No known vulnerabilities against package/version...

I believe that it will, yes. There are a few issues throughout the various toolsets on how to handle mixed-case packages. NuGet, for example, is explicitly case sensitive, while others are explicitly case insensitive and still others do not specify. We are gradually learning the ins and outs of each system and adjusting accordingly.


-fno-finite-math-only for almost 2x speed up, fix for [#19]

final compilation opts on cpu, -fno-finite-math-only instead of -fno-fast-math, and add -march=native.
benchmarks comparisons: https://github.com/karpathy/llm.c/issues/19#issuecomment-2049099144
and now:
step 0: train loss 5.356086 (took 9611.016869 ms)
step 1: train loss 4.300644 (took 8780.770364 ms)
step 2: train loss 4.623083 (took 7137.313333 ms)
step 3: train loss 4.599365 (took 6426.557283 ms)
step 4: train loss 4.616659 (took 6864.495874 ms)
step 5: train loss 4.231428 (took 6635.326672 ms)
step 6: train loss 3.753164 (took 6516.244371 ms)
step 7: train loss 3.650456 (took 6362.145571 ms)
step 8: train loss 4.182243 (took 6333.873539 ms)
step 9: train loss 4.199581 (took 6407.929416 ms)

Great find! Even better if you keep -ffast-math for all except gelu_backward, see https://github.com/karpathy/llm.c/pull/168


Switch to pyproject.toml

See https://til.simonwillison.net/python/pyproject - also https://github.com/simonw/llm-plugin and https://github.com/simonw/sqlite-utils-plugin

This broke things: https://github.com/simonw/click-app-template-demo/actions/runs/6398127839/job/17367572440
============================= test session starts ==============================
platform linux -- Python 3.9.18, pytest-7.4.2, pluggy-1.3.0
rootdir: /home/runner/work/click-app-template-demo/click-app-template-demo
collected 1 item

tests/test_click_app_template_demo.py F                                  [100%]

=================================== FAILURES ===================================
_________________________________ test_version _________________________________

    def test_version():
        runner = CliRunner()
        with runner.isolated_filesystem():
            result = runner.invoke(cli, ["--version"])
>           assert result.exit_code == 0
E           assert 1 == 0
E            +  where 1 = <Result RuntimeError("'click_app_template_demo' is not installed. Try passing 'package_name' instead.")>.exit_code

tests/test_click_app_template_demo.py:9: AssertionError
=========================== short test summary info ============================
FAILED tests/test_click_app_template_demo.py::test_version - assert 1 == 0
 +  where 1 = <Result RuntimeError("'click_app_template_demo' is not installed. Try passing 'package_name' instead.")>.exit_code
============================== 1 failed in 0.04s ===============================

Relevant comment:

https://github.com/pallets/click/issues/1884#issuecomment-843693678

Actually no I think it's this: https://github.com/simonw/click-app/blob/3b87beb33b88e86244003d52513a20c54f9dae48/{{cookiecutter.hyphenated}}/pyproject.toml#L2

That fixed it - tests pass now for https://github.com/simonw/click-app-template-demo/commit/968887d83f43c8c14acaa649be5c93f408f7bd6e


Algolia Integration

Is your feature request related to a problem? Please describe.
integrate Algolia search functionalioty in the current docusaurus project
Describe the solution you'd like
Algolia should be enabled and visible on the top-right.
Something like this:

Describe alternatives you've considered
No response
Additional context
No response

I will take this, I have already determined the first steps to integrate algolia docsearch.
According to docusarus' search docs to use Algolia DocSearch we must apply to the DocSearch program here.
The checklist for applying says that we must already have the content before application as they will not validate our request otherwise.

@FrancescoXX the owner needs to apply to this program

yes I think this is on me

Is the Algolia integration something that will require extra configurations @FrancescoXX?

I sent  the request, only I can do this. work in progress, let's update in some weeks as they are usually slow

I sent the request, only I can do this. work in progress, let's update in some weeks as they are usually slow

Awesome @FrancescoXX. No problemo!

Is the Algolia integration something that will require extra configurations @FrancescoXX?

Well if we are accepted they will index our website for free. That's Francesco had to apply.
If you look at the checklist I sent above, they want a production ready website (usually a documentation or blog as they mentioned). I think we should've designed the landing page of freeweb3resources.com before applying. It still has some placeholders. I actually wanted to remove the placeholders and create at least a custom landing page but I never got to start it...

Is the Algolia integration something that will require extra configurations @FrancescoXX?

Well if we are accepted they will index our website for free. That's Francesco had to apply.
If you look at the checklist I sent above, they want a production ready website (usually a documentation or blog as they mentioned). I think we should've designed the landing page of freeweb3resources.com before applying. It still has some placeholders. I actually wanted to remove the placeholders and create at least a custom landing page but I never got to start it...

No problem Arda, all will be handled.

We're in this together.

How's this going @FrancescoXX?

@FrancescoXX??

Any updates on this @ardasevinc, @FrancescoXX??

Thanks for the response @ardasevinc!!

Any updates @FrancescoXX??

Can I close this @FrancescoXX?

why close it? it just needs time and I am working on the integration

It's done now, right @FrancescoXX.


feat/all-regulars-query

Please review before merging.

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

GitHub release
v3.12.0

Your semantic-release bot :package::rocket: