[suggestions] entities list and props

There was a discussion about map2prop. The ideas are the next:
1- be able to save a list of entities you can customize (for example, have a squadmaker that spawns a headcrab called A, and another spawning a garg called B). The list can be saved to a .txt and be accessed to quickly paste the selected entity in the map. This would help a lot when making map series where you have the same entity setups. Right now the only way to copy over is to save the .ent files of both maps, and manually copy over the desired entity text from one to the other. Or just remaking the entity from scratch in the second map. which is cumbersome
2- map2prop is a great tool, but model collision in this game is a pain. In the future it will have the ability to import the model with an automatically created collision clip hull of the size of the model. But this is for map editors so we cannot use it, although this is a great idea to suggest for bspguy:  Have a tool to automatically create an invisible func_wall brush cube of the size of the selected model, at the center of it, if that is even remotely possible

@EmmaCarro now entities can be copied/pasted with CTRL+C/CTRL+V between newbspguy windows


react-router-dom  not working

I have following implementation of "react-router-dom", but  I am not able to get it working. can someone guide me what's the underlying issue.
App.jsx
`
import React from "react";
import Main from "../components/Main";
import Home from "../components/Home";
import { BrowserRouter, Match, Miss, Link } from 'react-router-dom';

  const App = () => (

   <BrowserRouter>

            <Match exactly pattern="/" component={Main} />
            <Match pattern="/home" component={Home} />

    </BrowserRouter>
  );

export default App;

`
Index.jsx
import React from "react";
import ReactDOM from "react-dom";
import Main from "./components/Main";
import Home from "./components/Home";

import Page from './components/Page';
import App from "./config/App";

ReactDOM.render(
   <App/>,
    document.getElementById('app')
);

I get the following error :

I ran into this as well. I got it working by using Route instead of Match:
import React from "react";
import Main from "../components/Main";
import Home from "../components/Home";
import { BrowserRouter, Route, Link } from 'react-router-dom';

const App = () => (
    <BrowserRouter>

            <Route exact={true} path="/" component={Main} />
            <Route path="/home" component={Home} />

    </BrowserRouter>
);

export default App;

As @overthemike said, you should be using the <Route> component. <Match> and <Miss> were components from the alpha that were removed. <Route> and <Match> are essentially the same thing, but with slightly different prop names (exactly -> exact, pattern -> path).


UI needs work

Hey,
Love your work. I'm using BB to track my 3week old sons <dad joke>poo-gress</dad joke>. We were very into it during the first week but as we get less and less sleep we're finding the UI is a bit too fiddly (particularly the date/time entry).
I'm a frontender these days (was a Django man myself) and was thinking of redoing the forms to make them easier for tired parents who forget when/what the timer is on/for... you know what i mean.
I see you have a good API setup (have you looked into GraphQL yet?) so i might try and write a frontend app using that. Do some interactive D3.js charts.  Maybe even some DTW clustering (as feedings are a bit staccato for us).
Anyway, do you think its worth having the front & back in the same repo or should they be separate projects? I'm deploying to Heroku and  not sure how to combine a Django + Create React App (at work we keep them separate but that's a big project and parents would want the simplest deploy i guess?).
word
alex
p.s. these are big words as i might get an hour or two a day in while he's sleeping (if i'm not too sleep deprived myself :)
p.p.s If you have another plan for the frontend? Otherwise i can work independently for now and just talk to the API.

The date/time entry is definitely fiddly when you need to make manual changes. What other issues have you run in to?
Ultimately I would prefer to sort out and make improvements to the existing UI without a big rebuild at this point. But if you want to go big, I think it would make sense to do this on a fork. My intention is to create a 1.0 release with a simple frontend and make (or merge!) improvements further down the road. In our three months of usage so far we have largely found the UI to be good but certainly not perfect.
A simple deploy is definitely a big focus here. I already think it’s a bit complicated (:
Good luck with the little ones! It’s damn stressful with just one (:

What, having more makes it less stressful...?

😭😭
👶👶
💩💩
💤💤
😭😭
👶👶
💩💩
💤💤
😭😭
👶👶
💩💩
💤💤
🕐 🕜 🕙 🕥 🕚 🕦 🕛 🕧 🕑 🕝 🕒 🕞 🕓 🕟 🕔 🕠 🕕 🕡 🕖 🕢 🕗 🕣 🕘 🕤

:D
I feel ya!
We have stopped tracking all together as the interface is too hard for my partner and i'm not awake all of the time. She tends to input stuff after it happens as shes too frantic while 💩  is going down and the time inputs are too hard to use on a phone (the popup calendar doesn't disappear after you choose a day, you have to click to calendar button again). Also the mother-in-law is here and i havne't even tried to explain it to her.
I'm thinking of making all the combinations of inputs (i.e. left breast, right breast, formula, bottle breast milk, sleep, pooh, wee) into a list of buttons which start/stop the time. If you click one while another is going it ends the previous timer and starts a new one with the new activity. The concept of a timer should be transparent to the user (i.e. they don't need to know about it).
Also, the reporting isn't motivating enough to keep up with the tracking (which adds extra pain). I guess the point is to see if the sleeping patterns ( for me).
Having said that the dashboard is quite useful! To be able to check when the last diaper change was is handy or the last feeding.

I would certainly love to see your ideas for improving the time entry. My wife and I mostly input things as they happen so we rarely ever end up modifying a time, it's very interesting to hear that others use it differently and that is a pain point.
Combination buttons for timers seem like a good idea. Do you have a vision for how it might be organized? I'm just worried about jamming too much in to the timer detail interface.
Re: timers being transparent, do you not use multiple timers at once with more than one child? I set them up this way so that multiple children could be tracked with multiple timers going at once. How would this work if timers were transparent? I think it would require more data (e.g. the child and activity) at the start, right?
And yes, I agree that the reporting is pretty bleh. Actually, my biggest motivation for building this app was to create the "sleep pattern" graph, which is kind of neat to see now (3.5 months in) but really not super valuable. I agree that the dashboard is the most useful part of the app, and it's something I want to improve on for customization in the long (e.g. allowing users to enable/disable and re-order cards).

