ios - set extensions bundle id based on its provisioning profile

Describe the solution you'd like
Main app bundle id is set at build runtime by using the one specified into provisioning profile. As confirmed by support, extensions bundle id is taken from source repository and can't be changed at build runtime. Would be very useful if the behaviour of extensions bundle id is like the main app's one.

@simonetodisco Thanks for this feature request! We'll keep this open as a possible enhancement for extensions.

@nilofer @simonetodisco any idea where the extension's bundleid is grabbed from? i have a case where we specify the bundleid using a target/scheme combination and the build scripts don't seem to be respecting this. instead they appear to be using the value from the first buildsettings node they find in the xcode config

I'm seeing the same thing, @akempe -- frustrating!!

do we have any solution for this ?


PSR4 Autoloading with composer 2

There are a lot of depcrecation notices when autoloading classes with composer. The new classes won't be autoloaded with v2.
We need to rename the "resources" folder to "Resources" to be compliant with psr4.
I submitted a PR.

#27


Add youtubedl.mattjeanes.com to the default whitelist

One of the main reasons why people use Streamcore is so that they can play youtube videos with some sort of ytdl api.
The only current candidate I have to potentially whitelist is https://github.com/MattJeanes/YouTubeDL, because it's open source and owned by someone who is at least decently known in the gmod community.
I think this is a pretty low risk thing to add since it's somewhat easy to prove as open source and you can always just take it off your custom client whitelist. Leaving this open in case for any objections or if someone has a more reputable api.
(Also if you want to ask about gaerrison's api or others, they aren't owned by particularly reputable people nor are they open source, so not happening.) (Also I don't know if you could have a purely github hosted ytdl repo, if so please let me know because that'd kind of void the need for this.)

Nobody has spoken so I'll add it. We'll see if there's any problems if/when this gets ported to wiremod.


IndexError: list index out of range

Hi, I am trying to run the example script:
from scweet import scrap
from user import get_user_information, get_following, get_followers
following, followers, join_date, location, website, description = get_user_information("realDonaldTrump")
print('following:'+following+'\nfollowers: '+followers+'\njoin_date: '+join_date+ '\nlocation: ' +location + '\nwebsite: '+website + '\ndescription: '+description)
And am facing the following issue:
Traceback (most recent call last):
File "user_data.py", line 4, in
following, followers, join_date, location, website, description = get_user_information("realDonaldTrump")
File "D:\Twitter\Scweet\Scweet\user.py", line 8, in get_user_information
driver = utils.init_driver(headless=headless)
File "D:\Twitter\Scweet\Scweet\utils.py", line 187, in init_driver
chromedriver_path = chromedriver_autoinstaller.install()
File "D:\Twitter\Scweet\scweet-venv\lib\site-packages\chromedriver_autoinstaller_init_.py", line 15, in install
chromedriver_filepath = utils.download_chromedriver(cwd)
File "D:\Twitter\Scweet\scweet-venv\lib\site-packages\chromedriver_autoinstaller\utils.py", line 166, in download_chromedriver
chrome_version = get_chrome_version()
File "D:\Twitter\Scweet\scweet-venv\lib\site-packages\chromedriver_autoinstaller\utils.py", line 117, in get_chrome_version
version = process.communicate()[0].decode('UTF-8').strip().split()[-1]
IndexError: list index out of range
Please help!! Thank you.

Hi. Do you have chrome installed in your system ?

Hi. Do you have chrome installed in your system ?

I had not installed Chrome. What a bummer!! The script works now! Thank you!

I had not installed Chrome. What a bummer!! The script works now! Thank you!

@the-data-mogul  Hhahha, it's ok. It heppens.

@the-data-mogul  Hhahha, it's ok. It heppens.

我安装了chrome，但还是出现了这个问题，请问怎么办

以前可以使用，后来突然不行了


alter table drop column from partition

Tiny issue here: after droping column from partition system.columns data about colums size is not refreshed.


Hide list of Redmine targets if system has only 1 Redmine

Backup, Restore and Services pane has list of Redmine.
But almost system could have only 1 Redmine.
So app should hide this list because it occupy extra space and it is lengthy.
So it should change the existing behavior to the following behaviors:

If system has only 1 Redmine, list is hidden
If system has multiple Redmines, list is visible

Close


Should skip @ignore token

Although this is not going to be in the docs, evaluates it.
Re: [B] module.exports in BoolJS/booljs-api

:+1: will fix in the next release!

:+1: :smile:

Done. :shipit:


Building a Comprehensive Reputation System for the Stacks Blockchain

Grant Proposal: Building a Comprehensive Reputation System for the Stacks Blockchain
Applicant: Trajan ZeroAuthority
Project Title: Empowering the Stacks Community: Building a Decentralized Reputation System
Total Requested Funding: $150,000
Project Summary:
This proposal outlines the development of a comprehensive, on-chain reputation system for the Stacks blockchain. This system will address the current lack of trust and incentive for user contributions within the Stacks ecosystem. We propose five key initiatives that will empower users, incentivize positive contributions, and foster trust:
1. Universal Profile Open Source

Problem: Currently, Stacks user profiles are limited, hindering user identity and expertise showcasing.
Solution: Develop an open-source universal profile for all Stacks wallets and authenticated users. This profile will allow users to store and share personal information, creating a richer user experience.
Impact: Increased user engagement, improved communication and collaboration within the community, ability for users to build their personal brand.

2. On-chain Reputation Layer

Problem: The absence of an on-chain reputation system makes it difficult to establish trust and verify user contributions within the ecosystem.
Solution: Build a robust, on-chain reputation layer for Stacks and Bitcoin, integrating with existing platforms like Stacks Discord and Stacks Github. This layer will track user contributions (e.g., posts, code commits, project completions) on the blockchain, fostering trust and transparency.
Impact: Increased trust in user interactions, verification of user contributions and expertise, ability to identify valuable community members.

3. Open Bounty Reputation

Problem:  There's a lack of incentive for users to actively contribute to the Stacks ecosystem.
Solution: Create an open bounty system leveraging Clarity smart contracts. Users will earn on-chain reputation for completing tasks and contributing to projects. This system incentivizes valuable participation and empowers users to build their reputation.
Impact: Increased user participation in ecosystem development, incentivizes valuable skill contribution, empowers users to build a verifiable reputation.

4. Non-transferrable NFT Badges

Problem: The current system lacks a visual representation of user achievements and expertise.
Solution: Design non-transferrable reputation badges as NFTs (Non-Fungible Tokens) with Clarity contracts. These badges will visually represent user achievements and expertise, promoting transparency and fostering trust within the community.
Impact: Easy identification of user achievements and expertise, promotes transparency and trust in user interactions, creates a sense of accomplishment and gamification within the community.

5. Clarity Development Tools

Problem:  Existing tools may not provide adequate security scanning for Clarity smart contracts.
Solution: Develop a Clarity code library and tools for automated security scanning and code analysis. This open-source tool will be integrated with platforms like zeroauthority.xyz and allow developers to scan code repositories on Github, enhancing the security of Stacks applications.
Impact: Improved security posture of Stacks applications, increased developer confidence in code quality, fosters a more secure and reliable Stacks ecosystem.

Overall Impact:
This project will have a significant impact on the Stacks ecosystem by:

Empowering users:  Enabling users to build their reputation and showcase their value.
Encouraging participation:  Incentivizing positive contributions, fostering a more active community.
Building trust:   Creating verifiable records of user activity and contributions.
Enhancing security:    Providing developers with tools for secure code development.

Project Timeline:
The project will be delivered in phases over a period of 9-15 months.
Budget:
The total requested funding is $150,000.
Conclusion:
This grant proposal presents an initiative to build a comprehensive, on-chain reputation system for the Stacks blockchain. This system will empower users, incentivize positive contributions, and build trust within the Stacks community. We are confident that this project will be a valuable asset to the Stacks ecosystem and contribute significantly to its growth.
Additional Information:

we built an entire platform with on-chain reputation with the initial 25,000 and we have paid out of pocket since 2022, which DeGrants on Stacks and STX users benefit today
organization's experience in blockchain development (Describe any past projects or contributions to the Stacks community).
detailed project plan with specific milestones and deliverables to be added.
resumes &/or profiles of key team members involved in the project

Thank you for considering our proposal!

#17 | Security-focused Clarity Course
Develop a comprehensive educational curriculum covering smart contract development
Zero and HODLSTX are exceptionally well-suited for this bounty due to our extensive experience and proven track record in the field.
Zero brings over 15 years of experience as a security engineer, specializing in standard deployments, SaaS applications, and privacy in technology risk. This deep expertise ensures robust and secure development practices tailored to meet modern security standards.
Together, Zero and HODLSTX have developed innovative applications using Clarity language, establishing a leading platform for onchain gigs and endorsements. Our notable projects include:

Zero Authority: ZeroAuthority.xyz - A platform facilitating onchain gigs. Our applications are actively used by notable entities in the ecosystem such as HeroGamer and DeGrants. For an example of our work, visit HeroGamer Gig.

Trajan: Trajan.app - A pioneering platform for onchain endorsements. For a demonstration of its use, see Endorsement Example.

Our solutions are not only innovative but also widely adopted and trusted within the community, reflecting our ability to deliver reliable and impactful technology. This track record of success and our comprehensive experience make us the perfect fit for this bounty. We have worked with web3 security auditors and developers like Friedger.
Phase 1: Planning and Research (8 weeks), Cost: $12,000
Identify target audience needs, define course structure, and gather resources. Research Clarity code libraries and tools for security scanning. Develop a detailed project plan with timelines, deliverables, and assigned responsibilities. Compile existing materials and engage experts for content creation.
Phase 2: Development and Production (8 weeks), Cost: $53,000
Create comprehensive course content, including written materials, video lectures, and practical exercises. Develop and integrate Clarity code libraries and security scanning tools. Publish tools on GitHub and zeroauthority.xyz. Conduct beta testing, gather feedback, and refine content and tools accordingly.
Phase 3: Launch and Evaluation (6 weeks), Cost: $5,000
Launch the course with a marketing campaign and provide access to materials and tools. Offer support through forums, Q&A sessions, and workshops. Collect feedback and usage data, evaluate the course's effectiveness, and identify areas for improvement. Plan for regular updates and continuous improvement.
The cost per hour for the entire project is approximately $22.08.
To calculate the total cost per hour for the entire project, we first need to convert the total project duration from weeks to hours.
Total project duration: 22 weeks
Since there are 7 days in a week and 24 hours in a day:
Total project duration in hours = 22 weeks × 7 days/week × 24 hours/day
Total project duration in hours = 22 × 7 × 24 = 3,168 hours
Now, to find the cost per hour:
Cost per hour = Total project cost / Total project duration in hours
Cost per hour = $70,000 / 3,168 hours ≈ $22.08/hour
So, the cost per hour for the entire project is approximately $22.08.

