Error: GitHub Badges page is not responsive in mobile view

Describe the Error

The tables of GitHub Badges page are not responsive.

Expected behavior

These tables should be responsive in mobile view so that user can easily understand the badges & it basic info.

Additional context
https://github.com/user-attachments/assets/8af4f44f-484e-43b4-952f-fff3ac8e93aa
@sanjay-kv sir Please assign this issue to me under GSSoC'24

@sanjay-kv The issue that I was trying to fix was removed by someone in the github badges page. So please close this issue.


About Visualization

Hi @YuelangX , I successfully get fitting results from videos, but I have difficulty in visualization.
How to get visualization results like  gifs/ .
Vertices can be exported to mesh and view in external Viewer, but how to project with a camera to get a mask with actual positon in image like your results?
Thank you!

Have you set visualize as True in the config file? The visualization results will be saved.

whoops, it was set to False due to OpenGL problem.
Many thanks!


Feb 29th bug?

What did you do?
./flexlm_exporter --path.lmutil="/opt/ansys_inc/shared_files/licensing/linx64/lmutil" --path.config="/etc/flexlm-exporter/flexlm-exporter.yml" --web.telemetry-path="/metrics"
What did you expect to see?
valid data for processing in prometheus/grafana
What did you see instead? Under which circumstances?
ts=2024-02-29T12:43:32.719Z caller=lmstat.go:579 level=error collector=lmstat couldnotconvert=0001-01-01T00:00:00Z tounixtime:="parsing time "2023-02-29T13:18:00Z": day out of range"
ts=2024-02-29T12:43:32.719Z caller=lmstat.go:579 level=error collector=lmstat couldnotconvert=0001-01-01T00:00:00Z tounixtime:="parsing time "2023-02-29T12:50:00Z": day out of range"
System information
Linux 4.18.0-477.27.1.el8_8.x86_64 x86_64
FlexLM Server information
me@my-machine:/tmp # /opt/ansys_inc/shared_files/licensing/linx64/lmutil lmstat -f cfd_solve_level2 -c 1055@my-server
lmutil - Copyright (c) 1989-2009 Flexera Software, Inc. All Rights Reserved.

FlexLM Exporter version
flexlm_exporter, version 0.0.12-3-g4f401f9 (branch: main, revision: 4f401f91858c4843db764267364f3432f7cfbd9e)
  build user:       colleague@his-machine
  build date:       20240229-12:35:33
  go version:       go1.21.6
  platform:         linux/amd64
  tags:             netgo static_build

FlexLM Exporter configuration file
licenses:
  - name: app1
    license_server: 1055@my-server
    features_to_include: cfd_solve_level2
    monitor_users: True
    monitor_reservations: True
    monitor_versions: False

Logs
No response

Hi @muetho68,
Nice catch, This is a known problem related to the parsing of dates, as flexlm does not return years as part of the date, and indeed 2023 had no Feb 29th. I will take a look at it, and try to handle it gracefully. Anyways PRs are more than welcome.

Hi @mjtrangoni ,
as suspected the flexlm_exporter is working today, on a "normal" day. But the next Feb 29th is only 4 years away ;-)


Specifically provide CPU, memory allotments in quality gates

What does this PR do?
This commit places specific CPU and memory limits on our idle quality gate experiments.
Motivation
By default the target has the runner's full allotment of resources and as we have asserted a bound on memory it makes sense to bound the memory available to the target to more closely mimic deploy conditions.
Additional Notes
REF https://github.com/DataDog/datadog-agent/pull/31326
REF https://github.com/DataDog/datadog-agent/pull/31246

/merge


ASN blocks/bans

Having bans based on ASN could be useful. It would make blocking specific ISP's/Organizations a lot easier than using CIDR (some organizations can have hundreds of ipblocks and is a pain to keep updated). One can get a DB of ASN's from https://maxmind.com (account required), or https://db-ip.com/db/download/ip-to-asn-lite.

This is already partially supported actually, i just need to automate the loading of the datasets and decide if i want to load them into the database at all or just keep them in memory.
Ill see if i can finish this soon, I already do this in another project so should be pretty trivial.


Improve issues for asking new command

Add github issue templates

bug report
feature_request ( new command )

Fix #87 Improve issues for asking new command
Note that the merge need to be on the master branch

Did you test this files in a repository ?

Did you test this files in a repository ?

@SebSept  to test you can we the following link https://github.com/friends-of-presta/fop_console/blob/19e734d54b99f3d065465a1e4028e01acbc9cd44/.github/ISSUE_TEMPLATE/feature_request.md
Or simply paste the md content when opening a new issue :)

@SebSept  to test you can we the following link https://github.com/friends-of-presta/fop_console/blob/19e734d54b99f3d065465a1e4028e01acbc9cd44/.github/ISSUE_TEMPLATE/feature_request.md
Or simply paste the md content when opening a new issue :)

yes, sure. 👍🏼

yes, sure. 👍🏼

Thanks @nenes25  :)

Thanks @nenes25  :)

The merge is done on master.
Can you make a PR on dev please @nenes25 ?
The templates are not applied when submitting an issue... Do you know why ?

The merge is done on master.
Can you make a PR on dev please @nenes25 ?
The templates are not applied when submitting an issue... Do you know why ?

@SebSept my bad in fact dev is the default branch in this project i didn't notice as by default it's master.
I can make a pull request in dev branch it will fix this normaly

@SebSept my bad in fact dev is the default branch in this project i didn't notice as by default it's master.
I can make a pull request in dev branch it will fix this normaly

no problem !
Activating the feature in configuration has created some default files, I'm cleaning the job...

no problem !
Activating the feature in configuration has created some default files, I'm cleaning the job...


Fixed bindings that end with *.js

Unintentionally discovered that imports from react-dom/server.js do not work(was able to easily write my own small binding for this, but this is an easy fix and totally doable). Tested on test-utils as well, same thing

Thank you for your contribution! Sorry for the long delay in merging.


Support css animation classes mimic reactjs/react-transition-group v1

Addresses #35
This is what ember-css-transitions links to as the main inspiration for this add-on. The version they are referring to in the React docs is actually v1.
This branch attempts to support passing in a hash of class names as mentioned here: https://github.com/peec/ember-css-transitions/issues/35#issuecomment-614995716
Unfortunately this won’t work for Tailwind, Animate.css users. Due to both enter/ enterActive (or leave/leaveActive) classes being applied the latest class in the stylesheet will show. So in my PR fade-in works but fade-out does not.

closed in favor of https://github.com/peec/ember-css-transitions/pull/38


Update index.html

Fixes #146

onsistent Labeling: Clear and uniform button labels.
Enhanced Usability: Easier for users to understand button functions.
Improved Aesthetics: A more professional and polished look.
Better Accessibility: Easier identification and use for all users.
Easier Maintenance: Simplified updates and modifications in the future.
Increased User Satisfaction: Higher likelihood of user engagement and retention.

Please mention your issue no.

#146

this is the issue number

Thank you.

Your welcome 😁


fix(deps): use v5 core with all services

PR summary
This PR modifies v4 go core references to reference the v5 go core.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

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


Starts making zipkin2.Span optional for external reporting

This migrates data formerly handled only by the zipkin reporter into
MutableSpan. To complete decoupling will take future pull requests
that add trace IDs to MutableSpan and make the logging reporter use
MutableSpan by default instead of zipkin types.

ok I think this is done


Remove note about http/https in password reset emails

I missed this template in https://github.com/cfpb/cfgov-refresh/pull/4834. This removes the note about http/https and :443 in password reset emails.
Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the CFPB development guidelines
[x] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[x] Reviewers requested with the Reviewers tool :arrow_right:

This same change was reviewed in #4834. I'm going to merge this.

Could we instead remove this whole template so that we use Wagtail's built-in one?

Could we instead remove this whole template so that we use Wagtail's built-in one?

Huh, yeah, it doesn't seem like our extra bits at the end there add enough value to override the original template.


Fix webpack production mode build

Fix https://github.com/EnduranceCode/endurancetrio-race-results/commit/3704ea385bfc56540be731b38ac4e2daf8a6154a


Unable to run

Hello,
Did the installation using cargo build --release, did set the environnement variables :
When I type echo $DYNHOST_USERNAME it prints the right thing (same as the two others), but when I try to run the program (using ./dynhost in /dynhost/target/release), it says that DYNHOST_USERNAME isn't set :
DYNHOST_USERNAME must be set
I'm running the program on an Debian 10 4.19.0-6-amd64, on an Xeon-Based system

