enum bitmasks in template

I really like the elegant simplicity achieved by your enum classes!
However, I got stuck on a problem using them in templates. The following code inspired by ATL CWinTraits fails. Any idea of a solution?
enum class ServiceHandler : uint16_t
{
    accept_none                     = 0u,
    accept_stop                     = SERVICE_ACCEPT_STOP,
    accept_pausecontinue            = SERVICE_ACCEPT_PAUSE_CONTINUE,
    accept_shutdown                 = SERVICE_ACCEPT_SHUTDOWN,
    accept_paramchange              = SERVICE_ACCEPT_PARAMCHANGE,
    accept_netbindchange            = SERVICE_ACCEPT_NETBINDCHANGE,
    accept_hardwareprofilechange    = SERVICE_ACCEPT_HARDWAREPROFILECHANGE,
    accept_powerevent               = SERVICE_ACCEPT_POWEREVENT,
    accept_sessionchange            = SERVICE_ACCEPT_SESSIONCHANGE,
    accept_preshutdown              = SERVICE_ACCEPT_PRESHUTDOWN,
    accept_timechange               = SERVICE_ACCEPT_TIMECHANGE,
    accept_triggerevent             = SERVICE_ACCEPT_TRIGGEREVENT,
    accept_userlogoff               = SERVICE_ACCEPT_USER_LOGOFF,
    accept_lowresources             = SERVICE_ACCEPT_LOWRESOURCES,
    accept_systemlowresources       = SERVICE_ACCEPT_SYSTEMLOWRESOURCES
};
enableEnumClassBitmask(ServiceHandler);

template <ServiceHandler Taccepttraits = ServiceHandler::accept_none>
class ServiceAcceptTraits
{
public:
    ServiceHandler GetAcceptTraits(void) const noexcept  { return Taccepttraits; }
};
using StandardAcceptTraits = ServiceAcceptTraits<
      ServiceHandler::accept_stop
    | ServiceHandler::accept_pausecontinue
    | ServiceHandler::accept_shutdown>;

This is intended to be used like so:
template <
	class TderivedClass,
	const wchar_t* Tservicename,
	class TServiceAcceptTraits = StandardAcceptTraits>
class NO_VTABLE ServiceBase
{
};

compilation gives
error C2440: 'specialization': cannot convert from 'bitmask<ServiceHandler>' to 'ServiceHandler'

If you refer to the table in the Readme, you'll see that the result of operator| is a bitmask<T>. You can also refer to my blog post for a more thorough explanation. Based on the example you gave, I believe your template should be: template class TderivedClass, const wchar_t* Tservicename, class TServiceAcceptTraits = bitmask<StandardAcceptTraits>> class NO_VTABLE ServiceBase {};

Thanks for the kind attention and the suggestion. This is a bit over my head.
The problem is that ServiceAcceptTraits works like a kind of property, just as ATL::CWinTraits holds the style of a Win32 Window, a DWORD made out of a combination of specific styles. In my case, ultimately there is a uint16_t member assigned by the ServiceAcceptTraits from a combination of specific functionality values. The fact that only a combination of specific values is valid makes it tempting to use an enum class. Sadly I can't get it to work. So currently, I commented out the class specification in my enums and reverted to this based on normal enums:
template <uint16_t Taccepttraits = ServiceHandler::accept_none>
class ServiceAcceptTraits
{
public:
    ServiceHandler GetAcceptTraits(void) const noexcept  { return Taccepttraits; }
};
using StandardAcceptTraits = ServiceAcceptTraits<
      ServiceHandler::accept_stop
    | ServiceHandler::accept_pausecontinue
    | ServiceHandler::accept_shutdown>;

The enumclass bool operator is useful for validity tests, but I think I need a kind of enum valuetype operator. I think using casts or special types takes away the elegance of the solution which probably makes it better to revert to normal enums.

I believe I missed the real issue in my previous reply with the line using StandardAcceptTraits = ServiceAcceptTraits<ServiceHandler::accept_stop | ServiceHandler::accept_pausecontinue | ServiceHandler::accept_shutdown>;.
You are trying to encode the mask into the type system and the result of operator| doesn't do that for you right now. You could probably get the desired result with the following code:
      (ServiceHandler::accept_stop
    | ServiceHandler::accept_pausecontinue
    | ServiceHandler::accept_shutdown).value>;```

==========
Original reply I was about to write, but might still be enlightening…
==========
There is a semantic difference between a mask and an enumerator and reflecting that semantic difference in the type system makes it possible to prevent additional programming mistakes. When handling the `bitmask<T>` type, you can access the underlying value (an integral type) using its `value` member.

If you'd rather not have the bitmask type, you can give a try to the previous enum class helpers used in the [first blog post](https://dalzhim.github.io/2016/02/16/enum-class-bitfields/) I made on the subject.

Yes, thanks!! The following works
template <uint16_t Taccepttraits = 0 /*ServiceHandler::accept_none*/>
class ServiceAcceptTraits
{
public:
    uint16_t GetAcceptTraits(void) const noexcept  { return Taccepttraits; }
    void SetAcceptTraits(uint16_t trait) const noexcept  { Taccepttraits = trait; }
};
using StandardAcceptTraits = ServiceAcceptTraits<
     (ServiceHandler::accept_stop
    | ServiceHandler::accept_pausecontinue
    | ServiceHandler::accept_shutdown).value>;

or with other words
bitmask<enum ServiceHandler> mask2 = ServiceHandler::accept_stop | ServiceHandler::accept_shutdown;
uint16_t mask3 = mask2.value;
uint16_t mask4 = (ServiceHandler::accept_stop | ServiceHandler::accept_shutdown).value;

Hiding bitmask and having an operator underlying_type() (?) would be nice though

Hiding bitmask<T> is not an option as it is what makes it possible to detect more bitmask-related programming errors at compile-time. Same goes for operator underlying_type() as this would reintroduce bug-prone implicit conversions that were eliminated by using enum class rather than enum.

OK, it was just a suggestion. I suspected operator underlying_type() would be regarded as somewhat take away the point of enum class, but if restricted to the bitmask class I would like it very much. Isn't the values validated already in the bitmask? Anyway, I tried the following simple patch
enumclass.diff.txt
or at line 63
    constexpr operator underlying_type(void) const
    {
        return value;
    }

which makes the following convinency work (just as normal enums)
uint16_t mask5 = ServiceHandler::accept_stop | ServiceHandler::accept_shutdown;
The main.cpp test works as well

You're welcome to use that patch if it helps you. The reason I don't want to include it is that I want the following piece of code to raise a compilation error.
void f(int);

f(ServiceHandler::accept_stop | ServiceHandler::accept_shutdown);

I agree, the following which is allowed by the patch is even worse
auto mask1 = ServiceHandler::accept_stop | ServiceHandler::accept_shutdown | 10;
None of the enum class bitmask solutions I've seen is dealing with the issue of getting the resulting value in a bitmask, other than your .value hack above that is. I guess the conclusion is to either use the hack or use normal enums.


Emaggable vendors + Familiars for Chaplain

About the PR
Vendors can now be emagged to add things to them, currently only used by the pietyvend.
All cult gear moved to pietyvend's emag inventory.
I decided to give chaplain something no servers have: We agreed null rods suck, some people don't like faith either, but the chaplain needs something that helps with his roleplay and gimmicks.
I decided on familiars, which don't encourage violence the same way a straight up weapon does, but still allow lots of room for gimmicks, theming, roleplay, and robustness. The fact they're ghost roles by default means that at least 1 other person has reason to go along with whatever chaplain's gimmick for the round is, too.
Screenshots

https://user-images.githubusercontent.com/60792108/156284685-c2afd93e-8873-4f9a-a43a-dd5f8617fd77.mp4
Note: All the localization bugs have been fixed as far as I can tell
Changelog

:cl: Rane

add: Chaplains can now summon a familiar from their bible.
add: Evil chaplains can now emag the Pietyvend for some goodies.
fix: You can now draw blood from most mobs.

conflcits + reviews


Update free-courses-en.md

Added A python programming course
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
Add resource
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Why did you remove the Mosh course?


Question about training processing

Hi
I run the code in the Fewrel dataset. I user maml+cnn as the model and bert as the embedding according to Tabel2 in the paper.During the training, the model was soon overfitted and the best epoch for 5way1shot and 5way5shot are 9 and 14.
I wonder if it's normal.
I use the "bert-base-uncased" type of bert and do not finetune it in meta-training.
The dev acc: 5way1shot:0.5114 ± 0.0932;   5way5shot:0.6348 ± 0.0563
I use the following parameter:
python src/main.py
--cuda 0
--way 5
--shot 1
--query 25
--mode 'train'
--embedding 'cnn'
--classifier 'mlp'
--dataset=$dataset
--data_path=$data_path
--n_train_class=$n_train_class
--n_val_class=$n_val_class
--n_test_class=$n_test_class
--pretrained_bert=$pretrained_bert
--bert_cache_dir=$pretrained_bert
--maml
--maml_firstorder
--maml_innersteps 10
--bert
--notqdm
--maml_stepsize 0.01 \
Thank u

Yes, it is normal. BERT + CNN is a very powerful model built on top of the input words. It is able to overfit the train tasks very easily. However, the learned representation may not be useful for unseen val tasks (this is why the dev acc is very low).

Thank u


Fix query on bloom in case of multiple data files in one segment

Problem: Query on bloom datamap fails when there are multiple data files in one segment.
Solution: Old pruned index files were cleared from the FilteredIndexSharedNames list. So further pruning was not done on all the valid index files. Hence added a check to clear the index files only in valid scenarios. Also handled the case where wrong blocklet id is passed while creating the blocklet from relative blocklet id.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/584/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/581/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/586/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/587/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/585/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/582/

@manishgupta88 Please review.

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/715/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/722/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/723/

Can you add a testcase to reproduce this issue, I tried query using bloom filter on multiple data files in one segment in local machine, and it seems fine.
@shivamasn

@jackylk This issue is reproducible only in case of concurrent scenario and in distributed environment.


[tvmop] use size_var for placeholder & compute to reduce size of codegen

It's a follow up of https://github.com/apache/incubator-mxnet/pull/17438

Thanks @reminisce


[useAsyncData] Data in named variable

Hi,
When using useAsyncData I can get the right content if I use this code:
<script setup>
const { find } = useStrapi4();

const { data, pending, refresh, error } = await useAsyncData(
  'events',
  () => find('events')
);
</script>

but... as data is too generic and I need to get content from two different entities, I just tried to make the change proposed in nuxt's useAsyncData example:
<script setup>
  // Define params wherever, through `defineProps()`, `useRoute()`, etc.
  const { data: post, refresh } = await useAsyncData('post', () => $fetch(`https://api.nuxtjs.dev/posts/${params.id}`) )
  // Or instead - useFetch is a convenience wrapper around useAsyncData when you're just performing a simple fetch
  const { data: post, refresh } = await useFetch(`https://api.nuxtjs.dev/posts/${params.id}`)