Although I see this is an old thread, and I'm not sure how much work is still being put into this, I'd like to re-ignite/continue the discussion to see if there are any improvements I might be able to help with in the few months I have left with decent sleep. I'm trying to practice/get my wife to practice using the app so it is familiar when we do need it.
Here are some of my thoughts:
*Possibility of changing how inputs are done for 'duration' inputs (like length of nap, length of playtime, etc) to have the stop time be current time (like currently coded) then the ability to enter either start time OR duration if you already know how long (my wife loves to set timers for everything so she'll already know if they played for 30 minutes, etc). This could eliminate some of the messing with the finicky calendar.
*Possibility of having start and stop buttons (similar to timer functions) to start and stop a feeding.... Although thinking about this more, the timer function seems to accomplish this.
Also my API game is a little weak, and I'd like to know if there is a way to accomplish my second thought via the API... I plan to create a raspberry pi device with buttons so we can just push a button and have it log the info into the app so we don't have to fumble with/find our phones, just push the button and be done. I'm planning to have a button for diaper changes, one to start feeding and one to stop feeding, but I'm not sure the best way to accomplish this with the API so any guidance would be appreciated there.
Thank you for making such an awesome app!

FYI I moved your API questions in to #76 and I'll give some thoughts on them there.
Not a great deal has changed since this thread, and I'm always happy to accept PRs or detailed thoughts on UI changes.
The datetime selection has indeed been a pain point for some so if you can come up with a good way to handle multiple types of input there, I'm all for it. I have never taken the time to really look in to options for that. All the form interfaces are pretty "dumb" right now so changes can be a little tricky.
The timer should essentially do what you want. You can create any type of timed entry directly from a timer instance. Generally, our process with the little one was to start a timer for whatever we were doing and then initiate the new entry (diaper change, sleep, or breast feeding) from the timer itself. This will auto-fill both the start and end times (and that's part of why I have never put deep effort in to changing the datetime select interface).


Date fields not set when generating SDK

When we are generating the client SDK of the following interface:
export class CreditCase {

  id: number & tags.Type<'uint32'>
  state: CreditCaseState

  company_name: null | string
  email: (string & tags.Format<'email'>) | null
  firstname: null | string
  lastname: null | string
  mobile_number: null | string
  phone_number: null | string

  created_at: Date
  updated_at: Date

}

It outputs the following:
import type { Format } from "typia/lib/tags/Format";
import type { Type } from "typia/lib/tags/Type";

import type { CreditCaseState } from "./CreditCaseState";

export type CreditCase = {
    id: (number & Type<"uint32">);
    state: CreditCaseState;
    company_name: string;
    email: (string & Format<"email">);
    firstname: string;
    lastname: string;
    mobile_number: string;
    phone_number: string;
    created_at: ;
    updated_at: ;
}

Upgrade to v2.1.6, then your problem would be fixed.


Support Chunked DPO Loss Kernel

Summary
Add support for a fused, torch-compiled, and chunked DPO (Direct Preference Optimization) loss kernel, as requested in https://github.com/linkedin/Liger-Kernel/issues/371.
This implementation is largely based on the excellent work done on ORPO (https://github.com/linkedin/Liger-Kernel/pull/362) by @shivam15s.
DPO Loss Formulation
In a reference setting (not reference free):
$$r_\theta(x,y_c) - r_\theta(x,y_r) = \log(\pi_\theta(y_c|x)) - \log(\pi_\theta(y_r|x))$$
$$-\log(\sigma((\log(\pi_\theta(y_c|x)) - \log(\pi_\theta(y_r|x)) - \log(\pi_{\theta_{\text{ref}}}(y_c|x)) + \log(\pi_{\theta_{\text{ref}}}(y_r|x)))/\beta))$$
Corresponds to:
# Policy model log probabilities
policy_chosen_logps = log_probs(policy_chosen_logits)
policy_rejected_logps = log_probs(policy_rejected_logits)

# Reference model log probabilities
ref_chosen_logps = log_probs(ref_chosen_logits)
ref_rejected_logps = log_probs(ref_rejected_logits)

# Compute advantages
chosen_advantages = policy_chosen_logps - ref_chosen_logps
rejected_advantages = policy_rejected_logps - ref_rejected_logps

# DPO loss
logits_diff = (chosen_advantages - rejected_advantages) / beta
losses = -F.logsigmoid(logits_diff)

In this PR:

The above mathematical equation shows that to maximize the reward difference, we get formula:
$$r_θ(x_c) - r_θ(x_r)$$
This can be further optimized using just:
$$-log(σ((π_θ(x_c) - π_θ(x_r))/β))$$
So, the code implements:logits_diff = (chosen_logps - rejected_logps) / beta  # (π_θ(x_c) - π_θ(x_r))/β
losses = -F.logsigmoid(logits_diff)                   # -log(σ(logits_diff))

Sum up DPO and NLL:
$$L_{DPO+NLL} = L_{DPO}+αL_{NLL}$$

Testing Done

Hardware Type: NVIDIA L40S (48G)
[X] run make test to ensure correctness
[X] run make checkstyle to ensure code style
[X] run make test-convergence to ensure convergence

Great work @austin362667 ! The additional summing of NLL loss is going to be useful for IRPO loss as well :). I'll be creating a simple base class which adds the boilerplate code (backward/torch compile logic) that you can inherit from, as @pramodith mentioned

Issue addressed. Thanks @Tcc0403 @lancerts  @pramodith @shivam15s and @ByronHsu for review!

I think we should make chunked_loss functions nn.Module (like flce and fljsd) for users? same for orpo? cc @shivam15s @ByronHsu

@Tcc0403 that is the plan!


Panic while reading information_schema.KEY_COLUMN_USAGE

What type of bug is this?
Crash
What subsystems are affected?
Distributed Cluster
Minimal reproduce step
Reading the information_schema.KEY_COLUMN_USAGE table
What did you expect to see?
Query success
What did you see instead?
Panic
What operating system did you use?
Unrelated
What version of GreptimeDB did you use?
0.8.1
Relevant log output and stack trace
ERROR read_from_region: common_telemetry::panic_hook: panicked at greptimedb/src/catalog/src/information_schema/key_column_usage.rs:259:21:

The table might be dropped while iterating so it does not always exist.
https://github.com/GreptimeTeam/greptimedb/blob/3f4928effc1c416caf67cd5a12dfe1408f43c9de/src/catalog/src/information_schema/key_column_usage.rs#L228-L260


`to_s': stack level too deep (SystemStackError)

Description
We are having this error on our bugsnag account every since we installed this gem to integrate with bugsnag. Is this known? The information we have it's not really helpful so I thought about reporting it to see if this is really happening from the gem itself or not.
Btw: This is happening only for our delayed_jobs
Issue
gems/activesupport-6.0.1/lib/active_support/core_ext/numeric/conversions.rb:107:in `to_s': stack level too deep (SystemStackError)
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:100:in `filters_match?'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:115:in `filters_match_deeply?'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:33:in `block in traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `each'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:36:in `block in traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `each'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `block in traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `map'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:36:in `block in traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `each'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `block in traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `map'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:36:in `block in traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `each'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `block in traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `map'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:41:in `traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:36:in `block in traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `each'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:32:in `traverse_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:17:in `clean_object'
    from gems/bugsnag-6.12.2/lib/bugsnag/cleaner.rb:75:in `clean_object_encoding'
    from gems/bugsnag-6.12.2/lib/bugsnag/helpers.rb:21:in `trim_if_needed'

Environment
Library versions:

apipie-rails (0.5.16)
bugsnag (6.12.2)
delayed_job (4.1.8)
delayed_job_active_record (4.1.4)
delayed_job_recurring (0.3.8)
factory_bot_rails (5.0.2)
rails (6.0.1)
rails-dom-testing (2.0.3)
rails-html-sanitizer (1.3.0)
request_store (1.4.1)
rspec-rails (4.0.0.beta2)
rubocop-rails (2.3.2)
sprockets-rails (3.2.1)

debug mode or production?: prod

I just found the reason. We were using bugsnag along with AppSignal (https://appsignal.com/). After disabling this gem the problem stopped. I hope it helps!

Hi @igorescobar - thanks for the report! This looks like a bug. We will investigate and get back to you.

I run into the same issue since version 6.12, although probably not related to AppSignal. The error only happens on production and AppSignal is also running on staging, where the error does not occur.
All fine with version 6.11.1.

Fixed in v6.13.1

I am still not able to deploy to production, still failing when running the Rails db:migrate-task. This time it seems it is related to AppSignal.
bundler/gems/rails-e063befb14ae/activesupport/lib/active_support/tagged_logging.rb:49:in `current_tags': stack level too deep (SystemStackError)
    from bundler/gems/rails-e063befb14ae/activesupport/lib/active_support/tagged_logging.rb:54:in `tags_text'
    from bundler/gems/rails-e063befb14ae/activesupport/lib/active_support/tagged_logging.rb:23:in `call'
    from /home/deploy/.rbenv/versions/2.7.1/lib/ruby/2.7.0/logger.rb:585:in `format_message'
    from /home/deploy/.rbenv/versions/2.7.1/lib/ruby/2.7.0/logger.rb:475:in `add'
    from bundler/gems/rails-e063befb14ae/activesupport/lib/active_support/logger_thread_safe_level.rb:53:in `add'
    from /home/deploy/.rbenv/versions/2.7.1/lib/ruby/2.7.0/logger.rb:528:in `info'
    from gems/bugsnag-6.13.1/lib/bugsnag/configuration.rb:225:in `info'
    from gems/bugsnag-6.13.1/lib/bugsnag.rb:115:in `block in notify'
    from gems/bugsnag-6.13.1/lib/bugsnag/middleware_stack.rb:89:in `block in run'
    from gems/bugsnag-6.13.1/lib/bugsnag/middleware/callbacks.rb:14:in `call'
    from gems/bugsnag-6.13.1/lib/bugsnag/middleware/warden_user.rb:38:in `call'
    from gems/bugsnag-6.13.1/lib/bugsnag/middleware/rails3_request.rb:37:in `call'
    from gems/bugsnag-6.13.1/lib/bugsnag/middleware/rack_request.rb:90:in `call'
    from gems/bugsnag-6.13.1/lib/bugsnag/middleware_stack.rb:94:in `run'
    from gems/bugsnag-6.13.1/lib/bugsnag.rb:91:in `notify'
    from gems/bugsnag-6.13.1/lib/bugsnag/integrations/rake.rb:21:in `rescue in execute'
    from gems/bugsnag-6.13.1/lib/bugsnag/integrations/rake.rb:20:in `execute'
    from gems/appsignal-2.10.6/lib/appsignal/hooks/rake.rb:18:in `execute'
    from gems/bugsnag-6.13.1/lib/bugsnag/integrations/rake.rb:19:in `execute'
    from gems/appsignal-2.10.6/lib/appsignal/hooks/rake.rb:18:in `execute'
    from gems/bugsnag-6.13.1/lib/bugsnag/integrations/rake.rb:19:in `execute'
    from gems/appsignal-2.10.6/lib/appsignal/hooks/rake.rb:18:in `execute'
    from gems/bugsnag-6.13.1/lib/bugsnag/integrations/rake.rb:19:in `execute'
    from gems/appsignal-2.10.6/lib/appsignal/hooks/rake.rb:18:in `execute'
    from gems/bugsnag-6.13.1/lib/bugsnag/integrations/rake.rb:19:in `execute'
    from gems/appsignal-2.10.6/lib/appsignal/hooks/rake.rb:18:in `execute'
    from gems/bugsnag-6.13.1/lib/bugsnag/integrations/rake.rb:19:in `execute'
    from gems/appsignal-2.10.6/lib/appsignal/hooks/rake.rb:18:in `execute'
    from gems/bugsnag-6.13.1/lib/bugsnag/integrations/rake.rb:19:in `execute'

Hi @manubo, that error seems to be caused by AppSignal using alias_method where we're using Module#prepend and they aren't compatible with eachother - see https://github.com/bugsnag/bugsnag-ruby/issues/556 and https://github.com/bugsnag/bugsnag-ruby/pull/559 for some background
Unfortunately there's no easy fix for this as if we revert the Module#prepend change, then we'll break compatiability with any package that uses Module#prepend. We're looking at ways we can fix this but it's a difficult problem to solve
This blog post by New Relic explains the problem in-depth and has a suggested fix under the heading "What should customers do currently?" - essentially Bugsnag and AppSignal should work together if Bugsnag is loaded after AppSignal. Hopefully this works for you
AppSignal have an open issue for this problem which may be worth keeping an eye on too - https://github.com/appsignal/appsignal-ruby/issues/603

@imjoehaines Thanks Joe for sharing that 👍🏼


Prompt "forgets" part until I run prompt -p

Thank you very much for prezto. I just migrated today from oh-my-zsh, and it's turning out to be quite snappy.
When I start my terminal (iterm2 and os x terminal on OSX 10.11.4), after I enter any command, like ls or something, the prompt "forgets" part of itself. To wit: after I enter the command, for example with both sorin or garrett, I get only the small > at the very left and not the colorful, large >>>.
Then, if I enter prompt -p and preview all the prompts, it consistently fixes the problem. The colorful large >>> comes back and stays until I exit the session. By the way, prompt -l or -c have no effect.
This phenomenon does not happen when I reset all the prezto-related rc files back to their defaults, but, rather only when I add in some various variables and commands to the config files. So it must be something I have in my rc files.
One way to troubleshoot it is going to be going through each line of my rc files, commenting out, and testing again. However I just wanted to ask if anyone had seen this problem before, and if perhaps you could point me in the right direction, regarding anything that might be a culprit.
Sincerely,
Rick

I don't think it's Prezto. It's iTerm2. Try a different build. Try Terminal.app.

I don't think it's Prezto either. Apologies for the general question. Same thing happens for both your default theme and the garrett theme, in both iTerm2 3 and the latest Terminal.app.
I'll test by commenting settings, and upgrading iTerm2 as well.

Ok, this was related to iTerm, @sorin-ionescu.
When I installed iTerm2 3 it offers to install command line integration, which it appends to your .zshrc in this format:
 test -e "${HOME}/.iterm2_shell_integration.zsh" && source "${HOME}/.iterm2_shell_integration.zsh"

For reference the file is copied up to this gist:
https://gist.github.com/RickCogley/6e0104cc5109cff8bd7616e8b9339aeb
It's obviously messing with things, so I have disabled it for now.

Thanks for your patience.


Documentation for titlehub api endpoint doesn't exist

Hey,
I am talking about https://titlehub.xboxlive.com/users/xuid(2584878536129841)/titles/titlehistory/decoration/achievement,image,detail specifically, it doesn't seem to support skipItems and continuationToken params so it's a bit though to work with it as there's no documentation provided.

Thanks for the URL

Maybe this will help someone, I surely haven't found any docs for this endpoint but I know I would have just about killed to have it laid out this simply a few weeks ago... Sorry if the code is a bit hideous
import fs from 'fs'
import { Authflow as AF } from 'prismarine-auth';
let authf = new AF('', './auth')
// Initiate a code proof exchange to auth with microsoft, and wait for the user to complete it before moving on

const response = authf.getXboxToken().then(auth => // Easiest XSTS auth ever
  axios.get(`https://titlehub.xboxlive.com/users/xuid(${'2535987654321012'})/titles/titlehistory/decoration/scid,image,detail`, {
    headers: {
      'x-xbl-contract-version': '2',
      'Authorization': `XBL3.0 x=${auth.userHash};${auth.XSTSToken}`,
      "Accept-Language": "en-US"
    }
  }).then((req => { // Prep a JSON file in the CWD for output
    if (!fs.existsSync(`./data.json`)) {
      fs.writeFile(`./data.json`, '[]', (err) => {
        if (err) return console.error(err)
        console.log(req)
      })
    }
    const datalist = []

    req.data.titles.forEach(t => datalist.push(t))
    fs.writeFileSync(`./data.json`, JSON.stringify(datalist)) // Output the serialized response to data.json
  }))
)

