Build Error When Testing Hazy State Tracking

$ coverage run --parallel-mode --source="." inquisition.py -c build/src/conf/build_hazy_tracking_enabled.cfg
Traceback (most recent call last):
 File "inquisition.py", line 173, in <module>
/home/travis/virtualenv/python3.5.3/lib/python3.5/site-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
 InsecureRequestWarning)
 main()
 File "inquisition.py", line 157, in main
 erudite.startAnomalyDetectionEngine()
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 640, in startAnomalyDetectionEngine
 self.performTrafficNodeAnalysis()
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 548, in performTrafficNodeAnalysis
 dstNodeFieldName = self.getFieldNameFromType(typeID=3)
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 111, in getFieldNameFromType
 hostFieldName = dbResults['field_name']
KeyError: 'field_name'
Traceback (most recent call last):
 File "inquisition.py", line 173, in <module>
 main()
 File "inquisition.py", line 157, in main
 erudite.startAnomalyDetectionEngine()
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 640, in startAnomalyDetectionEngine
 self.performTrafficNodeAnalysis()
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 547, in performTrafficNodeAnalysis
 srcNodeFieldName = self.getFieldNameFromType(typeID=2)
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 111, in getFieldNameFromType
 hostFieldName = dbResults['field_name']
KeyError: 'field_name'
Traceback (most recent call last):
 File "inquisition.py", line 173, in <module>
 main()
 File "inquisition.py", line 157, in main
 erudite.startAnomalyDetectionEngine()
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 640, in startAnomalyDetectionEngine
The command "coverage run --parallel-mode --source="." inquisition.py -c build/src/conf/build_hazy_tracking_enabled.cfg" exited with 0.
 self.performTrafficNodeAnalysis()
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 548, in performTrafficNodeAnalysis
 dstNodeFieldName = self.getFieldNameFromType(typeID=3)
 File "/home/travis/build/magneticstain/Inquisition/lib/destiny/Erudite.py", line 111, in getFieldNameFromType
2.35s hostFieldName = dbResults['field_name']
KeyError: 'field_name'

This bug is happening in this function:
    def getFieldNameFromType(self, typeID):
        """
        Get name of field to use based on type ID

        :return: str
        """

        hostFieldName = ''

        # define sql
        # DEV NOTE: pymysql seems to have some sort of bug where it only validates strings correctly.
        # If we use %d here, execute will fail even if we explicitly cast typeID as an int.
        sql = """
                SELECT
                    field_name
                FROM
                    Fields
                WHERE
                    field_type = %s
                LIMIT 1
            """

        # execute query
        with self.inquisitionDbHandle.cursor() as dbCursor:
            dbCursor.execute(sql, typeID)

            # fetch results
            dbResults = dbCursor.fetchone()
            if dbResults:
                hostFieldName = dbResults['field_name']

        return hostFieldName

Adding an IndexError exception catch for field_name should resolve this. Additionally, we should have the records added to the build sql file since these records are expected to be present after installation.

Changed to:
        # get field names associated with each field type
        try:
            srcNodeFieldName = self.getFieldNameFromType(typeID=2)
            dstNodeFieldName = self.getFieldNameFromType(typeID=3)
            self.lgr.debug('using [ ' + str(srcNodeFieldName) + ' ] field as source traffic node and [ '
                           + str(dstNodeFieldName) + ' ] field as destination traffic node')
        except KeyError as e:
            self.lgr.warning('problem while trying to identify field names, skipping traffic analysis  :: [ ' + str(e)
                             + ' ]')
            return

Fixed with commit https://github.com/magneticstain/Inquisition/commit/61dcc0e57aa11c20c4d30a6dc861489664dd88c2
$ coverage run --parallel-mode --source="." inquisition.py -c build/src/conf/build_hazy_tracking_enabled.cfg
/home/travis/virtualenv/python3.5.3/lib/python3.5/site-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)
The command "coverage run --parallel-mode --source="." inquisition.py -c build/src/conf/build_hazy_tracking_enabled.cfg" exited with 0.

Completed with commit https://github.com/magneticstain/Inquisition/commit/3c59315d8ebcdbef39e6d62c31f1eecd0710e203


npm start do not work in examples/js/e-commerce on windows

🐛 Current behavior
When running npm-start we are getting below error on windows systems
BABEL_ENV' is not recognized as an internal or external command.
Suggested fix - add cross-env in package.json has fixed the issue.
🔍 Steps to reproduce
go to instantsearch-master\examples\js\e-commerce
type npm install
type npm start
error - BABEL_ENV' is not recognized as an internal or external command
Live reproduction
https://codesandbox.io/s/github/algolia/instantsearch.js/tree/templates/instantsearch.js
💭 Expected behavior
Server should start at port 3000
Package version
1.15.0
Operating system
windows
Browser
chrome
Code of Conduct

[X] I agree to follow this project's Code of Conduct

What you should be able to do as a workaround is:
npm install  --save-dev cross-env

change package.json#script#start
"start": "cross-env BABEL_ENV=parcel parcel index.html --port 3000",

Thanks @Haroenv that was my suggested fix as well in the issue. But shouldn't this be updated in git as well?

You're actually the first person that has used these examples on Windows without WSL, so we weren't yet aware of the issue. I'll verify first if this is the only solution possible.


Allow duplicates

Patch to allow for export even if there are duplicate resources with the same key.
New -d option added to allow this

thanks for PR. this is much appreciated and duplicates definitely could be an issue when dealing with pile of XML files.. Can you please check that line regarding resourceKey.ToLower() ?

Pushed a new commit.
Now the compare is case insensitive but the key is imported in correct case of the first occurance of the key.
Will this work?

yup, this might blend


Trouble with deploing zip archives with terraform

Hello! I'm new to apex up and got trouble. I'm working with terraform to deploy all my resources to AWS and i need to create zip archives to deploy it on s3 and then on lambda. So, trouble is in 'main' file, that created, when i run 'up build' in all cases. This file blocks deploing to AWS with error: "zip achive must be non-empty'. When i delete main file from zip, deploing is fine without errors. So, what can i do with this issue? I have about 100 lambda funcs and  cannot delete it mannualy

Hmm I'm not sure I understand the scenario, you use Up to build and then Terraform to deploy? By default Up will build your program as ./server, and Up itself injects ./main (the Up proxy) before deploying so it becomes part of the zip.
The ./main is cmd/up-proxy, and it's stored in the up binary, so I guess if you wanted to avoid using up for deployments you would have to do your own build and copy it to ./main. This is where that happens https://github.com/apex/up/blob/cafa45273ba0949244219265f23803c47fda6947/platform/lambda/lambda.go#L907-L919

That issue depends only on project requirements. We used another apex app for build zip, but it became out of date. So we need another solution, but also we need to save our terraform scripts for deploying. TY for answer, i will try to use your advice


Return row count when inferring schema from JSON

arrow-csv's infer_schema() returns the number of records read, along with the schema.  This is useful information!  arrow-json's infer_json_schema(), on the other hand, only returns the schema itself.  It would be nice if it matched arrow-csv.

Arguably it's less important in arrow-json than it is in arrow-csv, since with NDJSON you can just count the newline characters to get the row count.  (As opposed to CSV, where quoted fields may contain newline characters without indicating a new row, so you really need to parse it to get the row count.)

label_issue.py automatically added labels {'arrow'} from #5008


store prometheus metrics in postgresql

Hi
I'm trying to store prometheus metrics in postgresql based on prometheus-postgresql-adapter. I modified the docker-compose.yml to the docker-compose-pg-old.yml.pdf (which includes 2 additional services corresponding to the first 2 containers in prometheus-postgresql-adapter, and comments out the local storage for prometheus). The prometheus.yml is modified as shown in the prometheus.yml.pdf to direct "read" and "write" to postgresql. I had to build the prometheus docker image to include the modified prometheus.yml.
The stack is deployed under the name "mon". The mon_prometheus should connect to the "mon_prometheus_postgresql_adapter", which in turn connects to mon_pg_prometheus (the postgresql database). The problem is that "mon_prometheus" service is unable to connect the "mon_prometheus_postgresql_adapter". The logs from "mon_prometheus" says:
level=error ts=2018-02-20T04:13:33.284782524Z caller=engine.go:544 component="query engine" msg="error selecting series set" err="error sending request: Post http://mon_prometheus_postgresql_adapter:9201/read: dial tcp: lookup mon_prometheus_postgresql_adapter on <IP_ADDRESS>:53: no such host"
Regards

mon is the stack name, Swarm DNS does not contain the stack name, so you should use prometheus_postgresql_adapter instead of  mon_prometheus_postgresql_adapter.