On May 17, 2024, at 14:56, Stacks Foundation<EMAIL_ADDRESS>wrote:
Thank you for your submission! Your application will be reviewed and a community contributor or Stacks Foundation staff member will be in touch.

To calculate the total cost per hour for the entire project, we first need to convert the total project duration from weeks to hours.
Total project duration: 22 weeks
Since there are 7 days in a week and 24 hours in a day:
Total project duration in hours = 22 weeks × 7 days/week × 24 hours/day
Total project duration in hours = 22 × 7 × 24 = 3,168 hours
Now, to find the cost per hour:
Cost per hour = Total project cost / Total project duration in hours
Cost per hour = $70,000 / 3,168 hours ≈ $22.08/hour
So, the cost per hour for the entire project is approximately $22.08.

On May 17, 2024, at 14:56, Stacks Foundation<EMAIL_ADDRESS>wrote:
Thank you for your submission! Your application will be reviewed and a community contributor or Stacks Foundation staff member will be in touch.


Update queries so that unsubmitted works as intended

Context
The way submitted_at is updated has changed in the 2024 recruitment cycle. In the 2023 cycle it meant  all the application choices on the application form had been submitted. But in 2024, it just means that at least one of the choices has been submitted.
I've gone through all the identified workers and made a judgment about whether or not they should be updated to ensure we send messages / cancel applications for the right group of people.
Changes for each individual worker are listed below. Where the worker is related to end of cycle, that's noted.
CancelUnsubmittedApplicationsWorker (end of cycle related))
Changes
Removes the filtering for unsubmitted application_choices.
Why?
If submitted_at is nil, then ALL the application_choices are unsubmitted now.
We no longer need to check that an unsubmitted application_choice exists.
SendEocDeadlineReminderEmailToCandidatesWorker (end of cycle related)
Changes
We want to add two additional filters
  .where.not(candidates: { submission_blocked: true })
  .where.not(candidates: { account_locked: true })

Why
So that we don't send messages to people who can't actually submit an application.
No change related to submitted_at. We've written the email with the audience described in mind.
SendNewCycleHasStartedEmailToCandidatesWorker (end of cycle related)
Changes
Removes specific years. (2023 and 2024)
Why

