text:
When creating a developer scratch org, the community 'Report Builder' feature wont be available

Summary
After the spring 20 release, a new feature became available for communities, this feature allows community members to create reports inside the community.
If you create a new scratch org with force:org:create using a definition file with the org edition set to 'Developer' this feature wont be available.
This is not the case if the edition is set to 'Enterprise'.
Steps To Reproduce:

Create a new scratch org using the following definition file

  "orgName": "Demo company",
  "edition": "Developer",
  "features": [
    "API",
    "Communities",
    "ConnectedAppToolingAPI",
    "DebugApex",
    "EinsteinAnalyticsPlus",
    "Interaction",
    "MarketingUser",
    "MultiCurrency",
    "PardotScFeaturesCampaignInfluence",
    "PersonAccounts",
    "ProcessBuilder",
    "RecordTypes",
    "SalesforceIdentityForCommunities",
    "Sites",
    "Workflow",
    "WorkflowFlowActionFeature"
  ],
  "settings": {
    "omniChannelSettings": {
      "enableOmniChannel": true
    },
    "quoteSettings": {
      "enableQuote": true
    },
    "languageSettings": {
      "enableTranslationWorkbench": true
    },
    "lightningExperienceSettings": {
      "enableS1DesktopEnabled": true
    },
    "communitiesSettings": {
      "enableNetworksEnabled": true,
      "enableNetPortalUserReportOpts": true
    },
    "analyticsSettings": {
      "enableAnalyticsSharingEnable": true,
      "enableLightningReportBuilder": true,
      "enableMassEnableReportBuilder": true
    }
  }
}

open the scratch org and go to Setup -> All communities and create a new community with the 'Partner Central' or the 'Customer Account Portal' template
After creation, in the workspace page select 'Builder'
At the top left of the page there is a button to change the page, click there and type 'Report'
Change the edition from 'Developer' to 'Enterprise' and repeat steps 1-3

Expected result
There should be a page called 'Report Builder', and the 'New Report' button should display inside the the 'Report List' page.
Actual result
No report builder page is created and the button is not visible
Additional information
This is not a problem with the Developer edition because the feature should be available for developer orgs and I've confirmed that if you repeat the steps in a Developer Sandbox the feature will be available correctly, so it should be a problem with the scratch org creation.
SFDX CLI Version: 7.54.4
SFDX plugin Version
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-help 2.2.3 (core)
@oclif/plugin-not-found 1.2.3 (core)
@oclif/plugin-plugins 1.7.9 (core)
@oclif/plugin-update 1.3.9 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.7.1 (core)
generator 1.1.2 (core)
salesforcedx 48.10.1 (core)
├─ salesforcedx-templates 48.8.0 (core)
├─ salesforce-alm 48.10.0 (core)
└─ @salesforce/sfdx-plugin-lwc-test 0.1.5 (core)
OS and version: Win 10

After further investigation, the problem seems to be intermittent, because after testing more than 10 times, I just created a new scratch org using the exact same steps with the exact same definition file and the feature is available.
I've noticed that this also happens with a  community setting called 'enableGuestRecordReassignOrgPref', sometime its available, sometimes its not.
Our original problem was because we already have source files from a community that is using the new experience bundle, and this community has the 'createreport' route, this source was giving errors when pushing to a new scratch org because the 'Report builder' feature was no available.
It seems to me that some scratch orgs are being created with some features disabled, but I'm not able to pinpoint what the problem might be.

@vviotto  I am sorry you are encountering this issue. This looks to be a problem with communities that we do not own from the CLI point of view. Please file a support case so that the community team can help you.

authors: clairebianchi vviotto

repo: forcedotcom/cli


text:
upgrade utile to 0.3.0

https://github.com/foreverjs/forever is already using utile to 0.3.0.
forever-monitor is still using 0.2.1.
utile 0.2.1 has security vulnerability, https://github.com/Dome9/policy_reports/issues/2.
Any plans to upgrade forever-monitor to utile 0.3.0?

Thanks for reporting! I'll take a look.

source: gharchive/issue

authors: advaittrivedi kibertoad

repo: foreverjs/forever-monitor

license: mit

license_type: permissive

license_source: bigquery


text:
Hello world in R

