Error 404 when trying to edit the docs

Describe the bug
When I tried to click on the "edit" icon on the top right corner in https://ehrapy.readthedocs.io/en/latest/usage/usage.html (does not matter which method page), I got the 404 Page not found error. It apparently looks for the .rst files in ehrapy/docs/usage, but these do not exist.
To Reproduce
Steps to reproduce the behavior:

Go to https://ehrapy.readthedocs.io/en/latest/usage/usage.html
Click on the edit icon on a random method page
You'll get the 404 Error page

Expected behavior
I guess the user should be able to see the source code (the method itself and the example in the docs)

The source code of each function contains the docstring which is parsed by the doc setup when setting up the docs; so this is a dynamic process rather than a static one with parsing a single .rst file or similar. So by clicking the source link next to the method signature, it shows you everything (since docstring == doc basically). So maybe we should find a way to simply delete the edit button on a single function docs page at all?
Am I missing something @Zethson ?

It's an issue of using markdown instead of rst. This can be fixed.  Tuesday, 13 September 2022, 08:54PM +02:00 from Philipp Ehmele  @.*** :

The source code of each function contains the docstring which is parsed by the doc setup when setting up the docs; so this is a dynamic process rather than a static one with parsing a single .rst file or similar. So by clicking the source link next to the method signature, it shows you everything (since docstring == doc basically). So maybe we should find a way to simply delete the edit button on a single function docs page at all?
Am I missing something  @Zethson ?
—
Reply to this email directly,  view it on GitHub , or  unsubscribe .
You are receiving this because you were mentioned. Message ID:  @ github . com>

It's an issue of using markdown instead of rst.

What's the issue here?

We're not pushing the rst files and only the markdown files exist. So the link goes to nowhere.  Tuesday, 13 September 2022, 09:02PM +02:00 from Philipp Ehmele  @.*** :

It's an issue of using markdown instead of rst.
What's the issue here?
—
Reply to this email directly,  view it on GitHub , or  unsubscribe .
You are receiving this because you were mentioned. Message ID:  @ github . com>

Since we don't upload the generated rst files to the repository because we generate them on the fly by translating the markdown into the rst files that are actually rendered.
Think it would be tricky and messy to fix this. Hence, I removed the edit button for now.


Adding Border Width

In this issue, we have to add border width.
Unit of these widths will be in em.
a) Border-1
b) Border-2
c) Border-3
d) Border-4
e) Border-5
Add accordingly and in case of any queries, you can participate in the discussions.

hey, @atharvagadkari05 the value of em will be 1,2,3,4,5 according to that border classes?

okay, then I can get started to work on this issue. @yashsehgal

hey, @atharvagadkari05 the value of em will be 1,2,3,4,5 according to that border classes?

what do you mean by em unit, because 1, 2, 3, 4, 5 ems are too large values for a border?

hey, @atharvagadkari05 the value of em will be 1,2,3,4,5 according to that border classes?

what do you mean by em unit, because 1, 2, 3, 4, 5 ems are too large values for a border?

yup that's what i thought

hey, @atharvagadkari05 the value of em will be 1,2,3,4,5 according to that border classes?

what do you mean by em unit, because 1, 2, 3, 4, 5 ems are too large values for a border?

yup that's what i thought

Let's plan out the widths as well. Like, on using et-border-1 the border-width actually will be 0.2em, then et-border-2 will be 0.4em and so on. What do you think @ItsMeIshan @atharvagadkari05 @WH0SUMIT ??

@yashsehgal that's awesome we can do this!

one more thing

Try using the naming conventions as et-bw-VALUE_OF_WIDTH
where bw means border-width to keep the features easy to use.

one more thing

Try using the naming conventions as et-bw-VALUE_OF_WIDTH
where bw means border-width to keep the features easy to use.

it means we can go on like et-bw-1, et-bw-2 and so on @yashsehgal

one more thing

Try using the naming conventions as et-bw-VALUE_OF_WIDTH
where bw means border-width to keep the features easy to use.

it means we can go on like et-bw-1, et-bw-2 and so on @yashsehgal

right! @ItsMeIshan 👍🏽

I have assigned this issue to you, Go for it 🚀

cool getting started with it!

hey, @atharvagadkari05 the value of em will be 1,2,3,4,5 according to that border classes?

what do you mean by em unit, because 1, 2, 3, 4, 5 ems are too large values for a border?

yup that's what i thought

Let's plan out the widths as well. Like, on using et-border-1 the border-width actually will be 0.2em, then et-border-2 will be 0.4em and so on. What do you think @ItsMeIshan @atharvagadkari05 @WH0SUMIT ??

@yashsehgal Sorry, I forgot to mention the exact no. but I think this looks great.

@ItsMeIshan You can proceed with this and please remember the class naming convection specified by @yashsehgal.


Better handling of invalid rule configuration options

Continuing discussion in #4206: how should rules display that their configurations are invalid?
Right now, as @cheeZery suggested, they can use the showWarningOnce strategy and not run. Should there be a standard utility for this?
More grandly, what if there were a system to validate options once per rule on startup? Rules already have JSON schemas specified, can we use it to remove the burden of validity checking from each rule?

I did some trial by error for this validation feature. I found that the method to validate the options itself wouldn't be that hard to implement. For example jsonschema seems suited for the job
and the parseConfigFile method in src\configuration.ts might be a good place to implement that logic. Something like:
    function validateRulesOptions(
        rules: Map<string, Partial<IOptions>>,
        rulesDirectory?: string | string[],
    ): Map<string, Partial<IOptions>> {

        const validator = new Validator(); // import { Validator } from "jsonschema";
        rules.forEach((ruleOptions, ruleName) => {
            // TODO: Make sure ruleSeverity is not "off" and ruleArguments aren't undefined

            const Rule = findRule(ruleName, rulesDirectory);
            // TODO: Make sure Rule is defined and has metadata

            if (Rule.metadata.options === null) {
                if (ruleOptions.ruleArguments.length !== 0) {
                    // TODO: Print warning that given rule doesn't expect any options
                }
                return;
            }

            const validationResult = validator.validate(ruleOptions.ruleArguments, Rule.metadata.options);
            if (!validationResult.valid) {
                // TODO: Print warning that given options don't match rule's JSON schema, maybe also print validation errors
            }
        });
    }

The tricky part is how the JSON schema for the options is currently written and how the options are written in tslint.json. The rule array-type for example has on string option. The JSON schema is declared as:
        options: {
            type: "string",
            enum: [OPTION_ARRAY, OPTION_GENERIC, OPTION_ARRAY_SIMPLE],
        },

But since ruleArguments are always arrays, the option will be something like ["array-simple"], so the validation would fail. But we obviously also can't just parse the first item of the array to the validation, because there are rules, where more than one string can be provided, e.g. comment-type rule (there the option is declared as array of strings, so it works just fine).
Long story short: I guess either a lot of JSON schemata had to be fixed or the way options are declared (e.g. for more than on string [true, ["foo", "bar"]] instead of [true, "foo", "bar"].
Maybe the problem can be solved with the new way of declaring rule options with an option prop.

@cheeZery do you pretend to submit a PR with this?

@rafaelss95 actually no, I'm not :) since this issue still got the tags "In Discussion" and "Needs Approval".
In light of #4534 I'm also not sure the guys are willing to allow/implement such a change which has potential to break some stuff (e.g. if users and/or plugins misconfigured their rules).
Although it also might be easier to migrate to a new system when solid tests are in use.

💀 It's time! 💀
TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱
If you'd like to see this change implemented, you have two choices:

Recommended: Check if this is available in ESLint + typescript-eslint ✅
Not Recommended: Fork TSLint locally 🤷♂

👋 It was a pleasure open sourcing with you!
If you believe this message was posted here in error, please comment so we can re-open the issue!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


Incremental relabeling

Atm. AdaptiveObjects are relabeled whenever their inputs change.
Since this doesn't play well with nested "bind-like" operations we should finally solve that issue.
It can cause massive runtime overhead (i suspect it to be quadratic or worse) and it does occur when  synthesizing one value of a complex structure (e.g. BoundingBox of a scene)

Solved via lazy relabelling during evaluation


Support Deno 2.0

Issue
Setup:

Deno Version: 2.0.0 (stable, release, aarch64-apple-darwin)
v8 Version: <IP_ADDRESS>-rusty
Typescript Version: 5.6.2
SuperOak Version: 4.8.1

Details
Deno test started breaking after upgrading to Deno 2.0:
Test code:
Deno.test({
	name: 'init test',
	fn: async () => {
		const initReq = await superoak(app);
		const initRes = await initReq
			.post('/init')
			.set('Content-Type', 'application/json')
			.send(initPayloadDemo)
			.expect(Status.OK)

	sanitizeOps: false,
	sanitizeResources: false,
});

ERRORS
./src/tests/play.test.ts (uncaught error)
error: (in promise) ReferenceError: window is not defined
      (window as any)[SHAM_SYMBOL].promises,
      ^
    at completeXhrPromises (https://deno.land/x/superdeno@4.9.0/src/test.ts:192:7)
    at https://deno.land/x/superdeno@4.9.0/src/test.ts:558:21
    at close (https://deno.land/x/superdeno@4.9.0/src/close.ts:47:52)

This error was not caught from a test and caused the test runner to fail on the referenced module.
It most likely originated from a dangling promise, event/timeout handler or top-level code.

Superoak still works fine on Deno 1.46.3, the latest Deno 1.x version before 2.0.

This is a problem with superdeno module.
I am not quite familiar with the code that handles the xhr sham, but you can try this workaround to make your tests work with Deno v2 and superoak.
Before your tests, run this line:
(globalThis as any).window = globalThis;

Hi all 👋
As @petruki points out, it seems there has been a long lived bug in https://github.com/cmorten/superdeno/blob/main/src/test.ts#L192 which makes Deno v2 fall over (this line should read (globalThis as any)[SHAM_SYMBOL].promises!)
I could patch this line however both superdeno and superoak were only ever meant to be drop-in replacements for the supertest package in a world where NPM wasn't supported by Deno.
Deno is now very much claiming Node and NPM compatability so I would encourage as you do the major upgrades to consider migrating off of superdeno and superoak.
I might consider continuing to support superoak as a thin wrapper over supertest, but will most likely look to sunset superdeno now that it needn't exist afaik

Thank you both for responding so quickly. If you don't have anything to add, I can close this issue.


Add multiversion support for development dependencies

It was implemented for runtime dependencies only.

Looks good! Will merge and cut a release in the morning.

Thank you!

Thanks Mike for maintaining this gem!

v1.4.0 was just released with this fix in it.


Minimal reader

Client that retrieves chain head (== whole chain in the case of Getty, because only one cell will be used per canonical) given canonical id

This can either contain a builtin Datastore client (more consistent with eventual IPFS usage), or call to a remote hosted datastore shim (more lightweight)


Newsletter subscribe link in README.md

It would be good at some point to put the subscribe to newsletter link in this repo's README

Closing - Added link in README.


Support file/directory exclusion from jar and war files.

This PR adds an --exclude param to allow for multiple path exclusions. Currently it supports a relative path from the application's root, but could easily be changed to support regexp patterns.

Looks great - thanks!


fix #1648: support submit storm jar via rest interface

submit storm application through UI failed with the following error. The same example could be run successfully through command line.
[ERROR] [01/22/2016 14:30:21.968] [OneForOneStrategy] cannot assign instance of scala.collection.immutable.List$SerializationProxy to field io.gearpump.util.Graph.edgeList of type scala.collection.immutable.List in instance of io.gearpump.util.Graph
akka.actor.ActorInitializationException: exception during creation
        at akka.actor.ActorInitializationException$.apply(Actor.scala:166)
        at akka.actor.ActorCell.create(ActorCell.scala:596)
        at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:456)
        at akka.actor.ActorCell.systemInvoke(ActorCell.scala:478)
        at akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:263)
        at akka.dispatch.Mailbox.run(Mailbox.scala:219)
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)
        at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
        at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
        at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: java.lang.ClassCastException: cannot assign instance of scala.collection.immutable.List$SerializationProxy to field io.gearpump.util.Graph.edgeList of type scala.collection.immutable.List in instance of io.gearpump.util.Graph
        at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2127)
        at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1305)
        at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2003)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1921)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
        at akka.serialization.JavaSerializer$$anonfun$1.apply(Serializer.scala:136)
        at scala.util.DynamicVariable.withValue(DynamicVariable.scala:58)
        at akka.serialization.JavaSerializer.fromBinary(Serializer.scala:136)
        at akka.serialization.Serializer$class.fromBinary(Serializer.scala:60)
        at akka.serialization.JavaSerializer.fromBinary(Serializer.scala:120)
        at io.gearpump.cluster.UserConfig.getValue(UserConfig.scala:116)
        at io.gearpump.streaming.appmaster.AppMaster.io$gearpump$streaming$appmaster$AppMaster$$getUpdatedDAG(AppMaster.scala:310)
        at io.gearpump.streaming.appmaster.AppMaster$$anonfun$3.apply(AppMaster.scala:78)
        at io.gearpump.streaming.appmaster.AppMaster$$anonfun$3.apply(AppMaster.scala:77)
        at akka.actor.TypedCreatorFunctionConsumer.produce(Props.scala:343)
        at akka.actor.Props.newActor(Props.scala:252)
        at akka.actor.ActorCell.newActor(ActorCell.scala:552)
        at akka.actor.ActorCell.create(ActorCell.scala:578)
        ... 9 more