We no longer need to be specific about year of the cycle. We can use 'current' and 'previous' instead
The original query didn't actually look at unsubmitted... It assumed that the applications were unsubmitted because the query is done on the day apply opens. But for completeness, I've added it. (we don't want to send messages to someone who submitted as soon as apply opened)

SendStatsSummaryToSlack
Changes
No changes required
Why
Does not use the submitted_at in the queries. We are not looking at unsubmitted choices either. Just choices that are in specific states.
We are counting application choices. Eg 'submitted applications' is counting the number of choices that have been submitted. There can be multiple choices per application_form.
So the status of the application_form is moot.
SendWeeklyStatsSummaryToSlack
See WeeklyStatsSummary class
Changes
No changes required
Why
Does not use the submitted_at in the queries. We are not looking at unsubmitted choices either. Just choices that are in specific states.
We are counting application choices. Eg 'submitted applications' is counting the number of choices that have been submitted. There can be multiple choices per application_form.
So the submitted_at field on the application_form is moot.
SupportInterface::ApplicationsBySubjectRouteAndDegreeGradeExport
Changes
No changes required
Why
We have been generating the data to this specification (where.not submitted_at: nil) for the entire cycle, so to change the data now would make it incomparable to previous reports.
SupportInterface::ApplicationsByDemographicDomicileAndDegreeClassExport
Changes
No changes required
Why
We have been generating the data to this specification (where.not submitted_at: nil) for the entire cycle, so to change the data now would make it incomparable to previous reports.
NudgeCandidatesWorker
GetUnsubmittedApplicationsReadyToNudge
Changes
Replace .unsubmitted with unsubmitted application choices
Add filters to ensure we are only sending message to people who should receive them
Why
Using 'unsubmitted' changes the intended behaviour significantly. We want to nudge people with inflight applications.
We should only nudge people who can action things and who have subscribed to emails
GetIncompleteCourseChoiceApplicationsReadyToNudge
Changes
Add filters to ensure we are only sending message to people who should receive them
Why
Since the application has no application choices, the form should be unsubmitted (nothing to submit)
GetIncompletePersonalStatementApplicationsReadyToNudge
Changes
Replace .unsubmitted with unsubmitted application choices
Add filters to ensure we are only sending message to people who should receive them
Why
Using 'unsubmitted' changes the intended behaviour significantly. We want to nudge people with inflight applications.
We should only nudge people who can action things and who have subscribed to emails
GetIncompleteReferenceApplicationsReadyToNudge
Changes
Remove unsubmitted -- it's moot because they could not have submitted anything if they do not have application choices
Add filters to ensure we are only sending message to people who should receive them
Why
Using 'unsubmitted' changes the intended behaviour significantly. We want to nudge people with inflight applications.
We should only nudge people who can action things and who have subscribed to emails
Guidance to review
Link to Trello card
(Trello ticket)[https://trello.com/c/njdwKzXF]
Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated added to the Azure KeyVault

 CA: [Clock Workers] Assess impact of submitted_at on workers


Update README example with new ActiveSupport Notification syntax

#405 changed the subscription syntax to comply with ActiveSupport specification.
This Pull Request updates an example in the README that used the old syntax.

Awesome, thank you!


Header image aspect ratio depends on excerpt length

[x] This is a question about using the theme.
[ ] I believe this to be a bug with the theme --- not Jekyll, GitHub Pages or one of the bundled plugins.
[ ] This is a feature request.
[x] I have updated all gems with bundle update.
[x] I have tested locally with bundle exec jekyll build.

Environment information

OS: Ubuntu 14.04
Minimal Mistakes version: 3.4.4
github-pages version: ?

Expected behavior
I expect the aspect ratio of a header image to be the same whether I use that image is used as a regular image or as an overlay image with an excerpt.
Steps to reproduce the behavior
See example post here.
The front matter looks like this
---
title: Modularity in LaTeX
header:
  image: header.png
---

and the image has a certain aspect ratio as shown:

Now, if we change to overlay image with an excerpt,
---
title: Modularity in LaTeX
excerpt: blarg
header:
  overlay_image: header.png
---

then the image becomes much less tall, as shown here

Interestingly, if we leave the excerpt line out, the auto-generated excerpt is much longer, and as a result the header image is taller.
To produce this error, I cloned the repo, adjusted the configuration, and wrote the post linked above.

The "hero" headers are fundamentally different, which is why you're observing differences in how they look.
header:
  image: image-filename.jpg

Default header.image uses a <img> element which has some CSS on it to scale it to fit the full width of the screen. The height scales proportionally to the width maintaining the image's aspect ration.
header:
  overlay_image: unsplash-image-1.jpg

While header.overlay_image does not use an <img> element and instead adds it as a background-image to div.page__hero--overlay. Since that image is added via inline CSS it doesn't know what the aspect ratio of the image. It simply applies a background image to the parent container.
If more content is added to it making the container larger the image will appear taller.

If there's is less content it will appear shorter.

What you can do is add CSS to apply a height to that container. This could become problematic as the height will vary at different screen sizes, and will be especially hard to maintain if your images all have different aspect ratios.
I'm sure there is some sort of JavaScript magic you could apply, but that's out of scope of this theme.

What you can do is add CSS to apply a height to that container.

This leads to an obvious question: how does one apply CSS to specific elements, i.e. the height of the hero imagine on one specific post? I was trying to figure that out also in order to change the overlay title color, because some images make white titles hard to read. Unfortunately, I only figure out how to do this by editing the hard-coded value in _sass/_page.scss directly. Is there a way to edit the title color or image height on a per-post basis?

This hasn't been merged into master yet but there was an enhancement to allow custom classes.
The way this will work is you assign custom class names to a post or page's YAML Front Matter like so:
classes:
  - your-class-name

This will add your-class-name to the <body> element. Allowing you to specifically target the overlay with a selector like .your-class-name .page__hero--overlay, and then adding whatever CSS you need to style it.
I should be merging this into master shortly.

there's a discussion of custom classes in the docs, but you're saying that's not merged yet. In any case

How does one add inline CSS to classes defined in the front matter? A trivial example in the docs would be helpful.

Using custom classes seems a bit odd because we're then overriding CSS from _page.scss in our custom class. It's not obvious to me why the custom class properties would take priority. Is there some way to parametrize the stuff in _page.scss in a way that the parameters can be defined on a per-post basis?

I realize that in asking two questions here I might be going outside the bounds of a single issue. I can break up the discussion into smaller more focused ones if you prefer.

My bad. It was merged in. Too many themes too many issues too many PR, hard to keep it all straight :stuck_out_tongue:
You can't add inline CSS via Front Matter. You either have to add <style>your css</style> as part of the post/page's content or add those classes to main stylesheet.
The later is probably the better option. I'd create your own custom .scss, place it in _sass and then @import it into /assets/css/main.scss.
RE: 2. I get why that would be odd. Because of how the background images are assigned that's really the only option as you can't do it in _page.scss as that file doesn't read a post or page's YAML Front Matter.
Not saying it's an ideal option but it's certainly one of the more common approaches. Back when "art directed" posts were all the rage a few years ago that's how a lot of people did it eg: custom class overrides in the body of a post.
The custom classes take priority depending on the "cascade", hence the name CascadingStyleSheets. If you add a height or colors to .your-custom-class .whatever, it will take priority over .whatever because it of specificity. There are sites devoted to the topic that will explain it better than I can.

You can't add inline CSS via Front Matter. You either have to add  as part of the post/page's content...

Ewwwwww

...or add those classes to main stylesheet. The later is probably the better option. I'd create your own custom .scss, place it in _sass and then @import it into /assets/css/main.scss.

Aha! I may be missing something really obvious, but even if I do this, how would I set attributes like the title color on a per-post basis? See next item.

RE: 2. I get why that would be odd. Because of how the background images are assigned that's really the only option as you can't do it in _page.scss as that file doesn't read a post or page's YAML Front Matter.

Yeah this gets at the real problem. Is there some way to parametrize the sass in a way that we can pick values of the parameters on a per-post content? If not, I'd really like to figure out a way to set that up.

Back when "art directed" posts were all the rage a few years ago that's how a lot of people did it eg: custom class overrides in the body of a post.

I see how that works, but it's not DRY and it messes up the separation of content and styling, so I'm interested in finding another way.

The custom classes take priority depending on the "cascade", hence the name CascadingStyleSheets.

I should have been more clear. I understand that CSS uses cascade to determine precedence. It's just not obvious whether custom classes are higher or lower in the cascade than the defaults because there's no specification about how custom classes propagate to the final document.
Thanks for your help so far.

To be clear, I am totally happy to do the legwork in setting up a way to parametrize CSS attributes on a per-post basis (assuming it's possible). Right now I'm trying to understand how the present system works and understand the boundaries of what's possible.

The present system isn't meant to be a full on custom CSS for every post/page slution. The theme isn't built for that nor will it ever be.
It's merely adding the ability to add custom classes to the body to use a simple JS hooks or to style an element here and there. If you're looking to inject custom CSS into every page to change title colors or anything else then the better solution would be to add your own custom Liquid to the `_layouts.
I have yet to see a DRY approach to this problem. It's possible if you're doing something simple like wanting an inverted style for every element to improve light on dark then sure. But if you're looking to do more than all bets are off unless you want to build a custom CSS file for every post/page.

And no, you can't currently do that with the way Jekyll reads assets. What you're looking to do is really not possible (well not easily at least). You'd essentially need to evaluate the Sass file(s) against every post/page to pull in YAML Front Matter to do what you want. And that likely wouldn't work as each post/page would just end up overwriting each other unless you're naming classes specifically.
My understanding of Jekyll is that isn't something done out of the box. You can ask around on talk.jekyllrb.com but without a custom plugin I think you are out of luck.

Two solutions I can think of, both of which involve you customizing layouts and includes to bend it to your will. Not something I'm interested in adding to the theme as it opens the doors to a million and one customizations as everyone will want something different. But if you're interested here's what you could do:
Option 1
Jam custom variables in _config.yml which are accessible from the site object. /assets/css/main.scss could then pull from those as it is processed by Jekyll. Any of the partials would not though since they don't contain YAML Front Matter and are treated by Jekyll as static assets.
A real simple example:
_config.yml:
custom-var1: green

/assets/css/main.scss:
.my-custom-var1 {
  color: site.custom-var1;
}

Option 2
Edit layouts and includes adding conditional statements where you want to apply customizations.
Example:
Say you want to change the post title's color using a value specified in it's YAML Front Matter.
post/page YAML:
title-color: green

And then modify the template:
<h1 class="page__title" {% if page.title-color %}style color: "{{ page.title-color }};"{% endif %}>

As you can see this has the potential to turn into a maintenance nightmare.
Again this is probably something that is super out of scope with this theme and dips more into "how to use Jekyll" land. I'd read out on talk.jekyllrb.com or Stackoverflow. Perhaps there are others who have a better solution.

The present system isn't meant to be a full on custom CSS for every post/page slution. The theme isn't built for that nor will it ever be.

Of course not. You must get a lot of people expecting your theme to solve all the world's problems...

If you're looking to inject custom CSS into every page to change title colors or anything else then the better solution would be to add your own custom Liquid to the `_layouts.

Yeah, that seems like a half-decent approach. Will use that as a stop-gap for now. I'll see if I can figure out a better way though.
Thanks for your help.

Of course not. You must get a lot of people expecting your theme to solve all the world's problems...

Naturally :wink:

@mmistakes
I am trying to set a min-height for the overlay-image.
I can see that it is wrapped around the class ".page__hero--overlay. How do I overwrite this class or add more css class to the container of the overlay-image?


Travis build refactored

Hi, I've refactored the Travis build with the following changes:

Dependencies are now installed on lowest or latest version; this is mandatory because if a version is allowed we need to test it
PHPUnit is now pinned to ^6.0.13 because there are some issues with intermediate minor versions, never tested before this PR and point 1 got emerged
Symfony is now pinned to ^3.0 for the same reason, Travis fails with Symfony ~2.0 but previous Travis config didn't show it
Code Coverage is done in one build only, on the lowest PHP Version but with the latest dependencies; an ENV variable is set to be clear on the build
CS Fixes are checked on an own build without tests involved; an ENV variable is set to be clear on the build
PHP 7.2 is now tested, but allowed to fail
PHPUnit@dev is tested on latest PHP only to reduce build matrix

Looks nice, thx.

Dependencies are now installed on lowest or latest version; this is mandatory because if a version is allowed we need to test it

This would actually mean we would have to test EACH version. Not only the highest and lowest. But I get the point... at least a way to find stuff like 2.


Dialogs created by Dialogs on Windows don't have focus

This makes using dialogs without a mouse inconvenient. I noticed this when working with #4634 but this is more related to #4619.

I actually fixed this already as part of #4634. Decided to submit a separate issue because the problem is different and actually more severe than #4634.

Even after the initial fix, text entry boxes didn't have focus similarly as they had on Linux. This meant that possible initial text wasn't selected. Also that will be fixed as part of this issue.


blocking problem in NodeBB 1.18.X

Hi @oplik0 , how are you? Thanks again for the plugin.
We are using NodeBB 1.18.6 with Persona 11.2.21 and two-way block plugin 1.3.1
In case it is easy to fix, here are some problems with the plugin...
Let's say User A blocked User B,
User A does not see any posts of User B, or any topics started by User B; which is how it should work; however "in recent cards" (we use 2.0.19) User A can see the topic User B started and what he/she wrote.
Additionally, User B, unfortunately, can see what User A wrote if that is the last post (on the /recent page) of the topic, however, it works OK when User B clicks the topic title, User B cannot see the post of User A on the topic. Additionally, like the problem above User B can see the topic User A started and what he/she wrote.
So, if it is possible;

Can those topics on recent cards be blocked?
And, can you prevent User B see the last post of the topic on /recent page if that post belongs to someone blocked User B.

Thanks a lot.

I'll look into this after Christmas, hopefully I will find time to do this before end of the year :)

Thanks a lot @oplik0 , you are the best.
I have one more question (more like a feature request if you see this as a good addition to the plugin). We use the "browsing users" plugin, so avatars of the users browsing the same topic can be seen.  Do you think it is easy to block the appearance of the avatar of the blocked person on these pages?
So, in the end, this plugin will be more like the "blocking" function of the many social media sites. You do not see the blocked person and also his/her posts; and vice versa...

I'll have to look into how the browsing-users plugin works again, but IIRC it didn't work on per-user basis. I'll see what I can do though.

So, turns out it broke with NodeBB updates. I remembered that I worked on getting teasers to work!
I'll work on the browsing-users now, but I'll make a separate issue for that in case I'm not able to finish it today.

@oplik0 thanks a lot.

Should be fixed in v1.4.0:

GitHub release: https://github.com/oplik0/nodebb-plugin-two-way-block/releases/tag/v1.4.0
NPM: https://www.npmjs.com/package/nodebb-plugin-two-way-block/v/1.4.0

Hi @oplik0 , thanks a lot.
It looks like it is working well on /recent page. However last topics on /categories can be seen, and we are having errors on the log (which might be related).
[nodebb-plugin-two-way-block] encountered an error while processing teasers: TypeError: Cannot read properties of undefined (reading 'uid')
    at /home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:58:67
    at Array.map (<anonymous>)
    at Object.twoWayBlock.filterTeasers [as method] (/home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:58:17)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at fireMethod (/home/fsuzer/nodebb/src/plugins/hooks.js:137:11)
    at Object.fireFilterHook [as filter] (/home/fsuzer/nodebb/src/plugins/hooks.js:168:12)
    at Hooks.fire (/home/fsuzer/nodebb/src/plugins/hooks.js:105:17)
    at Topics.getTeasers (/home/fsuzer/nodebb/src/topics/teaser.js:89:18)
    at async Promise.all (index 0)

I wasn't actually able to replicate that issue, but tried to fix it based on the error log. If it still persists in 1.4.1 I'll try harder to find what might be going on :) Also<EMAIL_ADDRESS>now doesn't show blocked people (and with this plugin also doesn't show people who blocked you)

Hi @oplik0 , with 1.4.1 we do not get that error in the logs anymore. Thanks again 🙏

Hi @oplik0 , sorry for bothering you again. It works perfectly with the "browsing users" plugin. Thanks a lot for the integration.
And additionally, the plugin works perfectly on the threads, as well as on the /recent page...
However, we have problems in two places... the person who blocked you can be seen in the "recent cards" and also in the "most recent post" of the categories page(in teasers)...
When I refresh those pages when the blocking person is the last post owner, I keep getting these errors:
2022-01-15T03:16:36.077Z [4567/9407] - error: [nodebb-plugin-two-way-block] encountered an error while processing teasers: TypeError: Cannot read properties of undefined (reading 'uid')
    at /home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:68
    at Array.map (<anonymous>)
    at Object.twoWayBlock.filterTeasers [as method] (/home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:18)
    at fireMethod (/home/fsuzer/nodebb/src/plugins/hooks.js:137:11)
    at Object.fireFilterHook [as filter] (/home/fsuzer/nodebb/src/plugins/hooks.js:168:12)
    at Hooks.fire (/home/fsuzer/nodebb/src/plugins/hooks.js:105:17)
    at Topics.getTeasers (/home/fsuzer/nodebb/src/topics/teaser.js:88:18)
    at async Promise.all (index 0)
    at loadTopics (/home/fsuzer/nodebb/src/topics/index.js:93:80)
    at async Promise.all (index 0)
2022-01-15T03:21:47.396Z [4567/9407] - error: [nodebb-plugin-two-way-block] encountered an error while processing teasers: TypeError: Cannot read properties of undefined (reading 'uid')
    at /home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:68
    at Array.map (<anonymous>)
    at Object.twoWayBlock.filterTeasers [as method] (/home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:18)
    at fireMethod (/home/fsuzer/nodebb/src/plugins/hooks.js:137:11)
    at Object.fireFilterHook [as filter] (/home/fsuzer/nodebb/src/plugins/hooks.js:168:12)
    at Hooks.fire (/home/fsuzer/nodebb/src/plugins/hooks.js:105:17)
    at Topics.getTeasers (/home/fsuzer/nodebb/src/topics/teaser.js:88:18)
    at async Promise.all (index 0)
    at loadTopics (/home/fsuzer/nodebb/src/topics/index.js:93:80)
    at async Promise.all (index 0)
2022-01-15T03:23:06.008Z [4567/9407] - error: [nodebb-plugin-two-way-block] encountered an error while processing teasers: TypeError: Cannot read properties of undefined (reading 'uid')
    at /home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:68
    at Array.map (<anonymous>)
    at Object.twoWayBlock.filterTeasers [as method] (/home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:18)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at fireMethod (/home/fsuzer/nodebb/src/plugins/hooks.js:137:11)
    at Object.fireFilterHook [as filter] (/home/fsuzer/nodebb/src/plugins/hooks.js:168:12)
    at Hooks.fire (/home/fsuzer/nodebb/src/plugins/hooks.js:105:17)
    at Topics.getTeasers (/home/fsuzer/nodebb/src/topics/teaser.js:88:18)
    at async Promise.all (index 0)
2022-01-15T03:23:36.725Z [4567/9407] - error: [nodebb-plugin-two-way-block] encountered an error while processing teasers: TypeError: Cannot read properties of undefined (reading 'uid')
    at /home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:68
    at Array.map (<anonymous>)
    at Object.twoWayBlock.filterTeasers [as method] (/home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:18)
    at fireMethod (/home/fsuzer/nodebb/src/plugins/hooks.js:137:11)
    at Object.fireFilterHook [as filter] (/home/fsuzer/nodebb/src/plugins/hooks.js:168:12)
    at Hooks.fire (/home/fsuzer/nodebb/src/plugins/hooks.js:105:17)
    at Topics.getTeasers (/home/fsuzer/nodebb/src/topics/teaser.js:88:18)
    at async Promise.all (index 0)
    at loadTopics (/home/fsuzer/nodebb/src/topics/index.js:93:80)
    at async Promise.all (index 0)

I appreciate your help.

@AliCihan fixed it in 1.4.2. I missed one place where I also referenced uid in the way it was included previously in teaser data (now it's under teaser.user.uid instead of just teaser.uid)

thanks @oplik0 , I have upgraded and restarted, this time instead of "(reading 'uid')" error, we get "(reading 'user')" error...
2022-01-16T18:26:05.850Z [4567/24177] - error: [nodebb-plugin-two-way-block] encountered an error while processing teasers: TypeError: Cannot read properties of undefined **(reading 'user')**
    at /home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:68
    at Array.map (<anonymous>)
    at Object.twoWayBlock.filterTeasers [as method] (/home/fsuzer/nodebb/node_modules/nodebb-plugin-two-way-block/library.js:60:18)
    at fireMethod (/home/fsuzer/nodebb/src/plugins/hooks.js:137:11)
    at Object.fireFilterHook [as filter] (/home/fsuzer/nodebb/src/plugins/hooks.js:168:12)
    at Hooks.fire (/home/fsuzer/nodebb/src/plugins/hooks.js:105:17)
    at Topics.getTeasers (/home/fsuzer/nodebb/src/topics/teaser.js:88:18)
    at async Promise.all (index 0)
    at loadTopics (/home/fsuzer/nodebb/src/topics/index.js:93:80)
    at async Promise.all (index 0)

Alright, should be fixed correctly now :)
However, it still won't entirely work with recent cards after all. If a topic was created by and contains only replies from blocked users/users who blocked you it will show the original post.
This is an issue with the recent cards plugin and explicitly removing that initial post causes even worse issues (it shows a post from a different topic under the one that should be blocked for some reason)

@oplik0 thanks a lot. I believe the recent cards part is ok.
Thanks to you, we have eliminated many possible interactions between two users. Especially on regular topics, browsing user lists, and on the most recent reply part. That is good enough :) Many thanks 🙏
I have a quick question related to what you wrote just above, when there is a newly created topic by a user that blocked you, in the previous versions of the plugin we were not seeing the teasers on /categories page, instead it was showing the topic that comes one before... But these new versions, if that is the only post on the newly created topic, it shows the person and his/her post even in the teaser. Do you think it is tricky to reverse this to the old version? If it is tricky or breaks some other things, it is ok though.

