Locative/581 (support for older phone)

With the change of FFM and then the loss of Life360, I'm on the hunt for a new platform to perform geospacial automation and track my horde of kids.  Problem, 4 of them are using older iPhone 6s that are maxed at iOS 12.5.7 and therefore run an older version of Locative.
The "Send Test-Request" is successful.... but I'm getting errors on entry and exits of geofences.  To make it even more fun, the older version doensn't have an option to (Trigger "Enter" Event) or exit.  So, to test, I'm driving around town with a pocket full of iPhones.
Attached is the debug log of an entry and exit by one of the iPhone 6s.  (Note: all my iPhones get bumped up a year when they appear in the log... The 6s shows up as a 7, the 7 shows up as an 8.  The X shows up as an 11 and the 13s show up as 14s.
Side thought.... I'm also looking at the "OwnTracks" app.  I can get your plugin to see it, but the format I guess is off.  That app is a (IMO) better alternative to Life360.  It does geofences (Regions) and you can track friends, but there is also a decent API publicly available for it.  I've only tinkered with that app, not worth it if I can't get it automated.
Last side comment.  I can't think of a case use, but I was trying to create a iOS Shortcut to populate as a Custom device in your plugin.  I couldn't get the setting right.... but I think I was close.  <- Just something to mess around with.
Geobeacon Debug.txt

Looks like the older versions of Locative do not include a content-type header.  I'll need to look at the code and see how critical that is.  There's error checking in there now to abort if it's not there, but I don't know if there's a work-around.

Try https://github.com/FlyingDiver/Indigo-GeoFence/releases/tag/2022.1.5

Thankyou.  I’ll know how it’s going in a couple hours when the kids get out of school and the notifications start rolling in.
Respectfully,
Bill Moore
@.***
832-294-3096

On Jan 11, 2024, at 11:22 AM, Joe Keenan @.***> wrote:
Try https://github.com/FlyingDiver/Indigo-GeoFence/releases/tag/2022.1.5
—
Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-GeoFence/issues/5#issuecomment-1887618813, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF2IS3THZRGTQYPLV4FEWF3YOANUHAVCNFSM6AAAAABBVXACKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBXGYYTQOBRGM.
You are receiving this because you authored the thread.

Closer, but error 'key body_params not found in dict'  Debug log attached.
Debug Geofence body_params.txt

Turn on debug logging.  I need to see the actual content you're getting.

This?
Here is an exit and enter log:
GeoFence Debug                  reflector_handler: se.furtenbach.indigo.plugin.beacon : (dict)
file_path : (list)
headers : (dict)
accept : / (string)
accept-encoding : br, gzip, deflate (string)
accept-language : en-us (string)
connection : close (string)
host : localhost:14876 (string)
user-agent : Locative/581 CFNetwork/978.0.7 Darwin/18.7.0 (string)
x-forwarded-for : <IP_ADDRESS> (string)
x-forwarded-host : redact.indigodomo.net (string)
x-forwarded-server : somereflectorhere.indigodomo.net (string)
incoming_request_method : GET (string)
url_query_args : (dict)
api_key : redact (string)
device : C6B2F9D7-F43F-45A1-A7F0-8484C2ADB0E4 (string)
device_model : iPhone7,2 (string)
device_type : iOS (string)
id : ISL (string)
latitude : 29.4948942979611 (string)
longitude : -95.17218354777557 (string)
timestamp :<PHONE_NUMBER>.737016 (string)
trigger : exit (string)
GeoFence Debug                  No content-type header found
GeoFence Debug                  user-agent: Locative/581 CFNetwork/978.0.7 Darwin/18.7.0, content-type: None
GeoFence Debug                  Recognised Locative/Geofancy
GeoFence Warning                Recognised Locative/Geofancy, error parsing data: 'key body_params not found in dict'
GeoFence Debug                  reflector_handler: se.furtenbach.indigo.plugin.beacon : (dict)
file_path : (list)
headers : (dict)
accept : / (string)
accept-encoding : br, gzip, deflate (string)
accept-language : en-us (string)
connection : close (string)
host : localhost:14876 (string)
user-agent : Locative/581 CFNetwork/978.0.7 Darwin/18.7.0 (string)
x-forwarded-for : <IP_ADDRESS> (string)
x-forwarded-host : redact.indigodomo.net (string)
x-forwarded-server : somereflectorhere.indigodomo.net (string)
incoming_request_method : GET (string)
url_query_args : (dict)
api_key : redact (string)
device : C6B2F9D7-F43F-45A1-A7F0-8484C2ADB0E4 (string)
device_model : iPhone7,2 (string)
device_type : iOS (string)
id : ISL (string)
latitude : 29.4948942979611 (string)
longitude : -95.17218354777557 (string)
timestamp :<PHONE_NUMBER>.276222 (string)
trigger : enter (string)
GeoFence Debug                  No content-type header found
GeoFence Debug                  user-agent: Locative/581 CFNetwork/978.0.7 Darwin/18.7.0, content-type: None
GeoFence Debug                  Recognised Locative/Geofancy
GeoFence Warning                Recognised Locative/Geofancy, error parsing data: 'key body_params not found in dict'

Hmm.  That old version is doing an HTTP GET instead of the HTTP PUT that the newer versions do.  There's no config options in that version to change it?
That's going to be more work.
Can you do the same thing for a current version so I can be sure I have that one correct?

Interesting…. global settings was set to “PUT”  individual fence set to “GET”.  Clicking the “GET” allowed me to change it to “PUT”.  Let me walk to the end of the neighborhood to trigger an event and I’ll update.

On Jan 11, 2024, at 5:40 PM, Joe Keenan @.***> wrote:
Hmm. That old version is doing an HTTP GET instead of the HTTP PUT that the newer versions do. There's no config options in that version to change it?
That's going to be more work.
Can you do the same thing for a current version so I can be sure I have that one correct?
—
Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-GeoFence/issues/5#issuecomment-1888138863, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF2IS3TH6WJTCXENSBJX4KDYOBZ73AVCNFSM6AAAAABBVXACKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGEZTQOBWGM.
You are receiving this because you authored the thread.

I'm golden.  You can close this one out.  I have all 3 of the older iphones reporting in now.  Thank you much and sorry I missed the individual GET/POST option.
The older version is a PITA.  Menu text is white on a white background (so I have to guess where the "save" text is).  For a location, there is no option to trigger an event.  So for every fence for every phone, I have to physically go to that location while looking at indigo logs from another phone, go home, find the new device and save it with a name.

Can you check to see if they work with the released plugin, not the pre-release?

  Yes, I can confirm that the older phones are working with the 2022.1.4 version.


[jsmn] Add new port

https://github.com/zserge/jsmn
Test with https://github.com/myd7349/Ongoing-Study/tree/master/cpp/CMake/vcpkg/jsmn_tests on:

[x] x86-windows
[x] x86-windows-static
[x] x64-windows
[x] x64-windows-static
[x] x64-linux

Thanks for the new port, @myd7349!


Remove firmware file from version control

This patch removes a firmware file that was accidentally added to
version control.

It right there in the beginning, but maybe not that much visible on the PR's view:

https://github.com/Nitrokey/pynitrokey/pull/151/files

Will keep in mind to look for that in the future.

Yeah, I tested the nitropy nk3 fetch-update command with the cwd and forgot to remove the file before git add . :facepalm:


Remove unnecessary db request while adding task

Using the timestamp assigned by the coordinator node does not provide any benefit over using a client-provided timestamp.

https://ocd.appscale.com:8080/job/Daily Build/3024/


Trying to add unknown view tag: 682

Is this a bug report?
No

Have you read the Bugs section of the Contributing to React Native Guide?
Yes

Environment

react-native -0.43.4:
node -6.9.1:
npm -3.10.8:
yarn --version (if you use Yarn):

Then, specify:

Target Platform (e.g. iOS, Android): Android
Development Operating System (e.g. macOS Sierra, Windows 10): Mac OS
Build tools (Xcode or Android Studio version, iOS or Android SDK version, if relevant):
Android Studio SDK version 24

Steps to Reproduce

(Write your steps here:)
1.Even now, can not reproduce, only to see the online error log
2. com.facebook.react.uimanager.IllegalViewOperationException: Trying to add unknown view tag: 682
3.How to find where the problem occurred?  the tag? but how to find in js file?
Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Closing as this is not a bug report.


Timepicker error when selecting minutes

Materialize Release: 1.0.0-alpha.3
Chrome Version 64.0.3282.140 (Official Build) (64-bit)
Windows 10 desktop

When selecting minutes in Timepicker component initialized in the following way:
M.Timepicker.init(inputElement, {     "autoClose": true,     "twelveHour": false });
Timepicker throws the following uncaught exception:
Uncaught TypeError: this.minutesView.addClass is not a function at Timepicker._handleDocumentClickEnd (materialize.js?36ce:9357)
It appears that in _handleDocumentClickEnd method, this.minutesView is an instanceof Element and, therefore, does not have an addClass method.  As a result, the following line fails:
this.minutesView.addClass('timepicker-dial-out')

Hi. Is there any need of further details for this issue to get looked at?

no, thanks for reporting the issue

Fixed in cafc9724220ae48fdaab1d85e1f27a81a51a9859


Gulp crash leaves server running

Leaving this here with the hope that someone who knows Gulp better than I will see it.
I'm currently working on the ES6 + Browserify rewrite (es6-refactor branch) and whenever gulp watch throws an error it prints it and then exits, but it leaves the server running in the background.
This means that when running gulp watch again to get the watcher started, the server tries to listen and always fails because there's already the old server running on 3000 (netstat -tulpn, kill -9 pid etc).
Pretty sure it should be possible for Gulp to throw an error without exiting? Otherwise it would be good to not start the game server if there's already something running on 3000.
Also, not sure why the build process is trying to find modules in the bin/ directory. That's what's causing these crashes in the first place. Error below:
events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: Cannot find module './chat' from '/home/dan/dev/fork/agar.io-clone/bin/client/js'
    at /home/dan/dev/fork/agar.io-clone/node_modules/browserify/node_modules/resolve/lib/async.js:55:21
    at load (/home/dan/dev/fork/agar.io-clone/node_modules/browserify/node_modules/resolve/lib/async.js:69:43)
    at onex (/home/dan/dev/fork/agar.io-clone/node_modules/browserify/node_modules/resolve/lib/async.js:92:31)
    at /home/dan/dev/fork/agar.io-clone/node_modules/browserify/node_modules/resolve/lib/async.js:22:47
    at Object.oncomplete (fs.js:107:15)

It's also probably worth pointing out that the first thing I tried was moving the transform away from the pipe, as shown in the gulp browserify recipe.

Ok I'm looking at it

@danprince

Also, not sure why the build process is trying to find modules in the bin/ directory

build process if using /bin for nodemon in run task
every other task is outputing to /bin

Cheers. Added to my local branch.
I know what /bin is being used for, but it's browserify throwing an error, saying that it can't find a module in the bin dir. Browserify should only care about the client/js dir.

gulp build works fine, but gulp watch does something funny with Browserify.

i think it it is internal browersify/babelify stuff
propably this crap work like this:

babel outputs common.js modules to bin dir
then browersify is looking at this folder but hey there is missing module and you are getting this error

But browserify isn't responsible for any watching, it knows that it's source comes from ./client/js/games.js, no matter what triggers the watch, that is where it should try and find it's modules relative to.

gulp watch are just runnig gulp build when files in client and server folders are changing.
Nodeamon form gulp run (which is also started from gulp watch) is watching bin folder and is restarting when files are chaging there.

nvm I'm wrong about how browersify/babelify work
I'll look at it later but tell me @danprince if everything is working well for you?

Yeah, everything's awesome apart from this error.
Just resorting to having gulp run in the background and running gulp build manually, which is fine for now.

@danprince after my fix too?

The fix stops gulp watch from crashing when it errors, but the browserify error is still there and it doesn't create a build because of it.

Maybe now it is working

Has this been fixed?

Closing it since it appears to have been fixed.


fix: ContainerRegistry - Updated to latest PE schema - avm/res/container-registry/registry

Description

Updated PE schema to latest
Addressed identity warning
Added PE to WAF test

Closes #1789
Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utlities (Non-module effecting changes)
[ ] Azure Verified Module updates:

[x] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] I have run Set-AVMModule locally to generate the supporting module files.
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings

Converting to Draft due to Conflicts

Resolved


Update README.yaml

Update some incorrect field names in the example
The README.md file still needs to be regenerated
what

Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
Use bullet points to be concise and to the point.

why

Provide the justifications for the changes (e.g. business case).
Describe why these changes were made (e.g. why do these commits fix the problem?)
Use bullet points to be concise and to the point.

references

Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
Use closes #123, if this PR closes a GitHub issue #123

/rebuild-readme

/test all


Feature Request Discussion: Fraud Protection Mechanism

Describe the issue
The network doesn't have sufficient fraud protection in place to facilitate wider payment system adoption. Combining an algorithmic fraud detection mechanism and community-driven fraud prevention volunteers paid in Doge (like mining for node operators) would protect consumers while maintaining a de-centralized system.
Expected behaviour
Wallet holders intending on accepting Doge for payments for goods/services should have a means to be KYC validated by the network so consumers sending transactions to those merchants can have confidence of the legitimacy of the merchant. It is possible to be de-centralized while also safer.
Actual behaviour
Fraudulent entities take advantage of consumers with no means of consumer recourse. There is no basis for consumers to have trust in the entity they are sending coins too.
What version of Dogecoin Core are you using?
Latest Release
Discussion Points
Long-article context: https://www.reddit.com/r/dogecoin/comments/n9oyas/the_doge_card_day_2_a_21st_century_payment/
High-Level Feature Implementation Approaches:

Wallet Wrappers - companies that provide wallet services are solely responsible for this
This is where we are today. It is inefficient and centralized. Entities have the authority and incentive to act in their best interest not in wallet holders such as increasing profits/revenue and reducing cost even if that means taking short cuts or charging for security/fraud protection features.

Federated Nodes - the network provides implementation across disparate, independent solutions
This is perhaps a middle-ground stepping-stone solution. It would allow auxiliary nodes to enhance the core nodes functionality and follow a more micro-service based architecture. It would require core support in allowing the auxiliary nodes to issue rewards or charge increased transaction fees and so a mechanism would need to be in place for that. The drawback is cohesion. In a federated sense, it doesn't take much for there to be vast chaos, repetition/duplication of work, and conflict. This most aligns with decentralization though.

Core nodes - the network provides a core implementation / process
This is the hardest level of effort and would solve some challenges but create others. It would help facilitate an adoption model through a centralized process providing sufficient consensus, but it would also likely be very slow and increase the amount of technical work to manage within the core client.

Given the ability for the micro-service architecture, I would promote federated nodes to implement network enhanced features and look for input on ideas of how the nodes could be accepted and authorized to issue Doge rewards or charge higher transaction fees for their work (likely the later). The RPC mechanism would also need to modified to support interaction with the auxiliary nodes.

I agree with this totally.Thats the address I instructed Binance to send  my Doge to . I don't know what wallet Binance used because I don't have a Doge wallet . Now this site promised to double my Doge . How can he send me my Doge back of I never had a wallet in the first place and second the website doge-snl.com disappeare
They kept instructing me to connect my trust wallet to binance and to transfer all my other coins and then give them the address.
since I am stupid , I didnt know how to connect and when I went to chat .. the site was gone and I want to track the address.
In some sites .. the address is not valid .. in other sites it states there is 1.6 mil dollars  .

Moderation note: I'm going to remove anything that shows an address, in this specific case because the last thing I want is anyone sending more coins to them.