Thanks Stefan. The previous error is gone, but the postgresql metrics tables are still empty.
I removed all configurations related to "--storage.tsdb" from prometheus Dockerfile and the modified docker-compose.yml file. "remote_write" and "remote_read" point to "prometheus_postgresql_adapter" instead of "mon_prometheus_postgresql_adapter", but I don't know why metrics are not inserted into postgresql.
The logs of the "mon_prometheus" say:
level=warn ts=2018-02-20T16:21:33.776289124Z caller=queue_manager.go:225 component=remote msg="Remote storage queue full, discarding sample. Multiple subsequent messages of this kind may be suppressed.". If postgresql can't take more data, I expected, at least, to record some initial data, then stops receiving any more data.
Regards


feat: recommend adding new entry point to list all the Kernal routines by name and addresses

or revise initialization to also display names

BTW the term "monitor" is misleading, it's a Kernal profiler 😉

good point on terminology, punting for now.
initialization now displays names


Question: Is it possible to disable a tab header?

I can't see anything from the code around this. Would it be straightforward to add/do you accept PRs?

Friendly poke :-)

Friendly poke :-) @bartlenaerts

My apologises for the very late reply, but this is implemented in version 2.6.0. Thank you for your commit.


[Feature Request] Synchronize releases to upstream

Hello,
I'm building some Docker container and would like to sync with the upstream releases so my container will be automatically updated and deployed to a stable version. Is that possible with pull?
Thank you.

I recommend creating a workflow to do whatever you wish after the branch is updated.
Once you fork the repo, Create a new branch, make it the default branch, and add pull.yml as well as a workflow file with this trigger
on:
  push:
    branches:
      - master

You can then do anything you want in the workflow file including but not limited to build and deploy. This way you have maximum control of what you wish to do.

I guess you misunderstand my question. The problem now I'm facing is that pull only synchronize commits, not releases. And I would like to know if pull will implement it.

That will not be implemented but you can do it yourself using the workflow method in my comment above.

I see. Thank you.


Forget Password Page needed

Hi, almost every installation uses some kind of authentication provider like auth0, the password is only meant as a workaround. Therefore there is no such feature.


Changed the logic for proxies and absentee votes + little improvements