I'll have to check again how it's handled, but I'm fairly sure it was a change in NodeBB. Since all I'm doing is passing an empty teaser array if whole topic should be blocked, and that behavior hasn't changed.
I'll look into it later, but not today unfortunately.

Yeah, the issue is that if I try to add teasers from different topics to the mix things start mixing and you start seeing topics with teasers from different ones.
In the end the most reasonable behavior I was able to get here happens when, if all teasers are blocked, I return undefined, as then recent cards don't break as badly (they show an empty teaser instead of shifting all further teasers a card left), and stock NodeBB teaser spots show no new posts instead of the blocked teaser.
It's not perfect, but NodeBB and recent cards would need to be modified for this to work properly, and I don't really want to undertake that effort myself.

dear @oplik0 , thank you very much. 🙏
this 1.4.4 version works perfectly; teasers are fixed and empty card in recent cards is no problem at all... Additionally, our log is clear, there is no more error coming from the two-way-block plugin. Thank again, you are the best 👍


[HOLD Next Steps Auth Migration][$250] Expense status doesn't update after completing the action

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

Version Number: 9.0.17-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @saracouto
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1722617920576379
Action Performed:

Submit an expense and get a violation
Fix the violation
Violation message doesn't update in the upper side of the screen

Expected Result:
Once the user clears the violation, the message should update from "Waiting for Sara Couto to fix the issue(s)" to the corresponding next step
Actual Result:
The message "Waiting for Sara Couto to fix the issue(s)" was still there even after fixing the violation
Workaround:
unknown
Platforms:

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

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

Screenshots/Videos

https://github.com/user-attachments/assets/013b1346-7811-4300-a4f7-2d22f153a80d

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01bfe746236df54daa
Upwork Job ID:<PHONE_NUMBER>521988875
Last Price Increase: 2024-08-14
Automatic offers:

rayane-djouah | Reviewer | 103528411
dominictb | Contributor | 103528413

Issue OwnerCurrent Issue Owner: @rayane-djouah

Moving to #wave-control as it's optimistic next steps/violations related. CC: @dangrous @dylanexpensify

assigning myself so I can take a look when proposals are approved!

Adding another BZ - I'll be out until 8/21

Yep, looks good to me! I'm wondering - to solve the "There's no violation before, but after edit there's violation" case, could we just do: currentTransactionViolations.length != nextViolationOnyxUpdate.value.length?

Nice, @dominictb when can we get the PR raised for review?

Okay so in talking with @mountiny and trying to make this work on the backend, it's going to bog down our code speed and also just be very tricky to do it currently. However! We're in the process of migrating the next steps code, and once that's done we should be able to fix this much more easily.
It does mean in the meantime, though, that we won't want to merge this front-end fix if it will just be overwritten by the backend. So I think this (and the PR, which I'll post on too) will be on hold for the next steps migration to auth. Sorry for the trouble!

Still on hold Melvin, don't close this.

We've actually got a temporary fix that should get this moving again, should be merged soon. We're still doing the migration, but I'm pretty sure this will work in the meantime.

Okay I thinkkkkk this is deployed. Can we retest and see if it's fixed?

hrm can you let me know how you set up the workspace / rules / etc. so I can try to replicate? I've found one place in the code that I can fix, but I think there's another one.
Also @mountiny did we figure out how to fix that issue with the cached violations? That's not this bug, but it's related.

Also @mountiny did we figure out how to fix that issue with the cached violations? That's not this bug, but it's related.

I think yes, will send you a PR

This is the PR btw https://github.com/Expensify/Web-Expensify/pull/44311 however, after testing it locally the cache seems to not get updated  before the report next steps are computed. It will require more digging 🕳

Thanks @Dominic! So we're looking at two next step issues (cc @mountiny).
For a policy on Instant Submit, we're hitting this block even if a report has violations. We should probably add a condition there, that's relatively easy, and doesn't change any existing tests.
For a policy on manual submit, we SHOULD be hitting this block, but we're not because the logic is checking a lot of stuff about that specific user, and it's conflicting for some reason. So instead we're going down here. I think we can probably just drop everything after $hasViolations since everything is more streamlined now? But I'm not 100% sure. The tests would need some adjustment but I'm hopelessly confused now as to what is "expected".

@dangrous sounds right, but I agree this is really finicky and gotta be careful around the test

So I think a lot of the tests are messed up, annoyingly. E.g they're creating reports with expenses that have violations, when that's not the behavior they're testing. See my latest comment on https://github.com/Expensify/Web-Expensify/pull/44527 . I'm trying to power through and make these changes correctly, but a little stuck

okay so the caching is fixed, the instant submit case is fixed, I just need to implement the manual submit case. And then we should be good?

okay I think I got all of it in that PR - will take it out from draft momentarily

Issue not reproducible during KI retests. (First week)

Amazing! Where do we stand on this issue, all? Assuming we can't reproduce anymore, can we just close? Is payment needed? Further front end work? Thanks!

this is on prod now, so bumping ^ - thanks!

Issue not reproducible during KI retests. (First week)

New version of the fix for this is now in backend review!

Issue not reproducible during KI retests. (Second week)

Issue not reproducible during KI retests. (Third week)


CI: Build and test using GitHub Actions

This commit builds all executables and runs the unit tests whenever a
push (to any branch) happens or a pull request gets created.
Please note: While compilation errors break the build, failing tests do
not as there are currently failing unit tests in master.
Signed-off-by: Reto Schneider<EMAIL_ADDRESS>

LGTM


sched: Remove the unnecessary DEBUG_TCBINFO option

Summary
since the linker can remove g_tcbinfo, if no code really reference it
Impact
gdb debugging
Testing
ci

@Ouss4 , @gustavonihei I think you both wrote/worked this/in file

@Ouss4 , @gustavonihei I think you both wrote/worked this/in file (arch/xtensa/src/common/xtensa_tcbinfo.c)

The point that @xiaoxiang781216 is making is that the are just data definitions in a static library.  It doesn't need to be built conditionally because it will not be drawn into the build from the library if it is not referenced by anything.  Nothing else is changed.

@Ouss4 , @gustavonihei I think you both wrote/worked this/in file (arch/xtensa/src/common/xtensa_tcbinfo.c)

The point that @xiaoxiang781216 is making is that the are just data definitions in a static library. It doesn't need to be built conditionally because it will not be drawn into the build from the library if it is not referenced by anything. Nothing else is changed.
There are a few additional changes here that don't related to the title or description.

Corrects a register name

These changes are moved to https://github.com/apache/nuttx/pull/9859.

Removes TCB_STACK_OFF and TCB_STACK_SIZE_OFF (unused?)