@stanleyxu2005
There is no need for services to depend on storm.
We can add storm classpath while launching the "StormRunner" process.

load StormRunner with the full class name instead of StormRunner.getClass
add the storm classpath System.getProperty("gearpump.home") + "/lib/storm/*"

Current coverage is 60.46%

Merging #1918 into master will decrease coverage by -2.20% as of 73dad72

@@            master   #1918   diff @@
======================================
  Files          174     174
  Stmts         5225    5249    +24
  Branches       578     578
  Methods
======================================
- Hit           3274    3174   -100
  Partial          0       0
- Missed        1951    2075   +124

Review entire Coverage Diff as of 73dad72

Uncovered Suggestions

+0.29% via ...cutor/Executor.scala#271...285
+0.25% via .../master/Master.scala#124...136
+0.21% via .../MasterService.scala#257...267
See 7 more...

Powered by Codecov. Updated on successful CI builds.

@stanleyxu2005 you can refer to generated output/target/pack/bin/storm for an example of launching StormRunner.

compile failed
[error] /home/travis/build/gearpump/gearpump/services/jvm/src/main/scala/io/gearpump/services/MasterService.scala:223: not enough arguments for method submitAndDeleteTempFiles: (mainClass: String, argsArray: Array[String], fileMap: Map[String,java.io.File], classPath: Array[String], systemConfig: com.typesafe.config.Config, userConfigFile: Option[java.io.File])Boolean.

[error] Unspecified value parameter systemConfig.