</script>

so, I changed my code to this (notice the data: events change):
<script setup>
const { find } = useStrapi4();

const { data: events, pending, refresh, error } = await useAsyncData(
  'events',
  () => find('events')
);
</script>

but this results in an error like this (on server console):
RefImpl {
  __v_isShallow: false,
  dep: undefined,
  __v_isRef: true,
  _rawValue: {
    error: {
      status: 500,
      name: 'UnknownError',
      message: 'fetch failed ()',
      details: FetchError: fetch failed ()
          at async /home/user/.../node_modules/@nuxtjs/strapi/dist/runtime/composables/useStrapiClient.mjs:44:14
          at async setup (/home/user/.../app.vue:50:12)
    }
  },
  _value: {
    error: {
      status: 500,
      name: 'UnknownError',
      message: 'fetch failed ()',
      details: FetchError: fetch failed ()
          at async /home/user/.../node_modules/@nuxtjs/strapi/dist/runtime/composables/useStrapiClient.mjs:44:14
          at async setup (/home/user/.../app.vue:50:12)
    }
  }

If I replace the find('events') with the $fetch('https://api.nuxtjs.dev/posts/1') from the example, it works perfectly populating the events variable.
Any idea about this?
Thanks!

In fact, It doesn't work like that, I have to add the {server: false} option for it to work. Like this:
const { data, pending, refresh, error } = await useAsyncData(
  'events',
  () => find('events'),
  {server: false}
);

A whole example or blog post about whole creation with an example API would be great to have...

I'm closing this as I was doing a fast test of this module and haven't set it up properly.
Once I set up the auth middleware, it worked properly. Didn't know why I got data in data variable and no in the events one but... now it working.


Use abstract socket address as the IPC socket

Related issue number

Fixes #1304

Closing as it won't work on Kubernetes, as abstract socket is subject to CLONE_NEWNET however non-abstract UNIX-domain socket only relies on the file visibility.


Method chaining make it easy to use

-1

$em
->close()
->createQueryBuilder() // Error!
;

so? that normal?

$em->close(); $em->createQueryBuilder(); // Error

@ronfroy I should have been more explicit... what's the advantage of a fluent interface? Save few keystrokes?

it improves developpement speed, especially with IDE and autocomplete and makes code more readable and concise.

$em
->beginTransaction()
->persist($entity1)
->persist($entity2)
->commit();

@ronfroy Ok, so let's see what we can evaluate:

beginTransaction: Non-obvious to return EM back, we're debating internally it should return an instance of Transaction. Adding fluent support makes it a BC break if in the future, with the argument against of saving keystrokes. Not valid IMHO.
persist: Partially agree.
commit: If we do Transaction, it should return Transaction instance. Same as before, BC break for no reason.

Based on this, I don't see improvements of adding fluent interface with the advent of saving keystrokes and making our API impossible to be changed. That's why I'm -1.

What's about flush and persist?

:-1: This PR is not acceptable, you've even put return $this into functions that are already supposed to return a different kind of data.

@DHager & @guilhermeblanco
I think that there are methods like procedures and methods like functions. Procedures will never have return value, so they can easily be fluent. beginTransaction is a  procedure and this make no sense to return another object. getTransaction is a function and can return another object.

Fluent interfaces are great when you're dealing with a very well-contained data model that is either immutable or mutates cleanly without side-effects, so that the interface is a "poor-man's Domain Specific Language".
Unfortunately I think Doctrine is pretty much the opposite of that situation, due to the issues it tackles. There always needs to be some breathing-space to add special-case code and workarounds for the different database vendors, and the amount of tricky-state being managed is extreme.

On the entityManger layer we are dealing with well-conained data (entity) not like in dba. I'm wrong?
"There always needs to be some breathing-space to add special-case code and workarounds for the different database vendors, and the amount of tricky-state being managed is extreme."
I don't really understand. breathing-space can be use or not use with fluent interface and amount of the state is exactly the same? It's just more freedom?
"Add the fact that it's a library which is widely-used in long-term products, and you have to be even more conservative with API changes."
Yes i agree. But fluent interface don't break the current usage ^^

Closing, and re-using http://ocramius.github.io/blog/fluent-interfaces-are-evil/, which I actually wrote exactly for this kind of PR.
Sorry @ronfroy, not going to add fluent interfaces unless required.


[5] Create a database representation for the data structure, with function calls

Requested to add:

doc string,
type checking
timeout and re-trying connection

https://pymongo.readthedocs.io/en/stable/

Documented on the database wiki.
https://github.com/MaksimEkin/data-structures-game/wiki/Database

python manage.py test game_board.database.test_db


Filter resource file names to avoid including the same file multiple times.

Addresses issue #882.

It marked my comments as outdated, but they're not

Good point @jackkoenig. I think string comparisons are fine as long as the same strings are generated for the same resource file in all cases. We should note this in the PR and at the sites where the paths are generated.
One could argue that it's really not sufficient to just verify that the paths match (or don't) - we should be checking file contents.


Update Group Context Extensions

Adds back to upstream the update_group_context_extensions method that we needed to get mutable metadata working.
cc @cameronvoell @franziskuskiefer

@nplasterer @cameronvoell let me know when I should look at this again.

@nplasterer I made a PR to your fork branch here that updates the comment and adds a test https://github.com/nplasterer/openmls/pull/1

Merged @cameronvoell PR in. This should be ready for a review now @franziskuskiefer. 🙏


fet-1490: basic CSP

Closing this as we do not use server-side rendering and thus no next middlewares


📖[Docs] Document minimal catalog selection

Documents the new features for catalog selection.
Description

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

Addresses https://github.com/operator-framework/operator-controller/issues/1154

/assign @dhoover103

Honestly, I don't have anything to add - this already has various examples that I was still working on putting together for my version of the doc.


Launch from kernelspec test not starting

Happens consistently.
Might be a regression.

29.txt
Example log of a failed run.

Wasn't reproing locally anymore. Deassigning due to oof.


ESP32 reboots all 5 to 10 minutes

Hi there
Many thanks for this great project.
I created a home-assistant-glow with a "Node MCU ESP32" from Joy-it.
Almost everything works fine, the impulses from the power meter are recognized correctly.
But what is weird, the ESP32 seems to restart every 5 to 10 minutes.
This can be recognized by the fact that the home-assistant-glow device is not available for a few seconds in HA and when back, the total energy counter is reset to 0.
At first I thought this is due to electromagnetic interference.
Therefore I've kept the wires between the sensor and the ESP32 extremely short and I've installed a ferrite ring on the incoming USB power cable.
Unfortunately, this did not change anything at all. The reboots are still in the same frequency, between 5 to 10 minutes.
Does anyone have any idea what the cause for these reboots could be?
Is there a watchdog on the device that is not triggered correctly?
Could interference be interspersed on the reset/en signal?

Have found the following in the log at the time of the reboot or maybe better called reset:
[18:13:58][D][sensor:121]: 'House - Power consumption': Sending state 2368.42090 W with 0 decimals of accuracy
[18:13:58][D][light:035]: 'Red' Setting:
[18:13:58][D][light:046]:   State: ON
[18:13:58][D][sensor:121]: 'House - Total energy': Sending state 0.08800 kWh with 3 decimals of accuracy
[18:13:58][D][light:035]: 'Red' Setting:
[18:13:58][D][light:046]:   State: OFF
[18:14:01][D][sensor:121]: 'House - Power consumption': Sending state 2364.53198 W with 0 decimals of accuracy
[18:14:01][D][light:035]: 'Red' Setting:
[18:14:01][D][light:046]:   State: ON
INFO home-assistant-glow.local: Unexpected error while reading incoming messages: [Errno 104] Connection reset by peer
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/aioesphomeapi/connection.py", line 505, in run_forever
    await self._run_once()
  File "/usr/local/lib/python3.9/dist-packages/aioesphomeapi/connection.py", line 480, in _run_once
    pkt = await self._frame_helper.read_packet()
  File "/usr/local/lib/python3.9/dist-packages/aioesphomeapi/connection.py", line 219, in read_packet
    return await self._read_packet_plaintext()
  File "/usr/local/lib/python3.9/dist-packages/aioesphomeapi/connection.py", line 197, in _read_packet_plaintext
    preamble = await self._reader.readexactly(1)
  File "/usr/lib/python3.9/asyncio/streams.py", line 723, in readexactly
    await self._wait_for_data('readexactly')
  File "/usr/lib/python3.9/asyncio/streams.py", line 517, in _wait_for_data
    await self._waiter
  File "/usr/lib/python3.9/asyncio/selector_events.py", line 856, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