Good catch! it's fixed by https://github.com/apache/nuttx/pull/9878. Both fields are used to support TRACE32 thread awareness debugging.

@Ouss4 , @gustavonihei I think you both wrote/worked this/in file (arch/xtensa/src/common/xtensa_tcbinfo.c)

The point that @xiaoxiang781216 is making is that the are just data definitions in a static library. It doesn't need to be built conditionally because it will not be drawn into the build from the library if it is not referenced by anything. Nothing else is changed.
There are a few additional changes here that don't related to the title or description.

Corrects a register name

These changes are moved to https://github.com/apache/nuttx/pull/9859.

Removes TCB_STACK_OFF and TCB_STACK_SIZE_OFF (unused?)


Clair

Clair scanning solution for docker images.
Prerequisites:
RDS database, DB should be populated with vulnerabilities manually by running a Clair container (https://github.com/coreos/clair/tree/v1.2.6).
Not doing so, will result in: "No vulnerabilities were detected in your image."
Cartridge issue:
In the pipeline view DB credentials are exposed.

Could you please cover Prerequisites in README of this cartridge.

Canceling this PR due to Clair was declined in a favor of Anchore.


Launch error

Hello, I'm having problems when lauching the program.
This is the errors i'm getting :
2023-10-04 16:51:06 Traceback (most recent call last):
2023-10-04 16:51:06   File "app.py", line 17, in
2023-10-04 16:51:06     from api import ModelMetadataAPI, ModelPredictAPI
2023-10-04 16:51:06   File "/home/max/api/init.py", line 16, in
2023-10-04 16:51:06     from .metadata import ModelMetadataAPI  # noqa
2023-10-04 16:51:06   File "/home/max/api/metadata.py", line 16, in
2023-10-04 16:51:06     from core.model import ModelWrapper
2023-10-04 16:51:06   File "/home/max/core/model.py", line 19, in
2023-10-04 16:51:06     import tensorflow as tf
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow/init.py", line 102, in
2023-10-04 16:51:06     from tensorflow_core import *
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow_core/init.py", line 28, in
2023-10-04 16:51:06     from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
2023-10-04 16:51:06   File "", line 1019, in _handle_fromlist
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow/init.py", line 50, in getattr
2023-10-04 16:51:06     module = self._load()
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow/init.py", line 44, in _load
2023-10-04 16:51:06     module = _importlib.import_module(self.name)
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/importlib/init.py", line 127, in import_module
2023-10-04 16:51:06     return _bootstrap._gcd_import(name[level:], package, level)
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow_core/python/init.py", line 52, in
2023-10-04 16:51:06     from tensorflow.core.framework.graph_pb2 import *
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow_core/core/framework/graph_pb2.py", line 16, in
2023-10-04 16:51:06     from tensorflow.core.framework import node_def_pb2 as tensorflow_dot_core_dot_framework_dot_node__def__pb2
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow_core/core/framework/node_def_pb2.py", line 16, in
2023-10-04 16:51:06     from tensorflow.core.framework import attr_value_pb2 as tensorflow_dot_core_dot_framework_dot_attr__value__pb2
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow_core/core/framework/attr_value_pb2.py", line 16, in
2023-10-04 16:51:06     from tensorflow.core.framework import tensor_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__pb2
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow_core/core/framework/tensor_pb2.py", line 16, in
2023-10-04 16:51:06     from tensorflow.core.framework import resource_handle_pb2 as tensorflow_dot_core_dot_framework_dot_resource__handle__pb2
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow_core/core/framework/resource_handle_pb2.py", line 16, in
2023-10-04 16:51:06     from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/tensorflow_core/core/framework/tensor_shape_pb2.py", line 42, in
2023-10-04 16:51:06     serialized_options=None, file=DESCRIPTOR),
2023-10-04 16:51:06   File "/opt/conda/lib/python3.7/site-packages/google/protobuf/descriptor.py", line 561, in new
2023-10-04 16:51:06     _message.Message._CheckCalledFromGeneratedFile()
2023-10-04 16:51:06 TypeError: Descriptors cannot not be created directly.
2023-10-04 16:51:06 If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
2023-10-04 16:51:06 If you cannot immediately regenerate your protos, some other possible workarounds are:
2023-10-04 16:51:06  1. Downgrade the protobuf package to 3.20.x or lower.
2023-10-04 16:51:06  2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).
2023-10-04 16:51:06
2023-10-04 16:51:06 More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates
I tried installing an older version of protobuf (3.20) and forcing it in the requirements.txt, i put the lastest version of tensorflow
Any idea what i'm doing wrong ?
Thanks

I added streamlit==1.9.0 in requirements.txt and it fixed it ...


Update Cake.Yarn NuGet package icon to the new Cake-Contrib logo for Cake addins

We've recently released new icons for Cake extensions, to help more easily differentiate Cake Addins, Modules, Recipes, etc.

More information: https://github.com/cake-contrib/graphics

:tada: The changes implemented in response to this issue shipped with Cake.Yarn v1.0.0
The release is available on:

:rocket: GitHub Release
:package: NuGet Package


testLogBackInSameRealmDownload occasionally fails on CI

Example: https://ci.realm.io/job/objc_pr/5257/configuration=Release,target=osx-object-server,xcode_version=8.3.3/console
Test Case '-[RLMObjectServerTests testLogBackInSameRealmDownload]' started.
/Users/realm/workspace/objc_pr/configuration/Release/target/osx-object-server/xcode_version/8.3.3/Realm/ObjectServerTests/RLMObjectServerTests.mm:742: error: -[RLMObjectServerTests testLogBackInSameRealmDownload] : ((3 == c) is true) failed - Expected 3 items, but actually got 1 (parent)
Test Case '-[RLMObjectServerTests testLogBackInSameRealmDownload]' failed (1.388 seconds).

Hopefully fixed by #5184.


CEPH RBD Provisioner Creates PV that fails to attach

I have setup a CEPH cluster. Independent of that I have followed processes found online to setup RBD provisioning.
The process I've followed is found here:
https://medium.com/velotio-perspectives/an-innovators-guide-to-kubernetes-storage-using-ceph-a4b919f4e469
This has largely worked. I have a "fast-rbd" storage class as follows:

I've created the various resources required for provisioning:

I've created the secrets to access ceph properly.

I am able to create PVC's that successfully bind to the PV created by the provisioner

However, the pod that I create fails to attach to the volume:

Looking at the pod in more detail I see the following

Googling the warning:

fail to check rbd image status with (executable file not found in $path)

I find various hits online including this one
It would seem that others have struggled with this. I dont fully understand the resolution described here. I am looking for guidance relative to getting past this problem
I believe the problem is that the running container does not include "rbd" in its path. Its not clear to me how this is properly resolved.
Guidance/Advice would be appreciated.
Dave

I am trying an CephFS provisioner instead of an RBD provisioner.
The PVC is not even binding:

Here is my cephfs provisioner

The corresponding claim:

The provisioner and other resources

and the secrets:

I'm just not sure how to debug this.

Your node needs to have the rbd binary installed and in $PATH.

Hi @wongma7
Thanks for the reply.
Which node are you referring to? Are you saying that the K8S worker node needs this? This seems a bit odd. It seems to place a burden on the worker node that is specific to RBD.
On a different note, can you take a look at my comment above. I am trying an alternative use of CEPHFS, rather than RBD. For some reason the CEPHFS provision fails to persistent volume.
I was wondering how the provisioner knows which pool to use. With the RBD provisioner, I explicitly specify a pool. However with the CEPHFS provisioner I only specify a claimRoot "/pvc-volumes". Its not clear to me how this root is mapped to a CEPH resource.

I'll write up my question about CEPHFS on a separate issue. I dont want it to get lost here. I'll keep this one focused on RBD.

Wow. I got RBD working. On Centos all i needed to do was
yum install centos-common

do not close this issue, for it not fix yet

Hi,
I had the same issue.
on debian installing the ceph-common package on the node resolved the issue


Expose resolver via API

Add a new field to the API to expose the "resolver" of a comment/
conversation. This is not available in the GitHub API v3.
Extend struct to contain "Resolver". Might be empty (nil).
Rename "Reviewer" to "Poster" in PullReviewComment to make it
clear this is the person posting a comment. The API is unchanged
('user').
Only the first comment of a conversation might have a resolver,
the others seem to be always nil.

@sotho build is failing. Not sure why just on pgsql though.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@dc56fb7). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master   #15167   +/-   ##
=========================================
  Coverage          ?   43.57%
=========================================
  Files             ?      668
  Lines             ?    80605
  Branches          ?        0
=========================================
  Hits              ?    35121
  Misses            ?    39779
  Partials          ?     5705

Impacted Files
Coverage Δ

modules/convert/pull_review.go
85.71% <100.00%> (ø)

Continue to review full report at Codecov.

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

@sotho please ajust / resolve conflicts - as per #15144


Need a mechanism for setting/getting an index for repeating forms.

I am creating a custom template in the same vein as the Repeating Section example.  I want to keep the custom template as generic as possible.  This means having the repeated forms and fields driven from an array in the model and fields defined in the implementors controller.  The challenge comes when I want to delete a particular "row" from the form.  I tried setting an index in the formState object and then retrieve that index when creating my delete button and store it in the data field of the delete button and retrieve it in the onClick function so I can remove that index from the array in the model.  However, the value that is stored for each repeated form is the last index value.  IOW the index value in the data object is the same, whatever the highest index value.
Here is a link to a jsBin that shows what I'm trying to do.  the number in the delete button is the index stored for that button.  I would expect the numbers to be 0, 1, 2, etc.  but they are all the same.  When you add a row you will see the value on all buttons increment by one each time the add button is pressed.
I suspect this has something to do with the formState object.  The docs say that object is shared by all fields in a form, but since each "row" in my form is a form, I wouldn't expect the formState object to be shared by all forms.  I'm sure I'm missing something but need a little guidance.
http://jsbin.com/dajode/3/edit?html,js,output

I don't know if this is related to the issue, but what I am most concerned about is that the name attribute of the fields in the repeat section are not unique.  I spent about an hour trying to figure out the issue is with that but to no avail.  I will revisit it tonight.

I am facing the same problem. Can u please help me in case u already found the solutions to this @jlowery457


[devtools] WebAuthn tab documentation

New documentation for WebAuthn tab
Target Live Date: 2020-10-01

[x] This has been reviewed and approved by (@chybie )
[x] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

