Heroku deploy button is not work.

I try to deploy to Heroku with "Deploy to Heroku" button.
But, error has occurred.
FATAL:  permission denied for database "postgres"
DETAIL:  User does not have CONNECT privilege.
Couldn't create database for {"adapter"=>"postgresql", "username"=>"******", "password"=>"**********************", "port"=>5432, "database"=>"******", "host"=>"*******.compute-1.amazonaws.com"}
rake aborted!
PG::ConnectionBad: FATAL:  permission denied for database "postgres"
DETAIL:  User does not have CONNECT privilege.
/app/vendor/bundle/ruby/2.4.0/gems/pg-0.20.0/lib/pg.rb:56:in `initialize'
/app/vendor/bundle/ruby/2.4.0/gems/pg-0.20.0/lib/pg.rb:56:in `new'
/app/vendor/bundle/ruby/2.4.0/gems/pg-0.20.0/lib/pg.rb:56:in `connect'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/postgresql_adapter.rb:701:in `connect'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/postgresql_adapter.rb:220:in `initialize'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/postgresql_adapter.rb:38:in `new'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/postgresql_adapter.rb:38:in `postgresql_connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:759:in `new_connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:803:in `checkout_new_connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:782:in `try_to_checkout_new_connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:743:in `acquire_connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:500:in `checkout'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:374:in `connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:931:in `retrieve_connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_handling.rb:116:in `retrieve_connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/connection_handling.rb:88:in `connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/tasks/postgresql_database_tasks.rb:10:in `connection'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/tasks/postgresql_database_tasks.rb:19:in `create'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/tasks/database_tasks.rb:117:in `create'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/tasks/database_tasks.rb:137:in `block in create_current'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/tasks/database_tasks.rb:304:in `block in each_current_configuration'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/tasks/database_tasks.rb:303:in `each'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/tasks/database_tasks.rb:303:in `each_current_configuration'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/tasks/database_tasks.rb:136:in `create_current'
/app/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.1/lib/active_record/railties/databases.rake:27:in `block (2 levels) in <top (required)>'
/app/vendor/bundle/ruby/2.4.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in `load'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in `kernel_load'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:27:in `run'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:360:in `exec'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor.rb:369:in `dispatch'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:20:in `dispatch'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/base.rb:444:in `start'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:10:in `start'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:35:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
/app/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:27:in `<top (required)>'
/app/bin/bundle:3:in `load'
/app/bin/bundle:3:in `<main>'
Tasks: TOP => db:create
(See full trace by running task with --trace)

I set "ROOT_URL" only in Config Variables. Other parameter is default.
Is there any problem in potmum code? Or my environment?

Thanks report!
I fixed the problem with #28 .
Please try again :)

I successed to deploy! Thanks :pray:


Support multiple Logsene tokens

This is from https://github.com/sematext/spm-agent-docker/issues/5
If I have 2 containers, one running Apache and the other one running Elasticsearch, just for example, I may actually want to send their logs to 2 different Logsene apps.

We could use the Docker API to scan conainer labels of started container for LOGSENE_TOKEN. Users simple add --label LOGSENE_TOKEN=your_logsene_token to the Containers run command (Nginx, Elasticsearch, ...) and Sematext Docker Agent will recognize that the Logs should be routed to the specified Logsene Applications. This could be extended to additional config settings like filters (e.g. to log only errors).
Example:
  docker run --label LOGSENE_TOKEN=YOUR_ES_APP_TOKEN
  LOGSENE_FILTER="error|exception|warning" -p 9200:9200 elasticsearch
  docker run -e LOGSENE_TOKEN=YOUR_WEB_APP_TOKEN -p 80:80 nginx

Logs of containers without LOGSENE_TOKEN will be routed to the default Logsene App specified during startup of sematext/sematext-agent-docker.

There is an interesting discussion to update labels at runtime: https://github.com/docker/docker/pull/18958
Once label updates are available we could change routing to apps dynamically by changing the labels.

Done in Github master and published on Docker Hub sematext/sematext-agent-docker:dev and sematext/sematext-agent-docker:1.29.33 (build running)
After successful tests it can be published on Docker Hub with the latest tag.
This does not include LOGSENE_FILTERS (separate feature ...).

Fantastic, thanks for the quick fix. I also find this solution very good.

Thx @szakasz if you like to test, pls. let me know if you see any issue. I will run the new agent on our test server too ...

Awesome :)

Hi @megastef, I've tried to do some testing. Unfortunately, it turns out that Kubernetes and hence OpenShift 3 doesn't support labelling of the Docker containers directly (https://github.com/kubernetes/kubernetes/issues/3764). Labels are available and customizable at higher levels like pods or Services, but custom labels don't get propagated to the Docker container.
Therefore in this form we cannot test and use this new feature. Would it maybe be possible to add a similar option for Docker environment variables the same way as described in https://github.com/sematext/spm-agent-docker/issues/5#issuecomment-143657965? You could maybe first check the env var LOGSENE_TOKEN, if that's not set then the label LOGSENE_TOKEN, and finally if neither is set then use the default one specified at the Startup of SPM. What do you think?

Interesting :) - sure we can check env vars too. Give me a second ... ;) This shows the first idea is always the best one. As far I know Kubernetes is planning to use docker labels in the future (as soon labels can be updated ...).
Do you know how to query pod labels by container id with Kubernetes API?
Just curious as we are working on improvements for Kuberntes too.

Thanks for the quick reply. Unfortunately I am not such an expert with Kubernetes, but it would be definitely a very good solution, if you could grab the labels of the pod where the container sits in. I am sure this is documented somewhere.

Ok, anyhow I'm working on the environment variables. Takes a bit, as those are arrays to search instead of simple dictionaries like the labels.

Build done for sematext/sematext-agent-docker:1.29.35 and sematext/sematext-agent-docker::dev
https://hub.docker.com/r/sematext/sematext-agent-docker/builds/
docker run --label LOGSENE_TOKEN=REPLACE_WITH_YOUR_LOGSENE_TOKEN -p 80:80 nginx
# or use environment variable on Kubernetes (no support for Docker labels)
docker run -e LOGSENE_TOKEN=REPLACE_WITH_YOUR_LOGSENE_TOKEN -p 80:80 nginx

When this runs fine for a while on the test servers, we will make it latest.
On each log event a cache is checked, and if there is no entry docker inspect is triggered with label and env var search to make sure that logs don't go to the default LOGSENE_TOKEN.
The info from "docker inspect" is cached to avoid too many Docker API calls and the cache gets cleared by Docker Events. On "start" and "attach" events the check for LOGSENE_TOKEN is cached (in the hope that the token is available for the first log line arrives), on "die" event the cache entry gets removed. We have to watch if this has performance impacts for scenarios where containers live very short (start/stop) as it triggers then docker inspect calls. Tests went well so far.

sematext/sematext-docker-agent:1.29.36  is :latest on Docker Hub.
So this feature is available for all users.

Thanks, the first tests have been successful. One minor question though regarding https://github.com/sematext/sematext-agent-docker#log-routing:
What is the order of precedence when checking docker label resp. env-var LOGSENE_TOKEN? If both are defined, which is applied?

When both are defined the Label. Highest to lowest priority:

Container Label
if no Label is set, env var for app Container
else global Logsene token set for the sematext agent as env variable


Not working on a closed network

Hi,
I installed Aerial on my MAC El Capitan and I love it.
I have a weird issue, where it does not work on a restricted network at work, it take timer to get an image and then not video just an image. I don't know what the network has to do with screen saver, and I tried reinstalling and manual placing the file in the screen saver library with no luck. When I go back home, it works normal
Any thoughts?
Thanks
Ayman

hi,
the screensaver streams the videos through the web from apple servers.
it has a cache function in the latest version that downloads the videos to your computer so the saver will also work offline.
take care, the download of the videos is more than 5gb.
all this is also written in the documentation.
cheers.

Thanks,
I download the latest version, but how does it download the videos, do I let it run, do I need to trigger anything, or is it in the background.
Thanks again,
Ayman

On Nov 23, 2015, at 17:31, fletch247<EMAIL_ADDRESS>wrote:
hi,
the screensaver streams the videos through the web from apple servers.
it has a cache function in the latest version that downloads the videos to your computer so the saver will also work offline.
take care, the download of the videos is more than 5gb.
all this is also written in the documentation.
cheers.
—
Reply to this email directly or view it on GitHub.

hi, it's easy, just check out the settings of the screen saver, it's kind of self explaining.
implemented since 1.2beta4, latest is 1.2beta5.
also it's all written in the readme file.
best regards.

@aymanaltounji Did you get the screensaver working?

Yes
Ayman

On Jan 29, 2016, at 02:06, Alistair McMillan<EMAIL_ADDRESS>wrote:
@aymanaltounji Did you get the screensaver working?
—
Reply to this email directly or view it on GitHub.

Cool. Glad to hear it. :)


doc/book updated leptos version.

Recently a large number of doc issue were fixed...
When I run
cargo outdated
I see some outdated packages were being used in the doc area. So this is a minor tidy

The last fix, removed a lingering issue reported by "CLIPPY". which was not what I was going for but is nice.

Thanks! FYI I'm rewriting all the book stuff so feel free to ignore any of this, it will disappear soon.


Issue with data type that is being exported to excel

On exporting/downloading data into excel sheet, the data in excel is shown as string even though I am passing one of the field value as Number.
In below amount field, transactionAmount is of type Number but in excel I am getting this amount as String. Please find below screenshot of the amount field in excel.
Amount : "transactionAmount"

Please let me know if there is a fix for this issue ?
Thanks,
Mahesh

Hi there, I update the component to fix this issue. Sorry for the late response.


feat: verify payload scanner version & implement local i18n

fix https://github.com/NodeSecure/cli/issues/69
need review:

i18n translation
allowing deep merge in i18n package: https://github.com/NodeSecure/i18n/issues/112

I will update the i18n part later (when new version is available).


Fix citation for environmental data

My team and I have been hard at work locating new environmental data to fill in some important gaps in the current version of d-place and to correct what we perceive as limitations of the CRU TS v.3.3. data set. I am happy to announce today that we not only managed to do that, but were also able to get ahold of what we think are much better quality data sets than the ones we had (sources cited below for those that care about the details). Notably, the new variables provide FULL coverage (yes… that includes ALL societies for the info-pacific, which means no more limits on the environmental questions we ask!). Any way, attached are the data and source details. Enjoy!

A)  I’m not sure I know who to contact to update the data on D-PLACE (Simon… is that you or is it still Stephanie? Would you guys mind updating the web page with the new data? ALSO… could someone please update my lab’s web page in D-PLACE’s “team” url? It should be “https://pages.wustl.edu/botero", rather than "http://cabotero.weebly.com/“. Thanks!
B) I believe older variables with the same names as the ones provided here should no longer be distributed to avoid confusion (maybe they could be archived under something like “heritage data”?). The newer data is REALLY much better and we should discourage the use of the older one...
C) NEW DATA AND DATA SOURCES

Climate data

Annual mean, annual variance, predictability, constancy and contingency for both precipitation and temperature are now based on the “Baseline Historical (1900-1949), CCSM ecoClimate model”. The source citation is:
Lima-Ribeiro,M. et al. 2015. ecoClimate: a database of climate data from multiple models for past, present, and future for Macroecologists and Biogeographers
Biodiversity Informatics 10, 1-21. PDF
Please note that the definitions for these variables remain identical as what we currently have in D-PLACE but that the basic units for precipitation data are now grams per square meter per month. Big shout out to the folks at ecoClimate.org who kindly shared with us the raw data from their models (something that is not typically distributed to end users), allowing us to compute predictability, constancy and contingency just the way we wanted.

Physical landscape

The current version of D-PLACE includes elevation and slope data from the GTOPO30 dataset (in fact, our current slope data were computed by Rick Step and he never shared with us the exact methods he used, so I am happy to switch to something I can completely vouch for). We have taken advantage of a newer and more accurate data source for elevation: the Global Multi-resolution Terrain Elevation Data 2010 (Link here: GMTED2010), which has replaced the GTOPO30 data over the years. Please note that elevation data from GMTED2010 comes at a whopping 30 ArcSec resolution (!!!) which I use to compute initial —highly local— estimates that are then down sampled to a 0.5 by 0.5 degree resolution in order to maintain consistency with all other D-PLACE variables.
Citation: Global Multi-resolution Terrain Elevation Data courtesy of the U.S. Geological Survey (Downloaded 14 Jul 2014 from http://topotools.cr.usgs.gov/gmted_viewer/)

Update on precipitation units from Carlos 06/10/2017:
Sorry. It was simply a Freudian typo. I meant ml rather than mm. Our unit is ml/m2/month... mm (which is what one typically reports) indicates the is the amount of rain accumulated in a vessel. Whether you have a wide bucket or a narrow cylinder, you expect the same height to accumulate as long as rain falls evenly across the surface. However, the ecoclimate guys use precipitation flux instead and when you do that, you need to take into account the amount of surface that you are measuring. 2000mm is 200cm (the height of the volume of water being measured) and 1 meter is 100 centimeters (the width and length of the volume being measured) that means that 2000mm of rainfall annually corresponds to:
200cm100cm100cm = 2,000,000cubic centimeters of water falling across the meter2 per year. One cubic cm is one ml of water so our measurement of 156628ml/m2/month * 12 months =~ 1900000ml/m2/year. In other words, our estimate for the Guna is basically exactly what is expected for eastern panama. All the best,
Carlos

SO, summary:
New precipitation units: ml/m2/month
New slope units: degrees

Hi all, sorry only just saw this. Is this the new environmental data from a while ago that we have yet to update on D-PLACE? I believe the last conversation we had about this involved reformatting the data to fit with our current load scripts. I guess that never happened - I'll do it this week/weekend unless it has been done and I'm looking at an older email.

@stefelisabeth I'll take care of this. Yes, it's the data from a while ago and unfortunately it made its way online.

This looks like it was fixed last year, but that we somehow then reverted (perhaps a later commit pushed through a non-updated variable definition list, i.e., the ones flagged by @xrotwang: https://github.com/D-PLACE/dplace-data/commit/26c8b8e67f06cde2601bbca759bb8bd825213f9e#diff-77b33c2b54755ecbd98eb853e88ce1ca)

I think the fixed data just didn't make it to the website.

"New" D-PLACE has it right: http://dplace.clld.org/parameters/MonthlyMeanPrecipitation

Well, that’s good. But, aren’t both “Old D-PLACE” and “New D_PLACE” pulling from the same data repository? So, does this mean that we could simply ‘push’ all changes made to repository files since the last update of “Old D-PLACE”, and fix these problems?
Thanks again

Dunno. I never pushed anything to the production server. Ping @Bibiko
kirbykat<EMAIL_ADDRESS>schrieb am Di., 12. Juni 2018, 17:03:

Well, that’s good. But, aren’t both “Old D-PLACE” and “New D_PLACE”
pulling from the same data repository? So, does this mean that we could
simply ‘push’ all changes made to repository files since the last update of
“Old D-PLACE”, and fix these problems?
Thanks again
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/D-PLACE/dplace-data/issues/151#issuecomment-396622533,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1HKBPo0VRsni7cPattCMKDX6pnIhXtks5t79hGgaJpZM4PwLfY
.

I'll check it if I'm back in Germany this Sunday.

@Bibiko did you get a chance to check when and what data last got uploaded to the production site?

@kirbykat @Bibiko Presumably, the data online now is release 1.1 which has the wrong variable description. So I guess what we should do, is

either create a bugfix release 1.1.1, just fixing this particular problem
or create release 1.2 from the current status of the master branch in the data repos

and push the release to production.

Will be superseded by a D-PLACE 2 release.


[$500] Scan -<EMAIL_ADDRESS>only changes to Expensify after opening the message in thread

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.8-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Log in with a new account
Go to any chat
Create a Scan request using an image that will fail the scanning
After the scanning fails, click on the IOU preview twice to open IOU details page
Right click on the "scanning failed" system message > Reply in thread

Expected Result:
In Step 4, the owner of "scanning failed" system message is displayed as Expensify
Actual Result:
In Step 4, the owner of "scanning failed" system message is<EMAIL_ADDRESS>It only changes to Expensify after opening the system message in thread
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/67410c2b-baee-47b4-9f79-16ed8c8acaa6
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e866fa63ee2203e1
Upwork Job ID:<PHONE_NUMBER>650776576
Last Price Increase: 2023-12-13

Proposal
Please re-state the problem that we are trying to solve in this issue.
<EMAIL_ADDRESS>only changes to Expensify after opening the message in thread
What is the root cause of that problem?
When the account id doesn't exist getDisplayNameForParticipant will return the login/email if it can't find the account in ONYXKEYS.PERSONAL_DETAILS_LIST so the email is displayed but after opening in thread it will be included in ONYXKEYS.PERSONAL_DETAILS_LIST and Expensify will be returned as the display name and hence Expensify is displayed
What changes do you think we should make in order to solve the problem?

We make an exception for CONST.EMAIL.NOTIFICATIONS and return Expensify as displayName as we did for concierge
if (Number(accountID) === CONST.ACCOUNT_ID.NOTIFICATIONS) {
        return {
            accountID,
            displayName: 'Expensify',
            login: CONST.EMAIL.NOTIFICATIONS,
            avatar: UserUtils.getDefaultAvatar(accountID),
        };
    }

What alternative solutions did you explore? (Optional)

When I scan a receipt to a workspace and it fails, this is what I see

This seems pretty clear.

Log in with a new account

@anmurali This issue occurs when logging in a new account where the<EMAIL_ADDRESS>doesn't exist in personal details list on Onyx.

This issue occurs when logging in a new account where the<EMAIL_ADDRESS>doesn't exist in personal details list on Onyx.

@FitseTLT what would cause this to be the case? I am not sure if this is actually possible or is an edge case.

@anmurali here it is. It occurred when I signed in with a new account and created a request with receipt.

Log in with a new account

I can reproduce this on my over 6-month old account with significant amount of activity.

Screenshot of reproduction

I believe the one thing my account and a new account have in common is they both don't have the Expensify account ID in personalDetailsList, which is why I most likely was able to reproduce the issue.
@anmurali Based on your earlier comment, you probably already had the Expensify accountID in your personalDetailsList from an earlier interaction.
Here's how I found out the accountID was missing.
When inspecting the props passed to the ReportActionItemThread preview below the scan request, I noticed the Expensify avatar isn't shown, and this is because its accountID is needed to retrieve the avatar picture from personalDetailsList.

Screenshot of props

Screenshot of missing accountID

It's only after I started a reply thread with the Expensify account did the accountID get added to personalDetailsList, and the avatar and display name got updated.

Screenshot of updated personalDetailsList

That being said, I think it would be a good idea to have the Expensify accountID added to personalDetailsList right after an account is opened given, like Concierge, it also sends automated responses, unless maybe there's some other reason why it's not included there in the first place.

@eVoloshchak thoughts on this bug and @FitseTLT's proposal?

I agree with @Pujan92's comment https://github.com/Expensify/App/issues/32581#issuecomment-1845008701

How about adding this required entry in the personalDetailsList itself within the backend 'OpenApp' api response, which can avoid more custom checks in front end

While we can fix this on front end, I don't see a reason why<EMAIL_ADDRESS>contact shouldn't be added to personalDetailsList by a back end. This will also ensure we won't have to do the same fix on FE in case other service accounts are added, they can just be updated on the BE.
@anmurali, could you assign an internal engineer to this please?

I meant to get around to looking at this today but didn't get the chance. Will try to take a look at it early next week.

@blimpich - any updates here?

@anmurali not yet, I was OOO monday and then had to take a sick day yesterday. Playing catch up today.

@eVoloshchak can you clarify for me, we're trying to check for / add these personal details whenever the user opens the app? Or just when a new user is created?

@blimpich @eVoloshchak - any updates here?

@blimpich, apologies, missed the original message

can you clarify for me, we're trying to check for / add these personal details whenever the user opens the app? Or just when a new user is created?

It should be added to personal details whenever an account is created (I assume it would also be there every time user opens the app, unless we clear personal details?)

Sounds good. I don't think we clear personal details, but I also wouldn't be surprised if there is some edge case. Knowing that the main issue though is when creating a new user is helpful. Thank you 🙂

Looked into this a little bit today, its slightly difficult to reproduce on the typical Expensify engineers machine since getting smart scan setup locally is quite a pain. Will keep looking into this.

Banged my head against this today. @Beamanator it looks like you added this chunk of code so that concierge would be handled when we're looking for personal details. Do you remember if you looked into whether this should be done on the backend? All good if you don't remember, 8 months ago is a long time to remember a single block of code and why you put it where it was.
Right now I'm having a hard time figuring out where to put this in the backend. When we request personal details from the backend we do a complicated query to basically say "who does this person know" to see who's information we need, but its based off who the user is interacting with and doesn't really use any constants for Expensify service accounts, so its not clear where exactly this fix should be in the backend. I'll keep looking into this but it is a bit tricky.

Sorry for the delay @blimpich !
Hmm IIRC (of course i have a perfect memory of previous alex decisions), I added this as a safety net, because we didn't "always" have concierge details available in Onyx - but I like the plan to move this to the backend so we can remove this dumb looking check from the frontend.
Hmm and it sounds like you're looking into some more forward-thinking solution where we can hard-code future expensify account "personal details", right?
My thought would be: Maybe you could add some code near here which would manually add some "expensify bot accounts" (or whatever we wanna call them) & their personal details to the Onyx response when opening the app?

Update: put out a PR on the backend for fixing this. Waiting on feedback.

Update: PR for backend finally got merged this morning. Waiting for it to deploy. Once its deployed we can check to see if this is still an issue in production.

Adding in BZ backup when I am OOO

Still an issue in production. The personal details list now has<EMAIL_ADDRESS>in it but it doesn't have a display name so it looks the same as before. Just created a PR to give it a display name, then this should be good.

Thanks for the update @blimpich 🤞

Updated in production. Display name now works.
https://github.com/Expensify/App/assets/17171674/bdfc0ef7-d749-4c64-a765-574223628c1f

I'm going to do a bit of code cleanup on the frontend, then I will consider this done and close the issue.

Ah I forgot to close this issue. Frontend changes have been merged and a separate issue was created for paying the C+ contributor here: https://github.com/Expensify/App/issues/37190.
Since payment is handled in that issue and this issue has been resolved I'm going to close this now.


Exclude Google Drive tests of the CI

These tests make the CI spam the Google Drive API, the CI now gets banned by Google Drive very often.
I think we can just skip these tests from the CI for now.
In the future we could have a CI job that runs only once a day or once a week for such cases
cc @albertvillanova @mariosasko @severo

I was thinking exactly the same: running unit tests that request continuously a third-party API is not a good idea.


How to define the spatial distance ε for EDR and LCSS similarity algorithms?

I observe on code the eps (ε) is set to 200 for LCSS.
Let's assume a dataset with human trajectories like Geolife. I want to measure the similarity of two random trajectories from this dataset using the EDR or/and LCSS algorithm(s).
I wonder, which factors to consider in order to define the value of spatial distance threshold ε used by EDR and LCSS?
I suppose that if I use a different dataset, like Hurricanes or Animals movements, this threshold should be different as the movement pattern is different. The speed of a hurricane is different than the speed of a walking human.
Also, the sampling rate is something to take into consideration?

I think it depends on the sampling interval and the background information (for example, the width of the road for taxi tracks). Of course, your requirements are also important. The smaller EPS is, the more rigorous the distance function is and the less similar trajectories are.


release: 1.12.6

:robot: I have created a release beep boop
1.12.6 (2023-05-25)
release

1.12.6 (ed9cbf7)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/starudream/go-lib/releases/tag/v1.12.6 :sunflower:


(fix) Make plug-in loadable in mayapy by checking kLibraryApp mode

Hi,
Thanks for a great plug-in!
The plug-in initialize and uninitialize are checking for kBatch mode but are not checking for kLibraryApp mode, making it not loadable in mayapy. This pull request should fix the issue.
I found another mayapy-related issue which I could not find a solution to. I will open an issue on this.

Thanks! Sorry for my delay!


Protocol "https" not supported or disabled in libcurl

Hello Guys,
Sorry if this error does not belong here.  I am trying to install SimpleElastix with superbuild and I get the following error.   I searched for a solution and tried some of the things that had been suggested but the problem continues. I have little familiarity with Linux.
Any help?
-- downloading...
src='https://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=6e0cc6d1bdac7a4308151f9b3571b86e&name=pcre-8.37.tar.gz'
dst='/home/davood/build/PCRE-prefix/src/method=midas.bitstream.download&checksum=6e0cc6d1bdac7a4308151f9b3571b86e&name=pcre-8.37.tar.gz'
timeout='none'
error: downloading 'https://www.lua.org/ftp/lua-5.1.5.tar.gz' failed
status_code: 1
status_string: "Unsupported protocol"
log:
--- LOG BEGIN ---
Protocol "https" not supported or disabled in libcurl
Closing connection -1
--- LOG END ---error: downloading 'https://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=2d6ec8ccdf5c46b05ba54a9fd1d130d7&name=swig-1.7.0.zip' failed
status_code: 1
status_string: "Unsupported protocol"
log:
--- LOG BEGIN ---
Protocol "https" not supported or disabled in libcurl
Closing connection -1
--- LOG END ---error: downloading 'https://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=6e0cc6d1bdac7a4308151f9b3571b86e&name=pcre-8.37.tar.gz' failed
status_code: 1
status_string: "Unsupported protocol"
log:
--- LOG BEGIN ---
Protocol "https" not supported or disabled in libcurl
Closing connection -1
--- LOG END ---

Can you check if it is a network issue? Is it reproduced if you try to install on a different (e.g. home) network?

Thank you so much for the quick reply.
Unfortunately I don't think I can try it on another network.   This is a desktop computer in our lab and it's the only computer I have access to right now.

Closing since it has been long since I last run into this issue.


Move MagnifierBuilder, MagnifierOverlayInfoBearer from text_selection.dart

This PR moves the MagnifierBuilder and MagnifierOverlayInfoBearer classes from text_selection.dart to magnifier.dart where they seem to belong better. MagnifierOverlayInfoBearer. _fromRenderEditable constructor is replaced by a simple method TextSelectionOverlay. _buildMagnifier().
test-exempt: refactor only, no functional change.
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[ ] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

/cc @antholeole

I can get behind this. I considered making this change multiple times. The reason why I didn't was because I wanted everything in widgets/magnifier.dart to be text-editing agnostic, since it can lead users to think the magnifier can only be used for text editing. That being said, These methods and data classes are tightly coupled to both the magnifier and the selectionOverlay, and could easily go in both places.
cc @Renzo-Olivares what are you thoughts? I'm leaning towards approval because this is a change I was going to make myself but opted not to. If it was suggested so quickly, I probably made the wrong choice :)

I can get behind this. I considered making this change multiple times. The reason why I didn't was because I wanted everything in widgets/magnifier.dart to be text-editing agnostic, since it can lead users to think the magnifier can only be used for text editing. That being said, These methods and data classes are tightly coupled to both the magnifier and the selectionOverlay, and could easily go in both places.
cc @Renzo-Olivares what are you thoughts? I'm leaning towards approval because this is a change I was going to make myself but opted not to. If it was suggested so quickly, I probably made the wrong choice :)

I think I like these better in magnifier.dart, but I agree it could go in either. This cleans up text_selection.dart a bit. I like the use of the _buildMagnifier function vs MagnifierOverlayInfoBearer._fromRenderEditable.

On board! @tgucio do you mind cleaning up those nits? Definitely my mess leftover from my PR, sorry about that.

@antholeole sure thing - will update in a bit. Coud you also maybe add the "automerge" label?

@tgucio Could you ask @Hixie for a test-exempt on discord? Thanks

test-exempt: code refactor with no semantic change

Bad bot.
/cc @LongCatIsLooong @justinmc to see if they could take a look? (2nd review)

I somehow missed TextMagnifierConfiguration in the original change so moved this one to magnifier.dart too. @antholeole @Renzo-Olivares could you PTAL?
Also converted MagnifierOverlayInfoBearer.empty to a static const so it's a single compile time instance.

If someone could label this with "autosubmit" again that'd be great.


Add offers to sitemap

Motivation

At the moment, only pages, events and pois are included in the sitemap. Offers are missing.
Proposed Solution

Add all routes to offers to the sitemap. Create a new class OfferSitemap in sitemaps.py which inherits from WebappSitemap similar to e.g. PageSitemap.
The queryset should be:
queryset = Offer.objects.all()

which should then be filtered in the __init__()-method as follows:
self.queryset = self.queryset.filter(
    region=self.region
)

Then, add the function get_absolute_url() to the Offer model which should return the absolute url in the following form:
<region_slug>/<language_code>/offers/<offer_slug>
Please also add docstrings to all classes and methods.

Hello, I would like to contribute and solve this issue. Can you please assign it to me ?

Hey @stanislavkocan, cool! :rocket:
I updated the issue description to give more details on the proposed solution.

Thanks @timoludwig :) I would like to ask you, what should be the language_code ? If I understand correctly, offers are same in English and German version, that's why we filter only by region. It means that same offers should be in both sitemaps just with different language_code ?
Right now, I set language_code to self.region.default_language.code (that was the only way how I knew to get language), but offers appear only in "German" sitemap with code de-de.
Thank you :)

Ah sorry, I forgot about this problem. Yes, the offers are the same for different languages. But we want to include them in all sitemaps for all active languages. One example:

https://integreat.app/augsburg/de/offers/sprungbrett
https://integreat.app/augsburg/en/offers/sprungbrett

are both identical, but we need both urls in the sitemap. Clearly we can't access the required language parameter from the model, so my approach with implementing get_absolute_url() won't work. My next idea would be to add a function location() to the OfferSitemap class... if I understand the docs correctly, this is used to retrieve the urls of items before the fallback to get_absolute_url().

Ok, I will take a look.
However, does it make sense to filter it by region ?
self.queryset = self.queryset.filter(     region=self.region )
I deleted it and right now offers appear in english version too, just with language_code de-de. Now I only need to somehow implement this location you mentioned.
Correct me if I am wrong, my first issue.
Thanks

However, does it make sense to filter it by region ?

Yes, filtering by region is necessary, because offers should only appear in the region's sitemap if they are activated for that specific region. I didn't test the syntax, so maybe my suggestion doesn't work as expected, but filtering is indeed necessary. You can also give self.queryset = self.region.offers a try.

I deleted it and right now offers appear in english version too, just with language_code de-de. Now I only need to somehow implement this location you mentioned.

I'm not sure why they appear when you delete the filter, maybe you activated the offer for another region than you are requesting the sitemap? You can also push your changes to a feature branch of your fork so I can have a look at your progress if you want.

Yes, now it's clear to me. It seems like it works with location(), I will do some testing and then push.

Fixed by @stanislavkocan in #511


⚠ Bofrost.com has degraded performance

In 9be1fee, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 878 ms

Resolved: Bofrost.com performance has improved in b8829b8 after 7 minutes.


DM-34974: add note about where to put ndarray types

@ktlim : changes to our numpydoc guide requires System Architect approval. I think this change wouldn't need an RFC, but please let me know.
@nevencaplar : is this change helpful in answering your question from Slack? Here's what the built version looks like: https://developer.lsst.io/v/tickets-DM-34974-ndarray/python/numpydoc.html#array-types

Yes, I think that is a helpful change.


chore(TDI-38993): increase test coverage

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-38993
This is an extend to the current tests.
Temporary chore before splitting the module in a definition and runtime modules (WIP).
What is the new behavior?
Please check if the PR fulfills these requirements

[X] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[X] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:

Pull request test result: success :star:

Pull request test result: success :star:

Pull request test result: success :star:

Pull request test result: failure :x:

Pull request test result: success :star:

Pull request test result: success :star:


[MB -7717] Mitigate remaining staticcheck errors

Description
Fixes remaining staticcheck errors and enables staticcheck linter
Setup
pre-commit run -v --all-files golangci-lint
Expected result: You should get no errors
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Warnings

:warning:

It looks like you are attempting to bypass a linter rule, which is not within
security compliance rules.
** Contains prohibited linter override "#nosec". **
Please remove the bypass code and address the underlying issue. cc: @transcom/Truss-Pamplemoose

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against ef4cdf4d4d7f3f719eccf176f8c299464818b4b4


Switch to front domains that don't require SNI.

If a connection fails when processing an invitation, retry with
a new front domain if possible.
Workaround for https://github.com/uProxy/uproxy/issues/2619

Would be good to add a few more comments to clarify the logic and suggest future improvements, then 👍

OK, I've improved the comments based on your suggestions.


Bump max daily rule updates for enikshay

@orangejenny

@orangejenny yup, thanks - 500,000 is correct. now that we're on the new cluster going to make this 10x higher


AAD authentication error

Hello Team
I am currently trying to connect my Databricks workspace to SQL server using the connector. I am trying to use the AAD user name and password method
So far I keep getting this error  -
com.microsoft.sqlserver.jdbc.SQLServerException: Failed to authenticate the user @.com - in Active Directory (Authentication=ActiveDirectoryPassword).
the @.com is my microsoft username
So currently trying to recreate this for a support ticket I am working on. The JDBC url was taken from the SQL database connection string. (ADO.NET (Active Directory password authentication)
I have been using the code snippet provided on github
I have also made myself an active directory admin within the SQL server setting.
this is the full error i am getting
Py4JJavaError: An error occurred while calling o485.load.
: com.microsoft.sqlserver.jdbc.SQLServerException: Failed to authenticate the user "I have taken out my username " in Active Directory (Authentication=ActiveDirectoryPassword).
at com.microsoft.sqlserver.jdbc.SQLServerADAL4JUtils.getSqlFedAuthToken(SQLServerADAL4JUtils.java:62)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.getFedAuthToken(SQLServerConnection.java:4264)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.onFedAuthInfo(SQLServerConnection.java:4237)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.processFedAuthInfo(SQLServerConnection.java:4202)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onFedAuthInfo(tdsparser.java:289)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:125)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:37)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:5173)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3810)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:94)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3754)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7225)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3053)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2562)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2216)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2067)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1204)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:825)
at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.$anonfun$createConnectionFactory$1(JdbcUtils.scala:64)
at org.apache.spark.sql.execution.datasources.jdbc.JDBCRDD$.resolveTable(JDBCRDD.scala:56)
at org.apache.spark.sql.execution.datasources.jdbc.JDBCRelation$.getSchema(JDBCRelation.scala:226)
at org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:35)
at org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:370)
at org.apache.spark.sql.DataFrameReader.loadV1Source(DataFrameReader.scala:384)
at org.apache.spark.sql.DataFrameReader.$anonfun$load$2(DataFrameReader.scala:373)
at scala.Option.getOrElse(Option.scala:189)
at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:373)
at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:258)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244)
at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:380)
at py4j.Gateway.invoke(Gateway.java:295)
at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132)
at py4j.commands.CallCommand.execute(CallCommand.java:79)
at py4j.GatewayConnection.run(GatewayConnection.java:251)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.concurrent.ExecutionException: mssql_shaded.com.microsoft.aad.adal4j.AuthenticationException: {"error_description":"AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '022907d3-0f1b-48f7-badc-1ba6abab6d66'.
Trace ID: 1123399b-6832-49f7-8a60-3a38675f0801
Correlation ID: 05cb7dde-133e-427b-b118-194f90860d55
Timestamp: 2021-08-18 19:43:14Z","error":"interaction_required","error_uri":"https://login.windows.net/error?code=50076"}
at com.microsoft.sqlserver.jdbc.SQLServerADAL4JUtils.getSqlFedAuthToken(SQLServerADAL4JUtils.java:60)
... 38 more
Caused by: mssql_shaded.com.microsoft.aad.adal4j.AuthenticationException: {"error_description":"AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '022907d3-0f1b-48f7-badc-1ba6abab6d66'.
Trace ID: 1123399b-6832-49f7-8a60-3a38675f0801
Correlation ID: 05cb7dde-133e-427b-b118-194f90860d55
Timestamp: 2021-08-18 19:43:14Z","error":"interaction_required","error_uri":"https://login.windows.net/error?code=50076"}
at com.microsoft.sqlserver.jdbc.SQLServerADAL4JUtils.getSqlFedAuthToken(SQLServerADAL4JUtils.java:53)
... 38 more
Any help on this would be great
Thank you

gone through the thread in https://github.com/microsoft/sql-spark-connector/issues/26 but still no avail, also started it from scratch but nothing seems to work.

If you look at the bottom of the exception:
Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '022907d3-0f1b-48f7-badc-1ba6abab6d66'

So you are required to have an MFA-challenge, but driver does not support this. If you connect using SQL Server Management Studio, using authentication: Azure Active Directory - Universal with MFA, there will be a browser pop-up to login + MFA.
I'm also struggling with this issue at the moment...

If you look at the bottom of the exception:
Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '022907d3-0f1b-48f7-badc-1ba6abab6d66'

So you are required to have an MFA-challenge, but driver does not support this. If you connect using SQL Server Management Studio, using authentication: Azure Active Directory - Universal with MFA, there will be a browser pop-up to login + MFA.
I'm also struggling with this issue at the moment...

Hi Alex
I have managed to sort this out, you can disable MFA. I am adding it to this tread in case future users have this error. 2 ways around use the 1) Service Principle or 2)change policy

Use a Service Principal instead of a user to perform the sign-in as instructed in the Spark Connector documentation, since Service Principals are not subject to CA policies enforcement while using the Password authentication flow.
a.	How to use Service Principal for authentication: https://docs.microsoft.com/en-us/sql/connect/spark/connector?view=sql-server-ver15#python-example-with-service-principal
b.	How to create a service principal with a secret and assign it access to resources: https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#register-an-application-with-azure-ad-and-create-a-service-principal
Change the CA policy in a way to allow the authentication to work. The way you change the CA policy is up to you or your IT security team. Possible solutions that can be applied here are:
a.	Add the IP address where the Apache Spark connector is running to the trusted locations list of the CA policy: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition
b.	Exclude your user from the CA policy: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-users-groups#exclude-users
c.	Change the grant type to something else beside MFA: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-grant
For more information about CA policies and how to configure them, please follow this link: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-policies

This works for me to at least connect, it's not a durable solution (yet) since access-tokens expire after 1H by default.

Use the Azure CLI to Authenticate with MFA, for the account you want to use for the database-connection.
Generate an access_token: az account get-access-token https://database.windows.net --query accessToken -o tsv remove query /output to get some insights about this token / lifetime etc..
Connect like this (No Azure:

jdbc_df = (spark.read.format("com.microsoft.sqlserver.jdbc.spark")
              .option("url", url)
              .option("dbtable", db_table)
              .option("accessToken", access_token)
              .option("encrypt", encrypt)
              .option("databaseName", database_name)
              .option("hostNameInCertificate", host_name_in_certificate)
              .load())

Like the samples/Databricks-AzureSQL/DatabricksNotebooks/SQL Spark Connector - Python AAD Auth.py

Hi @abij
Have you tried to use the refresh token instead of the normal access token?

refreshToken does not work.
The refreshToken (valid for many days) can be used to get a new accessToken (1H valid and refresh token) without the MFA requirement.
There is a nice mechanism using MSAL (python) to renew AccessToken with local file cache, silent refresh.
https://msal-python.readthedocs.io/


Javadoc Syntax highlighting

Highlighting for Javadoc sections on a Java file is missing.
See also https://github.com/redhat-developer/vscode-java/issues/94

There's a JavaDoc textmate bundle already: https://github.com/textmate/javadoc.tmbundle/blob/master/Syntaxes/JavaDoc.tmLanguage


fix: types for useGeolocation

By default tsc was generating and object based on the initial state, where every property was always null.
This set GeoLocationSensorState the properties to their expected types, as well as defining the return type of useGeolocation.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Reorganize secondary nav links into sectioned ecosystem dropdown

I noticed the nav was starting to get a little cluttered, so I put this together as an experiment:

Pulled all ecosystem resources into the Ecosystem dropdown (including the blog and all community links).
Organized Ecosystem links into new subsections: Help, News, Core Plugins, and Resource Lists.
Improved styling of desktop and mobile dropdowns to accommodate a variety of screen dimensions.
Renamed Languages to Translations to disambiguate from programming languages.

@yyx990803 Beyond general feedback, please also let me know if it looks like the order of links doesn't make sense based on what you can tell from site analytics.

I like it. I'd love to have the headings a bit more defined though. Maybe using bold fonts or a color with more contrast.

@yyx990803 I improved it a bit and deployed. Feel free to tweak it further with your more refined eye. 🙂


Make a contributors shoutout section

Make a contributors shoutout section like the one on hackrack.in Just below the hero section make a different CSS file for it.

can you assign this to me ??

You can work on it assign it to you 👍

can you plese share the progress @rohan-b-84

this issue is open with some changes
there is a change in design

Can I work on it ?

@khushi818 work on this issue look at the design and take the code for the heading and para from the events para and heading you just have to code the avatars all the above code you can get from the events page if you have any confusion let me know

Great I will start working on it.

Hey, demonicirfan I would like to work on this issue. Can you please assign this task to me?

Is there anything I can work on with


Ui updates

This PR adds some nice visual improvements and bug fixes.

A few observations after running the UI against mock server and demo/chaincode/fpc (all rebuilt from the version in this PR):

The following buttons didn't do anything (and no visible error was shown in dev tools or alike). I assume they are all not yet implemented?  (Maybe might be useful to have somewhere a list on what is supposed to work and should be tested?): 'Auction History', 'Bid Summary', 'My results', 'Settings', 'Help'.
in auctioneer view, the order of buttons as 'create', 'endRound', 'startNextRound' seems a bit confusing; i would have expected it to be 'create', 'start', 'end'
i would assumed that either startNextRound or endRound would have increased the round number but it was always one (i have to admit, i only tested where there was a single round with a single bid which resulted in the first endround to close clocking and the following startnextround performed assignment phase and closed auction
the auction status as "closed" seems a bit confusing; gives the impression of the auction being closed rather than just bidding is not open yet.  Maybe rephrasing it as 'waiting for round to be opened' or alike would be clearer.   There also didn't seem a difference between the round being inactive and the auction actually being finished? Related to that i was not sure, though, also how i could refresh the view given that stuff happens asynchronously in the background (auto-refresh could of course also work but i don't think the app currently does it, at least i couldn't see corresponding network events)
is there currently any way to view the final results? Couldn't find it.
might be useful to have somewhere visible (and editable) the auction id?  For mock server you can easily reset the state so you can again create auction with auctionid 1 but with real fabric network this gets much more complex/lengthy?
in the transaction viewer you currently also show transaction which failed (not that this is per-se a problem for the demo, just noticed ...)

Anyway, above my notes playing with the UI a bit.  Doesn't have to be all addressed in this PR, i.e., i'm perfectly fine merging it as-is, but at least for the first question (i.e., what is supposed to work and what not) would be useful to know


Data Path Assignment by Desired CIDR

There's a case that the user may want to select the desired
data path for node2node communication by its own. But now
it seems Cilium can't support that.
This feature enhancement enables the user to set the desired
outgoing interface and its data path IP(v4) address by
a designated CIDR, which may be different from the default
which currently is just the node IP.
The usage of this feature is simply done by adding a declaration
in the installation ConfigMap of Cilium, e.g, by cilium-cli:
data-path-ipv4-cidr: "xxx.xxx.xxx.xxx/yyy"
This patch here just supports overlay tunnel mode now, which would
lead the data traffic and tunnel endpoint selection to the
matched interface IP address by the specified CIDR.
I think it's easy to be extended to direct routing mode in the future
with some more work here.
Signed-off-by: TrevorTaoARM<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Thanks for contributing!

Fixes: #issue-number
<!-- Enter the release note text here if needed or remove this section! -->

@TrevorTaoARM ping?

@TrevorTaoARM ping?

Yes.

Thanks for the contribution!
Before discussing the code, I would like to understand what are the concrete use-cases for this feature. In other words, is this a "nice to have" or is there a specific problem that it tries to solve. Can you provide a concrete example of where this would be used? Can you also explain in the example why existing configuration approaches (e.g., defining the network interface instead of a CIDR) would not work or they would have issues?

Yes, I think it's a natural way to choose a data path (network interface) by a specified CIDR.
I didn't know if there's an exitsted way to choose it by a specified network interface.
Actually it would greatly facilitate our data path selection when we have multiple data paths for an internal node2node communication but only desire 1 (or more in the future).

Thanks for the contribution!
Before discussing the code, I would like to understand what are the concrete use-cases for this feature. In other words, is this a "nice to have" or is there a specific problem that it tries to solve. Can you provide a concrete example of where this would be used? Can you also explain in the example why existing configuration approaches (e.g., defining the network interface instead of a CIDR) would not work or they would have issues?

Yes, I think it's a natural way to choose a data path (network interface) by a specified CIDR. I didn't know if there's an exitsted way to choose it by a specified network interface. Actually it would greatly facilitate our data path selection when we have multiple data paths for an internal node2node communication but only desire 1 (or more in the future).

Selecting the data path by NIC may not be a desired way as the NIC name may differ on different hosts(nodes), but a common CIDR can select the IP data path by a matched CIDR string with that of the NIC.

@TrevorTaoARM We are still trying to justify adding the flag to the agent which complicates quite a bit UX. We are wondering whether you have tried to solve the problem by using --node-ip flag in kubelet? This would set k8s Node IP which is used for tunnel endpoints.

@brb Yes, I knew the way of setting the NodeIP of the k8s, actually I had used it as a temporary solution when I need to choose a desired interface without this change.
But this solution is a little tricky here, because it's just for the communication between k8s control plane components of each node, but not for Cilium node 2 node communication between pods.
Another shortcoming of this way is that you need to set the --node-ip flag in every node of your k8s cluster, which is very bothering for a large cluster. You need to find the actual node-ip of each node you want instead of just a CIDR.

Moving to draft to remove from review & janitoring queues until the reviews are addressed or answered and the branch rebased on latest master.


Change travis

I generate the .travis.yml file with the runscript from multi-ghc-travis, just adding the tested-with property into the cabal file, as the multi-ghc-travis suggest.
I also had to change the test, so that they can run in any GHC version.

Redirect  to #14


RestKit Returns 200 response status code on cache load from 304

I was testing out the eTag code from my server using RestKti and was
happy to see that RestKit uses eTags out of the box.  However, I do
some post processing on the objects returned from RestKit that I
really don't need to do if the server returns a 304.  So in my
objectLoader:didLoadObjects: method I figured I'd implement this
little check and bail so as to save a few cycles:
RKResponse *response = objectLoader.response;
if ([response statusCode] == 304)
{
return;
}
But to my surprise the response objects statusCode comes back as 200.
I checked the trace logs and RestKit did find the 304 correctly.
2011-07-09 23:42:37.346 TSLTest[42214:207] D
restkit.network:RKResponse.m:105 NSHTTPURLResponse Status Code: 304\
Is there a reason that RestKit would tell me 200 instead of passing
through the 304?
Thanks,
Rob

I am noticing this exact same behavior.
My server is returning a 304 status code but RestKit is telling me it was a 200
Sinatra output:
localhost - "GET /api/2.0/getFakeObjects HTTP/1.1" 304 0

Client side response handler:
-(void)objectLoaderDidLoadUnexpectedResponse:(RKObjectLoader *)objectLoader{
  NSLog(@"Response: %@", [objectLoader.response bodyAsString]);
  NSLog(@"Request url: %@", objectLoader.response.request.resourcePath);
  NSLog(@"Status: %i", objectLoader.response.statusCode);
  if (objectLoader.response.statusCode == 304) {
    [delegate didReceieveUnmodifiedResponse]; //never gets called
  }
}

Console output
Response: <nil>
Request url: getFakeObjects
Status: 200

The behavior in question is due to the way RestKit uses its cache.  If an an RKObjectLoader receives a response with 304 status, The response is actually loaded from RestKit's cache.  The 304 response is released and set to nil and the old response is re-constructed with the original status code.
If you do not want RestKit to use the cached response you can set the cache policy on the client like this rkObjectManager.client.cachePolicy = RKRequestCachePolicyNone;.  This will cause RestKit to continue mapping the response object as normal and the response status code will be the same.
An alternate solution would be to have a separate delegate method for cached responses so you could do this:
-(void)objectLoader:(RKObjectLoader *) didLoadCachedResponse:(RKResponse *)response{
  //my cached response handler method here
}

This issue is pretty old, so I'm assuming it isn't getting any attention.  Does anyone think a solution like this would be worthwhile?

There is a boolean property on the RKResponse called wasLoadedFromCache that will return YES on a cached response load for a 304. There is the issue that you can't necessarily tell why a particular cached response was loaded -- only that it was. Some additional transparency via properties on the response makes more sense to me than additional delegates.


Get DT properties

Created by: @bayegan Apr 08 2022 at 00:47 CET
Last updated: Jul 19 2022 at 14:13 CET
ClickUp ID: IK-2646
Given
I am a python SDK user
When
When I want to get DT properties
Then
I have an API in the SDK available. The API implement respective functionality as Node SDK and has 95% unit test coverage.

Commented by: @bayegan Apr 08 2022 at 00:48 CET
cc @bradtumy


Manual (and automatic) backup doesn't work (Unfortunately, SMS Backup+ has stopped)

I'm having this issue for a while now. Each time I hit the BACKUP button the application crashes and a message pops up on screen "Unfortunately, SMS Backup+ has stopped"
The same happens each time an automatic backup is triggered (the message pops up on screen).
Expected behaviour
I tap on the BACKUP button, the application shows the messages: "Working, logging in...", then "Working, calculating...", and then backs up any non backed up messages and call logs without crashing.
Actual behaviour
I tap on the BACKUP button, the application shows the messages: "Working, logging in...", then "Working, calculating...", and then the application closes completely, living me on the home screen with the message "Unfortunately, SMS Backup+ has stopped"
Steps to reproduce the behaviour

Open the app
(If you haven't connected your GMail account, do so)
Tap the BACKUP button

Specifications:

Android version: 6.0
Phone model / brand: Studio XL 2/BLU
SMS Backup+ version installed: 1.5.11-beta18
Messaging app: Messages (version 3.0.040) (com.google.android.apps.messaging)

I have compiled from source and I have run the application in debug mode to find out where is the application crashing, it seems it crashes on the first call to:
com/zegoggles/smssync/mail/PersonLookup.java:51 Cursor c = mResolver.query(personUri, PHONE_PROJECTION, null, null, null);
with call stack:
E/AndroidRuntime: FATAL EXCEPTION: AsyncTask #1
                  Process: com.zegoggles.smssync, PID: 26993
                  java.lang.RuntimeException: An error occurred while executing doInBackground()
                      at android.os.AsyncTask$3.done(AsyncTask.java:309)
                      at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
                      at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
                      at java.util.concurrent.FutureTask.run(FutureTask.java:242)
                      at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
                      at java.lang.Thread.run(Thread.java:818)
                   Caused by: java.lang.IllegalArgumentException: column 'data1' does not exist
                      at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:170)
                      at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:140)
                      at android.content.ContentProviderProxy.query(ContentProviderNative.java:421)
                      at android.content.ContentResolver.query(ContentResolver.java:498)
                      at android.content.ContentResolver.query(ContentResolver.java:441)
                      at com.zegoggles.smssync.mail.PersonLookup.lookupPerson(PersonLookup.java:51)
                      at com.zegoggles.smssync.mail.MessageGenerator.messageFromMapSms(MessageGenerator.java:83)
                      at com.zegoggles.smssync.mail.MessageGenerator.messageForDataType(MessageGenerator.java:72)
                      at com.zegoggles.smssync.mail.MessageConverter.convertMessages(MessageConverter.java:115)
                      at com.zegoggles.smssync.service.BackupTask.backupCursors(BackupTask.java:269)
                      at com.zegoggles.smssync.service.BackupTask.fetchAndBackupItems(BackupTask.java:153)
                      at com.zegoggles.smssync.service.BackupTask.acquireLocksAndBackup(BackupTask.java:133)
                      at com.zegoggles.smssync.service.BackupTask.doInBackground(BackupTask.java:126)
                      at com.zegoggles.smssync.service.BackupTask.doInBackground(BackupTask.java:49)
                      at android.os.AsyncTask$2.call(AsyncTask.java:295)
                      at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                      at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
                      at java.lang.Thread.run(Thread.java:818)
E/Surface: getSlotFromBufferLocked: unknown buffer: 0xab5c2b40

thanks, that is a weird bug. maybe some numbers are stored in a different table? i'll see if there's a better fix for this, if not we can just the try/catch solution.


Creating resources from YAML in a non-default namespace errors

The issue was originally recorded in their UI ticket, but the actual bug is a backend issue.
The UI ticket is rancher/rancher#1745 in /rancher/dashboard
(https://github.com/rancher/dashboard/issues/1745)
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
https://github.com/rancher/dashboard/issues/1745#issuecomment-783765215
also see https://github.com/rancher/dashboard/issues/1745#issuecomment-783767887

Confirmed this fix was indeed a ui fix - will be closing this one as a duplicate and re-open the UI issue for testing.


Refactored object inspec checks

@jjasghar  Can I get a quick merge/check on this PR? its refactoring the checks so that we can skip the files that dont exist on our system

@jjasghar Can you merge it today when you get the time? thanks!

As of this morning I've enforcing the DCO for this repo.
With our new policy please use the DCO signing process.

Or if you want a more perminant option the following is a way to set it forever:
$ git config commit.gpgsign true

Can you update your commit with this please?

@jjasghar  sure ill do it right away

@jjasghar does that look good?

thanks! 🤘


[xy-chart] add circle packing constraint to keep circles within the width of the chart

closed by #91


Add compression for the index format

For files with very large compression ratios, the index might actually grow larger than the original file because the seek points are 32 KiB of uncompressed data for each chunk (every 4 MiB per default). I.e., for compression ratios >128, the seek points take up as much as the original file. However, in these cases, the seek points would also compress very well even without back-references to the previous data. Therefore, compression should be done. There could be:

Compression of the whole index file: Probably not advisable because it would make #10 impossible.
Compression of each seek point: Compression might not be optimal but should be sufficient, especially the Huffman-Coding should help.
Compression bunches of seek points, e.g., bunches of 10: More complex to implement.

This would make resuming decompression more difficult. If each window is compressed independently, then we could simply prepend the compressed window in front of the actual compressed chunk data and then we could simply skip the first window size amount of decompressed bytes. This feels almost trivial to implement.
In tests with wikidata.json, it didn't improve compression significantly, less than 1%. So for now, don't do this.

Other unrelated compression:

Shave off bytes by analyzing what is actually referenced in the coming data. It is very likely, that the very next back-reference will not reference the data 32 KiB back, i.e., the start of the window.

The farthest distance alone is often up to 90% of the window, and therefore doesn't help compression much but see below.

In combination with compression, we might go even further and replace unused values in the window with zero in order to increase the compressibility. However, keeping track of which values are used and which aren't, would become more expensive.

For wikidata.json only ~15% of the symbols in the window are actually referenced. However, after compression, this pruning of the other 85% "only" improves the compressed output by a bit more than 2x., compression itself, yields ~8x reduction in size.
For 4GiB-base.gz, this pruning shaves off much more even after compression, because the windows don't compress well. In total, the index is now ~ 400 kB instead of 25 MB.

All of these optimizations would make the format incompatible with that of indexed_gzip. This is problematic, especially in combination with ratarmount, which currently stores indexes in the indexed_gzip format. However, the shaving off of bytes could be implemented by simply replacing them with zeros in order to make them compress more easily! Then, ratarmount could implement a compression for the whole index file or even in chunks and provide a Python file object abstraction to rapidgzip when #10 has been implemented. This would preserve the compatibility of ratarmount indexes agnostic of the backend (indexed_gzip, rapidgzip) when implemented correctly.
Still, for standalone use, the compression per seek point would still be useful.

Format Outline:
Index Format Outline:

 - Magic Bytes: Don't have to be super short, it's negligible compared to a window anyway.
 - Format Version
 - Flags
   - Offset Format:
     - Continous: Encoded chunk size is given by the distance to the next chunk. This is true for the decompressed size anyway
     - Patches: Chunks are stored as (decompressed offset, encoded offset, encoded size, window offset) tuples.
                Note that this means that in general encoded patches could be overlapping.
                For zip, this is used for zip bombs. Therefore it might be forbidden in the future,
                although I don't see why it should. This index format isn't meant for extracting to disk
                anyway, so a decompression bomb like this would only affect runtime, which seems ok to me
                because rapidgzip is meant for multi-gigabyte or even multi-terabyte files anyway.
                It is meant to support, e.g., making all the files inside a zip file accessible as a single
                seekable file object.
     - Continuous without windows: Intended for bzip2 index files
     - Patches without windows:
       -> maybe instead of a weird enum, use flags to enable encoded size and window offset tuple members
       -> same for CRC32 checksum
         -> Use enum for checknum instead: None, CRC32, Adler, SHA?...
         -> Store size of checksum member so that unknown checksums can simply be ignored.
            Else, we wouldn't know how long a member in the chunk database is
     - Flag whether chunks are sorted. Could be helpful to enable bisection search based on the encoded offset,
       for whatever reason. Else, kinda like a checksum
     - Flag whether windows are sorted? Not sure why that could be wanted.
       To decide whether access would be random or not? Simply as a checksum, i.e., if they are not actually sorted, then error out.
   - Window Compression:
     The windows should either be not compressed or compressed with the same algorithm as the accompanied archive.
     This is for dependency reasons. Decoders who only want to use this for LZ4 files should not be required to
     support all possible compression schemes.
     - None
     - Deflate
     - gzip (in contrast to Deflate this effects that the windows are also checksummed)
     - Deflate + Shared Dictionary (?)
     - LZ4
     - ZSTD
     - bzip2
 - Compressed File Size
 - Decompressed File Size
 - Number of Chunks
 - Chunk offsets / size list in the format according to "Offset Format". Must be sorted by decoded offset.
   All offsets should be unsigned 64-bit.
   The encoded size probably could be 32-bit but who knows, simply be safe and make it 64-bit
   Each entry should be fixed size in order to theoretically facilitate bisection search instead of
   having to read all entries.
   - (decoded offset, encoded offset, encoded size, window offset, window size?, CRC32 checksum for this chunk!)
   - (decoded offset, encoded offset, encoded size, window offset, window size?, CRC32 checksum for this chunk!)
   - ...
 - Windows: Raw concatenated windows of varying size. In order to get the required window in O(1), offsets into
            this stream are also stored with the chunk offsets. Because of that window offset, these windows
            could be ordered randomly or windows might even be reused by different chunks. This is allowed,
            although I suspect that the usual case would be one window per chunk and windows are in the same
            order as the chunks.
            Note that
   - Window 1:
     -
     - Size of this window block to facilitate jumping to the next window
       Theoretically, the window offsets above would suffice. Therefore, this is more a
   - Window 2
   - ...

General Notes:

 - All multi-byte numbers in the format described here are stored with
   the least-significant byte first (at the lower memory address).
 - encoded/compressed offsets and sizes are always in bits, decompressed in bytes

Kinda fixed with gztool index format support. There still might be yet another index format that works cross-compression and fixes some small issues with gztool indexes.


Deconvolution layer support

+1

+1

+1

+1

+1

+1

+1

+1

+1

I think someone has already took care of this:
https://github.com/philkuz/caffe-tensorflow


how to handle two event handlers of wifi

we are working on sntp and  mqtt examples together, but we are getting evnt handler implicit declaration, so can someone how to use two different event in that handler function.

In file included from /home/user/esp32/esp-idf/esp-mqtt-master/oTA_WITH_sub_pub/main/./main.c:94:0:
/home/user/esp32/esp-idf/esp-mqtt-master/main/./mqtt_wifi.h:80:18: error: redefinition of 'event_handler'
static esp_err_t event_handler(void *ctx, system_event_t *event) {
^
In file included from /home/user/esp32/esp-idf/esp-mqtt-master/main/./main.c:93:0:
/home/user/esp32/esp-idf/esp-mqtt-master/oTA_WITH_sub_pub/main/./ota.h:45:18: note: previous definition of 'event_handler' was here
static esp_err_t event_handler(void *ctx, system_event_t *event)
^
make[1]: *** [main.o] Error 1
make: *** [main-build] Error 2

When you write an ESP-IDF application that uses WiFi, it is your responsibility to write an event handler which is invoked when important lifecycle events occur relating to WiFi.  If you have logic that you want executed when an event occurs, you must merge the execution of that logic into your handler.  If you have two sample applications that perform different work items when a WiFi event arrives, you must manually merge the code (or chain the handlers together) to achieve the task.  You can't register multiple handlers in ESP-IDF.

Hi @jaggi , did the above suggestion help you resolve the issue?

I tried handling the WiFi events with two handlers, one handler where actual logic is written and the second with only the occurrence of the event is printed. It works in this way. I believe as long as you don't place the same logic in both handlers, you are good to go.


[WIP] Implement iOS one-click deploy.

Implements onc-click deploy to iOS simulators (via xcode xcrun simctl) and devices (via third-party tool - ios-deploy).
https://streamable.com/zqca9
ios-deploy part needs testing, I do not have any iDevices to test it on real hardware.
There's already PR for the same thing but it only supports real devices via ios-deploy: #11765
Fixes: #2703

Implements onc-click deploy to iOS simulators (via xcode xcrun simctl)

That reminds me, do the official iOS export templates contain x86 binaries for use with the Simulator?

That reminds me, do the official iOS export templates contain x86 binaries for use with the Simulator?

Yes:
3.1.1 templates have i386, armv7, x86_64, arm64 libs.
3.2 alpha 3 templates have x86_64, arm64 libs.

That reminds me, do the official iOS export templates contain x86 binaries for use with the Simulator?

XS/XR+ iPhones use ARMv8.3 CPUs (arm64e), probably we should add this to officeal template as well, but AFAIK it's optional and normal arm64 libs should work on new devices too. (#26267)

Slightly related but I also found this repo that tries to do the same thing, might be helpful as a reference.
https://github.com/PrestonKnopp/godot-ios-deploy

I gave this a whirl with my iphone 7, and ipod touch, it works really well so far.

This works in the simulator but not on the device for me. @Relintai can you confirm this works from a mac to a device and without using the simulator?

It did work for me. As I said I tried it with my real iPhone 7, and my iPod touch (5th gen). It worked flawlessly with both of them, every single time, also with multiple projects.
Something might have changed since then though, because for example now ios-deploy says to uninstall the npm version (commit from yesterday), and I had the npm version.
I'll clean rebuild, update everything on my mac and test again in a few days.

This is too outdated and need to be redone.


Changes to specify Validator configuration in a web service call

Modified RedPen web server and core to support passing configuration settings with the validation request JSON
Added new JSON-based validate API call that permits the specification of the language, parser, output format, the enabled validators and their configurations.
Updated the web GUI to sub-impose the validators under the editor to provide space to add the editable properties
Added extra tab to show the JSON request’s content
Implemented server-side processing of JSON configuration and creation of redpen instance
Updated GUI to send edited properties along with each validate request
Fixed bug with line number calculation for multiple blank lines in PlainTextParser
Corrected highlighting and positioning of errors displayed in editor
Cleaned up GUI to make it more suitable for presentations

Coverage decreased (-0.3%) to 80.42% when pulling e461fb61707d77fd98c10bdcafba261bcb70cbdd on gerryhocks:master into 813be48f62dded4070381e41d0de3b0e0400b831 on recruit-tech:master.

:+1:

Excellent work @gerryhocks! I will merge after I understand the changes. Hopeufully tomorrow..

No problem! Let me know if there are any issues.

Thank you a lot as always!


Request : add internal temperature sensor x Smart Heater

Which model is this? Need the Hxxxx number.

H713A

Which type of device is this? Light, heater, leak sensor, etc.

Smart Heater

Which connection methods does this device have? Wifi? Bluetooth? LAN mode? All?

All

Anything else?

Hi. Whit this plug-in, is not possibile add temperature sensors of this device. Thank you. Best Regards

news ?


Less dramatic outcome for Errno::ETIMEDOUT case.

Adjusts/replaces #61 and closes #62.
@halorgium, I believe this is a good way to handle Errno::ETIMEDOUT gracefully -- return how much was written, rather than passing along a "crash" ... This might be flawed reasoning however.
Please consider: If it is necessary to be sure something crossed the wire, the upstream needs to check total_written is valid. But for those who don't care about the outcome per se, there is no exception raised to take out an actor.
My thought is that an actor's life can be spared, and whatever ought to run after a response is written can be run. For example, I save state and do some per-connection cleanup which a termination is not. Whether the transfer was correct is the responsibility of upstream code, if high accuracy is needed, but for the majority of cases, accuracy is optional.

This is old. Can we please review and close if no longer useful?

I'm concerned that this behaviour wouldn't allow the user to handle the case explicitly. I think this is something we should revisit in the future, but for now I'm going to close this PR.

Agreed, will re-raise in future if needed. But will probably implement a different "dynamic rescue" allowing injection of specialized rescues if needed.


Warn about unrecognized pkg.json options

Warn about unrecognized pkg.json options
...because there's a good possibility it's a mistake.

done


Implement Unit Tests

Initial outline of complete unit test coverage with partial implementation

build_tests are fixed by this PR, but fail because they run on PR to dev, so automation runs the automation from the dev branch

Needs updated ovos_utils https://github.com/OpenVoiceOS/ovos-utils/pull/143

Relates to https://github.com/NeonGeckoCom/NeonCore/issues/424


ci: allow renovate[bot] for PR in this repo as well

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


[BEAM-1218] Moving dataflow runner related code to vendor directory

R: @sb2nov

LGTM if jenkins is happy.

Coverage decreased (-0.003%) to 69.274% when pulling bf336d08951d7d6aaead23f9fa3968ffe9703863 on aaltay:beam into 9151676a53e74a330773f7bfdb82dd7ed16640df on apache:master.

Thank you. jenkins pre-commit test is green, I will merge this.


Set column and row index to one

When adding a comment to a xlsx sheet the process panics due to the index currently starting at 0 by default. This doesn't work as indices start at 1 in the sheet, so it makes sense to adjust the default value.

hi. tomgroenwoldt
Thank you for the PR.
Excellent suggestion.
We will merge them.

Thanks for the quick response. This is an awesome crate! :)


Pipeline fails with `fetch': key not found: "FilePath" (KeyError)