Hey,
I am talking about https://titlehub.xboxlive.com/users/xuid(2584878536129841)/titles/titlehistory/decoration/achievement,image,detail specifically, it doesn't seem to support skipItems and continuationToken params so it's a bit though to work with it as there's no documentation provided.

hello，can I get play duration from this api？ Please！

Hi Guys,
Is there some way to get these XUID-s from the WEB Rest API.
I'm building a web app with live auth in it and after that I wanted to fetch some public user data, like count of achievements and gamerscore.
Any thoughts?


temporary fix to get around validation

No modification for Ruby

No modification for NodeJS

No modification for Python

@fearthecowboy What is this about? Can you help me understand what is the glitch or you are just testing it out?


Moved period outside of conditional in line 33

The period wasn't rendering in cases where the condition was not met because it was inside the conditional.

Why:
Closes [issue link]

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

https://www.paypal.com/pools/c/8OmsxaiDuZ
On Sat, Oct 22, 2022, 12:54 PM Rachel Schipull @.***>
wrote:

The period wasn't rendering in cases where the condition was not met
because it was inside the conditional.
Why:
Closes [issue link]
What's being changed (if available, include any code snippets,
screenshots, or gifs): Check off the following:

I have reviewed my changes in staging (look for the "Automatically
generated comment" and click the links in the "Preview" column to view your
latest changes).
For content changes, I have completed the self-review checklist
https://github.com/github/docs/blob/main/contributing/self-review.md#self-review
.

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/21558
Commit Summary

a64523e
https://github.com/github/docs/pull/21558/commits/a64523ee93f477367972c78328cff10f82ec3413
Moved period outside of conditional in line 33