Whoops!
There were 10 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-devtools/webauthn/images/02-enable-virtual-auth.png - Try to keep files below 500K, was 503K
src/content/en/tools/chrome-devtools/webauthn/images/03-authenticor.png - Try to keep files below 500K, was 549K
src/content/en/tools/chrome-devtools/webauthn/index.md#L14 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L19 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L22 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L42 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L47 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L54 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L73 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L77 - Line must be at most 100 characters

cc @nsatragno and @jschfflr for review.

Whoops!
There were 10 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-devtools/webauthn/images/02-enable-virtual-auth.png - Try to keep files below 500K, was 503K
src/content/en/tools/chrome-devtools/webauthn/images/03-authenticor.png - Try to keep files below 500K, was 549K
src/content/en/tools/chrome-devtools/webauthn/index.md#L14 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L19 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L22 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L42 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L47 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L54 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L73 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L77 - Line must be at most 100 characters

Whoops!
There were 10 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-devtools/webauthn/images/02-enable-virtual-auth.png - Try to keep files below 500K, was 503K
src/content/en/tools/chrome-devtools/webauthn/images/03-authenticor.png - Try to keep files below 500K, was 549K
src/content/en/tools/chrome-devtools/webauthn/index.md#L14 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L19 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L22 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L42 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L47 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L54 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L73 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L77 - Line must be at most 100 characters

Whoops!
There were 13 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-devtools/webauthn/images/02-enable-virtual-auth.png - Try to keep files below 500K, was 503K
src/content/en/tools/chrome-devtools/webauthn/images/03-authenticor.png - Try to keep files below 500K, was 549K
src/content/en/tools/chrome-devtools/webauthn/index.md#L14 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L19 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L22 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L42 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L47 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L54 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L73 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L77 - Line must be at most 100 characters
src/content/en/updates/2019/12/devtools.md#L218 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/12/devtools.md#L35 - Line must be at most 100 characters
src/content/en/updates/2019/12/devtools.md#L56 - Line must be at most 100 characters

Whoops!
There were 13 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-devtools/webauthn/images/02-enable-virtual-auth.png - Try to keep files below 500K, was 503K
src/content/en/tools/chrome-devtools/webauthn/images/03-authenticor.png - Try to keep files below 500K, was 549K
src/content/en/tools/chrome-devtools/webauthn/index.md#L14 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L19 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L22 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L42 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L47 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L54 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L73 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/webauthn/index.md#L77 - Line must be at most 100 characters
src/content/en/updates/2019/12/devtools.md#L218 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/12/devtools.md#L35 - Line must be at most 100 characters
src/content/en/updates/2019/12/devtools.md#L56 - Line must be at most 100 characters


Incompatible provider version jfrog/artifactory

It is not possible to automatically install the provider via terraform init on linux_amd64

As a workaround, I tried with all versions of jfrog/artifactory. But all of them are giving same error and also tried with commenting the version in jfrog/artifactory provider block. Still the same error.
Can anyone help me with this issue?
below is the versions.tf file where versions of required providers were declared.
terraform {
required_version = "~> 1.0"
backend "remote" {
hostname = "app.terraform.io"
organization = "platformzero"
workspaces {
name = "tf-artifactory-cloud"
}
}
required_providers {
artifactory = {
source = "jfrog/artifactory"
#version = "2.6.21"
}
}
}
provider "azurerm" {
#version = "= 2.89.0"
subscription_id = var.subscription_id
tenant_id = var.tenant_id
features {}
}

Hi,
I had no issue using the latest provider version 2.6.22 on my local machine (Kubuntu 21.10)
❯ terraform init --upgrade

Initializing the backend...

Initializing provider plugins...
- Finding jfrog/artifactory versions matching "2.6.22"...
- Using previously-installed jfrog/artifactory v2.6.22
❯ terraform init --upgrade

Initializing the backend...

Initializing provider plugins...
- Finding jfrog/artifactory versions matching "2.6.22"...
- Using previously-installed jfrog/artifactory v2.6.22

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

running the code in a pipeline (base os: ubuntu 20.04, hosted agent on Azure)  I ran into the same error
+ terraform init --upgrade

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding jfrog/artifactory versions matching "2.6.22"...
╷
│ Error: Incompatible provider version
│
│ Provider registry.terraform.io/jfrog/artifactory v2.6.22 does not have a
│ package available for your current platform, linux_amd64.
│
│ Provider releases are separate from Terraform CLI releases, so not all
│ providers are available for all platforms. Other versions of this provider
│ may have different platforms supported.

I'm having the same issues here on an Intel mac. I'm trying an upgrade from v2.2.12 to anything else and getting
Error: Incompatible provider version
│
│ Provider registry.terraform.io/jfrog/artifactory v2.2.11 does not have a package available for your current platform, darwin_amd64.
│
│ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have different platforms supported.

@stefanfreitag I suspect what you're seeing when it works is a previously downloaded instance of the provider, note the line:
- Using previously-installed jfrog/artifactory v2.6.22

That's what I see too when I revert back to my original version.

It seems that the key registered in the registry does not exist.
$ curl -s https://registry.terraform.io/v1/providers/jfrog/artifactory/2.6.22/download/darwin/amd64 | jq .
{
  "errors": [
    "signing key 6B219DCCD7639232 not found for jfrog"
  ]
}

We're experiencing the same issue, with all versions of the provider.

Same issue here with version 2.6.21, but not with 2.6.22. I am using Ubuntu 20.04.

@aliculPix4D Isn't it because you have 2.6.22 in your machine?
(Could you check ls .terraform/providers/registry.terraform.io/jfrog/artifactory/, please?)
I am getting the following error regardless of os or version.
$ curl https://registry.terraform.io/v1/providers/jfrog/artifactory/2.6.22/download/linux/amd64
{"errors":["signing key 6B219DCCD7639232 not found for jfrog"]}

I think this is probably happening in all versions.

@cappyzawa I just did a fresh terraform init; No issues with 2.6.22 for me.
ls .terraform/providers/registry.terraform.io/jfrog/artifactory/2.6.22/linux_amd64
LICENSE  README.md  terraform-provider-artifactory_v2.6.22

doing the same with 2.6.21 results in:
│ Error: Incompatible provider version
│
│ Provider registry.terraform.io/jfrog/artifactory v2.6.21 does not have a package available for your current platform, linux_amd64.
│
│ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this
│ provider may have different platforms supported.

hmmm.
Thanks for your checking!
There seems to be no workaround on the user side, so we have to wait for the maintainer to respond.

It's all automated - so, if there was an error, that would be a head scratcher. I'll talk to @alexhung

We are investigating this issue. It looks like TF replaces our existing signing key with a new one (that we requested to add), and thus all versions signed by the existing key are no longer valid on the registry. We're working with TF to attempt to recover the existing key.
Hold on tight.

Is there any workaround for this? Every version on registry.terraform.io/jfrog/artifactory appears to be broken for me.

Quick update: TF is in the process of restoring the public key to the registry. They also told us that once that's restored, all the existing binaries on the registry would be available to download once again.
Stay tuned. I'll update once I heard more.

Good news (mostly)
The public key is restored and I've published new version (2.6.23) to the registry and confirmed that it is available for install.
However, I was not able to install versions prior to 2.6.22 and I'm working with TF to determine the problem and any resolutions.

I could successfully pull version 2.6.23. However, I am getting 403 forbidden error when connecting to our artifactory. Could you advise what could have caused the reason? The credentials have not changed.

As far as we can tell the only available version is 2.6.23, all other versions are still not available. This is not such a good news since we broke backward compatibility at 2.2.15 and not all of us can readily upgrade. Very much stuck. Sigh.

@yoeluk Have you clear the cache directory and lock file? We tested all the way back to 2.6.15 and they are all available.

@alexhung yeah, we don't cache... this provider is used with several automatic pipelines and we don't commit the lock files to it either but it is possible that there is a CDN cache for my region I guess?

