Release source code for NetNewsWire 3.3.2 as a branch

I have been a paid NetNewsWire 3.3.2 user for several years and I love it. I prefer its classic UI and I wasn't happy with the direction Black Pixel was taking the app. I would like to continue using 3.3.2, but there are a few showstoppers. The most critical issue is support for feeds that use SSL. Of course, I'm assuming Black Pixel transferred rights to the 3.3.2 source code to the author. That  did happen, right?

@brentsimmons Thanks for making the NetNewsWireLite repo public. If you could use some help with either 3.3.2 or 4.0, I'd love to contribute.

Well, it looks like this isn't going to happen, so I'll share my hacky workaround here if you want it: https://github.com/tungol/flask-proxy
That's a quick flask application I'm using to let NNW 3 fetch a local URL over HTTP that returns the contents of a HTTPS URL from elsewhere.

Thanks much! I suspect I've been missing out on many posts due to the SSL bug.  I still prefer the classic UI in NNW 3, as opposed to the "modern" style influenced by iOS. I expect to switch over to NNW Lite, assuming it also offers the classic UI as an option.

On Sep 5, 2018, at 11:16 PM, tungol<EMAIL_ADDRESS>wrote:
Well, it looks like this isn't going to happen, so I'll share my hacky workaround here if you want it: https://github.com/tungol/flask-proxy
That's a quick flask application I'm using to let NNW 3 fetch a local URL over HTTP that returns the contents of a HTTPS URL from elsewhere.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Device Proxy

Migration of proxy device into the new devices interface.

I suspect this needs rebasing now :)

@stgraber the c.restartProxyDevices() function is already called in the correct places after a container is started. By updating this function to use the new device package implementation, the tests are all passing OK. I remember we discussed that the device proxy might need to use a a hook to start after the container has started, but this seems to be unnecessary. Is this OK?

@stgraber this is ready for review now.

@stgraber I made some more tweaks this morning to container_lxc.go to remove more unused code and to remove more of the device specific if statements.

@tomponline can you send a followup branch which updates doc/containers.md to replace container with guest as valid value for bind?

@stgraber will do thanks

@stgraber  https://github.com/lxc/lxd/pull/6042


License?

Can you please provide a license for use of Handesk?  Or have I missed it?