[error]     submitAndDeleteTempFiles(

[error]

+1


How to customize symbols?

Hello,
I'd like to render the map elements more flexibly by using symbol. I find that the AGSTextSymbol has lots of properties, but for other symbols like AGSLineSymbol I don't find the way to realize complex display. In fact, I really want to know how to customize symbols.

A neat way to achieve complex affects is by using AGSCompositeSymbol to combine a number of point, line and polygon symbols.  https://developers.arcgis.com/ios/latest/api-reference/interface_a_g_s_composite_symbol.html


Password confirmation

When a user changes their segue password on the my account page, they should be prompted to verify their current password before changes take effect.
This is to prevent a malicious user hijacking an account when a computer is left logged in and unattended.

This has been done, probably with the new account setting page when it was released.

This has sort of been done, actually. The old one isn't actually verified, which needs fixing.

Fixed here: https://github.com/ucam-cl-dtg/isaac-api/commit/0296a95c6532dff014672b47e744d256ef4763e2


chore(master): Release 0.46.7

:robot: I have created a release beep boop
aztec-package: 0.46.7
0.46.7 (2024-07-16)
Features

Devnet updates (#7421) (103f099)

Bug Fixes

Cli l1-chain-id option (#7490) (307bc57)

Miscellaneous

Turn on elaborator (#7451) (0599500)

barretenberg.js: 0.46.7
0.46.7 (2024-07-16)
Miscellaneous

barretenberg.js: Synchronize aztec-packages versions

aztec-packages: 0.46.7
0.46.7 (2024-07-16)
Features

Add unconstrained context to txe (#7448) (699fb79)
Add unconstrained getters to sharedmutable (#7429) (c0ff566)
Devnet updates (#7421) (103f099)
Point::fromXandSign(...) (#7455) (225c6f6)

Bug Fixes

avm: Update generated verifier (#7492) (f1216a7)
Cli l1-chain-id option (#7490) (307bc57)
Don't pass secrets to earthly-ci 'publish docs' command (#7481) (a3f6feb)
Fix msg_sender direct call exploit (#7404) (1dcae45)
Missing NoteSelector from JSON RPC proxies (#7493) (b209fad)
pxe: Best effort noir call stack generation (#7336) (0c7459b)
Validate gas used (#7459) (6dc7598)

Miscellaneous

avm: More stats and codegen cleanup (#7475) (1a6c7f2)
Checking compute_encrypted_note_log  against TS impl (#7491) (1e8a597)
Included subrelation witness degrees in the relations relevant to zk-sumcheck (#7479) (457a115)
Replace relative paths to noir-protocol-circuits (71960d4)
Turn on elaborator (#7451) (0599500)

barretenberg: 0.46.7
0.46.7 (2024-07-16)
Features

Point::fromXandSign(...) (#7455) (225c6f6)

Bug Fixes

avm: Update generated verifier (#7492) (f1216a7)

Miscellaneous

avm: More stats and codegen cleanup (#7475) (1a6c7f2)
Included subrelation witness degrees in the relations relevant to zk-sumcheck (#7479) (457a115)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/aztec-packages-v0.46.7 :sunflower:

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/aztec-package-v0.46.7 :sunflower:

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/barretenberg.js-v0.46.7 :sunflower:

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/barretenberg-v0.46.7 :sunflower:


about name of area attribute case sensitive

Is your feature request related to a problem? Please describe.
I am using asp.net core 3.1，create a Area called Admin，I created a homecontroller with the area attribute name set to admin，when i debug with windows，it's ok，but i publish to linux,it's bad。
I know that Linux is case sensitive，but i am browser access case insensitive.
Describe the solution you'd like
Whether area name should be case insensitive.

@hryh thanks for contacting us.
What you are likely experiencing is an issue when trying to find the view. I would recommend you make the casing of the Area be the same as the one in the folder. Another possibility is that we are lowercasing all the file paths and that might require you to use lowercase letters for area names.
@pranavkm do you have any thoughts here?

As @javiercn noted, case sensitivity typically comes from the OS's file lookup. With runtime compilation, MVC relies on the operating system to perform view lookups. A mismatch in case would result in failure to lookup in a case sensitive OS like Linux. Preserving case consistency across controllers, actions and view file names would be the way to go.


[improve][broker] Use bulk operation instead of iteration

Motivation
Use bulk operation instead of iteration
Modifications
Use putAll,addAll method instead of forEach
Verifying this change

[ ] Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

The addAll() will also has a iteration  operation,  I wonder will addAll will be more efficient than iteration

/pulsarbot rerun-failure-checks

The addAll() will also has a iteration operation, I wonder will addAll will be more efficient than iteration

Thanks for your reivew,addAll()  and putAll() internal implementation also has a iteration operation, fortunately, HashMap's putAll() method resize before iteration, so it is more efficient. And looks cleaner.


Updated AWS provider to 1.34.0

Ideally, Octopus would fetch the latest plugin release from Hashicorp.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@storkie the 2018.9.0 release of Octopus Server will update the Terraform AWS plugin to version 1.39.0.
We have an open issue related to downloading of any additional plugins.


Remove Slide

I need to be able to remove slides from the presentation. I note that this is listed as an item in the backlog, although I cannot find a backlog to add my comment to.
I've forked the project and hope to be able to contribute a method to add this feature.
Thanks for the good work!

Just found https://github.com/scanny/python-pptx/issues/67. Closing this issue.


Add test preparation for arch based systems

Proposed changes:

add prepare-testes-arch in the Makefile of project

closes #10828

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: SamuelNoB:white_check_mark: emysdias:x: Matheus73You have signed the CLA already but the status is still pending? Let us recheck it.


Red screen after searching or tapping a story

@sreilly I've seen only one report so far, but can you look into this? This is on iOS 7.1.2
"Whenever I try to search or click on a story I get a red screen and never anything else."

@thm Ah yes, there was a bug in the web page viewer which would only happy on iOS7 and earlier.  I've fixed it and pushed a copy to the app store for review.  The current internal testflight build also has this fix, but alas iOS7 doesn't have the ability to install testflight builds.  I have tested it manually on an old iOS7 phone.

@sreilly thanks!


[TEST] fill up access token test

fill up remaining line not be covered by existing AccessTokenServiceTest

@abzymeinsjtu please run 'mvn spotless:apply' to fix the code style

updated

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 39.07%.  Consider uploading reports for the commit 348f008 to get more accurate results

Additional details and impacted files
@@             Coverage Diff              @@
##                dev   #15710      +/-   ##
============================================
+ Coverage     39.05%   39.07%   +0.01%
- Complexity     4845     4851       +6
============================================
  Files          1316     1316
  Lines         45011    44975      -36
  Branches       4818     4794      -24
============================================
- Hits          17581    17574       -7
+ Misses        25524    25500      -24
+ Partials       1906     1901       -5

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


We need federation!

I would suggest two types: Input Federation (e.g. for data coming from TTN) and output federation (get data from other instances, requires authentication and authorisation for non-public-sensors)

Maybe we even should think about local instances (at home) and cloud instances (inside "Freifunk-Mesh-Cloud")

I think it is better to think about the types as pull federation and push federation, similar to the activitypub standard.

Maybe, for me it seems best to do push federation from sensors to ingress, and pull federation to get/view data.

Maybe, for me it seems best to do push federation from sensors to ingress, and pull federation to get/view data.

What scenarios do we have for federation?
I can think of "User wants to display data from remote server", this would be a "pull" or "output" type federation.
We don't need federation for getting data from TTN into Freifunk-IoT, the gateway can just push the data to the correct server in the first place.
I'm trying to think of a scenario for "push" or "input" federation but can't.

Not sure what you mean with "local" and "cloud" instances? Why should an instance run at home be different from an instance run in "the cloud"?

Local/Cloud: Aggregate Data on local homeserver (i.e. when connectivity issues occur), but view it on cloud/public instance

We don't need federation for getting data from TTN into Freifunk-IoT, the gateway can just push the data to the correct server in the first place.

I think federation would be the right approach. Normal input is when a sensor is adding something. When another kind of aggregator - this would be a TTN-Gateway - is adding something, for me it seems the best to handle it as federation.

Local/Cloud: Aggregate Data on local homeserver (i.e. when connectivity issues occur), but view it on cloud/public instance

We don't need federation for getting data from TTN into Freifunk-IoT, the gateway can just push the data to the correct server in the first place.

I think federation would be the right approach. Normal input is when a sensor is adding something. When another kind of aggregator - this would be a TTN-Gateway - is adding something, for me it seems the best to handle it as federation.

I would also say, that something like gateways are very likely to occur. This would allow a setup, where not every device/aggregator needs direct internet/cloud access. Especially considering the exploits from the past on IoT devices.


java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__cmsg_nxthdr" referenced by

Hi, on my android device, has this error
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__cmsg_nxthdr" referenced by ...
NDK Version:10e
SDK API 22
Device Version Android 4.4.4
and in Android NDK, Revision 10b (September 2014) History:
Made the following fixes to the Android-L headers:
Renamed cmsg_nxthdr to __cmsg_nxthdr.

How are you compiling / using libuv?

LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
my Android.mk, Thanks
LOCAL_MODULE := uv_static
LOCAL_MODULE_FILENAME := libuv
LOCAL_SRC_FILES := 	src/unix/android-ifaddrs.c
src/fs-poll.c
src/inet.c
src/threadpool.c
src/unix/async.c
src/unix/core.c
src/unix/dl.c
src/unix/fs.c
src/unix/getaddrinfo.c
src/unix/getnameinfo.c
src/unix/linux-core.c
src/unix/linux-inotify.c
src/unix/linux-syscalls.c
src/unix/loop-watcher.c
src/unix/loop.c
src/unix/pipe.c
src/unix/poll.c
src/unix/process.c
src/unix/proctitle.c
src/unix/pthread-fixes.c
src/unix/signal.c
src/unix/stream.c
src/unix/tcp.c
src/unix/thread.c
src/unix/timer.c
src/unix/tty.c
src/unix/udp.c
src/uv-common.c
src/version.c
LOCAL_C_INCLUDES := $(LOCAL_PATH)/include
$(LOCAL_PATH)/src
$(LOCAL_PATH)/src/unix
LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
$(LOCAL_PATH)/src
LOCAL_CFLAGS   := -D__ANDROID__ -D__linux__ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
include $(BUILD_STATIC_LIBRARY)

in API 15: socket.h,
#define CMSG_NXTHDR(mhdr, cmsg) cmsg_nxthdr((mhdr), (cmsg))
and in API 21
#define CMSG_NXTHDR(mhdr, cmsg) __cmsg_nxthdr((mhdr), (cmsg))

We just use CMSG_NXTHDR, so I'm not sure what libuv can do here. I'm going to close this, since it's a platform issue specific to Android. We support API level >= 14 (IIRC) on a best effort basis.
Alternatively, try to compile libuv using the provided android-configure script and see if that makes any difference.


Interrupting cancelable asynchronous resource allocations

I think it would be useful for the library to make a conceptual distinction between interrupting control flow and interrupting "long" operations. For example, adding a variant of asyncInterrupt that is cancelable even inside .uninterruptible (at least when noInterrupt <= 1) would allow us to use potentially long allocating operations inside brackets acquire:
def acquire(uri: URI): IO[E, R] = IO.interruptible { (k: IO[E, R] => Boolean ) =>
  val future = openIsLongButCancelable(uri)
  future.addListener {
    case Success(resource) =>
      if (!k(IO.succeed(resource))) {
        // Fiber has been interrupted
        resource.close()
      }
    case Failure(e) =>
      k(IO.fail(e))
  }
  Left(IO.succeedLazy(future.cancel()))
}

Surely, I don't want to be interrupted on a flatMap and leak a freshly allocated resource, but I don't want to waste time allocating things I no longer need either.

I'm open to doing some work here, but it needs to be extremely well developed because of the potential for resource leaks. @systemfw has some ideas.
Have you considered using Managed? Managed lets you describe a resource whose acquisition can be interrupted safely. It's a slightly different pattern than bracket but may accomplish what you're looking for here.
Note that this example has a race condition in it. What if the future returned by openIsLongButCancelable has, for all intent and purposes, acquired its resource, but has not yet returned from Future { ... }? Or if it is a future from Promise#future, then possibly the resource has been acquired, but the line of code which sets the promise has not yet been invoked.
Fundamentally, if you allow examples like this, then they will leak resources eventually. The races are small, a matter of microseconds, but they will happen and you can observe them if you repeatedly try in tight loops.

As far as I can tell, only compound (i.e. made with flatMap) Managed are interruptible, individual Managed.make are still uninterruptible in acquire. There is a test for that behavior in ManagedSpec.
I could've been more clear about the example. The future there is not scala.concurrent.Future, but something properly designed for cancellation, like Netty's ChannelFuture. Anyway, please take a look at #580, it tackles the issue in a more generic way.

This problem is solved by Managed with reservation, but examples suggested by @mvv point the way to something more general, #706. Closing this in favor of that one.


V2 Production - No email sent to CLA Signatory

Summary
When a CLA Manager selects "no" to send an email to an authorized signer for their company, the dialog box says the email was sent, but no email was delivered. There is no record in Mandrill of the email being sent.

Currently blocked by requestCorporateSignature: {code: 400, message: "Post "/v1/request-corporate-signature": unsupported protocol scheme """,…} code: 400 data: null message: "Post "/v1/request-corporate-signature": unsupported protocol scheme """ success: false __typename: "RequestCorporateSignatureResult"  response. It appears the api_base_url was not passed in the request for this use cas

Currently blocked by requestCorporateSignature: {code: 400, message: "Post "/v1/request-corporate-signature": unsupported protocol scheme """,…} code: 400 data: null message: "Post "/v1/request-corporate-signature": unsupported protocol scheme """ success: false __typename: "RequestCorporateSignatureResult"  response. It appears the api_base_url was not passed in the request for this use cas

David to syncup with Harold.

David to syncup with Harold.

Now I am getting:

In the console the response:
{"data":{"requestCorporateSignature":{"code":400,"message":"[POST /v1/orgs/{salesforceID}/scopes][400] createOrgUsrRoleScopesBadRequest  &{Code:400 Message:organization-service - usernames: non zero value required XRequestID:f0b6c160-56cf-11eb-b583-697c69266abd}","success":false,"data":null,"__typename":"RequestCorporateSignatureResult"}}}

Now I am getting:

In the console the response:
{"data":{"requestCorporateSignature":{"code":400,"message":"[POST /v1/orgs/{salesforceID}/scopes][400] createOrgUsrRoleScopesBadRequest  &{Code:400 Message:organization-service - usernames: non zero value required XRequestID:f0b6c160-56cf-11eb-b583-697c69266abd}","success":false,"data":null,"__typename":"RequestCorporateSignatureResult"}}}

When sent to hwillson+signatory2, a confirmation box that an email was sent, but still no email received.

When sent to hwillson+signatory2, a confirmation box that an email was sent, but still no email received.

I also tried sending this to a signatory email with gmail so as to not cause any conflict with assigning the LF employee role. Same result. The email never arrived.

I also tried sending this to a signatory email with gmail so as to not cause any conflict with assigning the LF employee role. Same result. The email never arrived.

@dealako , fyi.. Asha checked this one on Staging and it working fine there.

@dealako , fyi.. Asha checked this one on Staging and it working fine there.

Tested this in dev and received an email however there was a slight delay in receiving the email . Currently dont have access to prod projects for test purposes

Tested this in dev and received an email however there was a slight delay in receiving the email . Currently dont have access to prod projects for test purposes

@WillsonHG and I tested in PROD - observed successful email:

@WillsonHG and I tested in PROD - observed successful email:

@vinod-kadam - I recommend we either re-test one more time and/or close and possibly re-open if this pops up again.

@vinod-kadam - I recommend we either re-test one more time and/or close and possibly re-open if this pops up again.

I have verified on production today that I received an email both to the signatory with an email/user in the system, and one without a user in the system.

I have verified on production today that I received an email both to the signatory with an email/user in the system, and one without a user in the system.


How to calculate moon type

I need to calculate rising/falling moon type.

This library does not presently calculate moonrise, moon transit, or moon set.
They could be added in the future, but in the meantime, you might try:

https://github.com/mourner/suncalc (Suncalc.getMoonTransit())
https://github.com/darkskyapp/astro (astro.lunar.transit(), astro.lunar.rise(), astro.lunar.set())


Reduce log level

Hi! Is there a way to reduce the log level of the application? I see that passwords used for sending notifications are being leaked in the logs which is not very secure.

@dcasado try to assume that I cannot see what you are seeing on your screen and that I am not sitting next to you, please try to help me out here, I am not a mind reader, please paste some of the output - obviously redact the 'important' stuff

maybe some env var for setting it hmm

Sorry I gave you little information. First of all I'm using Docker container version 0.39.4
From what I saw the log below is written every time I click the button Save in the notifications settings. I have setup email and gotify notifications. I have changed the places where passwords are shown in plain text with GOTIFY_TOKEN and EMAIL_PASSWORD as well as other sensitive information.
Taking a look at the code I saw these two lines that can be the cause of this logging but I'm not sure and I didn't test to change it.
https://github.com/dgtlmoon/changedetection.io/blob/ecba130fdb49cd8e226e3b5a34df81754c2fbc22/changedetectionio/notification.py#L27
https://github.com/dgtlmoon/changedetection.io/blob/ecba130fdb49cd8e226e3b5a34df81754c2fbc22/changedetectionio/notification.py#L28
Log output:
DEBUG:apprise:Loaded E-Mail URL: mailtos://EMAIL_USER:****@EMAIL_SERVER/TO_EMAIL?from=FROM_EMAIL&mode=starttls&smtp=EMAIL_SERVER&user=EMAIL_USER&format=html&overflow=upstream&rto=4.0&cto=15&verify=yes

headers="{}"

smtp_host="EMAIL_SERVER"

from_addr="FROM_EMAIL"

targets="['TO_EMAIL']"

verify="True"

secure="True"

qsd:="{}"

qsd-="{}"

qsd+="{}"

qsd="{'user': 'EMAIL_USER', 'pass': 'EMAIL_PASSWORD', 'smtp': 'EMAIL_SERVER', 'from': 'FROM_EMAIL', 'to': 'TO_EMAIL'}"

url="mailtos://EMAIL_SERVER"

schema="mailtos"

query="None"

path="None"

fullpath="None"

host="EMAIL_SERVER"

port="None"

password="EMAIL_PASSWORD"

user="EMAIL_USER"

TRACE:apprise:E-Mail URL mailtos://EMAIL_SERVER?user=EMAIL_USER&pass=EMAIL_PASSWORD&smtp=EMAIL_SERVER&from=FROM_EMAIL&to=TO_EMAIL unpacked as:

DEBUG:apprise:Loaded Gotify URL: gotifys://GOTIFY_URL/A...u/?priority=8&format=text&overflow=upstream&rto=4.0&cto=4.0&verify=yes

priority="8"

token="GOTIFY_TOKEN"

verify="True"

secure="True"

qsd:="{}"

qsd-="{}"

qsd+="{}"

qsd="{'priority': 'high'}"

url="gotifys://GOTIFY_URL/GOTIFY_TOKEN"

schema="gotifys"

query="GOTIFY_TOKEN"

path="/"

fullpath="/"

host="GOTIFY_URL"

port="None"

password="None"

user="None"

TRACE:apprise:Gotify URL gotifys://GOTIFY_URL/GOTIFY_TOKEN/?priority=high unpacked as:

DEBUG:apprise:Loaded E-Mail URL: mailtos://EMAIL_USER:****@EMAIL_SERVER/TO_EMAIL?from=FROM_EMAIL&mode=starttls&smtp=EMAIL_SERVER&user=EMAIL_USER&format=html&overflow=upstream&rto=4.0&cto=15&verify=yes

headers="{}"

smtp_host="EMAIL_SERVER"

from_addr="FROM_EMAIL"

targets="['TO_EMAIL']"

verify="True"

secure="True"

qsd:="{}"

qsd-="{}"

qsd+="{}"

qsd="{'user': 'EMAIL_USER', 'pass': 'EMAIL_PASSWORD', 'smtp': 'EMAIL_SERVER', 'from': 'FROM_EMAIL', 'to': 'TO_EMAIL'}"

url="mailtos://EMAIL_SERVER"

schema="mailtos"

query="None"

path="None"

fullpath="None"

host="EMAIL_SERVER"

port="None"

password="EMAIL_PASSWORD"

user="EMAIL_USER"

TRACE:apprise:E-Mail URL mailtos://EMAIL_SERVER?user=EMAIL_USER&pass=EMAIL_PASSWORD&smtp=EMAIL_SERVER&from=FROM_EMAIL&to=TO_EMAIL unpacked as:

DEBUG:apprise:Loaded Gotify URL: gotifys://GOTIFY_URL/A...u/?priority=8&format=text&overflow=upstream&rto=4.0&cto=4.0&verify=yes

priority="8"

token="GOTIFY_TOKEN"

verify="True"

secure="True"

qsd:="{}"

qsd-="{}"

qsd+="{}"

qsd="{'priority': 'high'}"

url="gotifys://GOTIFY_URL/GOTIFY_TOKEN"

schema="gotifys"

query="GOTIFY_TOKEN"

path="/"

fullpath="/"

host="GOTIFY_URL"

port="None"

password="None"

user="None"

TRACE:apprise:Gotify URL gotifys://GOTIFY_URL/GOTIFY_TOKEN/?priority=high unpacked as:

Ahuh ok, yeah, thanks - I didnt realise it would be coming from apprise directly, btw - how do you use Gotify in your situation?
I'll look at a fix, maybe turn on TRACE for debugging, problem is many people report some issue, which is not directly todo with changedetection.io but is more with apprise (for example they send a huge payload and the notification service wont accept it)

I'm still testing the setup but I plan to use Gotify to notify me of changes in a web page just as email. I'm not planning on sending huge diffs just a little text to know which page has changed.
Yeah something configurable would be awesome, that you can turn off if those logs are not needed but can be turned on if an issue is detected to report it.

https://github.com/dgtlmoon/changedetection.io/pull/403 disabled the 'TRACE' output and saves the last 100 errors to the session, I think this should be a huge improvement


WIP: change CI to debug windows crash

This is a temporary PR to debug the windows crash on CI
Motivation

What are the most important goals of the ticket or PR?
PR Author Checklist
Check before marking the PR as ready for review:

[ ] Will the PR name make sense to users?
[ ] Does the PR have a priority label?
[ ] Have you added or updated tests?
[ ] Is the documentation up to date?

For significant changes:

[ ] Is there a summary in the CHANGELOG?
[ ] Can these changes be split into multiple PRs?

If a checkbox isn't relevant to the PR, mark it as done.
Specifications

Complex Code or Requirements

Solution

Testing

Review

Reviewer Checklist
Check before approving the PR:

[ ] Does the PR scope match the ticket?
[ ] Are there enough tests to make sure it works? Do the tests cover the PR motivation?
[ ] Are all the PR blockers dealt with?
PR blockers can be dealt with in new tickets or PRs.

And check the PR Author checklist is complete.
Follow Up Work

@conradoplg Could we close this PR now that the issue's been resolved?

@conradoplg Could we close this PR now that the issue's been resolved?

Yep. The CI change is still useful so we can keep the branch around.


Various updates

Hello
Your library is awesome.

Merging in your recent commit (UIImage/NSImage + Cache), I got a lot of conflicts as we both addressed the same image memory issues :)
So, I decided to take your most recent branch and apply my code updates to it (to have a small number of commits) and make this PR. I hope you find it (or parts of it) useful.
Change list:

Updated .gitignore to include possible output of latest assimp build (including dynamic library for the macOS target)
Added the example projects to the workspace
Using CGImageRef directly for both iOS and Mac targets, rather than creating UIImage / NSImage wrapper for each platform
Test targets no longer require to be familiar directly with assimp
Silly typo-crash fixed when MY_DEBUG was set and a call to DLog(@" N VERTICES: %@", @(nVertices)); was made
Importer'saiFace->mNumIndices != 3 edge case error fix
SCNTextureInfo - Managing _image, _color and _colorSpace memory manually
SCNTextureInfo - Sorted out some embedded textures / colour glitches I encountered
SCNTextureInfo - Sorted out construction and assignment of externalTexturePath
SCNTextureInfo - Added sanity assertions
SCNTextureInfo- Simplified embedded texture creation and memory footprint
Automatically load first animation when loading the model
Allow model export to .scn / .dae / .obj
use fileURLWithPath
All targets pass Static analyser with no "blue" issues
Pass both xctests
(Tested separately works well with assimp v4.1 with BitCode for assimp, dynamic library for assimp on macOS)

Regards,
Doron Adler

Codecov Report

Merging #108 into master will increase coverage by 0.2%.
The diff coverage is 93.4%.

@@            Coverage Diff            @@
##           master     #108     +/-   ##
=========================================
+ Coverage   74.74%   74.95%   +0.2%
=========================================
  Files          17       17
  Lines        1564     1589     +25
=========================================
+ Hits         1169     1191     +22
- Misses        395      398      +3

Impacted Files
Coverage Δ

AssimpKit/Code/Model/Tests/AssimpImporterTests.m
64.5% <100%> (-0.17%)
:arrow_down:

AssimpKit/Code/Model/AssimpImageCache.m
81.81% <71.42%> (-18.19%)
:arrow_down:

AssimpKit/Code/Model/AssimpImporter.m
89.06% <92.85%> (-0.02%)
:arrow_down:

AssimpKit/Code/Model/SCNTextureInfo.m
97.1% <95.16%> (+0.35%)
:arrow_up:

Continue to review full report at Codecov.

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

@Norod Thanks for these contributions, extremely useful.
Any chance, you can give a shot to resolve the conflicts? Otherwise I will give it a dash in the weekend post Sep 20.
Sincerely apologize for the delay, work took priority!
Thanks again.


Debug Logs should not private certificates

Do you want to request a feature or report a bug?
Bug
What did you do?
When I start traffic with traefik with --loglevel=DEBUG traefik logs all information it gets back from the k8s in the line Configuration received from provider kubernetes which contain the json  contains private certs data as well from ingress tls secret's.
What did you expect to see?
Logs that were safe to share and free of my private SSL certs. I would like traefik to never dump my private certificates into standard out. Which is generally pushed to external log collection like ELK or even a 3rd party
What did you see instead?
Traefik dumping my private SSL certs to standard out. Which would be fine if I wasn't running in kubernetes which pushes all logs to our log collector.
Output of traefik version: (What version of Traefik are you using?)
v1.7.0-rc2

What is your environment & configuration (arguments, toml, provider, platform, ...)?
na
If applicable, please paste the log output in DEBUG level (--logLevel=DEBUG switch)
this is the exact problem, the logs are impossible to share because they contain secret data.

Closed by #3665.

Closed by #3788.


Please guide configuration step number 3, and when drag and drop file to Xcode where exactly to drop and do i have to rename json file that contains animation?

Please guide configuration step number 3, and when drag and drop file to Xcode where exactly to drop and do i have to rename json file that contains animation?

I guide lottie file name to loading.json in this project.
If you want to rename lottie file, then change below code location.
https://github.com/HwangTaehyun/react-native-lottie-splash-screen#:~:text=Dynamic *t %3D [Dynamic new]%3B
  UIView *animationView %3D [t createAnimationViewWithRootView%3ArootView lottieName%3A%40"loading"]%3B // change lottieName to your lottie files name
  animationView.backgroundColor %3D [UIColor whiteColor]%3B // change backgroundColor
Thank you.


Add Intercoin (ITR) tokens to MetaMask

Relevant Links:
Website: https://intercoin.org
Community: https://community.intercoin.org
Channel: https://youtube.com/c/intercoin
Presentation: https://intercoin.org/presentation.pdf
Press: https://www.coindesk.com/in-defense-of-blockchain-voting
Telegram: https://t.me/intercoin
Twitter: https://twitter.com/IntercoinOrg
LinkedIn: https://www.linkedin.com/company/intercoin
GitHub: https://github.com/Intercoin

Hi @xrn , what does the "pending community activity" label represent?


THRIFT-5272 printTo does not properly handle i8 datatypes

This fixes Thift5272. Using the patch provided with the issue and adding a test for it.
There is one commit for the test, which includes related build-files (Makefile + CMake). So you can see the test is actually detecting the issue.
There is 2nd commit for the fix, this also makes the test pass.
The 3rd commit is just updating a deprecated and a missing header
If needed I can squash commits of test and fix.

When running on AppVeyor without the fix, the test correctly failing with error:
      Start 17: UnitTests
17: Test command: C:\projects\build\MSVC2015\x86\bin\Debug\UnitTests.exe
17: Test timeout computed to be: 300
17: Thrift: Thu Jul 18 15:01:47 2024 getaddrinfo() -> 11001; No such host is known.
17:
17: Running 76 test cases...
17: An error message from getaddrinfo on the console is expected:
17: C:/projects/thrift/lib/cpp/test/Thrift5272.cpp(43): error: in "Thrift5272Test/printTo": check text == "Meta(byte_type=0, i8_type=0, i16_type=0, i32_type=0, i64_type=0)" has failed [Meta(byte_type=
17: , i8_type=
17: , i16_type=0, i32_type=0, i64_type=0) != Meta(byte_type=0, i8_type=0, i16_type=0, i32_type=0, i64_type=0)]
17: C:/projects/thrift/lib/cpp/test/Thrift5272.cpp(54): error: in "Thrift5272Test/printTo": check text == "Meta(byte_type=50, i8_type=50, i16_type=50, i32_type=50, i64_type=50)" has failed [Meta(byte_type=2, i8_type=2, i16_type=50, i32_type=50, i64_type=50) != Meta(byte_type=50, i8_type=50, i16_type=50, i32_type=50, i64_type=50)]
17: C:/projects/thrift/lib/cpp/test/Thrift5272.cpp(65): error: in "Thrift5272Test/printTo": check text == "Meta(byte_type=127, i8_type=127, i16_type=127, i32_type=127, i64_type=127)" has failed [Meta(byte_type=, i8_type=, i16_type=127, i32_type=127, i64_type=127) != Meta(byte_type=127, i8_type=127, i16_type=127, i32_type=127, i64_type=127)]
17:
17: *** 3 failures are detected in the test module "thrift"
17: Detected memory leaks!
17: Dumping objects ->
17: {9859} normal block at 0x0052B048, 73 bytes long.
17:  Data: <                > 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
17: Object dump complete.
17/52 Test #17: UnitTests ........................***Failed    3.44 sec

You can also see the linebreaks in the log as of the null-byte in 1st test-case.

@emmenlau  What's the statis with this? It still says "changes requested"? Is this correct?

I updated the mentioned code and pressed "resolve conversation for it" 3 weeks ago

Just found the "request re-review" button, but "Changes requested" state remains

@SvenRoederer Thanky, if you had an JIRA account I could also assign yout the ticket ;-)

@Jens-G I had thought about Jira account too, but I'll change job soon  and not sure how much I'll still with Thrift ...

@SvenRoederer  That's bad news, would be a loss.

fwiw, the source tar.gz archive in https://dlcdn.apache.org/thrift/0.21.0/ doesnt contain lib/cpp/test/Thrift5272.thrift so the build fails here (porting thrift to OpenBSD).


WinAppDriver failed to up

I have configured WinAppDriver to listen on external IP (static), sometimes after restart it fails to up with following error. The WinAppDriver is configured to start on log on.

Thanks in advance

Port 80 is reserved for HTTP, can you please try with a different port?

I closed the issue , as IP address can be configured *.
https://github.com/Microsoft/WinAppDriver/issues/39


Orders needs to updated with new api version. Change '100' default value in param max_results in Orders.list_orders to None.

URI in Orders should be changed to "/Orders/2013-09-01"
VERSION in Orders should be changed to "2013-09-01"
NS in Orders should be changed to '{https://mws.amazonservices.com/Orders/2013-09-01}'
This is because the old version of 2011-01-01 has been deprecated.
The max_results param in Orders.list_orders should be changed to None instead of '100'. When it's defaulted to 100 then the api will NOT return a NextToken. This is because the default value when MaxResults is not specified is already 100 and if there's more than 100 orders resulting from your query, it supplies the NextToken field. When MaxResults is set to 100, the query results don't exceed 100 and thus the api doesn't return a NextToken field.
Edit: nevermind about max results.

Any plan to merge this?

For info, here is a copy of a recent (2016-10-31) from Amazon re timing:

Hello,
The 2011-01-01 version of the MWS Orders API section is being deprecated, and this affects you.
In 2014, we released version 2013-09-01 of the Orders API section. At that time and in the years following, we added new functionality to this version that the older version (2011-01-01) does not have.
When we first announced the new version, we said that if you didn't need the added functionality, you could continue to use version 2011-01-01 until the sunset date, February 28, 2017, after which it will no longer be available. That is still true.
However, we also said that the MWS portal pages, client libraries, and documentation for version 2011-01-01 would be available on https://developer.amazonservices.com until the sunset date. That is no longer true. We have discontinued support of the portal pages, client libraries, and documentation for version 2011-01-01.
We encourage you to make the transition to version 2013-09-01 now. To see the most recent updates to this version, go to this Client Libraries page, http://docs.developer.amazonservices.com/en_US/orders/2013-09-01/Orders_ClientLibraries.html
Thank you,
Amazon Marketplace Web Service


Document NormalModule

Feature to document

From https://webpack.js.org/api/loaders/:

Resolves the given request to a module, applies all configured loaders and calls back with the generated source, the sourceMap and the module instance (usually an instance of NormalModule). Use this function if you need to know the source code of another module to generate the result.

NormalModule links to the source, but it's difficult to figure out what some of this does, and which parts plugin authors can rely on. module.buildInfo seems very useful, for instance.
I don't know when this feature was introduced.
Author(s)

I don't know who introduced this feature.
Additional information

[ ] I am willing to work on this issue and submit a pull request.
Sorry, I don't really know how it works, so I can't document it.

If I'm not mistaken, it was a part of compilation hooks before, but the change wasn't widely reflected in the docs outside the given link afaik.


Reduce syscall overhead in native epoll transport when a lot of timeo…

…uts are scheduled
Motivation:
At the moment we might end up calling timerfd_settime everytime a new timer is scheduled. This can produce quite some overhead. We should try to reduce the number of syscalls when possible.
Modifications:

If we are using Linux Kernel >= 5.11 use directly epoll_pwait2(...)
If the scheduled timeout is big enough just use epoll_wait(...) without timerfd_settime and accept some inaccuracy.

Result:
Fixes https://github.com/netty/netty/issues/11695

@normanmaurer this change looks great! In general though (as I'm sure you know) we don't set timerfd every time the EL goes to sleep, only if a deadline has expired or there's a new deadline earlier than an existing one. So I guess this would only cause a problem in cases there's continuous/frequent scheduled tasks used (as is the case in the motivating issue).
Anyhow, for this reason I think some corresponding changes will also be needed to the deadline tracking logic in EpollEventLoop. It currently assumes deadlines are persistent across calls to epollWait but now that may or may not be the case depending on whether or not timerfd was used.
With this new change we may need the native epollWait(deadline) call to return a flag indicating whether timerfd was used (and so whether the current deadline is persistent). In the case it isn't used, we need to call epollWait(deadline) the next time again rather than epollWaitNoTimerChange() which might have been used otherwise.

@normanmaurer this change looks great! In general though (as I'm sure you know) we don't set timerfd every time the EL goes to sleep, only if a deadline has expired or there's a new deadline earlier than an existing one. So I guess this would only cause a problem in cases there's continuous/frequent scheduled tasks used (as is the case in the motivating issue).

Yes I know :)

Anyhow, for this reason I think some corresponding changes will also be needed to the deadline tracking logic in EpollEventLoop. It currently assumes deadlines are persistent across calls to epollWait but now that may or may not be the case depending on whether or not timerfd was used.
With this new change we may need the native epollWait(deadline) call to return a flag indicating whether timerfd was used (and so whether the current deadline is persistent). In the case it isn't used, we need to call epollWait(deadline) the next time again rather than epollWaitNoTimerChange() which might have been used otherwise.

Good point...let me double check.
That said I think you agree that the general idea of this change makes sense, correct @njhill ?

That said I think you agree that the general idea of this change makes sense, correct @njhill ?

Yes, I really like the change. It's not clear yet how much impact it will have but seems there's a good chance it's noticeable in some cases and I don't see any downsides apart from a bit of added complexity.
By the way when I say "return a flag" by the way, I'm not sure exactly the best way to do that, maybe using a high bit of the return value. The loop needs to know one way or another though.

That said I think you agree that the general idea of this change makes sense, correct @njhill ?

Yes, I really like the change. It's not clear yet how much impact it will have but seems there's a good chance it's noticeable in some cases and I don't see any downsides apart from a bit of added complexity.
By the way when I say "return a flag" by the way, I'm not sure exactly the best way to do that, maybe using a high bit of the return value. The loop needs to know one way or another though.

We could also move some of the complexity to the java layer which might make it easier. Let me think about it a bit.

We could also move some of the complexity to the java layer which might make it easier. Let me think about it a bit.

Yeah I was wondering that too, but seems a bit messy to have the logic related to choosing different syscalls there (e.g. whether epoll_wait2 is available etc).

@normanmaurer yeah actually the necessary java change would be very simple if we can pass back that flag. If timerfd isn't used by the call to epollWait then just set prevDeadlineNanos to NONE rather than curDeadlineNanos here, and obviously move that line after the epollWait call rather than before it.

@chrisvest it's not really a better way, just something else that needs to be included for this to work properly. Currently if the java code sets a deadline once it won't pass any timeout on the next call to epollWait because the timerfd setting will persist. However with this change we need to make sure to always pass the deadline/timeout if timerfd wasn't used for the prior call, since it still needs to be included as a timeout arg in each call to epoll_wait/epoll_wait2.

@njhill Aha, yeah that makes sense!

@njhill @franz1981 @chrisvest PTAL again

Let's write a benchmark for this :P (if is possible)

Let me investigate why we have timeouts here...


[BUG] Regression selector

Describe the bug
Regression, grayskull is putting some selectors outside of the brackets
To Reproduce
Steps to reproduce the behavior:
requests==2.27.1
Probably it was introduced when stripping the ~=. As conda-build supports it we might let the old behaviour
Expected behavior
{% set name = "requests" %}
{% set version = "2.27.1" %}

package:
  name: {{ name|lower }}
  version: {{ version }}

build:
  skip: true  # [py==30 or py==31 or py==32 or py==33 or py==34 or py==35]
  script: {{ PYTHON }} -m pip install . -vv
  number: 0

source:
  url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/requests-{{ version }}.tar.gz
  sha256: 68d7c56fd5a8999887728ef304a6d12edc7be74f1cfa47714fc8b414525c9a61

requirements:
  host:
    - pip
    - pytest
    - python
  run:
    - certifi >=2017.4.17
    - chardet >=3.0.2,<5  # [py<3]
    - charset-normalizer >=2.0.0  # [py>=3,==2.0.*]
    - idna >=2.5,<3  # [py<3]
    - python
    - urllib3 >=1.21.1,<1.27

test:
  imports:
    - requests
  commands:
    - pip check
  requires:
    - pip

about:
  home: https://requests.readthedocs.io
  summary: Python HTTP for Humans.
  dev_url: https://github.com/psf/requests
  license: Apache-2.0
  license_file: LICENSE

extra:
  recipe-maintainers:
    - ADD_YOUR_GITHUB_ID_HERE

Outputs
If applicable, add the output to help explain your problem.
Environment:

conda list
pip list
grayskull --version

Additional context
Add any other context about the problem here.

Fixed


underground pipeline

I am currently exploring the capabilities of openglobus for a project that involves visualizing underground pipelines.
Could you please let me know if the library supports this functionality, or if there are any recommended approaches to achieve this within the framework?

Greetings @moeinmf92! Globus doesn't have this functionality. It's easy to adapt ui/ux to work underground and visualize objects like pipes, cylinders, spheres corridors, etc and even interact with them. But it doesn't have such tools from scratch. Globus is a bare-bones engine that could be used for such tasks.
Some enterprise BIM tools have this, from Hexagon, ArcGIS, and Skyline.... as far as I know, some proprietary projects built on CesiumJs also have this, or even Cesium has some basic tools, but I've never checked them out.
P.S.
The task is very interesting, and I have plans to make some basics in this way, such as visualizing and camera navigation underground and placing 3D objects here and there, not the pipes (pipes connections is another interesting task:)), kind of a very simple BIM interface.


Waka Time cannot detect if I rename my project folder

Waka Time cannot detect if I rename my project folder!

You can rename your project folder, after that rename project in waka web.


Item modules Validation

[ ] At least enable one type of transaction for each goods and service

sales information 3 decimal issue

issue fixed !


Gateway API v1

Is your feature request related to a problem? Please describe.

Gateway API has graduated to GA meaning there are now v1 versions of the following resources:

Gateway
GatewayClass
HTTPRoute

Relevant docs / release notes:

https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.0.0
https://kubernetes.io/blog/2023/10/31/gateway-api-ga/
https://kubernetes.io/blog/2023/10/25/introducing-ingress2gateway/

Describe the solution you'd like

Update cert-manager code / tests to ensure full compatibility with v1 resources.
Describe alternatives you've considered

N/A
Additional context

Re slack thread.
Environment details (remove if not applicable):

Kubernetes version: >= 1.24
Cloud-provider/provisioner: all
cert-manager version: 1.14 onwards?
Install method: all

/kind feature

So far I found that cert-manager is using v1beta1 here and in some make config resources.

Would you guys be able to get this into 1.14? 🙏🏻
Have a live AKS cluster with Gateway API 1.0. Could really use this. 🍻


feature: Add un-archive option for archived notes

Description

Request to add an un-archive option for archived notes. Currently, users can archive notes but have no way to easily restore them to the active notes list
Add an "Un-archive" button next to each archived note in the archive section. When clicked, the note should be moved back to the active notes list, making it easily accessible again.

Screenshots

Additional Context
Add any other context or information about the issue here.

@yashmandi : please assign this to me

Thanks for raising this issue . Assigned @mehul-m-prajapati


[fix] unable to generate thumbnail file

Coverage decreased (-0.01%) to 83.489% when pulling dcf5ae299ff92ed074df9ea83310a40b3dd1e542 on sunny4381:thumbnail-generation into 590a996dbf51ad5c74db095fdd93db54fde22f50 on shirasagi:master.


WaitForControlledPodsRunning: Print maxDuration

/kind feature
This can be used to estimate impact of enabling CL2_WAIT_FOR_CONTROLLED_PODS_USE_EXACT_OPERATION_TIMEOUT introduced in https://github.com/kubernetes/perf-tests/pull/2128 without actually enabling it.
/assign @marseel

/lgtm
/approve


Sidebar menu broken with 2.4.0

Hi,
I'm using admin-lte since one year. I have an angular 4 app and I build the sidebar menu dinamically and all worked fine until version 2.3.11 .
With 2.4.0 when I click on a first node of the menu the app reload the page instead of open the sub menu.

I am having this issue, too. Before the upgrade, it's all working perfectly until the release of 2.4.0
Expected Behavior:

Click on a Menu with Sub-Menu
Site should display all the sub-menu

How the system is actually behaving:

Click on a Menu with Sub-menu
The page reloads

Hi @fplini and @silverxjohn,
try adding this as your opening tag of the sidebar:

I had the same problem, now it works again.
Looks like the sidebar markup changed a little bit.
Best Regards

It doesn't work for me

https://adminlte.io/docs/2.4/upgrade-guide

also tried to add date-widget=tree in a ng4 app but it does not fix the menu.
Any other idea ?

I have spent too many hours this weekend trying to get the side bar working again since upgrading to 2.4. I'm also having the body height issue.  Completely frustrated.  Going back to 2.3.

I am not sure why the data attribute is not working :(
You could try the alternative by using the jQuery plugin directly:
$('.sidebar-menu').tree({
// Any options here
})

Documentation: https://adminlte.io/docs/2.4/js-tree

Did you remember to change data-toggle="offcanvas" to data-toggle="push-menu" for the button which toggles it? That is what I missed

Yes that made the menu "burger" toggling work again, but it has nothing to do with the sub menu opening

Ah, sorry yeah I misunderstood the issue!

I can still replicate the issue, I hope this will be fix soon. I have to revert back to 2.3.x at the moment coz I prefer using data attributes.

I'm having the same issue, having also spent a lot of time trying to fix it. Nothing in the upgrade guides help.

Since I didn't get a response on my comment https://github.com/almasaeed2010/AdminLTE/issues/1666#issuecomment-335041188
Did you attempt adding data-widget="tree" on the .sidebar-menu element?
You could also use the tree jquery plugin as mentioned above:
$('.sidebar-menu').tree({
  // Any options here
})

Thanks!

I'm having the same issue.  I  have a vanilla meanjs installation: https://github.com/meanjs/mean where I created a sidebar.client.view.html and copied the AdminLTE theme index.html into it starting with:

The sidebar shows up fine.  When I minimize it and hover over the elements, the submenus are shown correctly and I can click on any of the submenus and get the expected "page not found" since I did not setup the pages.  When I maximize the sidebar and click on any of the menu items, no submenu is shown.
I have just created a new private github repository that I can share with you if you wish to bypass the setup of the environment.  I am using:
"admin-lte": "^2.4.2"
"meanjs-version": "0.6.0"

@almasaeed2010 I think I have an idea now why my sidebar menu is broken with 2.4.0, I was trying to load adminlte.min.js via require.js, however when I tried to load adminlte.min.js via simple


fix: RequestsException with multi points layers and TSP option selected in point layer proc

Input input_points list was appended by lists of points not the points themselves.

Yes, exactly.


Added Yobit Exchange

Added Yobit Exchange
See comments in code
Fixed unix timestamps not returning time portion of DateTime

Thanks again for this. I hope your trading is going well :)

You're very welcome, and thank you for the continued maintenance.
I've got one last Exchange to add (LiveCoin) and that will be it for a while. I'll add more later. I'm only interested in Exchanges with trading APIs AND that allow deposits/withdraws via API. There's a handful more, but I have to get back to my trading software.
Markets are up. Trading is good. Let's all retire wealthy ;)

Did a little cleanup on the last pull request but all looking good. This will come in handy for multiple apps and websites I am planning. Thanks again for sharing.
Good luck! :)


thaumato readme

Without this line in the README the Docker won't start properly

Good point, the docker runs without it, but if you changed code and wanted to run the updated code you would need -v $(pwd)/:/workspace


Clean up BaseVector::addNulls API

Currently the BaseVector::addNulls(const uint64_t* bits, const SelectivityVector& rows) API has 2 vastly different behaviors
based on its input. If 'bits' in non-null then it sets nulls marked in
'bits' only for active rows in 'row'. However, if 'bits' is null then
it marks all selected rows in 'rows' as null. This is very confusing
as method comment itself only specifies the former behavior and the
expectation would be that if 'bits' is a nullptr, then there are no
nulls to add. This difference can result in silent bugs that only
surface if 'bits' is sometimes null and sometimes not. I have
therefore separated the two behaviors in two separate APIs.
Also, I traced all usages of this API up the usage hierarchy to ensure
its used correctly. Fortunately, till now, all uses that pass a 'bits'
variable seem to only call it when bits is non-null and other usages
that expect the former behavior pass an explicit nullptr.
Regardless, for the first iteration of this change, I am setting the
legacy addNulls() API to throw if a nullptr is passed in 'bits' to
flush out any callsites I might have missed and hope to catch them in
tests. Will remove this in the next patchset/update to this PR.

encountered this unexpected behavior change while reviewing #5939


Add tests for Blocs, Daos and Repository

Depends and based on https://github.com/wednesday-solutions/flutter_template/pull/3
Description:

Add tests for WeatherRepository
Add tests for CityDao
Add tests for weatherBloc
Add tests for citiesBloc
Update cities bloc to only debounce search events
Fix typos

Let's back merge to master to reduce the changelog.
Also would be great to get CI started on this template.

I have setup the CI to run in both the folders.
Could you please remove the required build workflow check as that file no longer exists.


web-test-runner: handle multiple spec files with same name

Command
test
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When using the experimental web test runner builder, a project with several spec files with the same name (in differetn directories) can't run ng test
Minimal Reproduction
npx @angular/cli@next new wtr-same-name --defaults --no-routing
cd wtr-same-name
npm i --save-dev @web/test-runner

Replace the test runner in angular.jsonwith @angular-devkit/build-angular:web-test-runner
ng test --no-watch
ng g c other/app
ng test --no-watch

The second ng test fails as there are two spec files names app.component.spec.ts
Exception or Error
❯ ng test
NOTE: The Web Test Runner builder is currently EXPERIMENTAL and not ready for production use.
The 'assets' option is not yet supported by this builder.
The 'styles' option is not yet supported by this builder.
The 'inlineStyleLanguage' option is not yet supported by this builder.
The 'stylePreprocessorOptions' option is not yet supported by this builder.
The 'sourceMap' option is not yet supported by this builder.
The 'progress' option is not yet supported by this builder.
⠙ Building...
✘ [ERROR] Two output files share the same path but have different contents: app.component.spec.js.map

✘ [ERROR] Two output files share the same path but have different contents: app.component.spec.js

Your Environment
Angular CLI: 17.1.0-rc.0
Node: 18.19.0
Package Manager: npm 9.7.1
OS: darwin arm64

Angular: 17.1.0-next.5
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1701.0-rc.0
@angular-devkit/build-angular   17.1.0-rc.0
@angular-devkit/core            17.1.0-rc.0
@angular-devkit/schematics      17.1.0-rc.0
@angular/cli                    17.1.0-rc.0
@schematics/angular             17.1.0-rc.0
rxjs                            7.8.1
typescript                      5.3.3
zone.js                         0.14.2

Anything else relevant?
No response

Getting the same issue in Angular 19 with Karma in "buildMode: application".

Getting the same issue in Angular 19 with Karma in "buildMode: application".

Can you create a new issue with a reproduction for this? If this happens for Karma with application builder, that wouldn't be a known issue (unlike WTR).

@jkrems got it: https://github.com/angular/angular-cli/issues/28915.


Utility trait for stats-based skipping logic

Parquet footer stats allow data skipping, very similar to Delta file stats. Except parquet isn't quite as convenient to work with and arrow-parquet doesn't even try to help (it can't, because arrow-compute expressions are opaque, so there's no way to traverse and rewrite them into stats-based skipping predicates).
We implement row group skipping support by traversing the same push-down predicate that delta-kernel already uses to extract a for Delta file skipping predicate. But instead of rewriting the expression, we evaluate it bottom-up (no-copy, O(n) work where n is the number of nodes in the expression).
This PR does not attempt to actually incorporate the new skipping logic into the default reader. That (plus testing the integration) should likely be a follow-up PR.

I just pushed lots of changes:

Added complete set of tests for the data skipping logic
Doc comments for everyone
Significant changes and additions to the data skipping logic itself (partly to fix bugs the tests uncovered)
Split the code into two files to match the structure that emerged.

At this point, the PR is no longer WIP. We can decide whether wiring up the row group skipping should be done in this PR or as follow-up work.

This build/coverage failure doesn't look good?
The provided token has expired. Request signature expired at: 2024-09-27T05:46:37+00:00

Ah i'll look into the coverage token issue tomorrow!

Ah i'll look into the coverage token issue tomorrow!

Must have been some weird timing race -- a retry succeeded immediately.

my preference though is that we wire it up in this PR otherwise it's just dead code until that PR lands and we know priorities change and such. But I don't have a strong enough opinion to hold up.

I started down that path, but it's a big enough change of its own (and needing tests of its own) that I ended up swinging the other way. All the actual parquet reader logic has been split into a separate PR https://github.com/delta-incubator/delta-kernel-rs/pull/362, and this PR is now completely self-contained and tested. We can keep iterating on the other PR while this one merges.

re

Those are some impressive tests I have to say.
and
wow that's quite a test suite :)

I know from past bad experience that this is NOT fun stuff to debug. Better to test it near-exhaustively up front and hopefully save some of that pain later.


LifecycleError on shutdown

Trinity version: x.x.x
OS: osx/linux/win
Python version (output of python --version):
Environment (output of pip freeze):

What is wrong?
Left in a bit of context, but the main problem starts with Task exception was never retrieved:
Task <coroutine object BaseService.run at 0x7faf442a8468> finished unexpectedly: BrokenPipeError(32, 'Broken pipe')

sys:1: ResourceWarning: unclosed <socket.socket fd=14, family=AddressFamily.AF_INET, type=2050, proto=0, laddr=('<IP_ADDRESS>', 30303)>

Task exception was never retrieved
future: <Task finished coro=<AsyncioManager.run() done, defined at /home/jcarver/code/trinity/venv/lib/python3.6/site-packages/async_service/asyncio.py:181> exception=LifecycleError('Should have already been completed',)>
Traceback (most recent call last):
  File "/home/jcarver/code/trinity/venv/lib/python3.6/site-packages/async_service/asyncio.py", line 205, in run
    await self._wait_all_tasks_done()
  File "/home/jcarver/code/trinity/venv/lib/python3.6/site-packages/async_generator/_util.py", line 53, in __aexit__
    await self._agen.athrow(type, value, traceback)
  File "/home/jcarver/code/trinity/venv/lib/python3.6/site-packages/async_service/asyncio.py", line 344, in cleanup_tasks
    await task
  File "/home/jcarver/code/trinity/venv/lib/python3.6/site-packages/async_service/asyncio.py", line 142, in _handle_cancelled
    raise LifecycleError("Should have already been completed")
async_service.exceptions.LifecycleError: Should have already been completed

How can it be fixed
:man_shrugging:

Well, with just that traceback it'd be nearly impossible to track this down. If it happens again, please include the debug logs. Closing for now as I haven't seen it lately


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit c236bc2:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit c236bc2:
:clock10: Full build: the average full build time is 6 min(s) 5 sec(s), this is based on the last 491 build(s) for this repository.

Docs Build status updates of commit c236bc2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Panic with invalid SLURM file

I did some testing and found that goRTR either panics or has undesirable behavior if invalid data is provided.  Maybe do some sanity checking before accepting data?
When an invalid prefix (v4 or v6, either the address portion or mask portion) is provided in the prefix assertion section, goRTR panics with:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x6af31e]

goroutine 1 [running]:
github.com/cloudflare/gortr/prefixfile.(*SlurmLocallyAddedAssertions).AssertROAs(0xc00014a460, 0xc009b72000, 0x24de6, 0x32a16)
        /home/agallo/go/src/github.com/cloudflare/gortr/prefixfile/slurm.go:138 +0x12e
github.com/cloudflare/gortr/prefixfile.(*SlurmConfig).AssertROAs(...)
        /home/agallo/go/src/github.com/cloudflare/gortr/prefixfile/slurm.go:154
main.(*state).updateFile(0xc0000c0000, 0x7ffc1078324d, 0x21, 0x0, 0x0)
        /home/agallo/go/src/github.com/cloudflare/gortr/cmd/gortr/gortr.go:403 +0xdba
main.(*state).routineUpdate(0xc0000c0000, 0x7ffc1078324d, 0x21, 0x258, 0x7ffc10783296, 0x24)
        /home/agallo/go/src/github.com/cloudflare/gortr/cmd/gortr/gortr.go:507 +0x2c0
main.main()
        /home/agallo/go/src/github.com/cloudflare/gortr/cmd/gortr/gortr.go:861 +0x666

example entry used to cause this:
           {
             "asn": 65039,
             "prefix": "<IP_ADDRESS>/355",
             "comment": "I trust the TESTNET-2"
           },

If an invalid ASN is provided, there is no panic, this message is logged:
ERRO[0002] Slurm: json: cannot unmarshal number<PHONE_NUMBER> into Go struct field SlurmPrefixAssertion.LocallyAddedAssertions.PrefixAssertions.ASN of type uint32

And goRTR ignores all entries in the Prefix Assertion section
code used to generate this:
           {
             "asn":<PHONE_NUMBER>,
             "prefix": "<IP_ADDRESS>/24",
             "comment": "I trust the TESTNET-2"
           },

For the local assertions, things got a bit worse-
An invalid address specification, such as
          {
             "prefix": "<IP_ADDRESS>/322",
             "comment": "local something"
           },

results in goRTR filtering everything:
INFO[1204] Slurm filtering: 0 kept, 151101 removed, 2 asserted
INFO[1204] New update (2 uniques, 2 total prefixes). 0 bytes. Updating sha256 hash 06580ab7a3b1872323ef1f513acdd402e901de75f6c13304101bbb37b9c66408 -> b56168b0fac51993de909cfaf6c1c294a76513bd64649fd45e6a9b4ee2624f00
INFO[1206] Updated added, new serial 1

All entries from the upstream validator (I'm using octoRPKI in this test) are filtered.  I confirmed  that only 2 prefixes made it to the router I was testing with.
Maybe provide some sanity checking for the input via SLURM?
Thank you.

Will fix. Thank you for reporting

I'd be happy to test.  Just let me know

I merged the change on master: could you git pull and go build inside cmd/gortr?

I don't see any more panics.  Thanks for the quick fix!


Only set persistent | coherent map flags when we have glBufferStorage

Also disables coherent memory types when glBufferStorage is not available
Fixes #issue
PR checklist:

[x] make succeeds (on *nix)
[x] make reftests succeeds
[x] tested examples with the following backends: gl
[ ] rustfmt run on changed code

This makes OpenGL <4.4 platforms with mapping somewhat less "capable" than those without mapping at all, as emulated mapping does emulate persistent mapping.


LifecycleAwareSessionManager doesn't differentiate between failed token renewals and intermittent network exceptions

The LifecycleAwareSessionManager.renewToken() method invokes the LifecycleAwareSessionManager.doRenew(LifecycleAwareSessionManager.TokenWrapper) method inside of a try block and only catches instances of the RuntimeException class.  If the execution enters into the catch block, the exception is logged and no further attempts are made to renew the token.  In order for this code to be reliable, the Vault server cannot afford any downtime at all, because any network hiccup that causes an exception like the following for example:
Cannot renew token; nested exception is org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://_my_vault_server_/v1/auth/token/renew-self": Connection reset; nested exception is javax.net.ssl.SSLException: Connection reset

It seems to me that until the Vault server responded with an HTTP 403 error, there's no harm to continue scheduling renewal attempts until the token is known (by the spring-vault code) to expire.

Since version 2.2, you can configure a LeaseStrategy. dropOnError is the default so you can customize the behavior for your case.

Thank you for the prompt response.  I'm new to this code base and hadn't explored what the LeaseStrategy could offer.  However, I don't think that using an alternate LeaseStrategy by itself would resolve the issue.  It would simply control whether the line https://github.com/spring-projects/spring-vault/blob/712d8ec0b667684c5f4b325c1cd7cae2919cabf4/spring-vault-core/src/main/java/org/springframework/vault/authentication/LifecycleAwareSessionManager.java#L213 gets called or not.
The renewToken method still returns false unconditionally line 224, which then breaks the chain in the scheduleRenewal() method https://github.com/spring-projects/spring-vault/blob/712d8ec0b667684c5f4b325c1cd7cae2919cabf4/spring-vault-core/src/main/java/org/springframework/vault/authentication/LifecycleAwareSessionManager.java#L341. It seems like if the returned value of getLeaseStrategy().shouldDrop(exception) could be used to also control the returned value of the renewToken function, then I could see this working quite well.

It's been nearly 2 months since I've provided more feedback and yet that label is still attached to this issue.  Is there some additional information that I can provide?

I updated the ticket state. I hadn't the time to look into details yet.

@marcboudreau asking you this question since it looks like you've studied the code. Isn't it true that if LeaseStrategy. dropOnError is true, then the token will be set to empty, causing the next request to initiate a new login request?
@mp911de feel free to shed some light on this as well?
In my case, I'd be OK if clearing the token forces the next vault request to first create a new token.

@turaleck in some cases that would be fine.  I'm thinking if using the github or kubernetes authentication method, where there is no explicit limit on the lifetime of the tokens used to complete the authentication.  However, with authentication methods such as approle, the secret_id has a TTL, which limits its lifetime.  There's also the possibility that a maximum number of uses was configured for the secret_id as well.
In our case, we are creating the Vault tokens as part of our deployment pipeline and setting the VAULT_TOKEN environment variable accordingly and the vault.token property is set to token.
We do have one of our senior developers, exploring alternatives this week, and in the event that we find something, we will share it.

We now control the renewal by considering the outcome of LeaseStrategy to retain the token and attempt a renewal later on.

Currently, we are using spring vault library and would like to use LeaseStrategy to retain the lease in case of an error. Is there any sample on how to do that ?


Feature/region agora vai

What's the purpose of this pull request?
Adds regionalization.
This PR represents the code that has already been merged on next.
Tests incoming.
How it works?
Tell us the role of the new feature, or component, in its context.
How to test it?
https://sfj-8d671be--carrefourbrfood.vtex.app/
Set the CEP to "01309-010"
Search for "ovo de páscoa"
If product availability hasn't changed much, it should look like this:

Change the CEP to "22250-040".
The products should look like this:

Click on the first one. The product should be available:

Change the CEP back to "01309-010". The product should be unavailable:

References
Spread the knowledge: is there any content you used to create this PR that is worth sharing?
Extra tip: adding references to related issues or mentioning people important to this PR may be good for the documentation and reviewing process

Exist a store using this region provider that i can test?

I have mixed feelings about this PR.
Correct if I'm wrong, but what I got from this PR is that if a user is in a different region than the pre-rendered version of a category page, the user will first see the pre-rendered version first, then JS will load, and then all the products will shuffle on their screen. Am I right ?  If so I'm not happy on merging this PR

@tlgimenes it is not an ideal long term solution, but it is what was possible to do on the current time constraints. moreover, for client side navigation, it shouldn't be a problem.
the experience can be improved afterwards

@tlgimenes the only practical issue, as far as I know, is for the specific case when a user, who already has their region set, comes from an external source to a pre-rendered category page, that has different products for his specific region.
this can be fixed later

GUYS, THIS IS A SERIOUS PROBLEM !! THE PR WASNT APPROVED YET, THERE ARE LOTS OF LITTLE THINGS TO IMPROVE! I'M TRYING TO MAKE A SERIOUS WORK HERE ! THIS PROJECT MUST HAVE A MUCH HIGHER QUALITY THAN WE HAVE IN STORE FRAMEWORK. HAVING A PAGE THAT "SAMBAS" IS NOT ACCEPTABLE !

@tlgimenes The current limitations of this feature, considering the time constraints, were previously discussed and agreed upon, and that the features that were in the next branch would be merged into master in their current states was also agreed upon.
Also, this PR was approved by @klzns.
Moreover, the only situation the page shifts is a very specific one, mentioned above, that will only affect one store--the one that prompted the need for this feature, and it can be fixed if prioritised.
Minor code nitpicks can also be fixed if prioritised.
Not having this feature is a no-go for the client.


Implement Settings Sections and Pages

Compare to:

Related to: https://github.com/loklak/loklak_webclient/issues/227

As we see the section has been set up. So, well-done! Thank you. The settings page itself should now get implemented in M3.


Add macOS support.

Already works.  Already been using it.  Just needs to be added to the podspec.

Ah, looks like because of updates with UIImage/NSImage you also need the changes here:
You could just #ifdef a little in DataCache.swift and support macOS though.

But you have changed the code to Cocoa and NSImage, it won't work on iOS anymore, will it?

Yeah, it won't like that.  That's just for me on macOS.  You can easily support both though via wrapping my code and using:
#if os(OSX)
    import Cocoa
#elseif os(iOS)
    import UIKit
#endif

This supports macOS but doesn't support iOS. I will close it.


Allow variants of HeaderPattern for pre-canned Apache 2.0 license

Allow variants of HeaderPattern for pre-canned Apache 2.0 license

Nice!


Latest changes (0.5.0) break the S3BotoStorage's use of location

I use the follow code so that I could set the prefix of the location to be the same as the one on the local directory:
from django.conf import settings
from storages.backends.s3boto import S3BotoStorage

class StaticStorage(S3BotoStorage):
    location = settings.STATICFILES_LOCATION
    def path(self, name):
        return self.url(name)

class MediaStorage(S3BotoStorage):
    location = settings.MEDIAFILES_LOCATION
    def path(self, name):
        return self.url(name)
~

Prior to 0.5.0, the location will only affect the result directory on s3, but now it tries to look for the static files while taking this variable into account.
For example. If STATICFILES_LOCATION = "static"
In the past, the search path would have been "/static/js/webpack.js"
Now it is "/static/static/js/webpack.js"
this variable location should affect where Collectfast is looking for files. This happens not only to the files under /static but for other static files, such as admin related things. There is an extra "/static" in the path.
This was reproduced in 0.5.1 too

This should have been fixed in 0.5.1. I can reproduce this in 0.5.0 using AWS_LOCATION = "/static" but not in 0.5.0. See https://github.com/antonagestam/collectfast/pull/90
Is there a reason you're overriding the path method?
Btw, I recommend upgrading to boto3 and using the S3Boto3Storage.

Closing this until further information is supplied.


Major updates on Swift for TensorFlow revival

With no chance in sight for Google to start work on S4TF again, development will continue on this fork. Major announcements about the resurrection effort will be posted here, such as the beta stages of Metal and DirectML acceleration.

CC: a few people paying attention to https://github.com/pytorch/pytorch/issues/47702 have expressed interest in the resurrection of S4TF. This comment will automatically create a link in the issue tracer.

For starters, there is a spreadsheet of which S4TF ops are compatible with which backend frameworks. Some image processing and linear algebra ops may be dropped from Swift for TensorFlow since they are XLA-specific and seem rarely used. DirectML decided not to support may of those ops, citing them as domain-specific.

Most development will happen in a private repository, with major features only being pushed here once they're fully completed. This is the same approach PyTorch is taking, so I won't have the benefit of being 100% open-source.

You can also expect the S4TF tutorials listed on Swift-Colab to be patched and redirected here.


Supports test for PPC

As per #562 , here is the state of PPC support:

minimal version is POWERPC8 with VSX enabled
all targets compile
Failure happens here probably due to errors in BE/LE handling :

unit.real.core.hi
unit.real.core.lo
unit.real.core.lohi

Ok - so ppc8 little endian, ppc9 we will add later?


Extending the default store for all services

Hi,
I am trying to add a few properties to the store of all services. This includes some state, getters, mutations etc.
How exactly are we supposed to do this?
In my setup, I just created a global store object like -
const mycustomstore = {
    state: { newProperty: 1 },
    getters: { getNewProperty(state) { return state.newProperty },
    ....
}

which I am then passing to the setup feathers-vuex call
const {
  makeServicePlugin,
  makeAuthPlugin,
  BaseModel,
  models,
  clients,
  FeathersVuex
} = feathersVuex(feathersClient, {
  serverAlias: 'newAPI',
  idField: '_id',
  skipRequestIfExists: true,
  ...mycustomstore
})

This seemed to do the job for the time being, but I ran into the issue where when I create custom store properties inside the individual service - It overrides the global store addons.
After some digging, I found that the issue was in how the makeServicePlugin handles the options.
return function makeServicePlugin(config) {
    const options = Object.assign({}, defaults, globalOptions, config)
    ....

So coming to the real question - is there a reason to not merge the options?
Something like -
return function makeServicePlugin(config) {
    const options = lodash.merge({}, defaults, globalOptions, config)
    ....

If not, I can just create a wrapper that does (something like a customMakeServicePlugin, similar to the customBaseModel).
Is there something that I might be missing here or is there a different recommended way of achieving this use case [global custom store to all services + service-specific store]?
Thanks!

src/store/defaults.js
export const state = {
  attr1: true,
  attr2: true
}
export const getters = {}
export const mutations = {}
export const actions = {}

src/store/services/service-one.js
import { state, getters, mutations, actions } from '../defaults.js`

makeServicePlugin({
  state: {
    ...state,
    customAttr1: true
  },
  getters: {
    ...getters,
    customGetter(){}
  },
  mutations: {
    ...mutations,
    customMutation(){}
  }
  actions: {
    ...actions,
    customAction(){}
  }
})

Closing, since I think the above is the best solution for this.  Feel free to comment, reopen if required.


Upgrade cypress 11.0.0 devDependencies in ui

Description
https://docs.cypress.io/guides/references/changelog#11-0-1

Fixed an 11.0.0 regression that caused enabling experimentalSessionAndOrigin to throw a webpack error.

Fixed an 11.0.0 regression where using custom reporters would cause Cypress to throw a 'Cannot find module' error.

https://docs.cypress.io/guides/references/changelog#11-0-0

Incorporated V8 snapshots into the build process of the Electron binary to improve startup time and reduce the time to download and unzip the binary during installation.

Cypress now correctly handles CSVs and other non-html MIME types.

Checklist

[ ] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed

/test gke-postgres-ui-e2e-tests
/test gke-ui-e2e-tests

/test gke-postgres-ui-e2e-tests
/test gke-ui-e2e-tests

/test gke-postgres-ui-e2e-tests


Create Post “welding”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
f5b7b937fd7ec0e5aca148776c61ac4eb1a7b58a

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/654d877da5cffc0009b00186


A11y improvements.

Provide a skip-to-content link at the top of the page.
Change the behavior of the admin toolbox shortcuts dropdown.

Please let me know if there are any questions. I'm happy to provide screenshots / screencasts and additional explanations (either in this pull request comment thread or as code comments).

I assumed you've verified the shortcut menu still works and looks the same.


eq 404 Min Value Validation

What is the context of this PR?
Implements MinValue validation on numeric answers
How to review

Run tests
Ensure feature works as per https://trello.com/c/PfYRU46S/404-validation-min-value-front-end-changes

 Validation - Min value front end changes

@hamishtaplin Why have we co-located withUpdateAnswerValidation and withToggleAnswerValidation in the Validation folder? The current pattern is to locate them within enhancers