ConnectionResetError: [Errno 104] Connection reset by peer
INFO Disconnected from ESPHome API for home-assistant-glow.local
WARNING Disconnected from API
INFO Successfully connected to home-assistant-glow.local
[18:14:13][D][light:035]: 'Red' Setting:
[18:14:13][D][light:046]:   State: OFF
[18:14:16][D][api:095]: Accepted <IP_ADDRESS>
[18:14:16][D][api.connection:727]: Home Assistant 2021.9.7 (<IP_ADDRESS>): Connected successfully
[18:14:16][D][sensor:121]: 'House - Power consumption': Sending state 2367.64233 W with 0 decimals of accuracy
[18:14:16][D][light:035]: 'Red' Setting:
[18:14:16][D][light:046]:   State: ON

I just received and installed a new "Node MCU ESP32" device.
Now all works well.
There must have been an hardware defect on my previous device.


Updates botappid check for PowerVirtualAgentsDialog

Updates the check for botAppId in PowerVirtualAgentDialog to check for empty string as well
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


References Error

Your paper published in arxiv https://arxiv.org/abs/2108.11250 v4,[7] may MultiNet: Real-time Joint Semantic Reasoning for Autonomous Driving rather than R. Chandra and P. Bahl, “Multinet: Connecting to multiple ieee 802.11networks  using  a  single  wireless  card,”  inieeeinfocom2004,  vol.  2.IEEE, 2004, pp. 882–893.
Thank you!

I' m sorry for this mistakes, I will correct it immediately. Thank you again for your valuable comments!

Your paper published in arxiv https://arxiv.org/abs/2108.11250 v4,[7] may MultiNet: Real-time Joint Semantic Reasoning for Autonomous Driving rather than R. Chandra and P. Bahl, “Multinet: Connecting to multiple ieee 802.11networks using a single wireless card,” inieeeinfocom2004, vol. 2.IEEE, 2004, pp. 882–893.
Thank you!

I' m sorry for this mistakes, I will correct it immediately. Thank you again for your valuable comments!

All my best wishes for the future!


Update dependencies for Senzing 3.8.0

See https://github.com/Senzing/senzing-tools/issues/137

Pull requests:

https://github.com/Senzing/g2-sdk-go-mock/pull/94


Do not treat feature options as mutually exclusive

Consider a Rust crate with the following features. The crate enables "foo" by default, and it also supports feature "bar":
[features]
default = ["foo"]
foo = []
bar = []

Suppose a user wants to build the crate with only the "bar" feature. The user uses --no-default-features to disable "foo", then adds "bar":
cargo build --no-default-features --features bar

Utilities like cargo-objcopy first build the crate, so we would expect that replacing build with objcopy would yield the same behavior. However, before this PR, using objcopy like
cargo objcopy --no-default-features --features bar --verbose

shows the following verbose output:
"path/to/cargo" "build" "--features" "bar" "--message-format=json"

We notice that --no-default-features is dropped.

Reproduce in practice
I noticed this issue when working with newly-added examples in the teensy4-rs project. From the hypothetical above, replace --feature bar with --feature rtic, and add an --example flag:
git clone https://github.com/mciantyre/teensy4-rs.git
cd teensy4-rs
git checkout 8cf06cf

cargo objcopy --verbose --example rtic_blink --no-default-features --features rtic -- -O ihex out.hex

"/Users/mciantyre/.rustup/toolchains/stable-x86_64-apple-darwin/bin/cargo" "build" "--example" "rtic_blink" "--features" "rtic" "--message-format=json"
   Compiling teensy4-bsp v0.1.0 (/Users/mciantyre/Projects/teensy4-rs)
error: could not compile `teensy4-bsp`.

To learn more, run the command again with --verbose.
error: Failed to parse crate metadata

I've intentionally selected an example that fails to link without also specifying --no-default-features. The actual error isn't reported in that output. But, the verbose output shows that we're treating these flags as mutually exclusive, favoring --features rtic over --no-default-features

This PR proposes that we do no treat these command-line flags as mutually exclusive. As of this PR, the same usage of cargo-objcopy results in the expected build command that has both flags.
We seem to also treat these flags as mutually exclusive when constructing the metadata command:
https://github.com/rust-embedded/cargo-binutils/blob/bd59333418dbbe34b8caa9c772745f092ed7832f/src/lib.rs#L279-L287
This PR does not address that usage. It looks like cargo_metadata treats these arguments as mutually exclusive, since there's only one features value, which is possibly one of three CargoOpt variants. Fixing that seems out of scope.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @therealprof (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

cargo_metadata's feature option exclusion is described in oli-obk/cargo_metadata#79.

@ZeroErrors Seems you agree with this change?

Yep, makes total sense that it should act this way.
May be a good idea to make an issue for the cargo_metadata portion of the problem so its not forgotten about.

I'll happily take the PR and leave the issue reporting on cargo_metadata to someone else. ;)


the bot buys if the owner buys his shares, even if the account is not new

Hello Friend Thanks for the Bot It Works Well.
There is only one thing that I would like you to help me change since I am not a good programmer. It is that the bot buys when the owner makes a new purchase, I would like a new condition to be set. If the owner bought the action before, in that case the bot does not buy. buy only when it is really a new account. thank you

I can't do individual customizations to the code, sorry


Add header() method to support HTTP/S Headers

Headers are sometimes important for fetching source files from secure locations (i.e. Google Cloud Storage, AWS S3). This PR provides a clearcut method for adding HTTP headers with assurance that headers are applied in the right order on the ffmpeg and ffprobe commands.

New headers() method added.
README updated.
Tests written.

Examples
ffmpeg
ffmpeg()
  .input('https://www.googleapis.com/storage/v1/b/my-private-bucket/o/my-file.mp4?alt=media')
  .headers('Authorization: Bearer xyz123...')
  .headers('X-My-Custom-Header: 1234')
  .output('path/to/saved/file.mp4');

ffprobe
ffmpeg()
  .input('https://www.googleapis.com/storage/v1/b/my-private-bucket/o/my-file.mp4?alt=media')
  .headers(['Authorization: Bearer xyz123...', 'X-My-Custom-Header: 1234'])
  .ffprobe((err, res) => {
    ...
  });

Fixes https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/issues/882

The TravisCI check seems to be choking on something unrelated to this PR.

That TravisCI check is failing due to missing remote file @ https://www.johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz

Yes, John changed his URLs, the new one is https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz

I'll make a separate PR to fix the test suite

Tests are fixed, you can rebase on master

Any updates on this?


Probability intervals implementation

Function and tests for the probability intervals calculation of each convex hull

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

Project coverage is 100.00%. Comparing base (c37b4b4) to head (0cdf95d).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           22        40   +18
=========================================
+ Hits            22        40   +18

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


Add GKE default pod into allowlist in Mount Launched of Privileged Container rule

Signed-off-by: Hi120ki<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind release

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

/area CI

What this PR does / why we need it:
In GKE cluster, a system container gce-pd-driver that manages Persistent Disk is running.
But the rule Mount Launched of Privileged Container detects as false positive.
Process: mount -t ext4 -o defaults /dev/disk/by-id/google-pvc-<id> /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-<id>/globalmount

This container runs in kube-system namespace, and image is from gke.gcr.io/gcp-compute-persistent-disk-csi-driver.
I added it into allowlist(macro : user_known_mount_in_privileged_containers ).
I'm waiting for your comments on adding it into allowlist and my proposed changes.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Add GKE default pod into allowlist in Mount Launched of Privileged Container rule

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hi120ki
Once this PR has been reviewed and has the lgtm label, please assign mstemm for approval by writing /assign @mstemm in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @hi120ki ,
thanks for helping with FPs we really need this type of contribution :)
The only suggestion from my side is to create a new macro related to GKE. The macros like user_known_mount_in_privileged_containers are usually used as macros that each user can customise based on their environment. If we find something related to a specific technology we use to create a new macro related to it. :)
Thanks

@darryk10 I see. I revert and add new macro macro: known_gke_mount_in_privileged_containers as allowlist.
Cloud you check it?

/milestone 0.33.0
/ok-to-test

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: darryk10, hi120ki
Once this PR has been reviewed and has the lgtm label, please assign mstemm for approval by writing /assign @mstemm in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 1c9189cac088f67f7e9d69e3b83a1e3cac740fd4

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: darryk10, hi120ki, jasondellaluce, Kaizhe
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: darryk10, hi120ki, jasondellaluce, Kaizhe, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Closing and reopening to trigger the CI
/close

@leogr: Closed this PR.

In response to this:

Closing and reopening to trigger the CI
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/reopen
/hold
for the CI to complete

@leogr: Reopened this PR.

In response to this:

/reopen
/hold
for the CI to complete

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/hold cancel


Still Active or?

Hi Roberto,
Was looking to see if this is still planned to be maintained or if you have moved on with other exciting projects since it appears to not have been touched for some time.
Thank you, either way still an interesting project.

@airboss001 It hasn't been touched in a while because it simply works :) I do spend more time on our Node.js ORM, that's true. But as far as the browser ORM is concerned, this works fine. I'm working a lot with React + React Native nowadays, so I don't spend a lot of time on the Aurelia plugins.
@doktordirk does though, and others use it a lot. More than 100 installs in a week, without updates, tells me that it's still alive and kicking.
I hope this answers your question! 🍻

Thanks for the response.
And good news about the project.
Sometimes its hard to tell if it is abandoned, or just (as you note) works.


deduplicate and simplify code of integration tests

with #101 the function getOcis is moved to OcisPhpSdkTestCase.php, so it would be good to use it wherever needed/possible

Closing this issue as the task is done here. https://github.com/owncloud/ocis-php-sdk/pull/167