It is MIT so you don’t need anything
Jordi Puigdellívol
El 5 de marzo de 2018 a las 11:21:40, Brian Merritt (
<EMAIL_ADDRESS>escribió:
Can you please provide a license for use of Handesk? Or have I missed it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BadChoice/handesk/issues/104, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFuzAZnFZZvEJFT19_QCo-QcErqZcCyks5tbRGygaJpZM4ScCh8
.

Where please does it say that?  Repos typically have a license file or at least license in the readme.

You are right, there is not licencse file there,
I’m gonna add it
Feel free to submit a PR with updating the readme with the licencse text:
License
The Laravel framework is open-sourced software licensed under the MIT
license https://opensource.org/licenses/MIT.
Jordi Puigdellívol
El 5 de marzo de 2018 a las 11:48:02, Brian Merritt (
<EMAIL_ADDRESS>escribió:
Where please does it say that? Repos typically have a license file or at
least license in the readme.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BadChoice/handesk/issues/104#issuecomment-370381029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFuzP3_SeNlbDecmmHIJqw0L7IsaKL-ks5tbRfhgaJpZM4ScCh8
.


Sample Repository Link Missing?

Description
The Description link in the main repo links to this Documentation; however its Samples on GitHub just dumps you to the OfficeDev organization and not an actual samples on how to use the Open XML SDK...
Can a proper link be provided to the repo containing samples?  Especially UWP ones.
Thanks

I'm not sure where that's supposed to go - maybe @tomjebo does. As for samples, you can look at the tests to see how to do some of the things. If you encounter any issues with UWP, let us know - we don't currently have test coverage for .NET Native, but have made best efforts to support it.

@michael-hawker I will inquire about that link (Samples on Github) to find out if it was intended to point somewhere else.

@michael-hawker just in case you haven't seen it before, there is a lot of code sample and other content on  openxmldeveloper.org.

@tomjebo they have a big notice at the top saying it's going away.  Plus it's not really organized to easily find samples.  Searching for 'uwp' for instance brings up nothing.

Docs has changed. Not sure if there's a sample repo. Happy to link to one from the README if someone has one.


[3.0] Fixes for generic ObjC classes conforming to Swift protocols.

Fix a SILGen and IRGen bug that caused crashes and linker errors when ObjC generic classes conformed to Swift protocols. rdar://problem/27869089

@swift-ci Please test OS X


Craftable nuke real

About the PR

Added Uranium-235, Uranium-238, and Uranium-234
These can be found in Uranium mats. Uranium mats have a VERY small amount of 234, slightly more 235 and mostly 238
Enriched uranium can be made with 55 Uranium-235, 10 Uranium-234, and 35 Fluorine
Most pre-existing recipes using uranium will be changed to use Uranium-238
As an irl chemistry enjoyer this is realistic and cool and adds more variety to rare chems and we haven't even gotten to the best part yet
CRAFTABLE NUKE!!!!
WIP (vaguely similar to how a real nuke works)
Build the base from 15 wood, then 20 steel, then a makeshift shotgun, then a uranium shotgun shell, then a puck of enriched uranium (recipe found above, highly radioactive btw), then a pipe, then 30 steel.
I'm not sure whether to make this detonateable, prolly not. It sells for 50k though!! Maybe make it so it makes a big explosion if you explode it with c4 or something???
Why / Balance

Fun for chemistry and cargo and everybody plus it encourages cargo to get uranium which they NEVER DO.
I plan on adjusting how much of each isotope uranium mats give
as of now it's:
235- 1u per mat, used for enriched uranium
238- 8.5u per mat, used in chem recipes
234- 0.5u per mat, used in enriched uranium, deals 5 rad per unit
i should lower 234's damage but still keep it up and also maybe lower the radioactivity of enriched uranium because it's pretty easy to use for murder rn
https://github.com/Verbalase/Goob-Station/assets/135462166/02c0e430-1836-481b-9ae1-60b39f2d9402
Technical details

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

add reagents to demon core (you are immediatly incinerated upon grinding it)

chlorine + flourine + water + potassium?

chlorine + flourine + water + potassium?

that is not very sciency


How would one model an "auth-capture" scenario?

I'm exploring sequence and trying to apply it to a problem where an account may "promise" to pay up to X, and then end up paying Y (where typically Y < X). So if I start with 100 in my ledger, and promise 50, my balance is still 100 from one perspective, but I only have 50 left to promise. Then as that promise is resolved as 30 instead of 50, my balance is 70, and I have 70 left to promise.
Would this be best as two separate ledgers? One ledger with metadata distinguishing promises from movements (but balance computation becomes hard)?
Thanks!

AFAIK this is more of an accounting problem. You'd represent this with multiple accounts in an accrual accounting manner. So perhaps something like:
Starting state
Bank Account: 100
Funds Available: 100
Auth
Funds Available: -50
"I promise to pay" Account: +50
Capture
Bank Account: -30
"Paid" Account: +30
"I promise to pay" Account: -50
Funds Available: +30

As @sandyscoffable mentioned, I wouldn't use separate ledgers; just create intermediate accounts for any money movement/state you need. This is why it is super important to have a ledger that has a simple API, doing this type of thing should be straightforward in a good ledger implementation.


Invoke constructor of a Class with arguments?

Is there a way to invoke a constructor of a Class with arguments, and get that new Class instance back?

Solution


Usage Questions

When I try to checkout in the sandbox with a German address, it complains that the shop does not deliver there - where do I need to adjust that?
Where can I find the names of the config options usable in https://github.com/solidusio-contrib/solidus_paypal_commerce_platform#i-already-have-api-credentials - as I can't use credentials from the code and the visual form at the same time.

Full Issue:

```sh
Started GET "/solidus_paypal_commerce_platform/shipping_rates?order_id=R977809399ℴ_token=[FILTERED]&address%5Bcity%5D=Berlin&address%5Bstate%5D=&address%5Bcountry_code%5D=DE&address%5Bpostal_code%5D=10117" for <IP_ADDRESS> at 2022-09-29 20:29:49 +0200
Processing by SolidusPaypalCommercePlatform::ShippingRatesController#simulate_shipping_rates as */*
  Parameters: {"order_id"=>"R977809399", "order_token"=>"[FILTERED]", "address"=>{"city"=>"Berlin", "state"=>"", "country_code"=>"DE", "postal_code"=>"10117"}}
  Spree::User Load (0.1ms)  SELECT "spree_users".* FROM "spree_users" WHERE "spree_users"."deleted_at" IS NULL AND "spree_users"."spree_api_key" = ? LIMIT ?  [["spree_api_key", "undefined"], ["LIMIT", 1]]
  Spree::Order Load (0.1ms)  SELECT "spree_orders".* FROM "spree_orders" WHERE "spree_orders"."number" = ? LIMIT ?  [["number", "R977809399"], ["LIMIT", 1]]
  Spree::User Load (0.1ms)  SELECT "spree_users".* FROM "spree_users" WHERE "spree_users"."deleted_at" IS NULL AND "spree_users"."id" = ? LIMIT ?  [["id", 3], ["LIMIT", 1]]
  CACHE Spree::Order Load (0.0ms)  SELECT "spree_orders".* FROM "spree_orders" WHERE "spree_orders"."number" = ? LIMIT ?  [["number", "R977809399"], ["LIMIT", 1]]
  CACHE Spree::User Load (0.0ms)  SELECT "spree_users".* FROM "spree_users" WHERE "spree_users"."deleted_at" IS NULL AND "spree_users"."id" = ? LIMIT ?  [["id", 3], ["LIMIT", 1]]
  TRANSACTION (0.0ms)  begin transaction
  Spree::Country Load (0.1ms)  SELECT "spree_countries".* FROM "spree_countries" WHERE "spree_countries"."iso" = ? LIMIT ?  [["iso", "DE"], ["LIMIT", 1]]
  Spree::State Load (0.1ms)  SELECT "spree_states".* FROM "spree_states" WHERE "spree_states"."country_id" = ? AND "spree_states"."abbr" = ? ORDER BY "spree_states"."name" ASC LIMIT ?  [["country_id", 57], ["abbr", ""], ["LIMIT", 1]]
  Spree::State Load (0.1ms)  SELECT "spree_states".* FROM "spree_states" WHERE "spree_states"."country_id" = ? AND "spree_states"."name" = ? ORDER BY "spree_states"."name" ASC LIMIT ?  [["country_id", 57], ["name", ""], ["LIMIT", 1]]
  Spree::Store Load (0.0ms)  SELECT "spree_stores".* FROM "spree_stores" WHERE "spree_stores"."id" = ? LIMIT ?  [["id", 1], ["LIMIT", 1]]
  Spree::Order Exists? (0.1ms)  SELECT 1 AS one FROM "spree_orders" WHERE "spree_orders"."number" = ? AND "spree_orders"."id" != ? LIMIT ?  [["number", "R977809399"], ["id", 10], ["LIMIT", 1]]
  Spree::Adjustment Load (0.0ms)  SELECT "spree_adjustments".* FROM "spree_adjustments" WHERE "spree_adjustments"."order_id" = ? AND "spree_adjustments"."source_type" = ?  [["order_id", 10], ["source_type", "Spree::PromotionAction"]]
  Spree::LineItem Load (0.0ms)  SELECT "spree_line_items".* FROM "spree_line_items" WHERE "spree_line_items"."order_id" = ? ORDER BY "spree_line_items"."created_at" ASC, "spree_line_items"."id" ASC  [["order_id", 10]]
  Spree::Product Load (0.0ms)  SELECT "spree_products".* FROM "spree_products" INNER JOIN "spree_variants" ON "spree_products"."id" = "spree_variants"."product_id" WHERE "spree_variants"."id" = ? LIMIT ?  [["id", 45], ["LIMIT", 1]]
  TRANSACTION (0.0ms)  rollback transaction
Completed 422 Unprocessable Entity in 35ms (Views: 0.2ms | ActiveRecord: 0.8ms | Allocations: 31326)
```
this only happens when I try to checkout with credit card or SEPA, if I use PayPal itself it works

Hi @xeruf 👋

Sorry, I am a bit confused, the PayPal screenshot is showing that the store cannot ship to the Berlin address, but this only happens when I try to checkout with credit card or SEPA, if I use PayPal itself it works sounds like it's fine in PayPal. I am little confused. You'll need to state what countries you support shipping in by Spree::ShippingMethod and possibly zones, you can do this via /admin/shipping_methods.

The preference keys for the PaymentMethod can be found via terminal or code:

SolidusPaypalCommercePlatform::PaymentMethod.first.preferences.keys
=> [:server, :test_mode, :client_id, :client_secret, :paypal_button_color, :paypal_button_size, :paypal_button_shape, :paypal_button_layout, :display_on_cart, :display_on_product_page, :display_credit_messaging, :venmo_standalone, :force_buyer_country]

The following are only the extra ones that come from this PCP PaymentMethod, and doesn't show the standard ones from Solidus:
https://github.com/solidusio/solidus_paypal_commerce_platform/blob/1f862dd0e2c4a3c22d5bb6f93e88d779cad1c845/app/models/solidus_paypal_commerce_platform/payment_method.rb#L6-L16

Thank you!
Let me clarify: When I use this plugin and pay with a paypal account, it processes just fine, but when I use paypal payment without an account through Credit Card or SEPA I get this error.

I have only the defaults configured so far: EU_VAT and NA


Add support for linux? [meson]

I've managed to get this example running on linux using the meson build system without being invasive on the part of the submodules. Is this something that can be added here?
Here's my implementation https://github.com/neutrino2211/WalnutLinuxSanityCheck
The major additions are in the scripts folder

Its so good you provide extensive installation instructions.

@Nonoreve Yeah. Installation instructions for anything linux are complicated, so I just copied the Vulkan instructions word for word.


Reduce the number of restart for tigera-manager

Description
Tigera-manager is restarted by operator in a multi-tenant environment due to the following:

we are picking up kibana certificates instead of elastic and we are setting the annotations to use kibana certificate. At the next reconciliation, this changes. This is happening because external kibana and external elastic have the value and thus the same hash. Certificate manager only keeps one of them, as it stores as a hash for the certificate. We do not need external kibana certificates and we can stop rendering them. (How we store certs for the trusted bundle: https://github.com/tigera/operator/blob/2f071c36038db04ff46aa0de9b0422efe74daff9/pkg/tls/certificatemanagement/certificatebundle.go#L104)

diff tigera-linseed-566bbc65cf-cc-tenant-u45b0nkt tigera-linseed-5db6cd6fcd-cc-tenant-u45b0nkt
7,10c7,9
<     deployment.kubernetes.io/revision: "3"
<     deployment.kubernetes.io/revision-history: "1"
<   creationTimestamp: "2024-09-16T18:39:49Z"
<   generation: 1
---
>     deployment.kubernetes.io/revision: "2"
>   creationTimestamp: "2024-09-16T21:37:18Z"
>   generation: 2
14,15c13,14
<     pod-template-hash: 566bbc65cf
<   name: tigera-linseed-566bbc65cf
---
>     pod-template-hash: 5db6cd6fcd
>   name: tigera-linseed-5db6cd6fcd
24,25c23,24
<   resourceVersion: "696063"
<   uid: ec4c7d2f-60b0-41ed-a6b7-1f79767c3093
---
>   resourceVersion: "696071"
>   uid: feb1aa56-42f0-447d-9ea9-4dc4e9e5d655
27c26
<   replicas: 1
---
>   replicas: 0
31c30
<       pod-template-hash: 566bbc65cf
---
>       pod-template-hash: 5db6cd6fcd
41c40
<         tigera-operator.hash.operator.tigera.io/tigera-secure-es-http-certs-public: ba4e8391ac56eed2f5bf4458d05f25f92d65c672
---
>         tigera-operator.hash.operator.tigera.io/tigera-secure-kb-http-certs-public: ba4e8391ac56eed2f5bf4458d05f25f92d65c672
46c45
<         pod-template-hash: 566bbc65cf
---
>         pod-template-hash: 5db6cd6fcd
249,253c248,249
<   availableReplicas: 1
<   fullyLabeledReplicas: 1
<   observedGeneration: 1
<   readyReplicas: 1
<   replicas: 1
---
>   observedGeneration: 2
>   replicas: 0

diff tigera-secure-es-http-certs-public tigera-secure-kb-http-certs-public
8,9c8,9
<   creationTimestamp: "2024-09-16T16:26:51Z"
<   name: tigera-secure-es-http-certs-public
---
>   creationTimestamp: "2024-09-16T16:26:49Z"
>   name: tigera-secure-kb-http-certs-public
15,18c15,18
<     name: tigera-secure-es-http-certs-public
<     uid: 567c1091-3617-403f-8281-45cdcbf3ee31
<   resourceVersion: "350817"
<   uid: 71a7273f-4e90-4274-91f9-ca18032a015b
---
>     name: tigera-secure-kb-http-certs-public
>     uid: 5ae7df17-f223-40c3-9323-6a9fed331a73
>   resourceVersion: "350753"
>   uid: 3025e0fe-fe33-4483-ade0-305fc3b8b892

voltron routes are configured by different components (cloud rbac, image assurance) and can produce different volume mounts/volumes which causes tigera-manager to create a new replica set.

diff tigera-manager-d68b7cbd4-cc-tenant-cvlocpq8 tigera-manager-5c44d49556-cc-tenant-cvlocpq8 --color
7,10c7,10
<     deployment.kubernetes.io/revision: "29"
<     deployment.kubernetes.io/revision-history: 3,5,7,9,11,13,15,17,19,21,23,25,27
<   creationTimestamp: "2024-09-16T16:50:20Z"
<   generation: 27
---
>     deployment.kubernetes.io/revision: "28"
>     deployment.kubernetes.io/revision-history: 2,6,8,10,12,14,16,18,20,22,24,26
>   creationTimestamp: "2024-09-16T16:37:11Z"
>   generation: 26
14,15c14,15
<     pod-template-hash: d68b7cbd4
<   name: tigera-manager-d68b7cbd4
---
>     pod-template-hash: 5c44d49556
>   name: tigera-manager-5c44d49556
24,25c24,25
<   resourceVersion: "749585"
<   uid: 857c37aa-dddd-41cd-9996-4f13914aca15
---
>   resourceVersion: "749515"
>   uid: 881189f0-5d90-48d2-897c-259856f6ae94
27c27
<   replicas: 1
---
>   replicas: 0
31c31
<       pod-template-hash: d68b7cbd4
---
>       pod-template-hash: 5c44d49556
59c59
<         pod-template-hash: d68b7cbd4
---
>         pod-template-hash: 5c44d49556
305,307d304
<         - mountPath: /config_maps/tigera-image-assurance-api-public-cert
<           name: cm-tigera-image-assurance-api-public-cert
<           readOnly: true
310a308,310
>         - mountPath: /config_maps/tigera-image-assurance-api-public-cert
>           name: cm-tigera-image-assurance-api-public-cert
>           readOnly: true
359,362d358
<           name: tigera-image-assurance-api-public-cert
<         name: cm-tigera-image-assurance-api-public-cert
<       - configMap:
<           defaultMode: 420
366a363,366
>           name: tigera-image-assurance-api-public-cert
>         name: cm-tigera-image-assurance-api-public-cert
>       - configMap:
>           defaultMode: 420
377,381c377,378
<   availableReplicas: 1
<   fullyLabeledReplicas: 1
<   observedGeneration: 27
<   readyReplicas: 1
<   replicas: 1
---
>   observedGeneration: 26
>   replicas: 0

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

This is happening because external kibana and external elastic have the value and thus the same hash. Certificate manager only keeps one of them, as it stores as a hash for the certificate.

I think we should be fixing Certificate manager. It is fine to remove external kibana because it isn't needed in this case but we should go ahead and fix certificate manager to not filter out duplicate hashes.

@tmjd Can we do it in a different PR ? I am not sure why we added that part and if it is actually needed.


Update build-constraints.yaml

Reenabled sync-mht (after checking that it builds without HUnit < 1.3)

Thanks.


feat: debugger related helpers and utils

Proposed Changes

new util for dumping debugger compliant .tok.map file and aggregated sources json (avm.sources) file
new util for dumping simulated transactions object with unique filename prefixed by timestamp, last round and counts of all unique transaction types in a group simulated
tweaking config singleton
adding logic to auto search for .algokit.toml file with default max depth set to 10, user can overwrite this either by directly passing path OR setting an env variable
adding initial documentation (though main bulk should be on extension repo side and associated docs)
unit tests + smoke testing on fresh beaker project instance
adding logic to specify buffer size that dynamically removes old files

@neilcampbell until merged, feel free to also install from this branch to test out extension side of things


Consider adding mbadinst CSR

If omitting features like misaligned memory accesses and certain CSRs is going to be the most common implementation strategy, it may be worth provisioning an optional mbadinst register that holds the instruction word that most recently caused an illegal instruction trap.  This saves several instructions and a likely D$ miss in the emulation path.
A similar template in H/S modes could improve virtualization performance for the same reason.
If the instruction is >XLEN bits, the register would only reflect the LSBs.
(Implementation note: if illegal instructions are detected early & in-order in the pipeline, it's not necessary to pipeline the whole instruction word down; one microarchitectural shadow copy suffices.)

Possible alternative: use mbadaddr for this purpose, since it is redundant with mepc on illegal-instruction traps.

Need to be careful about what shows up in MSBs; simplest thing to do is to zero them.

How precious are these CSRs, really?
The extra real-estate for flip-flops in the core for 32 (or 64 bits) is indeed significant.
However, reserving and allocating the register number is not a significant burden, is it?
Re:

Possible alternative: use mbadaddr for this purpose, since it is redundant with mepc on illegal instruction traps.

I'd suggest making mbadaddr undefined for trapped instructions that do not have an addressing component.
And that mbadinst contain the trapping instruction in the LSB with any MSB undefined.
As an implementation optimization mbadinst is alias with mbadaddr and the instruction be injected into mbadinst if that overall reduces complexity/cost/etc.
I suggest MSB be undefined as it could allow a future extension to, say inject the actual compressed instruction there - or to indicate a fused instruction, etc.. I only foresee this as significant on RV64/RV128.
Further, how is an illegal compressed instruction shown?
Indeed, if an instruction has the low order bit 00,01 or 10 and it is not a valid Compressed Instruction, is it an illegal Compressed instruction, or "just" an illegal instruction.
e.g. is x"00000000" one or two illegal instructions - does it depend upon C extension being implemented?
This does raise the question of how to handle an illegal exception raise by the hart before the remainder of the instruction is read (for example at the end of a cache line).
I would recommend that at least the 4 LSBytes as available to the decoder be written to mbadinst, whether the format would otherwise be 16bit on a Compressed Extension implementation or not, and whether all the instruction had been loaded for the decode yet.
Imposing a further fetch of the remainder of an illegal instruction is too heavy handed.
And in the case of x"FFFFFF..." completely unnecessary.
The trap handler must be able to parse the instruction from LSB forward and detect early illegal formats in the lower 2 bytes. Otherwise, the trap handler will have to read the instruction from memory.
The mbadinst will potentially help with race conditions that have modified the code before the trap handler gets to processing it, likely a very rare occurrence, but without this register it likely will be extremely difficult to identify.

I don't like design that allows badaddr be an alias of badinst, as this doesn't provide any real advantage over just defining a common "bad" CSR that holds the offending bit pattern, and is confusing.
I think you want to make any unwritten upper bits be zero to avoid propagating information between traps, and to avoid explicit masking in some code paths.
I'd expect trap handler to always parse one parcel (2 bytes) a time when C extension supported, so should find trap cause in first two bytes of longer instruction if straddling cache lines, and this will disambiguate 0x00000000 case. I agree don't want to force fetch unit to fetch past first trap, or past one instruction if faulting instruction less than XLEN bits long.
For instructions>XLEN, if handler can't determine what to do from first XLEN bits, will have to refetch from memory - no worse than current scheme.
Alternatlvely, could require multiple CSRs sufficient to hold max instruction bytes.  Even then, a system with hardware supporting up to X-byte instructions might want to emulate system supporting >X-byte instructions, so would still have to read from memory.
Macro-op fusing implementations should behave transparently the same as non-fusing implementations.

Agreed.

The main subtle point here IMO is that M-mode needs to be able to know the number of valid parcels in mbadinst.
This could be done by saying that mbadinst always holds either 0 or a complete instruction, or by using a second CSR to indicate the length.
In the former case hardware and M-mode need to agree on what "a complete instruction" is.  I'd rather not leave that implementation-defined. but §10.3 clearly indicates that implementations are allowed to differ on whether 0x00010001 is 1 instruction or 2.  One option would be to use the figure 1.1 table, but modify it so that the first row says "16-bit if MISA.C is 1, 32-bit otherwise".

Yeah, I think misa.C should disambiguate this for the 16-vs-32 case, and 48-bit+ extensions will similarly be disambiguated by additional bits in misa.

I don't like design that allows badaddr be an alias of badinst, as this doesn't provide any real advantage over just defining a common "bad" CSR that holds the offending bit pattern, and is confusing.
agreed. If we can still redefine CSRs at this juncture - and I assume from your response, we can.
And if we are going to do it, we need to do it in v1.10.
Which means that on an illegal instruction, this register must written; Cleared if the implimentation does not provide any illegal instruction bytes.
In terms of naming is instbad sufficient? As with pseudo-op,  badaddr and badinst could be different names for the same csr address.

I'd expect trap handler to always parse one parcel (2 bytes) a time when C extension supported
Or emulated (even if C extension is not (fully) implemented in hardware).

I think you want to make any unwritten upper bits be zero to avoid propagating information between traps, and to avoid explicit masking in some code paths.

Unwritten bytes of trapped instruction(s)- Agreed for 32/64. Perhaps RV128 could benefit from meta data in the higher byte(s).
I'd like us to reserve them in RV128 for now. This does align with the potential plans for address
The trap handler has to determine if the whole instruction is one which it intends to emulate. In the event that the higher bytes are truly zero in the instruction, the trap handler will have to reread those bytes to ensure they are so in memory. Again, no worse than without the csr.
However, I proposed that as many bytes as are seen by the decoder be written (and minimally Even if the trap parsing could determine a possible reason for invalid opcode in fewer bytes. because many an available to theseen by the

oops. the quotes extended more than I intended.

I don't like design that allows badaddr be an alias of badinst, as this doesn't provide any real advantage over just defining a common "bad" CSR that holds the offending bit pattern, and is confusing.

agreed. If we can still redefine CSRs at this juncture - and I assume from your response, we can.
And if we are going to do it, we need to do it in v1.10.
Which means that on an illegal instruction, this register must written; Cleared if the implimentation does not provide any illegal instruction bytes.
In terms of naming is instbad sufficient? As with pseudo-op, badaddr and badinst could be different names for the same csr address.

I'd expect trap handler to always parse one parcel (2 bytes) a time when C extension supported

Or emulated (even if C extension is not (fully) implemented in hardware).

@aswaterman would it be a pain for 64-bit rocket-ish implementations today to write 0 to mbadinst if (insn & 31) == 31?  I'm assuming we won't have a single "48-bit extension" with a dedicated bit in misa, the 48-bit opcode space will be used by a large number of standard and nonstandard extension?

The main subtle point here IMO is that M-mode needs to be able to know the number of valid parcels in mbadinst.

As I suggested - the zero bytes are sufficient to delimit all the definitively  known bytes of the instruction the decoder has. The high order zero bytes will need to be checked.

This could be done by saying that mbadinst always holds either 0 or a complete instruction, or by using a second CSR to indicate the length.

An additional CSR is overkill for a non-essential helper fucntion.

In the former case hardware and M-mode need to agree on what "a complete instruction" is. I'd rather not leave that implementation-defined. but §10.3 clearly indicates that implementations are allowed to differ on whether 0x00010001 is 1 instruction or 2. One option would be to use the figure 1.1 table, but modify it so that the first row says "16-bit if MISA.C is 1, 32-bit otherwise".

And The MISA.C bit does not help if the M-Mode is intending on emulating the mode on machines that (honestly and transparently) clear C bit because they do not provide the hardware support in the decoder. .

@David-Horner my point is that if you clear the top 16 bits of a valid instruction, say "lui a0, 17", you wind up with a different valid instruction, in this case "lui a0, 1".  CLZ is not sufficient.

And The MISA.C bit does not help if the M-Mode is intending on emulating
ditto for 48 bit opcode emulation. What hardware registers indicate of there support , apparently, can be what every they want if they emulate it.
According to - casinovic

At the first meeting at the last workshop, the consensus was that there was no need/ impossible to distinguish between hardware and software implementations of a feature.

@aswaterman: doesn't misa.C indicate that that the standard C extension is supported, which is slightly different to the question of whether 16-bit instructions are supported. An implementation might use the C opcode space for non-standard 16-bit instructions, but they couldn't advertise misa.C in that case.

@sorear - what I am suggesting is that the CSR are a help, and will not disambiguate all situations.
In the case you suggest, neither opcode is illegal (regardless of the literal value, lui is non likely to trap
So, in the typical case a zero upper half word will have to reread the instruction.
And, for clarity, the granularity should always be 2 bytes provided at a time.
All non-provided be zero'd.
This reduces to the "non-implemented" case that write the register to zero.

Alternatlvely, could require multiple CSRs sufficient to hold max instruction bytes. Even then, a system with hardware supporting up to X-byte instructions might want to emulate system supporting >X-byte instructions, so would still have to read from memory.

It doesn't have to be mandated, but certainly more instrbad CSR could be defined (instrbad2, etc).
And for the instruction decode (illegal trap case), the same convention of high order zero half words  need further checking. The RV128 intension of meta data in the high order bytes of the auxiliary csr (instrbad2) could be implemented with the additional registers in RV32/RV64

Macro-op fusing implementations should behave transparently the same as non-fusing implementations.

Agreed - it should fall back to discrete instructions. But an optimistic decoding  implementation may cause a illegal instruction trap (which is really an unsupported instruction trap, possibly with a further cause in the mcause CSR) and allow the M-mode to handle some fringe cases.
I hope we can also provide support to this model with a clean instrbad design.

@asb IMO, in the event of conflicting non-standard extensions, the M-mode software needs to be aware of them (hence won't need to interrogate misa.C)

I believe the other traps that store an address value in mbadaddr (breakpoint , address-misaligned or access exception) would also substantially benefit from the mbadinstr information.
This means that separate CSR registers is required.
@sorear

or by using a second CSR to indicate the length.

In the general case, the occurrence of high order half-word zero values is low (1 of 65536).
Even so, a convention for WLRL can be used to determine the half words of the faulting instruction  that have been written to the register vs default filler:
CSRRS individual half words that are zeros in the register to ones would set the bits iff the value is not part of the trapped instruction.
This is the classic WLRL that occurs when the "unconstrained" parts of the legal value are changed.
The special case of CSRW of -1 needs to be allowed to set all the bits to differentiate between implementations that do not support the WLRL convention.
If it cannot be determined that this convention is implemented, then fall back to reread of the opcode is required.

Let's not have mission creep here. The goal is a good spec, not a perfect
one.
mbadinst is meant to improve the performance of illegal instruction
emulation--not for any other reason.
On Sat, Mar 4, 2017 at 9:07 AM David-Horner<EMAIL_ADDRESS>wrote:

I believe the other traps that store an address value in mbadaddr
(breakpoint , address-misaligned or access exception) would also
substantially benefit from the mbadinstr information.
This means that separate CSR registers is required.
@sorear https://github.com/sorear
or by using a second CSR to indicate the length.
In the general case, the occurrence of high order half-word zero values is
low (1 of 65536).
Even so, a convention for WLRL can be used to determine the half words of
the faulting instruction that have been written to the register vs default
filler:
CSRRS individual half words that are zeros in the register to ones would
set the bits iff the value is not part of the trapped instruction.
This is the classic WLRL that occurs when the "unconstrained" parts of the
legal value are changed.
The special case of CSRW of -1 needs to be allowed to set all the bits to
differentiate between implementations that do not support the WLRL
convention.
If it cannot be determined that this convention is implemented, then fall
back to reread of the opcode is required.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/issues/12#issuecomment-284165289,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-7wnoJFcfTHlm8zgMe_pRjIFuY57dcks5riZo6gaJpZM4L-WFY
.

I don't think we're going to do the potentially-zero-parcel thing for 32-bit instructions.
If the instruction is 32 bits long, then either (a) the whole instruction is fetched and reported as an illegal instruction, then placed into mbadinst, with bits 32 and above zero-filled, or the (b) an access or misalignment exception occurs, and mbadaddr is written with the address.  Partial fetches of 32-bit instructions never cause illegal instruction traps.  This keeps emulation of standard 16-bit and 32-bit instructions simple (which was the whole point of adding this register in the first place!).
If 16-bit instructions are supported, then either (a) the system supports 16-bit instructions, an illegal instruction trap occurs, and 16 bits are written to misa with the upper bits zero-filled, or (b) the system doesn't support 16-bit instructions, an illegal instruction trap occurs, and 32 bits are written to misa, with bits 32 and above zero-filled; or (c) an access or misalignment exception occurs, and mbadaddr is written with the bad address.
These both keep emulation of 16-bit and 32-bit standard instructions simple, which was the whole point of adding mbadinst!
For >32-bit instructions, here are two options that are both simple to implement and compatible with the above:

Unconditionally zero-fill bits 32 and above.  This has the advantage of being simple to spec, and has similar behavior for RV32 and RV64+.
If the machine supports N-bit instructions, fetch up to N bits and put min(N, XLEN) of those bits into mbadinst.  This is also easy to spec, and easy to use, if there is a way of determining N.  (N can vary with misa.)

@aswaterman

If 16-bit instructions are supported, then either (a) the system supports 16-bit instructions, an illegal instruction trap occurs, and 16 bits are written to misa with the upper bits zero-filled, or (b) the system doesn't support 16-bit instructions, an illegal instruction trap occurs, and 32 bits are written to misa..

I expect mbadinst was intended here.
With the above, If mbadinst is a distinct CSR from mbadaddr, then it should be read-only.
Or are all these registers that could be accessible in lower privilege levels read-write to allow virtualisation?
Are mcause and mbadaddr implicitly readable in lower privilege levels if x-edeleg illegal instruction
is enabled for that level?
Should mbadinst be explicitly added as implicitly accessible in the same situation?
Or should we be adding a mechanism like that for the hardware performance counters?

(I'm still assuming the design that mbadaddr is used for this purpose, possibly with a new name.)
No, mbadaddr is not accessible to less-privileged code.  Supervisor has its own sbadaddr register.  If an exception is delegated to S-mode, and that exception would've written mbadaddr, sbadaddr is written instead.

Going to write this up with mbadbits being the single CSR that contains the offending bit pattern, either address or instruction depending on trap type (and I guess can be used for bad data values in future)  I'm assuming we can alias mbadaddr and mbadinst to this same CSR in the assembler.
I'm also assuming whole instruction is fetched and placed into mbadbits, or bottom XLEN bits if >XLEN bits, with any unused upper bits zeroed.

Writeup pushed.


server.go panic: runtime error: invalid memory address or nil pointer dereference

In server.go in line 255
// the connection is not connected but it's inside the room, we remove it on disconnect but for ANY CASE:
						s.leaveRoom(sid, msg.to)

please change to
// the connection is not connected but it's inside the room, we remove it on disconnect but for ANY CASE:
						sid := connectionIDInsideRoom
						if c != nil {
							sid = c.id
						}
						s.leaveRoom(sid, msg.to)

Why not just ?

if c == nil {
   continue
}


Fixed Russian translation

Fixed 3 strings so they look more Russian

Please pull the latest changes in the repo and update the PR.


Make unit model hashable

Is your feature request related to a problem? Please describe.
Currently, the units model is not hashable although the content should be immutable and, hence, frozen.
But due to the missing Config in the model the __hash__ function is not generated by pydantic.
Describe the solution you'd like
I would like to add the following content to the model:
class Unit(BaseModel):
    ...

    class Config:
        extra = 'ignore'
        allow_population_by_field_name = True
        allow_mutation = False
        frozen = True

Describe alternatives you've considered
Inherit, the Unit model and add a specific Config object. However, this may lead to inconssitency
Additional context
Use case:
I have a list ob sensors that also contains information about the unit.
For mapping measurements to the sepcific sensors I regularly must loop throuth this list. Therefore, caching such lookup can be wuite useful. Caching though requires hashing of the Objects in the list that I qant to operate on.

Hello @tstorek , thanks for the detailed report, it makes sense to me. Can you describe a bit more what do you mean by "caching", and what kind of error you have received while trying to cach? It could be useful to other users, who later come into the same problem. But anyway, it is nich to hear from you! :)

@djs0109 Python supports builtin caching of functions as long as all args are hashable. Using this minimized access time if the function call is identical with a former function call because the function reponse was already caluculated earlier. This is quite useful for filtering etc.


Fixed #24675 --Implemented an option to avoid unnecessary queries to MySQL since MySQL 5.6

https://code.djangoproject.com/ticket/24675#ticket
Since MySQL 5.6 setting MYSQL_AUTO_IS_NULL is unnecessary. Implementing this eliminates one query in every connection resulting in better performance.
http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_sql_auto_is_null
System Variable	Name	sql_auto_is_null
Variable Scope	Global, Session
Dynamic Variable	Yes
Permitted Values	Type	boolean
Default	0

I left a comment on the ticket, did you get notified about it?

Hi @timgraham, I did not. I will take a look to see if I can find another workaround. I will comment on the ticket.

buildbot, add to whitelist.

Also, could you try to add a test as described on the ticket?

Hi Tim. I will do that. I am  travelling right now and I'll do as soon as I am available.

Friendly reminder in case you have a chance to finish this now.

Closing due to inactivity. Please send a new PR when you have time to update it, thanks!

this is still not merged to latest release of django, it has been 9 months. what is the eta on it?

Django 1.10


develop sampling output view

This applies the changes of #32 onto the new base #40 (again, hoping that can be a starting point)
I realize there are some questions about the correctness of the items.
What I would suggest so that we can move forward until we can get the proper tests in place

Hide the controversial columns (N_eff, N_eff/s, R_hat) for the time being
Verify the other columns - that should be pretty straightforward
Put them back in once we have proper tests

That way we can benefit from most of this improved view while we do further dev.
What do you think @WardBrian @jsoules ?

Two thoughts:

Does this actually depend on implement general data model - agnostic starting point for further development #40, or could it be done independently? It seems to me like it could, but I might be missing something

Technically it could, but I'm really hoping we can merge 40 first - it doesn't add features, it simplifies and removes things so that we can be at a base starting point for proposed development. Looking at the files changed, it's true I wouldn't anticipate any conflicts... but I hope we can just merge 40 and then it's not an issue.

Rather than merge ess code we don't want to use, could we just pull the plots tabs into their own PR and not do anything to the summary tab yet?

I can move the ess stuff into a separate PR... But shall we keep the table with the non-controversial columns? That way the ess PR can be pure to that.

I think I spotted a meaningful disagreement between Stan's summary and this table in every column. Some may just be up to different implementation choices for e.g. quantile computation, but I'd like to look into them more.
As for depending on #40, I think it is always better to not have interdependence when it isn't needed. I'd be happy to merge a plots-only based-on-main version of this today, but if it is dependent on another PR that will naturally take more time

I think I spotted a meaningful disagreement between Stan's summary and this table in every column. Some may just be up to different implementation choices for e.g. quantile computation, but I'd like to look into them more.

Okay sounds good... I'll separate all that out.

As for depending on #40, I think it is always better to not have interdependence when it isn't needed. I'd be happy to merge a plots-only based-on-main version of this today, but if it is dependent on another PR that will naturally take more time

I think it's okay to wait. If we end up not merging #40, then I'll make the adjustments at that point.


Substrate storage changes solutions

Now the explorers(such as subscan.io) are often keep a partial state of balances etc. according to Extrinsics. But that is not extensible for implementing domain specific features.

https://github.com/paritytech/substrate/pull/9642


issue https://github.com/cypress-io/cypress/issues/4925

Hi Manas!
not sure how to contact you, sorry for offtop..
issue https://github.com/cypress-io/cypress/issues/4925
when I run in osx
mkdir -p /var/run/dbus && dbus-daemon --config-file=/usr/share/dbus-1/system.conf --print-address

got error
dbus[14375]: Failed to start message bus: Failed to open "/usr/share/dbus-1/system.conf": No such file or directory

are you able to assist?

What are your system details?


Update kotlinx.coroutines to 1.8.0-RC2

Since https://github.com/Kotlin/kotlinx.coroutines/pull/3921, delay(Duration) will be rounded up to the nearest milliescond, instead of rounding down/truncating.
This caused tests to fail that were waiting for 16 milliseconds for a GPS of 60, since the 1000 / 60 = 16 + 2/3 is now being rounded to 17 and not 16.

Cannot auto-update because of conflicts.


Spike: KIC 2.0 - CRD Migration

We need to ensure that v1.x upgrades cleanly to v2.0, particularly when using a helm upgrade.
Acceptance Criteria:

[ ] all v1 CRDs can upgrade to v2 CRDs cleanly (using kubectl apply -f <crd>.yaml)
[ ] integration tests exist in KIC proving the upgrade works for ALL CRDs and protecting against regressions
[ ] legacy integration tests should work properly on the updated CRDs

Possibility: define a new API version with appropriate conversions.

K8S does provide a standard mechanism for indicating how it should conversions between one version and another in https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#webhook-conversion. That requires a new API version and that we write some helper service to handle the actual translation.

K8S does provide a standard mechanism for indicating how it should conversions between one version and another in https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#webhook-conversion. That requires a new API version and that we write some helper service to handle the actual translation.

This makes sense to me, I don't have any qualms with this approach when we spike this.

I would like to bring up the following for discussion:

The change between the "legacy CRDs" and the "Railgun CRDs" is purely technical and not semantic. We're just moving from one way of generating CRDs from schema definitions to another.
We want the change above to be transparent and non-breaking.

That said, I believe that the upgrade to railgun does not deserve a new APIVersion of our manfiests (so we should IMO withdraw from the idea I pitched above about a new API version), and we should strive for:

making the new CRDs a viable in-place replacement for the old CRDs.
KIC 2.0 being drop-in compatible with KIC 1.x manifests

That said, I believe that the upgrade to railgun does not deserve a new APIVersion of our manfiests (so we should IMO withdraw from the idea I pitched above about a new API version), and we should strive for:
* making the new CRDs a viable in-place replacement for the old CRDs.
* KIC 2.0 being drop-in compatible with KIC 1.x manifests

This all sounds good to me, I have no comments just :+1:

A couple of alternative options:

come up with not-supported-resources.yaml (including CRDs, etc), user execute "helm uninstall ..." or  "kubectl delete -f not-supported-resources.yaml" before install latest KIC version.
implement CRD upgrade as part of controller - V1 is expected, v1beta1/v1alpha1 is expired, delete associated resource before upgrading to latest version

Let me know if we have offline discussion about the feasibilities.


Refresh Lodestar User Guide

Is your feature request related to a problem? Please describe.
Documentation page is out of date
Refresh user guide for content and style
Add FAQ / usecases
Add dev guide / ecosystem packages
Add motivation / architecture descriptions / diagrams
Additional context
https://docs.ethermint.zone/

i'm gonna start heading in this general direction

open to suggestions if anyone has anything more specific or different than what is listed above

User guides were updates 2 months ago and are fairly updated


delete config 403

Hi,
I have the same issue. I checked the request from the developer console. I throws this error.
detail: "CSRF Failed: CSRF cookie not set."


v2 progress

This pull request will serve as a progress indicator on work i am doing to bring this gem up to date and move from the now deprecated Vimeo v2 API to v3 (Current)

[x] Clean up and update gem from some use of old conventions
[ ] Implement Vimeo v3 API (This is quite an epic story, so i will break this down in the next few days)
[ ] Update tests to reflect all changes

All feedback is welcome.

Sorry for the delay, here are the stories for the implementation of the Vimeo V3 API

[ ] Decide on design pattern that fits into Vimeos API model
I am getting some ideas from sferik/twitter, but seeing how Vimeo has nested resources in some areas i will need to adjust the design to fit into this. Open to ideas if anyone has any.

[ ] Implement Categories endpoint and functions

[ ] Implement Channels endpoint and functions

[ ] Implement Groups endpoint and functions

[ ] Implement On Demand endpoint and functions

[ ] Implement Tags endpoint and functions

[ ] Implement Users endpoint and functions

[ ] Implement Videos endpoint and functions

I have worked with a few design choices and i think i have come up with a solution that i think will work quite well.
# Create a new Vimeo client with the required access_token to interface with
# Vimeo's API
client = Vimeo::Client.new do |client|
  client.access_token = 'ah'
end

# Vimeo has 7 top resources: Categories, Channels, Groups, Me, On Demand, Tags
# Users, Videos. I am going to make the pluralized form of the resource publically
# avaliable in the client. Each resource will also be class to allow
# access to attrs and to sub functions ie: /categories/#{id}/users.
# A usage example would be as such.

categories  = client.categories # => [Vimeo::Entities::Category]
channels    = client.channels   # => [Vimeo::Entities::Channel]

users = channel.first.users     # => [Vimeo::Entities::User]
users.first.name                # => "My Vimeo Name"

@colby-swandale You are credit to team. I was just looking at rolling my own v3 Vimeo solution - though it'd probably be sufficient for my (narrow) purposes, I'd love to have a more fully-featured option like you're building. :clap:

Hey Guys,
Quick update, i have started the request and response implementation. At the moment i can make a good request and build a category object from its response. Though that was through manual debugging and still yet to write tests to confirm the functionality is working. So a good part almost out of the way but still a long road ahead.
Sorry this progress has been quite slow, i am juggling between life/work but i promise i will keep working on this.
Thanks Guys!
@chrispatterson thanks! appreciated a lot.

Hi everyone,
Anyone keeping an eye on this PR would have noticed that i have not made any commits for quite some time. Don't worry i have not abandoned this project, my only computer died a few weeks back and had to wait for a replacement to arrive. Numerous personal events has also eaten most of the my spare time that i can allocate to this project but i now will start putting some time down again to work on this.
Thanks guys!

@colby-swandale Vimeo integration has moved onto my plan for the next week or so. I'd love to use your work - any chance this will be in shape for use by then, or should I plan on rolling my own for now at least?
I appreciate the work you've been doing, and will probably want to revisit using this regardless whether it's a fit for my immediate needs. Just trying to plan my time allocation. :thumbsup:

@chrispatterson i wouldn't bet on it, the code is fairly unstable right now and i could bring in a breaking change at any point until i release a beta so i would advise you either see if you can use the current version of the this gem or roll a quick implementation yourself. If you need any help let me know.

@colby-swandale After a couple of months of having other issues frontburnered ahead of this, I'm finally looking at vimeo integration.
I'm guessing this is still not ready for production use, so I've taken a pass at a simple vimeo upload, but have kind of run aground. I'm getting an error about bytesize not being defined for a hash, which makes me suspect Faraday isn't using multipart, but when I inspect the connection it appears to be using the Faraday::Request::Multipart builder.
All videos will be uploaded using a single account, and I don't need any management support apart from being able to upload videos and store the resulting vimeo id. My basic module and more details are at https://gist.github.com/chrispatterson/6545e7413d430afa34ed, and any input is much appreciated. (It feels like I'm missing something obvious).
Thanks in advance for the help.

This is going to be my last update as i have run out of steam to put more work into this pull request. We're not using Vimeo any longer at my place of employment and finding time to work on this is becoming increasingly difficult. I am going to close this PR but anyone is welcome to continue working and making improvements if you desire.


No persistent volume is configured

Good morning, I have tried the new deployment, and all went well until “Install GitOps runtime and initiate config-bootstrap process”. That is almost the end of the lab deployment.  At that stage of the deployment, it resulted in two (2) cluster operators not working: I believe that image-registry is not configured to use persistent volume. With the other versions, this issue didn’t happen. Please, see attached document. Please, can you help? Thanks and regards
empty persistentvolumes.pdf
.

I opened in discussion. thanks and regards


[contracts] Introduce immutable variables to WASM contracts

Solidity has the concept of immutable variables, which value can be set once in contract’s constructor and guaranteed to stay unchanged afterwards. OpenZeppelin has recently recommended ink! to introduce this feature too, to provide contract developers with more flexibility in designing and building secure and efficient smart contracts. In this issue we’ll try to think about how we can introduce the similar concept into ink! and Pallet Contracts.
WebAssembly has indeed the similar construct - immutable global. Its initializer lives in the Globals section of the WASM module, and uses a constant initializing expression.
The constructor of WASM contracts in the pallet_contracts is the deploy exported function. This function is called once at the time of contract instantiation on-chain. Contract instantiation is done after the re-instrumentation and uploading the contract WASM blob on-chain, and it in general can be done in a separate (from uploading) extrinsic, when deploying a new contract instance of a code already stored on-chain. This approach allows to save gas and storage deposit for the caller account. Changing the Global section of the module on the step of contract instantiation would require its code altering and re-uploading on chain, implying an additional costs for contract authors.
Another approach could be to use an imported global in the contract module (note: currently importing globals to WASM contracts is forbidden). Pallet contracts could define the global and initialize it in the “env” module during the instantiation of the module to the WASM engine. For that it would need to somehow get the initializing expression from the constructor (deploy exported function of a module, which is to be designed by contract developer in #[ink(constructor)]). We can e.g. expose a host function init_immutable_global to the contracts API for that purpose on the pallet side.
But the core problem here is that we instantiate the module first to the WASM engine, and only after that we call the exported deploy function. My gut feeling it that probably we’d have to use WebAssembly start function for solving this issue, which is by design intended for initializing the state of a module (and is currently forbidden in WASM contracts as well).
@athei  @cmichi @ascjones @HCastano wdyt?

Immutable variables is a programming language feature. It is in the case of solidity and it should be in our case, too. I see no reason to bake this complexity into pallet-contracts. As a rule of thumb: If a feature can be implemented in user space this is where it should be implemented. Adding complexity (and policy) to privileged code should only be done with a very good rationale.
In this case I don't see a bid advantage in moving this logic to pallet-contracts: ink! can solve this problem by flagging certain fields as read only: We remove direct field access for the root storage struct and generate accessor functions (we leave out the setter for read only variables).

I agree with Alex here. Can you move this into the ink! repo and spec it out based on ink!'s perspective instead?

Anything needs to be done other than just use Rust's const ?


Terminal tab title - using cwdFolder

Testing #133549
See the recording below:

cwdFolder appears twice in the title
Terminal title is not maintained on window reload

you have title set to ${cwd} and description, by default, is ${cwd} .
the single tab view will show title - description. so ${cwd} - ${cwd} is expected given the settings you used

@meganrogge, why does the title/description change on reload?

Sorry - did not see that part - will investigate


⚠ TorrentLeech has degraded performance

In f2a9410, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 6946 ms

Resolved: TorrentLeech performance has improved in cc14c48 after 7 minutes.


react/jsx-sort-props breaks the code

Tell us about your environment
"babel-eslint": "^9.0.0",
"eslint": "5.6.0",
"eslint-plugin-react": "^7.11.1"

ESLint Version: 9.0.0
Node Version: 10.6.0
npm Version: -
yarn Version: 1.9.4

What parser (default, Babel-ESLint, etc.) are you using?
Babel-ESLint
Please show your full configuration:
I created a repo to reproduce the bug: https://github.com/davesnx/eslint-bug-react-sort-props

Configuration

module.exports = {
  parser: 'babel-eslint',
  plugins: ['react'],
  rules: {
    'react/jsx-sort-props': 1
  }
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

import React, { Component } from 'react'
import PropTypes from 'prop-types'

const PictureChoice = () => {
  return (
    <List
      className={className}
      onStageAnswer={onStageAnswer}
      onCommitAnswer={onCommitAnswer}
      isFocused={isFocused}
      direction={direction}
      allowMultipleSelection={allowMultipleSelection}
      measureLongestChildNode={measureLongestChildNode}
      layoutItemsSize={layoutItemsSize}
      handleAppScroll={handleAppScroll}
      isActive={isActive}
      resetSelection={resetSelection}
      onKeyboardChoiceHovered={onKeyboardChoiceHovered}
      keyboardShortcutType
    />
  )
}

export default PictureChoice

npx eslint . --fix

What did you expect to happen?
So theorically the rule should re-order my props, in the worst case scenario, not sort them. But actually is breaking them. It's a weird output:
import React, { Component } from 'react'
import PropTypes from 'prop-types'

const PictureChoice = () => {
  return (
    <List
      allowMultipleSelection={allowMultipleSelection}
      className={className}
      direction={direction}
      isFocused=handleAppScroll={handleAppScroll}ection=isActive={isActive}owMultiplisFocused={isFocused}ardShortcutType
      layoutItemsSize={layoutItemsSl
      layoutItemsSize={layoutItemsSize}
      handleAppScroll={handleAppScroll}
      isActive={isActive}
      resetSelection={resetSelection}
      onKeyboardChoiceHovered={onKeyboardChoiceHovered}
      keyboardShortcutType
    />
  )
}

export default PictureChoice

It's actually trying to sort in a weird way, and it's not consistent.
Happens with a boolean props as well

      isFocused=

      handleAppScroll={handleAppScroll}

      ection=

      isActive={isActive}

      owMultiplisFocused={isFocused}

      ardShortcutType
      layoutItemsSize={layoutItemsSl

Does this only happen with babel-eslint?

I think this is a duplicate of #1922. This rule doesn’t make an attempt of handling multiline props properly :/

In that case we should entirely disable the autofixer, pending making it behave properly.

same happens for me with autofixer


[Bug] [Yarn Queue] Config of Queue Doesn't Work.

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I have set up queues (non-default queues) for both tenants and users according to similar settings, but whether the user runs tasks or other users run tasks, the final queue used on yarn is still default.
Besides, the version is 3.0.
The queue name on dolphinscheduler is the same as the queue name on yarn.
What you expected to happen
Tenant queue settings and user queue settings take effect.
How to reproduce

I created a test user, mounted it under the mask tenant, set the test user as the flink queue, the mask tenant as the flink queue, and used the shell node to perform the hive -e "sql" task, but the task was run in the default queue .
Anything else
No response
Version
3.0.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

After testing: found that this problem exists in 3.1.x  too

The queue does not take effect in the shell task node. It's not a bug.
However, I think we can provide the queue variable in the shell node for users to use.

I don't think so. Since there is a queue configuration, it can definitely be used, otherwise the queue is of little significance.

Thanks for the reply, will this feature be fixed in the near future?

Thanks for the reply, will this feature be fixed in the near future?
This needs to be reproduced, and then the problem can be solved in a targeted manner.


chore: update node version to 18 SOFIE-2367

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Dependency update

What is the new behavior (if this is a feature change)?

Runs the gateways on node 18. This is in preparation for the node16 end of life in October.
Gateways outside of the mono-repo are not affected, but we will likely eventually mark the integration libraries are not supported on 16, so they should be upgraded when convenient.
Node 16 is still allowed to be used as the version with sofie locally, to minimise developer pain for now, but eventually that will be disabled.

Other information:

Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[x] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report
Patch coverage has no change and project coverage change: -18.88 :warning:

Comparison is base (84947de) 75.85% compared to head (a774c52) 56.98%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff               @@
##           release50     #937       +/-   ##
==============================================
- Coverage      75.85%   56.98%   -18.88%
==============================================
  Files             27      479      +452
  Lines           5476    75822    +70346
  Branches         525     3767     +3242
==============================================
+ Hits            4154    43206    +39052
- Misses          1320    32564    +31244
- Partials           2       52       +50

see 452 files with indirect coverage changes

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


Mention dep2nix

https://github.com/nixcloud/dep2nix

Does this mean we should be using dep2nix instead of the v2 branch of go2nix for packaging our dep-based application?

I would use dep2nix for now.
I also encourage Go users to look into vgo modules and maybe start a new vgo2nix tool than can replace go2nix in the future.

Thanks for the update. :-)

@adisbladis has started https://github.com/adisbladis/vgo2nix

@adisbladis has started https://github.com/adisbladis/vgo2nix

Amazing how Google currently doesn't return that link as a result when searching for vgo2nix. Thanks for sharing it.


As soon as everybody answered game should continue (not just when song is over)

closed in 44cd9665ba36480fbf183579b9b5d7202323cbea


SuperMAG download options

Documenting our changes for the old SuperMAG download routine (called test_download as of the #223 merge).
The main issue right now is that this is 100+ lines of untested and unusable code since SuperMAG blocked script access.
Potential courses of action:

delete function and point to version 1.2 to resurrect download routines in case script access is restored.
comment out code so that version is not lost in the git labyrinth.
leave things as they are and take the ~0.8% hit in the testing.

My preferred course is to delete and point to the last usable version.  @aburrell? @rstoneback?

My preference is to comment this time since it reduces the chances we forget in the future. That being said I can absolutely accept deleting it and relying on git to get the code back if SuperMAG opens data back up.
On Jun 4, 2019, at 10:36 AM, Jeff Klenzing <notifications<EMAIL_ADDRESS>wrote:
My preferred course is to delete and point to the last usable version. @aburrellhttps://github.com/aburrell? @rstonebackhttps://github.com/rstoneback?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/rstoneback/pysat/issues/233?email_source=notifications&email_token=AA3N26LLOR4ISKAUZ46JD43PYXBJDA5CNFSM4HSXAA52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW3EUFA#issuecomment-498485780, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA3N26L32HTRZIQC4F5QQOTPYXBJDANCNFSM4HSXAA5Q.

Angeline votes for delete and point to old version.

Note for future us:  The last copy of the SuperMAG download routine is the test_download function in commit 1f21f8afd06c558fc8bc08c500e3c377c4a879bc
See you on the other side, old code.

Closed with merge of #235.


explode_json_array error on destination_cbgs

If you try to call explode_json_array on destination_cbgs column from the social distancing data set you will get an error when calling pandas explode function
day_visits_exp = df[[place_key, file_key, array_column+'_json']].explode(array_column+'_json')

Error thrown: "KeyError: 0"
This is the error you get when trying to explode a column contain a json that has data stored as {"string" : integer}
I think in our case we get this error because if you try to express 012345 to an integer you get an error because an integer cannot start with a 0.

Suggested work around is to call unpack_json_and_merge, when we ask to explode destination_cbgs.
if array_column == 'destination_cbgs' and place_key == 'origin_census_block_group': # hard coded work around
    return unpack_json_and_merge(df,array_column, value_col_name=value_col_name,key_col_name=array_sequence)

We can also try to catch any case where someone tries to call this function with an improper array to explode.
Normally I would say calling explode_json_array with a data column like 'bucketed_distance_traveled' is a mistake on the user. However, it is not very obvious to call unpack_json_and_merge when wanting to explode 'destination_cbgs', since destination_cbgs can be viewed as integers unlike the values in 'bucketed_distance_traveled' clearly being a string
To generalize the approach we can do something like
df[array_column + '_json'] = load_json_nan(df,array_column)
try:
  day_visits_exp = df[[place_key, file_key, array_column+'_json']].explode(array_column+'_json')
except:
  return unpack_json_and_merge(df,array_column, value_col_name=value_col_name,key_col_name=array_sequence)

If we go with this approach then we might want to think about adding a parameter to unpack_json_and_merge and unpack_json that lets you specify the column you are passing is already loaded from a json. This way we can avoid calling load_json_nan twice on the same column. I think json.loads might even throw an error on an already loaded column, so having a parameter to pass in would avoid such an error.

@ryanfoxsquire What do you think about this approach to solve the problem? We should be able to correct any issues of someone incorrectly calling explode_json_array by doing this. Thus, solving the issue at hand as well as making it easier to use our functions.
We could also include a print statement that lets the user know when exploding failed and that we are returning unpack_json_and_merge instead. However, we will reintroduce the issue of printing a million times when multithreading, so maybe it's not worth it.

@bpblakely  can you provide more details and a minimal example that reproduces the error?
You say

I think in our case we get this error because if you try to express 012345 to an integer you get an error because an integer cannot start with a 0.

Can we confirm that that is exactly what triggers the error you are seeing? And can you post the entire error message you see?
It's still not clear to me why this error happens with SDM.destination_cbg column but not with Patterns.visitor_home_cbg column. I'd like to pinpoint what exactly causes the error and why this is different between SDM and Patterns.

The error happens to me when trying to use Patterns.visitor_home_cbg column. Not sure why it isn't happening for you.
Here's the exact steps I used to get the error.
f_path1 = r'F:\SG\weekly patterns new\patterns\2020\07\01\23\patterns-part1.csv.gz'
df1 = sgpy.read_pattern_single(f_path1)
sgpy.explode_json_array(df1,array_column='visitor_home_cbgs')

Here's the error message:
Traceback (most recent call last):

  File "<ipython-input-29-30dbc702917e>", line 1, in <module>
    sgpy.explode_json_array(df1,array_column='visitor_home_cbgs')

  File "G:\Python File Saves\safegraph_py.py", line 173, in explode_json_array
    day_visits_exp = df[[place_key, file_key, array_column+'_json']].explode(array_column+'_json')

  File "D:\Anaconda\lib\site-packages\pandas\core\frame.py", line 6318, in explode
    result = df[column].explode()

  File "D:\Anaconda\lib\site-packages\pandas\core\series.py", line 3504, in explode
    values, counts = reshape.explode(np.asarray(self.array))

  File "pandas\_libs\reshape.pyx", line 129, in pandas._libs.reshape.explode

KeyError: 0

@bpblakely Wait, sorry, taking a step back.
Why are you trying to use explode_json_array  on either destination_cbg or visitor_home_cbg? I had not looked closely and I assumed this was an error with unpack_json() based on your original description. I apologize for misunderstanding.
explode_json_array  is only meant for array columns such as Patterns visits_by_day or popularity_by_hour. These columns contain a string that is an array of numbers with no label or index and are intended to be referenced by their order in the array, e.g.,

popularity_by_hour |
A mapping of hour of day to the number of visits in each hour over the course of the date range in local time. First element in the array corresponds to the hour of midnight to 1 am. See also, Places Manual |
JSON [Integer] |
[ 0, 0, 0, 0, 0, 0, 0, 222, 546, 444, 333, 232, 432, 564, 456, 345, 678, 434, 545, 222, 0, 0, 0, 0 ]

In contrast, unpack_json_and_merge() is meant for columns that actually have key:value pairs, e.g.,

popularity_by_day |
A mapping of day of week to the number of visits on each day (local time) in the course of the date range. See also, Places Manual |
JSON {String: Integer} |
{"Monday": 3300,"Tuesday": 1200,"Wednesday": 898,"Thursday": 7002,"Friday": 5001,"Saturday": 5987,"Sunday": 0}

(quotes from patterns docs page)
destination_cbgs falls into the second category

destination_cbgs |
Key is a destination census block group and value is the number of devices with a home in census_block_group that stopped in the given destination census block group for >1 minute during the time period. ... |
JSON {String: Integer} |
{"130890212162":91,"131210101101":22,"131350502123":20}

Is there some specific reason you are hoping to use explode_json_array() with the destination_cbgs column? It is not the intended use, and I would recommend using unpack_json_and_merge()`. Maybe there is a use case I am not thinking about, or maybe we need to improve our documentation somewhere to avoid this confusion?

@ryanfoxsquire The error is because the function is being called on a dictionary, not a list. So, the problem is still using the wrong function for what you want to do. I had someone asking me for help due to this issue and it wasn't obvious why there was an error and that he should be calling the other function. It even got me tripped up for a day trying to fix it. So, I think avoiding the problem and correcting it might be better.
In order to catch this error we can either apply load_json_nan on the first item of the column you provide. After applying load_json_nan you can check if the result is either a dictionary or a list. If it's a dictionary we can call unpack_json_and_merge instead.

More discussion here: https://safegraphcovid19.slack.com/archives/C014FK2QWNL/p1599184256028200?thread_ts=1599087924.021300&cid=C014FK2QWNL
conclusion:
Let's not add code to the repo for the purpose of handling the case of  people misunderstanding which function to use, and catching that and redirecting them to the correct function on the backend.
We should expect people to use the functions for their intended purposes. If people are not sure which function to use, then then it is our failure in documentation/readme.  That problem is better solved with improved documentation, not more code.
I think we should consider additional documentation, possibly in the readme, to help people use the right function.

Not an error, planning to update docs to avoid confusion of misusing functions


Request to run local LLMs instead of paid API

Contact Details
No response
What features would you like to see added?
There are free open-source databases you can run at home now and they will only get better.
Installing has been made easy via sites like https://ollama.ai/
Please add support to connect to local database via Ollama.
More details
There is a great need for people be be able to run their own open source LLM at home.
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct

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

You can try using a project like litellm which can connect to ollama, and be used as a backend for Open Source models. I will test it soon and then write a guide.

That would be great. Thanks!

If it helps, LiteLLM mentions running LibreChat and ollama in the below page
LiteLLM Documentation - Proxy Server

I think it's pretty misleading to call this project "LibreChat" when it's relying on proprietary, paid APIs

I think it's pretty misleading to call this project "LibreChat" when it's relying on proprietary, paid APIs

Libre in software means to have "very few limitations on distribution or the right to access the source code to create improved versions." This project is completely open-source, with the least limited license for use, and utilizes open-source solutions and philosophies, to improve upon its origin for those who build and use it.
The fact that this project has been downloaded over 650,000 times from github containers, not including non-container downloads, without transacting a single dollar for this, lays claim to the term Libre even in its inherent meaning.
To be clear, it's not relying on proprietary, paid APIs as you said, rather building mainly on a framework that OpenAI has set as the industry standard for interacting with LLMs remotely. LibreChat can utilize countless other open-source solutions to use local large language models following this framework, which is why it's useful to have a standard. This is not limited to LiteLLM, but also to many other API services that integrate local LLM solutions.
@nightpool This project lays more claim to being open-source than even Meta's LLama models, and frankly your comment undermines the open-source efforts to provide it freely.

Right now, this isn't a huge priority but it's planned to have a dedicated 'reverse proxy' endpoint to serve any alternative endpoint need, provided the OpenAI spec is followed, which even Mistral API follows.


Fixed typo: s/unqiue/unique/g

This is a just a basic typo fix in the plugins_volume.md file
The unique word was incorrectly spelled. Twice.
Signed-off-by: Damien Nadé<EMAIL_ADDRESS>

LGTM 🐭

LGTM

looks like this was merged in the 1.12 bump branch, so has to be cherry-picked to master


Polaris unable to scan media library

Every time I try to scan for media, the button just turns red and says "Error :(".
The error message in the log is as follows:
Error while writing to index command buffer: sending on a closed channel
Skipping DDNS update because credentials are missing
Skipping DDNS update because credentials are missing
Starting up database
Database file path: /home/media/.local/share/polaris/db.sqlite
Mounting API on /api
Beginning library index update
Mounting static files on /
Starting up server
Starting up UI (headless)
Skipping DDNS update because credentials are missing
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', /checkout/src/libcore/option.rs:335:21
note: Run with `RUST_BACKTRACE=1` for a backtrace.

My media is on a NAS, and I've tried everything. Accessing it through a UNC path on both windows and linux, Mounting it as a network drive on windows, mounting it into a folder using CIFS on linux. I'm totally out of ideas.
PS. I know the NAS is accessible because emby can see it using any of the above methods on the exact same computer.

Thank you for the report!
A few questions:

Can you post the full log?
Does it still happen after restarting polaris (or the computer where it runs)?

Hey @agersant,
That's the log file in its entirety. Only different between that and the file on disk, is that I isolated it from the subsequent restart of Polaris.
To answer your second question, restarting Polaris has no effect.

If it would help you, I can do a TeamViewer session or something with you. Just let me know

Thank you!
I'll take a look locally first and keep you posted. The crux of the error seems to be the very first line of the log. Polaris uses a Rust construct called a channel to communicate with the thread responsible for indexing the collection (and telling it to begin work). In this case, it looks like the channel is immediately in a unusable state.

Whelp, no idea what I did, but it's working now. Only downside is that I can't for the life of me figure out how to make it a systemd service. But that's for another issue.

I'll make the error handling a little cleaner around this, but I'm unsure how it happened in the first place.
Regarding systemd, here is the script I use whenever I need to re-image my Raspberry Pi which runs Polaris. One of the things it does is setup Polaris as a systemd service:
https://gist.github.com/agersant/1c3bac006b4201fcf3bf4c857c56067c

Thanks, but systemd is complaining about that PID file not being readable. Any ideas?


Add e2e tests

This PR:

includes capi test framework and e2e tests

Ref: https://release-1-5.cluster-api.sigs.k8s.io/developer/e2e

Depends on #75

I rebased this for cluster-api 1.6.1, ref #18

tests is gone

What about using github environments to control when and by whom these tests get run?
https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment
There still is the e2e environment from my initial testing that constantly is failing.

What about using github environments to control when and by whom these tests get run? https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment
There still is the e2e environment from my initial testing that constantly is failing.

yes, good point,
I don't know how to run the fork there though 😄

We could but pull_request_target is nice and simple. @avorima we can use environments if you can come up with a working workflow but I don't want the PR to be blocked on this.

We could but pull_request_target is nice and simple. @avorima we can use environments if you can come up with a working workflow but I don't want the PR to be blocked on this.

The documentation for this event says: Avoid using this event if you need to build or run code from the pull request.. It even expands on this in the Warning section.
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target
To me that sounds like a security risk which should not be merged.

@wikkyk  did i mess it? 😄

@avorima check the open points

blocks #92


Hardware requirements

Hi
I'm facing memory issue.
Can someone who successfully trained the 2B model please reveal what GPU, GPU memory and system memory they had on the PC on which they trained ?
Thanks

Thanks for sharing the details. Any idea what is the minimum gpu RAM that
can do it?
Thanks
On Wed, 11 Dec 2024 at 7:24 AM, zhangfaen @.***> wrote:

I used A800 80GB GPU
—
Reply to this email directly, view it on GitHub
https://github.com/zhangfaen/finetune-Qwen2-VL/issues/23#issuecomment-2533442767,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY52JXWCDSG6J4CQFRCBMD32E6LNTAVCNFSM6AAAAABTIUUAQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZTGQ2DENZWG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Naming seems wrong for one of the method

		/// <summary>
		/// Set interval between two dates.
		/// </summary>
		/// <param name="startDate">Start date.</param>
		/// <param name="finishDate">Finish date.</param>
		/// <returns>The instance itself.</returns>
		public virtual Ticker SetInterval(DateTime startDate, DateTime finishDate)
			=> SetStartDate(startDate).SetFinishDate(finishDate);

Based on the rest of the methods I think this should be named SetPeriod under the hood it use SetStartDate and SetFinishDate and both are mutating the period not the interval

Thank you @0Lucifer0, will fix it!


Update bee client pinning API

Will merge once we get a 🟢 run 👍

bee nodes added
gc: reserve check
Seed:<PHONE_NUMBER>656113963
node bee-1
reservestate: {5 1024 0 0}
created batch id 6215ff34cbe856bb552327db8ebccfa00f69adb37553e8784dfdcf8e8ba503e7 with depth 16 and amount 3
reservestate: {5 0 2 1}
uploaded pinned chunk "07f7806f27850fdd2d01683a44b1d11aed49b5bc239dbea22b469a81a41a3eff"
uploaded 100 chunks with batch depth 16, amount 1, at radius 5
uploaded 10 chunks with batch depth 16, amount 1, at radius 6

created batch id 9b126d95c7bcddc7738fad52be636ebb01990e025e5a7c3b7edbc77e018cba0c with depth 16 and amount 3
reservestate: {6 0 4 1}
retrieved low value chunks: 90, gc'd count: 10
retrieved low value high radius chunks: 10, gc'd count: 0
uploaded 100 chunks with batch depth 16, amount 3, at radius 6
created batch id 179705f8cbfae96905f7809c67d2c703e7227516862c7315938d9cb32b03ee2d with depth 16 and amount 3
reservestate: {7 128 1 1}
retrieved high value chunks: 100, gc'd count: 0


internal: inherit original ResponseWriter's interfaces

Signed-off-by: Tw<EMAIL_ADDRESS>(Thank you for contributing to Caddy! Please fill this out to help us make the most of your pull request.)
1. What does this change do, exactly?
make internalResponseWriter inherit original ResponseWriter's interfaces.
2. Please link to the relevant issues.
N/A.
3. Which documentation changes (if any) need to be made because of this PR?
No.
4. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I am willing to help maintain this change if there are issues with it later

@mholt , I second this. We could define a type which wraps underlying types and implements all the interfaces. Then middleware could just embed it.

If that would work, we should look into that. :)

Ok, I will work out a change soon.


Allow for more config options

I'd like to be able to change the messages sent, and maybe have it so you don't need to use a recovery compass. I'd much prefer for it to automatically show in chat when a player triggers an alarm

Thanks. Ill try to make this and make it less cluttered in the config file.
Problems that may arise with that:

Scoreboard "messages" cant have new formatting as chat messages have. Internally they are just colored(team colors) player names
Over cluttered config file

Anyways thanks for the suggestion and ill do smth to provide functionality :)

I updated the plugin :D
Now each text value can be customized and removed if value of text is ""
Please, @Swirren, reply back if ya satisfied with config options now or you wish for more.
Thanks,
GibbDev


Add drag and angular drag to rigid body (remaining properties later)

Current rigidbody implementation does not include all Unity rigidbody features.

Also, the default angular drag value of 0.05 is used even though there is no way to change the value in the MRE.

Hi scm2217. We are adding rigid body properties incrementally. I will add this issue to the roadmap for drag and angular drag, which are straight forward. Deferring constraints for the time being, as they will require additional work.

Deferring constraints for the time being, as they will require additional work.

@eanders-MS Rigid body constraints are already supported in the SDK so there is no need to defer.

Oh interesting. I thought we pulled that. Are they in app-relative coordinates? That was the extra work part above.

When you freeze a component of the position or rotation, you are freezing for all coordinate spaces.  Physics only cares that you froze that component of the position/rotation.

I was thinking how we'd support the per-axis constraints shown above.

@eanders-MS That is what I am talking about.  Those are supported in the SDK right now.
export enum RigidBodyConstraints {
	None = 'none',
	FreezePositionX = 'freeze-position-x',
	FreezePositionY = 'freeze-position-y',
	FreezePositionZ = 'freeze-position-z',
	FreezePosition = 'freeze-position',
	FreezeRotationX = 'freeze-rotation-x',
	FreezeRotationY = 'freeze-rotation-y',
	FreezeRotationZ = 'freeze-rotation-z',
	FreezeRotation = 'freeze-rotation',
	FreezeAll = 'freeze-all',
}


Update Index.cshtml.cs

Update custom fields on the user.

@Erwin537  Thanks for fixing this. Name was being updated, but not DOB.

@Rick-Anderson is it possible for me to also propose a change on the documentation page for people following the docs without downloading the sample? Or is that something only you can do?

@Erwin537  what did you have in mind?

You can always propose a change.

@Rick-Anderson in the section addressing the changes that should be done to the register page that line of code should be added and highlighted as well I guess. (https://docs.microsoft.com/en-us/aspnet/core/security/authentication/add-user-data?view=aspnetcore-2.1&tabs=visual-studio#update-the-accountregistercshtml-page)
Okay, Typing this reply I found out how it works, it references the files from github and in querystrings it says which lines to highlight. Not sure how to do that though, as the referenced file is not yet updated. Should I have included those changes in this PR?

@Erwin537  I can fix that and you can review my PR. Send me a screen shot of what needs updating. Is it just the code you added?
I wonder how name was updated without your code.

this - right?

@Rick-Anderson yes, perfect 👍
I just tested using "Name" (I used other properties to test) but Name doesn't save for me without that one line of code either. Does your browser maybe do some autofill which made you think the property was saved?


Release 3895 4008 to prod beta

cc @cowanrc

Codecov Report
Base: 89.68% // Head: 89.68% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (cd2fb6e) compared to base (d1962aa).
Patch coverage: 97.22% of modified lines in pull request are covered.

:exclamation: Current head cd2fb6e differs from pull request most recent head 101a326. Consider uploading reports for the commit 101a326 to get more accurate results

Additional details and impacted files
@@              Coverage Diff              @@
##           prod-beta      #74      +/-   ##
=============================================
- Coverage      89.68%   89.68%   -0.01%
=============================================
  Files             42       42
  Lines            669      659      -10
  Branches         123      121       -2
=============================================
- Hits             600      591       -9
+ Misses            69       68       -1

Impacted Files
Coverage Δ

...tlementsList/ManifestEntitlementsListContainer.tsx
100.00% <ø> (ø)

...lliteManifestPanel/satelliteManifestPanelUtils.tsx
98.36% <96.00%> (-0.41%)
:arrow_down:

.../SatelliteManifestPanel/SatelliteManifestPanel.tsx
76.08% <96.15%> (+2.64%)
:arrow_up:

...ifestEntitlementsList/ManifestEntitlementsList.tsx
82.35% <100.00%> (ø)

src/hooks/useCreateSatelliteManifest.ts
100.00% <100.00%> (ø)

src/hooks/useDeleteSatelliteManifest.ts
100.00% <100.00%> (ø)

src/hooks/useExportSatelliteManifest.ts
100.00% <100.00%> (ø)

src/hooks/useManifestEntitlements.ts
100.00% <100.00%> (ø)

src/hooks/useSatelliteManifests.ts
100.00% <100.00%> (ø)

src/hooks/useSatelliteVersions.ts
100.00% <100.00%> (ø)

... and 2 more

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

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


can't create a client without API KEY and Secret

If I'm just making calls to the Voice API which only requires app id and private key credentials the client fails if I don't have values for key and secret even though these are not used by the API.
For example:
client = Nexmo::Client.new(application_id: application_id, private_key) will cause the request to fail but if I create the client with
client = Nexmo::Client.new(application_id: application_id, private_key: private_key, key: 'dummy', secret: 'dummy') its fine

Yep, need to make the args optional and change to raising an exception when trying to use the key and secret instead, similar to #78.

Implemented in 9304941


File handle leak when exception in QueueFile construction

Fixed issue where a file handle was being leaked when an exception occurred during construction of QueueFile.
This issue was discovered when attempting to delete the file associated
with the QueueFile. The file was locked and couldn't be deleted (this
only occurs on Windows as Linux does not prevent deletion).
In the fix, if any exceptions occur during the construction of
QueueFile, the random access file is closed before returning.

Appears there is a new issue with errorprone (unrelated to these changes) which is causing Travis CI to fail. The unit tests can be updated to use ArrayDeque versus LinkedList to solve this.

We can fix that in a separate PR. The error-prone version should have been
pinned so new checks don't fail on existing code.
On Tue, Nov 28, 2017 at 3:27 PM Chris Smith<EMAIL_ADDRESS>wrote:

Appears there is a new issue with errorprone (unrelated to these changes)
which is causing Travis CI to fail. The unit tests can be updated to use
ArrayDeque versus LinkedList to solve this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/tape/pull/179#issuecomment-347653203, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEEYsP5jAtSbDtvAznlZMOKELM_H0Vks5s7GzBgaJpZM4Qt2Qt
.

sorry, that failure was my fault.
Is it alright to use try-with-resources? Tell Java 6 users to use desugar or similar?

I don't think we should impose that just yet. Maybe in another year once D8 is widely deployed.

oh, sorry, i read this wrong. looks good.

Thanks!


CTEs with only SELECTs in postgres require COMMIT/ROLLBACK

Executing
WITH x AS (SELECT 1)
SELECT * FROM x;

will be considered a transaction by dbeaver (v21.2.4) and I have to rollback/commit manually on my database (postgres 13).
Changing to smart commit mode doesn't help.

thanks for the report

Any news on this quite old issue?
I am heavily working with CTEs and it's driving me crazy.
BTW, it's happening on Mysql (MariaDB) as well, and I don't think it's related to the DBMS.
I'm on Linux, DBeaver 23.2.0.
Cris

@Cris70 My workaround these days is:
After connecting I put the connection in auto-commit mode and by default my user has only read rights via the following construct:

myuser is granted ROLE readonly (with auto-inherit)
myuser is granted ROLE readwrite (without auto-inherit)

SO I have to call SET ROLE readwrite; before being able to write anything and usually I'm smart enough to do that in a separate window with manual commit/rollback.

Still an issue as of Version <IP_ADDRESS>409221725


Documentation needs more information

This page https://github.com/emqx/kuiper/blob/master/docs/en_US/rules/sinks/edgex.md states that after processing, Kuiper will send the data to the EdgeX message bus: "Publish result to EdgeX message bus without keeping original metadata" and "3. The data sent to EdgeX message bus." and "Publish result to EdgeX message bus with keeping original metadata".
However, this is not how Kuiper works. Kuiper runs it's own ZeroMQ message bus and it publishes data to it's own ZeroMQ message bus after it processes data from EdgeX. Anyone writing a service to get data after Kuiper has processed it will need to get it from Kuiper's ZeroMQ. This should be made more clear in the documentation.
I've created this EdgeX documentation issue: https://github.com/edgexfoundry/edgex-docs/issues/225

Doc was updated and it will be included in 1.0.0 version.

Close the issue.


'DISPLAY' is not recognized as an internal or external command, operable program or batch file.

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Hi @AKHILMELATH.
Not sure how you're getting that error message. dotnet is the name of the command, not display. Can you share some screenshots?


CeE Kit - PowerBI Dashboard data - confusion around column names

We need to fill out what is actually occurring after we run the flow.
After running the Sync Audit Logs flow, it doesn't appear to be bringing over accurate information. The created on date and the modified date for instance doesn’t match the details view page in Power Apps and the Power Automate. Also, we need info for last run date and time.
Component (please tell us which flow or app you are experiencing issues with):

Solution [e.g. Core, Nurture]
Version [e.g. 1.29]
Sync Audit Logs flow / PowerPlatform Admin Dashboard / CoE
To Reproduce
Steps to reproduce the behavior:

Go to ' Dashboard-PowerPlatformAdminDashboard-2021-02-02 ' Source: CoEStarterKit.zip
Click on 'Apps page & Cloud flows'
Expected behavior
Based on the info in the PowerBI report the last run date should match to the last run date on the Power Automate
Screenshots
See attached File.

Thanks,
CoE.docx

Our audit logs do not gather data for Power Automate. They only gather data for Power Apps. This data is stored in the Last Launched field of the Power Apps table.
Further they do not gather the created/modified dates, we get that from the product connectors themselves. And each row in dataverse for us has 2 entries for created and modified, one for the object (the flow_created date for example) and one for the row in the table (the date the flow was entered into inventory)

Hope that helps

Does the Audit log [admin_userupn] collect the value of the user who launched the app?

Yes that is correct. That represents the person that launched the app in the case of LaunchPowerApp
I'm going to close this out as there isnt anything further to do here to assist.
Thanks for using CoE