Describe the bug
After latest update to <IP_ADDRESS>1 all our DevOps pipelines are failing with the following error message:
/home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/dependabot-nuget-0.263.0/lib/dependabot/nuget/discovery/workspace_discovery.rb:16:in `fetch': key not found: "FilePath" (KeyError)
This is the full stack of the error:
/home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/dependabot-nuget-0.263.0/lib/dependabot/nuget/discovery/workspace_discovery.rb:16:in fetch': key not found: "FilePath" (KeyError) 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/dependabot-nuget-0.263.0/lib/dependabot/nuget/discovery/workspace_discovery.rb:16:in from_json'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in bind_call' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in validate_call'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/_methods.rb:277:in block in _on_method_added' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/dependabot-nuget-0.263.0/lib/dependabot/nuget/discovery/discovery_json_reader.rb:69:in workspace_discovery'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in bind_call' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in validate_call'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/_methods.rb:277:in block in _on_method_added' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/dependabot-nuget-0.263.0/lib/dependabot/nuget/discovery/discovery_json_reader.rb:46:in dependency_set'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in bind_call' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in validate_call'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/_methods.rb:277:in block in _on_method_added' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/dependabot-nuget-0.263.0/lib/dependabot/nuget/file_parser.rb:51:in discovered_dependencies'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in bind_call' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in validate_call'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/_methods.rb:277:in block in _on_method_added' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/dependabot-nuget-0.263.0/lib/dependabot/nuget/file_parser.rb:34:in parse'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in bind_call' 	from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/call_validation.rb:270:in validate_call'
from /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/sorbet-runtime-0.5.11463/lib/types/private/methods/_methods.rb:277:in block in _on_method_added' 	from bin/update_script.rb:531:in '
##[error]The process '/usr/bin/docker' failed with exit code 1
Everything was working fine with version <IP_ADDRESS>7
To Reproduce
We are just running the pipeline. I'm attaching the pipeline definition (azure-pipelines-dependabot.yml) and the dependabot configuration (dependabot.yml)
Expected behavior
Dependabot pipeline should not throw any errors
Extension (please complete the following information):

Host: Azure DevOps
Version <IP_ADDRESS>1

Server (please complete the following information):

Region: Central US
Version: -unknnown

dependabot-configuration.zip

I'm getting this error on a fresh build too, even on 1.29.3 and earlier versions of the updater.
It seems that https://github.com/dependabot/dependabot-core/pull/10025 changed the native NuGet helpers in dependabot core 0.264 and because of this all builds of this project now use the new tools due to the way the docker images are built.
https://github.com/tinglesoftware/dependabot-azure-devops/blob/4fc47639abc6509e749c1e4ddfca1cb6459ebf99/updater/Dockerfile#L1-L4
I think the eaiest fix is to update the Rubygems to 0.264 so they match again. The long term fix is to try find a solution to that TODO comment.

Thank you very much for looking into this and for the quick answer!

We had the same problem, but it seems to be fixed now in 1.29.5.
Thank you.


Update README.md

@sbtaylor15 I think I need to get a PR fix in for our scans. I will try to do that this week.


Initial support for USB composite device HID and CDC.

Enable CDC so Pico-CEC appears as a connectable serial TTY device with baud rate 115200.
Add tcli v0.2.5 as submodule.
Add basic example CLI support via tcli for:

reboot [bootsel]

"reboot" -> reboot system
"reboot bootsel" -> reboot into bootloader

version

display version

I've finally worked out the right combination of USB enumerations to get composite USB HID and CDC.
This allows pico-cec to operate as both the original HID keyboard and a CDC serial console.
After some exploration, I have settled on tcli as the command line framework.
On my workstation, with any terminal emulator, I can connect to /dev/ttyACM0 at baud 115200 to interact with the system.


stream creation: Automatically mark initial messages as read for creator.

The current stream creation flow feels very spammy, especially when you're setting up a new Zulip realm, due to the 1-2 messages/stream sent at stream creation. These messages are sent in add_subscriptions_backend; grep for internal_prep_stream_message.
We should automatically mark those two messages as read for the stream creator.

@zulipbot claim


simplify docs structure

[ ] simplify further (move maintenance applications to applications, etc.)
[ ] make sure everything that should be excluded is excluded
[ ] check for duplicate files (CODE_OF_CONDUCT.md)
[ ] check links

 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.

@semuelle feel free to merge it, if you think it's ready


NullPointerException at: ZUGFeRDExporter.PDFattachZugferdFile(this)

Hello,
I copied the MustangWriter example form the project. I just changed the input and the output filename and the path to the files. When the program tries to attach the Zugferd file by calling .PDFattachZugferdFile(this), I get the following NullPointerException:
Exception in thread "main" java.lang.NullPointerException
	at org.mustangproject.ZUGFeRD.ZUGFeRDTransactionModelConverter.getPaymentData(ZUGFeRDTransactionModelConverter.java:454)
	at org.mustangproject.ZUGFeRD.ZUGFeRDTransactionModelConverter.getTradeSettlement(ZUGFeRDTransactionModelConverter.java:429)
	at org.mustangproject.ZUGFeRD.ZUGFeRDTransactionModelConverter.getTradeTransaction(ZUGFeRDTransactionModelConverter.java:187)
	at org.mustangproject.ZUGFeRD.ZUGFeRDTransactionModelConverter.convertToModel(ZUGFeRDTransactionModelConverter.java:103)
	at org.mustangproject.ZUGFeRD.ZUGFeRD1PullProvider.createZugferdXMLForTransaction(ZUGFeRD1PullProvider.java:77)
	at org.mustangproject.ZUGFeRD.ZUGFeRD1PullProvider.generateXML(ZUGFeRD1PullProvider.java:104)
	at org.mustangproject.ZUGFeRD.ZUGFeRDExporter.PDFattachZugferdFile(ZUGFeRDExporter.java:393)
	at MustangWriter.apply(MustangWriter.java:270)
	at MustangWriter.main(MustangWriter.java:283)

A similar error occurred in january.
I also tried to attach custom XML which works just fine.

did you try the corrected sample I had mentioned on 14 jan?

Yes, I tried the newest sample. also using mustang-1.7.8.jar

hi, tweimer just submitted a patch for mustang 2 on https://github.com/ZUGFeRD/mustangproject/pull/204 does that help?

Seems to be the same NullPointerException as in #165


Improving command line parsing

Currently we use http://ezoptionparser.sourceforge.net for command line arguments. This leads to large number of global options :
/path/to/isntall/directory/coreneuron_exec --help
-b, --spikebuf ARG          Spike buffer size. (100000)
-c, --threading             Parallel threads. The default is serial threads.
-d, --datpath ARG           Path containing CoreNeuron data files. (.)
-dt, --dt ARG               Fixed time step. The default value is set by
                            defaults.dat or is 0.025.
-e, --tstop ARG             Stop time (ms). (100)
-f, --filesdat ARG          Name for the distribution file. (files.dat)
-g, --prcellgid ARG         Output prcellstate information for the gid NUMBER.
-gpu, --gpu                 Enable use of GPUs. The default implies cpu only
                            run.
-h, --help                  Print a usage message briefly summarizing these
                            command-line options, then exit.
-k, --forwardskip ARG       Forwardskip to TIME
-l, --celsius ARG           Temperature in degC. The default value is set in
                            defaults.dat or else is 34.0.
-mpi                        Enable MPI. In order to initialize MPI environment
                            this argument must be specified.
-o, --outpath ARG           Path to place output data files. (.)
-p, --pattern ARG           Apply patternstim using the specified spike file.
-R, --cell-permute ARG      Cell permutation, 0 No; 1 optimise node adjacency; 2
                            optimize parent adjacency. (1)
-s, --seed ARG              Initialization seed for random number generator
                            (int).
-v, --voltage ARG           Initial voltage used for nrn_finitialize(1, v_init).
                            If 1000, then nrn_finitialize(0,...). (-65.)
-W, --nwarp ARG             Number of warps to balance. (0)
-x, --extracon ARG          Number of extra random connections in each thread to
                            other duplicate models (int).
--binqueue                  Use bin queue.
--checkpoint ARG            Enable checkpoint and specify directory to store
                            related files.
--mindelay ARG              Maximum integration interval (likely reduced by
                            minimum NetCon delay). (10)
--ms-phases ARG             Number of multisend phases, 1 or 2. (2)
--ms-subintervals ARG       Number of multisend subintervals, 1 or 2. (2)
--multisend                 Use Multisend spike exchange instead of Allgather.
--read-config ARG           Read configuration file filename.
--restore ARG               Restore simulation from provided checkpoint
                            directory.
--show                      Print args.
--skip-mpi-finalize         Do not call mpi finalize.
--spkcompress ARG           Spike compression. Up to ARG are exchanged during
                            MPI_Allgather. (0)
--write-config ARG          Write configuration file filename.

May be this can be improved with : https://github.com/CLIUtils/CLI11 ?

Hi @st4rl3ss, if you are working on this let me know, otherwise I will PR.

Hello! Actually it should be already implemented in the CLI11 branch, I was waiting for a review from @pramodk before proceeding with the PR.

CLI11 Implementation rebased and available in the CLI11 branch.

@st4rl3ss : could you open PR with that?

I think we can close this now :)