$ curl https://registry.terraform.io/v1/providers/jfrog/artifactory/2.6.23/download/linux/amd64 | jq                                                                                270ms  Tue 14 Dec 17:21:08 2021
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3297  100  3297    0     0  27940      0 --:--:-- --:--:-- --:--:-- 28179
{
  "protocols": [
    "5.0"
  ],
  "os": "linux",
  "arch": "amd64",
  "filename": "terraform-provider-artifactory_2.6.23_linux_amd64.zip",
  "download_url": "https://github.com/jfrog/terraform-provider-artifactory/releases/download/v2.6.23/terraform-provider-artifactory_2.6.23_linux_amd64.zip",
  "shasums_url": "https://github.com/jfrog/terraform-provider-artifactory/releases/download/v2.6.23/terraform-provider-artifactory_2.6.23_SHA256SUMS",
  "shasums_signature_url": "https://github.com/jfrog/terraform-provider-artifactory/releases/download/v2.6.23/terraform-provider-artifactory_2.6.23_SHA256SUMS.sig",
  "shasum": "ea27461d7f70018a4cdacca1e860866d87cc416519724f52aac068f83e14788e",
  "signing_keys": {
    "gpg_public_keys": [
      {
        "key_id": "6B219DCCD7639232",
        "ascii_armor": "-----BEGIN PGP PUBLIC KEY BLOCK-----\n\nmQGiBFICOY4RBADcL9qr50XhClS0yjpKipFKVaUutu7gFXeJdrNbMD3Dn9u0MH2R\nSDg2X8V7fH6UgpRxCKAijEjWohd3TfDv8Hlbdr2w9590GTsF71VqnXXXQIQRVedS\ntSWiPs+nmCrh5sokWQISgYU/iseDb+jqhwxEEflNXxcYKfCW5UL7GKypiwCgt0az\nIa3sIPlQf7cFHyFQ3C5tOAcEAJWzlTWll2SniJwCDzqTJr/UByNe8rmMUL8aanPb\nF6msrD+UUx6hhKZVrZseK4cL8CkW1JsDgtYL+2XyJkXokRjH6NWi69XksGbyl8Yw\nHOyY5WVIUelC4MWIjd3L7wEh4woS08TvxQO3uCL3o1zNmy++Oiax5+lUUBEBRvM9\nJoTfA/9aj7CpKsbcQfM9zfOytmKyr8/O1iQFXtEY8wN5RXfdCgPKtGL5fOWkjJOY\nEri/veTYDlNxzAuuyiz4dQmRsycdbbFQ+2Yg4GLsXYDVph/v9aQSVM2GATizY3fW\nZgfd0LcIrDZVEeemUrskusyoJB8QRNjadAJUlUSdudCK6Crd4bQbSkZyb2cgSW5j\nLiA8aW5mb0BqZnJvZy5jb20+iF8EExECAB8FAlICOY4CGwMGCwkIBwMCBBUCCAMD\nFgIBAh4BAheAAAoJEGshnczXY5IyL4AAnAlSgPskfgt5YkCRkhmkZ2DuH9yBAJ9C\nKahDyOvvGzFgYC7DdG/sdseVR7kCDQRSAjmOEAgA5JlfjGrnRmfIPIJ6zyt9BicZ\nQ6RRGIgQzwy/GdDHec2Oi9VQNJFXWZaqpol8DgwCADUftA+frfbrBDsgwL+oR0sx\nTK25g4zxd5z6CLrNjqfls6IY4HLFyZgJEM10/QhUiHFDnYfPPU5p16rqDcna1ILU\niF1Xwfghq+DyVDU5dSiMXkU++6U1VjK/LhVln40K4t9cQzvnVXVyufBI08NRFSY1\nI52ZWgMvhjyUL6f+N3lVpq1zJdr08EbTdp9y+gETfKx9kzvYKPnBsp1Kg2jEeG4l\numAu78BxokwVlxmDq6XB1rip4fmHfiSPROJ2XQdQYfN/g6N3qbwcbzW2Mlmw+wAD\nBQgA1+BbITyGkRqy12/4+j7uJh2gzcFO9/Qbo+FYMoHP4ecjHFS92Y0LddHKJHs8\nJebF0C8uIApO+X9ICoCUHLhbVlOV6nhgzPgKeuouC50dnXXt+/nInpW0C3w1Mzim\nqk6he/d1gw7J/u4aPro6QIOWnZQyHhMcUJRMa+K183oUUfs8SSV6kBGGrj+qzyzN\nwdz9HcW4CyTNafl0x0sT4EqaEyv1CYj+r84h8180akKF5QxdbnCOvTncm/zqTK4a\nkPiu+WBJ9rmWmJv2xWay+kt/FMAbnOU/0AIEdktiqpiO+NkVW+s2oOd+wMMu+5Ad\nxS8KgZ5hhx7DSuq5vC4zGbPSI4hIBBgRAgAJBQJSAjmOAhsMAAoJEGshnczXY5Iy\noU8AmPhzAkXBEO2Wet/qQMyHxqYYVZEAoKMW+THuhi0PhfdsOhWReceSOKpF\n=5Jv7\n-----END PGP PUBLIC KEY BLOCK-----",
        "trust_signature": "-----BEGIN PGP SIGNATURE-----\n\niQIzBAABCAAdFiEEUYkGV8Ws20uCMIZWfXLUJo5GYPwFAl9pIxwACgkQfXLUJo5G\nYPywsw/8C8bMZq3pDKfcfoUxVIJOj2uIwAMhze+Q1jqtAF9569oStLhZ0P3Qzgv9\neGQvFFa89kEJfjl6jAkps2fz0rJMF11e24NyPrR3iEdd/I/Rc3UMHD8NrlWzlQoX\nnkcLR2yA2RfpQGOecGSOzhnn3kuaOwUo7sLHXZwsLRXACT8VdoB4qd/KXvA0PwKv\nuPe0Q8M3Ho/EOoKO+2kznR+pSF0CczYNfM+cArHn4MgDOrierV5t3XZxDEpSg01A\ngWn3NLRQsgxlJuCvUfXjYQF6zpAeT00QHOLHyiZqpr9DDomvQW2IPBLq2SxQBss7\n6cfu/pNicxlM2n5yXFVxpoQZzVaB3PMRW+xh9IEWanRYSCVuWeWniWvoZ5P1Uhsv\ndXZWyf3egYXsjyHUt5tqkPcA5KDcy6j1Z9Oaj5lKckn7jkmD8t9LE2ohHPeLr1f6\n6dYziiFNJ7kjBqMFO5WV6XR4mWaeuEvwEh0sGEVmXPhHT9ZOEsICu7Srg6a15tCV\n5lmjW1Lnvdxg2HW6kFZCSHVKkbRqDqdQ1s4rg+DgVPAvFVYXY9WWEs0ZCttcDpY9\nD0wS6BPSRB/VbrxGq9s9lGxdKeGtOYsR6Zpej2CSJtIuPHWM4eTKXuchAdGlS+ea\nxUlzcGoRNKq4EGQtxeDqTVayEnmOmhn9+AmeQEZQYncRi8U7IRM=\n=vvCA\n-----END PGP SIGNATURE-----",
        "source": "",
        "source_url": null
      }
    ]
  }
}

but
$ curl https://registry.terraform.io/v1/providers/jfrog/artifactory/2.2.15/download/linux/amd64 | jq                                                                                135ms  Tue 14 Dec 17:21:14 2021
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    64  100    64    0     0    264      0 --:--:-- --:--:-- --:--:--   264
{
  "errors": [
    "signing key 6B219DCCD7639232 not found for jfrog"
  ]
}

@yoeluk I just tried the curl and looks like 2.2.15 is now available. Can you check?

@alexhung It is available now here too! Thank you so much for the support!!

Closing this issue as it looks like normal service has resumed.
Please create new issue if you encounter this signing problem.

I tried with 2.6.20, 21 and 22 and none of them works. I still get
 Provider registry.terraform.io/jfrog/artifactory v2.6.21 does not have a package available for your current platform, darwin_amd64.

Only working version is 2.6.23.

@alexhung We also experience same issue as Martin.

I can confirm that only some versions are working.
Working:
2.16.23
2.16.21
2.16.20
2.16.17
Not working:
2.16.22
2.16.19
2.16.18

@alexhung 2.2.15 still does not work for us in Terraform Cloud as well:
Provider registry.terraform.io/jfrog/artifactory v2.2.15 does not have a
package available for your current platform, linux_amd64.

@roehrijn I have the same behavior, certain versions work, and certain versions do not.
Based on some of the cache headers in the response:
$ curl -I -sSL registry.terraform.io/v1/providers/jfrog/artifactory/2.6.19/download/linux/amd64
HTTP/1.1 404 Not Found
Content-Type: application/json
Cache-Control: max-age=604800, stale-if-error=31536000, public
Last-Modified: Fri, 10 Dec 2021 17:11:14 GMT
Server: terraform-registry/1c82389f253fa390f5c803030473e97cd6b1134f
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Via: 1.1 varnish, 1.1 varnish
Content-Length: 64
Accept-Ranges: bytes
Date: Wed, 15 Dec 2021 14:17:31 GMT
Age: 85225
Connection: keep-alive
X-Served-By: cache-iad-kjyo7100070-IAD, cache-mdw17358-MDW
X-Cache: HIT, HIT
X-Cache-Hits: 1, 1
Vary: Accept-Encoding, X-Terraform-Version

I suspect that the Terraformer Registry is fronted by some kind of CDN, which may be caching the "bad" responses from the issue for a long time because they were 404s.

TF has confirmed that caching/CDN seems to be the issue. They are looking into this.

@martinm82 @szubster @roehrijn @maxdanilov @RussellRollins TF just informed me that they've purged the cache and all versions should be available.
Please report back here if you still have issue downloading your version. TF has another purge mechanism that is "more heavy-handed". 😄

I'm still seeing some issues from my local CDN POP, but it looks like our CI build is going to pass, so hopefully it's propagating out now! Thanks for all the attention folks.


ConvertConstructorIterfaceData in the cli not working with inheritence

If I have a discriminator the class outputed have no
"This.a = data.a && !()"...
Even if convert constructor interface data is true, other classes does use it right

Probebly NJsonSchema bug


Need support for Airflow 2.0.0

It is a major release from Airflow. It would be better if this supports 2.0.0

As of 1.10.10, Airflow provides its own docker image.

As of 1.10.10, Airflow provides its own docker image.


Adding MIT License

Issue #37 - Adding a MIT License

Hi Jack,
I need help on the google snapshot script.
Could you please help me to understand and execute the script.
I want to take backup for the jenkins volume installed over kubernetes cluster.


ErrorHandler is being ignored by android studio

when sqldelight crashes android studio only gives you the option to report to google and ignores out errorhandler. If the plugin is installed on vanilla IntelliJ it works fine

File a bug on b.android.com?
On Tue, Apr 26, 2016 at 7:38 PM Alec Strong<EMAIL_ADDRESS>wrote:

when sqldelight crashes android studio only gives you the option to report
to google and ignores out errorhandler. If the plugin is installed on
vanilla IntelliJ it works fine
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/square/sqldelight/issues/254

https://code.google.com/p/android/issues/detail?id=208285&thanks=208285&ts=1461717829

As of 3.0-canary-7 this is resolved


Fetch Data from Public API to Your AppGyver Application

Tutorials: https://developers.sap.com/tutorials/appgyver-fetch-data.html
The correct answer set for the last step (step 5) of the tutorial is actually "incorrect" as the app logic is set to fetch the data from the API only when a barcode is scanned.

Hi - thanks for your comment. I've just read the tutorial again and the correct answer is "Only when a barcode is scanned", so I'm not sure I follow your point here?

It's weird because, in my case I was get an "incorrect answer" message every time I selected that one. I only got it to work after selecting "Every five seconds", that's why I thought it was accepting and incorrect answer. Really can't explain how it happened.


Seek - Doc Clerification

https://kafka.js.org/docs/consuming#a-name-concurrent-processing-a-partition-aware-concurrency
await consumer.connect()
await consumer.subscribe({ topic: 'example' })

// you don't need to await consumer#run
consumer.run({ eachMessage: async ({ topic, message }) => true })
consumer.seek({ topic: 'example', partition: 0, offset: 12384 })

In this example, you don't await for consumer.run to finish.
I do want to wait until the run is successfully started and there are no errrors.

Can I safely do:

await consumer.connect()
await consumer.subscribe({ topic: 'example' })

// you don't need to await consumer#run
const p = consumer.run({ eachMessage: async ({ topic, message }) => true })
consumer.seek({ topic: 'example', partition: 0, offset: 12384 })
await p

What if I have 10 partitions. can I safely call seek 10 times and only then run await p?

I wasn't sure if the comment: you don't need to await consumer#run was related to this specific seek example or it's just a comment about run.
Thanks!

Hey @stavalfi, what you are doing is correct. The seek command will create an in-memory map that will trigger the seek command once the consumer is online. That's why we say that you don't need to wait for consumer#run.

What if I have 10 partitions. can I safely call seek 10 times and only then run await p?

Yes. The seek command is sync and will not generate any network calls. All will be resolved once the consumer gets online.

Feel free to re-open the issue in case of other questions.

@tulios Thanks! :)