Pull Request Type
What kind of change does this PR introduce?
Solved an issue/task
What is the current behavior?
No code to print Hello world
Issue Number: [#1447]
What is the new behavior?
Implemented code to print Hello world
Code Output

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!

source: gharchive/pull-request

repo: fork-commit-merge/fork-commit-merge

license: MIT

license_source: github-api


text:
tableview reloaddata 的时候会走 算高度的方法 然后将所有cell移除掉 出现了闪屏的情况

tableview reloaddata 的时候会走 算高度的方法 然后将所有cell移除掉 出现了闪屏的情况 望楼主帮忙看下

Look like you reset your data source. can you double check, feel free to re-open if still has the issues


text:
Bootstrap5: Missing icons for panel collapse/uncollapse

Hi Formio Team,
please can merge this pull request to add the icons for panel collapse/uncollapse.
Best regard
Ralf

Thank you!

authors: ralfeis travist

repo: formio/bootstrap


text:
HTML in labels

Hello, what is a proper way to include a link in a checkbox label? Use case: "I accept terms and conditions" Is it possible to put HTML there? Thank you!

Hi @aristid! Here are 2 ways you can do it: https://formkit.link/a8ed01530d62d03187a6d93539da562a
Also, feel free to ask these "how-tos" in the Discord

Thank you very much!

Also, feel free to ask these "how-tos" in the Discord.
Will do!

Is it possible to do the above, but within a form schema? Stand alone example works fine, but label appears as [object Object] when part of schema.

authors: aristid luan-nk-nguyen willans

repo: formkit/formkit


text:
Weird behavior with the mask

Reproduction
https://formkit.link/033713494457849aac57cb4ba02d9ae1
Describe the bug
Just add few number values, then delete these values.
The cursor jumps around when adding and deleting
Environment
• OS: [all]
• Browser [ chrome ]

Yep, looks like something we can take a look at — crux of the issue here is the suffix being used with a repeatable group — something we need to sort out.

authors: CavalcanteLeo justin-schroeder


text:
Guides update

Adding new pages and updating index to support a single Guides landing page. To do: delete the extraneous development folder and its index file.

Adding cla: yes label, as all commit authors are covered by CLA.

authors: Tabrarian blueandgold

repo: forseti-security/forseti-security


text:
Create Simple First Version for Web App Generator

The web app generation can be bundled with the orga server, but it should also be possible to generate web apps just by getting the data from a JSON file.
As a first step we need a simple web page, where an organizer can choose to upload a JSON file and generate the app that can be downloaded as a zip file.
The first version is similar to a graphical implementation of the Open Event Scraper (https://github.com/fossasia/open-event-scraper) with zip download, but should include additional design features in follow up versions including choosing a color scheme and theme.

To paraphrase @mariobehling:

Give me a UI/User flow ASAP
Construct with a UI and layout (genetella)
Read a JSON and display the data
Allow me to download the entire web app project in a zip with the JSON (which is the EASIEST once you have DONE the UI/User flow)
Call from a REST API URL later for hosted mode

@championswimmer @aayusharora understand?

@juslee
gentelella is a "Admin template" suitable for making dashboards, analytics panels etc
For the client-side webapp (that will be viewed by attendees), why do we need to use gentelella?

@championswimmer then suggest a new theme to use. Otherwise, use it first for consistency. You can refactor and replace the theme later. You should be able to easily refactor with a bit of work to use a new bootstrap theme. Code that in mind.

@championswimmer I do hope we will get started with this now. Please separate this issue into issues that can be done in a single day. We can use the part of the current Open Event Scraper to generate an app from a JSON. Then generate a schedule just like http://2016.opentechsummit.net/programm/ Once this is working you can change it to gentelella or another bootstrap theme, but please do start to get this going now. You can also do differently, but please start.

@mariobehling
Yes will get started right away
On Fri 27 May, 2016 04:02 Mario Behling, notifications@github.com wrote:

@championswimmer https://github.com/championswimmer I do hope we will
get started with this now. Please separate this issue into issues that can
be done in a single day. We can use the part of the current Open Event
Scraper to generate an app from a JSON. Then generate a schedule just like
http://2016.opentechsummit.net/programm/ Once this is working you can
change it to gentelella or another bootstrap theme, but please do start to
get this going now. You can also do differently, but please start.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-webapp/issues/203#issuecomment-222013988,
or mute the thread
https://github.com/notifications/unsubscribe/ABQ_yqFDbCsJPzxvPDvtLeuXU-DCEhjxks5qFh9sgaJpZM4IiAZV
.

@mariobehling
https://github.com/OpenTechSummit/open-event-scraper has audio support now.
It is in a state to be used to generate simple schedule page with sessions and speakers.
For the purpose of having a generated static html based website for events, we have it now.

@championswimmer What is the status on this? When do we have a UI to generate the web app?

See sample here:

View

Solved here #227 , will be opening issues for adding functionality .

All done

authors: aayusharora championswimmer juslee mariobehling

repo: fossasia/open-event-webapp


text:
Speculative sampling

Implements simple speculative sampling via candidate-consistent ground-truth sampling. See #12 for a discussion on implementation details and why this is needed in the first place.

Add __generate_targets() function, implementing both greedy and non-greedy selection
Enable sampling in speculative_generate()
Support temperature and top_k sampling as in non-speculative generate
Allow user to set these as arguments in the paged_speculative_inference.py demo script

Notably, for low temperature and top_k, we anecdotally observe no reduction in speculator performance compared to the greedy case!

Sample outputs demonstrating new sampling capabilities:
Below is an instruction that describes a task. Write a response that appropriately completes the request.

### Instruction:
Provide a list of instructions for preparing chicken soup.

### Response:

Greedy baseline:
Sure! Here are the steps to prepare chicken soup:

1. Start by chopping 1 onion and 3 cloves of garlic.
2. In a large pot, heat 2 tablespoons of olive oil over medium heat.
3. Add the chopped onion and sauté until it's translucent.
4. Add the chopped garlic and sauté for an additional 2 minutes.
5. Add
103 tokens in 34 steps

time to first token: 0.026240825653076172
time per token (decode): 0.009298106999073213

top_k=5, temperature=2: no slowdown
Here is a recipe for preparing a delicious homemade chicken soup:

Step 1: Gather Ingredients:

* 2 lbs. boneless skinless chicken breasts or thighs, cut into bite-sized pieces
* 2 carrots, peeled and chopped
* 2 celery stalks, chopped
* 1 large onion, chopped
* 2-4 cups of
104 tokens in 32 steps

time to first token: 0.02620673179626465
time per token (decode): 0.00881159076323876

top_k=5, temperature=5: slowdown due to low likelihood of (ridiculous) output
Soup-tactical Movement:
To create this savor-ific broth:
1. Gather the squad of chicken brews and chicken parts (legs and feet work best) in one area for staging. Ensuring all ingredients are at room temperature.
2. In a galleon (Larger pot) add one-quint (about 1.3 litters) water and two pinch's salt to create the bre
102 tokens in 68 steps

time to first token: 0.026073217391967773
time per token (decode): 0.018784146682888855

repo: foundation-model-stack/fms-extras


text:
fix: multiple runid creation bug with accelerate.

Description of the change
Fixes a bug where multiple runid were being created with accelerate.

Related issue number
N/A

How to verify the PR

Was the PR tested

[ ] I have added >=1 unit test(s) for every new method I have added.
[ ] I have ensured all unit tests pass

Fixes https://github.com/foundation-model-stack/fms-hf-tuning/issues/277

Tested it, seems to be working.
Using 8 GPUs:
  --use_fsdp \
  --fsdp_auto_wrap_policy=TRANSFORMER_BASED_WRAP \
  --fsdp_forward_prefetch=false \
  --fsdp_offload_params=false \
  --fsdp_sharding_strategy=FULL_SHARD \
  --fsdp_state_dict_type=FULL_STATE_DICT \
  --fsdp_cpu_ram_efficient_loading=true \
  --fsdp_sync_module_states=true \
  --rdzv_backend=static \
  --same_network \
  --num_processes=8 \
  --num_machines=${WORLD_SIZE} \
  --mixed_precision=no \
  --dynamo_backend=no \
  --machine_rank=${RANK} \
  --main_process_ip=${MASTER_ADDR} \
  --main_process_port=${MASTER_PORT} \
  -m tuning.sft_trainer \
  --aim_repo="${AIMSTACK_DB}" \
  --dataset_text_field="output" \
  --experiment="p-stack-tests-test62" \
  --gradient_accumulation_steps="1" \
  --learning_rate="1e-05" \
  --model_name_or_path="ibm-granite/granite-7b-base" \
  --num_train_epochs="5" \
  --output_dir="/cos1/stack/tests/test62" \
  --per_device_train_batch_size="1" \
  --response_template="\n### Label:" \
  --tracker="aim" \
  --training_data_path="/cos1/stack/sample-datasets/twitter_complaints.json" \
  --use_flash_attn="true" \
  --log_level="debug"

Gives only one run id in AIM dashboard

authors: HarikrishnanBalagopal dushyantbehl

repo: foundation-model-stack/fms-hf-tuning


text:
Font Colors

I am trying to create color blocks that have the same layout, but different colors for the font and background. This is what my index looks like :+1:

  <row class="call-out-1">
    <columns small="12" large="12">

Program 1

Sub Head

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Suscipit totam quasi ab aliquam saepe non fugiat laborum

            <button href="#" class="small">Find Out More</button>

    </columns>
  </row>

    <row class="call-out-2">
      <columns small="12" large="12">

Program 1

Sub Head

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Suscipit totam quasi ab aliquam saepe non fugiat laborum

                <button href="#" class="small">Find Out More</button>

      </columns>
    </row>

and my components for call-out-1 is
.call-out-1 {
  background: $light-gray;
  margin-top: $global-margin;
  Margin-top: $global-margin;
  margin-bottom: 0;
  Margin-bottom: 0;

  .columns {
    padding-top: $global-padding *2;
    padding-bottom: $global-padding *2;

    h4 {
      color:$dark-gray;

    p {
      color:$dark-gray;

    h6 {
      color:$success-color;
        }
      }
    }
  }
}

and call-out-2
.call-out-2 {
  background: $primary-color;
  margin-top: 0;
  Margin-top: 0;
  margin-bottom: $global-margin;
  Margin-bottom: $global-margin;

  .columns {
    padding-top: $global-padding *2;
    padding-bottom: $global-padding *2;

    h4 {
      color:$white;

    p {
      color:$white;

    h6 {
      color:$success-color;
        }
      }
    }
  }
}

They have all been imported and I know work, but it won't let me define the p class color or the h6 for some reason only the h4, and it just looks strange.

Are the variables getting overridden by another rule, or is it breaking altogether? If you have more screenshots or code snippets that might give us more info.
Thanks!

@hswidarski I fixed your code examples so they display. You wrap code with ``` to make it show.
Were you able to narrow what is happening here? Do you see any properties being overwritten in the inspector?

Closing as we did not receivy any further feedback.

authors: DanielRuf hswidarski rafibomb tdhartwick

repo: foundation/foundation-emails


text:
[!New-Latest!]$$ TikTok Follower Generator in-2024-2025 Real TikTok Follower Views And Likes

25 secs ago - Tik Tok Followers Free - Free Tiktok Likes app fast fans followers Tik Tok Followers Free - Free Tiktok Likes app fast fans followers TIK-TOK can help you to get the very first fans for the TIK-TOK videos, you will get to the key page and attract more followers.
👉✅🔴► CLICK HERE TO GET FREE NOW 🌍~
👉✅🔴► CLICK HERE TO GET FREE NOW 🌍~
Latest Update 11 Jun 2024
I hit 10,000 TikTok followers today. Normally, I don’t make a big deal out of this stuff. But, this feels like quite an accomplishment given the dramatic shift I’ve made.
It would be safe to say that six months ago, this would have been laughable. I wasn’t active on TikTok, and I detested everything about it (and short-form video generally). But, by the end of September, I put my old man shoes away and realized that this was something I needed to do.
When I committed to it, I made a conscious decision to become the most followed account related to the topic of Facebook ads on TikTok. I’m obviously not there yet, but this is a nice milestone.
What I did was simple and complicated at the same time. It really comes down to two things…
Have questions about short-form videos? Ask my AI-powered bot!
Some Ads Early
might take more and charge more and that is tiktok ads you should try this tip once having a popular video of yours use tiktok ads to make the video spreads much more and reach millions it might cost some money but it is 100 worthwhile besides getting 1000 free tiktok followers like what has been explained in promotion and make money you already knew that the more tiktok followers you have the more money you will make this section will give you a clue on how to get promotions on tiktok and how much you will make normally tiktok followers generator 2023 you ll reach fame in much less time free tiktok followers generator 2023 no human verification tiktok free followers generator unlimited free tiktok followers free tiktok likes 2023 tiktok followers generator grow your tiktok account with free and real followers now free tiktok followers fans and likes get up to 20k tiktok followers for free daily all you need is your username join us and be famous get real followers for more than 3 tiktok accounts rejos UPDATED FREE TIKTOK FOLLOWERS GENERATOR 2023 of external sources to get tiktok views at the start once the tiktok views start coming because of the uptake of the external sourced views the profile will soon get organic views hits and likes which will put the user on top free tiktok follower 99000 free tiktok followers
The toughest part of getting started is publishing videos into the void. Maybe it was to give me a psychological boost or to make my profile look a bit more desirable in the early going, but I ran a low level of TikTok ads during the first couple of months.
From the time I committed to creating videos on TikTok in October through the middle of December, I collected 3,253 followers via ads. It was a nice foundation.
This was good and bad.
The bad: I tried really hard to target precisely to build my audience with relevant people. All indications are that this wasn’t successful. It was mostly numbers padding (the relevant followers would come organically).
The good: We can knock vanity metrics all we want, but it does mean something on TikTok if someone has a following. It surely helped convince some relevant people that I was worth following.
Did this lead to a significant spike in engagement during those first few months? Not really. But I do think that it helped me reach the next step.
A Dedicated Commitment to Create
Look, I could run ads forever on TikTok, but unless I was actually creating good content, it would not matter. I dedicated myself early.
I would create bad videos in the beginning, there was no avoiding that. But the goal was to get myself out of that phase as quickly as possible. I created 70 videos in October. It was a difficult, challenging, and inefficient month of video creation.
But it was worth it. I started to figure out my process. I found a workflow. Needs like software and lighting became clearer to me.
I dedicated myself to publishing at least one video per day in 2023. Truthfully, I missed very few days once I started in October, but I wanted to avoid any days off going forward.
I’ve kept to that commitment and I’ve published more than 260 videos on TikTok. Consistency, volume, and quality. More than anything else, I’d say that these were the keys to my growth.
What I Didn’t Do
I didn’t try to go viral. I didn’t worry about trends or popular sounds. Trust me, you’re going to hear a lot of advice around that stuff.
But it’s wrong.
If all you care about is being popular, sure. Chase that stuff. But you’re going to attract a very general, random audience. And that’s not how you build an engaged following around a specialty.
While I haven’t completely niched down on TikTok (I talk about Facebook ads, video creation, and entrepreneurship), it’s at least a similar category. I don’t want to attract randos who don’t care about any of these things.
The result: Engagement is growing with the audience size.
Tracking Growth
TikTok only offers analytics back 60 days, as far as I can tell. But even within the past two months, the improvement really jumps out.
Those spikes are when some videos took off. I have three recent videos that received more than 30,000 views (all organic).
Those three videos alone resulted in 2,942 new followers.
But it’s not just those three. Here’s a look at the trend of views during the past 60 days…
Even during the end of January, most days I’d receive very few views. But then something started to change. The floor raised.
Engagement is no longer focused on a few videos. I can now expect that my recent videos will almost always get at least 1,000 views. That was definitely not the case before.
That doesn’t mean that this new engagement level will continue forever, but it’s certainly a good sign.!

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins
🔴📺📱👉 Click here Free Followers, Likes, Fans, Views and Coins

repo: foundation/foundation-sites


text:
Update README.md

Description

Remove reference to (wrong) node versions. It was misleading. Furthermore, even if the version was correct, it's redundant because of the entry within package.json
Types of changes

[X] Documentation
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (anything that would change an existing functionality)
[ ] Maintenance (refactor, code cleaning, development tools...)

Checklist

[X] I have read and follow the CONTRIBUTING.md document.
[X] The pull request title and template are correctly filled.
[X] The pull request targets the right branch (develop or develop-v...).
[X] My commits are correctly titled and contain all relevant information.
[X] I have updated the documentation accordingly to my changes (if relevant).
[X] I have added tests to cover my changes (if relevant).

because of the entry within package.json

actually would be nice to still mention minimum Node version in the README.md

Thanks. I will update the README in the next build.

authors: ameotoko beephotography joeworkman


text:
Cheatcode for setting tx.gasprice

Component
Cheatcode
Describe the feature you would like
In the same way users can set block.chainId via vm.chainId(...) or block.difficulty via vm.difficulty(...), it would be useful to be able to set tx.gasprice via a cheatcode.  Something that looks like vm.txGasPrice(...) and sets the tx.gasprice of the next transaction would be great.
Additional context
Have some code that compensates an off-chain relayer by tracking gas used then compensating the relayer with gasUsed * tx.gasprice. Currently unable to set tx.gasprice and the default value is 0.

Have some code that compensates an off-chain relayer by tracking gas used

ah okay, gotcha.
as you mentioned this should be just like the chainId cheatcode so can add this easily.
cc @mds1

authors: luketchang mattsse

repo: foundry-rs/foundry


text:
forge build doesn't work for PCs with ram < 16 gb

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (deb3116 2024-01-27T00:16:24.795550479Z)
What command(s) is the bug in?
forge test, forge build, forge script
Operating System
Linux
Describe the bug
SIGKILL for any PC that has lesser than 16gb ram

Just tested this on a virtual machine with less than 16 gigabytes of ram and had no issues. Please provide some code for which this does not work.

Have to apologise, the bug refers to projects that are moderately big in size
https://github.com/code-423n4/2024-01-salty

Whereas it builds normally for 16gb ram pcs,
My issue is that it shouldn't be executed in a way for SIgKill to happen
There must be a way to compile it despite the amount of code or restricted Ram available.
Ty, might be more of a feature request but I think it's essential for people with shit PCs

I ran /usr/bin/time -v forge build in that project specifically and it never used more than 3 gigabytes of RAM:
[⠊] Compiling...
[⠢] Compiling 172 files with 0.8.22
[⠃] Solc 0.8.22 finished in 52.11s
Compiler run successful!
	Command being timed: "../../foundry-rs/foundry/target/release/forge build"
	User time (seconds): 51.45
	System time (seconds): 1.96
	Percent of CPU this job got: 100%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0:53.26
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 3269624
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 0
	Minor (reclaiming a frame) page faults: 922490
	Voluntary context switches: 7497
	Involuntary context switches: 326
	Swaps: 0
	File system inputs: 0
	File system outputs: 204952
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0

This is on Arch Linux

If you're using via-ir, see also https://github.com/foundry-rs/foundry/issues/6895#issuecomment-1911570027
In any case, I am getting similar results to @onbjerg's comment above.
I'm going to close this since I assume most of the memory consumption is in solc.

authors: DaniPopes JADcooler onbjerg


text:
Add github action

Which component is your feature related to?
Other (Please describe below)
Feature Request
Would it be possible to add a github action that allows CI to download foundry version used project. The version could be found via the scarb.toml dependencies or a seperate file.

https://github.com/foundry-rs/setup-snfoundry
It is almost ready to be published

repo: foundry-rs/starknet-foundry


text:
Extract build_readable_text into shared crate

Closes #1127
Introduced changes

Extracted build_readable_text into shared crate to reuse it in sncast and forge-runner

Checklist

[x] Linked relevant issue
[ ] Updated relevant documentation
[ ] Added relevant tests
[ ] Performed self-review of the code
[ ] Added changes to CHANGELOG.md

We can move more stuff to shared.
e.g.
https://github.com/foundry-rs/starknet-foundry/blob/f3237f2325d5fd31fb066cbc18f279839521090c/crates/forge/src/pretty_printing.rs#L8-L11
https://github.com/foundry-rs/starknet-foundry/blob/f3237f2325d5fd31fb066cbc18f279839521090c/crates/sncast/src/response/print.rs#L167-L170
But im not sure if we want to do it here or in separate PR.

We can move more stuff to shared. e.g.
https://github.com/foundry-rs/starknet-foundry/blob/f3237f2325d5fd31fb066cbc18f279839521090c/crates/forge/src/pretty_printing.rs#L8-L11
https://github.com/foundry-rs/starknet-foundry/blob/f3237f2325d5fd31fb066cbc18f279839521090c/crates/sncast/src/response/print.rs#L167-L170
But im not sure if we want to do it here or in separate PR.

Separate issue(s) and PRs, but good call :+1:
I believe this particular function will be moved in https://github.com/foundry-rs/starknet-foundry/pull/1704#discussion_r1489892339

authors: Draggu THenry14 abulenok


text:
Deployment Plan erstellen

Deployment Plan für Beta entwerfen. (Softwareübergabe an Prof. Krawietz)

Zeit: 2.5h

authors: fowado fritzschefelix


text:
rust: writer automatically breaks chunks at size

Public-Facing Changes

Adds a new writer option, chunk_size, which will automatically break up chunks at a target (uncompressed) size.
Description

Fixes #727

cc. @mrkline

repo: foxglove/mcap


text:
template-haskell-2.12.0.0

template-haskell-2.12.0.0 is out of bounds for:

[ ] Agda-2.5.2 (>=2.8.0.0 && < 2.12). Andrés Sicard-Ramírez asr@eafit.edu.co @asr. @agda. Used by: library

[ ] RepLib-0.5.4 (>=2.4 && < 2.12). Joachim Breitner mail@joachim-breitner.de @nomeata. @sweirich. Used by: library

[ ] arrowp-qq-0.1 (< 2.12). Jose Iborra pepeiborra@gmail.com @pepeiborra.. Used by: library

[ ] avers-0.0.17.1 (>=2.11.0.0 && < 2.12). Tomas Carnecky @wereHamster. @wereHamster. Used by: library

[ ] bindings-GLFW-3.1.2.2 (>=2.10 && < 2.12). Brian Lewis brian@lorf.org @bsl. @bsl. Used by: library

[ ] boomerang-1.4.5.2 (< 2.12). Jeremy Shaw jeremy@n-heptane.com @stepcut. @stepcut. Used by: library

[ ] clash-lib-0.7.1 (>=2.8.0.0 && < 2.12). Christiaan Baaij christiaan.baaij@gmail.com @christiaanb. @clash-lang. Used by: library

[ ] clash-prelude-0.11.2 (>=2.9.0.0 && < 2.12). Christiaan Baaij christiaan.baaij@gmail.com @christiaanb. @clash-lang. Used by: library, benchmark

[ ] data-accessor-template-0.2.1.13 (==2.11.*). Henning Thielemann stackage@henning-thielemann.de @thielema.. Used by: library

[ ] email-validate-2.3 (>=2.11.1.0 && < 2.12). George Pollard porges@porg.es @Porges. @Porges. Used by: library

[ ] happstack-server-7.5.0 (< 2.12). Jeremy Shaw jeremy@n-heptane.com @stepcut. @stepcut. Used by: library

[ ] haskell-tools-ast-0.8.0.0 (==2.11.*). Boldizsár Németh nboldi@elte.hu @nboldi. @nboldi. Used by: library

[ ] haskell-tools-backend-ghc-0.8.0.0 (==2.11.*). Boldizsár Németh nboldi@elte.hu @nboldi. @nboldi. Used by: library

[ ] haskell-tools-debug-0.8.0.0 (==2.11.*). Boldizsár Németh nboldi@elte.hu @nboldi. @haskell-tools. Used by: library

[ ] haskell-tools-refactor-0.8.0.0 (==2.11.*). Boldizsár Németh nboldi@elte.hu @nboldi. @haskell-tools. Used by: library, test-suite

[ ] hsx2hs-0.14.1 (>=2.7 && < 2.12). Jeremy Shaw jeremy@n-heptane.com @stepcut. @seereason. Used by: library

[ ] ixset-typed-0.3.1 (>=2.8 && < 2.12). No maintainer. @well-typed. Used by: library

[ ] lens-family-th-0.5.0.0 (==2.11.*). Dan Burton danburton.email@gmail.com @DanBurton. @DanBurton. Used by: library

[ ] mediabus-0.4.0.1 (< 2.12). Sven Heyll svh@posteo.de @sheyll. @lindenbaum @sheyll. Used by: test-suite

[ ] mediabus-rtp-0.4.0.1 (< 2.12). Sven Heyll svh@posteo.de @sheyll. @lindenbaum @sheyll. Used by: test-suite

[ ] overloaded-records-0.4.2.0 (>=2.9 && < 2.12). Taylor Fausak taylor@fausak.me @tfausak. @trskop. Used by: library, test-suite

[ ] papillon-0.1.0.4 (==2.11.*). Yoshikuni Jujo PAF01143@nifty.ne.jp @YoshikuniJujo. @YoshikuniJujo. Used by: library, executable

[ ] prettyprinter-1.1 (>=2.9 && < 2.12). David Luposchainsky <dluposchainsky (λ) googles email service> @quchen. @quchen. Used by: executable

[ ] rattletrap-2.5.0 (==2.11.*). Stackage upper bounds. @tfausak. Used by: library

[ ] regex-1.0.1.3 (>=2.7 && < 2.12). Chris Dornan chris@chrisdornan.com @cdornan. @iconnect. Used by: library

[ ] regex-with-pcre-1.0.1.3 (>=2.7 && < 2.12). Chris Dornan chris@chrisdornan.com @cdornan. @iconnect. Used by: library

[ ] safecopy-0.9.3.2 (< 2.12). No maintainer. @acid-state. Used by: library, test-suite

[ ] stache-0.2.2 (>=2.10 && < 2.12). Mark Karpov markkarpov92@gmail.com @mrkkrp. @jsantos17 @jsl @sestrella. Used by: library

[ ] strive-3.0.3 (==2.11.*). Taylor Fausak taylor@fausak.me @tfausak. @tfausak. Used by: library

[ ] test-fixture-0.5.0.1 (>=2.10 && < 2.12). Alexis King lexi.lambda@gmail.com @lexi-lambda. @cjdev. Used by: library, test-suite

[ ] testing-feat-0.4.0.3 (>=2.5 && < 2.12). No maintainer. @JonasDuregard. Used by: library

[ ] th-data-compat-0.0.2.4 (==2.11.*). No maintainer. @khibino. Used by: library

[ ] th-desugar-1.6 (< 2.12). Richard Eisenberg eir@cis.upenn.edu @goldfirere. @goldfirere. Used by: library, test-suite

[ ] tttool-1.7.0.3 (>=2.7 && < 2.12). Joachim Breitner mail@joachim-breitner.de @nomeata. @entropia. Used by: executable

[ ] wai-routes-0.10.0 (>=2.9 && < 2.12). Anupam Jain ajnsit@gmail.com @ajnsit. @ajnsit. Used by: library

[ ] web-routes-th-0.22.6.1 (< 2.12). Jeremy Shaw jeremy@n-heptane.com @stepcut. @happstack @stepcut. Used by: library

I made a PR for temporarily disabling Agda.

Due to the large number of participants on this issue, I'm going to lock the conversation. Feel free to open a separate issue if you have anything out of the ordinary to discuss.

authors: DanBurton asr lwm

repo: fpco/stackage


text:
61-example/gitlab asg part 1

Purpose
To address issue #61 first part
Work done

Updated the Makefile so all steps properly work
Automated several steps using jl
Clearly documented all steps
List remaining to-dos for this issue

Achieved Goal
Given the state of the example, it was necessary to make several changes to get it to work at all. The opportunity was used to improve documention and automate steps where possible making it clearer and easier to use.
@ketzacoatl

@borsboom made change to README as per your request

Rather than push over this PR, I have created a new PR based on this one - see #159 for that. The primary reason for a new PR was to extract the commits from the various branch merges and squash them down to something smaller in the history. The new branch is nearly identical with the old one save for:
diff --git a/tests/gitlab-asg/cert-config.json b/tests/gitlab-asg/cert-config.json
deleted file mode 100644
index f8a9902..0000000
--- a/tests/gitlab-asg/cert-config.json
+++ /dev/null
@@ -1,13 +0,0 @@
-{
-  "signing": {
-    "default": {
-      "expiry": "8760h",
-      "usages": [
-        "signing",
-        "key encipherment",
-        "server auth",
-        "client auth"
-      ]
-    }
-  }
-}

authors: AronT-TLV ketzacoatl

repo: fpco/terraform-aws-foundation


text:
Fixes, Additions and Changes: Better preview and More options for mouse control

This update includes some aesthetics and functionality, the added joystick preview
will allow debugging mouse movement when later trying to implement a better mouse
translation to joysticks, it will also allow users to test and see how their
configuration is translated to the controller so they can fine tune their
settings.
Added

Controller Axis Preview on Controller Preview
Relative Mouse stick controls
Added final modifier to mouse control (More precise movements)
Fixed build bat not building 32bit files
Optional hide cursor (Useful for making minor mouse config changes)
Extra mouse engines (Relative, Raw, Raw + Sensitivity, None)
Information Tab on Input Editor

Changes:

Moved around classes in folder
Renamed the create downloads bat to "build.bat"
several un-named changes.

Fixes:

Fixed any errors while closing the Application
Some un-named fixes.

Thanks

authors: CallumCarmicheal fqlx

repo: fqlx/XboxKeyboardMouse


text:
TODO: The changelog is not added to the release notes for release candidates

As the version contains an "rc-X" suffix the changelog is not correctly parsed into the release notes during the Github Actions build process.

Seems to be fixed by something I did in the meantime here: https://github.com/fr-ser/grafana-sqlite-datasource/releases/tag/v3.1.3-rc.1

repo: fr-ser/grafana-sqlite-datasource


text:
test_commands is not stateless when using postgres

The db fixture makes tests stateless, w.r.t. dropping all tables.
In the test_commands.py module we call fractalctl commands via subprocess, and we do not revert this operation at the end.
This is OK for sqlite, since the db files are function-scoped, but not for postgres tests.

Moreover, the file (FRACTAL_SERVER_DIR / ".fractal_server.env").open("w") is not removed/reset after each test, but it should.


text:
feat(richard): transaction table

Fixes #28
Milestones To-do:

[x] Create basic table UI and review if if it is desired
[x] Create version with Integrated Blockscout API
[ ] Add unit tests (if applicable)

Huly®: DAPPK-38

Demo video: https://www.loom.com/share/f24b85a30e7b4c2cbe7459165dee07e9?sid=5b38c48f-128e-41b6-b138-b9178ac25063

repo: fractaldotbox/geist-dapp-kit


text:
Fix model update not being applied

Oops!

Thank you!

authors: krtek shanesmith

repo: fragaria/angular-daterangepicker


text:
Pushing to a sequence within a table doesn't always work

To Reproduce
(defwire main-wire
  {:k [1 2 3]} >= .table
  4 (Push .table :Key "k" :Clear false) ;; whether :Clear is explicitly stated doesn't seem to matter
  .table (Log))

(defmesh main)
(schedule main main-wire)
(run main)

Sometimes the sequence will get the 4th element, sometimes it won't.
Expected behavior
The sequence should get the 4th element.

This is some bad bug...
https://github.com/fragcolor-xyz/shards/runs/7551863403?check_suite_focus=true#step:4:3901
That is what I expected from documenting Shards, as it's QA at same time, I said this a year ago.. this is probably a super old bug 🤦

The solution was to prevent this behavior because by design Push is supposed to cash internally the key pointer.
The above code is highly inefficient and should be discouraged because it does 2 copies, and a full table clear on re-assign every cycle.
Bottom line, if you push stick with push.

Better use:
{:k .seq-var} if a similar behavior is needed.
Please document accordingly @satendrapalsingh
PR is #337

Better use: {:k .seq-var} if a similar behavior is needed. (and push normally to seq-var) Please document accordingly @satendrapalsingh PR is #337

Strange, it doesn't seem to work - the seqvar gets updated but the table does not.
[1 2 3] >= .seqvar                  ;; create a sequence variable
{:k .seqvar} >= .table              ;; use seqvar as sequence value in table
4 (Push .seqvar)                    ;; `Push` into seqvar instead of table
.seqvar (Log)                       ;; => [1, 2, 3, 4]
.table (Log)                        ;; => {k: [1, 2, 3]}

More misunderstanding...
>= or Set, will COPY.
try = or Ref

might want to document that too btw 👍

[1 2 3] >= .seqvar     ;; the const [...] IS COPIED INTO .seqvar
[1 2 3] = .seqvar ;; the const is simply referenced

More misunderstanding... >= or Set, will COPY. try = or Ref

I thought Ref/= creates immutable variables and Set creates mutable ones.
I can't Push into .seqvar  since its immutable if I create it via Ref
[1 2 3] = .seqvar
4 (Push .seqvar)
.seqvar (Log)
;; => Error: Push variable name already used as Ref. Overwriting a previously Ref variable with Push is not allowed, name: seqvar, input shard: Push

[1 2 3] >= .seqvar     ;; the const [...] IS COPIED INTO .seqvar
[1 2 3] = .seqvar ;; the const is simply referenced

Yeah, means the same thing right?

>= creates a mutable variable (since we copied the const into a new location and are free to change this new location data)
= creates an immutable variable (since we are just referencing the original value address and are not being allowed to modify its contents)

More misunderstanding... >= or Set, will COPY. try = or Ref

I thought Ref/= creates immutable variables and Set creates mutable ones.
I can't Push into .seqvar since its immutable if I create it via Ref
[1 2 3] = .seqvar
4 (Push .seqvar)
.seqvar (Log)
;; => Error: Push variable name already used as Ref. Overwriting a previously Ref variable with Push is not allowed, name: seqvar, input shard: Push

Expected.

[1 2 3] >= .seqvar     ;; the const [...] IS COPIED INTO .seqvar
[1 2 3] = .seqvar ;; the const is simply referenced

Yeah, means the same thing right?

>= creates a mutable variable (since we copied the const into a new location and are free to change this new location data)
= creates an immutable variable (since we are just referencing the original value address and are not being allowed to modify its contents)

Good yes

More misunderstanding... >= or Set, will COPY. try = or Ref

I thought Ref/= creates immutable variables and Set creates mutable ones.
I can't Push into .seqvar since its immutable if I create it via Ref
[1 2 3] = .seqvar
4 (Push .seqvar)
.seqvar (Log)
;; => Error: Push variable name already used as Ref. Overwriting a previously Ref variable with Push is not allowed, name: seqvar, input shard: Push

This just won't work because of all the rules we have.
What I mean is
1 >> .x
2 >> .x
3 >> .x
{:k .x}
...

As to have a variable sequence that ends into a table.

[1 2 3] >= .seqvar                  ;; create a sequence variable
4 (Push .seqvar)                    ;; `Push` into seqvar instead of table
{:k .seqvar} >= .table              ;; use seqvar as sequence value in table
.seqvar (Log)                       ;; => [1, 2, 3, 4]
.table (Log)                        ;; => {k: [1, 2, 3]}

This works, make sure you do it in the right order

Ah, I get it now - you meant use a variable to Push your value into and then use that var as transit to carry your pushed value into the table key/value pair.
I'll mention this in the details doc for Push.

[1 2 3] >= .seqvar                  ;; create a sequence variable
4 (Push .seqvar)                    ;; `Push` into seqvar instead of table
{:k .seqvar} >= .table              ;; use seqvar as sequence value in table
.seqvar (Log)                       ;; => [1, 2, 3, 4]
.table (Log)                        ;; => {k: [1 2 3 4]}

This works, make sure you do it in the right order

And I'll this sample to Push docs.
Thanks

Merged the fix #337

repo: fragcolor-xyz/shards


text:
bug: Virtual list append item update will miss items render

Framework7 version: 4.4.6
Platform and Target:  Chrome browser
Live Link or JSFiddle:  https://jsfiddle.net/mohshraim/1xs382bu/

Describe the bug
when add items to VL then scroll top, result that top items will disappear.
To Reproduce
Steps to reproduce the behavior:
please check jsFiddle:  https://jsfiddle.net/mohshraim/1xs382bu/
1- open about page
2- scroll to buttom until reach item 49 which will load with delay
3-scroll to top again,, top items will disappear..
+
4- while you are on top of page  click on nav buttton updateVL
5- this will show top items again... but when you scroll down bottom items will disappear.
and so on
THANKS

У меня была внешне похожая ситуация, причина - ошибка в моем коде. Рекомендую вам сравнить свой код с Kitchen, там все работает.

@shastox
Kitchen doen't contain any example with virtualList.appendItems  which is the reason of bug in indirect way that prevent virtualList.render () from working as expected.

Я за вас нашел ошибку в вашем коде:
 if (reachEnd) {
        app.infiniteScroll.destroy('#feed-list-pageContent'); //ERROR
        $$('#feed-list-infinite-scroll-preloader').remove();
      }

Вы просто уничтожаете page-content когда доходите до низа.

@shastox
This related
but i didnt destroy the page content,, i destroy infiniteScroll  component
to stop fire on('infinite', function () { ....
while i was tracing the source code on F7 i found that destroy infiniteScroll component will stop
VirtualList.prototype.handleScroll() from firing at F7 core... line 16827 ...
so in another words destroy infinitScroll will stop handelScroll on virtualList..
so bug is special case
and my work around to stop the destroy on infinitScroll and keep ignoring on('infinite', function () { ....  by adding any public variable..
will keep it open and let  @nolimits4web check if that should be fixed or ignored
Thanks @shastox  for your help

authors: mohshraim shastox


text:
Add code examples

This PR adds several examples to demonstrate how to use the low-level and high-level APIs of the parquet-go library.

Codecov Report

Merging #11 (9f47621) into master (d467d48) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   84.62%   84.62%
=======================================
  Files          46       46
  Lines        8135     8135
=======================================
  Hits         6884     6884
  Misses        895      895
  Partials      356      356

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 d467d48...9f47621. Read the comment docs.

authors: akrennmair codecov-io

repo: fraugster/parquet-go


text:
🛑 Senior School Website is down

In 3d162ca, Senior School Website (https://www.cranleigh.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Senior School Website is back up in 7e9a033.

repo: fredbradley/upptime


text:
Updating target "not found"

I'm having some problems trying to update a target through the REST API:
When updating an existing target through PUT I receive a Not Found error.
The logs show the following output:
[25/Mar/2016:23:36:13 +0000] "PUT /api/targets/target/56f5c99603c700200a96bfdf HTTP/1.1" 404 46 "-" "-"

The target with the specified ID does exist:

And I'm sending the following JSON to the server (I first do a GET for the specified target and modify the applications array before trying to PUT):
{ name: 'Inhouse',
  description: 'Target group for all Inhouse applications',
  applications: [],
  id: '56f5c99603c700200a96bfdf' }

Is this a bug, or am I doing something wrong?

I still haven't found a solution.
Did you have the chance to take a look?

Found the problem, but encountered another one while fixing it...
As a workaround, remove the id from the url, it will be taken from the json object.

Yes this seems to work.
Thanks!

I assume the "other" problem you have encountered is this one?:
(when viewing the details of a target, after removing an application that is inside that target)

TypeError: /opt/pushserver/app/views/administration/target/view.jade:25
    23|                 p.form-control-static
    24|                 each app in obj.applications
  > 25|                   span [#{allApplications[app].type}]#{allApplications[app].name} -
    26|             +backToListButton
    27|

Cannot read property 'type' of undefined
    at eval (eval at <anonymous> (/opt/pushserver/node_modules/jade/lib/index.js:218:8), <anonymous>:634:64)
    at eval (eval at <anonymous> (/opt/pushserver/node_modules/jade/lib/index.js:218:8), <anonymous>:661:4)
    at eval (eval at <anonymous> (/opt/pushserver/node_modules/jade/lib/index.js:218:8), <anonymous>:868:22)
    at res (/opt/pushserver/node_modules/jade/lib/index.js:219:38)
    at Object.exports.renderFile (/opt/pushserver/node_modules/jade/lib/index.js:380:38)
    at Object.exports.renderFile (/opt/pushserver/node_modules/jade/lib/index.js:370:21)
    at View.exports.__express [as engine] (/opt/pushserver/node_modules/jade/lib/index.js:417:11)
    at View.render (/opt/pushserver/node_modules/express/lib/view.js:126:8)
    at tryRender (/opt/pushserver/node_modules/express/lib/application.js:639:10)
    at EventEmitter.render (/opt/pushserver/node_modules/express/lib/application.js:591:3)
    at ServerResponse.render (/opt/pushserver/node_modules/express/lib/response.js:961:7)
    at /opt/pushserver/app/routes/frontend.js:157:13
    at Promise.<anonymous> (/opt/pushserver/app/controllers/crud.controller.js:65:7)
    at Promise.<anonymous> (/opt/pushserver/node_modules/mongoose/node_modules/mpromise/lib/promise.js:177:8)
    at Promise.emit (events.js:107:17)
    at Promise.emit (/opt/pushserver/node_modules/mongoose/node_modules/mpromise/lib/promise.js:84:38)
    at Promise.fulfill (/opt/pushserver/node_modules/mongoose/node_modules/mpromise/lib/promise.js:97:20)
    at /opt/pushserver/node_modules/mongoose/lib/query.js:1406:13
    at model.Document.init (/opt/pushserver/node_modules/mongoose/lib/document.js:254:11)
    at completeOne (/opt/pushserver/node_modules/mongoose/lib/query.js:1404:10)
    at Immediate.cb (/opt/pushserver/node_modules/mongoose/lib/query.js:1158:11)
    at Immediate._onImmediate (/opt/pushserver/node_modules/mongoose/node_modules/mquery/lib/utils.js:137:16)

Nope, it's another issue: when modifying both the list of applications & the name of a target, mongo behave... strangely to handle the update.
I'll fix the GUI for the "not app in target" issue.

Fixed on master.

authors: csysmans fredericbarrau

repo: fredericbarrau/pushserver


text:
Add second set of prerequisites

❓ What type of PR is this?

[ ] Refactor ♻
[x] Feature ✨
[ ] Bug Fix 🛠
[ ] Optimization 🚀
[ ] Documentation Update 📄
[ ] CI/CD 🤖

💬 Description

This PR is additional to the first set of prerequisites.
🎟 Related Tickets & Documents

Related Issue #2

🃏 Added/updated tests?
We encourage you to keep the code coverage percentage at 90% and above.

[x] Yes
[x] No, because this is not necessary.
[ ] No, and this is why:
[ ] I need help with writing tests

🌿 What branch would you like to merge this into?

develop
📷 [optional] What gif best describes this PR or how it makes you feel?

Summary by CodeRabbit

New Features

Introduced a new configuration option for code formatting, allowing for a maximum line length of 100 characters.
Added new configuration files to support module resolution, enabling cleaner import paths.
Introduced a new dependency to enhance the application's icon and UI component capabilities.
Created a central App class for managing application elements with improved structure.
Implemented two new test suites to ensure reliability of core functionalities.
Replaced user interaction logic with a structured application initialization process.

Bug Fixes

Enhanced error handling in the app initialization process.

Chores

Cleaned up the index.html file by removing extensive inline styles for better maintainability.

🚨 Check Failures: The checks are failing, but don’t worry! The issue is due to the main-page file not being included in this PR. The failure comes from commit 2bb4033 because main-page is not yet available. All good! 😊

This PR is needed as it stands. If there are additional prerequisites, please open a separate PR for those. Thanks! 🙌


text:
Added Quiz Question

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

HI @sinduraDasi!
Thank you for your interest in the Developer Quiz Site!
I noticed that you had attempted a few times to contribute a quiz question but the test kept failing.
The reason why our automated tests were failing was because you had some syntax errors here
Link: "https://www.sanfoundry.com/1000-python-questions-answers"/,

The / outside of the quotes caused the tests to fail.
If you are still interested in contributing, we welcome you to update your forked copy of the repo with the latest changes and add your Python questions to this quiz file.
https://github.com/freeCodeCamp/Developer_Quiz_Site/blob/main/src/data/python-quiz.ts
You are free to open a new PR with your new changes and we can review it 👍
Happy coding!


text:
form element issue- will not run test and chrome says blocked due to unusual code

Challenge Create a Form Element has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos.

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

<form action="/submit-cat-photo"> <input type="text" placeholder="cat photo URL"></form>

@katrenah thanks for the issue, and sorry that you're running into this issue. This is a known issue https://github.com/freeCodeCamp/freeCodeCamp/issues/13727. A quick workaround is to use a different browser than Chrome. Closing as duplicate and in favor of the previous issue. Happy coding!

authors: erictleung katrenah

repo: freeCodeCamp/freeCodeCamp


text:
Managing Packages with Npm - How to Use package.json, the Core of Any Node.js Project or npm Package

Describe your problem and - if possible - how to reproduce it
In Introduction to the Managing Packages with npm Challenges it says to click the following link to create a glitch project for the following lessons:
https://glitch.com/#!/import/github/freeCodeCamp/boilerplate-npm
or to clone the following repository:
https://github.com/freeCodeCamp/boilerplate-npm/
I did both and tried both for the next lesson How to Use package.json, the Core of Any Node.js Project or npm Package.
Cloning the repo and changing it just flat out doesn't work. Here's my repo on Github. If I put a link to my repo and submit the challenge, it fails with the message "package.json should have a valid "author" key" and this in the console:

it looks like the test is adding api into the filename and not even finding the package.json.
The issue with glitch is a bit trickier. It works fine on Firefox. However, if you use the original link at the start of the npm lessons to create your glitch project on Chrome, instead of getting a clone of the FCC project as your starter project, you get the base glitch app as your starter project. And, it doesn't work for the tests. (This is the app I got, https://flashy-paperback.glitch.me, it's not the FCC starter)
Note: If you originally create the Glitch app by clicking the "click here" on Chrome, the app that is created won't work for submitting lessons regardless of browser. You have to actually "click here" on Firefox, then you get a Glitch project that will work for the lessons in Firefox or Chrome.
Note that the Chrome issue might be more a Glitch issue with Chrome on Manjaro, for some reason Glitch runs super-slow, lags out, and crashes on Chrome for me.
Add a Link to the page with the problem
Tell us about your browser and operating system

Browser Name: Chrome
Browser Version: Version 66.0.3359.181 (Official Build) (64-bit)
Operating System: Manjaro Linux 17.1.10

If possible, add a screenshot here

@P1xt I looked at the source code of this challenge here.
The tests will pass only when provided_url + '/_api/package.json' returns a package.json file.
Thus, a github url will never pass the test.
Also, if you use any glitch project other than FCC starter code then it will not have a route /_api/package.json which serves the package.json file.  Hence, the tests will fail again.
If you look at the server.js in FCC starter file. You will find this code
app.route('/_api/package.json')
  .get(function(req, res, next) {
    console.log('requested');
    fs.readFile(__dirname + '/package.json', function(err, data) {
      if(err) return next(err);
      res.type('txt').send(data.toString());
    });
  });

This needs to be present only then the tests will pass.

@anku255 Yes, that is my point. The instructions specifically state that you can clone and use the github repo instead of Glitch - but

Thus, a github url will never pass the test.

Also, using Glitch to do the project was (for me) impossible on Chrome.

Hi @P1xt , @anku255
I found a work around for the GitHub instructions.
One can first create a feature branch named _api, make the required changes in package.json.
Then navigate to the modified package.json and click on raw format. Copy the url for the raw format.
In my case, it is _https://raw.githubusercontent.com/mihir-mahakalkar/boilerplate-npm/_api/package.json_.
The last step is to delete /_api/package.json string from the above url, and then paste it in the challenge input field. In my case, it should be _https://raw.githubusercontent.com/mihir-mahakalkar/boilerplate-npm_

@mihir-mahakalkar this solution worked for me. Well done. Thanks!

@DaniloNovakovic Thanks :+1:

that happen to me some timeout, idk why

same as @rabindranathfv, I noticed that after cloning the glitch project it thinks there is no 'package.json' and to run 'refresh' from the console. After which there are very few files left.
steps:

clone project using glitch link provided
see small error msg in top right that say's something went wrong
logs are complaining over and over that package.json does not exist
run refresh from the console and see that in fact the only files present are /assets and .env.

confirmed on codesandbox.io as well by cloning the github repo with a similar error message. On attempting to create a new sandbox from the github repo there is an error about missing package.json and the clone fails.
steps:

https://codesandbox.io/s/github
paste in https://github.com/freeCodeCamp/boilerplate-npm/
error page: something went wrong, could not find package.json

Glitch not working at all, neither is cloning from github.  Changing the package.json in glitch, and it basically deletes all the files, then tries to look for /app/server.js  from the bootstrap.  Doesn't read the json from github raw

For the section "Introduction to the Managing Packages with npm Challenges" we should not expect the students to have to run the server to get the _api/package.json route as nowhere in the instructions state that. Instead suggest what @unicorn93 mentioned. Or have them create a _api folder in their repo with a package.json in it

The section "Introduction to the Managing Packages with NPM Challenges" using the git repo, the instructions to run server.js to get the _api/package.json route are missing.
Maybe the instructions should suggest what @unicorn93 mentioned (https://github.com/freeCodeCamp/freeCodeCamp/issues/17584#issuecomment-409392042) or have them create an _api folder in their repo with a package.json in it
If you look at the challenges in the section, it's only a newbie intro to package.json. The folder structure and server set up seems complex for this purpose and does not provide enough instruction for git repo users.

Hi @P1xt , @anku255
I found a work around for the GitHub instructions.
One can first create a feature branch named _api, make the required changes in package.json.
Then navigate to the modified package.json and click on raw format. Copy the url for the raw format.
In my case, it is _https://raw.githubusercontent.com/mihir-mahakalkar/boilerplate-npm/_api/package.json_.
The last step is to delete /_api/package.json string from the above url, and then paste it in the challenge input field. In my case, it should be _https://raw.githubusercontent.com/mihir-mahakalkar/boilerplate-npm_

This worked for me as well on a fork of tha repo. Because the check function as @anku255 noticed look fro that path

I cant unterstand what need to do.. I did everything suggested here, but it's not work

I used github to do the "Basic Node and Express" tutorial but when I gave it my link, it always gave me a 404 error message even though I submitted the raw JSON and checked my answers online. If you checkout the following users in the thread, anku255 and unicorn93, they provide a solution to the problem. However, this only worked for the "Managing packages with npm" tutorial but not the Node and Express. If you take a look at line 17 in the following link, here, it shows what url is required and what it appends. I did that way but it still didn't work.

Having the same issue.  Code and app link I submitted.  (Actually, I tried all links Glitch would give me -- project, live app, code, and the "view" page link.)    Firefox 77.0.1 (64-bit, Win 10).

@themagicbean , Whilst this may not be the issue you are facing, please note: Glitch has been highly unstable, for the past month. The status of Glitch can be found here: https://status.glitch.com/

Tested with the current production site and by forking the boilerplate-npm repo with this link on the Introduction to the Managing Packages with npm Challenges intro page: https://repl.it/github/freeCodeCamp/boilerplate-npm
Went through all the challenges in this section on Repl.it and didn't run into any issues.

Hello, I've just started this course and have experienced the same error as reported before, however, I am using Repl.it.  I tried the earlier suggestion of sharing the raw data link from Github and still get an error about missing a valid author key.  I also tried removing all the existing code so the file only had "author": "hollidayeric", remaining.
Here is my Repl.it file link: https://repl.it/@hollidayeric/boilerplate-npm#package.json.  In case it was something with creating the code in my own Repl.it account I did it anonymously as well.  I still received the error and am not able to proceed.  Please share any suggestions or steps I may have missed.
Here is the code as it currently appears in Repl.it:

Here is the link and Test Result from the course:

@hollidayeric The link you are providing in the solution box is not the link to the live app the tests need access to.
The link to submit should look something like:
https://boilerplate-npm.hollidayeric.repl.run
And is available to copy from the preview browser URL bar
Hope this clarifies

@Sky020 - Thank you!  I still had trouble with https://boilerplate-npm.hollidayeric.repl.run.  I opened the editor in a new window and noticed the link is slightly different for the program.  It is running and works to submit the lessons with this link: https://boilerplate-npm.hollidayeric.repl.co

Fork from https://github.com/freeCodeCamp/boilerplate-npm.git
add "author": "your name"
run
copy link after appear

authors: IgorSushko1 P1xt Sky020 TCarmine TheNewStyles anku255 designerdarpan hollidayeric htkoca ilobo22 jminkler mihir-mahakalkar rabindranathfv robjloranger scissorsneedfoodtoo themagicbean trikunc


text:
[learn-css-transforms-by-building-a-penguin]: step-2 first test

Describe the Issue
The test fails to catch the difference between an element and class selector
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-css-transforms-by-building-a-penguin/step-2
Your code
.body {
  background: linear-gradient(45deg, rgb(118, 201, 255), rgb(247, 255, 222));
}

The hint is

You should set background to linear-gradient(45deg, rgb(118, 201, 255), rgb(247, 255, 222)).

But the first hint should be displayed instead:

You should use the body element selector.

The regex fails to tell the difference between an element and class selector.
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/14-responsive-web-design-22/learn-css-transforms-by-building-a-penguin/61967e74a8e3690ab6292daa.md
Expected behavior
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/14-responsive-web-design-22/learn-css-transforms-by-building-a-penguin/61967e74a8e3690ab6292daa.md
Screenshots
No response
System
All
Additional context
No response

We should just use the getStyle method on the CSSHelp class to look for 'body'. Examples of this can be seen in other tests.

An issue with the https://github.com/freeCodeCamp/freeCodeCamp/labels/help wanted or https://github.com/freeCodeCamp/freeCodeCamp/labels/first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute, and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum

Hi @ShaunSHamilton, My name is Om Bansal and this is my first time contributing to open source can i work on this issue?

Go for it - we will accept the first fully correct PR that fixes the issue.

authors: Ombansal744 ShaunSHamilton jeremylt


text:
fix(email): Check unquiness of email

This should let us check for uniqueness of email when the user attributes are updated via the API.

I have back-ported some utils from #9660
Tested this with a duplicate user instance and reset password logic, which is the most cited area of this issue.

Note: I have although left the error message display to a raw message returned from loopback, this is done intentionally because the entire reset logic is going away in any case with passwordless.
@BerkeleyTrue:
Also, any users already duplicated will be affected. To find out we should do some backend purging or notifications to such users.

Also do we need this on production?

@raisedadead We originally removed the email check because we only allowed third party sign ups, and that resulted in only having usernames as unique to everyone.
Since we are now moving to email first validation, should we just remove the email validation deletion?

@BerkeleyTrue Excellent point, yes we should do that when we remove GitHub auth completely (maybe after passwordless goes in).
Until then this is we would still need this (as we are still creating user accounts, with GitHub)

Ok, then an addition to passwordless would be to remove the ability to create accounts with github and re-add the original email validations.

@BerkeleyTrue Yes, that is correct and https://github.com/freeCodeCamp/freeCodeCamp/issues/10407 should address this.
I have updated the user stories so that this is tracked there.

Just confirming again, do we need this on production?

authors: BerkeleyTrue raisedadead


text:
fix(challenges): Call resetQuiz() when dashedName of the quiz changes

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #16801
Description
'currentIndex', 'selectedChoice' and 'correct' state variables of the Quiz
component were not changing when navigating to other quiz challenges
through map. Fixed it by calling resetQuiz() whenever dashedName of
the quiz changes.

@Bouncey i have made the changes requested.

Great work! Thanks @YogeshSharma0201 :+1:


text:
feat(interview-prep): Gamma Function

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[ ] Small bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[ ] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #XXXXX
Description

Thanks for the PR. We will review this soon /cc @scissorsneedfoodtoo

:+1: Everything LGTM! :+1:
Thank you again for your contribution, @NitronR. Looking forward to the next!

authors: NitronR raisedadead scissorsneedfoodtoo


text:
A React environment spell-checked

Corrected some mistakes.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@LeWanderer It looks like you edited a guide article that has been moved, so I am closing this PR. If you still want to make this contribution please submit another PR.

authors: LeWanderer joshalling


text:
Text Editing

Changed some translations to improve the text in spanish.

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for  creating this PR.  However, since it was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you.

Hi @don0t
As there has been no response from your end for a while, we are closing this PR.
Feel free to request this PR to be reopened or create a new PR, if you still wish to make the changes you originally added plus any additional change requests asked of you.  Also, remember to update your fork, so you have the latest version of master in case it has changed significantly.
Happy Coding!


text:
Add MDN docs link

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks for the PR @yusuf-delvi, but MDN was added with a previous merge. We welcome future contributions, thanks and happy coding!


text:
Fixed typo from "getHachedEggCount" to "getHatchedEggCount"

Original wording: getHachedEggCount
New wording: getHatchedEggCount

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Congrats @JulienGS25 on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


text:
fix(docs): Update troubleshooting and include docker commands

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

As discussed in #35841 the troubleshooting section needed updating.

Thanks @SammyHass and @RandellDawson for the suggestions.  I went with Randell's wording for the opening paragraph as I felt it fit better with the overall tone of the document.  Sammy's point about verbosity was a good one, but I used **Stuff** rather than a header to be consistent with earlier in the document.

@SammyHass The OP has made some changes.  Do you think these are better than the original version?

@Manish-Giri as far as I understand it, it needs to be run, but only once.  It sets the ownership of various directories to allow a less privileged user (called node) to install packages in them.

authors: RandellDawson ojeytonwilliams


text:
Update it

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[ ] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.

authors: RandellDawson vidhidrana


text:
Web interface: build.html: Invalid request or no data available yet.

Prerequisites

☑ Have you checked for an existing issue describing your problem?
☑ Are you running the latest version?
☑ Is your ports tree recent?
☑ Is your FreeBSD Host on a supported release?

Describe the bug
At (for example):
file:///usr/local/poudriere/data/logs/bulk/main-default/2021-05-28_14h04m32s/build.html
– whilst packages are built:

Invalid request or no data available yet.

How to reproduce
Steps to reproduce the behaviour:

poudriere ports -u
put in place the four files from https://codeberg.org/Alexander88207/FreeBSD-Ports/src/branch/main/print/pdfarranger
poudriere bulk -b latest -J 3 -j 13 print/pdfarranger
in Firefox, visit:

/usr/local/poudriere/data/logs/bulk/main-default/latest/build.html
Expected behaviour

build progress.

Screenshot

Environment

Host: 13.0-RELEASE-p1
Jail: 13.0-RELEASE-p1
Browser: Firefox 88.0.1, Surf 2.1
Poudriere version: poudriere-devel-3.3.99.20210521
Ports branch and revision: latest

root@mowa219-gjp4-vm-freebsd-13-zfs:~ # poudriere jail -i -j 13
Jail name:         13
Jail version:      13.0-RELEASE-p1
Jail arch:         amd64
Jail method:       http
Jail mount:        /usr/local/poudriere/jails/13
Jail fs:           zroot/poudriere/jails/13
Jail updated:      2021-05-27 12:57:17
Jail pkgbase:      disabled

Additional context
I get the same – Invalid request or no data available yet. – with poudriere-devel-3.3.99.20210521 on 14.0-CURRENT.

It's a Firefox restriction on file://. From what I recall it is against javascript and cross-site requests.
@bsdjhb What did you do to fix this?

Thanks, now I see:
file:///usr/local/poudriere/data/logs/bulk/main-default/latest/build.html

works in Falkon and qutebrowser …

… might also work in Konqueror (the Go button is broken, I haven't reported the bug yet)

In Firefox the following setting in about:config helps.
security.fileuri.strict_origin_policy=false

Just wanted to write that this is also happening on Chromium - Version 106.0.5249.119 (Official Build) (64-bit) (I'm guessing for similar reasons). Besides disabling these security settings (or using a different browser), would it be possible to have an easier/official way to get access to all build information? Essentially it would be nice to get some sort of print out like synth. I don't use synth (just poudriere on both my server and my laptop, but the synth ui output list was nice ;D).

Just a quick note: the issue can also be server side: I ran into this issue using Safari on the Mac.
When I looked at the page using the Developer Console, I found that apache24 was throwing 403s for */.data.json files, as my server is locked down to prevent serving most files that start with a dot.
I tweaked my httpd-vhosts.conf file to permit these files, and all is well.

Maybe a peculiarity of my everyday Firefox profile … with the more modern design, I no longer see the originally reported phrase,

Invalid request or no data available yet.

Firefox to the left, qutebrowser to the right:

authors: Schamschula bdrewery fearedbliss grahamperrin lherschi

repo: freebsd/poudriere


text:
About Memory Port when add --repl-seq-mem command to generate verilog

I use SeqMem to generate a ram with a white mask. And I add --repl-seq-mem this command to Replace sequential memories with black boxes.
However, the clock, en and address port are divided into reading and writing as the following codes.
ram ram ( // @[DescribedSRAM.scala 20:21]     .R0_addr(data_arrays_0_R0_addr),     .R0_en(data_arrays_0_R0_en),     .R0_clk(data_arrays_0_R0_clk),     .R0_data_0(data_arrays_0_R0_data_0),     .R0_data_1(data_arrays_0_R0_data_1),     .R0_data_2(data_arrays_0_R0_data_2),     .R0_data_3(data_arrays_0_R0_data_3),     .W0_addr(data_arrays_0_W0_addr),     .W0_en(data_arrays_0_W0_en),     .W0_clk(data_arrays_0_W0_clk),     .W0_data_0(data_arrays_0_W0_data_0),     .W0_data_1(data_arrays_0_W0_data_1),     .W0_data_2(data_arrays_0_W0_data_2),     .W0_data_3(data_arrays_0_W0_data_3),     .W0_mask_0(data_arrays_0_W0_mask_0),     .W0_mask_1(data_arrays_0_W0_mask_1),     .W0_mask_2(data_arrays_0_W0_mask_2),     .W0_mask_3(data_arrays_0_W0_mask_3)   );
What should I do, If I want to generate a ram like this.
module ram(   input RW0_clk,   input [9:0] RW0_addr,   input RW0_en,   input RW0_wmode,   input [3:0] RW0_wmask,   input [31:0] RW0_wdata,   output [31:0] RW0_rdata );

You can take a look at https://github.com/freechipsproject/chisel3/wiki/Memories#mem to see how to infer a single-port read-write memory.

You are right.
I find that I can add the "-infer-rw" command to generate the single port ram without changing codes while executing chisel.
Thanks a lot.


text:
Add Protobuf FIRRTL Emitters

Add a new API that enables users to include FIRRTL emitters that write protobuf.
Checklist

[x] Did you write out a description of the feature you want to see?
[x] Did you look around for any related features?
[x] Did you specify relevant external information?

Feature Description
Add the ability for users to include protobuf emitters like how they include FIRRTL emitters.
As one API idea, a user could do the following to write low FIRRTL to a Foo.pb file.
firrtl -i Foo.fir -X low -o Foo.pb

Type of Feature

new feature/API

Related Features
A user can manually do this with firrtl.proto.ToProto.writeToStream. However, no protobuf emitter transform exists making protobuf emission a second-class citizen.
External Information
This was requested on Gitter/Matrix (permalink).

One issue with deriving it from the file extension of the output file is it doesn't work with -e, so I think it needs to be a separate argument like --emit-proto|-pb or something.

Yeah, good point.
The unambiguous option here is via --custom-transforms and with an output file annotation that's sensitive to a specific emitter. Since we now support multiple emitters, a single output file really isn't expressive enough for supporting multiple emitters.
I do think a simpler API could be supported like: -Xlow:proto:modules:Foo.bar or -Xhigh:firrtl:circuit:Baz.qux. These are equivalent to a more verbose option format, e.g., --custom-transforms LowFirrtlEmitter --emitter-option LowFirrtlEmitter:proto --emitter-option LowFirrtlEmitter:modules --emitter-option LowFirrtlEmitter:filenameBase:Foo.bar. But, there's a clear expansion of simpler, shorthand options to more complex ones.

authors: jackkoenig seldridge

repo: freechipsproject/firrtl


text:
Exporter Crashes on Logfile with non UTF8 Chars

Hi There,
my exporter is crashing when it's trying to read a logfile which contains "non UTF8" Chars.
INFO[0000] Starting Prometheus Oracle exporter 1.1.3     source="main.go:942"
INFO[0000] Config loaded:  /etc/prometheus-oracle.yml    source="main.go:944"
INFO[0000] Listening on :9161                            source="main.go:952"
panic: label value "Fehler beim autom Ausf\xfchren von Job 128" is not valid UTF-8
goroutine 34 [running]:
github.com/prometheus/client_golang/prometheus.(*GaugeVec).WithLabelValues(0xc000132128, 0xc0002ef360, 0x5, 0x5, 0x100ee40, 0x0)
/root/go/src/github.com/prometheus/client_golang/prometheus/gauge.go:217 +0xe0
main.(*Exporter).ScrapeAlertlog(0xc000150100)
/usr/local/prometheus_oracle_exporter11/alertlog.go:145 +0x825
main.(*Exporter).Collect(0xc000150100, 0xc0001405a0)
/usr/local/prometheus_oracle_exporter11/main.go:879 +0x2c6
github.com/prometheus/client_golang/prometheus.(*Registry).Gather.func1()
/root/go/src/github.com/prometheus/client_golang/prometheus/registry.go:442 +0x19d
created by github.com/prometheus/client_golang/prometheus.(*Registry).Gather
/root/go/src/github.com/prometheus/client_golang/prometheus/registry.go:534 +0xdf8
from the alert log:
ORA-12012: Fehler beim autom Ausfhren von Job 128
i just fixed the log, but you might want to have a look at it if you like ;)

Thanks, Fixed:
https://github.com/freenetdigital/prometheus_oracle_exporter/commit/4d84f80ce204cd60495a5ac212424a47b4b8a960

awesome! thx @floyd871