gRPC Python KeyError Raised During UpdateChannelPolicy When global=True Is Set

Background
When trying to set the global variable for the PolicyUpdateRequest gRPC endpoint in python, a KeyError is raised.
Example:
stub.UpdateChannelPolicy(ln.PolicyUpdateRequest(global=True, base_fee_msat=1000, fee_rate=0.000001, time_lock_delta=40))
Will result in the following python error:
KeyError: 'global'
Your environment
Lnd: lncli version 0.12.1-beta commit=v0.12.1-beta
OS: Windows
Backend: bitcoind
Python 3.8.5
Steps to reproduce
Try to execute the UpdateChannelPolicy via gRPC and python while also setting the global variable to True.  As per the below documentation:
https://api.lightning.community/?python#updatechannelpolicy
Expected behaviour
The expected behavior is to update all channel policies without specifying a channel point.
Actual behaviour
Conflict causing a key error while trying to set global variable.
Work-around
I was able to solve this issue by manually editing my rpb_pb2.py file and changing the name of the variable from global to target_all.  I am then able to set the variable properly and the expected result is observed.
Example:
stub.UpdateChannelPolicy(ln.PolicyUpdateRequest(target_all=True, base_fee_msat=1000, fee_rate=0.000001, time_lock_delta=40))
Result:
All channel policies are updated.
Proposed Solution
Update the variable name for this gRPC endpoint to something other than global to avoid any clashes in python.
Potential remediation:
https://github.com/cryptosharks131/lnd/commit/973ced1529d21bf3b53206e60b80ee3daa2ad9e0

I was able to validate the above mentioned fix after rebuilding rpc_pb2.py with the updated rpc.proto file.  I have opened a pull request to rename the gRPC variable to update_all and to remediate the issue under pull request #5164.

Sorry for only getting back to you on this so late. I don't think renaming a field in the RPC is the correct solution. This would potentially break other people that rely on the field name.
Can you try this instead?
args = {'global': True, 'base_fee_msat': 1000, 'fee_rate': 0.000001, 'time_lock_delta': 40}
stub.UpdateChannelPolicy(ln.PolicyUpdateRequest(**args))

See https://stackoverflow.com/questions/4179175/python-named-argument-is-keyword.

I can confirm this does allow you to use the existing variable name to update all channels as well.

I am not sure how regenerating the other proto files affects the lnd binary's gRPC interface but with just the single change to rpc.proto, existing gRPC users are not affected as they would have to rebuild their rpc_pb2.py from the new rpc.proto in order to observe the effect of the variable change.

The native golang gRPC interface (and all interfaces for other languages) are generated from rpc.proto. So renaming the field will affect all API users. Therefore I'm in favor of documenting this special case in the Python documentation for the RPC instead of renaming the field itself.

I agree, that seems like the easiest thing to do in this case.
To help facilitate this, I have reverted the variable change on the attached pull request and pushed an update for the documentation to reflect this special scenario.


Avoid performing many selects when archiving billing transactions

Our current implementation performs an ordered select query over all transactions for the month for every 1000 transactions which heavily loads the database and is very slow.

Old but good write-up of the underlying issues -- http://thebuild.com/blog/2010/12/13/very-large-result-sets-in-django-using-postgresql/

The djorm-ext-core module can be found at https://github.com/niwinz/djorm-ext-core and supports both Django<=1.6  and Django>=1.6.

Ready for review.
Any thoughts on how to test that the server side cursor is actually being used would be appreciated because I don't have any great ideas for that.

Bleh. It looks like djorm-core-ext is thoroughly broken on Django 1.5.8. I will need to fix this up.

Ah, it appears that things were not as dire as they first seemed -- we just needed a newer version of psycopg2.

Ready for re-review.

The new pyscopg2 version was needed because the withhold argument to cursor was added in 2.4.3 -- see http://initd.org/psycopg/docs/cursor.html?highlight=withhold#cursor.withhold.

There's no real way that we can test memory usage during a test is there? We could use resource, but I'm not sure how reliable it would be.

I was hoping I could inspect Django's model cache directly, but I couldn't
find a way that didn't involve grubbing around in lots of private
attributes on Django classes. We could use gc.get_objects() and look for
instances of the model.

Okay then :+1: from me. Wondering if we could could create a large table on solo using a Django shell, then running this and watching memory.


Code not passing despite correct output

Challenge Title Case a Sentence has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

var firstLetters = [];
var lastLetters = [];

function titleCase(str) {
  var splitString = str.split(" ");
  for (var i = 0; i < splitString.length; i++ ) {
    var firstLetter = splitString[i].charAt(0).toUpperCase();
    firstLetters.push(firstLetter);
  }

  for (var j = 0; j < splitString.length; j++ ) {
    var lastLetter = splitString[j].substr(1).toLowerCase();
    lastLetters.push(lastLetter);
  }

  for (var k = 0; k < firstLetters.length; k++) {
      firstLetters[k] += lastLetters[k];
  }

 var finalString = firstLetters.toString();
 var parsedString = finalString.replace(/,/g, " ");
 return parsedString;
}

titleCase("HERE IS MY HANDLE HERE IS MY SPOUT");

@CoryARamirez thanks for the issue. You have global variables in your code. Our challenge tests run your function over and over and if you have any global variables, they will change with each test. So move your global variables to within your function and your code will pass. Happy coding!


show instagram user information

please add variable in template for use to show instagram user information (follower,following,posts).
thanks.

You don't need to use Instafeed for this. You can just make an AJAX request to this API endpoint using your access token: https://www.instagram.com/developer/endpoints/users/#get_users_self


[v1] Implement createIndex and deleteIndex

Problem
Need to implement createIndex and deleteIndex on the new client accessed from const client = await Pinecone.createClient(). The old client, const legacy = await new PineconeClient(); legacy.init(), should continue to work exactly as before.
These methods have the following changes from their legacy counterparts:

[x] Simpler arguments.

For createIndex, argument has been simplified from { createRequest: { name: 'foo', dimension: 256 } } to { name: 'foo', dimension: 256 }.
For deleteIndex, argument has been simplified from { indexName: 'foo' } to 'foo'

[x] Cleaned up return values. No longer return empty string '' on success. The point of the createIndex and deleteIndex methods are their side-effects (creating/deleting an index), not fetching and displaying data. So there's no need to return anything here.
[x] Concise and actionable error messages. Client-side argument validation informs the user when they have passed argument values with incorrect type.

Old: PineconeError: PineconeClient: Error calling deleteIndex: RequiredError: Required parameter requestParameters.indexName was null or undefined when calling deleteIndex.
New:  PineconeNotFoundError: Index 'baz' does not exist. Valid index names: ['foo', 'jen-numpy-test']

[x] When needed, details about server-side validation errors (e.g. invalid index name) are shown when PineconeBadRequestError is thrown.
[x] Proper stacktraces
[x] Argument types exported

Solution
This diff mostly follows the approach used in PR #66 to add new methods to the client. Some small changes were made to validation methods to improve error messaging which resulted in a lot of minor changes to assertions about error messages created in earlier commits.

The buildValidator in validator.ts now passes errors as complete sentences to the onError callback. In some cases this results in slightly longer error messages, but makes it much easier to integrate these errors into larger messages.
Moved some logic I wanted to reuse about building richer error messages with the list of available indexes out of control/describeIndex.ts and into a control/utils.ts where it could also be accessed from control/deleteIndex.ts. There's some structural similarity between these two client methods because they are both trying to act on a single index by name.

Type of Change

[x] New feature (non-breaking change which adds functionality)

Test Plan

Unit tests added included in PR, integration test suite to come in future diff
Manual tests using npm run repl

createIndex
createIndex: Happy path
> await client.createIndex({ name: 'foo', dimension: 10 })
undefined
> await client.listIndexes()
[ 'foo', 'jen-numpy-test' ]
> await client.describeIndex('foo')
{
  database: {
    name: 'foo',
    metric: 'cosine',
    pods: 1,
    replicas: 1,
    shards: 1,
    podType: 'p1.x1'
  },
  status: { ready: false, state: 'Initializing' }
}

createIndex: Argument validation
> await client.createIndex()
Uncaught:
PineconeArgumentError: Argument to createIndex has a problem. The argument must be object.
    at /Users/jhamon/workspace/pinecone-ts-client/dist/validator.js:45:15
    at /Users/jhamon/workspace/pinecone-ts-client/dist/validator.js:36:13
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:62:21
    at step (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:33:23)
    at Object.next (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:14:53)
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:4:12)
    at Client.createIndex (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:57:40)
> await client.createIndex({})
Uncaught:
PineconeArgumentError: Argument to createIndex has a problem. The argument must have required property 'name'. The argument must have required property 'dimension'.
    at /Users/jhamon/workspace/pinecone-ts-client/dist/validator.js:45:15
    at /Users/jhamon/workspace/pinecone-ts-client/dist/validator.js:36:13
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:62:21
    at step (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:33:23)
    at Object.next (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:14:53)
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:4:12)
    at Client.createIndex (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:57:40)
> await client.createIndex({ name: 0, dimension: 0})
Uncaught:
PineconeArgumentError: Argument to createIndex has a problem. The property 'name' must be string. The property 'dimension' must be >= 1.
    at /Users/jhamon/workspace/pinecone-ts-client/dist/validator.js:45:15
    at /Users/jhamon/workspace/pinecone-ts-client/dist/validator.js:36:13
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:62:21
    at step (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:33:23)
    at Object.next (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:14:53)
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:4:12)
    at Client.createIndex (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:57:40)

createIndex: Accepts and passes optional configuration values
> await client.createIndex({ name: 'bar', dimension: 10, metric: 'dotproduct', pods: 2, podType: 'p1.x2'})
undefined
> await client.describeIndex('bar')
{
  database: {
    name: 'bar',
    metric: 'dotproduct',
    pods: 2,
    replicas: 1,
    shards: 2,
    podType: 'p1.x2'
  },
  status: { ready: false, state: 'Initializing' }
}