Fix searchkick results records

Searchkick::Results#records method is removed https://github.com/ankane/searchkick/commit/28637dfa6f2206d16e4b5d08d77a70e8b1270738#diff-c9d8a34bd555e8c17266487beede9166
Also fixes https://github.com/ronzalo/spree_searchkick/issues/21

This pull request also includes the fix from (https://github.com/ronzalo/spree_searchkick/pull/22)


FileNotFoundError for pipx_shared.pth with pipx install --python and pyenv

Describe the bug

I have pipx installed from Homebrew (yay!), as well as pyenv. When I run pipx install black, the resulting venv using the python3.7 interpreter from Homebrew. When I run pipx install --python python3.8 black (or any other version, with any other package), I get the error mentioned in the issue title and reproduced below.
How to reproduce

$ pipx install --verbose --python python3.8 black
pipx > (_package_name_from_spec:93): Determined package name: black
pipx > (_package_name_from_spec:94): Package name determined in 0.0s
pipx > (run_subprocess:108): running python3.8 -m venv --without-pip /Users/brian/.local/pipx/venvs/black

pipx > (rmdir:18): removing directory /Users/brian/.local/pipx/venvs/black
Traceback (most recent call last):
  File "/usr/local/Cellar/pipx/<IP_ADDRESS>/libexec/bin/pipx", line 11, in <module>
    load_entry_point('pipx==<IP_ADDRESS>', 'console_scripts', 'pipx')()
  File "/usr/local/Cellar/pipx/<IP_ADDRESS>/libexec/lib/python3.7/site-packages/pipx/main.py", line 590, in cli
    return run_pipx_command(parsed_pipx_args)
  File "/usr/local/Cellar/pipx/<IP_ADDRESS>/libexec/lib/python3.7/site-packages/pipx/main.py", line 172, in run_pipx_command
    include_dependencies=args.include_deps,
  File "/usr/local/Cellar/pipx/<IP_ADDRESS>/libexec/lib/python3.7/site-packages/pipx/commands/commands.py", line 62, in install
    venv.create_venv(venv_args, pip_args)
  File "/usr/local/Cellar/pipx/<IP_ADDRESS>/libexec/lib/python3.7/site-packages/pipx/venv.py", line 139, in create_venv
    pipx_pth.write_text(f"{shared_libs.site_packages}\n", encoding="utf-8")
  File "/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/pathlib.py", line 1235, in write_text
    with self.open(mode='w', encoding=encoding, errors=errors) as f:
  File "/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/pathlib.py", line 1203, in open
    opener=self._opener)
  File "/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/pathlib.py", line 1058, in _opener
    return self._accessor.open(self, flags, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/Users/brian/.local/pipx/venvs/black/lib/python3.7/site-packages/pipx_shared.pth'

$ pipx --version
<IP_ADDRESS>

$ pyenv version
3.8.0 (set by /Users/brian/.pyenv/version)
2.7.15 (set by /Users/brian/.pyenv/version)
3.7.4 (set by /Users/brian/.pyenv/version)
3.6.9 (set by /Users/brian/.pyenv/version)

$ pyenv which python3.8
/Users/brian/.pyenv/versions/3.8.0/bin/python3.8

Expected behavior

pipx should install a package using the python3.8 interpreter from pyenv.
I get the same error using an absolute path with --python $(pyenv which python3.8), but --python $(brew --prefix python@3.8)/bin/python3 works.

Looks like a bad interaction with pyenv and pipx_shared.pth .  This reminds me a little of #294, in that it seems like a problem involving both pyenv and pipx_shared.pth.
My guess is that this has something to do with detecting which python we're using, and that is getting messed up because of the use of pyenv.  It's interesting to note that even though --python python3.8 is used, it is looking for pipx_shared.pth in path /Users/brian/.local/pipx/venvs/black/lib/python3.7/site-packages/pipx_shared.pth (note the 3.7.)

The first problem that happens when using --python python3.8 in install and pyenv, is that for some reason the venv is getting installed with the system python, and ending up (in my case) with python3.7.
I can successfully

use python3.8 via pyenv from the command-line to create a python3.8 venv
run python3.8 -V from a subprocess in python3.7.6 and get back the right answer ("python3.8.1")

What never works (even in the pipx code)

:x: building a python3.8 venv from python3.7.6

Something very weird is going on.  Observe me trying to use subprocess in python3.7.6 to make a venv with python3.8:
carvel:pipx python3
Python 3.7.6 (default, Dec 30 2019, 19:38:26)
[Clang 11.0.0 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import subprocess
>>> subprocess.run(["python3.8", "-V"])
Python 3.8.1
CompletedProcess(args=['python3.8', '-V'], returncode=0)
>>> subprocess.run(["python3.8", "-m", "venv", "venv"])
CompletedProcess(args=['python3.8', '-m', 'venv', 'venv'], returncode=0)
>>> subprocess.run(["ls", "venv/bin"])
Activate.ps1		easy_install		pip3.7
activate		easy_install-3.7	python
activate.csh		pip			python3
activate.fish		pip3
CompletedProcess(args=['ls', 'venv/bin'], returncode=0)
>>>

On macOS, there's some kind of voodoo with the environment variable __PYVENV_LAUNCHER__.  This variable is set and used for Framework builds of python.  The Framework binary (as I understand the explanation) is a stub, and it starts a subprocess and communicates which version it is through this (temporary?) environment variable.  I notice on my system (macOS) it is set to /usr/local/Cellar/python/3.7.6_1/bin/python3.7 during pipx's run_subprocess() function before the invocation of subprocess.run().  This variable has caused people trouble before:

https://github.com/pypa/virtualenv/issues/845
https://stackoverflow.com/questions/26323852/whats-the-meaning-of-pyvenv-launcher-environment-variable
https://bugs.python.org/issue22490#msg227579
https://github.com/python/cpython/pull/9516

I'm wondering if running pipx from a macOS Framework python build, and using a subprocess to start a pyenv build of python (probably NOT a Framework build) is confusing which python gets built in the venv.  This could also be why @bhrutledge is able to succeed when he uses the 3.8 homebrew build, as the 3.8 homebrew build WILL be a Framework build.

Well I made progress.  If I remove __PYVENV_LAUNCHER__ from env in run_subprocess() (like we do for PYTHONPATH then I can successfully build a venv really based on python3.8
Afterwards it cannot find pip, but still, progress.

Hm.  Now the problem is that it thinks that it should install the pipx_shared.pth file to my system pyenv python3.8.1 directory, and not to the venv directory.
Which is why it is not finding pip.

Ah it turns out that util.get_site_packages() was using get_script_output(), another function that uses subprocess.run().  When I deleted __PYVENV_LAUNCHER__ from the env of this subprocess.run() command as well, everything worked.
So I can fix this bug, if every time we use a subprocess.run() we delete __PYVENV_LAUNCHER__ from its environment.
I have no idea what side effects that might cause.

So I can fix this bug, if every time we use a subprocess.run() we delete __PYVENV_LAUNCHER__ from its environment. I have no idea what side effects that might cause.

Thanks for for the investigation, @itsayellow. I'm glad it's not just me. :)
This reminded me of a chat I had at PyCon with a current maintainer of virtualenv. He said one of the reasons for its continued existence is that it facilitates creating virtual environments using different
Might there be any other workarounds?
If not, instead of deleting __PYVENV_LAUNCHER__ and PYTHONPATH from a copied environment, would it make any sense to start with a blank environment, and explicitly set the variables needed by pipx?

Possibly relevant? https://virtualenv.pypa.io/en/latest/reference/#compatibility-with-the-stdlib-venv-module
Has there been any discussion of pipx using virtualenv instead of venv?

:+1: thanks for the link, that's a lot of useful information.  (Some I'm still trying to parse in my head!)

Has there been any discussion of pipx using virtualenv instead of venv?

Not really, I think we were trying to stay with the built-in venv because pipx is a python3.6+ tool, and so far venv has served well.

If not, instead of deleting PYVENV_LAUNCHER and PYTHONPATH from a copied environment, would it make any sense to start with a blank environment, and explicitly set the variables needed by pipx?

It's a fair question.  Originally I believe that all env variables were implicitly used.  Later, we specifically removed PYTHONPATH because homebrew was manipulating it for its own uses that conflicted with pipx.  So the subject of environment variables might need some conscious thought.
As far as __PYVENV_LAUNCHER__, I believe we can safely remove it, because it was never really meant to be a user variable, it was only meant to be created by the main python binary to allow it to communicate to a subprocess.  Since we are starting a fresh python as if from a shell, we shouldn't have this set beforehand.

I just reinstalled using brew install --HEAD pipx, and confirmed that the fix resolves my issue. Thanks for the prompt fix!

Glad it works for you!  Thanks for your help on this issue.


Refactor/negotiation trajectory

What's new

#206 - following the discussion on removing negotiation trajectories in the leaflet overlay checkbox
https://user-images.githubusercontent.com/29136440/106719686-91cb7380-663d-11eb-8367-4687f8b629cd.mp4

removed the negotiations trajectory option in the leaflet overlay checkbox
only show negotiation trajectory when user is in the negotiations panel and hide the normal trajectories
when user navigates out of the negotiations panel, go back to showing normal trajectories

Showing the different trajectories is done by passing the current index of the omni panel to visual schedulizer. If the index matches the index of negotiations panel, the existing trajectories will be cleared.
Two other minor issues:

home button currently requires 2 clicks to go back to current main menu.
the close button currently still opens to existing view despite calling resetView.

Solved that by creating a new object in dashboard reducer with the current view set to the result of stack.stackNavigator.reset()
Right now, users still have to click on the negotiation to show the negotiations trajectory. Is there any intention to automatically select the latest accepted negotiations that removes the need for clicking?
Self-checks

[x] I'm familiar with and follow this Typescript guideline
[ ] I added unit-tests for new components
[x] I tried testing edge cases
[x] I tested the behavior of the components that interact with the backend, with an e2e test

Discussion

Thanks, I like how it looks, does this PR also fix the new loop and delivery request changes?

Two other minor issues:
home button currently requires 2 clicks to go back to current main menu.
the close button currently still opens to existing view despite calling resetView.

These are non related issues right? I guess they are introduced when I did the schedule visualizer/dashboard refactor.

Thanks, I like how it looks, does this PR also fix the new loop and delivery request changes?

Nope, I am on an old version of RMF demos

These are non related issues right? I guess they are introduced when I did the schedule visualizer/dashboard refactor.

Yup, they are not related. But the UI does not look in sync so I guess they are indirectly related