Count admitted delegates and votes to recieve correct.
Change authorized voters, if anything voting-related changes.
Update keypads, if a user is deleted. (fixes #41 )
Fixed typos in the migration
Changed proxy logic, so if a proxy has an absentee vote, it will not be overwritten. (fixes #37)

@jwinzer This should fix all the things we've spoken about yesterday. Please test it nd let us discuss this by phone.

This is not working correctly if you have "pure proxies", i.e. representatives with no own shares.
The terminology I've been using has somehow gotten messed up. I would like to restore it.
authorized voter: a present user with a keypad assigned. He may be authorized to vote for himself and/or others (mandates).
admitted delegate: a delegate who is admitted to cast a vote for a motion. He is admitted if he has voting shares AND an authorized voter (which can be himself).

Closed in favor of #52


update dependency to fix vulnerability

Address https://github.com/jonschlinkert/lazy-cache/issues/12
See https://ossindex.sonatype.org/vulnerability/CVE-2021-25949?component-type=npm&component-name=set-getter&utm_source=go-http-client&utm_medium=integration&utm_content=1.1

Created temporary copy till this PR is merged: https://www.npmjs.com/package/lazy-cache-copy


Open Daily Note taking precedence over Append to Daily Note?

This is great stuff!  I just got it set up.  Everything I've tried seems to work great, except od.  When I open Alfred and type od hello world, I see two results:

Open Today's note
Append to Today's Daily note

The top one is selected.  If I hit enter, it opens my note, but my text seems to be gone.  If I press down and then enter, it seems to append.
I went into the workflow, clicked on the od entry for opening, and changed it to No Arguments.
Now, it seems to work like I expect.  If I type od, it shows just Open Today's note, and then if I keep typing, it only shows Append to...
Is there something messed up with my setup, do you think?  Am I supposed to have to hit down in order to append with od foo?

good idea, changed it to your suggestion.


BACKLOG-20485 Get rid of unnecessary vars, add drop targets on lists,…

… update props

JIRA

https://jira.jahia.org/browse/BACKLOG-20485
Description
Get rid of unnecessary vars, add drop targets on lists, protect from dropping something that is not our list item, various improvements.

Wrong branch


Use cohere re-ranker after we got the reranked list of the fused documents

This could easily be an extra step between the final RAG preparation and the fusion reranking.
See https://github.com/pinecone-io/examples/blob/master/learn/generation/better-rag/00-rerankers.ipynb
import cohere

os.environ["COHERE_API_KEY"] = os.getenv("COHERE_API_KEY") or getpass.getpass()
co = cohere.Client(os.environ["COHERE_API_KEY"])
rerank_docs = co.rerank(
    query=query, documents=docs.keys(), top_n=25, model="rerank-english-v2.0"
)

We can use the reranker to enhance the augmentation for both the document and the connector RAG queries.


Changing the AWS federation username to use the vault-username

@thorix made me do it!

The code change looks fine, I am a bit concered about the number of go vendor packages that where added/removed for no code change.
I ran a go mod tidy and it cleans up most the added modules.

nice1

We talked about the change added there at the end. This will enable stim to source/validate the username from Vault. It seemed just trusting the set username from the stim config was maybe not the best. Also, maybe better code practice if the username didn't exist to go to the source. This is less of a security feature since the user could always take the Vault provided IAM creds and just generate their own STS AWS console access. The provided username is collected from the user and should never be trusted anyways...


change logging message in barback/pub

Consider the message:
Warning from Transformer on asset-path
Instead of:
Warning in Transformer on asset-path

This issue has been moved to dart-lang/pub#784.


[FEATURE] Enhancement - Email Security Hub findings/alerts based on risk rating

Email Security Hub findings/alerts based on risk rating

Shipping in v1.5.0 (version # could change)


Update Morpho Safe App

Safe app request
Create a request to update a Safe app

Revision checks

[X] Used smart contracts were audited.
[X] Your Safe App include a manifest.json file at the root with the required data.
[X] The app can be loaded as a custom Safe App in the Apps section of https://app.safe.global.
[X] The app auto-connects to the Safe.
[X] You are able to trigger and execute one transaction with a Safe.
[X] RPC requests are optimized (not triggering many requests in a very short time period).

Name/Description

Type

Update
The Morpho safe apps are batching txs but they are not flagged as Batch transactions apps in your UI
Is it possible to correct that?

Best regards
Compatible Networks

- Mainnet

Hi there! Sure thing, we will add the tag 😄 Will post a comment in here as soon as it is added.
Cheers!

It should be available now


As a Project coordinator, I want to see the number of days until the due date of a report

Description:
Make a custom widget for the due date, to be used in the Quarterly reports page
Acceptance Criteria:
Given that I see a due date widget
When I click on it
Then I see a calendar input
Given that I see a due date widget, with a selected date (e.g. Apr. 05, 2022)
When the number of days between the current date and the selected date is less than or equal to 60 days
Then the widget displays Due in X days (Apr. 05, 2022)
Given that I see a due date widget, with a selected date (e.g. Apr. 05, 2022)
When the number of days between the current date and the selected date is greater than 60 days
Then the widget displays Due in Y weeks (Apr. 05, 2022)

Development Checklist:

[ ] The widget should be accessible, i.e. being fillable with keyboard navigation
[ ] https://www.npmjs.com/package/react-datepicker is a good candidate for this component
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

Hey team! Please add your planning poker estimate with ZenHub @BCerki @dleard @gurjmatharu @mikevespi @pbastia @Sepehr-Sobhani

@matthieu-foucault any opinion on what the widget should display if the due date is past?

Only display the date in that case? @suhafa what do you think?

Only displaying the date works for 'Report Due Date'. As for 'Received Date' we could show it as following if past due:

Thanks @mikevespi!
A couple of observations/questions:

This ticket only applies to quarterly reports and I don't see a ticket that will apply this to all the reports? In particular, the due date count down.
I can't seem to trigger the overdue feature. It simply shows 0 days.

This ticket only applies to quarterly reports and I don't see a ticket that will apply this to all the reports? In particular, the due date count down.

I added it to the other reports in the received date PR @mikevespi

@LindsayMacfarlane The overdue function is only on the received date widget. They're one after the other so the information will be right there. That ticket is in flight right now I believe so should be in soon.

Thanks @mikevespi ! This is a really cool feature. I'll move this ticket to closed unless you still need it open?

I think it can close, the PR adding it to the other forms due dates was just merged, so will be in dev next release


Borders are not rendered as nicely as in screenshot

Hi. The borders look disconnected and bad for me, but the look nice in the screenshots. What could be the issue?
Terminal: Konsole
Config: https://github.com/lumbo7332/dotfiles/tree/main/dot_config/nvim

This will be either your terminal or your font. I'd recommend trying out some different fonts to see if that changes things, or a different terminal. Some terminals have special-case rendering to make box-drawing characters look correct. I personally switched from alacritty to kitty because most fonts I tried look like this or worse in alacritty.

Oh I understand. Thanks.


--json returns non-json string

🐛 Bug Report
--json option returns additional information about run tests alongside JSON output, which makes this option useless. Using --json option with --outputFile=test-result.json works correctly, since the file is created with the JSON-only content.
To Reproduce
Run:
yarn jest --watchAll=false --json
Current output:
yarn run v1.22.4
$ react-scripts test --watchAll=false --json
 PASS  src/App.test.js
  ✓ renders without crashing (18ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        0.938s, estimated 1s
Ran all test suites.
{"numFailedTestSuites":0,"numFailedTests":0,"numPassedTestSuites":1,"numPassedTests":1,"numPendingTestSuites":0,"numPendingTests":0,"numRuntimeErrorTestSuites":0,"numTotalTestSuites":1,"numTotalTests":1,"openHandles":[],"snapshot":{"added":0,"didUpdate":false,"failure":false,"filesAdded":0,"filesRemoved":0,"filesUnmatched":0,"filesUpdated":0,"matched":0,"total":0,"unchecked":0,"uncheckedKeysByFile":[],"unmatched":0,"updated":0},"startTime":1613934060410,"success":true,"testResults":[{"assertionResults":[{"ancestorTitles":[],"failureMessages":[],"fullName":"renders without crashing","location":null,"status":"passed","title":"renders without crashing"}],"endTime":1613934061340,"message":"","name":"/Users/example/tests/dir✨  Done in 1.80s.

Expected behavior
Output returns only JSON (as yarn jest --watchAll=false --json --outputFile=test-result.json)
{"numFailedTestSuites":0,"numFailedTests":0,"numPassedTestSuites":1,"numPassedTests":1,"numPendingTestSuites":0,"numPendingTests":0,"numRuntimeErrorTestSuites":0,"numTotalTestSuites":1,"numTotalTests":1,"openHandles":[],"snapshot":{"added":0,"didUpdate":false,"failure":false,"filesAdded":0,"filesRemoved":0,"filesUnmatched":0,"filesUpdated":0,"matched":0,"total":0,"unchecked":0,"uncheckedKeysByFile":[],"unmatched":0,"updated":0},"startTime":1613934048587,"success":true,"testResults":[{"assertionResults":[{"ancestorTitles":[],"failureMessages":[],"fullName":"renders without crashing","location":null,"status":"passed","title":"renders without crashing"}],"endTime":1613934049538,"message":"","name":"/Users/example/tests/dir/tets.js","startTime":1613934049261,"status":"passed","summary":""}],"wasInterrupted":false}

https://jestjs.io/docs/en/25.x/cli#--json

if you don't want to see stderr you can redirect it to /dev/null and it will only print the stdout
yarn jest --watchAll=false --json  2>/dev/null

Thank you @lidlanca, I didn't know about that workaround. But it seems to me a bit hacky and I would rather expect the output to be JSON. Especially the test messages are included in the resulted object.

Oh, there should be a --outputFile=* something, to describe this special working.


[EventRequest] Table 5741 - OnBeforeCheckTransHeader

Can you add event OnBeforeCheckTransHeader to table 5741 "Transfer Line"?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Make confusion matrix

Add code to the notebook to display the confusion matrix
(if possible) trace our recorded audios to check their performance

Code needs tidying up (mainly where the imports are done), but it works! LGTM.


Week 3: Continuous Integration Using GitHub Actions

Topics: Configure GitHub Actions that use the Ansible playbooks you’ve prepared
Tasks:

Understand GitHub Actions and set up basic CI workflows:

Research and read-up on GitHub Actions, YAML workflows, and how they can be used for CI/CD.
Create a simple GitHub Action that runs on a push event to test Terraform code (e.g., run terraform validate).
Set up a pipeline that validates Terraform configurations and runs a plan.
Document the setup and structure of the GitHub Actions workflow.

Automate Terraform deployments using GitHub Actions:

Set up a GitHub Actions workflow that not only validates and plans but also automatically applies the configuration on merges to a specific branch.
Use GitHub secrets for securely storing OpenStack API credentials or environment variables and integrate them into the workflow.
Test the full pipeline (validate, plan, apply) for automated OpenStack instance creation.
Configure the GitHub Actions workflow to send notifications on failures (e.g., through email or Slack).

Complete testing and full documentation of the project:

Run multiple CI pipelines and observe behavior under heavy loads or stress (e.g., simulate multiple concurrent deployments).
Handle common issues and errors in the pipeline (e.g., invalid Terraform configurations or failed API requests).
Automate the tear down, destruction and cleanup of resources as part of the GitHub Actions workflow to ensure resources are not left running unnecessarily.
Complete full documentation for both Terraform scripts and GitHub Actions, covering how they are set up, how the pipeline works, and any troubleshooting steps.

Hi Team,
@thinacalana1 @mthiadonis @NomAsh2247 @DCSpear @TebogoDira
If you are done with these tasks, let us know so that this issue can be closed.


Topology is not showing over UI in laster version of orchestrator 2.1.5

Hi ,
Upgraded latest version of orchestrator orchestrator-2.1.5-1.x86_64 but topology is not showing over UI .Nothing getting any error in the orchestrator log .
Could you please suggest me to resolve this issue .
Web page log : Uncaught ReferenceError: isCompactDisplay is not defined
at Object.success (cluster.js:1555)
at j (jquery.min.js:2)
at Object.fireWith [as resolveWith] (jquery.min.js:2)
at x (jquery.min.js:5)
at XMLHttpRequest.b (jquery.min.js:5)
(anonymous) @ cluster.js:1555
j @ jquery.min.js:2
fireWith @ jquery.min.js:2
x @ jquery.min.js:5
b @ jquery.min.js:5
XMLHttpRequest.send (async)
send @ jquery.min.js:5
ajax @ jquery.min.js:5
m.(anonymous function) @ jquery.min.js:5
getData @ cluster.js:1679
domReady @ cluster.js:1545
j @ jquery.min.js:2
fireWith @ jquery.min.js:2
ready @ jquery.min.js:2
J @ jquery.min.js:2
cluster.js:1494 Uncaught ReferenceError: isCompactDisplay is not defined
at renderCluster (cluster.js:1494)
at Object.success (cluster.js:1541)
at j (jquery.min.js:2)
at Object.fireWith [as resolveWith] (jquery.min.js:2)
at x (jquery.min.js:5)
at XMLHttpRequest.b (jquery.min.js:5)

Thank you!

The function isCompactDisplay() moved from cluster.js to orchestrator.js as per https://github.com/github/orchestrator/commit/60621513
I'd suggest refreshing your browser cache ; Shift+refresh or Cmd+refresh should do the trick.

Closing as no response given and as I believe this is a non-bug.


Field with _id suffix returns nil when a similar is filled

Description
When an enum attribute is populated, other similar attribute with suffix _id returns nil.
Reproduction Steps
create_table "invoices", force: :cascade do |t|
  t.string "partner_id", null: false
  t.integer "partner", null: false
end

FactoryBot.define do
  factory :invoice do
    partner_id { 'partner_id' }
  end
end

When partner is given, it returns nil:
build(:invoice, partner: :danca).partner_id
=> nil

When partner is not given or it is into factory as default, returns normally:
build(:invoice).partner_id
=> "partner_id"

Declaring both returns nil too:
build(:invoice, partner: :danca, partner_id: 'partner_id').partner_id
=> nil

Just the prefixed works:
build(:invoice, partner_id: 'partner_id').partner_id
=> "partner_id"

System configuration
factory_bot version:  6.0.2
rails version:  <IP_ADDRESS>
ruby version: 2.6.6p146 (2020-03-31 revision 67876) [x86_64-darwin19]

Thanks for the issue. This is a duplicate of https://github.com/thoughtbot/factory_bot/issues/1142, so I am going to close this issue and continue tracking it over there.


[Bug] "Statement" key doesn't work on remote link

Before Reporting

[X] I found no existing issues matching my bug
[X] My issue is not caused by a theme

Describe the Bug
The "Statement" key in "Patches" object doesn't work on remote link. The remote link itself accept a direct CSS inject, but when using "Statement", it doesn't work.
Expected Behavior
The "Statement" key should allows choices to a remote link.
Steps To Reproduce

In Skin.json, create a configuration to allow "true" and "false"
Create a regex that refer to a remote link (example: "https://steamcommunity.com/id*")
Insert a statement to allows user to choose multiple style (for example, "red" if the configuration is "true")
When starting steam, the statement doesn't inject the CSS based on the user's choice in the configuration.

Operating System
Windows
Anything else?
No response

same here


feat: ui notification component

fixes #220

Pull Request Test Coverage Report for Build 975

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 77.171%

Totals

Change from base Build 968:
0.0%

Covered Lines:
503

Relevant Lines:
632

💛  - Coveralls


CRUD of tasks

#39 #41
edit and delete function of #35
After the task is manipulated, the page needs to be refreshed manually

After added a task, I found that the page will not change, new task will not show in the page. I test in project page and inbox page. I need to refresh the page then the new task will be displayed.
I tested updateTask, similar problem. This time, after I editing the content or title, the content where I choose to change is changed. But if I change to other page, the content is not changed. Like I edit a task in today page, which also shown in inbox page. After I make change in the today page and click to the inbox page, the content is not changed. If I back to today page, the content still the old one. Only when I refresh the page, the content will change.

After added a task, I found that the page will not change, new task will not show in the page. I test in project page and inbox page. I need to refresh the page then the new task will be displayed.
I tested updateTask, similar problem. This time, after I editing the content or title, the content where I choose to change is changed. But if I change to other page, the content is not changed. Like I edit a task in today page, which also shown in inbox page. After I make change in the today page and click to the inbox page, the content is not changed. If I back to today page, the content still the old one. Only when I refresh the page, the content will change.

Yes, the auto page refresh is not in my plan at the moment, so I mentioned the page needs to be refreshed manually. We need to find an appropriate way to reload the route. For now, the shown task data only loads once when the page.js in the server is loaded, and all the pages in the application are based on this data. That's the reason for your second problem. If we reload the route each time when the data is updated, it will cause a 0.5 to 1-second delay, which will make a bad user experience.


WIP Invalid deref

Currently TypeErrors are thrown from property access of undefined for invalidated deref path get and set. For get we should return a criticalError, but I'm not sure what we should do for set.

@lrowe fwiw I have updated set impls in my secret-ish experimental branch that are more closely aligned with the throw-ing behavior of get.

@lrowe is this still relevant? Is there an issue referencing this? Looks like it might be stale with recent changes.

We should run the tests added in this branch on current master to see if this is still an issue.

@lrowe just tested. the tests don't succeed on latest master

Closing in favor of #940


Don't wrap global phase if parameterized

Summary
Dynamical decoupling cannot currently be applied on a circuits where global phases contain unbound parameters, due to the  _mod_2pi wrapping.
This PR replaces the _mod_2pi method with the global phase setter in DAGCircuit, wrapping the phase to the [0, 2π) interval (for floats).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 51.13%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
3304

Relevant Lines:
6462

💛  - Coveralls

Yes, indeed, I believe qiskit dynamical_decoupling would have the same problem, I can open an issue there too


INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS doesn't filter logs

Steps to reproduce:

start influxdb by docker image 1.7.7 with ENVs:

INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS_0: "4xx"
INFLUXDB_HTTP_ACCESS_LOG_STATUS_FILTERS_1: "5xx"

send there any data
logs contains rappahw [httpd] <IP_ADDRESS> - mydb [09/Oct/2019:08:07:57 +0000] "POST /write?db=mydb&p=%5BREDACTED%5D&precision=n&rp=&u=test HTTP/1.1" 204 0 "-" "-" e792484f-eb6b-11e9-820b-03420aff0011 2260

Expected behavior:
Logs should contains request with responses 4xx or 5xx.
Actual behavior:
Logs contains all https logs.
Environment info:

System info: Influx is running in docker, Host OS: Linux 4.19.0-5-amd64 x86_64
InfluxDB version: InfluxDB v1.7.7 (git: 1.7 f8fdf652f348fc9980997fe1c972e2b79ddd13b0)
Other relevant environment details: Docker 19.03.1

@sinacek Were you able to find the issue here ? Facing the same issue.

@himanshutyagi36 unfortunately not

is this an issue with toml/environment parser?


Add key normalizers

This change adds support for normalizing a key before it it submitted to a backend

It seems to me like it makes more sense to put this in the validator, and just fail lines with repeated dots. this is also faster, because you can implement it by using strstr(3), so it's just like something like:
if (strstr(stats_key, "..") != NULL) {
    goto fail;
}

I'm a little bit worried that if we add hacks like this then it encourages people to have buggy client code. Otherwise, you can still implement this whole thing simply and more efficiently again by using strstr(3) to find repeated dot sequences, and then only doing the replacement if there are any dots. This will be a lot faster because it avoids copying the string in the most common case (when there are no repetitions).


NETOBSERV-1471 gRPC export for packet capture

Description
Add gRPC export capability for packet capture.
Since I moved flow grpc to flowgrpc package, we will need to update FLP at the same time
I also took the opportunity to reuse the target host / port from flow config since it doesn't make sense to have both here.
Dependencies
n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[X] Will this change affect NetObserv / Network Observability operator? If not, you can ignore the rest of this checklist.
[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[X] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/retest

Rebased + removed tcp packet capture
https://github.com/netobserv/netobserv-ebpf-agent/pull/291/commits/6e65e79a0050842f22a82466d71bba97e02550ed

I am good with the changes few nit left other than that LGTM

/lgtm

pls remember to update the operator
https://github.com/netobserv/network-observability-operator/blob/1cd8e7670e47ee248965c72e5fc9bc8709fd615f/controllers/ebpf/agent_controller.go#L35

/approve

pls remember to update the operator https://github.com/netobserv/network-observability-operator/blob/1cd8e7670e47ee248965c72e5fc9bc8709fd615f/controllers/ebpf/agent_controller.go#L35

Here is the PR:
https://github.com/netobserv/network-observability-operator/pull/600


provider cluster: kubernetes CRDs

Update the CRD types so that they're compatible with our new type design.
re-generate the CRD clients.

Using a checkout of k8s.io/code-generator:v0.18.2, I've been able to generate all the akash clientset and integration packages. akash and akashd build fine, so now we primarily need to sort out our k8s dependency woes. There are some vscode flagged error messages which I'm a little confused by, but they might be vscode being confused.
I still need to go back and update the CRD types, but now I have a path see results of a build.

I think this can be considered done?


minimum max time value

add calculation of minimum max time value so user can plot BBMM...

[x] integrate the R code Bob wrote
[x] display helpful error message to user (replaced by next item)
[x] automatically change the max time value to the minimum value per animal

oops, ignore this issue; see #148 instead (:


Why does the fcn decoder not use any nonlinear activations?

I'm looking at decoder/fcn.py and trying to understand why no non linear activations (such as ReLu) are added. I expected to see them at each convolution and transposed convolution- but neither the upscore layers nor the the score layers have them. I figure this is very much intentional- I'd just like to understand why the decoder doesn't require the added nonlinearities.
Thanks!

Marvin's response to a similar question:

tf.image.resize_bilinear() is not trainable. In the original version of the FCN paper they used to train the deconvolution layer. They have stopped this, because it does not make a big difference. I have also experimented with tf.image.resize_bilinear(). If you set "trainable=False" (for the deconvolution weights) tf.image.resize_bilinear() yields the exact same result as my deconvolution layer. The speed is also exactly the same.

From the FCN original caffe implementation FAQ:

In our original experiments the interpolation layers were initialized to bilinear kernels and then learned. In follow-up experiments, and this reference implementation, the bilinear kernels are fixed. There is no significant difference in accuracy in our experiments, and fixing these parameters gives a slight speed-up. Note that in our networks there is only one interpolation kernel per output class, and results may differ for higher-dimensional and non-linear interpolation, for which learning may help further.

So, not only are non linear activations likely not necessary in this case, but the upsampling weights can be fixed.


Tooltip Popup is in the way of clicking on event links in List View

Describe the bug
After posting an event and you hover your mouse over a list view item you cannot click on the event to go to the full description
To Reproduce
Steps to reproduce the behavior:

Create a calendar in List View
Hover over the event
Popup gets in the way of clicking on the event to see full details page

Expected behavior
Hover over event and see a popup with a link that gets you to the full description
Additional context
When posting an event with "Custom Page" the event in list view reveals a magnify glass.  When you hover this you see the event description/summary.  Click on the event link and it goes to the custom page however you have to be fast enough to beat the popup or you cannot select it.

If you click on the magnify glass right now you go to the site event page instead of custom page url.

[ ] Review standard templates to get better initial display

@thabaum: Can you provide a screenshot or elaborate what is wrong?
This is what I get in list view:

Kind of funny I can put one up but not with generic content so I wont.
What happening is my older events (reuccuring) are using the old template I suppose, but if I put a new event in it works as you have pictured.
Good enough for me for now I suppose but my recurring events have that issue still I believe.

here are a couple other things I noticed... didnt realize I could just drop screenshots here into github this will help I was looking for how to do this but now see the note below (when I was looking on top for a way)

Also test NOTES is waht gets displayed it is very confusing.
Notes are notes, a summary is a summary so where do you put a full description?
Need to take out some guess work make this easier to work with for a user.   It has always annoyed me.  I may have better luck trying to work on this module with you for a while instead of trying to figure out the DNN Register using Email as Username issue I have been beating myself up on :)

OK now after adding/editing a new event the recurring events popup now shows under the link.
I guess I just needed to add a new event to make the changes take.


shortcodes and scripts not evaluated in .Summary

This is somewhat similar to another issue, but I think it is different enough to get its own issue.
{{ .Summary }} currently does not evaluate scripts from shortcodes.
Example:
I'm using the hugo-cloak-email theme/shortcode to cloak email addresses on my website. I'm using it on several pages, including some posts.
On my start page, I'm listing new posts with their summaries. Unfortunately, instead of evaluating the cloak-email shortcode script, it displays it in the summary:
Part of the summary and then in the middle of the sentence, a wild .cloaked-e-mail:before { content:attr(data-domain) "\0040" attr(data-user); unicode-bidi:bidi-override; direction:rtl; } var scriptTag = document.getElementById("e159018c021ece52c188cd9c35f6bd45"); var link = document.createElement("a"); var address = "nielgnetsh".split('').reverse().join('') + "@" + "ed.tsi-sf".split('').reverse().join(''); link.href = "mailto" + ":" + address; link.innerText = address; scriptTag.parentElement.insertBefore(link, scriptTag.previousElementSibling); scriptTag.parentElement.removeChild(scriptTag.previousElementSibling) appears! This is really ugly :(

Thanks, but we don't need more than one issue to track this.
#3235


Major Update for iteration 5

Pull Request Description
Title:  Pull Request: Backend and Frontend Updates for Email Verification, Admin Functionalities, Enhanced User Features, and Revised Unittest.
Summary
This PR introduces significant updates to both the backend and frontend, including the implementation of email verification, admin functionalities, and improved user interaction features. It also enhances the user experience with updates to event and account-related pages.
Changes Made:
Backend Changes

Email Verification and Notifications:

Implemented email verification functionality to ensure account authenticity.

Added email notifications for important updates, such as event status changes and account approvals.

Admin Functionalities.

Bookmark and like features.

Revised Unittest.

Enabled admin verification for organizers to ensure trustworthy event creation.

Added capabilities for administrators to:

Manage events (approve/reject, update statuses, etc.).

Oversee and manage organizer accounts.

Frontend Changes
Event Detail Page:

Built a comprehensive event detail view, showcasing:

Event descriptions, images, and organizer details.

Tags, categories, and other relevant information.

Like and Bookmark Features:

Integrated user-interaction features:

Users can like events to show interest.

Added the ability to bookmark events for future reference.

Account Info Page Revamp:

Redesigned the Account Info page for a smoother user experience.

Included clear visuals and better organization of user details.

Organizer Info Section:

Updated the Organizer Info section to include:
Detailed information about the organizer.
A dedicated area for showcasing organizer credentials and history.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 82.85714% with 72 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

backend/api/views/user.py
57.14%
30 Missing :warning:

backend/api/views/event.py
71.59%
23 Missing and 2 partials :warning:

backend/api/views/bookmarks.py
73.33%
7 Missing and 1 partial :warning:

backend/api/models/event.py
88.00%
2 Missing and 4 partials :warning:

backend/api/models/user.py
87.50%
1 Missing and 1 partial :warning:

backend/api/models/bookmarks.py
90.90%
1 Missing :warning:

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

Files with missing lines
Coverage Δ

backend/api/models/comment.py
100.00% <100.00%> (ø)

backend/api/models/like.py
100.00% <100.00%> (ø)

backend/api/models/organizer.py
100.00% <ø> (ø)

backend/api/models/ticket.py
100.00% <100.00%> (ø)

backend/api/views/comment.py
100.00% <100.00%> (ø)

backend/api/views/like.py
100.00% <100.00%> (ø)

backend/api/views/organizer.py
99.00% <100.00%> (-1.00%)
:arrow_down:

backend/api/views/ticket.py
100.00% <100.00%> (ø)

backend/api/models/bookmarks.py
90.90% <90.90%> (ø)

backend/api/models/user.py
82.81% <87.50%> (ø)

... and 4 more


ImportError: DLL load failed: The specified module could not be found.

trying to run this keep getting error any ideas?
from chatterbot import ChatBot
from chatterbot.trainers import ChatterBotCorpusTrainer
import os
from os import system, name
from time import sleep
def clear():
if name == 'nt':
_ = system('cls')
else:
_ = system('clear')
print('Loading...\n'*1)
sleep(1)
clear()
def setup():
bot= ChatBot('Bot')
wait = clear()
trainer = ChatterBotCorpusTrainer(bot)
corpus_path = 'D:/#1/test/'

for file in os.listdir(corpus_path):
    trainer.train(corpus_path + file)
name = input("Pls enter your name to begin:")
print('Welcome', name,'ask me anything you like!')

while True:
    message = input(name + ":")
    #print(message)
    if message.strip() == 'Bye':
        print('ChatBot: Bye')
        break
    else:
        reply = bot.get_response(message)
        print('ChatBot:', reply)

setup()
ERROR:
Traceback (most recent call last):
File "D:#1\scraping websites\chatbot_train.py", line 1, in
from chatterbot import ChatBot #import the chatbot
File "C:\Users\zurac\AppData\Local\Programs\Python\Python37\lib\site-packages\chatterbot_init_.py", line 4, in
from .chatterbot import ChatBot
File "C:\Users\zurac\AppData\Local\Programs\Python\Python37\lib\site-packages\chatterbot\chatterbot.py", line 2, in
from chatterbot.storage import StorageAdapter
File "C:\Users\zurac\AppData\Local\Programs\Python\Python37\lib\site-packages\chatterbot\storage_init_.py", line 1, in
from chatterbot.storage.storage_adapter import StorageAdapter
File "C:\Users\zurac\AppData\Local\Programs\Python\Python37\lib\site-packages\chatterbot\storage\storage_adapter.py", line 3, in
from chatterbot.tagging import PosHypernymTagger
File "C:\Users\zurac\AppData\Local\Programs\Python\Python37\lib\site-packages\chatterbot\tagging.py", line 8, in
import spacy
File "C:\Users\zurac\AppData\Local\Programs\Python\Python37\lib\site-packages\spacy_init_.py", line 12, in
from .cli.info import info as cli_info
File "C:\Users\zurac\AppData\Local\Programs\Python\Python37\lib\site-packages\spacy\cli_init_.py", line 6, in
from .train import train  # noqa: F401
File "C:\Users\zurac\AppData\Local\Programs\Python\Python37\lib\site-packages\spacy\cli\train.py", line 18, in
from ..gold import GoldCorpus
File "strings.pxd", line 23, in init spacy.gold
ImportError: DLL load failed: The specified module could not be found.
Process returned 1 (0x1)        execution time : 1.600 s

hi dear how you have solved this problem?

@zurachf help me please

Didn't solve it, Tried it with Ubuntu instead and it worked 🤔

@zurachf  i was facing same problem but solved just uninstall anaconda and remove directory from c and installed again problem solved

@HassanSheraz could you give more details on how you solved this problem?


Feature: import/include/require code?

Did you plan on including some mechanism to import/include/require code in Wren? Or is all code outside of core/iosupposed to be provided by the host application?

Yes and yes.
I need some sort of import mechanism, but the host application will have control over how the contents of the imported "module" thing are physically located.
I've put a little thought into this but I want to wait until there's a bit more Wren code in the wild (or at least that I've written) so I can get a better sense of how it feels to use with a real program.

Personally, I'd like to see an explicit "these are the objects that are exported" declaration rather than have everything public by default. My opinion, of course!

how about a 'module exports' array, a la node's module.exports object?

I've always thought Lua handled this pretty well.  In Lua whatever you return is exported, so you can simply return a table and that will be equivalent to module.exports.  This removes the need for a 'magic' object.

:+1: for that idea

Wren doesn't have tables, so the natural thing to return would be an object, but, yes, I've been thinking about something similar to what Lua does. A couple of tricky parts are figuring out how best to handle shared imports (you import a and b which both import c) and potentially cyclic imports.
I've been doing a lot of thinking here and have some rough notes. I'll try to put something together relatively soon with my idea(s). I definitely want to keep it simple, but I'm hoping to do something a little better than treating an import like a textual file include and dumping everything into a single global state.

In Node.js and Lua, shared imports are not a problem because imports do not affect the global (or even local) environment directly.  Instead, all imports have to be stored in a variable that acts as a sort of namespace for the exports.
Using this strategy allows you to sidestep a lot of problems with imports.

Yeah, I'm leaning towards that too. That solves some of the scoping problems, but not all of them. I need to spend some time gathering and writing down my thoughts here. It's not quite as easy in Wren as it might be in some other languages because of Wren's own constraints. In particular:

I want to keep it with a single-pass compiler.
But I want to report undefined variable errors at compile time.
And I'd like to support cyclic imports.

The last point may seem contentious, but statically typed languages generally don't have any problems with cyclic references between modules. That's important because it's entirely common for two modules to each have type annotations that refer to names defined in the other module.
Wren, of course, is dynamically typed, but I'm interested in having a separate static analysis tool for it to catch type errors. In that case, it would be nice if we had a good syntax for type annotations and if those names could be resolved correctly.
That means I'd like to not rule out cyclic imports if possible. But supporting them while keeping the module system very simple is pretty hard.

I wrote up a strawman. I'm not sure the best way to discuss proposals like this so, for kicks, I thought I'd try doing it in the issue tracker. I didn't want to post it here since it's super long (and there may be other separate module proposals so solve this bug), so it's here: #79.
Comment away!

WEP-0: Wren Enhancement Proposal :)
Could start at 0, community likes that better than 1?

I think we'll have to wait for a slightly more official proposal process before we start numbering them. :)

@peterlada Isn't the philosophy, "when in doubt, do what lua does?" So they should start at 1 :)

I'm not in doubt that starting at zero is the right answer! :D

Should imports only be allowed top level or allowed inside classes and methods?

Modules have landed in master!

Horray! :party:

:+1:

@zeckalpha, import statements are allowed anywhere a variable can be declared, including inside methods and functions.


boards: xtensa: odroig_go: use gpio-hog to turn LED off

Instead of using custom board init code.

You are fast guys.
I just tested it on my odroid-go device and works as it should.


[Feature] Copy generated release notes into CHANGELOG.md

First of all, thanks for the feature, it's really appreciated.
Do you think it would be useful to be able to modify the CHANGELOG.MD file in addition to generating the release notes? The modification would simply be an addition to the file of what has been generated. Then it could replace the Full Changelog field in the Release Note.
Maybe it's already feasible and if so I apologize.
Best,

I was looking for this feature today, this would still be useful 👍


feat(pagination): added pagination urls to sitemap

Needed to index all pages created by pagination and this is how I did it. Could maybe be useful for someone else.

Hi @rq-abrahamsson and thanks!
Can you show an example of how this should be used?

Hi @nunof07!
I'm not super experienced with Eleventy and have not written any plugin for it before so I hope my explanation will make sense.
But the use case I had was that I get data for a list of football pitches and I want to create one page for each with the same template so I did that with pagination and set size to 1. With the example data below this will create two pages and I want to index them both. So when using this plugin for generating a sitemap only the url for one of the generated pages was added which was not how I was expecting it to work. But maybe the current behavior is how it's expected to work for some?
pitches.html:
---
pagination:
  data: pitches
  size: 1
  alias: pitch
permalink: '{{ pitch.url }}'
layout: templates/layouts/base.liquid
---

{{ pitch.name }}

pitches.json
[
  {
    "name": "Name of first pitch",
    "url": "/name-of-first-pitch/",
    ...
  },
  {
    "name": "Name of second pitch",
    "url": "/name-of-second-pitch/",
    ...
  }
]

Thanks for the explanation. Hadn't tried this use case yet. Makes sense that the sitemap should include all paginated items.
I will setup an example with pagination and run some tests to make sure everything is covered.
Thanks again, appreciate it!

Hi @rq-abrahamsson ,
I've made a few changes to your PR. Added a pagination example and refactored the functions a bit.
Now calls the flatMap before the ignore check, so paginated items can also be ignored and spreads the full paginated page  object and not just the url property, so we can pass down other properties.
Thanks again and let me know if you find any issue with it!

I use pagination to generate a tag page for each occurrence of a tag on my site. After updating to v2.1.0 which includes this, the sitemap is adding a <url> entry for each tag, each time a new tag is found. For example, I have 13 tags right now, so there are 13 duplicate <url> entries for each tag. I'm not entirely sure what's going on here, but we might want to filter out duplicates if the URLs are identical? This could be because I set addAllPagesToCollections to true in the pagination configuration as well, so the tags were already being pulled in v2.0.6.
Poking around even more, v2.1.0 adds multiple entires for all of my /posts/ paginated pages, but doesn't include the page number, which results in duplicate entries as well. In v2.0.6 there was only one /posts/ entry, which seems to be what this PR was intending on fixing. Any thoughts with this? I'd be happy to poke at it some more, but this broke two different pagination configs on my site, so I thought I'd at least call it out 🙂

Hi @BrianMitchL , thank you for reporting this.
Regarding the tags, it seems that it is due to addAllPagesToCollections like you said. Wondering if that would have been the best solution from the start to include paginated items in the sitemap instead of introducing a change 🤔, but now it's probably better to ignore duplicates.
For the posts I have to check why the page numbers are not being included.
I'll look into it this week. Sorry for the troubles 😅.

No worries! Let me know if you want me to test anything out (commenting here, or tagging me in a new PR or something), or try to help with a fix.

@nunof07 v2.1.3 looks great!! 🚀 👏


How to minimize an quadratic objective function with constraint violation using penalty method

I want to minimize an indefinite quadratic function with both equality and inequality constraints that may get violated depending on various factors. So I want to use l1 penalty method that penalizes the violating constraints.

for example,
I have modified an example, to violate the constraints.
import osqp
import scipy.sparse as sparse
import numpy as np

# Define problem data
P = sparse.csc_matrix([[4., 1.], [1., 2.]])
q = np.array([1., 1.])
A = sparse.csc_matrix([[1., 0.], [0., 1.], [1., 0.], [0., 1.]])
l = np.array([0., 0., 0.2, 1.1])
u = np.array([1., 1., 0.2, 1.1])

# Create an OSQP object
prob = osqp.OSQP()

# Setup workspace and change alpha parameter
prob.setup(P, q, A, l, u, alpha=1.0)

# Solve problem
res = prob.solve()
print res.x

Obviously, this is an infeasible problem, so we need to change the objective function to penalize the error. So, I need help to formulate this problem that can be solved using osqp's python interface.

CVXPY 1.0 now supports QP parsing and is interfaced directly to OSQP. It can make your life much easier.
To define and solve your problem in CVXPY you can run the following script
import cvxpy
import scipy.sparse as sparse
import numpy as np

# Define problem data
P = sparse.csc_matrix([[4., 1.], [1., 2.]])
q = np.array([1., 1.])
A = sparse.csc_matrix([[1., 0.], [0., 1.], [1., 0.], [0., 1.]])
l = np.array([0., 0., 0.2, 1.1])
u = np.array([1., 1., 0.2, 1.1])
mu = 1  # Penalty parameter

# Define CVXPY problem
x = cvxpy.Variable(2)
# Standard objective
objective = cvxpy.quad_form(x, P) + q * x
# Penalty part of the objective
objective += mu * (cvxpy.norm1(A * x - u) + cvxpy.norm1(-A * x + l))
problem = cvxpy.Problem(cvxpy.Minimize(objective), [])
results = problem.solve(solver=cvxpy.OSQP, verbose=True)

For QP modeling questions, I suggest to use the OSQP forum.

Above method didn't work for my application as it is a non-convex problem,
`import cvxpy
import scipy.sparse as sparse
import numpy as np
import dccp
Define problem data
P = sparse.csc_matrix([[2., -4., 0.],
[0., 4., -4.],
[0., 0., 2.]])
q = np.array([1., 1., 0.])
A = sparse.csc_matrix([[-1., 1., 0.],
[0., -1., 1.],
[1., 0., 0.],
[0., 0., 1.],
[1., 0., 0.],
[0., 1., 0.],
[0., 0., 1.]])
l = np.array([-0.3, -0.3, 0.2, 0.7, -0.3, -0.3, -0.3])
u = np.array([0.3, 0.3, 0.2, 0.7, 1.1, 1.1, 1.1])
mu = 1  # Penalty parameter
mu = 15  # Penalty parameter
P =  .5 * (P + P.transpose())
Define CVXPY problem
x = cvxpy.Variable(P.shape[1])
Standard objective
objective = cvxpy.quad_form(x, P) + q * x
Penalty part of the objective
objective += mu * (cvxpy.norm1(A * x - u) + cvxpy.norm1(-A * x + l))
problem = cvxpy.Problem(cvxpy.Minimize(objective), [])
results = problem.solve(solver=cvxpy.OSQP, verbose=False)
print results
print x.value
`
I get the following error,
`/usr/bin/python2.7 /sqpproblem/probSlack2.py
Traceback (most recent call last):
File "/sqpproblem/probSlack2.py", line 54, in
results = problem.solve(solver=cvxpy.OSQP, verbose=False)
File "/usr/local/lib/python2.7/dist-packages/cvxpy-1.0.0-py2.7-linux-x86_64.egg/cvxpy/problems/problem.py", line 247, in solve
return solve_func(self, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/cvxpy-1.0.0-py2.7-linux-x86_64.egg/cvxpy/problems/problem.py", line 359, in _solve
raise e
cvxpy.error.DCPError: Problem does not follow DCP rules.
Process finished with exit code 1
`

The problem is non convex because your matrix P
P = sparse.csc_matrix([[2., -4., 0.],
                       [0., 4., -4.],
                       [0., 0., 2.]])

is not symmetric positive semidefinite. Are you sure your problem is nonconvex? Maybe it is just a modeling issue? I suggest you to have a look at the convex optimization book.
I close since it is not a solver issue.  The rest of the discussion is here.


[WIP] remove deprecated bat files of fsharp test suite

remove bat files of cambridge suite

[x] remove bat files
[x] fix build.cmd and runtests.cmd
[ ] check suite with coreclr works

ref #1074

+10000

@dsyme it's not +10000 - it's +1 −6,026 ;-)

Looks like some "Invalid" tests are being generated?
[00:23:16] 1) Invalid : FSharp-Tests-Core+NetCore+Netcore259.netcore259
[00:23:16] System.Exception : test directory 'C:\projects\visualfsharp-radou\tests\fsharp\core\netcore\netcore259' does not exists
[00:23:16]    at NUnitConf.FSharpTestSuite.setProps@194.Invoke(String message) in C:\projects\visualfsharp-radou\tests\fsharp\nunitConf.fs:line 194
[00:23:16]    at NUnitConf.FSharpTestSuite.setProps(String dir, IPropertyBag props) in C:\projects\visualfsharp-radou\tests\fshar
[00:23:16] p\nunitConf.fs:line 194
[00:23:16]    at NUnitConf.FSharpSuiteTestAttribute.NUnit-Framework-Interfaces-IApplyToTest-ApplyToTest(Test test) in C:\projects\visualfsharp-radou\tests\fsharp\nunitConf.fs:line 217
[00:23:16]
[00:23:16]
[00:23:16] 2) Invalid : FSharp-Tests-Core+NetCore+Netcore7.netcore7
[00:23:16] System.Exception : test directory 'C:\projects\visualfsharp-radou\tests\fsharp\core\netcore\netcore7' does not exists
[00:23:16]    at NUnitConf.FSharpTestSuite.setProps@194.Invoke(String message) in C:\projects\visualfsharp-radou\tests\fsharp\nunitConf.fs:line 194
[00:23:16]    at NUnitConf.FSharpTestSuite.setProps(String dir, IPropertyBag props) in C:\projects\visualfsharp-radou\tests\fshar
[00:23:16] p\nunitConf.fs:line 194
[00:23:16]    at NUnitConf.FSharpSuiteTestAttribute.NUnit-Framework-Interfaces-IApplyToTest-ApplyToTest(Test test) in C:\projects\visualfsharp-radou\tests\fsharp\nunitConf.fs:line 217
[00:23:16]
[00:23:16]
[00:23:16] 3) Invalid : FSharp-Tests-Core+NetCore+Netcore78.netcore78
[00:23:16] System.Exception : test directory 'C:\projects\visualfsharp-radou\tests\fsharp\core\netcore\netcore78' does not exists
[00:23:16]    at NUnitConf.FSharpTestSuite.setProps@194.Invoke(String message) in C:\projects\visualfsharp-radou\tests\fsharp\nunitConf.fs:line 194
[00:23:16]    at NUnitConf.FSharpTestSuite.setProps(String dir, IPropertyBag props) in C:\projects\visualfsharp-radou\tests\fshar
[00:23:16] p\nunitConf.fs:line 194
[00:23:16]    at NUnitConf.FSharpSuiteTestAttribute.NUnit-Framework-Interfaces-IApplyToTest-ApplyToTest(Test test) in C:\projects\visualfsharp-radou\tests\fsharp\nunitConf.fs:line 217

Closing because no change since May.

Closing a PR that has a comment "+10000" in it? Maybe better to find out why there's not been any activity on it. Is there a blocker on this? Does the OP need help to complete it?

@isaacabraham We will remove these files eventually.  I'm OK with closing this. Long-term open PRs have a significant mental burden for repo owners.

The deletion is easy enough, we don't need an open PR to track it.

The blocker is that we don't yet have a way to run the F# compiler for CoreCLR as part of our NUnit-based unit testing.

I spoke with Keven and there is also an issue that repro-ing test failures for the NUnit-based tests is really hard.  It makes it realy hard for active developers to move away from the batch files.

So I think we need to augment the testing process with output of step-by-step logs needed to repro the test failure independently.

I'll take a look at this as we most definitely need those batch files to go.

@isaacabraham it's me, i didnt update this pr, it's easy to continue work anyway.
I'll try to send a pr when ready and i have time to finish it (if someone doenst do that before me 😄 )

I spoke with Keven and there is also an issue that repro-ing test failures for the NUnit-based tests is really hard. It makes it realy hard for active developers to move away from the batch files.

the dotnet test can help in near future (.netcore/.net fw/mono ready).
Now is possibile to:

use visual studio test runner to reexecute only a single test
a single test can be executed from command line too, need documentation in dev guide


Higher-ranked lifetime error workaround

Workaround to a known issue of rustc: https://github.com/rust-lang/rust/issues/104382.
I encountered this issue when using this library with https://github.com/seanmonstar/warp. The error propagated from oci-distribution into my crate, outputting two hundred lines of error messages. Here is the horrible error messages from my project (https://github.com/linyinfeng/oranc/pull/24/commits/d9076872dbb26a39d167ddff88cd9e04df44a7d4, cargo.log).
After some bisect, debug, and search, I found that it is a known issue of rustc, and the workaround is simple.

Thanks for the fix!


AArch64: serde: Add serialize/deserialize support to AArch64 snapshot-related structs

To implement VM snapshot/restore, we need to serialize/deserialize some of the AArch64 structures. This PR adds the support and related unit tests for these structures.
Signed-off-by: Henry Wang<EMAIL_ADDRESS>

@MrXinWang looks good to me, but could you remove the first commit Merge pull request #1?

@sboeuf Done. Thanks!


Space not created

Space is not being created when it's specified without folder in profiles.yml. It appears as though create_schema is not called when folder isn't provided.
Current workaround is to ensure a folder is provided when trying to create a new space.

Duplicate closing.


⚠ Bofrost.es has degraded performance

In e82a821, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1246 ms

Resolved: Bofrost.es performance has improved in 6634a12 after 27 minutes.


feat: Support Buffalo Terastation NAS

:tada: This PR is included in version 2.0.0-next-major.14 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Import v11 builtin actors

Summary of changes
Changes introduced in this pull request:

Import v11 builtin actors
Added v11 actor cids for mainnet and calibnet

Reference issue to close (if applicable)

Closes
Other information and links

https://github.com/filecoin-project/lotus/blob/v1.22.0-rc4/build/builtin_actors_gen.go

Codecov Report
Patch coverage: 15.00% and project coverage change: -1.51 :warning:

Comparison is base (fdfea20) 13.45% compared to head (84f3026) 11.94%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #87      +/-   ##
==========================================
- Coverage   13.45%   11.94%   -1.51%
==========================================
  Files         201      328     +127
  Lines       20087    41506   +21419
==========================================
+ Hits         2703     4959    +2256
- Misses      17384    36547   +19163

Impacted Files
Coverage Δ

account_v11/src/state.rs
0.00% <0.00%> (ø)

account_v11/src/testing.rs
0.00% <0.00%> (ø)

account_v11/src/types.rs
0.00% <0.00%> (ø)

cron_v11/src/state.rs
0.00% <0.00%> (ø)

cron_v11/src/testing.rs
0.00% <0.00%> (ø)

datacap_v11/src/state.rs
0.00% <0.00%> (ø)

datacap_v11/src/testing.rs
0.00% <0.00%> (ø)

datacap_v11/src/types.rs
0.00% <0.00%> (ø)

eam_v11/src/ext.rs
0.00% <0.00%> (ø)

ethaccount_v11/src/types.rs
0.00% <0.00%> (ø)

... and 134 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

We don't need all 18k lines of code. Should be trimmed at some point in the future.


correct-wetday-frequency casts all output to float64

We had a fix to a bug in bad wetday correction in PR #174. The fix appears to work but it has the side effect of recasting input data to a different dtype on output.
For a concrete example, when we run this
dodola correct-wetday-frequency \
  "gs://scratch-170cd6ec/c4ddb434-70bd-45d0-923b-e87af09483cc/create-pr-references-dev-tgk5l-316395516/regridded.zarr" \
  --process "pre" \
  --out "gs://scratch-170cd6ec/20210126-wdf-corrected.zarr"

if the input zarr  has a "pr" variable that's float32, the output is float64.
This creates problems with the output data is later fed into numba or pre-compiled functions, it is also much larger in storage.
It would be great if we could get it to output to the same dtype as the input dataset.

found it :) https://github.com/ClimateImpactLab/dodola/pull/174#discussion_r793006110


How to limit fields returned from the JSON API?

Hi,
I have quite wide tables, and in many cases only want a subset of the data (to save on network bandwidth). I need to use the JSON API as handling pagination is so much easier, but I can't see a way to select specific columns.
Is there a way to do this, or is it a feature request?
Thanks!

Currently you can do this with a custom SQL query, but as you've noticed this means you don't get automatic pagination: https://latest.datasette.io/fixtures.json?sql=select+pk%2C+created%2C+state+from+facetable+order+by+pk+limit+10&_shape=array
I have an open issue to allow selecting specific columns on the table page: #615
A workaround you can use today is to define a SQL view that selects just the tables you want. View pages behave exactly like tables in that they provide pagination by default.


Secret detection

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"0303979da0247777beb48d72c80e4df30cba5dd3"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"0303979da0247777beb48d72c80e4df30cba5dd3"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"4b6092e2f26c8dc31d19c390347a6cfa06b3a93d"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"4b6092e2f26c8dc31d19c390347a6cfa06b3a93d"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (29.86%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"90df00abe70baaaf8f7ce2d472d417bc9d1b3481"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"90df00abe70baaaf8f7ce2d472d417bc9d1b3481"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"53c4cf9a84a225d44e31d07a0532e3392cc1d0be"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"53c4cf9a84a225d44e31d07a0532e3392cc1d0be"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"9693e5b90293bf488e53e4a7724a3b290de9d56f"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"9693e5b90293bf488e53e4a7724a3b290de9d56f"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"cf937bbfe5b86f491e1c31a186caa9cd4c03402d"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"cf937bbfe5b86f491e1c31a186caa9cd4c03402d"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"b86c8135f8adcb5aaef7a2d8f22afd61654bf7f4"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"b86c8135f8adcb5aaef7a2d8f22afd61654bf7f4"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (29.86%)

            :red_circle: Branch Coverage (9.78%)

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"af0db676a4be1428896ab0e0b90548c520fe193a"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"af0db676a4be1428896ab0e0b90548c520fe193a"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"1351d05e426e5f0ee4a5de28a9cdb09f6f28d2e6"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"1351d05e426e5f0ee4a5de28a9cdb09f6f28d2e6"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"4beb5586c0f64627cfd275e62eb6379a0145af0b"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"4beb5586c0f64627cfd275e62eb6379a0145af0b"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (29.86%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"334db7b3fd34c41ec1b465ea15a3216289af5a64"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"334db7b3fd34c41ec1b465ea15a3216289af5a64"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (29.86%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"40d6722022a8fae10f2119565d46d5e87b13cf12"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"40d6722022a8fae10f2119565d46d5e87b13cf12"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"0b9c36b3374e47a9ffadd0fe4d35502200298603"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"0b9c36b3374e47a9ffadd0fe4d35502200298603"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"9dafc38169fb13789f47224f76452b469c64538d"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"9dafc38169fb13789f47224f76452b469c64538d"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"e386984bf9105d43d636773ba60088c1ae95329f"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"e386984bf9105d43d636773ba60088c1ae95329f"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"665bd80a6e6e46cbbce55c888315d3ae8bae118a"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"665bd80a6e6e46cbbce55c888315d3ae8bae118a"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"77e3f0400347e5d20a605277105220f4bbd7a672"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"77e3f0400347e5d20a605277105220f4bbd7a672"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (29.86%)

            :red_circle: Branch Coverage (9.78%)

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Modified Files Coverage Summary

            :green_circle: Instructions Coverage (100%)

            :green_circle: Branch Coverage (100%)

File
Instructions Coverage (100%)
:green_circle:
Branch Coverage (100%)
:green_circle:

ExploitableSearchRepository.java
100%
:green_circle:
100%
:green_circle:

 Overall Coverage Summary

            :green_circle: Instructions Coverage (30.06%)

            :red_circle: Branch Coverage (9.78%)

 Following are detected SECRETS!! To be fixed !

{
"filename": "src/main/resources/application.properties",
"failure_list": [
{
"type": "filecontent",
"message": "Expected file to not to contain base64 encoded texts such as: spring.datasource.password=eyJhbGciOiJIUzI1NiIs...",
"commits": [],
"severity": "high"
},
{
"type": "filecontent",
"message": "Potential secret pattern : #spring.datasource.password="hwgeytfwqefjweqhfwef"",
"commits": [
"1d365299c8e6f82692b83b4676c2c83933020884"
],
"severity": "low"
},
{
"type": "filecontent",
"message": "Potential secret pattern : spring.datasource.password=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
"commits": [
"1d365299c8e6f82692b83b4676c2c83933020884"
],
"severity": "low"
}
],
"warning_list": [],
"ignore_list": []
}


Release 100.5 samples - Part 2

This is the second part of the 100.5 release. It includes the remaining samples for the latest version of the runtime.

@nixta Thank you for your feedback. Would you like any of the issues you mentioned addressed before the release or am I good to merge this PR?


Add Set.foldl/r simplifications

Including parts from #2
-- The following simplifications for Set.foldl also work for Set.foldr
Set.foldl f initial Set.empty
--> initial
Set.foldl (\_ soFar -> soFar) initial set
--> initial

The added helpers are generic enough to be used for Dict/Array/String/List.foldlr as well

No, it runs fine. I just forgot it :)

Wait, you don't run it on save? :scream:

I do run it on save on all other projects but in simplify I use the elm-land one which sometimes gets tripped up when formatting.

Aha, alright. Worth a bug report there probably :thinking:


Retries are not disabled when maxAttempts == 1

Fixes https://github.com/googleapis/gax-java/issues/711.

PTAL

PTAL again, changed the implementation again to what @igorbernstein2 and I had discussed


docker container ls does not show e-mail server port

Is this docker setup made so that it does not turn on the e-mail port?
this is my result when doing sudo docker container ls --format "table {{.ID}}\t{{.Names}}\t{{.Ports}}" -a:
CONTAINER ID   NAMES                    PORTS
619287aeacf1   aysvc_kitsu_processor
2a179bcc028f   ayon-docker-worker-1
1f164c15b178   cgwire-kitsu             <IP_ADDRESS>:8800->80/tcp, :::8800->80/tcp
490f7ea3e3cc   cgwire-zou-event
f3d68752f372   cgwire-zou-app
3666327c21c8   cgwire-meilisearch       <IP_ADDRESS>:7700->7700/tcp, :::7700->7700/tcp
35016994ee2f   cgwire-redis             6379/tcp
0fef65dafcc5   cgwire-zou-jobs
110e8b800c1b   cgwire-db-12             5432/tcp
25d3864dd72a   ayon-docker-server-1     <IP_ADDRESS>:5000->5000/tcp, :::5000->5000/tcp
aa106068f0a1   ayon-docker-redis-1      6379/tcp
a5e5116a2aec   ayon-docker-postgres-1   5432/tcp

Oh I see now, an email server is not included in this docker compose. Will close this issue.


I can't connect netopeer2-server

Hi,
I installed the yang-sysrepo-libnetconf2 requirements for netopeer2 from the devel branch on ubuntu 20.04. Libssh version I installed is 0.8.6 . I open the Netopeer2 server with the command " netopeer2-server -d -v3 " and I do not get an error in the opening part.
The error that I got :

[INF]: LN: Accepted a connection on <IP_ADDRESS>:830 from <IP_ADDRESS>:45992.
[INF]: SR: Session 114 (user "root", CID 30) created.
[INF]: LN: Received an SSH message "request-service" of subtype "ssh-userauth".
[INF]: LN: Received an SSH message "request-auth" of subtype "none".
[INF]: LN: Received an SSH message "request-auth" of subtype "password".
[INF]: LN: Failed user "alecanty" authentication attempt (#1).
[2023/05/23 19:34:03.937809, 1] ssh_packet_disconnect_callback:  Received SSH_MSG_DISCONNECT: 11:Bye Bye
[ERR]: LN: Communication SSH socket unexpectedly closed.

After the installation, I have not made any server and client-side settings. Where can I do the settings that need to be made before opening the server and where these settings are made? Where can I access the user and password settings that I will connect to?

Where can I do the settings that need to be made before opening the server and where these settings are made?

No manual configuration changes are needed after netopeer2 installation to make it work. But you can adjust them the same way you would any other YANG configuration, in sysrepo. You can use sysrepocfg, to see the configuration use sysrepocfg -X -m ietf-netconf-server.

Where can I access the user and password settings that I will connect to?

Currently, the users are read directly from the system and cannot be changed without changing the actual system users. We are working on updates that will allow configuring the users separately for NETCONF.