createIndex: When validations performed on the backend fail
> await client.createIndex({ name: 'foo-', dimension: 10 })
Uncaught:
PineconeBadRequestError: Invalid value: "foo-": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')
    at mapHttpStatusError (/Users/jhamon/workspace/pinecone-ts-client/dist/errors/http.js:127:20)
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:76:59
    at step (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:33:23)
> await client.createIndex({ name: 'quux', dimension: 10, podType: 'unknown-pod-type' })
Uncaught:
PineconeBadRequestError: Unsupported value: "unknown-pod-type": supported values: "c1", "c1.x1", "c1.x2", "c1.x4", "c1.x8", "c1.x16", "c1.x32", "p1", "p1.x1", "p1.x2", "p1.x4", "p1.x8", "p2", "p2.x1", "p2.x2", "p2.x4", "p2.x8", "s1", "s1.x1", "s1.x2", "s1.x4", "s1.x8", "s1h", "s1h.x1", "s1h.x2", "s1h.x4", "s1h.x8", "s2", "s2.x1", "s2.x2", "s2.x4", "s2.x8"
    at mapHttpStatusError (/Users/jhamon/workspace/pinecone-ts-client/dist/errors/http.js:127:20)
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:76:59
    at step (/Users/jhamon/workspace/pinecone-ts-client/dist/control/createIndex.js:33:23)

deleteIndex
deleteIndex: happy path
> await client.listIndexes()
[ 'foo', 'jen-numpy-test' ]
> await client.deleteIndex('foo')
undefined
> await client.listIndexes()
[ 'jen-numpy-test' ]

deleteIndex: validations
> await client.deleteIndex()
Uncaught:
PineconeArgumentError: Argument to deleteIndex has a problem. The argument must be string.
    at /Users/jhamon/workspace/pinecone-ts-client/dist/validator.js:45:15
    at /Users/jhamon/workspace/pinecone-ts-client/dist/validator.js:36:13
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/deleteIndex.js:63:21
    at step (/Users/jhamon/workspace/pinecone-ts-client/dist/control/deleteIndex.js:44:23)
    at Object.next (/Users/jhamon/workspace/pinecone-ts-client/dist/control/deleteIndex.js:25:53)
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/deleteIndex.js:19:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/jhamon/workspace/pinecone-ts-client/dist/control/deleteIndex.js:15:12)
    at Client.deleteIndex (/Users/jhamon/workspace/pinecone-ts-client/dist/control/deleteIndex.js:58:42)

deleteIndex: When requests fail (e.g. 404)
> await client.deleteIndex('quux')
Uncaught:
PineconeNotFoundError: Index 'quux' does not exist. Valid index names: ['foo', 'jen-numpy-test']
    at mapHttpStatusError (/Users/jhamon/workspace/pinecone-ts-client/dist/errors/http.js:131:20)
    at /Users/jhamon/workspace/pinecone-ts-client/dist/control/deleteIndex.js:82:63
    at step (/Users/jhamon/workspace/pinecone-ts-client/dist/control/deleteIndex.js:44:23)

Open question:

When creating index from a collection, should dimension still be required? Seems like probably not.

Merging because tests are green, but if there's any post-merge feedback I can create a follow-up.


Create striped logical volume for multiple disks

linear volume will be created when using lvcreate without -i switch. We should create striped volume for better IO performance, the number should be same as the underlying disk number, in this case is 2.

@ShiyangQiu : Thanks for your contribution! The author, @MSSedusch, has been notified to review your proposed change.

The LVM steps are just an example and in real cases, customers might have more disks. Can you add a description to the paragraph that 2 needs to be adapted and make it bold?

@ShiyangQiu : Thanks for your contribution! The author, @MSSedusch, has been notified to review your proposed change.

okay, i add a description for the -i switch

@MSSedusch Does this PR look okay for sign off now, please?

I am not sure if this change is really needed. During my tests I did not need to provide this parameter and got the expected performance anyway. @ShiyangQiu  are you sure this is required? Maybe -i defaults to the number of physical disks and is only required when you dont want to use all disks?