Hi, I just tried the steps you followed and I cannot reproduce unfortunately :(

Ok, can't see if it still happens


Add Plausible analytics for parity with legacy site

Need to include Plausible analytics (same as legacy site). We will eventually remove Plausible once we're comfortable with the information coming through Segment.
https://plausible.io/docs/plausible-script

Looks like you may have implemented Plausible in the original site @Bboyakers. Is there any chance you could take a look at this one?

Looks like you may have implemented Plausible in the original site @Bboyakers. Is there any chance you could take a look at this one?

Most definitely!

Oh, it looks like this is done via an existing plugin @BboyAkers :
https://plausible.io/docs/docusaurus-integration

Went ahead with this one since we're working on a timeline to get the new site launched @BboyAkers
There are still PRs that could use reviews though.

Kk! Sorry for the delay on my end! I'll checkout the PRs!


Make it easier to implement cirq.Sampler

Add sample_dict / sample_dicts methods to Sampler
Use cirq.ABCMetaImplementAnyOneOf to derive any of run/run_sweep/sample_dict/sample_dicts from any of the others
Fix deprecation warning from pytest by bumping version of pytest-asyncio
Fix cirq.to_sweep not saying it takes cirq.Sweepable

Discussion points:
The implementer still has to deal with boilerplate parameter resolution. Is there some nice way to expose a params argument to the user without requiring the implementer to deal with it? I came up with something interesting but possibly confusing:
    @value.boilerplate(lambda wrapped_function, self, program, *, params = None:
                       wrapped_function(self, program=protocols.resolve_parameters(program, params)))
    @value.alternative(requires='sample_dicts',
                       implementation=_sample_dict_from_sample_dicts)
    def sample_dict(
            self,
            program: 'cirq.Circuit',
    ) -> Dict[str, Any]:

Discussed offline - closing it.

Can we delete this branch?

Can we delete this branch?


add a CSS selector (optional?) to fetch the fields in the DOM

rather than fetching elements that have a "data-url" attribute, add an arbitrary css class selector (e.g. agnocomplete). Usage example:
$('.agnocomplete').selectize(/* ... */)

idea: we could make it a settings.

If it's not set or None, do not add the CSS class to the attributes.
if it's set, add it to the class attribute.

won't play nice... will add a data-agnocomplete (customizable to your needs)


German support

Awesome, thanks! Could you please add some tests to see that this works as expected? I know there are some similar tests somewhere in here: https://github.com/tictail/claw/blob/master/tests/text_quotations_test.py#L324

Thanks!

This is included in v1.1.0 of claw.


Add new workflow

I listed what it does in the previous pr, I have made a pr with everything wrong to my repo so you can see what it does:
https://github.com/DeDiamondPro/NotEnoughUpdates-REPO/pull/7

Me when it doesn't work

Me when it doesn't work

Me when that’s GitHub smooth brain protection since it needs the repo token to make annotations and stuff, it will work when its merged prob.

Everything is finished and the check can now be ran manually,
on pull request it checks all changed files
on push it checks all files
on manual activation it checks all files
also some improved error messages


Update variables.md

Python 3 print statement correction.

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

@rahulchordiya - Thank you for your contribution. Approved the info.

#sign-off


app.sqlite is not getting deleted

Describe the bug
So, when user click on logout then I am calling to delete for each table.
  // delete all the tables
  Future<void> deleteEverything() {
    return transaction(() async {
      await customStatement('PRAGMA foreign_keys = OFF');
      for (final table in allTables) {
        // type arguments for generic method 'delete<T extends Table, D>
        // Try adding an explicit type,
        //for example: delete<UserTable, UserTableData>(table)
        await delete<Table, dynamic>(table).go();
      }
      await customStatement('PRAGMA foreign_keys = ON');
    });
  }

But, app.sqlite file still exist.

So, is there any way possible to delete app.sqlite completely when user click on logout button...

This happens for both android and windows.

The reason that this doesn't delete the file is that deleting from a table will only remove the affected rows (in your case, all rows). But sqlite3 will keep the table schema in the database file, so it doesn't delete the entire database file.

So, is there any way possible to delete app.sqlite completely when user click on logout button...

For that to work reliably, you'd have to:

Close your database (call and await yourDatabase.close()).
Delete the database file (using File.delete).
Possibly open the database again, upon which drift will automatically create all tables again.

But if your intention is to remove user data from that file, you can just keep running the delete statements and then issue a customStatement('VACUUM') in the end. That will keep the table structure in the database so you don't have to re-create the tables. I don't see a compelling reason to fully delete the file, it doesn't give you any security benefits.

Really appreciate the quick response.  mm, so moving own-wards will not going to delete the files I will stick with what you advice.... (because it seems it required further permission to access file.)


fix: Add logic for converting Schema to dict in @swag_from

This fixes #464

Hey @billyrrr, do you mind reviewing this?

Hey @billyrrr, do you mind reviewing this?

Definitely, but, to be honest, the code base of flasgger is difficult to be grasped in full even for me. I would have to review several usages of convert_schema method, or maybe even do a few refactors before being able to review or merge this change.

Hey @billyrrr, do you mind reviewing this?

Definitely, but, to be honest, the code base of flasgger is difficult to be grasped in full even for me. I would have to review several usages of convert_schema method, or maybe even do a few refactors before being able to review or merge this change.

I just copied the functionality from SwaggerView i.e https://github.com/flasgger/flasgger/blob/4bdaed53aa4ed9b315c5f0b651705be526d0b182/flasgger/marshmallow_apispec.py#L103
In swag_from marshmallow schemas were not being converted.


duplicate markets on testnet (both on L1 and L2)

Subject of the issue
ETH-PERP and BTC-PERP are duplicated.
Your environment

Network used (Mainnet? L2?)
Which browser and its version

Expected behaviour
Only show ETH-PERP and BTC-PERP once.
Actual behaviour
But it shows twice:

and the isolated margin also is doubled, eg, I have only $50 but it shows $100.
Steps to reproduce
Go to dashboard page: https://kwenta.eth.limo/dashboard or https://dev.kwenta.io/dashboard/.

Thanks for the report. This is because of perp v2 migration.
Here is the fix: https://github.com/Kwenta/kwenta/pull/1712


How to restart TLM proxy

@yyao84 I have been playing around with the TLM proxy and for the most part it has been working great, however, I did run into a problem the other day where it seemed to randomly not respond to requests. Given that it had been working fine, I figured I would just try to restart it but was not exactly sure how I should do that. I played around with the services in the AWS console and eventually was able to get new instances running after trying a number of different things ... sure enough the TLM proxy started working fine again after this restart. However, assuming I am going to need to do this again at some point, I am  hoping to understand the "proper" way to restart the TLM proxy?

Hi @terry-wilson - the easiest way is to force a new deployment, which starts up new containers, drains connections from the old containers and then shuts them down.
In the console:

Navigate to ECS (double check the region, it takes me to a random region half the time if I don't have a preferred one set in my settings)
Select the TileLevelMarkerProxyStack-ecscluster cluster
Select the TileLevelMarkerProxyStack-ecsfargateservice service
Select the Update service button
In the Deployment configuration section, check Force new deployment
Select Update
This takes you to the Deployments tab for the service, where it shows you the status of the new deployment

To use the CLI:
aws ecs update-service --cluster ${cluster_name} --service ${service_name} --force-new-deployment
I've also seen issues with the TLM proxy, and am working on an update for it to not use Elasticache but rather sit behind CloudFront.


Docker licensefinder/license_finder seems to use old PHP version, upgrade to 7.3 or 7.4.

Hello,
First, thanks a lot for this very nice tools shared with the community.
Running docker run -t --rm licensefinder/license_finder:latest ... was working great until Ocramius php package abandonned PHP 7.2 support.
I get this bug when trying to generate licenses for a PHP project:
Digest: sha256:db4b2c335af7cff297f14385ddc4dcdea87033a726c2943b941cec15ed721f94
Status: Downloaded newer image for licensefinder/license_finder:latest
Generate License Finder report...
Traceback (most recent call last):
        22: from /usr/share/rvm/gems/ruby-2.6.5/bin/license_finder:23:in `<main>'
        21: from /usr/share/rvm/gems/ruby-2.6.5/bin/license_finder:23:in `load'
        20: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/bin/license_finder:6:in `<top (required)>'
        19: from /usr/share/rvm/gems/ruby-2.6.5/gems/thor-1.0.1/lib/thor/base.rb:485:in `start'
        18: from /usr/share/rvm/gems/ruby-2.6.5/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
        17: from /usr/share/rvm/gems/ruby-2.6.5/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
        16: from /usr/share/rvm/gems/ruby-2.6.5/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
        15: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/cli/main.rb:147:in `report'
        14: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/license_aggregator.rb:11:in `dependencies'
        13: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/license_aggregator.rb:49:in `aggregate_packages'
        12: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/license_aggregator.rb:49:in `flat_map'
        11: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/license_aggregator.rb:49:in `each'
        10: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/license_aggregator.rb:51:in `block in aggregate_packages'
         9: from /usr/share/rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/forwardable.rb:224:in `acknowledged'
         8: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/core.rb:78:in `decision_applier'
         7: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/core.rb:83:in `current_packages'
         6: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/scanner.rb:36:in `active_packages'
         5: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/scanner.rb:36:in `flat_map'
         4: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/scanner.rb:36:in `each'
         3: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/package_manager.rb:101:in `current_packages_with_relations'
         2: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/package_managers/composer.rb:14:in `current_packages'
         1: from /usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/package_managers/composer.rb:44:in `dependency_list'
/usr/share/rvm/gems/ruby-2.6.5/gems/license_finder-6.1.2/lib/license_finder/package_managers/composer.rb:50:in `composer_json': Command 'composer licenses --format=json' failed to execute: PHP Parse error:  syntax error, unexpected 'string' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST) in /var/www/html/vendor/ocramius/package-versions/src/PackageVersions/Installer.php on line 33 (RuntimeError)

On Ocramius side, bug has been reported here, but it is because it does no more support PHP 7.2:
https://github.com/Ocramius/PackageVersions/issues/121
I don't know which PHP version is used by docker licensefinder/license_finder, but if it is 7.2 (pretty old and no more supported), this issue could be fixed by going to PHP 7.3 or 7.4 which will be a good thing I think.
As Ocramius is used by many open source software in conjunction with composer, it make sense to update to more recent PHP version as license finder use composer.
For now, I can no more use it : (
Feel free to ask any information needed if I can help.
Thanks for reading me.

Thanks a lot for your fast fix, but there is awlays the problem : (
Could this issue be reponened please ?
I tested it but sadly last Ocramius PackageVersions works only with PHP 7.4.
Making a lint php with php 7.3 for this file bring a parse error https://github.com/Ocramius/PackageVersions/blob/master/src/PackageVersions/Installer.php#L33
Maybe it would be better to bump to php 7.4 version, so no parsing problem occurs for recent projects (and php 7.4 can parse old php file too). Here this is problem with this Ocramius package (very used by composer), but it could be happen with any project code using php 7.4 code. As all class are parsed by licensefinder, if it encounter a php 7.4 code syntax it breaks all the license generating process : (
There is two solutions:

bump to php 7.4
in case a parse error because PHP version cannot read the code, skip the file and go on processing other files so we can get the list of license. It will make it more resilient for new php syntax and prevent the all generating license process to abort.

Both solutions could be implemented in same time so it will be more robust for later.
Thanks.

@Yivan Alrighty, we will try to bump to 7.4. It make take a few days because we have an internal docker image that builds off of this and needs to be in sync but we will get it done.

@Yivan If you want to make a PR to do this bump.  I am hesitant with the skip file solution at the same time because then we could miss something in the unparsable file so maybe failing is the better way to go about this. Either way, 7.4 is modern so I am good with that part.

Hi, thanks. I just made a pull request to bump to php 7.4.
I hope docker hub image will be soon available so we can activate again the license finder on our CI.
For skipping file, yes it would prevent file parsing so some license could be missed. I understand.
For now it could be leave as it, as PHP 7.4 cli will ensure no parsing error should be happen.
Maybe on day as improvement, it could be leave to user decision with a flag (something like stopOnParseError: bolean). It is just an idea.
Thanks.


Add MaxTest

Add test cases
Changes proposed in this pull request:

I added few test cases that test Math.Max functions.

hi @shihlei, given the problems mentioned above, I am closing this now, but feel free to open a new PR if you get around it.


[type="password"] fallback

Discussion
This will temporarily change a [type="password"] input to a [type="text"] in the conditions that

the input needs a placeholder fallback
there is no value assigned to the input

This is to work around the "dots" that a [type="password"] field will show instead of characters by falling back to an input type that can present clear text.
Before (IE9)

After (IE9)

I'll close this if there is no interest :)


Update application-api to 8b646f622222d641fe4b05e7d62845037a88cada

For some reason the update PR did not get automatically created: https://github.com/redhat-appstudio/application-api/runs/17428616924
Manually updating

/approve

Why doesn’t PR approve add lgtm?


BOLTWALL IMPLEMENTATION

On this PR I added the Boltwall implementation, the boltwallServer directory houses the Boltwall implementation. Read the BOLTWALL.md doc to run Boltwall.
@Extheoisah

Closing this given that we went in a different direction. Thanks @elraphty for giving this a try!


Add guidelines for erb files

This pull request adds a styleguide file for erb and html in general. If there is anything else worth adding that I've missed I'm happy to add it into this PR.

🍍


No pairing with homebridge

Running Homebridge (0.2.15) at Ubuntu server (14.04.3 LTS). Homebridge starts but MyTouchHome and Eve app do not pair with homebridge. Using Philips Hue as accessoire. I see Homebridge connects with the bridge, because it initializes the PhilipsHue Platform Plugin Version (0.0.2) and fetches all my Philips Hue Lights (more than 10). I did reset the homekit config at iPad, changed the username in the bridge part of config.json, also changed the bridge name. But nothing helps. Installed versions:
npm version
{ npm: '3.3.12',
ares: '1.10.1-DEV',
http_parser: '2.6.0',
icu: '56.1',
modules: '47',
node: '5.3.0',
openssl: '1.0.2e',
uv: '1.8.0',
v8: '<IP_ADDRESS>',
zlib: '1.2.8' }
Finally I deleted both apps at my iPad, reboot and installed again. Unfortunately.
Strange is that I never has been asked to enter the code for pairing. What to do?

What do you specifically mean by this statement Homebridge starts but MyTouchHome and Eve app do not pair with homebridge - Can you see the Homebridge Accessory? When you enter in the ID what happens?

When I start homebridge at my ubuntu server everything seems to be ok. At the end I see the pin used for pairing and the port. Hiwever when I start one of the apps at my iPad. It does not ask me for the pin so they do not pair

So you try to "add and accessory" under a home and can't see Homebridge?

As written before in the apps I am not asked to enter the pin so It does nit find anything, no accessoires

Have you walked through this process?
http://www.insteon.com/support-knowledgebase/2015/5/4/adding-a-homekit-compatible-device

Yes but no pin question

It doesn't ask you to scan a pin after you select your Homebridge?? That's odd? You can select your Homebridge can't you?

No I cann't

No I can't

Can you try Bonjour Browser on a mac and see if the hap service is visible?

Is anyone else having issues pairing on an iOS 9.3 beta1 device?  I can see the 'HAP' under bonjour browser

On my 9.3 beta 1 phone, it pairs just fine but only the hub accessory is passed to Homekit.
I'm going to start investigating tonight unless someone figures it out before then.

@pdlove in iOS 9.3, HomeKit handles bridged accessory differently. When one or more bridged accessories are out of compliance (normally because the value is invalid), it just discard the accessory that has problem, but the bridge will be there.

Thanks. I'll take a look and see what's wrong with it. Thanks for the info.

Thank you. I got mine sorted out. No problems with 9.3 beta now.
It looks like there is a new mandatory Characteristic on BridgingState which I was testing on one device in my library. It's a new Characteristic as well that wasn't in the file.
There may be other Services I'm not using with mandatory Characteristics.
Will there be a process that can be used to update HomeKitTypes.js in HAP-NodeJS when the time comes? I would assume Apple has it backwards compatible so that it will still work with older versions of IOS after adding the new mandatory characteristic.

Apple didn't publish the BridgingState service so technically they can do what ever they wanted to change the service… I already made the changes to support iOS 9.3 in this branch (https://github.com/KhaosT/HAP-NodeJS/tree/bridgeUpdate), you can check the commit history and adopt the new behavior.

Finally I got it working, which means the apps do pair now with the bridge and reacts on speach cmds. What I did was a complete reinstall of most of the software (npm, nodejs, homebridge, etc), including changing to an older kernel. Than I tried again with new installed apps on my iPad and it was working. Then changed back to the newer kernel, reboot ubuntu and still working. What intrigues me is, what the cause was of the malfunction, but I changed so many things that I can not find out anymore. So, now other things to develop here, like using Siri and homebridge at two devices (iPad and iPhone) and start homebridge at boot as a service etc,

@KhaosT Does the current version of Homebridge work with HomeKit on iOS 9.3?

@AppleTechy as long as the current plugin doesn't use Service.BridgingState then they're fine.

I am a noob. I have been using homebridge for a while. It's great! However, after 9.3 all my accessories disappeared. I have no idea what service.bridgingstate means, and that is probably why I don't know how to fix it. I tried resetting homekit with iOS, deleting the persist file, and changing the port. The plugins I have been using are Nest, smartthings, and IFTTT. Any suggesstions?

Please update homebridge to 0.3.0 or later
Sent from my iPhone

On Mar 22, 2016, at 7:21 PM, PjRossi<EMAIL_ADDRESS>wrote:
I am a noob. I have been using homebridge for a while. It's great! However, after 9.3 all my accessories disappeared. I have no idea what service.bridgingstate means, and that is probably why I don't know how to fix it. I tried resetting homekit with iOS, deleting the persist file, and changing the port. The plugins I have been using are Nest, smartthings, and IFTTT. Any suggesstions?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

I tried updating it. Unless I am updating it wrong which could be a possibility. I have it running on startup using systemd. The command to update I use is, sudo npm update -g home bridge

Thanks! I tried updating it again and it worked. Not sure what happened. Must have done it wrong the first time.


Update french labels

Here are some updates on french labels.
A lot of time since I used the theme. It's usage as a ruby gem is a lot easier for updates ! Thank you for that ! 😃

Thanks as always!


[suggestion] Use elementaryOS HIG?

I dont think eOS offers anything special, but their HIG is really reasonable. Have you considered following it?
Thanks for the software.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Konv is meant to work on every platform available and by so I want it to looks the same everywhere. So I'll follow my own HIG ^^


Fixed mumo image name

mumo image in the example docker-compose.yml (goofball/mumo) doesn't exist. The correct image name is goofball222/mumo
@goofball222

Thanks for your contribution!


DataTransfer - AddFieldValue -  Add Note aboud audit fields

Could you please add the note about audit fields on this article as well.

Copying the SystemID and data audit fields using CopyRows is supported in Business Central version 21.5 and later.

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

ID: 932a01fe-bfc9-dd14-945f-f639f28d3385
Version Independent ID: 932a01fe-bfc9-dd14-945f-f639f28d3385
Content: DataTransfer.AddFieldValue(Integer, Integer) Method - Business Central
Content Source: dev-itpro/developer/methods-auto/datatransfer/datatransfer-addfieldvalue-method.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for the feedback! We've added the note. The updated article will be published soon.


(PUP-7648) Fix ci:test:git pre-suite on OSX 10.11

A number of problems prevented ci:test:git from executing properly
on OSX 10.11:

When performing a gem install bundler, system Ruby places the
binstub in /usr/local/bin. However, the SSH environment is not
configured with /usr/local/bin in PATH. There are multiple
solutions to this problem:

Add /usr/local/bin to ~/.ssh/environment in Beaker - covered
in BKR-1139. This allows any additional binaries that might
be installed (homebrew, git, other Ruby gems with binstubs)
to be available. This is the most effective universal solution
but will require a Beaker release.

Fully qualify the bundle command as /usr/local/bin/bundle to
work around this OSX specific problem, until it can be
assumed as in PATH as part of a new Beaker release.

Add to the host[:host_env] hash of environment variables via
a Beaker options file, so that PATH is augmented with
/usr/local/bin. Unfortunately this requires setting additional
hosts / options files on disk prior to any code running in
the Puppet pre-suite, to be picked up during Beakers host
initialization and injected into ~/.ssh/environment correctly.
Otherwise, the PATH would have to be manipulated in each new
SSH command. Due to beaker-hostgenerator commonly being used
to execute, its simpler in this case to just modify to use
an absolute path to /usr/local/bin/bundler as it is the only
command known to be impacted at this time.
Note that beaker-hostgenerator should also allow arbitrary
settings injection using {} syntax, but this doesn't appear to
work properly with ci:test:git and it's uncertain if it
properly handles the :host_env hash when writing to YAML.

Due to OSX SIP (System Integrity Protection) /usr/bin is not
writeable and /usr/local/bin should be used instead. Override
Beakers default puppetbindir setting to /usr/local/bin and use
that as the --binstub directory when installing the Puppet source
with Bundler. binstubs should continue to use /usr/bin/ruby as
the interpreter.

Similarly, when calling install.rb, provide --bindir as the same
/usr/local/bin as the system Ruby binstub dir is not otherwise
writeable. Beaker helpers will fully qualify the path to puppet
using the puppetbindir setting already.

Relates to https://github.com/puppetlabs/beaker/pull/1405

CLA signed by all contributors.

Looks like we need to retarget for either 4.10.x or later.

needs to be retargeted at 4.10.x, 5.3.x or master

This work is now happening in beaker-puppet as a part of PUP-8305


feat: add configurability to icons

Made icons configurable via options.
First draft, have not been able to test it properly yet, but if desired I'll look in to it more. Solves #131.

Looks good so far, this looks like something I would accept. Some thoughts just for information. I have been thinking that things like the sln icon should not be attached to the object itself but derived from the type field.
Im pretty sure the initial state of the testrunner is no longer valid so the refresh icon is never used.
The default icons were like a best effort from my side to find some suitable icons. Id be interested in seeing what icons you would use and maybe make those the defaults
But anyways, awesome PR! Let me know when you want me to test it and review it, looks good so far

Yeah, reasonable thoughts. My first idea was simply to use nerdfont-icons for everything, to streamline it. Like this:

Had to make a couple of small changes, I just wrote a simple merge_table early in the project without knowing of the vim deep extend. It was not an issue because there were no nested structures. I just added that fix here because if a user specifices a single icon they want to override the other icons become nil.
Would you mind updating the readme to inform that customizing icons is an option?

Dependency injection? huh?

Yeah, sorry about the confusion, it was late here when I wrote it. What I meant was that the way the options were being passed parameters felt a bit clunky.

Had to make a couple of small changes, I just wrote a simple merge_table early in the project without knowing of the vim deep extend. It was not an issue at the time because there were no nested structures. I just added that fix here because if a user specifices a single icon they want to override the other icons become nil.
Would you mind updating the readme to inform that customizing icons is an option?

Yes, will do. What is your opinion regarding the defaults?

Im a little skeptical to the skipped icon, is it intuitive enough? Maybe
But your defaults are definitely better than the current ones so please do update them with yours.
yeah passing around options seems weird but I still havent seen any nvim plugins with better ways to do it. Using vim.g is a no-go for me

Im a little skeptical to the skipped icon, is it intuitive enough? Maybe But your defaults are definitely better than the current ones so please do update them with yours.

I agree on the skip icon, I did not put that much time in to selecting icons, it was mostly for testing.
I thinkthe following selection would look nice as defaults, everything except the cs-logo uses octicons, seems like it would provide a nice default look.

Sold! #shipit

Updated the defaults and added them to the readme, I did not however change the screenshots of the testrunner, as I don't have a public project to give an example of.

Looks amazing! Great work!
What do you think, are we ready to merge?
The code looks good, I tested it and it works, there is no breaking changes, shipit?
One thing I noticed is that the default icons doesnt render for me in github markdown so im guessing the readme for most people will have ? for every icon. I dont know if people are using nerdfonts in their browsers idk, im fine with it so I guess we can merge?

Yeah the nerd font thing is inevitable I'd say. Go ahead and merge it! :)

@adriankarlen Amazing work!❤ Thank you for contributing! 😁


surface core value props earlier in installation instructions

New users do not appear to understand the meaning behind adding new nodes. Wrap in an explanation of what adding new nodes mean, and surface earlier that the SQL client is built-in.

Totally agree.
Another place to add an explanation might be where we talk about how to kill a node. A short sentence or two on how the data survives with a node down would be beneficial in understanding the core value props.


LUCENE-9454: Remove version field on Analyzer

Version switching on Analyzer behaviour should be implemented
in the various component factories, rather than on a mutable
setting on Analyzer itself.

+1, this is 9.0 only?

Yes, I should have made that clear, sorry!

@mikemccand I'm curious why you say:

This was an overly complex approach to backwards compatibility!

I think it's rather simple, and the PR was simple as well showing it was a simple idea.  If this approach is complex, what simple approach do you recommend instead?


refactor: api classes to pydantic conversion

What I did

fixes: #
How I did it
How to verify it
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

refactor: ManagerBase commit is in response to co-working with @fubuloubu on creating a Manager Base class that can handle injecting properties and passing them one time to all manager classes

Currently getting this error when trying to compile Solidity files:
ERROR: Unable to load project. Reason: 1 validation error for SolidityCompiler
config
  field required (type=value_error.missing)

I am unable to use the ape-ens plugin from this PR:
I try  this:
from ape_tokens import tokens

tokens["ENS"].balanceOf("juliya.eth")

and I get this error:
AttributeError: 'ENSConversions' object has no attribute 'networks'

I am unable to use the ape-ens plugin from this PR:
I try this:
from ape_tokens import tokens

tokens["ENS"].balanceOf("juliya.eth")

and I get this error:
AttributeError: 'ENSConversions' object has no attribute 'networks'

This is a breaking change for all imports, likely. We wanted to normalize the names to *_manager because we got into an issue due to confusing the different names

Closing this draft in favor of https://github.com/ApeWorX/ape/pull/509


Claiming space and signaling location of groups

Nick has asked how we plan to help groups meet at the event.
Seems like there are quite a few ways this could be done. One thing we can certainly do is put up the table names. Then people can signal better where they are.
Would love to know what @lorrainechu3n thinks!

Have suggested that we speak about how to claim space in the intro on Monday. Won't be needed before that and is only needed for in-person people.

Easy, can add to comms the morning of as a reminder!


Make name resolution resolve proc macros instead of relying purely on the build system

This makes name resolution look at proc-macro declaration attributes like #[proc_macro_derive] and defines the right proc macro in the macro namespace, fixing unresolved custom derives like thiserror::Error (which can cause false positives, now that we emit diagnostics for unresolved imports).
This works even when proc-macro support is turned off, in which case we fall back to a dummy expander that always returns an error. IMO this is the right way to handle at least the name resolution part of proc. macros, while the expansion itself should rely on the build system to build and provide the macro DLL. It does mean that they may go out of sync, but we can provide diagnostics if that happens (something like "could not find macro X in crate Y – ensure that all files of crate Y are saved").
I think it is valuable to be able to reason about proc macros even when we can't expand them, since proc macro expansion can break between Rust releases or users might not want to turn it on for performance reasons. It allows us to provide better diagnostics on any proc macro invocation we're not expanding (like a weak warning that informs the user that proc macro support is turned off, or that it has been disabled because the server crashed).
Fixes https://github.com/rust-analyzer/rust-analyzer/issues/5763

bors r=matklad


(bulk-crap-uninstaller) Switch AU to Get-GitHubRelease

Description
Switches bulk-crap-uninstaller to use Get-GitHubRelease
Motivation and Context
Part of #2007
How Has this Been Tested?
Ran AU script locally, it updated the package correctly.
Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

@TheCakeIsNaOH awesome work! Thanks for your contribution!


Added .gitattributes file

This way, the files would be available in the repository but it would not be downloaded when the package is required by another project.

Thanks a lot! 👏


Add name parameter to the tft request

As tmt-plans repository now contains morf tests for convert2rhel this
is needed to filter out tests that make no sense for leapp.

Can one of the admins verify this patch?


Resorce route middleware not work

Hi for averyone
Am trying to add a middleware to one of my resource routes but apparently it can't access the middleware when I enter the route:
Some help

apparently it can't access the middleware

what is the error? your message doesn't give enough info on the problem to determine what the cause is.
Worth noting that if it can't load your own custom middleware, that's far more likely to be an issue with your application than this package.

hi @lindyhopchris
thx for your response.
how much the route is accessed, the middleware should be called first, right? but it accesses the route without making the call

What middleware is listed when you use php artisan route:list (obviously filtering it by the route that has the problem)? That should confirm whether or not the middleware has been correctly added, as it should be shown in the middleware list for that route.

@lindyhopchris sure
ok. in the first image, i have the middleware added to route, and the next image, i have the route list, i  dont see the middleware added to this route, just i see sanctum middleware but this is in header route group.

if i add this middleware to route group, it work.
the middleware is 'role_or_permission' from spatie roles and permissions package

So I think your problem is this:
$resource->get('/')

That will collide with the JSON:API index route for the resource (i.e. the route that lists all resources for that resource type). The routes() helper method is for registering additional routes, not ones that collide with the routes that the package registers to match the JSON:API spec.
To add that middleware to the resource routes registered by the package, use:
$api->resource('bloodTypes')
  ->controller('BloodTypeController')
  ->middleware('role_or_permission...');

Hi @lindyhopchris
ok, but i dont need assign the route to group route, i need assign to single resource, in the official documentation we have an example, but, this not work

Your use is different though to the example.  This won't work:
$resource->get('/')

Because it collides with the JSON:API routes registered for the resource. The example uses a custom route i.e. one that doesn't collide with the JSON:API routes.


Sync eng/common directory with azure-sdk-tools for PR 6518

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/6518  See eng/common workflow

@danieljurek do you agree that these changes have nothing to do with this PR?

@scbedd -- Two categories of problems I'm seeing here:

Failures in CMakeGeneration jobs... These test steps that run BEFORE the build (and definitely before test). These are also failing when running the CI job directly against main so I think this is a problem manifesting in main cc @RickWinter
A test failed in cpp - core - ci, but it does not reproduce on re-run. Also, this is a novel failure for this test that hasn't shown up in previous runs.

Given that, I'd say that the evidence from these pipeline runs is that your change does not increase failures above what's already observable in main.


Reimport Either used in Executor

Subj
It is convenient when you need to implement own Executor
sqlx-core is also would be nice to have available for describe::Describe

@DoumanAsh would you please run cargo fmt?


Connection issue: UnhandledPromiseRejectionWarning

This extension does not work for me at all.
I have filled in grammarly.username and grammarly.password in settings.
Error message:
2020-02-24T07:49:37.149Z grammarly:host {
type: 'INIT',
documentId: 'file:///c%3A/XX.md',
account: 'public'
}
(node:19612) UnhandledPromiseRejectionWarning: FetchError: request to https://www.grammarly.com/signin failed, reason: getaddrinfo ENOTFOUND www.grammarly.com
at ClientRequest. (c:\Users\XX.vscode\extensions\znck.grammarly-0.6.2\out\server.js:15380:11)
at ClientRequest.emit (events.js:200:13)
at TLSSocket.socketErrorListener (_http_client.js:402:9)
at TLSSocket.emit (events.js:200:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:84:9)
(node:19612) UnhandledPromiseRejectionWarning: FetchError: request to https://www.grammarly.com/signin failed, reason: getaddrinfo ENOTFOUND www.grammarly.com
at ClientRequest. (c:\Users\XX.vscode\extensions\znck.grammarly-0.6.2\out\server.js:15380:11)
at ClientRequest.emit (events.js:200:13)
at TLSSocket.socketErrorListener (_http_client.js:402:9)
at TLSSocket.emit (events.js:200:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:84:9)
(node:19612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
(node:19612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)

Getting the same error, the extension has unfortunately not been working for the last two days. In addition to the above, I get an 401 for the authentification attempt
grammarly:auth authentication failed 401 Headers


Cityscape Fine-tuning

Dear @Lavreniuk,
Thank you for your grat work. May I inquire about the pre-trained KITTI model used for fine-tuning Cityscape?
Is it the 1024x320 KITTI model that utilizes ConvNeXt?
Your insights would be greatly appreciated.

hi @PoKoHA, thank you for your interest in our model! Yes, it is pre-trained KITTI model with ConvNeXt, you could download it using the links in the main of git repo.

Thank you so much for your kind and quick reply.


add mac compatibility mode

This change is potentially controversial, so consider it RFC rather than something final :)
On Mac a common modifier for hotkeys is Meta (aka Cmd, aka ⌘), while Ctrl is usually avoided. On the other hand, it's very uncommon for the Meta key to be used for app-level hotkeys on Windows or Linux.
To provide a familiar experience for users on all platforms, I suggest the Mac compatibility mode, which treats the Meta modifier as if it is Ctrl on Macs (unless both are used). So on Mac meta+b invokes ctrl+b, meta+ctrl+b still invokes meta+ctrl+b.
To keep the API minimal, I'm piggybacking on top of the overrides object, because basically this is a special kind of an override. A special opaque object MAC_COMPAT is exported, which can be mixed in with the rest of the overrides.
import { hotkeyKeyUX, startKeyUX, MAC_COMPAT } from 'keyux'

startKeyUX(window, [
  hotkeyKeyUX({ ...MAC_COMPAT })
])

getHotKeyHint also supports this and renders Ctrl as ⌘.
I'm open to all suggestions regarding the API and the idea in general.

I thought about something this as well. I think we should have it, at least as an option.
I will think about architecture after I finish my task at the conference. Around next week

Glad you're back from the conf :) Updated the API.

@ai Just letting you know, this PR is not abandoned, I will have time to revisit it later this week 👍

Nice. Thanks. I will release it after the shower.
Do you have Twitter account to mention you?

Thanks for reviewing so quickly! I'm not really on Twitter, but if you're comfortable doing so, you can link my Telegram channel: https://t.me/smalldogenergy - although it's fine if you won't :)

Thanks. Released in 0.7.


Software Setup

My current research topic DAW comparison. I‘ve watched two already, and it looks like LMMS is the way to go, as the others are not really open source and to some degree not even available on Linux.
I wonder, if there are non-gui options that are just as good and usable.

I haven‘t used it, but it seems to be the popular solution: Krita. Don‘t forget it.
I hope with the right tablet attached to a Linux computer this can be as good as Procreate.


migrate e2e tests to selenium-webdriver so they can be run on saucelabs

also checkout chai-webdriver and nightwatch

@yyx990803 i was wondering why you went with nightwatch.js tests. i'm currently looking for alternatives, the main motivation is around development-speed. i can't seem to get anything done in a reasonable amount of time because things like a repl are missing.
are there any "hacks" that you are using in development that are worth sharing?


FYI new official repository for spams

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
Hi,
I am part of the spams core dev team. We have restructured our project, and we now have an official repository on github at getspams/spams-python associated with the spams package on PyPI.
The maintenance of spams is again more active since not so long ago.
Best,
Installed packages
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main
_openmp_mutex             4.5                       1_gnu
ca-certificates           2022.2.1             h06a4308_0
certifi                   2021.10.8        py39h06a4308_2
ld_impl_linux-64          2.35.1               h7274673_9
libffi                    3.3                  he6710b0_2
libgcc-ng                 9.3.0               h5101ec6_17
libgomp                   9.3.0               h5101ec6_17
libstdcxx-ng              9.3.0               hd4cf53a_17
ncurses                   6.3                  h7f8727e_2
openssl                   1.1.1m               h7f8727e_0
pip                       21.2.4           py39h06a4308_0
python                    3.9.0                hdb3f193_2
readline                  8.1.2                h7f8727e_1
setuptools                58.0.4           py39h06a4308_0
sqlite                    3.38.0               hc218d9a_0
tk                        8.6.11               h1ccaba5_0
tzdata                    2021e                hda174b7_0
wheel                     0.37.1             pyhd3eb1b0_0
xz                        5.2.5                h7b6447c_0
zlib                      1.2.11               h7f8727e_4

Environment info
active environment : test_spams39
    active env location : /xxx/miniconda3/envs/test_spams39
            shell level : 3
       user config file : /yyy/.condarc
 populated config files :
          conda version : 4.11.0
    conda-build version : not installed
         python version : 3.9.5.final.0
       virtual packages : __linux=5.13.0=0
                          __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /xxx/miniconda3  (writable)
      conda av data dir : /xxx/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /xxx/miniconda3/pkgs
                          /yyy/.conda/pkgs
       envs directories : /xxx/miniconda3/envs
                          /yyy/.conda/envs
               platform : linux-64
             user-agent : conda/4.11.0 requests/2.26.0 CPython/3.9.5 Linux/5.13.0-35-generic ubuntu/20.04.4 glibc/2.31
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

Good to know.
Atm I think we are in need of a maintainer. I was maintaining this for a while, but have since moved on. If this is something you or someone you know is interested in, would be happy to help whoever get started here.

Thanks for your answer. I started a discussion about contribution to this feedstock in our project (c.f.
https://github.com/getspams/spams-python/issues/19). I'll keep you updated.
Ideally, to facilitate maintenance on both sides (pip and conda), we could try to adjust conda-forge python-spams to point to the now spams official repository for python (https://github.com/getspams/spams-python) and move the development work there (to avoid duplicated work) and hopefully reduce the number of required patches to make it work here.
What do you think?


Make anexia provider more resilient against errors

Signed-off-by: kstiehl<EMAIL_ADDRESS>What this PR does / why we need it:
The Anexia API can behave a little bit weird sometimes.

Requests to the API get a negative status code because of some internal engine timeouts but in the VM get's provisionend anyways. We are now tracking whether we already provisionend an IP, and stop provisioning more of them on error.
During deletion we use the new deprovisioning tracking
The machine controller remembers ongoing provisionings and reattaches to them now after an error

Which issue(s) this PR fixes (optional, in fixes #<issue number> format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Optional Release Note:

Anexia Provider is more resilient now and supports reattaching to ongoing provisionings after an error

@kstiehl Thank you very much for your effort. Can you please rebase your changes so we can start the reviewing process? Cheers!

@moadqassem just randomly saw your request and will do that on @kstiehl's behalf, as he does not work for us anymore - commits will say unverified here on github though

/retest

@kstiehl can you please refactor the PR to take care of:

pull-machine-controller-lint
pull-machine-controller-test
pull-machine-controller-verify-boilerplate

Other failures are not related to your PR and I'm taking a look at them.

@ahmedwaleedmalik I'll look into it

/ok-to-test


Simpler spatial

This PR takes a step or two toward #48. Here I have:

removed the alternate county data sources that we weren't using at all
constructed a national topojson file of county boundaries starting from the Census Bureau's data (approved by the WU team)
reduced reliance on the IPUMS-based files by displaying Census Bureau data rather than IPUMS data as county boundaries in the vizzy

In a future PR or two we should:

finish eliminating reliance on the IPUMS-based files by generating stateDict and countyDict from the Census Bureau files instead
after that, we can either take the preprocessing step out or push the census boundaries data manipulation into preprocessing
generate state boundaries by merging counties rather than by querying maps (this will improve the match between state and county boundaries)
shift reliance from the current state boundaries to those new merged-county boundaries

And when we get to performance refinements we should consider

keeping the 1 big national file of county boundaries, but maybe simplifying it to the minimum needed for a national view. then also build state-specific files with more detailed county boundaries, and only load those files on demand. build on the existing state-data-caching code in map_utils.js

@mwernimont here's your answer to where she's at with the topojson :)

@aappling-usgs is this what allows us to start using PR and VI shapes for @mwernimont's projection task?

not yet on the state shapes, which still currently rely on a dataset that doesn't have PR and VI. next PR, i hope.
but in the meantime, @mwernimont , you should be able to stop filtering out AK, PR, and VI centroid dots, and if the projection doesn't break with those dots added back in, then the projection is likely to work for the state shapes as well once we have them.

PR and VI dots work!


remove some commands and update ugdg

PE-D delete wrong class issue was due to a misunderstanding and random sorting of class when some command is executed.
Class list is useless since there is calendar so i removed it along with one of the delete class command.

you might want to commit something random to get Appveyor run again
it can fail randomly


Webpack CSS configuration for improved code coverage and code consistency

[ ] Parker Stylesheet Analysis
[ ] CSS Audit
[ ] CSS Modules
[ ] stylelint
[ ] Prettier

Replaced with discrete issues


Use --internal with sane defaults in scaffoldings

It's interesting that in the scaffolding there has been the fakeinbox and fakesmtp containers made to isolate restored backups in devel/test environments from making requests to the outside world, specifically when attempting to contact servers.
However, it turns out that since Docker 1.10, we can create networks with the --internal flag, which restricts access to the outside world perfectly fine (see https://github.com/moby/moby/pull/19276).
We can use that instead of using some of the proxies. It should be easier to understand for newcomers, and easier to maintain for oldcomers.

IMO we should replace fakesmtp for providing a mail catcher like odoo.sh does.

Yes, also. I'll open a new issue for that.


Fatal Exception: java.lang.LinkageError

Hi,
I got this LinkageError error on some Mi, Huawei and Samsung phones.
Is there anyway to fix it?
Thanks

@uzumaki258 Sry for the late reply. It's happening because I used mediations. And mediation packages are not same version with this package's admob version. So, I carefully checked mediations library versions to be same as this package's admob version number. And it fixed.


WPS seems to have troubels finding "truelats"

Hello,
I used the script and it did provide both binary as well as index files, but I can't get the WPS/geogrid to process the data (output HGT_M are all zeroes). I get this message error in the geogrid.log and don't have any clue about the problem's origin.
Processing HGT_M
WARNING: In GEOGRID.TBL, no specification for truelat1 in entry 1.
WARNING: In GEOGRID.TBL, no specification for truelat2 in entry 1.
WARNING: In GEOGRID.TBL, no specification for stdlon in entry 1.

Here is the created index file :
type = continuous
signed = yes
projection = mercator
dx = 0.0025
dy = 0.0025
known_x = 1.0
known_y = 601
known_lat = -18,30125
known_lon = -150.26125
row_order = top_bottom
wordsize = 8
tile_x = 625
tile_y = 601
tile_z = 1
tile_bdr=0
endian = little
units="meters MSL"
description="Topography height"

This is what my namelist.wps looks like ("THT" being the new high-res. elevation data I want to add) :
&share
 wrf_core = 'ARW',
 max_dom = 4,
 start_date = 2005-01-01_00:00:00,2005-01-01_00:00:00,2005-01-01_00:00:00,2005-01-01_00:00:00,
 end_date   = 2005-01-01_12:00:00,2005-01-01_12:00:00,2005-01-01_12:00:00,2005-01-01_12:00:00,
 interval_seconds = 21600,
 io_form_geogrid = 2,
 opt_output_from_geogrid_path = '/home3/datawork/pmauger/CONFIGS/V3_wrfout_base_coarse/WRF_FILES/WPS_DATA/HIGHRES',
 debug_level = 0
/

&geogrid
 parent_id         =   1,   1,  2,  3,
 parent_grid_ratio =   1, 5, 3,3,
 i_parent_start    =   1, 47, 323,40,
 j_parent_start    =   1, 15, 65,41,
 e_we              =   211, 441, 121,121,
 e_sn              =   79, 166, 121,121,
 geog_data_res     =   30s, 30s, THT+30s,THT+30s,
 dx = 105000,
 dy = 105000,
 map_proj = 'mercator',
 ref_lat   = -10.0000
 ref_lon   = -158.4
 truelat1  = -10.0000,
 truelat2  = 0.0,
 stand_lon = -158.4,
 geog_data_path = '/home3/datawork/pmauger/DATA/geog'
 opt_geogrid_tbl_path ='/home1/datawork/sjullien/MODELS/WRF/WPSV3.6.1_paul/WPS/geogrid'
/

Have you any idea what could have gone wrong ? Thank you.

It seems like known_lat has a comma instead of a period to describe the decimal number. Can you try modifying it to:
known_lat = -18.30125

and go back to us? Thank you


ci(zuul): fix reverse-dependency tests

Related to packit/packit#2008

:+1: to move the openshift tests to TF :smile:

I'm trying to rebase #2061 which should solve the tests as well.


HTML heading levels do not match TOC level

Unless I am mistaken, the "h" tags in the HTML source do not match the TOC level.
H2 for example is used for a top-level, single digit TOC entry.  H3 for double-digit (1.2).  Etc...
Is there a reason we started with H2 instead of H1?
It causes a bit friction when tracking down open and close sections that are messed up.  We should consider matching "h" levels with TOC levels before we get too far along the HTML path.  This will come up in ST at some point.

h1 corresponds to the title of the document.

I see that now in the front-matter.  Thank you.  H1 would be way to big for level-one entries in any case.  I think this can be closed as don't fix unless others think it is worth getting clever with the CSS to define a custom entry for the title in the front-matter and resize the H1-H5 tags.
Now that I have had this discussion, I will likely never get tripped up again...


simplify configuration

Corresponding changes for https://github.com/mitmproxy/mitmproxy/pull/5562.

Can you explain your reasoning behind this change? As far as I can tell, the logic that you're deleting has just moved to the Python side (except the tests which were here). And the deleted Configuration class is just a wrapper around port, server_private_key and client_private_keys anyway, and they are now just separate arguments?
There's also whitespace changes and reordered / unordered use statements that look weird - did you use non-nightly rustfmt?

I think doing the configuration generation on the Python side is significantly less complex and verbose. We don't need to pull in three additional dependencies (serde, serde_json, ini), we don't need to write custom serialization/deserialization for x25519 keys, and we don't need to deal with configuration objects if we can just pass two additional arguments to start_server.
Put differently, I don't think we need a configuration object. If you remove that from the equation it's most natural to just do the key handling in Python.

This makes any future changes wrt/ WireGuard parameters (i.e. PreSharedKey support or similar) a breaking change mitmproxy_wireguard, but if you want to deal with that, then ok.


Add (automated) documentation building to our builds

This is one of those todo things that gets pushed backwards allot.
I have been looking at a couple of different engines and the choice is basically

Doxygen
Sphynx

These two are alive, have an active userbase and thus stackexchange.
I worked with sphynx and I hate it. The documentation it produced is ugly
Doxygen: http://eigen.tuxfamily.org/dox/group__TutorialAdvancedInitialization.html
sphynx: https://docs.python.org/2.7/library/stdtypes.html
I'm currently adding doxygen documentation to one of my personal projects and could probable port the stuff I learned easy to NestMC.

bcumming [3:11 PM]
regarding autogen documentation, what are your plans there?
Because I have strong opinions about things like Doxygen that would require negotiation :wink: (edited)
w.klijn [3:14 PM]
sphynx is ugly and I have bad experience.
doxygen looks nice and is the other of the two major players
bcumming [3:15 PM]
For what it is worth: I think that Doxygen docstrings are a big hinderance to code readability.
w.klijn [3:15 PM]
What do you propose?
bcumming [3:16 PM]
I don't have any concrete proposals.
There will be parts of the library for which docstrings could be well justified, where we have a public API.

On a 'side' note. I'm putting on the table that I think documentation is a first class citizen for a successful project and expect to be writing a big part of it for NestMC.

Sooo. I have been looking for different c++ documentation generators:
Doc-O-Matic  :  payed
HeaderDoc: Last release 2009
Help Generator: Payed
ROBODoc: Last activity on github 2015
VSdocman: payed
DOC++: last release 2002
Imagix 4D: Payed
GenHelp Pro - FraserSoft:  payed
KDOC: The codebase is mostly orphaned now (from the homepage)
Twintext: The company writing it is dead
Universal Report: payed
The three viable options

Sphinx: Primary Python documentation, generates C++ documentation with Doxygen
Doxygen: defacto standard for C++ documentation generation
Reinvent the wheel:

Doxygen is good at generating documentation of APIs from docstrings.
Does it also provide a nice way to do documentation that is not derived from the source code? Like Sphinx which lets you write generic documentation.
I would like to have seperate files where documentation about how to use the API is defined, along with detailed rationale behind design choices, and descriptions of algorithms etc.

Yes: create a directory (e.g. doc) and use it for standalone doxygen files. A standalone file is basically a text file consisting of only the C++ comment, e.g.:
http://entrenchant.blogspot.de/2009/09/doxygen-gotchas.html

We have had automated generation of docs on Reathedocs via Sphinx since #328
http://arbor.readthedocs.io/


Update to DependencyCheck 2.1

Coverage decreased (-0.02%) to 98.421% when pulling c52ef4b9ed831e45cdeca8795fd822d3ae894b2c on dependencycheck2.1 into e1e5257d0458c77cdbff051ad9c806d75a27acb9 on master.


Corrected indentation in spec.collection in ClusterLogging CR

It was not possible to create ClusterLogging CR as per the YAML defined in the documentation. There was some indentation issue for which a fix has been proposed via this PR.

Version(s):

Red Hat OpenShift Logging 5.5, 5.6 and 5.7
Issue:

Link to docs preview:

Public Doc:
https://docs.openshift.com/container-platform/4.13/logging/v5_7/logging-5-7-administration.html#logging-deploy-loki-console_logging-5.7-administration
QE review:

[ ] QE has approved this change.

Additional information:

Something went wrong while working on a commit and led to this. Please ignore. Sorry for the spam.


Pointer Arrow

The yellow pointer arrow is far too large and distracting as it appear, there should be a more subtle fade in.

Linked to #2193


fix: add code transformers support for the rose-pine theme

fixes https://github.com/shikijs/shiki/issues/730

Thank you, but we couldn't just patch the themes, as they are synced with upstream and will get overridden. It's more like something on the shiki transformer side to support it.

Thank you, but we couldn't just patch the themes, as they are synced with upstream and will get overridden. It's more like something on the shiki transformer side to support it.

I didn't notice that I needed to synchronize from upstream; I was thinking too simply.

@lzl0304 did you open a PR/issue for the Rose Pine VSCode theme at all? I've patched my current shikijs install with your fix (thank you so much btw), but keen to see this get resolved properly. Unfortunately I don't know enough about why your fix works to open this PR myself.


Do crate version munging in release_tool, so changes can be committed.

Because we need to munge the version to publish the dependency crates, we ran into an issue with cargo complaining about a dirty repo: https://github.com/opendp/opendp/actions/runs/3325358361/jobs/5497961034
We could use the --allow-dirty flag, but that feels a little dicey.
Instead, this change moves the munging from publish_tool.py to release_tool.py, which is already dealing with git changes on the release branch.
Side note: We could've tested this locally outside GitHub, and avoided a lot of hassle, if not for the fact that you can't use --dry-run with workspaces. Possible solution here: https://github.com/rust-lang/cargo/issues/1169#issuecomment-1254260875

We already need to go in and set /VERSION, rust/Cargo.toml's workspace version, and python/setup.cfg's version. Should we handle setting those versions differently here?


SimpleEncoder/SimpleDecoder: Non-alpha encoding not correctly round-tripped

I can losslessly encode an image without an alpha channel, but when decoding the data is misaligned.
The encoder [specifies the data format] (https://github.com/imazen/libwebp-net/blob/master/Imazen.WebP/SimpleEncoder.cs#L69), but the decoder [always uses BGRA] (https://github.com/imazen/libwebp-net/blob/master/Imazen.WebP/SimpleDecoder.cs#L50)
I think the problem might be due to supplying PixelFormat32... to encoding methods that expect 24bits per pixel, because I noticed that a non-alpha compression is larger than a compression with an alpha channel.

Would it be possible to add a failing test case for this?

This test case is still failing. I'll see if I can fix it.

Issue is fixed with commit 6257f64b0229eca5bee154ca37c13871f52207bb


rewrite: Use "rc" and "refcell"  to avoid all clones.

Changes

Wrap the node with rc and refcell to avoid cloning the entire tree when modifying it.
Serialize internally using rlp. Removed the custom codec trait (because I don't think it is necessary).
Added the hasher trait of the custom hash algorithm and provided the implementation of keccak256.
Removed generics from TrieError

benchmark
before:

after:

fix #42

Tested in cita-vm, this pr is great!

Such amazing performance improvement !! :+1:


Use structopt for command line arguments parsing in cargo-fmt

This is part of work on #3310
I've started with only porting cargo-fmt to structopt (since it was causing problems with arguments parsing on Windows). But if this pull request is fine, I can proceed with porting the rest of binaries to structopt.
I would appreciate if someone with Windows machine can check whether it fixes Windows command line issues (e.g. #2694 and others).

Hm, it looks like it suffers from the same problem as the previous approach. When the program is called with cargo fmt (as opposed to just calling cargo-fmt executable directly), cargo passes the whole command line (including fmt as the first argument) to structopt, which does not expect fmt as an argument.
In order to fix that I can see two options, both are not great:

manipulate env::args() directly (dropping the first fmt argument), it's similar to what it is done now and what causes issues on Windows.
add optional and hidden argument fmt to structopt arguments description. I'm not 100% it's possible, because it would mean mixing positional arguments and flags. Also it's somewhat "hacky".

Hm, another option is to treat fmt as an optional subcommand, let me investigate that.

Another option is just filter out the extra fmt argument passed by cargo, i.e. something like:
    let args = env::args().filter(|x| x != "fmt");
    let opts = Opts::from_iter(args);

It looks like going with an optional subcommand is not a good option, because it requires too much boilerplate just to workaround that extra fmt argument passed by cargo.
I am not quite sure why cargo behaves like that, i.e. if it's invoked with 'cargo cmd' and finds cargo-cmd executable in PATH, then what is the point of passing that cmd argument again to the executable in question? We've already established the mapping between cargo-cmd and cargo cmd... Probably there are some good reasons for that, but I can't see them now.
For now I am choosing the filtering out option (even though it would prevent other cases for options fmt, e.g. if you want to format a file named fmt).
@scampi @topecongiro Please let me know your thoughts on that. Thank you!

@sphynx Thank you for your work! I haven't yet used structopt nor clap to implement cargo subcommand, so I don't have any useful advice off the top of my head, sorry. However, skimming through the structopt repo I have found an issue [1] that seems relevant. Would you mind reading it if you haven't?
[1] https://github.com/TeXitoi/structopt/issues/58

@topecongiro Thank you, I haven't seen this particular issue, but I've read it now. However, I've seen some other examples, e.g. in cargo script, which use clap subcommands to implement cargo subcommands. It's all doable, but I think it slightly complicates the code.
Here is a version with a mandatory subcommand fmt:
use structopt::clap::AppSettings;
use structopt::StructOpt;

const ABOUT: &'static str = "This utility formats all bin and lib files of \
                             the current crate using rustfmt.";

#[derive(StructOpt, Debug)]
#[structopt(
    bin_name = "cargo",
    author = "",
    raw(about = "ABOUT"),
    raw(setting = "AppSettings::DisableHelpSubcommand")
)]
pub enum CargoOpts {
    #[structopt(name = "fmt", author = "", raw(about = "ABOUT"))]
    FmtOpts(Opts),
}

#[derive(StructOpt, Debug)]
pub struct Opts {
    /// No output printed to stdout
    #[structopt(short = "q", long = "quiet")]
    quiet: bool,

    /// Use verbose output
    #[structopt(short = "v", long = "verbose")]
    verbose: bool,

    /// Print rustfmt version and exit
    #[structopt(long = "version")]
    version: bool,

    /// Specify package to format (only usable in workspaces)
    #[structopt(short = "p", long = "package", value_name = "package")]
    packages: Vec<String>,

    /// Options passed to rustfmt
    // 'raw = true' to make `--` explicit.
    #[structopt(name = "rustfmt_options", raw(raw = "true"))]
    rustfmt_options: Vec<String>,

    /// Format all packages (only usable in workspaces)
    #[structopt(long = "all")]
    format_all: bool,
}

And then I use it as follows in execute function:
    let CargoOpts::FmtOpts(opts) = CargoOpts::from_args();

The rest of the code stays the same. Also note that I'm not filtering out "fmt" from env::args().
This approach has a disadvantage that one has to pass fmt option even if invoking cargo-fmt directly, i.e. one needs something like cargo-fmt fmt --help.
Also, it feels a little bit like a hack: we need to pretend that we are cargo and fmt is our subcommand, even though we only support that single subcommand in cargo-fmt.

@sphynx Thank you so much for quickly testing it out! Given the pros and cons, I think the current implementation (the one using the filter) seems better. For the implementation that uses subcommand, I am also worried that the help message gets kind of corrupted.

even though it would prevent other cases for options fmt, e.g. if you want to format a file named fmt

We can prevent this with a small hack:
    let mut found_fmt = false;
    let args = env::args().filter(|x| {
        if found_fmt {
            true
        } else {
            found_fmt = x == "fmt";
            x != "fmt"
        }
    });

@topecongiro Totally agree with you. I've added your code with found_fmt workaround to my PR.

@topecongiro Is there anything else I need to do with this PR?

This PR is ready to be merged. Also I appreciate bunch of tests added in this PR, it eased my reviewing process.


Ionic serve was accidentally terminate

I have the latest version of ionic installed on my system. when  I run "ionic serve" it seem to work properly but after few seconds later it show some error as following:
TypeError: Cannot read property 'message' of undefined
at Server.error (D:\xxxxxxx\xxxxxxx\project\node_modules\tiny-lr\src\server.js:266:52)
at Socket. (D:\xxxxxxxx\xxxxxxx\project\node_modules\tiny-lr\src\server.js:217:22)
at emitOne (events.js:101:20)
at Socket.emit (events.js:191:7)
at onwriteError (_stream_writable.js:341:10)
at onwrite (_stream_writable.js:359:5)
at fireErrorCallbacks (net.js:483:13)
at Socket._destroy (net.js:524:3)
at Socket._writeGeneric (net.js:727:17)
at Socket._write (net.js:746:8)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ionic-hello-world@ ionic:serve: ionic-app-scripts serve "--v2" "--address" "<IP_ADDRESS>" "--port" "8100" "--livere load-port" "35729"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ionic-hello-world@ ionic:serve script 'ionic-app-scripts serve "--v2" "--address" "<IP_ADDRESS>" "--po
rt" "8100" "--livereload-port" "35729"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ionic-hello-world package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ionic-app-scripts serve "--v2" "--address" "<IP_ADDRESS>" "--port" "8100" "--livereload-port" "35729"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ionic-hello-world
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ionic-hello-world
npm ERR! There is likely additional logging output above.
npm ERR!      C:\Users\phanith\AppData\Roaming\npm-cache_logs\2017-03-24T06_52_49_748Z-debug.log
And this is the output of "ionic info":
Your system information:
Cordova CLI: 6.5.0
Ionic Frameowork Version: 2.3.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.4
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v7.7.4
Xcode version: Not installed
I was stuck with this since few days ago. Can anyone help me out with this problem? I cannot move on unless this problem solved. Thank you so much for your consideration.

Me too. Having same issue with a new ionic app. It just stays at ionic-app-scripts serve "--v2" "--address" "<IP_ADDRESS>" "--port" "8100" "--livereload-port" "35729"

Any comments or suggestions from ionic team are appreciated

Duplicate of https://github.com/ionic-team/ionic-cli/issues/2479


Fix systemd autostart to be more reliable

Fixes #56

Hey, took a while to get around to testing the change, but seems to work. Thanks a lot!

No worries, i completely understand :)


Correct typo in import statement

@xtate/compiled -> @xstate/compiled

Hmm, I do need to add a changeset as I want this update pushed to npm. I’m on my iPad, let me see how easily I can do that. (Pretty new to this whole pull request thing.)

Raising another PR with a changeset.
There's a very fine chance I'm doing this all sorts of wrong, so I won't be offended if someone tells me to stop.


update rather than replace passwd file

fixes https://github.com/openshift/s2i-python/issues/98

@GrahamDumpleton @mfojtik ptal.
@GrahamDumpleton this pretty much uses the code you provided in the issue (thanks!)

(will do follow on pulls to other repos once this merges)

LGTM.

will wait for @GrahamDumpleton :-)

What are you waiting for from me on this one?

@GrahamDumpleton does it look good to you?

Of what I remember of this, yes, looks okay.


Introduce "ondemand" linker sections

This is needed when the firmware is significantly bigger than the available
RAM.
This can be seen in action with the ARM64 demand paging support in PR #74129.

Pinned sections can still be used, right?

Well, you have to choose. Either you have explicit pinned sections and
everything else is implicitly evictable, or you have explicit on-demand
(aka evictable) sections and everything else is implicitly pinned. Both
tags may coexist of course.

Pinned sections can still be used, right?
Well, you have to choose. Either you have explicit pinned sections and everything else is implicitly evictable, or you have explicit on-demand (aka evictable) sections and everything else is implicitly pinned. Both tags may coexist of course.

Wonder if they should be make mutually exclusive by adding !LINKER_USE_ONDEMAND_SECTION to pinned section kconfig.

Nothing prevents both strategies from using the same backend. But their
initial state must differs.
In the explicit pinned model, everything is initially in memory and
stuff gets evicted when memory is tight. The backing store is used as a
swap space and is initially unpopu;ated. This assumes the firmware may
all fit in memory at boot time.
In the explicit on-demand model, most everything is initially in the
evicted state. The backing store already contains the evicted stuff,
most likely in read-only mode. This is especially useful when the
firmware is bigger than available RAM and no XIP is unavailable.
Where both strategies differ the most is in their initial MMU mappings.

@andyross @peter-mitsis ping


[FEATURE REQUEST] For template choice provide option to skip title/filename prompt

Is your feature request related to a problem? Please describe.
I use templater and I have a template that prompts the user for a variable. The variable is then used to rename the file. This leads to a double prompt.
Describe the solution you'd like

A switch to turn the filename prompt off.

Additional context
Currently I can use the command Templater: Create new note from template but it is a different flow that I don't use.

Nevermind, This can be solved by enabling "File Name Format" and providing a value.


Added exceptions in Google Drive sync process so that it fails correctly and moved the redirect url to a constant

I added an exception to the Google Drive sync process in case the user hasn't logged in to Google Drive.
Before my changes syncing via Google Drive didn't generate any errors if the user hadn't logged in. The bug is easy to reproduce:

Make a clean installation of this branch
Select Google Drive service for syncing
Click "Sync Now" without signing in to the Google Drive

Then the sync happily reported that 0 errors were generated even though nothing actually was synchronized because Google Drive wasn't even signed in.
I also added exceptions in a couple of other places, since they are supposed to be treated as a failure anyway. As far as I understand, SyncDataJob reports that sync was successful if no exceptions were generated during it, so I think it probably makes sense to put exceptions everywhere. From a bigger point of view it would have probably made more sense to make SyncDataJob work the other way around: to assume failure by default, unless the syncing process reported success, but I am not sure how it can be done.
I also moved redirect url into a constant so that it is in one place.

Thank you very much for fixing it and showing me how it should be done instead of simply fixing it! I am not very familiar with Kotlin, so I got scared when I attempted to use "const" and it said something about companion objects :) So I am very thankful for the learning opportunity.


Missing "toISO8601String" methods in NSDate

Documentation says that the method should be available in both DateInRegion and NSDate, but I could not find it. Is it a bug in documentation or a missing method? Thanks.

Thanks for the issue.
.toISO8601String is replaced by .toString(DateFormat.ISO8601)
Unfortunately the string functions have not been fully documented yet and should be added to the upgrade guide. Apologies for the time wasted, but Daniele and I decided to publish the v3 library before fully completing the docs as v2 urgently needed an upgrade.
This should work for both:
let dateStr1 = DateInRegion().toString(format: DateFormat.ISO8601)
let dateStr2 = NSDate().toString(format: DateFormat.ISO8601)

Please let us know whether or not this works for you.

That works well, thanks!