On the issue itself; identity and KYC for/on a blockchain is something I believe several startups are investigating ( https://consensys.net/ springs to mind), it's not something in scope for Dogecoin Core.


Update broken link

Thanks a lot for contributing!

 Probably you have the same problem in other repositories but I only checked this one.

Thanks! I fixed that one in the adapter generator already, so it shouldn't happen in the future :)
https://github.com/bankscrap/bankscrap/blob/master/generators/templates/README.md.tt#L38


question: should lib.cleanSource remove cmake cache files ?

Issue description
I've got a wireshark-custom overlay with src = super.lib.cleanSource ~/wireshark;
So I compile my program with nix-shell -A wireshark-custom '<nixpkgs>' but then, when I want to install it via nix-env -iA wireshark-custom I get this error:
CMake Error: The current CMakeCache.txt directory /tmp/nix-build-wireshark-dev.drv-0/wireshark/build/CMakeCache.txt is different than the directory /home/teto/wireshark/build where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt
I wonder if super.lib.cleanSource shouldn't ignore the "build" directory during the unpackPhase (potentially harmful) or at least remove CMakeCache.txt/CMakeFiles ? I can send a PR if that's the case.

It should ignore build directories in general, but I don't think it's reasonable to find a way that works for all invocations. I'd say cleanSource and cleanSourceFilter (used in its implementation) should be seen more as building blocks for making project-specific source import functions, such as builtins.filterSource (p: t: lib.cleanSourceFilter p t && builtins.baseNameOf p != "build"). I've worked with some projects that have a directory named build which contains actual sources, and don't think it would be a good idea to exclude it by default.
One (somewhat orthogonal) way to handle this is to use out-of-tree builds when using nix-shell, i.e. mkdir -p ~/builds/wireshark && cd ~/builds/wireshark && cmake ~/src/wireshark && make as opposed to creating a build directory within wireshark's source dir, which is a little cleaner in general IMHO.

Thanks for the nice solutions. I have implemented project-specific filters in my overlay as you recommanded.
Would be worth adding to the wiki though I am neurotic when it comes to mediawiki syntax.


Modal not usable without JavaScript. No Fallback

A modal is hidden by default, which makes it not usable if one wants to statically show a modal dialog for a user, which might not have JavaScript enabled.
As you can see in this JSBin example one can use d-block or style="display:block" to force showing the modal and also manually add the backdrop to the html without JavaScript, but the resulting modal is not "JavaScript-enabled". It is not possible to dismiss it by clicking the X or the backdrop.
So at the moment, when showing a Modal to non-JavaScript users the modal has reduced functunality for users with Javacript (In comparison to what would be "possible" for these users). But to add the missing functionality one has to hide the modal for non-JavaScript users which is not an option, because they need to be able to see/use it as well.
I would prefer if users with JavaScript would have access to the full functionality without completely removing the functionality for non-JavaScript users.
EDIT: This issue is kind of related to #24939. If the Javascript code would have an option to read an already shown modal from the DOM both issues could be fixed.

if your concern is making sure that a site which would normally show a modal for JS users on page load to still work (without the modal) for non-JS users, you should trigger the modal programmatically via JS once the page is loaded (so without JS, it's not triggered). or am i missing something?

I would like to show the modal for non-JS users.

but those users won't be able to close/dismiss it? i'm failing to understand the specific scenario here

They can if the Modal contains a link or form. Sorry, maybe i should have made that more clear and include it in the example.

They can (close the modal) if the Modal contains a link or form. Sorry, maybe i should have made that more clear and include it in the example.

That's not closing... that's navigating away from the page.

That's not closing... that's navigating away from the page.

Yes, but if they navigate away they don't need to close it anymore.

If you want the modal open on page load  just use
class="modal show"  ??
(instead of simply class="modal" or class="modal fade")

@bkdotcom yes i know i can do that. But then the modal does not work with javascript. The modal does not behave like a modal unless it is opened with $(...).modal().

No JS fallback

@bkdotcom This link will either not be visible for non-js users or not work for js users, so I don't see how it solves the problem.

@bkdotcom's suggestion is perhaps a bit facile.
taking a step back then, this request is asking for the ability to have a modal made explicitly visible in the static HTML by default, and then when JS is present, being able to "bless" the existing open modal to be a working modal.
in the interim, an approach that would possibly also work (and possibly much nicer, because then when JS in not enabled it wouldn't have non-functioning close buttons or similar) is to design the non-JS-enabled version of the page, have the static overlay (made appropriate for the non-JS scenario, i.e. without the "X" close etc) wrapped in a ... block, and for the JS-enabled case having the actual modal which triggers on page load. (though yes, that'd mean duplication of the content).

taking a step back then, this request is asking for the ability to have a modal made explicitly visible in the static HTML by default, and then when JS is present, being able to "bless" the existing open modal to be a working modal.

Yes, exactly.

I'm not completely sure if my suggestion below solves your problem completely, but here it goes. Also I haven't tested it completely for possible side effects.
<!DOCTYPE html>

  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width">
  <title>JS Bin</title>

  <link href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css" rel="stylesheet" type="text/css" />

Modal title

        <button type="button" class="close" data-dismiss="modal" aria-label="Close">
          ×
        </button>

Modal body text goes here.

        <form>
          <button type="submit" class="btn btn-primary">Save changes</button>
        </form>
        Close

	Open

This JS code is portable back to IE9. What it does is simply add a class in a local stylesheet and add that class to the modal, and if JavaScript is enabled immediately remove it before the browser engine even reaches the modal markup. If you want the dialog open to JavaScript enabled browser, you'd open it with a script placed after the modal markup on. In my example I just added the usual link to open and I had to remove the modal-backdrop markup part. That's most likely solvable however.
What you have to watch out for is that you know the exact position of the local stylesheet (in this case it's the last one, and as well the position of the rule that you want to remove in the local stylesheet.
Hope that helps

@herbalite Thats a very good workaround, which solves the problem i tried to describe in this issue! :+1:
I think it would be better to change bootstrap in a way that does not require this workaround, though.
(I think) one could easily add the default "show all modals"-class to bootstrap.css and the "hide all modals"-Javascript to the bootstrap.js.
Making the modals "show by default" instead of "hide by default"
@noobshow Sadly this is basically a reimplementation of a modal dialog, which should not be needed, because Bootstrap already has a very good CSS modal implementation. Or i'm missing something obvious here.

Sorry but currently there is no plan to use our Modal without JavaScript.
Before closing this issue, @mdo do you have any plan to allow that ?

@Mapeper You're missing the point there... It's not just a dialog i mean.
You can port the open and close to your custom css which would make the modal(even bootstrap modal) open and close with/without javascript.

@noobshow
Cool!  Looks like one of the examples on MDN:
https://developer.mozilla.org/en-US/docs/Web/CSS/:target

Is there anyone watching this?
Maybe this could be implemented as a fallback?

Apologies for the delay—no plans to implement any changes here to run the modal without JavaScript.


package.sh

In package.sh line 169 the check reads:
if [ ! -L /etc/init.d/influxdb ]; then

This does not work because -L check if file exists AND is symbolic. So if it does not exist at all nothing will happen.
I'd rather do something like
if [ -e /etc/init.d/influxdb ]; then
    #remove existing regardless if link or regular file
	rm /etc/init.d/influxdb
	ln -s $INSTALL_ROOT_DIR/init.sh /etc/init.d/influxdb
	chmod +x /etc/init.d/influxdb
else
	ln -s $INSTALL_ROOT_DIR/init.sh /etc/init.d/influxdb
	chmod +x /etc/init.d/influxdb
fi

#move runlevel stuff outside of above if loop
if which update-rc.d > /dev/null 2>&1 ; then
	update-rc.d -f influxdb remove
	update-rc.d influxdb defaults
else
	chkconfig --add influxdb
fi

The chmod is probably surplus since it points to an executable file anyway.

Thanks @Sineos -- how about a PR with your suggestions? We could merge it.

See #1797
I have never used git for anything else than cloning to my hdd for local builds let alone creating PR.
So please bear with me if I did mess it up.

Fixed by https://github.com/influxdb/influxdb/pull/1809


Clarify Other Features Section

It would have saved me some time if I had been warned of this limitation before trying it. I realize now that each argument has an "applies to" section, but it would be helpful to mention here as well.

Hi @lorenpaulsen, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@micurd - Could you please review this proposed change from @lorenpaulsen for your AzCopy article in the public repository?

Thanks @lorenpaulsen, I agree that this is a good change.
@tysonn - I would like to accept this pr.


BUG: Commit history of top 3 contributors is not linked

Is there an existing issue for this?

[X] I have searched the existing issues

What went down?
Commit history of all contributors have been linked but that of top 3 contributors is not linked, I would add link to commit history of top 3 contributors
https://github.com/mdazfar2/HelpOps-Hub/assets/162733812/9bea5347-d377-4f31-90a7-5fc32de19e04
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSoC'24 contributor
[X] I want to work on this issue

@mdazfar2 I want to work on this , please assign it to me

@Maana-Ajmera As of now, we do not need it. We will let you know in the future if there is a need. Please search for another issue and raise it, which I'm happy to assign to you.


Added documentation and usage example for keyed_column

This PR includes documentation for keyed_column along with a usage example including screenshot

@hecrj Could you check this PR? I have no response from the original reviewer.

I just want to make it clear that I'm not a maintainer, so I have no saying on whether it's fine. I just wanted to point out some small errors that I managed to catch.
Whether it gets implemented is up to Hector.


OperationalError: invalid sslmode value: "true"

In the Azure portal, the Settings->Connection strings states that the following should be the format of my python connection string:
dbname='{your_database}' user='azureuser@postgresql--3d9hs' host='postgresql--3d9hs.postgres.database.azure.com' password='{your_password}' port='5432' sslmode='true'

However, using this string format with psycog2.connect() throws OperationalError: invalid sslmode value: "true". Your documentation helped my debug this issue, but the Azure portal needs to be updated.

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

ID: d2184eee-03ed-bc72-cbae-57203d7e2269
Version Independent ID: 859b106a-f37d-e051-eb0a-58884b2df647
Content: Quickstart: Connect using Python - Azure Database for PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/connect-python.md
Service: postgresql
Sub-service: flexible-server
GitHub Login: @sunilagarwal
Microsoft Alias: sunila

@BlaneG , thank you for your feedback. We'll review this and get back to you shortly!

@BlaneG Can you please provide more information on what needs to be updated in the portal

@GeethaThatipatri-MSFT  The python connection string should include: sslmode='require' ~sslmode='true'~

@BlaneG document will be updated soon We will proceed to close this issue now.
If there are further questions regarding this, please comment and we will gladly continue the discussion. thanks again for your feedback in improving our documents.


Add pytest-socket

This pytest plugin blocks any attempt for tests to contact the network at the socket level.
Our tests should never rely on making an external network call, but it's currently possible (and very easy in functional tests) to accidentally do just that without noticing. pytest-socket prevents any outgoing network calls and immediately raises an exception when they occur, so we can spot the problem and fix it.

Codecov Report

Merging #594 (df18bf0) into main (00fe15e) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #594   +/-   ##
=======================================
  Coverage   80.91%   80.91%
=======================================
  Files          17       17
  Lines         744      744
  Branches       47       47
=======================================
  Hits          602      602
  Misses        130      130
  Partials       12       12

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


Plain text output widget

Does interact have an output widget for just plain text? I didn't see it in widgets.jl. Currently, I'm just returning a string, but that's not as nice because it shows rather than prints.

Okay, I understand the issue now. You want the quotes to go away and the text to not be monospaced. @stevengj does Text(string) escape HTML special characters like < and >?

Text outputs as text/plain, and therefore it need not do any escaping.


adding public references

ok @jmaag15 this matches WG consensus from 20220824 meeting now

@jmaag15 ping3

Updates as discussed 20220824, merging


python-lsp-server: fix aarch64-darwin

Motivation for this change
pyqt5 is broken on aarch64-darwin
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

How come pyqt5 is needed at all for any platform? I don't see it listed as a dependency in the python-lsp-server repo.

How come pyqt5 is needed at all for any platform? I don't see it listed as a dependency in the python-lsp-server repo.

pyqt5 used in test

test https://github.com/python-lsp/python-lsp-server/blob/c14a95e673396d58734968136d4a16dd2fb497de/test/plugins/test_completion.py#L269-L271
dependency https://github.com/python-lsp/python-lsp-server/blob/7b98f9f6ccc2338552a325d9f06a4d71198e1dae/setup.py#L69

How come pyqt5 is needed at all for any platform? I don't see it listed as a dependency in the python-lsp-server repo.

pyqt5 used in test

test https://github.com/python-lsp/python-lsp-server/blob/c14a95e673396d58734968136d4a16dd2fb497de/test/plugins/test_completion.py#L269-L271

dependency https://github.com/python-lsp/python-lsp-server/blob/7b98f9f6ccc2338552a325d9f06a4d71198e1dae/setup.py#L69

Ah apologies, I looked at HEAD, not the commit that this is building from

You could also use lib.meta.availableOn stdenv.targetPlatform rather than having to shadow the availability information of the package.

You could also use lib.meta.availableOn stdenv.targetPlatform rather than having to shadow the availability information of the package.

You could also use lib.meta.availableOn stdenv.targetPlatform rather than having to shadow the availability information of the package.

@risicle availableOn only considers two attributes of the package platforms and badPlatforms in our case a dependency of pyqt5 is broken so unfortunately availableOn is not an option.

You could also use lib.meta.availableOn stdenv.targetPlatform rather than having to shadow the availability information of the package.

@risicle availableOn only considers two attributes of the package platforms and badPlatforms in our case a dependency of pyqt5 is broken so unfortunately availableOn is not an option.

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

12 packages built:

python310Packages.pyls-flake8
python310Packages.pyls-isort
python310Packages.pyls-spyder
python310Packages.pylsp-mypy
python310Packages.python-lsp-black
python310Packages.python-lsp-server
python39Packages.pyls-flake8
python39Packages.pyls-isort
python39Packages.pyls-spyder
python39Packages.pylsp-mypy
python39Packages.python-lsp-black
python39Packages.python-lsp-server


Chatops widget not populating any messages

My chatops widget is blank and not populating any messages. I used api token with view message scope. It used to work before it stopped working ever since i upgraded to latest source code.

I am also getting the same issue, did you get this resolved?
Please share the fix, we are stuck from past 2 days

do you manage to make it  work ?


⚠ Bofrost.de has degraded performance

In 3d02506, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1995 ms

Resolved: Bofrost.de performance has improved in 17ff5a9 after 49 minutes.


Documentation does not have system requirements anywhere

@lfunkhouser We need to add system requirements to documentation. Because we cannot just provide a hyperlink like we traditionally do on the solutions pages. How do we want to write this? just copy/paste from the system requirements for Desktop, Pro, and WAB (Developer Edition) into their respective pdfs?

as per @lfunkhouser we are forgoing system requirements in distributed documentation at this time. accompanying documentation describes what version of core software are supported as well as required extensions, and we are making the assumption that if the user has the required core software, they have also been able to figure out and meet the minimum system requirements to run said pieces of software


Cannot find module './lib/compiler.js' in 2.6.0

In 2.6.0 release the compiler was extracted to its own file.
The extracted files are not included in the npm package published to the registry though (no /lib folder in node_modules/html-webpack-plugin).
Stack trace (running webpack build through gulp):
Error: Cannot find module './lib/compiler.js'
    at Function.Module._resolveFilename (module.js:326:15)
    at Function.Module._load (module.js:277:25)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (c:\dev\git\kw-advisory-gui\node_modules\html-webpack-plugin\index.js:7:21)
    at Module._compile (module.js:398:26)
    at Object.Module._extensions..js (module.js:405:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (c:\dev\git\kw-advisory-gui\webpack.config.js:5:25)
    at Module._compile (module.js:398:26)
    at Object.Module._extensions..js (module.js:405:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)

When reverting to 2.5.0 all is well again.
Regards
Sam Bernet

Same here, it seems like your latest changes with moving stuff to ./lib/compiler.js never made it's way to npm. Try to re-publish.

Oh sry forgot to update the package.json files array:
https://github.com/ampedandwired/html-webpack-plugin/blob/feature/loaders/package.json#L6
Will be fixed soon!


How can you get authorization results to set state

My question concerns the state of the authorization. Since navigateByUrl doesn't work, I have to use window.location.href to set the redirectUrl after logging in.
The issue I have is that I show some spinners etc based on the state of the authorization, for example, Unauthorized, Authorizing, Authorized.
Now I can't seem to find anything useful for my authorizing state, this leads to an issue where when I press on login, it adds the code to the url, then it sends you back to localhost before actually signing you in. This gives me a split second where the state becomes Unauthorized again because I don't have validAccessToken at that moment. I've tried subscribing to events but alas.

I'm not 100% sure if I grasp what you're after, but maybe this will help:

I tend to have an async auth guard which preserves state (target route)
My app.component shows a "Loading..." overlay (only partially opaque so you can see what's going on in the background - but you could make it fully opaque) while authorization stuff is loading everything
I don't let either the guards or the loading overlay do anything else until auth stuff has fully loaded
I check and use state (target route) in startup if it is available, using navigateByUrl

You can clone linked repository and try it for yourself. If you are not logged in, and try to access a protected route, everything should work.


Setting the base path via env variable (NUXT_APP_BASE_URL)

Issue Summary:
Nuxt 3 supports setting the base path via the configuration file or environment variables. However, the nuxt-i18n-micro library does not seem to support setting the base URL through the environment variable NUXT_APP_BASE_URL.
Steps to Reproduce:
Set the base URL in the nuxt.config.js file:
export default defineNuxtConfig({
  app: {
    baseURL: '/prefix/'
  }
})

Build the application:
npm run build
Change the base path using the environment variable and run the server:
NUXT_APP_BASE_URL=/test/ node .output/server/index.mjs
Access the application at localhost:3000/test/.
Expected Behavior:
The application should be served with the new base path /test/ and should work as expected.
Actual Behavior:
The application does not work as expected, and the following warning is displayed in the console:
[Vue Router warn]: No match found for location with path "/prefix/_locales/general/en/data.json"
Environment:
Nuxt Version: 3.13.2
nuxt-micro-i18n Version: 1.22.1
Node Version: 20.10.0
Operating System: MacOS
Additional Information:
The issue seems to be related to the nuxt-i18n-micro library not respecting the NUXT_APP_BASE_URL environment variable.
The application works correctly when the base path is set directly in the nuxt.config.js file.
Possible Cause:
The nuxt-micro-i18n library might be using the base URL defined in the nuxt.config.js file and not overriding it with the environment variable NUXT_APP_BASE_URL.
References:
Nuxt Configuration Documentation
Thank you for your attention to this matter.

tried locally
NUXT_APP_BASE_URL=/test/ npm run build
NUXT_APP_BASE_URL=/test/ node .output/server/index.mjs
everything works as expected, requests went to http://localhost:3000/test/_locales/, it seems the issue is somewhere else. There's also the apiBaseUrl parameter, and it might conflict with NUXT_APP_BASE_URL. Have you changed it? Try configuring it; maybe this will help.

I tried to simultaneously pass a parameter through env and config, resulting in some kind of strange conflict. Nuxt starts with the prefix from the config, and I'm not sure if it's possible to do it this way. If I use only the config or only env, everything works as it should

Thank you for checking. Can you try to build without setting NUXT_APP_BASE_URL=/test/ during build? In our case we build app once, but serve multiple times with different env variables to change the prefix for every website.

fixed, try v1.27.1

Thank you so much for your help! It's truly the best support I have ever experienced. And your library is pretty cool! We recently transitioned from Nuxt i18n, and I am impressed. It has everything we need: localized routes, SEO and dynamic loading of translations.
You're doing a great job!

thank you for your feedback

here


Update DLP doc with Form Recognizer

@JonVenezia : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off

@gclarkmt: I'm sorry - only the author of this article, @gclarkmt #Required; your GitHub user alias, with correct capitalization., can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Cosmetic niceties

Could we add a description, tags and general readme to the repo?

There's not going to be a more exhaustive general readme for now, but added tags & desc


add test userRepository

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 43.58%. Comparing base (0e2c858) to head (67ca7ef).
Report is 4 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

:exclamation:  There is a different number of reports uploaded between BASE (0e2c858) and HEAD (67ca7ef). Click for more details.
HEAD has 1 upload less than BASE

Flag
BASE (0e2c858)
HEAD (67ca7ef)

backend
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #45       +/-   ##
===========================================
- Coverage   54.71%   43.58%   -11.14%
===========================================
  Files          41       25       -16
  Lines         742      491      -251
  Branches       95       71       -24
===========================================
- Hits          406      214      -192
+ Misses        336      277       -59

Flag
Coverage Δ

backend
?

frontend
43.58% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[WFLY-12392] Removing javaee.api dependency from JSF modules

https://issues.jboss.org/browse/WFLY-12392

Ah, good catch, @bstansberry.

thanks @bstansberry, i've removed all the export="true"


Add build ids to all heat stacks

Creates a unique id no matter what branch we pull down, build id is always in the build parameters that jenkins supplies

retest


Add support for reserved named shadows

Feature Description
Add support for reserved named shadows, namely, shadows that start with a $.
Use Case
I'm thinking of creating a custom Greengrass component that reports the version of a natively installed software to the Software Package Catalog. I'd like the component to access the $package shadow through Shadow manager.
Proposed Solution
Change SHADOW_PATTERN to allow shadow names prefixed with a $. (e.g. \\$?[a-zA-Z0-9:_-]+)
https://github.com/aws-greengrass/aws-greengrass-shadow-manager/blob/b24dda476c3a8f64c2b34a784a89e27825e4c6aa/src/main/java/com/aws/greengrass/shadowmanager/model/Constants.java#L52

[x] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

Hi, thank you for bringing this to our attention.
Currently, Greengrass shadow manager component lets you manage AWS IoT Device shadows that are either named or classic only. For these configured shadows, shadow manager subscribes to their reserved MQTT topics to perform shadow operations.
To support reserved named shadows such as $package, we'll have to investigate all that it entails and evaluate the usecases. Adding it to our backlog for further evaluation.

Hi @saranyailla, thank you for your response.
I only changed the regex and it seemed to work fine, so I'd hoped it'd be a quick and easy fix, but I understand your need for a more thorough evaluation. I guess I'll keep using my fork for the time being. :smile:
Do you have a rough estimate of when this issue would be resolved?

We don't have an estimated timeline for this one yet. We'll use this thread to post any updates if any.


Introduce Pull Request Reviewers

Introduces a generated set of code owners to ensure a good contribution experience.
For more details/timelines (internal): go/codeowners

@confluentinc/csid-admins, @confluentinc/csid-contributors, @confluentinc/csid-reviewers please take action to review and merge this pull request.
For more details/timelines see: go/codeowners
Note: This pull request and subsequent comments are automatically generated


Add advanced integration e2e scenario

Quarkus RHTAP advanced scenario including promotion feature:

Create components in Red Hat Developer Hub.
Verify successful creation of components in Red Hat Developer Hub.
Ensure Red Hat Developer Hub creates a corresponding GitHub repository.
Initiate a Pull Request to trigger a PipelineRun for pull_request events in the GitHub repository.
Merge the Pull Request if the PipelineRun succeeds.
Upon merging the Pull Request, validate that the push PipelineRun starts and finishes successfully.
Verify that the new image is deployed correctly in the development environment.
Trigger a Pull Request in the component gitops folder to promote the development image to the stage environment.
Ensure that the EC Pipeline Runs are successfully passed.
Merge the promotion Pull Request to main.
Wait for the new image to be deployed to the stage environment.
Trigger a Pull Request in the component gitops repository to promote the stage image to the production environment.
Verify that the EC Pipeline Runs successfully passed.
Merge the prod promotion Pull Request to main.
Wait for the new image to be deployed to the production environment.

This is a good flow.
Some additional verify steps and details for PR and Build
After the build or pr step you can verify  the image, sbom, attestation and signature was built (later this willl pass EC which needs those 4 but checking they exist will help triage failures before you try EC
If you are testing the UI the actions on the right will also be enabled to view sbom, logs and acs scans.

Thank you! I will add a separate issue,


How to clear/reset applied filter chips from a button in custom toolbar?

I am upgrading from v2 to v3.1.4.
I have a refresh button in toolbar..
        customToolbar: () => {
            return <React.Fragment>
                <Tooltip title="Refresh">
                    <IconButton onClick={handleFilterReset}>
                        <RefreshIcon/>
                    </IconButton>
                </Tooltip>
            </React.Fragment>;

        },

In v2 I used to set the value of serverSideFilterList to [] whenever refresh button was clicked. This also cleared any filter chips that were applied.
In v3, with serverSideFilterList deprecated/gone when I click on refresh button, and if any filter chip is present, how it should be cleared?

The new method uses the filterList array of the columns.options object (the same way non-serverSide filters work). So if you wanted to remove all of the filters, you could do something like this on your columns array:
const resetFilters = () => {
  let newCols = this.state.columns.map(col => {
    col.options.filterList = [];
    return col;
  });
  this.setState({
    columns: newCols
  });
};

Thank you that worked perfectly. Awesome.


[feat] Can specifies the target directory in bundle.resources when embedding additional files

Describe the problem
My application depend on a closed source dynamic link library.
So, I should copy it into exe folder when developing and bundle.
I found the guide Embedding Additional Files, configures as following:
    "bundle": {
      ...
      "resources": [
        "foo-sys/foo/win/foo.dll"
      ]

the foo.dll will be copy to target_dir/foo-sys/foo/win/.
but i expect it to be copied into target_dir/.
Describe the solution you'd like
    "bundle": {
      ...
      "resources": [
        {"from": "foo-sys/foo/win/foo.dll", to: "./"}
      ]

Alternatives considered
No response
Additional context
No response

you can already do this like this:
    "bundle": {
      ...
      "resources": {
        "foo-sys/foo/win/foo.dll":  "./"
      }

where you use an object for resources instead of an array


ENH: style guide for letter writing

In Meeting 14, @johncoxon brought up that it would be useful to have a style guide to point people to.  This came up because we were doing a group review of a sample letter and found that we expected a certain style of formatting and didn't have a general grammer reason for some of the choices.  John suggested using JGR, since it's one of the most prolific journals in our field: https://www.agu.org/Publish-with-AGU/Publish/Author-Resources/Grammar-Style-Guide
This link could be included under letter-writing resources.

I think in the style guide we might also want to mention how it's good to use the same style/word choices as the group you are nominating/recommending to.


Esto es el "Step 5: Commit a file" pr

Esto es una descripcion: created a branch, created a file and made a commit, and opened a pull request

!!!!!


simplifying and standardizing launch-proxy

Closes #767, #755, and #757

Will check if we need --net=host on the weaveproxy or if we can drop it and use wait_for_status

Ah, d'oh. It needs --net=host so it can shell out for weave attach, etc...


feat: add boost filesystem, json, logic, math, multi_index, static_string, tti

as title
need skip url stability check

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.math) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.math, boost.multi_index) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.filesystem, boost.math, boost.multi_index) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.filesystem, boost.logic, boost.math, boost.multi_index, boost.static_string) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.filesystem, boost.json, boost.logic, boost.math, boost.multi_index, boost.static_string) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.filesystem, boost.json, boost.logic, boost.math, boost.multi_index, boost.static_string, boost.tti) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.filesystem, boost.foreach, boost.json, boost.logic, boost.math, boost.multi_index, boost.static_string, boost.tti) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.filesystem, boost.foreach, boost.json, boost.logic, boost.math, boost.multi_index, boost.pfr, boost.static_string, boost.tti) have been updated in this PR. Please review the changes.

CI has some real failures.

CI has some real failures.

@fmeum fixed it.