Without -i switch, the LV will be linear LV than striped one.
From: Sebastian Max Dusch<EMAIL_ADDRESS>Sent: Tuesday, May 8, 2018 6:49 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Shiyang Qiu (QQ<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Create striped logical volume for multiple disks (#7079)
I am not sure if this change is really needed. During my tests I did not need to provide this parameter and got the expected performance anyway. @ShiyangQiuhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FShiyangQiu&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222819232&sdata=jzq0gMTVSK8piI54jlanQDfxRSOv%2Bf12VCMCxSWd1OA%3D&reserved=0 are you sure this is required? Maybe -i defaults to the number of physical disks and is only required when you dont want to use all disks?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F7079%23issuecomment-387363099&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222829240&sdata=RxdtU%2B230XVExgsWrJjqK%2BWGjNjnZxrtXFvhaEtdLto%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPXZZBRW-P38Sv_H_VOyVVFUQy4eTFvNks5twXgIgaJpZM4TRctT&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222829240&sdata=xjOgfq41Wqk%2BXAXw01HA5bVqbJChZxR5KUtMlFznBFQ%3D&reserved=0.

Let me test again and update the team.
From: Shiyang Qiu (QQ)
Sent: Friday, May 11, 2018 4:29 PM
To: 'MicrosoftDocs/azure-docs'<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] Create striped logical volume for multiple disks (#7079)
Without -i switch, the LV will be linear LV than striped one.
From: Sebastian Max Dusch <notifications<EMAIL_ADDRESS>Sent: Tuesday, May 8, 2018 6:49 PM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Shiyang Qiu (QQ) <Shiyang.Qiu<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Create striped logical volume for multiple disks (#7079)
I am not sure if this change is really needed. During my tests I did not need to provide this parameter and got the expected performance anyway. @ShiyangQiuhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FShiyangQiu&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222819232&sdata=jzq0gMTVSK8piI54jlanQDfxRSOv%2Bf12VCMCxSWd1OA%3D&reserved=0 are you sure this is required? Maybe -i defaults to the number of physical disks and is only required when you dont want to use all disks?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F7079%23issuecomment-387363099&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222829240&sdata=RxdtU%2B230XVExgsWrJjqK%2BWGjNjnZxrtXFvhaEtdLto%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPXZZBRW-P38Sv_H_VOyVVFUQy4eTFvNks5twXgIgaJpZM4TRctT&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222829240&sdata=xjOgfq41Wqk%2BXAXw01HA5bVqbJChZxR5KUtMlFznBFQ%3D&reserved=0.

The testing result: without -i switch, the LV will be linear LV than striped one.
From: Shiyang Qiu (QQ)
Sent: Friday, May 11, 2018 4:40 PM
To: 'MicrosoftDocs/azure-docs'<EMAIL_ADDRESS>'MicrosoftDocs/azure-docs'<EMAIL_ADDRESS>Cc: 'Mention'<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] Create striped logical volume for multiple disks (#7079)
Let me test again and update the team.
From: Shiyang Qiu (QQ)
Sent: Friday, May 11, 2018 4:29 PM
To: 'MicrosoftDocs/azure-docs'<EMAIL_ADDRESS>MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Mention <mention<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] Create striped logical volume for multiple disks (#7079)
Without -i switch, the LV will be linear LV than striped one.
From: Sebastian Max Dusch <notifications<EMAIL_ADDRESS>Sent: Tuesday, May 8, 2018 6:49 PM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Shiyang Qiu (QQ) <Shiyang.Qiu<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Create striped logical volume for multiple disks (#7079)
I am not sure if this change is really needed. During my tests I did not need to provide this parameter and got the expected performance anyway. @ShiyangQiuhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FShiyangQiu&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222819232&sdata=jzq0gMTVSK8piI54jlanQDfxRSOv%2Bf12VCMCxSWd1OA%3D&reserved=0 are you sure this is required? Maybe -i defaults to the number of physical disks and is only required when you dont want to use all disks?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F7079%23issuecomment-387363099&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222829240&sdata=RxdtU%2B230XVExgsWrJjqK%2BWGjNjnZxrtXFvhaEtdLto%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPXZZBRW-P38Sv_H_VOyVVFUQy4eTFvNks5twXgIgaJpZM4TRctT&data=02|01|shiyang.qiu%40microsoft.com|33b9abed7c8a4de86ae508d5b4d142eb|72f988bf86f141af91ab2d7cd011db47|1|0|636613733222829240&sdata=xjOgfq41Wqk%2BXAXw01HA5bVqbJChZxR5KUtMlFznBFQ%3D&reserved=0.

ok, you are right, the -i is needed. Thanks!
#sign-off


Improved dialog text rendering

This PR ports over the latest text rendering changes from SMZ3.
It allows for up to 19 characters per line of text and supports arbitrary mapping of characters to user-defined graphics.
It also adds support for inverted colors by setting bit $10 when selecting a color.
Included is a new font with lowercase letter made by kan and me and the character table mappings to use it.
The patch also includes support for true VWF rendering, but using that would require different font graphics and changes to the character mapping table.
Using this properly would also require some changes in the main randomizer to account for the extended amount of characters per line, as well as changing the text to use lowercase letters.

This was something that was discussed as a possible inclusion in a future update, so figured I'd make a PR to make it easy to include in that case.

Added a commit that puts this feature behind a feature flag that requires -DFEATURE_NEW_TEXT=1 to be passed to asar to be included.


print() single map values

BEGIN
{
  @x[1] = 1;
  print(@x[1])
}

This script errors out with: The map passed to print() should not be indexed by a key.
printf is able to print a single map value - print should be able to as well.

Agreed.


Deleting, then attempting to recreate a namespace using the AzurePrep project causes the namespace creation process to hang

I'm preparing for another demo of the CTD project tomorrow, and I encountered, for the second time, an issue with the namespace creation process. Because the Streaming Analytics preview does not appear to support the US East data center, where I had pointed the AzurePrep project initially, I had to delete the namespace and event hubs that I created, and re-create them in US East 2.
When I ran the AzurePrep project the second time, and attempted to create a namespace with the same name as I used initially, the namespace creation process hung, with the console app repeatedly printing:
"Namespace [NAMESPACENAME]-ns in state Activating. Waiting..."
and the management portal showing the namespace in "Activating" state. As of writing this, the portal is still showing this after more than a half hour of waiting. The last time this occurred, I was eventually able to delete the namespace, but for the moment, the management portal does not even show that option.
I can't tell at this point whether moving from one datacenter to another is a necessary part of the repro, but here are the rough steps:

Run the AzurePrep app, and create the namespace in the desired subscription and datacenter.
Delete the newly-created namespace from the Azure management portal.
Run the AzurePrep app again, and attempt to create a namespace of the same name as step 1, in a different datacenter (I used US East initially, and US East 2 the second time).

As additional information, if I kill the console window that is showing the hung namespace activation, and run the AzurePrep app again, using a different namespace name, but the same datacenter as where the hang occurred, the namespace creation works normally, and completes almost instantly.

Update. An hour later, the hung namespace is finally active, and able to be deleted.

Tried to do the same and get this long activating too. Looks like Azure's internal specific - AzurePrep just shows status requsted from Azure, and it actually the same as shown at management portal, used to test it deleted from portal as well as from ClearResources tool. Unfortunally, do not have an idea whether it is by design or not, but most likely is.


Run dependency before lint on test_sequence

Avoids failure to run linting due to missing dependencies, like ansible modules or roles.
Fixes: #1908

@cloudnull @ekultails @gabrielecerami please review this.


Uncaught std::stoi error

In the file toviec.cpp line 26, it show that you don't handle the std::stoi error about large number (std::out_of_range)
operations.push_back(Operation(OperationType::PUSH, std::stoi(token)));

The input file:
99999999999999

Solution:
1 - Try handle it and give the user error about integer too big
2 - Use multiprecision library such as mpir or boost.multiprecision
Note: multiprecision maybe slower than pure int

In the file toviec.cpp line 26, it show that you don't handle the std::stoi error about large number (std::out_of_range)
operations.push_back(Operation(OperationType::PUSH, std::stoi(token)));

The input file:
99999999999999

Solution: 1 - Try handle it and give the user error about integer too big
2 - Use multiprecision library such as mpir or boost.multiprecision
Note: multiprecision maybe slower than pure int

In will give too bin int error but not multi precision. It will be fixed in next commit!

Fixed https://github.com/Jaysmito101/tovie/commit/07785ebe65340cba165b14d9bf642b65a860b1fe


Metal buffer views of depth/stencil formats

There is a (blocker) problem encountered in OSX CTS work, occurring in create_buffer_view. When the format requested is depth/stencil, metal validation error complains that those can't be linear (exact error to be provided here).
Test name: api.buffer_view.create.suballocation.uniform.d16_unorm"
Given that the Vulkan spec only allows OUT_OF_MEMORY errors from this function, and issuing those stops any further CTS runs, this is sort of a blocker for OSX CTS coverage tracking.
Possible ways to solve this:

try returning a different error for portability specifically
try convincing Metal that it's fiiine
implement a real workaround in Metal backend to support these cases

Edit: returning VK_INCOMPLETE seems to work, lowering priority

We need to handle compressed textures somehow too, i.e. block compression (BCx):

Test case 'dEQP-VK.api.buffer_view.create.suballocation.uniform.bc1_rgb_unorm_block'..
validateStrideTextureParameters:1165: failed assertion `Linear texture: cannot create compressed, depth, or stencil textures, pixelFormat (MTLPixelFormatBC1_RGBA) disallowed'


Segmentation fault when upgrading to v1.23.6

Environmental Info:
K3s Version: v1.23.6+k3s1
Node(s) CPU architecture, OS, and Version:
Linux  5.4.0-1059-raspi #67-Ubuntu SMP PREEMPT Mon Apr 11 14:16:01 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
Cluster Configuration:
1 master, 1 node
Describe the bug:
Unable to upgrade from v1.22.7+k3s1 to v1.23.6+k3s1, after running the install k3s encounters a segmentation fault when starting containerd.
Steps To Reproduce:
Upgrade k3s using the stable channel
Additional context / logs:
May 05 10:04:44 rpi1 k3s[7253]: time="2022-05-05T10:04:44Z" level=info msg="Module overlay was already loaded"
May 05 10:04:44 rpi1 k3s[7253]: time="2022-05-05T10:04:44Z" level=info msg="Module nf_conntrack was already loaded"
May 05 10:04:44 rpi1 k3s[7253]: time="2022-05-05T10:04:44Z" level=info msg="Module br_netfilter was already loaded"
May 05 10:04:44 rpi1 k3s[7253]: time="2022-05-05T10:04:44Z" level=info msg="Module iptable_nat was already loaded"
May 05 10:04:44 rpi1 k3s[7253]: W0505 10:04:44.424244    7253 sysinfo.go:203] Nodes topology is not available, providing CPU topology
May 05 10:04:44 rpi1 k3s[7253]: time="2022-05-05T10:04:44Z" level=info msg="Logging containerd to /var/lib/rancher/k3s/agent/containerd/containerd.log"
May 05 10:04:44 rpi1 k3s[7253]: time="2022-05-05T10:04:44Z" level=info msg="Running containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd"
May 05 10:04:44 rpi1 k3s[7253]: containerd: signal: segmentation fault
May 05 10:04:44 rpi1 systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
May 05 10:04:44 rpi1 systemd[1]: k3s.service: Failed with result 'exit-code'.
May 05 10:04:44 rpi1 systemd[1]: Failed to start Lightweight Kubernetes.

Can roll back to the previous stable version without issue.

What version of Ubuntu are you using? What model Pi is this? I'm unable to replicate this on my device.

Hi @brandond it's a Raspberry Pi 4 Model B Rev 1.2 running Ubuntu 20.04.4 LTS.

Can you run that same containerd command from the command line?
/var/lib/rancher/k3s/data/current/bin/containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd

@AlexLast  Could you provide the steps you have followed to upgrade? I am not able to reproduce the issue. I tried upgrading from v1.22.7+k3s1 to v1.23.6+k3s1
Device:
$ cat /sys/firmware/devicetree/base/model
Raspberry Pi 4 Model B Rev 1.2

Fresh install
curl -fL https://get.k3s.io | INSTALL_K3S_VERSION=v1.22.7+k3s1 sh -s - server

ubuntu@ubuntu:~$ kubectl get nodes
NAME     STATUS   ROLES                  AGE     VERSION
ubuntu   Ready    control-plane,master   4m49s   v1.22.7+k3s1
ubuntu@ubuntu:~$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   local-path-provisioner-84bb864455-xlgjp   1/1     Running     0          4m44s
kube-system   coredns-96cc4f57d-j7k45                   1/1     Running     0          4m44s
kube-system   metrics-server-ff9dbcb6c-rnfvb            1/1     Running     0          4m44s
kube-system   helm-install-traefik-crd--1-f6fxj         0/1     Completed   0          4m44s
kube-system   helm-install-traefik--1-r4wcr             0/1     Completed   2          4m44s
kube-system   svclb-traefik-4l8qz                       2/2     Running     0          75s
kube-system   traefik-56c4b88c4b-wgfh2                  1/1     Running     0          75s

Upgrade:
curl -fL https://get.k3s.io | INSTALL_K3S_VERSION=v1.23.6+k3s1

ubuntu@ubuntu:~$ kubectl get nodes
NAME     STATUS   ROLES                  AGE   VERSION
ubuntu   Ready    control-plane,master   17m   v1.23.6+k3s1
ubuntu@ubuntu:~$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   local-path-provisioner-84bb864455-xlgjp   1/1     Running     0          17m
kube-system   metrics-server-ff9dbcb6c-rnfvb            1/1     Running     0          17m
kube-system   coredns-d76bd69b-kd7fb                    1/1     Running     0          11m
kube-system   svclb-traefik-z88qz                       2/2     Running     0          11m
kube-system   helm-install-traefik-44prn                0/1     Completed   0          11m
kube-system   helm-install-traefik-crd-fppl7            0/1     Completed   0          11m
kube-system   traefik-df4ff85d6-vnn7l                   1/1     Running     0          9m38s
ubuntu@ubuntu:~$

Tried on a two node, 1 server 1 agent cluster
Fresh install two node:
ubuntu@ubuntu:~$ kubectl get nodes
NAME     STATUS   ROLES                  AGE     VERSION
ubuntu   Ready    control-plane,master   7m19s   v1.22.7+k3s1
rpi2     Ready    <none>                 75s     v1.22.7+k3s1

Upgrade two node:
ubuntu@ubuntu:~$ kubectl get nodes
NAME     STATUS   ROLES                  AGE     VERSION
ubuntu   Ready    control-plane,master   12m     v1.23.6+k3s1
rpi2     Ready    <none>                 6m31s   v1.23.6+k3s1

@AlexLast it sounds like there might be something wrong with your node. You might try doing rm -rf /var/lib/rancher/k3s/data and restarting K3s to see if re-extracting the containerd binary fixes anything. If not, check for kernel updates, make sure your power supply isn't cutting out, SD card isn't going bad, all the usual stuff that can causes crashes on a Pi.

Thanks both, the rm -rf /var/lib/rancher/k3s/data before installing seemed to do the trick


aelf-docs: add privatekey instruction in playground tutorial doc

https://github.com/AElfProject/aelf-docs/pull/324


Use runfromprocess-rs all the time

Fixes #24

I think we should have a github action in place to update the current image  with the new entrypoint.sh if it has changed.
As per now this will cause a full rebuild :cry:
Maybe some logic that does the following:

Checkout the repo.
Downloads the latest zwift container
docker run -d -t zwift netbrain/zwift:latest sleep infinity
docker cp zwift:/bin/entrypoint /tmp/entrypoint
diff entrypoint.sh /tmp/entrypoint
if exit code == 0, then the files are equal, if exit code == 1 then continue to next step
docker cp entrypoint.sh zwift:/bin/entrypoint
docker commit -m "$git message? or something hardcoded" -c "need to change the command" zwift netbrain/zwift:latest
docker tag netbrain/zwift:latest netbrain/zwift:$VERSION
docker push netbrain/zwift:latest && docker push netbrain/zwift:$VERSION
:partying_face:

Should also look into which files we should to this diff comparison against. Maybe even the runfromprocess-rs if it ever changes.
Thoughts?

Looks like the files required to be checked as of now is the runfromprocess-rs files, zwift-auth.sh and entrypoint.sh
Could probably also reorganize the repo a bit, so that all files used in the container is in it's own folder.
Would make diffing easier i guess.

It should probably be both sh scripts only.
runfromprocess-rs doesn't belong in the repo, and it's unlikely to change.

Could you elaborate on the "doesn't belong in the repo" part? Do you mean
it was a mistake to include the source code?
I'm open for changes, if you provide some argumentation for your stance on
this.
On Mon, Sep 18, 2023, 14:38 quietvoid @.***> wrote:

It should probably be both sh scripts only.
runfromprocess-rs doesn't belong in the repo, and it's unlikely to change.
—
Reply to this email directly, view it on GitHub
https://github.com/netbrain/zwift/pull/25#issuecomment-1723323473, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACTNC5UKZHUDAM3CDUMRNLX3A6DPANCNFSM6AAAAAA43VJDEM
.
You are receiving this because you commented.Message ID:
@.***>

Do you mean it was a mistake to include the source code?

Yes, there's no good reason to do that when you can just clone on build.
https://github.com/quietvoid/zwift/commit/cdd7f97c58654a05fddb56b63a102a6825dbc087#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557R10

Im fine with that as long as you promise to never delete the repo :)

The alternative is that you can just fork it, retag and use your fork.
I don't really care.


[Web] TypeError: undefined is not an object (evaluating 'dart.global.crypto.subtle.generateKey')

I'm trying to write a value into the storage:
await secureStorage.write(key: 'authDetails', value: jsonEncode(authDetails.toJson()));

and getting this error:
TypeError: undefined is not an object (evaluating 'dart.global.crypto.subtle.generateKey') 0m (dart_sdk.js, line 29145)
#0   packages/flutter_secure_storage_web/flutter_secure_storage_web.dart.js 136:59   write [0m (dart_sdk.js, line 29145)

flutter_secure_storage 8.1.0
Seems to happen only on mobile browsers: Safari, Chrome. iOS 17.0.3.

facing same issue on iOS browser.

I am closing all older issues. If this issue still exists in the latest version, please let me know.

Am facing a very similar, issue. In this case unable to setup notifications.


Revision doesn't work

I'm using a demo installation right now.
By default, 'Icon' entity already has 'Revision' on.
When I try to update an entity I get the next error:
Symfony \ Component \ Debug \ Exception \ FatalThrowableError (E_ERROR)
Call to undefined method Illuminate\Events\Dispatcher::fire()
…/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php237
I've also tried to add Revision behavior to another entity, but the same.

Hi @PeterKravets ,
Thanks for the issue. You're right, there was an error with the Revisions functionality after the update - the revisions package did not support Laravel 5.8. That's been fixed now, I've just run composer update on the demo and it works now. I've pushed the fix onto the demo.
Please run composer update on your project. That should fix it. Let me know if it doesn't.
Cheers!

There is no issue during update anymore.
But there is an error, when I go to the 'Revisions' page
Class 'Date' not found (View: /home/peter/backpack-demo/vendor/backpack/crud/src/resources/views/inc/revision_timeline.blade.php) (View: /home/peter/backpack-demo/vendor/backpack/crud/src/resources/views/inc/revision_timeline.blade.php)

Hmmm.... Weird, I'm not getting any such error. What versions are you running? Can you please copy-paste the output of php artisan backpack:base:version?

backpack/base                            1.1.5
backpack/crud                            3.6.24
backpack/newscrud                        2.1.10
backpack/permissionmanager               4.0.4
laravel/framework                        v5.8.30

My 2 cents:
It's because Date was removed for Carbon instead.
Try not adding a Date alias in your config/app.php but check if you have not overridden the revision_timeline template in \resources\views\vendor\backpack\crud\inc\revision_timeline.blade.php


[Docs]: Update Discord links and fix cards

Type
Bug report
What do you want to report?
We have enabled a verification step in Discord to prevent spam. A new invite link was generated. Also fix the height of the homepage cards
Code of Conduct

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

Pushed to prod. Old Discord invite link has been disabled


Development to Master (version update v0.0.4 to v0.0.5)

This merge will incorporate the following changes listed from CHANGELOG.md as v0.0.4 in Master. It's been a while since our last update with version 0.0.3 (April 25th, 2023), but lots of new features been added. See below.
Note to Developers: In case you're encountering errors with regards to userlist.ttl such as not being able to delete users or see the person's webId, it might mean that you're still using an older version of userlist.ttl. In this update, userlist.ttl has been revamped to handle new input fields in a slightly different manner. To reset the userlist.ttl, simply delete it from your Solid Pod under Users, log out of PASS and log back in. A new userlist.ttl will be generated for you in the Pod and you'll be able to add/delete users again.
Visual Changes Since v0.0.4
Home

Clients (formerly Home)

Forms

Inbox

Outbox

CHANGELOG - v0.0.5 (June 7, 2023)
Features

Updated UI for UserList and ManageUser with ClientList and AddClientModal (#209)
Generate PASS specific inbox and public container if it doesn't exist upon login (#201)
Render sent message in outbox (#191)
Include pagination for messages in inbox/outbox (#191)
Generate user outbox on log in if outbox does exist in user's Solid Pod (#186)
Using webIds instead of username as primary identifier (#169)
Allow users to choose different Solid Identity Providers when using PASS (#167)
Updated/Enhanced UI for Footer, Inactivity Notification, Client List, Form components, etc. (#166, #172, #178, #180, #187, #193, #206, #209, #210)
Render user messages from their Solid inbox on PASS (#148)

Fixes

Refactored src/model-helpers/User.js to update user activity correctly (#191, #214)
Corrected type in CrossPodWriteForm to use Upload instead of Search (#183)
Included corrections to JSDoc comments (#148, #179, #183, #184, #201)

Dev Changes

Refactored all PASS related contexts to UserDataContext (#214)
Refactored React Contexts for messages to MessageContext (#214)
Include SignInUserContext for storing podUrl to be used in PASS (#214)
Refactored fetchData and App.jsx (#214)
Include top level mock directory to simplify module mocks in unit tests (#211)
Refactoring custom hooks into individual files (#204)
Replaced UPLOAD_TYPES with INTERACTION_TYPES (#202)
Refactored PASS routing with AppRoutes and ProtectedRoutes (#198)
Created function to generate an outbox container for users if it doesn't exist in their Solid Pod (#186)
Optimized session-helper functions (#184)
Refactored set permission forms to pass in Access Object as a parameter to setDocAclPermission function (#183)
Updated all relevant components/functions using createDocAclForUser with new setDocAclForUser function (#183)
Optimized session-core functions (#183)
Included new JSDoc for new barcode scanner functions (#179)
Updated clearDoc.js and .gitignore to accomedate for new ZXing_barcaode.md (#179)
Organized utils directory into 4 subdirectories and rerouted import paths (#171)
Refactored contexts for userList from session-core to src/modal-helpers (#169)
Replaced removeKeys function with localStorage.clear (#167)
Replaced previous Login component with OidcLoginComponent (#167)
Created new test directory to store unit tests (#167)
Generate loading text for when user messages are being loaded from Solid (#148)
Removed types.d.ts in favor of better written JSDoc comments (#148)
Created new React Context and components for rendering inbox messages (#148)
Created new getInboxMessageTTL function to pull messages from Solid as JSON from TTLs (#148)

Others

Updated package-lock.json to fix high-security vulnerabilities (#224)
Updated GitHub Actions to have lints and unit tests separate from building (#181)
Updated GitHub Actions to run newer GitHub Actions workflows and correct node version (#181)
Included new technical documentation for barcode scanner (#179)

@timbot1789 if you have time to look over this.  It's 105 changed files.
You are more than welcome to look over all of them, but I think it would be really helpful to split up.  I think for the sake of the project you would be better to review the utils, tests, and contexts files.  I'm almost done going over the rest (at 73 of 105 reviewed.)

Alright, gonna attempt some refactors for one of the issues mentioned in the comments in another PR. It's pretty sizable so I've pushed it all there #236. If it looks good @xscottxbrownx, we'll merge it into this.


Pulumi always reports Kubernetes version as changed and try to do a replace

I have created a DOKS cluster, but now every time I run pulumi preview, it says the resource needs to be updated because the version has changed:
 +-  ├─ pulumi:providers:kubernetes                                 do-k8s                    replace     [diff: ~kubeconfig]
 +-  ├─ digitalocean:index:KubernetesCluster                        k8s-cluster               replace     [diff: ~version]

Here is my cluster resource:
export const cluster = new digitalocean.KubernetesCluster("k8s-cluster", {
  region: Regions.FRA1,
  version: config.clusterK8sVersion,
  name: config.clusterName,
  nodePool: {
    name: config.clusterNodePoolName,
    size: config.clusterNodePoolSize,
    nodeCount: config.clusterNodeCount,
    tags: clusterTags
  }
});

Could you please provide the preview detailed diffs?

It seems it only happens if I specify the "latest" version.
~ version: "1.16.6-do.0" => "latest"
``

I guess because it tries to compare the "latest" with the real version of the cluster which will always be different.

The only way I see to work around this, is to check if the version specified is latest, call the DO API to get the version that corresponds to latest and compare it to the value from the cluster. Not sure if the  DO API supports this anyway.

Not a big deal. It´s better to use a specific version anyway.

Thank you. You can close this issue if you want.

Thanks for the update!


Create PERMISSIONS.md

Implemented #51

@PatrickMatthiesen When you have time, no pressure on this PR, can you check if this aligns with what we have written in the chrome web store reviews? 🎉


Avoid over-matching when converting links to text

Adding some very primitive unit tests that reproduced the problem and validate this fixes it

(deployed to test environment, doesn't appear completely right yet)

deployed to test environment, now works well for CVE-2024-23452 .
If CodeQL is green I'll merge this CTR-style as CVE-2024-23452 is otherwise ready for disclosure.


IncludeFilter issue on .NET Core 3.1

Description
Hello
After migrating solution from .NET Core 2.2 to 3.1, my EF queries started throwing exceptions. The problem occurs when I use IncludeFilter syntax. I attached project in which im facing the issue. You can find sample code in IssueController.
Exception
Exception message:InvalidOperationException: Processing of the LINQ expression 'source => (IEnumerable<SkillName>)source' by 'NavigationExpandingExpressionVisitor' failed. This may indicate either a bug or a limitation in EF Core. See https://go.microsoft.com/fwlink/?linkid=2101433 for more detailed information.

Stack trace:
fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
      An unhandled exception has occurred while executing the request.
System.InvalidOperationException: Processing of the LINQ expression 'source => (IEnumerable<SkillName>)source' by 'NavigationExpandingExpressionVisitor' failed. This may indicate either a bug or a limitatio
n in EF Core. See https://go.microsoft.com/fwlink/?linkid=2101433 for more detailed information.
   at Microsoft.EntityFrameworkCore.Query.Internal.NavigationExpandingExpressionVisitor.ProcessSelectMany(NavigationExpansionExpression source, LambdaExpression collectionSelector, LambdaExpression resultSe
lector)
   at Microsoft.EntityFrameworkCore.Query.Internal.NavigationExpandingExpressionVisitor.VisitMethodCall(MethodCallExpression methodCallExpression)
   at System.Linq.Expressions.MethodCallExpression.Accept(ExpressionVisitor visitor)
   at System.Linq.Expressions.ExpressionVisitor.Visit(Expression node)
   at Microsoft.EntityFrameworkCore.Query.Internal.NavigationExpandingExpressionVisitor.Expand(Expression query)
   at Microsoft.EntityFrameworkCore.Query.QueryTranslationPreprocessor.Process(Expression query)
   at ?.?(IQueryable ?, Action`1 ?, RelationalQueryContext& ?, Object& ?)
   at Z.EntityFramework.Extensions.EFPlusExtensions.EFPlusCreateCommand(IQueryable source, Action`1 action, RelationalQueryContext& queryContext, Object& compiledQuery)
   at Z.EntityFramework.Plus.BaseQueryFuture.CreateExecutorAndGetCommand(RelationalQueryContext& queryContext)
   at Z.EntityFramework.Plus.QueryFutureBatch.CreateCommandCombined()
   at Z.EntityFramework.Plus.QueryFutureBatch.ExecuteQueries()
   at Z.EntityFramework.Plus.QueryFutureEnumerable`1.GetEnumerator()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Z.EntityFramework.Plus.QueryIncludeFilterParentQueryable`1.CreateEnumerable()
   at Z.EntityFramework.Plus.QueryIncludeFilterParentQueryable`1.GetEnumerator()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at IncludeFilterIssue.Controllers.WeatherForecastController.Issue() in C:\Users\xdelp\Desktop\Nowy folder\IncludeFilterIssue\IncludeFilterIssue\Controllers\WeatherForecastController.cs:line 41
   at IncludeFilterIssue.Controllers.WeatherForecastController.Get() in C:\Users\xdelp\Desktop\Nowy folder\IncludeFilterIssue\IncludeFilterIssue\Controllers\WeatherForecastController.cs:line 31
   at lambda_method(Closure , Object , Object[] )
   at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target, Object[] parameters)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

Fiddle or Project
https://github.com/del77/IncludeFilterIssue
Further technical details

EF version: EF Core 3.1.3
EF Plus version: 3.0.45
Database Provider: SQL Server 15.0.2070

I can confirm had the same issue on EFPlus 3.0.50 and 3.0.51

Thank you for the project,
We successfully reproduced the issue. We will look if we can do something about it.
Best Regards,
Jon

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Any progress on this issue?

Hello all,
Sorry for the long waiting,
We believe we finally find out how to fix this issue.
The v3.0.60 has been released today with a fix which remove the cast that was working under EF Core 2.x but was throwing starting from EF Core 3.x
If anyone has the chance to test it, let us know if everything is working.

This case from the project I provided has been solved by this update. Unfortunately, extended case is still throwing for me.

@JonathanMagnan, do you think this can be still fixed?

I hope so,
However, my developer that did the latest change, unfortunately, is not available till next Monday, so I was waiting for him to come back to follow this request with him

Any update about this issue? We are migrating our application from 2.2 and we are having the same problem with some queries.

Unfortunately @rvicoqbi ,
We didn't succeed to fix it.
We will have to fully re-write this feature and doing it will highly depend on how well work the filtered include now part of EF Core 5: https://www.learnentityframeworkcore5.com/whats-new-in-ef-core-5/filtered-included

@rvicoqbi, it turned out that _context.Courses.IncludeFilter(c => c.SkillCourses.Select(sc => sc.Skill.Names)).ToList(); from the repository I provided is the only one case which doesn't work after last fixes. Therefore I decided that until we can move to EF Core 5 which should support include filtering, I will use the following workaround:
Instead of:
_context.Courses.IncludeFilter(c => c.SkillCourses.Select(sc => sc.Skill.Names)).ToList();
I used:
_context.SkillNames.Future();
_context.Courses.IncludeFilter(c => c.SkillCourses.Select(sc => sc.Skill)).ToList();

That's exactly our case @del77 but we have bigger and more complex queries similar to that. So, let's try with your workaround and let's see if we can save this ball.
Yeah @JonathanMagnan, we are aware of EF Core 5 new functionalities and thinking in doing the migration to 5 instead of 3.1 but we aren't totally sure for now, debate is open 😄.
Thanks so much to both of you guys.


Eliminate mutex in deadline_filter

This could be significantly simplified if we can guarantee that a timer won't be started without first being cancelled.
Built on #9737

I think bugs and review comments are fixed.

Failed: #9550


[FLINK-29288] Make it possible to use job jars in the system classpath

What is the purpose of the change
Allowing to use job jars located in the system classpath (e.g. /opt/flink/lib). Currently it's not possible.
Brief change log

Making spec.job.jarURI optional, removing validation.
Updating FlinkConfigBuilder to not define pipeline.jars and pipeline.classpaths if the jarURI is not specified.
Updating UserLibMountDecorator to not create a usrlib folder if pipeline.classpaths is not defined. Otherwise Flink will try to load the provided class from the usrlib folder which is empty.

Verifying this change
This change added tests and can be verified as follows:

Running updated tests: DefaultValidatorTest,  FlinkConfigBuilderTest, UserLibMountDecoratorTest.
I've also deployed an operator with a custom Docker image built based on this branch to a staging environment. I confirmed that my custom Flink Docker image with a job jar in /opt/flink/lib can be executed successfully.

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

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changes to the CustomResourceDescriptors:  no, but it does make a required parameter optional
Core observer or reconciler logic that is regularly executed: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? docs

NOTE: I find UserLibMountDecorator implementation a bit weird. It looks like right now /opt/flink/usrlib is always created in the Application mode. The class comments mention pipeline.classpaths, but it seems like the classpaths specified this way can be located anywhere.  Flink's DefaultPackagedProgramRetriever explicitly adds usrlib and pipeline.classpaths separately. In my opinion, the operator should let the user create usrlib if needed. It's not in the scope of this PR, but I'm happy to create a follow-up issue.

If I understand it correctly this would in theory also solve https://issues.apache.org/jira/browse/FLINK-29144 as a side effect :)

Also this does not address the SessionJobs as we discussed in the Slack thread with @jeesmon.

Yes, but aside from providing the "no-op" jar, which I thought is something that @jeesmon is working on separately, is there anything else that's missing here?

If I understand it correctly this would in theory also solve https://issues.apache.org/jira/browse/FLINK-29144 as a side effect :)

In a way yes, you can place multiple jars in the system classpath instead and not specify anything as jarURI.

Re: CI failure, it looks like the Maven step completed successfully ([INFO] BUILD SUCCESS), but for some reason, the run stopped with Error: Process completed with exit code 1.. Is it a known issue?

Re: CI failure, it looks like the Maven step completed successfully ([INFO] BUILD SUCCESS), but for some reason, the run stopped with Error: Process completed with exit code 1.. Is it a known issue?

Please generate the java doc via 'mvn clean install -DskipTests -Pgenerate-docs' again
Error: Process completed with exit code 1.

@gyfora Are we fine with including a pre-built jar with this PR? Just double checking :)

@gyfora Are we fine with including a pre-built jar with this PR? Just double checking :)
flink-kubernetes-operator/src/main/resources/noop.jar

yes of course, why not? :)