File Changes
(1 file https://github.com/github/docs/pull/21558/files)

M
content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
https://github.com/github/docs/pull/21558/files#diff-8d2b281dec00333d1f58562c00dd578532e468ca5df7fd39b532a40d11b241f4
(2)

Patch Links:

https://github.com/github/docs/pull/21558.patch
https://github.com/github/docs/pull/21558.diff

—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/21558, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZVIUCWJC3GYYWM5WUP2WRTWEQL5VANCNFSM6AAAAAARL5IMV4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@rachelschipull Great catch! 👀
I'll get this triaged for review. Thanks for opening a PR! ⚡


stream did not contain valid UTF-8

The same error is reported when starting using cli or configuration file
martin -c world.mbtiles => Unable to load config file world.mbtiles: stream did not contain valid UTF-8

A config file should be there:
martin -c your_config_file.yml world.mbtiles

You could run Martin without config file either:
martin world.mbtiles

config.yaml.zip
When I use the configuration file, the tile data access 404, as shown in the figure.
This is my config file.

I suppose you are using the world_cities.mbtiles from Martin repo?
It's normal some requests is 404 because there is no data. But if every request is 404, there must be something wrong about the gridset.
The gridset of this file is 3857. What's the gridset in your frontend code?


Add Rain Finance token

{
"chainId": 101,
"address": "23GYXSNdxZi47QLY3c7iG6Q5g6heqWRReuNnAqdDiRfB",
"symbol": "RFT",
"name": "Rain Finance",
"decimals": 9,
"logoURI": "https://raw.githubusercontent.com/solana-labs/token-list/main/assets/mainnet/rain logo.jpg",
"tags": [
"utility-token",
"community-token"
],
"extensions": {
"instagram": "https://instagram.com/rainfinance.rft",
"telegram": "https://t.me/rainfinance",
"twitter": "https://twitter.com/rain_finance",
"website": "https://rainfinance.io"
}
},
"chainId": 101,
"address": "DFJDXWYUKiJV5vpgKaJTmiRWfVhYy2BYdGH66nqHxes6",

{
"chainId": 101,
"address": "23GYXSNdxZi47QLY3c7iG6Q5g6heqWRReuNnAqdDiRfB",
"symbol": "RFT",
"name": "Rain Finance",
"decimals": 9,
"logoURI": "https://raw.githubusercontent.com/solana-labs/token-list/main/assets/mainnet/rain logo.jpg",
"tags": [
"utility-token",
"community-token"
],
"extensions": {
"instagram": "https://instagram.com/rainfinance.rft",
"telegram": "https://t.me/rainfinance",
"twitter": "https://twitter.com/rain_finance",
"website": "https://rainfinance.io/"
}
},
"chainId": 101,
"address": "DFJDXWYUKiJV5vpgKaJTmiRWfVhYy2BYdGH66nqHxes6",

{
"chainId": 101,
"address": "23GYXSNdxZi47QLY3c7iG6Q5g6heqWRReuNnAqdDiRfB",
"symbol": "RFT",
"name": "Rain Finance",
"decimals": 9,
"logoURI": "https://raw.githubusercontent.com/solana-labs/token-list/main/assets/mainnet/rain logo.jpg",
"tags": [
"utility-token",
"community-token"
],
"extensions": {
"instagram": "https://instagram.com/rainfinance.rft",
"telegram": "https://t.me/rainfinance",
"twitter": "https://twitter.com/rain_finance",
"website": "https://rainfinance.io/"
}
},
"chainId": 101,
"address": "DFJDXWYUKiJV5vpgKaJTmiRWfVhYy2BYdGH66nqHxes6",


change cla doc

I have read the CLA Document and I hereby sign the CLA

Codecov Report

Merging #68 (0168a76) into main (691308b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #68   +/-   ##
=======================================
  Coverage   89.89%   89.89%
=======================================
  Files          15       15
  Lines         366      366
=======================================
  Hits          329      329
  Misses         26       26
  Partials       11       11

Continue to review full report at Codecov.

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


Bonding Contracts UI enhancement

`

The following components are deprecated by this new UI:

chefugov.tsx (deleted): the "claim Ubiquity rewards" button, it only worked with the first user share
deposit.share.redeem.tsx (deleted): It was just broken, didn't even attempted to call the removeLiquidity function
deposit.share.balance.tsx (deleted): The information is loaded on the BondingSharesExplorer component
deposit.share.tsx -> DepositShare.tsx: Integrated into BondingSharesExplorer

All the features are quite self-explanatory.
Resolves #9  #6 and all the issues community members were having with seeing their bonding shares. Also solves this issue from the uad-contracts repo https://github.com/ubiquity/uad-contracts/issues/33
Calculates the APY too, so resolves this one https://github.com/pavlovcik/uad-ui/issues/4

📝 Changed routes:

/monitor
/styles

(view full size)
(view full size)

/styles/tailwind

(view full size)

Commit acb14d6a9ded1fd1aa989651afcd93096847e31c (https://uad-ui-pdzfv8hh8-pavlovcik.vercel.app).

Looks like it's working on the current deployment; merge?

Aaaand I think I'm done, it's ready!


duffs, autarchical

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[a,d]

/trunk merge


Support Kubernetes pod security admission

What steps did you take and what happened:
Ran the following against an OpenShift version 4.12 cluster.  Version 4.12 is based on Kubernetes version 1.25 and configures Kubernetes pod security admission to enforce restricted by default.
 sonobuoy run --mode=certified-conformance --dns-namespace=openshift-dns --dns-pod-labels=dns.operator.openshift.io/daemonset-dns=default --timeout 14400

This issued the following warning:
W1108 15:20:50.839688     401 warnings.go:70] would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "kube-sonobuoy" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "kube-sonobuoy" must set securityContext.capabilities.drop=["ALL"]), seccompProfile (pod or container "kube-sonobuoy" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")

OpenShift automatic pod security namespace labeling saw that the namespace needed the following labels so added them:
    pod-security.kubernetes.io/enforce: privileged
    pod-security.kubernetes.io/enforce-version: v1.24

What did you expect to happen:
Sonobuoy should properly configure its Kubernetes resources to support restricted pod security admission.
Anything else you would like to add:
N/A
Environment:

Sonobuoy version: 0.56.10
Kubernetes version: (use kubectl version): 1.25
Kubernetes installer & version: N/A
Cloud provider or hardware configuration: Red Hat OpenShift on IBM Cloud
OS (e.g. from /etc/os-release): N/A
Sonobuoy tarball (which contains * below): N/A

Hi @rtheis,
v0.56.16 has just been released that adds a flag to set the enforce level. Please let me know if this is enough in your implementation and unblocks you without the optional version lock.

Thank you @franknstyle.  We'll pull this version into our testing and let you know.


fix unit tests

Before submitting a pull request, please read
https://github.com/bancolombia/scaffold-clean-architecture/wiki/Contributing
Description
Fix issue #245
Some IDEs like VSCode or Eclipse use the bin folder to compile and use resources. The plugin searches all the files by specific extension and concatenates it to the root of the test project, which generates an inconsistency in the file path, so the valid directories for file search are filtered.
Category

[ ] Feature
[x] Fix

Checklist

[x] The pull request is complete according to the guide of contributing
[x] Automated tests are written
[x] The documentation is up-to-date
[x] The pull request has a descriptive title that describes what has changed, and provides enough context for the changelog
[ ] If the pull request has changed structural files, you have implemented an UpgradeAction according to the guide

@santitigaga

Thank you for the help, When I execute the unit test in this branch  with windows,5 tests fail


Add prerequisite criteria for higher levels; Fixes #838

This commit officially adds the achieve_passing and achieve_silver
criteria for the silver and gold levels respectively.
The statuses for these criteria automatically calculated and stored
in the database along with an empty justification. This implementation
was chosen as it makes the code a bit simpler.
Upon deployment, the rake task
"update_all_higher_level_badge_percentages" must be ran to update
the new fields for all projects.
Signed-off-by: Jason Dossett<EMAIL_ADDRESS>

Codecov Report

Merging #872 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #872   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          45     45
  Lines        1441   1451   +10
=====================================
+ Hits         1441   1451   +10

Impacted Files
Coverage Δ

app/models/project.rb
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Looks good to me.
I think this simplifies the user's mental model; it means that when you get 100% of the silver criteria, you have earned the silver badge, the end.  That's easier to explain than to say "100% AND also have the passing badge".  Since it's captured in a single number, it'll also be easier to graph.
Adding the unused justification field is a little odd, but it makes sense that adding them would make the code simpler (by eliminating the need to handle special conditions).  There are already 276 fields in a project, so one more field doesn't really make any difference :-).


Implement clamp() for vectors to remove dependency on mpi_cpp_tools

Description
Add unit tests for this function.
Add a simple implementation of a clamp function for Eigen vectors to
remove the dependency on mpi_cpp_tools.
I put it in a separate header file for more isolated unit testing.  Let me know if I should add it to one of the existing headers instead.
How I Tested
With the unit tests. Not yest tested on the robot! This still needs to be done before merging.
I fulfilled the following requirements

[x] All new code is formatted according to our style guide (for C++ run clang-format, for Python, run flake8 and fix all warnings).
[x] All new functions/classes are documented and existing documentation is updated according to changes.
[x] No commented code from testing/debugging is kept (unless there is a good reason to keep it).

You can merge :+1:

You can merge

Thanks.  I'll merge after I tested it on the robot.


build script not running on Windows

Describe the bug
The npm run build command errors out on Windows. This is the error message I get when I run it -
PS D:\xampp\htdocs\gitcontributions\freeCodeCamp> npm run build

><EMAIL_ADDRESS>build D:\xampp\htdocs\gitcontributions\freeCodeCamp
> npm-run-all ensure-env -p build:*

><EMAIL_ADDRESS>ensure-env D:\xampp\htdocs\gitcontributions\freeCodeCamp
> cross-env DEBUG=fcc:* node ./tools/scripts/build/ensure-env.js

  fcc:tools:ensure-env pathMigration present +0ms

><EMAIL_ADDRESS>build:client D:\xampp\htdocs\gitcontributions\freeCodeCamp
> cd ./client && npm run build

><EMAIL_ADDRESS>build:server D:\xampp\htdocs\gitcontributions\freeCodeCamp
> cd ./api-server && npm run build

><EMAIL_ADDRESS>build D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server
> babel server --out-dir lib --ignore 'node_modules /**/*','/**/*.test.js' --copy-files

& node ../tools/scripts/build/ensure-env.js

'Client workers building...'  workers ready.' &
Error: EPERM: operation not permitted, scandir 'D:/$RECYCLE.BIN/S-1-5-18'
    at Object.readdirSync (fs.js:955:3)
    at GlobSync._readdir (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:288:41)
    at GlobSync._readdirInGlobStar (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:267:20)
    at GlobSync._readdir (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:276:17)
    at GlobSync._processReaddir (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:137:22)
    at GlobSync._process (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:132:10)
    at GlobSync._processGlobStar (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:380:10)
    at GlobSync._process (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:130:10)
    at GlobSync._processGlobStar (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:383:10)
    at GlobSync._process (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:130:10) {
  errno: -4048,
  syscall: 'scandir',
  code: 'EPERM',
  path: 'D:/$RECYCLE.BIN/S-1-5-18'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `babel server --out-dir lib --ignore 'node_modules /**/*','/**/*.test.js' --copy-files`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Dev\AppData\Roaming\npm-cache\_logs\2020-08-24T07_01_59_666Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build:server: `cd ./api-server && npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build:server script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Dev\AppData\Roaming\npm-cache\_logs\2020-08-24T07_01_59_694Z-debug.log
ERROR: "build:server" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `npm-run-all ensure-env -p build:*`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Dev\AppData\Roaming\npm-cache\_logs\2020-08-24T07_01_59_839Z-debug.log

To Reproduce
Steps to reproduce the behavior:

Follow the steps to be able the run the dev server locally
Run npm run build
See error

Expected behavior
The build script should run and build the production build which I'll be able to use with the start script.
Desktop (please complete the following information):

OS: Windows 10 (v2004) (64 Bit)
Node Version: v12.18.3

Additional context
I can currently run the dev server in Windows after applying the fixes in #39374 and #39454 manually.

You should launch PowerShell as administrator.

There shouldn't be any need to have elevated privileges when running fCC.  There's no need on 'nix systems, so hopefully Windows is the same.

So, I think you should try it on command prompt instead of PS.
On Wed, 26 Aug 2020, 6:57 pm Oliver Eyton-Williams, <
<EMAIL_ADDRESS>wrote:

There shouldn't be any need to have elevated privileges when running fCC.
There's no need on 'nix systems, so hopefully Windows is the same.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/39458#issuecomment-680879103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALFX2SYPZIIXKZ4OAFZSZWLSCUEVHANCNFSM4QJFWM3Q
.

I tried running the build script both in cmd and powershell with and without admin rights and it still fails.
I'll look more into it once I have some time.

I think there is a problem with permissions only as the first error is
'Client workers building...'  workers ready.' & Error: EPERM: operation not permitted, scandir 'D:/$RECYCLE.BIN/S-1-5-18'     at Object.readdirSync (fs.js:955:3)     at GlobSync._readdir (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:288:41)     at GlobSync._readdirInGlobStar (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:267:20)     at GlobSync._readdir (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:276:17)     at GlobSync._processReaddir (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:137:22)     at GlobSync._process (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:132:10)     at GlobSync._processGlobStar (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:380:10)     at GlobSync._process (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:130:10)     at GlobSync._processGlobStar (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:383:10)     at GlobSync._process (D:\xampp\htdocs\gitcontributions\freeCodeCamp\api-server\node_modules\glob\sync.js:130:10) {   errno: -4048,   syscall: 'scandir',   code: 'EPERM',   path: 'D:/$RECYCLE.BIN/S-1-5-18' }
and it clearly states operation not permitted
You can try this-

npm cache clean --force
delete node_modules folder
delete package-lock.json file
npm install

Recommend using WSL on Windows 10 (we do not have support for older OS), or alternatively use GitPod.


feat(#477): Add Longs Support for HexData Class

In this PR I add support of Long types for HexData class.
Closes: #477.

History:

feat(#477): try to add more types for HexData
feat(#477): repair all unit tests and add README for one of the integration tests
feat(#477): refactor HexData class
feat(#477): repair HexData class
feat(#477): add javadoc for HexData
feat(#477): add a few more tests
feat(#477): add long values parsing
feat(#477): fix all qulice suggestions
feat(#477): add one more puzzle

PR-Codex overview
The focus of this PR is to refactor the HexData class for better readability and maintainability. It introduces a DataType enum to handle data conversions more efficiently.
Detailed summary

Added a new DataType enum to handle data conversions more efficiently
Refactored HexData class to use DataType enum for value and type conversions
Updated tests in HexDataTest to cover new data type conversions

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@rultor merge

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 15min)

@rultor merge

@volodya-lombrozo The pull request is closed already, so I can't merge it

@rultor merge

@volodya-lombrozo I'm sorry, I don't understand you :( Check this page and try again please

@rultor merge

@volodya-lombrozo The pull request is closed already, so I can't merge it

@rultor merge

@volodya-lombrozo I'm sorry, I don't understand you :( Check this page and try again please


Running sqlx prepare without Cargo

Is your feature request related to a problem? Please describe.
We're using Bazel and rules_rust to build all of our Rust libraries and binaries. We don't use Cargo at all, which means that we don't have any Cargo.toml file to describe our workspace or crates, and as such cargo build cannot compile our project. Everything is defined in BUILD.bazel files instead.
Describe the solution you'd like
Provide a sqlx prepare command that doesn't require being run through Cargo, possibly taking in a .rlib instead and using a solution akin to UniFFI's metadata macros: embed the generated queries within the generated binary or library, and extract it as part of the sqlx prepare command.
Describe alternatives you've considered
Another way to fix this issue would be to provide first-class Bazel support, but that would not scale well to other cargo-less setups.

If I understand correctly, running rustc in "check" mode (the same way it's invoked by cargo check) with a few environment variables should be sufficient. cargo sqlx prepare invokes cargo check with SQLX_TMP, SQLX_OFFLINE set to false, and SQLX_OFFLINE_DIR points to the .sqlx folder.
So it should be possible to set up such a rule in Bazel to generate the .sqlx.


Perposal: sqlite3-wasm as presistent storage

File-based Persistence: IndexedDB appears to have hard metadata limits and does not work for large vaults (where caching is most desparately needed). An alternative multi-file database (of sorted JSON documents), like LowDB or LevelDB, will work better.

Check out the exciting news of high performance sqlite3 backed by OPFS from File System API:
https://sqlite.org/wasm/doc/trunk/index.md
https://developer.chrome.com/blog/sqlite-wasm-in-the-browser-backed-by-the-origin-private-file-system/

Note
the API required for sqlite3 to work, including SharedArrayBuffer, OPFS, is not yet available in Obsidian Mobile (backed by capactorjs)

Running example
After some testing, I've got sqlite3-wasm working in obsidian desktop (Installer v1.1.9), you can

download production build from https://sqlite.org/2022/sqlite-wasm-3400000.zip
replace the following code in sqlite3.js:

  const loadWasm = WebAssembly.instantiateStreaming
        ? async ()=>{
          return WebAssembly.instantiateStreaming(wfetch(), imports)
            .then((arg)=>onSuccess(arg.instance, arg.module));
        }
        : async ()=>{
          return wfetch()
            .then(response => response.arrayBuffer())
            .then(bytes => WebAssembly.instantiate(bytes, imports))
            .then((arg)=>onSuccess(arg.instance, arg.module));
        };

to
  const loadWasm = async ()=>{
          return require('fs/promises').readFile(PATH_TO_SQLITE3_WASM)
            .then(bytes => WebAssembly.instantiate(bytes, imports))
            .then((arg)=>onSuccess(arg.instance, arg.module));
        };

(replace variable PATH_TO_SQLITE3_WASM to actual file path)
(use nodejs's fsPromises.readFile for convenience, you can replace it with valut.adapter.readBinary())
3. load sqlite3.js
function loadScript(script) {
  let scriptElement = document.createElement('script');
  scriptElement.type = 'text/javascript';
  scriptElement.appendChild(document.createTextNode(script));
  document.body.appendChild(scriptElement);
}
loadScript(require('fs').readFileSync(PATH_TO_SQLITE3_JS, 'utf8'))

(replace variable PATH_TO_SQLITE3_JS to actual file path)

copy paste demo1() function definition and run the function after initialization:

log = console.log;
warn = console.warn;
demo1(await window.sqlite3InitModule());

I'd be happy to use sqlite3 as a metadata store but the lack of mobile support makes it an incomplete solution; am I stuck using IndexedDB on mobile?

To my knowledge, the reason why sqlite3-wasm not working on mobile is that underlying webview framework don't support enable file access API required for sqlite3-wasm, which won't be fixed easily. And the file access API is necessary to solve issue that other in-memory database solution like LowDB and sqljs have, because without direct file access, they will have to load the entire database to memory on load and overwrite the database file on save, and this behavior may be too resource-consuming for large vaults.
the sqlite3-wasm solution is bulit on top of latest web standard so it should be future-proof. To work around the issues on mobile, one potential solution is requset obsidian mobile support for sqlite3 capactor plugin, which provide support to connect to sqlite3 database using native code, and use a compat layer so that sql statements can be reused between two environment

Make.md uses sql.js and it works fine on mobile. You can just copy it.

10,000 vault sizes are not an issue for the indexer if you load/save based on user reports. Aidan is right that there are limits to in memory since the max is heap that can be allocated is ~200mb but with proper mem management, 15,000 vault kept around 120mb total while the indexer is entirely in mem. The other solutions mentioned are great but years out from being nearly ready. There are alternative solutions if you keep desktop only as mentioned.

I haven't tested the SQLite3-wasm that they released, the api is not as rich as sqljs but based on benchmarks it's more performant. Aiden if you want to get it to work for a plug-in you need to package the wasm as a base64 encoded binary in the main.je

Good news: possibility to support sqlite3-wasm in mobile with webview after 2023/03:
https://github.com/rhashimoto/wa-sqlite/discussions/67
https://sqlite.org/wasm/doc/trunk/persistence.md#:~:text=option is used.-,OPFS SyncAccessHandle Pool VFS,-(Added%20in%20SQLite

I was about to say that there are approaches like the following too > https://github.com/jlongster/absurd-sql 😄


Installed version doesn't have access to build setting preset files

This results in projects that don't have default build settings applied for config type, platform or product type

@pepibumur Do you have any tips here regarding homebrew? We need the SettingsPreset folder to be somehow accessible when running

I've managed to add that directory in by adding this to the install script in the Formula
pkgshare.install "SettingPresets"

Now I need find to out how to access these files

Fixed. Awaiting new release

I just saw it. How did you manage to access the files @yonaskolb?

Path(Bundle.main.bundlePath) + "../share/xcodegen/SettingPresets/\(path).yml"

If that doesn't exist I check the following for local builds and tests
Path(#file).parent().parent().parent() + "SettingPresets/\(path).yml"

It looks this issue is still happening, Installed latest version(2.17.0) by mint.

@farshadtx so the setting presets aren't loading? Do you get warnings when generating?

Yes, that's the problem.


Loading hello-world brings down the solution

Since moving to the non-command line exercism implementation (which nicely avoids us shelling out) - the exercise retrieval code doesn't pull down only the test without the solution.
So when you run the test it simply passes.
We should filter out the non-tests, and then use TDD to create a new class and let the tests guide you to a solution.

@samWson actually its not quite what I thought - it looks like its remembering my solution from before somehow? Is it cached somewhere - and how do I reset the cache? I can see that it could be advantageous to bring back my old solution if I had already worked on it.

@samWson I've now realised that its actually bringing down any code you submitted previously (and as  I hadn't left the pharo track, I still had some solutions still sitting up there).
I think this is actually how you would want it to work - so I'll close this. NICE


update clarity

we can make this one clearer, usually we seen  extern 'C' ... in header files, & and avoid paraphrasing redundancy in "source code file"

Learn Build status updates of commit 093a812:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/cpp/const-cpp.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@corob-msft
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@molecula451
I appreciate the time and effort you've put into improving the documentation. Unfortunately, this change isn't appropriate here. It's true that you can declare an extern "C" variable in a header file, but you can't include that header in a C source file, since C doesn't know what extern "C" means. Similarly, you don't want to define an extern "C" variable in a header file (that is, initialize it), because that can lead to multiple definitions that will make the linker throw an error. The example in this article really is meant to be used in a C++ source file (the sort with a .cpp extension). So, I'm sorry your effort isn't being rewarded, but this PR shouldn't be merged.

my bad, re-read the stuff, i tought i was read 2 times, cpp, thanks all good


PE AreaDetector Data Acquisition Sequence & Data Type

At XPD we use PE AreaDetector for 2D image data collection and save files in tiff format. There are two issues/changes needs to be addressed.

In the current data collection protocol, we SUM a numbers of frames and save them to one tiff file. The SUM is done in the Area Detector plugins defining same number of images in the NDARRAY SUM. This limits us in having one file for each step of a temperature o other positioner scan. In some circumstances we might need several summed tiff files collected and saved at each STEP of the scan. We would like to have this flexibility integrated into the Ophyd. This protocol can me achieved using the Area Detector NDARRAY plugins. But need help to implement the same into Ophyd. The same protocol to be used for Dark Image. I have tested this protocol using Area-detector not through Ophyd, it works fine.
The data type seems to be Int16 bit which limits to about 65K for the summed file. This might be a problem. We would like to change this to Float32.

@sghose
For point 1 https://github.com/tacaswell/ophyd/blob/master/ophyd/controls/area_detector.py#L692 that class needs to be modified to

set the number of frames going into the resource document to match the number really saved in def _insert_fs_resource(self).
set the correct area detector plugin fields to make that happen in def _extra_AD_configuration(self)
__init__ of this class will have to be updated to the value to be set on initialization + define an instance attribute to store the number of frames to be saved

Where does the logic to make sure that total frame % num to save == 0 live?  If area detector does not take care of it, that logic will also have to be implemented in AreaDetectorFileStoreTIFFSquashing.
This will automatically apply to both dark and light frames.
Not sure about point 2 as I am not sure exactly where the conversion to int64 is happening (or not happening).  My guess is that this is a setting in the area detector plugin layer.  Once we know what flag to set, it will be a matter of adding one line to the def _extra_AD_configuration(self) method

Note that I commented out a number of PVs so that Ophyd doesn't try to connect them when it starts.
The following PVs are commented out and need to be uncommented before this Issue can be closed.
tth in 10-endstation.py
slt_mb2_* in 10-optics.py

At XPD, dark frames are being collected in the wrong order... The dark frame needs to be collected before the light frame because the Perkin Elmer detector has a residual charge that remains in the dark image.

pe1.darkfield_interval = 3 is setting the number of dark frames to take at each data point NOT the number of data points to wait between taking each dark frame.  Is this the intended behavior?

If you monitor the shutter and the acquisition PVs of the Perkin Elmer detector, the following is produced for the following ascan: ascan(nullmtr, 0, 1, 3)
IPython output:
In [19]: ascan(nullmtr, 0, 1, 3)
Stored '_scan_id' (int)
writing to pv: XF:28IDC-ES:1{Det:PE1}TIFF1:FileNumber
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:ResetFilter
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:EnableCallbacks
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:EnableFilter
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:FilterType
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:AutoResetFilter
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:FilterCallbacks
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:NumFilter
writing to pv: XF:28IDC-ES:1{Det:PE1}cam1:NumImages
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:FilterCallbacks
writing to pv: XF:28IDC-ES:1{Det:PE1}TIFF1:NDArrayPort
2015-06-17 15:42:30,645 [ophyd_session:INFO] Scan ID: 558
2015-06-17 15:42:30,645 [ophyd_session:INFO] Time: 2015-06-17T15:42:30.642412
2015-06-17 15:42:30,645 [ophyd_session:INFO] uid: 015d1750-1d5c-439f-8392-a3630809845e
2015-06-17 15:42:30,645 [ophyd_session:INFO] Begin Run...
2015-06-17 15:42:30,646 [ophyd_session:INFO] pe1_acquire_time	pe1_image_darkfield	pe1_acquire_period	pe1_image_lightfield	shctl1	em_ch1	em_ch2	em_ch3	em_ch4
True
2015-06-17 15:42:43,177 [ophyd_session:INFO] 1.0	386f975d-651f-4077-993b-869629791f5e	1.0	38af632f-237b-4193-b8f0-577056cf80b9	1	0.313925743103	0.313997268677	0.314140319824	0.314140319824
True
2015-06-17 15:42:54,333 [ophyd_session:INFO] 1.0	386f975d-651f-4077-993b-869629791f5e	1.0	59250125-49b3-41fa-8a15-cf68a076d883	0	0.313854217529	0.313997268677	0.314211845398	0.314211845398
True
2015-06-17 15:42:56,145 [ophyd_session:INFO] 1.0	386f975d-651f-4077-993b-869629791f5e	1.0	ceb5d440-cdc2-41a2-9599-d1f8826511d7	0	0.313925743103	0.313997268677	0.314211845398	0.314211845398
True
2015-06-17 15:43:08,178 [ophyd_session:INFO] 1.0	b6a98040-0e59-4acf-8325-d2f4b3eaea84	1.0	758b0874-99e9-41d7-b2d0-b450a1a81728	1	0.313925743103	0.313997268677	0.314211845398	0.314211845398
2015-06-17 15:43:08,202 [ophyd_session:INFO] End Run...

camonitor output:
xf28id1@xf28id1-ws2:/nfs/xf28id1$ camonitor XF:28IDC-ES:1{Sh:Exp}Sts-Sts XF:28IDC-ES:1{Det:PE1}cam1:Acquire
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:41:41.858203 Closed
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:41:46.542360 Done
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:26.457341 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:26.457341 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:42:33.862111 Open
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:37.813295 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:37.813295 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:42:44.863799 Closed
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:48.840981 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:48.840981 Done
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:50.151471 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:50.151471 Done
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:51.962916 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:42:51.962916 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:42:58.870959 Open
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:43:02.993515 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:43:02.993515 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:43:09.872338 Closed

I am unsure if the shutter state is being reported correctly, because this scan output is very confusing

with ascan.darkfield_interval = 0
and ascan.user_detectors.append(pe1)
In [7]: ascan(nullmtr, 0, 1, 3)
Stored '_scan_id' (int)
writing to pv: XF:28IDC-ES:1{Det:PE1}TIFF1:FileNumber
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:ResetFilter
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:EnableCallbacks
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:EnableFilter
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:FilterType
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:AutoResetFilter
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:FilterCallbacks
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:NumFilter
writing to pv: XF:28IDC-ES:1{Det:PE1}cam1:NumImages
writing to pv: XF:28IDC-ES:1{Det:PE1}Proc1:FilterCallbacks
writing to pv: XF:28IDC-ES:1{Det:PE1}TIFF1:NDArrayPort
2015-06-17 15:54:40,148 [ophyd_session:INFO] Scan ID: 566
2015-06-17 15:54:40,148 [ophyd_session:INFO] Time: 2015-06-17T15:54:40.145223
2015-06-17 15:54:40,148 [ophyd_session:INFO] uid: 4c8bb407-2e9d-4f65-a49b-0cb2414386f0
2015-06-17 15:54:40,148 [ophyd_session:INFO] Begin Run...
2015-06-17 15:54:40,149 [ophyd_session:INFO] em_ch1	em_ch2	em_ch3	em_ch4	pe1_acquire_time	pe1_acquire_period	pe1_image_lightfield	shctl1
True
2015-06-17 15:54:51,926 [ophyd_session:INFO] 0.313925743103	0.313997268677	0.314211845398	0.314211845398	1.0	1.0	475a3a78-ad9f-4b95-b980-8d9916b9bfd3	1
True
2015-06-17 15:55:12,967 [ophyd_session:INFO] 0.313925743103	0.31406879425	0.314211845398	0.314211845398	1.0	1.0	5a67c612-3e74-4f5d-8077-c9452f796a57	1
True
2015-06-17 15:55:34,011 [ophyd_session:INFO] 0.313925743103	0.313997268677	0.314140319824	0.314140319824	1.0	1.0	50971889-f320-4704-983a-2e80aa5ce33a	1
True
2015-06-17 15:55:55,072 [ophyd_session:INFO] 0.313925743103	0.313997268677	0.314140319824	0.314140319824	1.0	1.0	3b53ff9c-9032-48f5-8e1f-b46104e7d5d4	1
2015-06-17 15:55:55,157 [ophyd_session:INFO] End Run...

and the camonitor output:
xf28id1@xf28id1-ws2:/nfs/xf28id1$ camonitor XF:28IDC-ES:1{Sh:Exp}Sts-Sts XF:28IDC-ES:1{Det:PE1}cam1:Acquire
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:52:25.949657 Closed
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:52:29.994294 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:54:42.463129 Open
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:54:45.960467 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:54:45.960467 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:54:53.462998 Closed
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:55:03.474460 Open
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:55:07.612528 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:55:07.612528 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:55:14.488999 Closed
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:55:24.476733 Open
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:55:28.656761 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:55:28.656761 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:55:35.468563 Closed
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:55:46.485008 Open
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:55:49.715600 Acquire
XF:28IDC-ES:1{Det:PE1}cam1:Acquire 2015-06-17 15:55:49.715600 Done
XF:28IDC-ES:1{Sh:Exp}Sts-Sts   2015-06-17 15:55:56.491426 Closed

This seems to be behaving correctly

This has been untouched since June.
@sghose If these issues persist make a new issue please.


fix(calendar): remove not nice border around calendar events

:tada: This PR is included in version 1.35.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Consolidate code shared between this repo and the workflow repo

I don't know what I was referring to.


v0.12.x - Add details when JSON decode failure occurs

Currently decode failure looks like this:
org.http4s.DecodeFailureException: Could not decode JSON   at org.http4s.MessageOps$$anonfun$as$1.apply(MessageOps.scala:92)   at org.http4s.MessageOps$$anonfun$as$1.apply(MessageOps.scala:92)   at scalaz.$bslash$div.fold(Either.scala:56)
In the newer versions, there are some details to assist on debugging.

The current behavior incorporates both the sanitized and details.  I think this would be a superior definition of ParseFailure.msg.
I pushed a 0.12.x branch as a basis for a pull request, and will publish an 0.12.5 if it would help.  (Not called release-0.12.x, because I don't want it to publish the site with our Travis setup.)

Fixed by #828


Missing URL?

[Under title "Configure Azure AD SSO", Step 4, only the identifier URL is present. Basic SAML Configuration
has two required fields "Identifier (Entity ID)" and also "Reply URL (Assertion Consumer Service URL)." The Reply URL value seems to be missing from step 4.]

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

ID: 166ceeac-caac-af97-0de7-4cf3ad1be1e9
Version Independent ID: 2fd6236b-4113-91e9-e0d2-8a6b89c18d82
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with Terraform Cloud
Content Source: articles/active-directory/saas-apps/terraform-cloud-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@c3474
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

#please-close


Add more checks from inspec-openstack-security

This refactors the openstack checks to be set up in the inspec meta
role for glance, neutron, nova. It also adds additional checks for
aodh, ceilometer, and heat. More checks for glance was also added
and the list of glance configuration files has been added as well.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

This depends on https://github.com/blueboxgroup/ursula/pull/2631 and will need to be rebased.

ok to test

This PR depends on a one profile structure for ursula-inspec. It depends on this PR: https://github.com/blueboxgroup/ursula-inspec/pull/5.
This PR is also in conflict with a another PR and will need to be rebased with #2631

split this out into two PRs.   one that adds the specs for heat etc back in,  the other for the ursula-inspec stuff.

retest

ok to test

ok to test

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

retest


Transforms not applied to named dependencies?

I am using partialify as a transform to allow me to require() HTML files. It works fine as long as the require('./some.html') call is in a file that is `require()'ed via file path, but if it's required by name the HTML gets parsed directly and throws an error. Guessing it's the same root issue as #600.

@thlorenz I would love to be able to apply transforms to some of the modules in node_modules manually.
Perhaps something like this:
"browserify": {
    "dependencies": [
        "moduleName: ["brfs"]
    ]
    "transform": [ "brfs" ]
  }


adds ctx to preprocess

This PR would allow context/ctx to be used in preprocess in the same way it is currently usable in transform.
This let's the user, for example, add issues/errors already in the preprocessing state.
Related to https://github.com/colinhacks/zod/issues/696

Made a couple tweaks but looks good.


Missing authorization group

          - missing authorization group

The Authorization Group in Reports wer not transferred to the local system.
What can I do?

Originally posted by @michasfer in https://github.com/abapGit/abapGit/issues/6104#issuecomment-1448345346

Ok, we tested once more like this:

new package created
one report created, with existing authorization group
all staged and pushed
checked in our internal gitea instance that the xml indeed shows a "SUCU" entry but no standalone SUCU file (was this what you meant by "generic class"? @mbtools )
deleted the package from the system but left the authorization group in place (in table TGTP)
recreated online package, pulled all objects
found that the authorization group entry is not carried over from the repository to the report properties

This time we used our internal gitea, the screenshot above however refers to an earlier test with a private repository that has since been deleted.

I checked and SUCU is for table maintenance (table TBRG_AUTH). Auth groups for programs are customizing. You can try to use a BC set or the AG data feature:

To persist the data during pull, you need the following addition:
CLASS zcl_abapgit_repo.
...
  METHOD zif_abapgit_repo~deserialize.
...
    " Deserialize data (no save to database, just test for now)
    lt_result = zcl_abapgit_data_factory=>get_deserializer( )->deserialize(
      ii_config  = get_data_config( )
      it_files   = get_files_remote( ) ).

   " Persist data
   zcl_abapgit_data_factory=>get_deserializer( )->actualize( lt_result ).   "<<< INSERT

PS: Generic class was referring to ZCL_ABAPGIT_OBJECTS_GENERIC (used by ZCL_ABAPGIT_OBJECT_SUCU)

@mbtools
Thx Marc
@AndreaBorgia-Abo
Thx Andrea for your support

@mbtools the data persistence could also be a nice addition but in this case it wasn't really need, do you think it would make sense to have it anyway?

persisting data needs some restrictions. you don't want ppl to overwrite SAP tables for example.
Something like preventing certain cases altogether and a "deserialize_check" for data with a warning popup
Discuss here: https://github.com/abapGit/abapGit/issues/3441


Unable to install

Thank you for making this project and I'm keen to try it out, but this line is preventing it from being installed:
https://github.com/u3u/fix-tsup-cjs/blob/d92b8903ea08ee7d3b243637c3b05a40059bd9f2/package.json#LL47C24-L47C34
npm ERR! command sh -c npx only-allow pnpm
npm ERR! npm ERR! code E401
npm ERR! npm ERR! Incorrect or missing password.
npm ERR! npm ERR! If you were trying to login, change your password, create an
npm ERR! npm ERR! authentication token or enable two-factor authentication then
npm ERR! npm ERR! that means you likely typed your password in incorrectly.
npm ERR! npm ERR! Please try again, or recover your password at:
npm ERR! npm ERR!     https://www.npmjs.com/forgot
npm ERR! npm ERR!
npm ERR! npm ERR! If you were doing some other operation then your saved credentials are
npm ERR! npm ERR! probably out of date. To correct this please try logging in again with:
npm ERR! npm ERR!     npm login

I believe the only way to allow npm users to use this would be to remove this lifecycle script. Or write something like pinst that rewrites it on publish.

Oh! My mistake, Can you try npx fix-tsup-cjs first?

Sorry, please try again with v1.1.1


Develop

This PR introduces a complete overhaul and redesign of free_fleet. This attempts to create multiple layers of abstractions that would accommodate different software configurations, mobile platforms and UIs, in order to be more widely used as a generic fleet management system.
The objective of this PR while development is still underway, is to have the API reviewed and modified if needed, such that further developments that use these new abstractions can be adapted without too many breaking changes.
Inspired and modeled after the fleet adapters from the RMF project, we have added these abstractions,

Middleware - Split between ClientMiddleware and ServerMiddleware, allows communication between the fleet manager and the mobile platform client. With this in place, users can implement and use their preferred middleware, for example ROS, ROS 2, different implementations of DDS, REST, MQTT or other web APIs.

Command Handle - This is used by the client to control the mobile platform, users will be able to implement this to interact with their preferred navigation stack or robot controlling API.

Status Handle - This is used by the client to gather information in order to update the fleet management system. The implementation will also be dependent on the mobile platform's API.

Other features:

Added a generalized console logging feature, which can be used throughout free_fleet, https://github.com/open-rmf/free_fleet/blob/develop/free_fleet/include/free_fleet/Console.hpp, will consider using spdlog for future iterations, https://github.com/open-rmf/free_fleet/issues/101.

Added basic Executor and Worker pattern for both the clients and managers

No dependency on ROS or ROS2, instead, any relevant implementations will be ported to free_fleet_ros1 and free_fleet_ros2, both which are under development.

This repository contains the package free_fleet_cyclonedds, which is a ready-to-use implementation of Middleware using CycloneDDS, release 0.8.0beta5, the same release version on ROS2 Galactic.

Message definitions have been pimpl-ized, https://github.com/open-rmf/free_fleet/tree/develop/free_fleet/src/messages

Also fixes:

Reactive message subscriptions - https://github.com/open-rmf/free_fleet/issues/88
Messages are generated during build - https://github.com/open-rmf/free_fleet/issues/90
Code style linting - https://github.com/open-rmf/free_fleet/issues/100

@mxgrey, thanks for the review so far! I have a much better understanding of how a reactive system can be useful in this scenario now, as well as how working towards a feature-based system would be great.
I haven't given much thought about the use of namespaces, other than using them as a way to keep things within categories or subsets (i.e. agv, transport, requests), I'll look into getting them towards component pipeline based as you mentioned. I'll develop these locally for now.
I've addressed most of the design concerns and got to implement what we have discussed previously regarding requests, I'd be keen to get your review again before any new commits. Let me know what you think.

Closing with https://github.com/open-rmf/free_fleet/pull/145


Bug: regression on icon.png loading

icon.png for a pack will not load if the name and ref are different in the pack.yaml
https://github.com/StackStorm/st2/issues/3128
https://github.com/StackStorm/st2/pull/3131
I just confirmed this in back-to-back testing.

@johnarnold Can you post the pack.yml you used in testing? I am trying to repro as well.

I can confirm that when pack name and ref are different in pack.yml, icon doesn't render. I chased it down to UI not even making calls to get the icon for the pack whose name is different from ref. I'll chase this down but it seems like a st2web problem.

https://github.com/StackStorm/st2web/blob/master/apps/st2-actions/actions.controller.js#L81
Looks like the URL we build is based on "name" and not "ref". I'll talk to @enykeev and @bigmstone who are our UI folks and figure out why we use "name" as opposed to "ref". Stay tuned.

Fix in https://github.com/StackStorm/st2web/pull/388


Grilles OP

Description
Description to Grille:

A flimsy framework of iron rods

Actual Grille:
Sure, reinforced glass can break in like 5 hits with a moderate damage source. But a "flimsy" framework of iron rods? Yeaahhhh that'd be 10+ hits eaasy without any doubt.


Update errors/warning message for cross-manifest rule

fixes #309
updated UI for validation results and replace the error tables with card (the similar errors keep concatenated).

All errors will be in error section (like wrong schema, mismatch, invalid values). All failed cross-manifest validation will be in the warning section (the users still be able to submit the manifests).
Preview

For notes: I tested with "HTAN Parent Biospecimen ID" with the four cross-manifest rules and here are the output messages from schematic.
matchAtLeast - values: Value(s) ['HTA111111_121324', 'sdsadasd'] from row(s) [2, 3] of the attribute htanparentbiospecimenid in the source manifest are missing.
matchAtLeast - set: Value(s) ['HTA111111_121324'] from row(s) [2] of the attribute htanparentbiospecimenid in the source manifest are missing. Manifest(s) ['syn24986734'] are missing the value(s).
matchExactOne - values: Value(s) [['HTA111111_121324'], ['sdsadasd']] from row(s) [2, 3] of the attribute htanparentbiospecimenid in the source manifest are not present in only one other manifest
matchExactOne - set: No matches for the values from attribute htanparentbiospecimenid in the source manifest are present in any other manifests instead of being present in exactly 1.

Merge into develop for testing and could update for languages later on.


Site Already Installed error

Just uploaded files and went to _install. Step 2 fails and it says Site Already Installed

Your site is already installed. If you want to redo a clean installation, please delete your "_constants.php" file and delete all the content of your database.

Please remove the "_constants.php" file, and try again the installer (in another browser or with incognito mode if possible to avoid any further problems)

Where is the _constants.php file?
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sat, Feb 24, 2018 at 10:05 PM, ♚ PH⑦ Soria ♛<EMAIL_ADDRESS>wrote:

Please remove the "_constants.php" file, and try again the installer (in
another browser or with incognito mode if possible to avoid any further
problems)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/174#issuecomment-368223817,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjFDa2yXYHHY1gkuSv2goVAhbSQcGicHks5tX_rsgaJpZM4SRv9X
.

There is no "_constants.php" file in the root folder.

When I try in "incognito mode" it says the following error instead:

"/storage/ssd3/113/4844113/public_html/_protected/app/configs/config.ini" is not found.

I get to the second install phase, the part where it says enter protected directory then the "Site Already Installed" error occurs.
When I go back to the root folder in the browser, it says the config error.
I assume this is because there's an issue in the install process. I've changed over all directory permissions as instructed.
Any other tips?
Or anyway to do a manual install?
Thank you very much for your assistance!

Hi again!
The error message you got only shows up if _constants.php exists. Maybe you have cache issues (from is_file() or browse).
For this reason, can you please remove the whole pH7CMS folder, re-unzip  pH7CMS zip file and make a new installation from scratch (and with a new browser session and using a new database as well).
Hope that will work!

Where is the _constants.php file? I asked that before but didn't get an answer.
I downloaded the v12 update the other day.

_constants.php file is generated once the website in installed.

Is there anyway to do a manual install? Obviously the _constants.php file doesn't exist because the website isn't installed and it's not in the directory.
Deleting all the files and trying again doesn't help either as I've tried that over and over again and receive the same result.

Manual installation is difficult to do (follow what InstallController does...).
I suggest to try with another host or with another local host environment. I see you use Windows, so the best would be to switch to another one (XAMPP, WampServer, etc)

Thanks for the reply.
That sucks... checked all server requirements and they seem to be fine. It's not a Windows server, using Linux.
All good, will go try some other dating software with better support.
Thanks for your help though.

Your screenshot was taken on Windows. Did many installations on Debian, openSUSE, CentOS and Fedora and never had any issues.

Sorry there, big mistake ! I don't use Windows ever since 2004. I have many system and there all done on either Debian Jessie, Stretch or at worst a Slackware. But you didn't get it right as like I said, the installation worked fine on my self-hosted server from home and I only got problem when I pushed the installation over onto my shared hosting. After I checked out the log, there was a security issue raised by mod_security and needed to change some option to ask apache to modify the some variables to make sure it does include the real domain name and not the shared one (the make REQUEST_URI match what a loopback would give on a machine with one IP and many different dns ie Vhost).
The screenshot was took over a Gnome 3

with standard GTK look
`

polynamaude I think the response regarding Windows was to me... yes it was a screenshot of Windows but it was the local files after unpacking the .zip, not a screenshot of the server files which appear exactly the same BEFORE the installation process.

Oh freak sorry ! I must have been more tired than I was initially thinking to have got messed up between two completely different conversation, one that I was part of and the other I was only following.
Sincere excuses


Make sure index variable comes first

Reorders variable list in Entity.__init__() so that the index variable is at the front of the list.

Codecov Report

Merging #168 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #168      +/-   ##
==========================================
+ Coverage   92.88%   92.88%   +<.01%
==========================================
  Files          70       70
  Lines        7486     7491       +5
==========================================
+ Hits         6953     6958       +5
  Misses        533      533

Impacted Files
Coverage Δ

featuretools/tests/entityset_tests/test_entity.py
100% <100%> (ø)
:arrow_up:

featuretools/entityset/entity.py
85.4% <100%> (+0.07%)
:arrow_up:

Continue to review full report at Codecov.

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

Looks good, merging


problem concerning convergence

Hi!
I try expotential and Matern 5/2 kernal for 10 variables,but do not converge or with a trend to converge after 40 iterations.
Could you give any suggestion?
How about building (sparse) GP with evaluated samples to run iteration for BO?
Will this converge?
Thank you!
Best!

That is very highly dependent on the problem. Such behavior can be happening for a ton of reasons. Maybe the objective is all bumpy, with many local minima, maybe there is no structure in the parameter space, maybe the objective is noisy. I am afraid I don't have any generic advice to give here.

What do you mean by "maybe there is no structure in the parameter space"?

That's more about the cases when you have many categorical variables. There are techniques that could be used in such cases: http://proceedings.mlr.press/v80/lu18c.html . But if the space is unstructured, you optimization essentially becomes brute force no matter what you do


Header/Footer samples on component site out of date with latest compiles CSS

Bug Report

What is the issue?

The NHS component library has sample headers and footers https://service-manual.nhs.uk/design-system/components/header
Theres are out of date with the latest 8.0.1 compiled CSS.
What steps are required to reproduce the issue?

Try the latest styles with the sample header code
What was the environment where this issue occurred?

Device: Apple M1 Pro
Operating System: Mac OS
Browser: Chrome
Browser version:
NHS.UK frontend package version: 8.0.1
Node version: N/A
npm version: N/A

Is there anything else you think would be useful in recreating the issue?

Hi Steven, thanks for submitting this issue. We are currently updating the service manual to version 6.0.0, with the release scheduled this week which will address this issue and keep the Service Manual and Frontend Library inline with each other :)

Hi Steven, I'm closing this issue as the service manual release is live here: https://github.com/nhsuk/nhsuk-service-manual/releases/tag/v6.0.0 and it's now up to date. Thanks :)


[MOD]: modify card && table by remove shadow-xl class

remove big shadow from card && table

Hi, whats the reason behind this change?

For a better user experience and user interface, I think the shadows suggest layers.
And I don't prefer having a shadow in large elements.
And the absence of shadows or a little percentage works to relax the eye and keep distractions away.
I see that the design has become cleaner after removing the big shadow

Thanks!


pull request for e2e test at 12/13/2016 19:45:02

: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.