GRU::zero_state -> wrong shape

Hey,
The GRU::zero_state is missing a dimension which makes the seq method fail. According to the PyTorch doc, you can make it work by changing it to:
   fn zero_state(&self, batch_dim: i64) -> GRUState {
        let dim = if self.config.bidirectional { 2 } else { 1 };
        let shape = [dim * self.config.num_layers, batch_dim, self.hidden_dim];
        GRUState(Tensor::zeros(&shape, (Kind::Float, self.device)))
    }

Should be a similar problem with the LSTM struct.
Cheers

Would you have some more details on how you're using this? Maybe you want to compare your code with the seq2seq example and the char-rnn example included in tch-rs. Both examples should work fine with the current zero_state implementation (using GRU and LSTM), that said I think they probably only use num_layers=1.

Hmmm, the char-rnn example fails to run on my setup: Cloned latest repo and linked them to PyTorch C++ 1.1 libraries (libtorch).
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: TorchError { c_error: "Expected more hidden states in stacked_rnn (apply_layer_stack at ../aten/src/ATen/native/RNN.cpp:515)

Looks like there is some incoherence between seq and step (maybe this was introduced in the 1.1 release ?). Anway I would suggested using step for the time being as does the seq2seq example and everything seems to work well here - and I'll try to fix the seq behavior when I get a chance.

The PyTorch 1.1 API doc states that: The GRUCell module (used by step) take a 2-dimensional input while the GRU module ( used by seq_init) takes a 3-dimensional one. Maybe they have changed the function signatures in 1.1 as you point out.
For this reason, I find seq_init more convenient than step for doing the incremental decoding as I can work in 3D all the way through. Making the GRUState public is all I needed to do to make everything work as I initialise - a single-layer and unidirectional GRU in this case - with:
let init_state = GRUState( Tensor::zeros(&[1,batch_size,self.hidden_size], (Kind::Float, Device::Cpu)) );
let encoder_output_set = self.encoder.seq_init( &emb_x, &init_state );

These issues are simple to fix, I am happy to contribute if it helps.

By 'simple to fix', do you mean that it's easy to switch 'zero_state' to work for 'seq_init' ? I agree that this would indeed be easy to change but this would break the current seq2seq example as it relies on 'step' rather than on 'seq', so I would like to think a bit more about what this involves before making the change. 'step' could probably be implemented using 'seq' but I'm a bit unsure of the performance implications of this.
Anyway I'll try to think about it over the next few days, and I think you're right that the 3D case should be well supported - also this is probably the only way to get biderctional or multi-layered RNN to work. Another conclusion is that this part of the API should have some tests so that we catch issues earlier as it's a bit sad that examples that use to run don't work anymore.

Yes, just had a look at the code for the translation example. The problem would be on your 2 uses of the zero_state (line 127 and 158) that you directly pass to step. But the fix is as easy as using squeeze on the output of the new 3D 'zero_state' function. That would fix the seq call in the char-rnn example at the same time.

I'm afraid this would only work in the current situation but wouldn't fix the case where bidirectional is true or where num_layers is greater than one. As gru_cell and lstm_cell don't support these options anyway we should probably either not expose them or have a step implementation that supports them (which makes sense for num_layers but less for bidirectional).

Ok let's look at it this way, taking GRU as an example: A GRU is simply a vector of GRUCell. You have one cell per direction and per layer, so an initial state for the GRU is just a stacked vector of the initial 2D state for each cell, hence 3D.
Your zero_state function is currently returning the initial 2D state for a single cell but it is a method of the GRU struct which is where the inconsistency lies. Why not renaming your function to zero_state_cell and make mine as the zero_state?

Your zero_state function is currently returning the initial 2D state for a single cell but it is a method of the GRU struct which is where the inconsistency lies. Why not renaming your function to zero_state_cell and make mine as the zero_state?

Sorry I probably wasn't very clear in my previous comment but I think that there is a more profound issue behind this which is that step doesn't handle some of the options than seq does and I don't think such a change would fix it. So before handling the zero state differently I think we should rationalize the RNN trait and be clear whether or not this supports bidirectional (probably hard) and num_layers (maybe easier).

From a code architecture perspective, I think having 2 separate traits is best: RNN and RNNCell. Number of directions and number of layers would not apply to a Cell by very definition, so it would make the library very consistent.

Maybe, an other possibility would be to have RNN and RNNBidirectional as num_layers could actually apply to cells if you just stack them.
From an user perspective this may be a bit simpler as when you use RNN you would have access to both step and seq, seq is useful for training but step is actually pretty useful for inferences e.g. for things like char-rnn or more time series tasks.

After all, why would you want to expose RNNCell at all? The user can always create one using an RNN and use seq_init to go step-by-step if required (that's what I do in my seq2seq implementation). I can not think of a configuration where you would need to stack RNNCell and avoid RNN.

Yes that's actually what I meant by "'step' could probably be implemented using 'seq' but I'm a bit unsure of the performance implications of this.". I'm not sure how the performance of these compare especially on gpu so this should probably be studied a bit more in depth.
That said step doesn't make much sense for bidirectional things hence providing it only for the 'standard' rnn trait and not for the bidirectional one may make sense.

I see what you mean about step in a bidirectional setting. It can be calculated but hard to see a practical use for it. While we are on the subject, I could not get GRU to work at all in a bidirectional setting. It could be a bug in the PyTorch C++ API, I am not sure.

Actually PyTorch 1.2 just got released and hopefully include the latest fixes on the C++ side so I'll switch to using it and will give a try at bidirectional at this point.

Yep, and it looks like it has been fixed!

C++ Frontend bug fixes
nn::RNN: Fix assertions in bidirectional RNN. (22850).

I will give it a go as well.

Yep, and it looks like it has been fixed!

C++ Frontend bug fixes
nn::RNN: Fix assertions in bidirectional RNN. (22850).

I will give it a go as well.
Unfortunately, I am still getting the same inaccurate error when trying to initialise a bidirectional GRU

c_error: "Odd number of params or hiddens given to a bidirectional RNN"

Yep, and it looks like it has been fixed!

C++ Frontend bug fixes
nn::RNN: Fix assertions in bidirectional RNN. (22850).

I will give it a go as well.

Unfortunately, I am still getting the same inaccurate error when trying to initialise a bidirectional GRU
c_error: "Odd number of params or hiddens given to a bidirectional RNN"

What did you use as initial shape, something like [num_layers*2, batch, hidden] ?
I should have some time to work on this over the weekend so I'll probably give it a try too + split the bidirectional vs unidirectional rnn traits.

Yep, I followed the PyTorch doc pretty closely. Here is the code snippet:
let emb_x = self.embedding.forward( &x ); // [batch_size,seq_len,dim]
let init_state = GRUState( Tensor::zeros(&[2,batch_size,self.hidden_size], (Kind::Float, Device::Cpu)) );
let encoder_output_set = self.encoder.seq_init( &emb_x, &init_state );

with self.encoder initialised with:
encoder: nn::gru(&p, hidden_size, hidden_size, RNNConfig{ bidirectional: true, ..Default::default() })

I just pushed some changes that seem to get bidirectional and multiple layers to work on GRU.

This does not include any trait change, step is implemented in terms of seq_init.
The LSTM hasn't been adapted yet.
You can see some relevant tests at the bottom of nn_tests.rs, this should give an idea of how shape works (I haven't tested it on real life examples as I only have access to a small laptop right now).
If this seems reasonable after testing it a bit more I'll adapt the LSTM to work in a similar way.

I have updated my code to use a bidirectional GRU encoder with a 2-layer GRU decoder, and it is training well so far. Also, I have noticed that the load on CPU during training has massively decreased with this version of libtorch. Great work.


Initial work on ledger orchestrator.

Work in progress. Do not review.

@ekzhu @jackgerrits  No idea what to do with this pyright type error. Seems impossible to make a GroupChatManager that doesn't descend from BaseGroupChatManager
/home/afourney/repos/autogen/python/packages/autogen-agentchat/src/autogen_agentchat/teams/_group_chat/_ledger_orchestrator/_ledger_orchestrator.py
  /home/afourney/repos/autogen/python/packages/autogen-agentchat/src/autogen_agentchat/teams/_group_chat/_ledger_orchestrator/_ledger_orchestrator.py:25:38 - error: Argument of type "type[LedgerOrchestratorManager]" cannot be assigned to parameter "group_chat_manager_class" of type "type[BaseGroupChatManager]" in function "__init__"
    "type[LedgerOrchestratorManager]" is not assignable to "type[BaseGroupChatManager]"
    Type "type[LedgerOrchestratorManager]" is not assignable to type "type[BaseGroupChatManager]" (reportArgumentType)
  /home/afourney/repos/autogen/python/packages/autogen-agentchat/src/autogen_agentchat/teams/_group_chat/_ledger_orchestrator/_ledger_orchestrator.py:33:9 - error: Method "_create_group_chat_manager_factory" overrides class "BaseGroupChat" in an incompatible manner
    Return type mismatch: base method returns type "() -> BaseGroupChatManager", override returns type "() -> LedgerOrchestratorManager"
      Type "() -> LedgerOrchestratorManager" is not assignable to type "() -> BaseGroupChatManager"
        Function return type "LedgerOrchestratorManager" is incompatible with type "BaseGroupChatManager"
          "LedgerOrchestratorManager" is not assignable to "BaseGroupChatManager" (reportIncompatibleMethodOverride)

@ekzhu @jackgerrits No idea what to do with this pyright type error. Seems impossible to make a GroupChatManager that doesn't descend from BaseGroupChatManager
/home/afourney/repos/autogen/python/packages/autogen-agentchat/src/autogen_agentchat/teams/_group_chat/_ledger_orchestrator/_ledger_orchestrator.py
  /home/afourney/repos/autogen/python/packages/autogen-agentchat/src/autogen_agentchat/teams/_group_chat/_ledger_orchestrator/_ledger_orchestrator.py:25:38 - error: Argument of type "type[LedgerOrchestratorManager]" cannot be assigned to parameter "group_chat_manager_class" of type "type[BaseGroupChatManager]" in function "__init__"
    "type[LedgerOrchestratorManager]" is not assignable to "type[BaseGroupChatManager]"
    Type "type[LedgerOrchestratorManager]" is not assignable to type "type[BaseGroupChatManager]" (reportArgumentType)
  /home/afourney/repos/autogen/python/packages/autogen-agentchat/src/autogen_agentchat/teams/_group_chat/_ledger_orchestrator/_ledger_orchestrator.py:33:9 - error: Method "_create_group_chat_manager_factory" overrides class "BaseGroupChat" in an incompatible manner
    Return type mismatch: base method returns type "() -> BaseGroupChatManager", override returns type "() -> LedgerOrchestratorManager"
      Type "() -> LedgerOrchestratorManager" is not assignable to type "() -> BaseGroupChatManager"
        Function return type "LedgerOrchestratorManager" is incompatible with type "BaseGroupChatManager"
          "LedgerOrchestratorManager" is not assignable to "BaseGroupChatManager" (reportIncompatibleMethodOverride)

I will put in a new PR to fix this.

Looks good overall. I think exposing the n_rounds and n_stalls might be useful.

Ooops. Yeah, I forgot to wire that back up to the Team


Minor Issue - A single missing texture ; easy fix.

Thanks for reporting an issue to an Elytra project!
When reporting an issue to an Elytra project, please make sure to include:

The version of the mod you are using architecturecraft-1.12-2.68
Your Minecraft version 1.12.2
Your Forge version 1.12.2 - <IP_ADDRESS>64
The crash report or log, uploaded to gist.github.com
https://gist.github.com/P3rf3ctXZer0/8e7bc9a177e79c2aacda53db65d56d62

Same Issue for me. Would like to know if this is important or not

Welp, the only custitem occurence is here : https://github.com/elytra/ArchitectureCraft/blob/1.12/src/main/java/com/elytradev/architecture/client/render/RenderingManager.java#L399
I don't know what would happen with this line removed, tho.


asking about LCM lora

in the paper, you make image consistency model with lora,
is that the lcm_lora ?

Yep. You are right.


reverting patch issue

when i open game it reverts patches and doesnt open
i have a mac air m1
macos sonoma 14.1.2

Don't Work for ARM CPU. ㅠ_ㅠ
( Your mac use ARM CPU )
I am waiting for patch to ARM Support.....

is it available now arm support?

yes, I download that release but same issue
doesnt working :/

when i open game it reverts patches and doesnt open i have a mac air m1 macos sonoma 14.1.2

i get the same error before,
but after update to sonoma 14.4 (beta version), it can be launch the game
hope will help you

It works now on 14.4.


unpack_from requires a buffer of at least xxx bytes

I am using current master code.
I have a consumer consuming message from one Kafka topic, when some events occurred, it triggers a pure Python producer to produce some messages to another topic.
Traceback:
Traceback (most recent call last):
  File "/home/brm_index/venv/local/lib/python2.7/site-packages/brm_index/workers/base.py", line 140, in index_bulk
    to_index = self.map_docs(docs, source)
  File "/home/brm_index/venv/local/lib/python2.7/site-packages/brm_index/workers/basic.py", line 134, in map_docs
    self.on_mapped(body)
  File "/home/brm_index/venv/local/lib/python2.7/site-packages/brm_index/workers/basic.py", line 218, in on_mapped
    k: body.get(k) for k in self.relation_keys
  File "/home/brm_index/venv/local/lib/python2.7/site-packages/brm_index/workers/base.py", line 348, in schedule_relation
    json_util.dumps(message, ensure_ascii=False).encode('utf-8'))
  File "/home/brm_index/venv/local/lib/python2.7/site-packages/pykafka/producer.py", line 350, in produce
    self._raise_worker_exceptions()
  File "/home/brm_index/venv/local/lib/python2.7/site-packages/pykafka/producer.py", line 204, in _raise_worker_exceptions
    raise ex
error: unpack_from requires a buffer of at least 27949 bytes

It seems that the producer can't restore to normal state after the exception, causing the process hanging.
PyKafka version: @b2ca8eb
Kafka version: 0.9.0

Thanks @messense. I've seen this before, but I haven't been able to reproduce it reliably. It may have something to do with a lack of available memory.

@messense do you have additional logs from before the traceback? There should be another traceback just before this one in the logs that shows where in the worker thread this error originated.

@emmett9001 No, no traceback logs from before the traceback.

I changed to rdkafka based producer and it works good for now.
But I think the cause of this is some network connections got stucked as we have a lot of API requests in our program and some of them didn't set timeout policy.

@messense Though I can't prove it, I think this may be caused by a lack of available memory in your python interpreter. This seems to jibe with your description of hung API requests.

I don't think this has to do with memory, @emmett9001. And, we're seeing this issue in production at Parse.ly now, so re-opening the issue.

I have the same problem，maybe you can increase the "fetch_message_max_bytes", in pykafka/utils/struct_helpers.py:_unpack() function, items.extend(struct.unpack_from('!' + ch, buff, offset)) raise the problem, i find increase fetch_message_max_bytes maybe increase the buff length.

I'm able to reproduce this reliably with the following code:
https://gist.github.com/hbbtstar/f3663299f12f97de170369c49a2f1d54
The traceback I get from that code is this:
Traceback (most recent call last):
  File "get_random_crawled_urls.py", line 22, in <module>
    msg = consumer.consume()
  File "/home/alourenco/pykafka/pykafka/simpleconsumer.py", line 483, in consume
    self._raise_worker_exceptions()
  File "/home/alourenco/pykafka/pykafka/simpleconsumer.py", line 276, in _raise_worker_exceptions
    reraise(*self._worker_exception)
  File "/home/alourenco/.pyenv/versions/3.6.6/envs/casterisk-realtime3/lib/python3.6/site-packages/six.py", line 686, in reraise
    raise value
  File "/home/alourenco/pykafka/pykafka/simpleconsumer.py", line 440, in fetcher
    self.fetch()
  File "/home/alourenco/pykafka/pykafka/simpleconsumer.py", line 804, in fetch
    min_bytes=self._fetch_min_bytes
  File "/home/alourenco/pykafka/pykafka/broker.py", line 45, in wrapped
    return fn(self, *args, **kwargs)
  File "/home/alourenco/pykafka/pykafka/broker.py", line 327, in fetch_messages
    return future.get(response_class, broker_version=self._broker_version)
  File "/home/alourenco/pykafka/pykafka/handlers.py", line 76, in get
    return response_cls(self.response, **response_kwargs)
  File "/home/alourenco/pykafka/pykafka/protocol/fetch.py", line 216, in __init__
    broker_version=broker_version)
  File "/home/alourenco/pykafka/pykafka/protocol/fetch.py", line 157, in __init__
    response = struct_helpers.unpack_from(fmt, buff, offset)
  File "/home/alourenco/pykafka/pykafka/utils/struct_helpers.py", line 49, in unpack_from
    output = _unpack(fmt, buff, offset, 1)[0]
  File "/home/alourenco/pykafka/pykafka/utils/struct_helpers.py", line 79, in _unpack
    offset + 4, count)
  File "/home/alourenco/pykafka/pykafka/utils/struct_helpers.py", line 115, in _unpack_array
    item, offset = _unpack(fmt, buff, offset)
  File "/home/alourenco/pykafka/pykafka/utils/struct_helpers.py", line 96, in _unpack
    items.extend(struct.unpack_from('!' + ch, buff, offset))
struct.error: unpack_from requires a buffer of at least 24951 bytes

The machine in question has about 6GB of RAM free at the moment, so as far as I can tell it's not a memory issue.

Also, as an aid, I logged out the ch offset, and buff variables when the exception occurs:
ch is 24951s
offset is 10
bytearray(b'\x00\x00\x00\x01\x00\rcrawled_items\x00\x00\x00\x04\x00\x00\x00\x03\x00\x00\x00\x00\x00\x00\x05P\xaaf\x00\x00\x00\x00\x00\x00\x00\x08\x00\x00\x00\x00\x00\x00\x07\xfc\x0c\x88\x00\x00\x01\x9b\x00\x00\x00\x00\x07\xfc\x0c\x87\x00\x00\x01\x8f;w\xfd\xea\x00\x02\xff\xff\xff\xff\x00\x00\x01\x81\x82SNAPPY\x00\x00\x00\x00\x01\x00\x00\x00\x01\x00\x00\x01m\xbb\x05\xf0H\x00\x00\x00\x00\x07\xfc\x0c\x87\x00\x00\x02\xaf\x8f\x8f\x91\xad\x00\x00\xff\xff\xff\xff\x00\x00\x02\xa1{"apikey": "herald-review.com", "canonical_url"\x01&\x1cttps://h>.\x00\xf0r/business/dewitt-county-board-gives-wind-farm-developer-a-victory/article_651e6817-0674-5648-b818-195661ee1aaf.html\x01\xa14response_link"\xfe\xa1\x00\xfe\xa1\x00J\xa1\x00<diff": [["change\x01\xb59V\x14hash64\x01\x14(TrmItu39Ttg>\x0f\x00\x08], f>\x00\x01-\x14Ea9br1\x1d\np]], "ts":<PHONE_NUMBER>026, "url\x01\x17\x04["\xfe\xc9\x01\xfe\xc9\x012\xc9\x01\x01\xafPcontent_type": "url"}\x00\x00\x00\x0c\x00\x00\x00\x00\x00\x00\x05U4\xfd\x00\x00\x00\x00\x00\x00\x00\x10\x00\x00\x00\x00\x00\x00\x05v\xc6?\x00\x00\x00\x00\x00\x00\x00\x00')

the ch string there seems weird to me- from the struct docs, that means we're trying to unpack a 29451 byte string? that seems huge to me, but I'm only dimly knowledgeable about the whole struct / memoryview business.

This happens after I reset offsets using our little helper script.
Traceback (most recent call last):
  File "/data/virtualenvs/casterisk/bin/reset_offsets", line 11, in <module>
    load_entry_point('casterisk', 'console_scripts', 'reset_offsets')()
  File "/data/apps/cogtree/builds/casterisk/20180824_00_633ee536ce/casterisk/scripts/reset_offsets.py", line 49, in main
    log.debug("First message returned %s", consumer.consume().value)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/simpleconsumer.py", line 477, in consume
    self._raise_worker_exceptions()
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/simpleconsumer.py", line 274, in _raise_worker_exceptions
    reraise(*self._worker_exception)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/six.py", line 686, in reraise
    raise value
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/simpleconsumer.py", line 439, in fetcher
    self.fetch()
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/simpleconsumer.py", line 831, in fetch
    min_bytes=self._fetch_min_bytes
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/broker.py", line 45, in wrapped
    return fn(self, *args, **kwargs)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/broker.py", line 327, in fetch_messages
    return future.get(response_class, broker_version=self._broker_version)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/handlers.py", line 76, in get
    return response_cls(self.response, **response_kwargs)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/protocol.py", line 1137, in __init__
    broker_version=broker_version)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/protocol.py", line 1078, in __init__
    response = struct_helpers.unpack_from(fmt, buff, offset)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/utils/struct_helpers.py", line 49, in unpack_from
    output = _unpack(fmt, buff, offset, 1)[0]
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/utils/struct_helpers.py", line 79, in _unpack
    offset + 4, count)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/utils/struct_helpers.py", line 115, in _unpack_array
    item, offset = _unpack(fmt, buff, offset)
  File "/data/virtualenvs/casterisk/lib/python3.6/site-packages/pykafka/utils/struct_helpers.py", line 96, in _unpack
    items.extend(struct.unpack_from('!' + ch, buff, offset))
struct.error: unpack_from requires a buffer of at least 25966 bytes

The code triggering @dan-blanchard's traceback above
for topic_name in settings['kafka']['topics'].values():
        topic = kafka_client.topics[topic_name]
        offset = OffsetType.LATEST if args['--offset'] == "latest" else OffsetType.EARLIEST
        consumer_group = settings['kafka']['consumer_group']

        log.info("Resetting topic: %s and consumer group:%s to %s", topic_name,
                 consumer_group, offset)
        log.info("Please stop your topology prior to running, otherwise you will "
                 "have to run again")

        consumer = topic.get_simple_consumer(consumer_group=consumer_group,
                                             auto_offset_reset=offset,
                                             reset_offset_on_start=True)

        log.debug("First message returned %s", consumer.consume().value)

I ran into this today during some Kafka experimentation, and after a lot of digging, learned that both my case and the cases described above are simply results of using the wrong broker_version kwarg on KafkaClient (rather, not specifying it, since it defaults to 0.9.0). Neither of the above examples specify this argument. As a result, the decoding logic for FetchResponse is treating the beginning of the response buffer as ThrottleTime, a newly added field in 0.9.0, instead of what it actually is when the cluster is 0.8.2: the length of the Topics array. This mistake causes all fields to be misread during decoding, which causes our traceback when it tries to treat some random payload data as a string length.
Since the actual fix is to use the API as defined, I've added a helpful error message in https://github.com/Parsely/pykafka/pull/866. cc @dan-blanchard @hbbtstar

Thanks @emmett9001 . I made the same mistake today. You reminded me that it could be the KafkaClient version that caused this error. My kafka version is <IP_ADDRESS> and the default specified broker version for KafkaClient is 0.9.0. So I'm trying to add a parameter broker_version to specify that the broker version is <IP_ADDRESS>. Finally, I succeeded and did not report such mistakes again.
It looks like this
client = KafkaClient(hosts="<IP_ADDRESS>:9092,<IP_ADDRESS>:9092",broker_version='<IP_ADDRESS>')

Thanks @emmett9001 . I made the same mistake today. You reminded me that it could be the KafkaClient version that caused this error. My kafka version is <IP_ADDRESS> and the default specified broker version for KafkaClient is 0.9.0. So I'm trying to add a parameter broker_version to specify that the broker version is <IP_ADDRESS>. Finally, I succeeded and did not report such mistakes again.
It looks like this
client = KafkaClient(hosts="<IP_ADDRESS>:9092,<IP_ADDRESS>:9092",broker_version='<IP_ADDRESS>')
it can solve my problem.  thanks

Hi,
We are currently trying to take the consumer groups info using the following basic code:
`config = SslConfig(cafile='/home/kafka/caroot.pem', certfile='/home/kafka/client.pem', keyfile='key.pem', password='passwd')
client = KafkaClient(hosts="kafkahost:9093", ssl_config=config, broker_version='2.4.0')
def describe_groups(client):
client.cluster.get_managed_group_descriptions()
describe_groups(client)`
and it returns the following trace
Traceback (most recent call last):   File "kafkaconsumer.py", line 46, in <module>     describe_groups(client)   File "kafkaconsumer.py", line 44, in describe_groups     client.cluster.get_managed_group_descriptions()   File "/usr/local/lib/python3.6/dist-packages/pykafka/cluster.py", line 428, in get_managed_group_descriptions     in itervalues(broker.list_groups().groups)])   File "/usr/local/lib/python3.6/dist-packages/pykafka/broker.py", line 45, in wrapped     return fn(self, *args, **kwargs)   File "/usr/local/lib/python3.6/dist-packages/pykafka/broker.py", line 561, in describe_groups     return future.get(DescribeGroupsResponse)   File "/usr/local/lib/python3.6/dist-packages/pykafka/handlers.py", line 76, in get     return response_cls(self.response, **response_kwargs)   File "/usr/local/lib/python3.6/dist-packages/pykafka/protocol/admin.py", line 144, in __init__     member_info[3])   File "/usr/local/lib/python3.6/dist-packages/pykafka/protocol/base.py", line 168, in from_bytestring     response = struct_helpers.unpack_from(fmt, buff, 0)   File "/usr/local/lib/python3.6/dist-packages/pykafka/utils/struct_helpers.py", line 49, in unpack_from     output = _unpack(fmt, buff, offset, 1)[0]   File "/usr/local/lib/python3.6/dist-packages/pykafka/utils/struct_helpers.py", line 79, in _unpack     offset + 4, count)   File "/usr/local/lib/python3.6/dist-packages/pykafka/utils/struct_helpers.py", line 115, in _unpack_array     item, offset = _unpack(fmt, buff, offset)   File "/usr/local/lib/python3.6/dist-packages/pykafka/utils/struct_helpers.py", line 96, in _unpack     items.extend(struct.unpack_from('!' + ch, buff, offset)) struct.error: unpack_from requires a buffer of at least 21589 bytes
The version of python that we are using is 3.6.9 and also the version of pykafka is 2.8.0
If there are any suggestions, that would be greatly appreciated.
Tnx


Packages not finding updates

Versions
Atom: 0.176.0-f7ecc3e
OS: Ubuntu 14.04
settings-view: 0.174.0
When going to the "Updates" section of "Settings", it says "All of your installed packages are up to date!". I have friends who are seeing packages updating. They are running previous versions of Atom ~0.173.0 on Linux. I also know for a fact there are updates, ie: Linter my current version is 0.10.0 and the newest version is 0.10.1. I'm not sure what happened or when, but I have not received any updates for a few days now at least.
Issue still occurs when attempting atom --safe and sudo atom

If you run apm upgrade from the command line, does it show any?

@kevinsawicki Would it be affected by the fact I had been testing a package I've been developing through the same atom?
$ apm upgrade
Package Updates Available (0)
└── (empty)

Would it be affected by the fact I had been testing a package I've been developing through the same atom instance?

It shouldn't be, unless that package is linter.
So if you run apm list, you see<EMAIL_ADDRESS>in the output?

It shouldn't be, unless that package is linter.
Haven't messed with linter at all.

$ apm list
Built-in Atom packages (79)
├──<EMAIL_ADDRESS>├── ...
└──<EMAIL_ADDRESS>
/home/stramel/.atom/dev/packages (1)
└──<EMAIL_ADDRESS>
/home/stramel/.atom/packages (23)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

I'm seeing this too, exactly same atom version (also, just checked and still happening built straight off master 0.176.0-4baea35), ubuntu 14.04 too if that's relevant.
Couple of other things I managed to find:

apm install packagename@version seems to work fine to install updated versions of the packages that aren't seeing updates, but...
apm install packagename without explicit version fails with No available version compatible with the installed Atom version: 0.176.0-f7ecc3e

Could it be somehow to do with the updated semver version in apm a week or so ago, getting confused by the -f7ecc3e appended to the end of the version?

Could it be somehow to do with the updated semver version in apm a week or so ago, getting confused by the -f7ecc3e appended to the end of the version?

Totally could be, thanks for the tip, will check into that now.

Further digging shows this which I guess is what's breaking stuff (I chucked a few logs in my apm install getLatestCompatibleVersion and >0.50.0 is what it's trying to satisfy):
> require('npm/node_modules/semver').satisfies('0.176.0-aaaaaa', '>0.50.0')
false
> require('npm/node_modules/semver').satisfies('0.176.0', '>0.50.0')
true

(run from in my apm dir, reason for npm/node_modules/semver rather than just semver is because that's what it is in apm's install.coffee, although I'm not sure why)

@jbt great work! :+1:

Thanks @stramel for reporting this and @jbt for the insight, should be fixed on master now.

Confirmed (well, for me at least), woop! :+1:

@jbt @kevinsawicki Thank you both! :+1:


Zoom beyond level 5 issue EPSG:3978

Hi,
I am just trying to use your project with the Leaflet 1.0 beta 1 via the leaflet-proj-refactor branch.
I have a map layer here http://geoappext.nrcan.gc.ca/arcgis/rest/services/BaseMaps/CBMT_CBCT_GEOM_3978/MapServer
which I can view all the way in to zoom level 17 in its built in viewer, here:
http://geoappext.nrcan.gc.ca/arcgis/rest/services/BaseMaps/CBMT3978/MapServer?f=jsapi
I am trying to set that layer up in Proj4Leaflet.  My code is below.  It works great from zoom=0 to zoom=5. The problem is that when I try to zoom in past level 5, I get the null tiles only.  I am wondering if it is my issue or a bug in Proj4Leaflet ?
Any suggestions as to what to try ?  Thanks.
<!DOCTYPE html>

    <title>Proj4Leaflet LCC</title>
    <meta charset="UTF-8">
    <link rel="stylesheet" href="lib/leaflet.css" />

I tried it at Leaflet 0.7.5 + the master branch (without changing proj4.js), with the same results. :-(

Looks like you are missing two zoom levels in you resolutions.
resolutions: [
  38364.660062653464,
  22489.62831258996,
  13229.193125052918,
  7937.5158750317505,
  4630.2175937685215,
  2645.8386250105837,
  1587.5031750063501, <- missing
<PHONE_NUMBER>537042,
<PHONE_NUMBER>021168,
<PHONE_NUMBER>0127004,
<PHONE_NUMBER>5074085,
<PHONE_NUMBER>5044451,
  66.1459656252646,
  38.36466006265346,
  22.48962831258996,
  13.229193125052918, <-- missing
  7.9375158750317505,
  4.6302175937685215
],

Thank you!


Update tableauViz.js-meta.xml

Add Option to make filter based on the Field Attributes for Community Pages as well.

Tableau Viz LWC is being Archived
All outstanding PRs and Issues are being addressed and closed. For more information, please see the README


Handling static files download

Hi,
needed to link to static files on the server....
this is what i come up with
@route 'files', {path: '/files/*'},-> window.location.href = window.location.href

Or does someone has a better idea?

@cmather I'm still a bit confused about this. I just want to host a static file from public folder e.g. public/images/logo.png for download.
For a regular website, I'd just use:
download me

But when I try this in Iron Router, I just get a redirect to the image file itself.
The solution in your previous post seems like something for dynamically creating a file on the server but I just want to serve a regular static file, so is there something a little simpler than creating the server route and manually serving a server response? Maybe I am missing something here.


feat: improve toggle-nvidia just command

https://github.com/ublue-os/config/issues/223

closing as needs further thinking


DSA 2.1 Strings: Substrings - Audio

Description
What are substrings? Give examples. How do you implement them? Mention atleast three approaches.
Important: Do not use assign command for this issue.
Task

[ ] Audio

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to Issue Guidelines.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be same as the issue.
This issue is only for 'GWOC' contributors of 'DSA' Domain.

Hey I wanted to take up this issue and work upon it. I will complete the issue in the format stated by you Kindly assign this issue to me.
Name : Vanshika Pandey
Batch no: 10

Hey I wanted to take up this issue and work upon it. I will complete the issue in the format stated by you Kindly assign this issue to me. Name : Vanshika Pandey Batch no: 10

Assigning this issue to you @vanshikapandey, all the best!

Thank you so much:)


Invalid equality check in list_jobs

Reported by @manuelm in amongst PR #2.

e.g. modify https://github.com/kraih/minion/tree/master/examples/linkcheck to use Storable
./script/linkcheck minion job -e foo -a '[23, "bar"]'
./script/linkcheck minion job
Use of uninitialized value in string eq at …/Minion/Backend/Storable.pm line 71.

@manuelm, I have a working unit test for this one too.
How about you create a new PR with just the change to Storable.pm?  Then I can merge that into a release for tomorrow.

Sure, if you want. Do you want me to remove this testcase https://github.com/niczero/minion-backend-storable/pull/2/commits/39254af50bb4704a140b4565d2b3e8818353c6d9#diff-f635e0684068ebb5429c39075efd225a as well?

This is fixed in v6.07 6ade8b3


Add empty placeholder viz for volcano plots

Resolves item 3 in https://github.com/VEuPathDB/web-monorepo/issues/358
Screenshot of empty placeholder viz:

Nope, i didn't have anything in mind at all! I think it's pretty clever!


Recent changes from Unicorn Global

Add recent changes from UnicornGlobal/liquid-linter-cli in preparation of handover to new owners/maintainers.

Merging despite security failure, as those will need to be fixed in follow-up MRs.


feat : Add themes and custom quotes

I added two themes namely algolia and monokai. I also added a feature to customize quotes by adding a query myquote by the user

Great! Can you add info about this in README?

oke sure

oke done @PiyushSuthar

Looks good to me, Thanks for the contribution 🎉


error: LLVM Translation failed for operation: builtin.unrealized_conversion_cast

Trying to run following gpt2 demo with triton-cpu and certain tirton kernel fails with above error:
import torch
from transformers import AutoTokenizer, AutoModelForCausalLM
from torch._inductor import config

@config.patch(cpu_backend="triton")
@torch.compile(backend="inductor")
def generate(prompt, model, tokenizer):
    input_ids = tokenizer(prompt, return_tensors="pt").input_ids
    gen_tokens = model.generate(
        input_ids,
       # max_length=4,
       # do_sample=False,
       # pad_token_id=tokenizer.eos_token_id,
    )
    gen_text = tokenizer.batch_decode(gen_tokens)[0]
    return gen_text

def test_gpt2_demo():
    tokenizer = AutoTokenizer.from_pretrained("gpt2")
    model = AutoModelForCausalLM.from_pretrained("gpt2").to(torch.float)
    prompt = "Thanks for"
    print("\nInput prompt: ", prompt, "\n")

    # run on CPU
    gen_text = generate(prompt, model, tokenizer)

    print("CPU output: ", gen_text, "\n")

test_gpt2_demo()

Dump of triton IR with more details are attached in log file.
log.txt
cc @ienkovich @minjang

From what I see in the log, this is due to the missing lowering for tl.device_assert. Asserts support has been added just recently: aa6a64e476f6fa4a50c69f626c09a312a2db65c8. Did you use the latest version with this patch included? If the latest version still fails, a Triton kernel reproducer would help a lot to debug the issue.


drivers: spi: spi_controller_peripheral: drivers.spi.spi_fast fails

Describe the bug
Test  tests/drivers/spi/spi_controller_peripheral/drivers.spi.spi_fast fails.
Observed for<EMAIL_ADDRESS>To Reproduce
Steps to reproduce the behavior:

have nrf54h20dk/nrf54h20/cpuapp connected
go to your zephyr dir
call ./scripts/twister -s drivers.spi.spi_fast -p<EMAIL_ADDRESS>--device-testing --device-serial /dev/ttyACM0 -v --inline-logs --west-flash="--erase" --fixture spi_loopback
See console output with error

Expected behavior
Valid console output
Impact
Not clear
Logs and console output
*** Booting Zephyr OS build v4.0.0-837-gb88d0bf8c7ee ***
Running TESTSUITE spi_controller_peripheral
===================================================================
START - test_basic

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:243: run_test: (periph_rv not equal to srx_len)
Got: 0 but expected:16
 FAIL - test_basic in 0.027 seconds
===================================================================
START - test_basic_async

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:243: run_test: (periph_rv not equal to srx_len)
Got: 0 but expected:16
 FAIL - test_basic_async in 0.027 seconds
===================================================================
START - test_basic_zero_len

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:243: run_test: (periph_rv not equal to srx_len)
Got: 0 but expected:8
 FAIL - test_basic_zero_len in 0.027 seconds
===================================================================
START - test_basic_zero_len_async

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:243: run_test: (periph_rv not equal to srx_len)
Got: 0 but expected:8
 FAIL - test_basic_zero_len_async in 0.027 seconds
===================================================================
START - test_only_rx

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:249: run_test: rv not equal to 0

 FAIL - test_only_rx in 0.024 seconds
===================================================================
START - test_only_rx_async

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:249: run_test: rv not equal to 0

 FAIL - test_only_rx_async in 0.023 seconds
===================================================================
START - test_only_rx_in_chunks
E: Scattered buffers are not supported
 SKIP - test_only_rx_in_chunks in 0.004 seconds
===================================================================
START - test_only_rx_in_chunks_async
E: Scattered buffers are not supported
 SKIP - test_only_rx_in_chunks_async in 0.004 seconds
===================================================================
START - test_only_tx

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:243: run_test: (periph_rv not equal to srx_len)
Got: 0 but expected:16
 FAIL - test_only_tx in 0.027 seconds
===================================================================
START - test_only_tx_async

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:243: run_test: (periph_rv not equal to srx_len)
Got: 0 but expected:16
 FAIL - test_only_tx_async in 0.027 seconds
===================================================================
START - test_only_tx_in_chunks
E: Scattered buffers are not supported
 SKIP - test_only_tx_in_chunks in 0.004 seconds
===================================================================
START - test_only_tx_in_chunks_async
E: Scattered buffers are not supported
 SKIP - test_only_tx_in_chunks_async in 0.004 seconds
===================================================================
START - test_short_rx

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:243: run_test: (periph_rv not equal to srx_len)
Got: 0 but expected:12
 FAIL - test_short_rx in 0.027 seconds
===================================================================
START - test_short_rx_async

    Assertion failed at zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:243: run_test: (periph_rv not equal to srx_len)
Got: 0 but expected:12
 FAIL - test_short_rx_async in 0.027 seconds
===================================================================
TESTSUITE spi_controller_peripheral failed.

------ TESTSUITE SUMMARY START ------

SUITE FAIL -   0.00% [spi_controller_peripheral]: pass = 0, fail = 10, skip = 4, total = 14 duration = 0.279 seconds
 - FAIL - [spi_controller_peripheral.test_basic] duration = 0.027 seconds
 - FAIL - [spi_controller_peripheral.test_basic_async] duration = 0.027 seconds
 - FAIL - [spi_controller_peripheral.test_basic_zero_len] duration = 0.027 seconds
 - FAIL - [spi_controller_peripheral.test_basic_zero_len_async] duration = 0.027 seconds
 - FAIL - [spi_controller_peripheral.test_only_rx] duration = 0.024 seconds
 - FAIL - [spi_controller_peripheral.test_only_rx_async] duration = 0.023 seconds
 - SKIP - [spi_controller_peripheral.test_only_rx_in_chunks] duration = 0.004 seconds
 - SKIP - [spi_controller_peripheral.test_only_rx_in_chunks_async] duration = 0.004 seconds
 - FAIL - [spi_controller_peripheral.test_only_tx] duration = 0.027 seconds
 - FAIL - [spi_controller_peripheral.test_only_tx_async] duration = 0.027 seconds
 - SKIP - [spi_controller_peripheral.test_only_tx_in_chunks] duration = 0.004 seconds
 - SKIP - [spi_controller_peripheral.test_only_tx_in_chunks_async] duration = 0.004 seconds
 - FAIL - [spi_controller_peripheral.test_short_rx] duration = 0.027 seconds
 - FAIL - [spi_controller_peripheral.test_short_rx_async] duration = 0.027 seconds

------ TESTSUITE SUMMARY END ------

===================================================================
PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: Ubuntu 20.04.1 LTS
Toolchain Zephyr SDK 0.16.8
Commit SHA or Version used: v4.0.0-837-gb88d0b

Additional information:

used set of pins:

spi130_default_alt: spi130_default_alt {
		group1 {
			psels = <NRF_PSEL(SPIM_SCK, 0, 0)>,
				<NRF_PSEL(SPIM_MOSI, 0, 8)>,
				<NRF_PSEL(SPIM_MISO, 0, 6)>;
		};
	};

spis131_default_alt: spis131_default_alt {
		group1 {
			psels = <NRF_PSEL(SPIS_SCK, 0, 1)>,
				<NRF_PSEL(SPIS_MISO, 0, 7)>,
				<NRF_PSEL(SPIS_MOSI, 0, 9)>,
				<NRF_PSEL(SPIS_CSN, 0, 11)>;
		};
	};

It is probably fixed by #81134


Trying to configure credentials so I can run synth

This is not an issue but a plea for help. When I run synth it returns
Synthesizing this full stack, Stack Name: mytestStack Not making progress trying to resolve environmental context. Giving up. [Error at /mytestStack] Need to perform AWS calls for account<PHONE_NUMBER>12, but no credentials have been configured
I tried following this link https://github.com/localstack/aws-cdk-local/issues/39 but to no avail. Ive also looked at the other issues
I am trying to run cdklocal in  gitlab ci
localstack is up and running before I run synth. I can create a bucket etc..
here are the services that are available
curl localstack:4566/health   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   864  100   864    0     0  96000      0 --:--:-- --:--:-- --:--:--  105k {"features": {"initScripts": "initialized"}, "services": {"acm": "available", "apigateway": "available", "cloudformation": "available", "cloudwatch": "available", "config": "available", "dynamodb": "available", "dynamodbstreams": "available", "ec2": "available", "es": "available", "events": "available", "firehose": "available", "iam": "available", "kinesis": "available", "kms": "available", "lambda": "available", "logs": "available", "opensearch": "available", "redshift": "available", "resource-groups": "available", "resourcegroupstaggingapi": "available", "route53": "available", "route53resolver": "available", "s3": "available", "secretsmanager": "available", "ses": "available", "sns": "available", "sqs": "available", "ssm": "available", "stepfunctions": "available", "sts": "available", "support": "available", "swf": "available"}, "version": "0.14.0"}
How do I satisfy the credentials cdklocal needs?
This is my latest try in the ci file
    - aws configure set aws_access_key_id foo
    - aws configure set aws_secret_access_key bar

    - echo "[default]" > ~/.aws/config
    - echo "region = us-east-1" >> ~/.aws/config
    - echo "sso_account_id =<PHONE_NUMBER>12" >> ~/.aws/config
    - echo "sso_role_name =<PHONE_NUMBER>12MyRoleName" >> ~/.aws/config
    - echo "output = json" >> ~/.aws/config

This is the resultant  config and creds when i cat the files when the ci job runs
$ cat ~/.aws/config
[default]
region = us-east-1
sso_account_id =<PHONE_NUMBER>12
sso_role_name =<PHONE_NUMBER>12MyRoleName
output = json
$ cat ~/.aws/credentials
[default]
aws_access_key_id = foo
aws_secret_access_key = bar

These are variables
variables:
     AWS_DEFAULT_REGION: us-east-1
    AWS_ACCESS_KEY_ID: foo
    AWS_SECRET_ACCESS_KEY: bar
    STACK_NAME: mytestStack
    CDK_DEPLOY_REGION: us-east-1
    CDK_DEPLOY_ACCOUNT:<PHONE_NUMBER>12

This is how I am running synth
- cdklocal synthesize --profile default -v
here are the version of awscli and aws-cdk-local. Could Node be issue?
$ cdklocal --version
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!                                                                                !!
!!  Node v11.15.0 has reached end-of-life and is not supported.                     !!
!!  You may to encounter runtime issues, and should switch to a supported release.  !!
!!                                                                                !!
!!  As of the current release, supported versions of node are:                      !!
!!  - ^12.7.0                                                                       !!
!!  - ^14.5.0                                                                       !!
!!  - ^16.3.0                                                                       !!
!!  - ^17.3.0                                                                       !!
!!                                                                                !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(node:1486) ExperimentalWarning: queueMicrotask() is experimental.
2.15.0 (build 151055e)
$ aws --version
aws-cli/1.19.112 Python/2.7.17 Linux/5.4.0-1009-aws botocore/1.20.112

Here is some of the verbose output
CDK toolkit version: 2.15.0 (build 151055e) Command line arguments: { _: [ 'synth' ],   profile: 'default',   v: 1,   verbose: 1,   deployAccount:<PHONE_NUMBER>12,   deployRegion: 'us-east-1',   lookups: true,   'ignore-errors': false,   ignoreErrors: false,   json: false,   j: false,   debug: false,   ec2creds: undefined,   i: undefined,   'version-reporting': undefined,   versionReporting: undefined,   'path-metadata': true,   pathMetadata: true,   'asset-metadata': true,   assetMetadata: true,   'role-arn': undefined,   r: undefined,   roleArn: undefined,   staging: true,   'no-color': false,   noColor: false,   validation: true,   quiet: false,   q: false,   '$0': 'cdklocal' }
I am wondering if the REAL VPC I need to reference in my project is causing the issue. I x-ed out the leading 7 chars

Setting "vpc-provider:account=123456789012:filter.vpc-id=vpc-xxxxxxxxce5f18eb92:region=us-east-1:returnAsymmetricSubnets=true" context to {"$providerError":"Need to perform AWS calls for account<PHONE_NUMBER>12, but no credentials have been configured","$dontSaveContext":true}
Setting "CDK_DEFAULT_REGION" environment variable to us-east-1
context: { 'vpc-provider:account=123456789012:filter.vpc-id=vpc-xxxxxxxce5f18eb92:region=us-east-1:returnAsymmetricSubnets=true':
   { '$providerError':
      'Need to perform AWS calls for account<PHONE_NUMBER>12, but no credentials have been configured',
     '$dontSaveContext': true },

Thanks for reporting @powerserg19 . Please note that we're using a different default account ID in LocalStack - it should be<PHONE_NUMBER>00 (not<PHONE_NUMBER>12). Can you try changing it, or commenting out the account ID part in general?
Also, is it required to specify a profile at all? Ideally cdklocal should work out of the box without having to manually customize the credentials (if that's not the case, we need to fix it). Can you please share the log output of a plain vanilla run of cdklocal synthesize, without specifying a profile or using custom credentials in the environment? Thanks!

@whummer  First off - Thank you very much for your early response!
It finally synthesizes without specifying account. I had tried that early on in this effort and did not realize that my stack was not account and region agnostic. I made several changes to make it agnostic.
Thanks again for you help.
Much appreciated!

@whummer I tried to run cdklocal deploy "nameofStack" I  got un-resolvable account error.  How do I depoy without account?
: Error: Unable to resolve AWS account to use. It must be either configured when you define your CDK Stack, or through the environment Unable to resolve AWS account to use. It must be either configured when you define your CDK Stack, or through the environment

I am perplexed by this. I created a simple stack and all it does is create bucket. There is not reference to account or region. Synth passes but when I run deploy its tell me that I need to specify an account.

@powerserg19 Can you please share your LocalStack startup configuration, as well as the full logs of the last cdklocal ... run? Please note that the local STS service needs to be enabled - so make sure to either include it in the LocalStack SERVICES environment config, or not specify this config at all (which is preferred).

The first two txt files which are java files. They are the CDK code that creates the stack.
The third one is my gitlab yml file. It doesn't specify services and I curl the localstack health endpoint which returns all the services running. Including STS. The fourth file is the CI job output. I called cdklocal deploy with the -v.
Thanks again!
SigmaplusCdk.txt
BucketTest.txt
gitlab-ci.txt
ci-job-log.txt

@whummer
I realize this isn't a cdklocal issue
but If you look at the output, cdklocal trying to connect to <IP_ADDRESS>:4566 to get the default account ID and its failing.
Looking up default account ID from STS
Unable to determine the default AWS account: { Error: connect ECONNREFUSED <IP_ADDRESS>:4566
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1088:14)
  message: 'connect ECONNREFUSED <IP_ADDRESS>:4566',

Im running this in gitlab so how can I configure localstack such that cdklocal can access the host?
Currrently I have this config for localstack
  services:
    - name: localstack/localstack:0.14.0
      alias: localstack

and I can reach the host via
localstack:4566/health

I understand now. I dont alias it :)

@whummer
I figured out
LOCALSTACK_HOSTNAME:  localhost

here is the full deploy result. I get the same behavior if i do

cdklocal bootstrap aws://000000000000/us-east-1 or cdklocal -v bootstrap aws://unknown-account/unknown-region

Synthesizing this full stack, Stack Name: testgaia
Experiment run type: world-graph-search
Creating a default VPC:
 ⏳  Bootstrapping environment aws://000000000000/us-east-1...
Trusted accounts for deployment: (none)
Trusted accounts for lookup: (none)
Using default execution policy of 'arn:aws:iam::aws:policy/AdministratorAccess'. Pass '--cloudformation-execution-policies' to customize.
CDKToolkit: creating CloudFormation changeset...
CDKToolkit |  0/14 | 7:06:54 PM | CREATE_IN_PROGRESS   | AWS::CloudFormation::Stack | CDKToolkit
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | TrustedAccounts
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | TrustedAccountsForLookup
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | CloudFormationExecutionPolicies
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | FileAssetsBucketKmsKeyId
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | PublicAccessBlockConfiguration
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | FileAssetsBucketName
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | ContainerAssetsRepositoryName
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | Qualifier
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | HasTrustedAccounts
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | HasTrustedAccountsForLookup
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | HasCloudFormationExecutionPolicies
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | HasCustomFileAssetsBucketName
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | CreateNewKey
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | UseAwsManagedKey
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | HasCustomContainerAssetsRepositoryName
CDKToolkit |  0/14 | 7:06:54 PM | UPDATE_IN_PROGRESS   | AWS::CloudFormation::Stack | UsePublicAccessBlockConfiguration
CDKToolkit |  1/14 | 7:06:54 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | FileAssetsBucketEncryptionKey
CDKToolkit |  2/14 | 7:06:54 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | FileAssetsBucketEncryptionKeyAlias
CDKToolkit |  3/14 | 7:06:56 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | StagingBucket
CDKToolkit |  4/14 | 7:06:56 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | StagingBucketPolicy
CDKToolkit |  5/14 | 7:06:56 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | ContainerAssetsRepository
CDKToolkit |  6/14 | 7:06:56 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | FilePublishingRole
CDKToolkit |  7/14 | 7:06:57 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | ImagePublishingRole
CDKToolkit |  8/14 | 7:06:57 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | LookupRole
CDKToolkit |  9/14 | 7:06:58 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | FilePublishingRoleDefaultPolicy
CDKToolkit | 10/14 | 7:06:59 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | CloudFormationExecutionRole
CDKToolkit | 11/14 | 7:06:59 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | CdkBootstrapVersion
CDKToolkit | 12/14 | 7:07:00 PM | CREATE_COMPLETE      | AWS::CloudFormation::Stack | DeploymentActionRole
CDKToolkit | 12/14 | 7:07:00 PM | CREATE_FAILED        | AWS::CloudFormation::Stack | CDKToolkit
Failed resources:
 ❌  Environment aws://000000000000/us-east-1 failed bootstrapping: Error: The stack named CDKToolkit failed to deploy: CREATE_FAILED (Deployment failed)
The stack named CDKToolkit failed to deploy: CREATE_FAILED (Deployment failed)
Cleaning up project directory and file based variables

Thanks for the update @powerserg19 . Looks like we're one step closer - the error you're seeing is coming from the CloudFormation deployment. Can you please enable DEBUG=1 in your LocalStack container environment, and then share the detailed container logs here? There is likely an issue with the deployment of one of your resources.. Also, please note that some advanced features may only be supported in our Pro version. Thanks

@whummer
Attached is the output with DEBUG on. This is just the deployment of a vanilla example stack. Not my product stack. All it contains is bucket creation. I attached that code earlier in this thread. In this case "cdklocal deploy" works but it fails when I try bootstrap just the same as my product stack( which needs bootstrap because its large) . If you want the product ouput logs i can supply them though I may have to redact a few things.
Here is my CI file
before_script:
  - docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY
  - apt-get -yq update && apt-get -yq install -y python3.7  python-pip
  - python3 -V

stages:
  - synth

synthisize project:
  tags:
    - java11
  stage: synth

  services:
    - name: localstack/localstack:0.14.0
      alias: localstack

  variables:
     AWS_DEFAULT_REGION: us-east-1
    STACK_NAME: testDeploy
    LOCALSTACK_HOSTNAME: localstack
    DEBUG: 1

  script:
    - apt update && apt install git -y
    - npm install -g aws-cdk-local aws-cdk
    - pip install awscli
    - cdklocal --version
    - aws --version
    - curl localstack:4566/health
    - cdklocal synth
    - cdklocal -v -v -v --debug bootstrap aws://000000000000/us-east-1
    - cdklocal -v deploy

ci-job-log.txt

@whummer
I followed this thread https://github.com/localstack/localstack/issues/5382
and set<EMAIL_ADDRESS>It passed the bootstrap part and it also deployed my vanilla stack which only consists of a bucket.
When I ran this against my product stack, it passed the bootstrap then  almost immediately failed
This was the error
testgaia: deploying...  ❌  testgaia failed: ReferenceError: BUCKET_NAME_OUTPUT is not defined BUCKET_NAME_OUTPUT is not defined ReferenceError: BUCKET_NAME_OUTPUT is not defined     at ExistingToolkitInfo.get (/usr/lib/node_modules/aws-cdk-local/bin/cdklocal:151:43)     at makeBodyParameter (/usr/lib/node_modules/aws-cdk/lib/api/deploy-stack.ts:423:38)     at deployStack (/usr/lib/node_modules/aws-cdk/lib/api/deploy-stack.ts:248:31)     at processTicksAndRejections (internal/process/task_queues.js:86:5)

@whummer
What does BUCKET_NAME_OUTPUT not defined mean and how can I satisfy that ?


⚠ Bofrost.at has degraded performance

In a3a0c83, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1131 ms

Resolved: Bofrost.at performance has improved in 7642aa5.


Split up pico_ice_sdk libraries

Alternative patch landed: https://github.com/tinyvision-ai-inc/pico-ice-sdk/commit/4aea79e0e136b7fa08eb1c277a66755161207053


Update Tempest App

Updates to the Tempest.
Walkthrough:
Updated the rain inches so that it shows decimals
Updated the pressure steady icon so it's an arrow instead of a straight line
Added a drop-down schema option that allows the user to choose whether to display Feels Like temperature or Dew Point temperature.

Is it possible to have an option to only display the single temperature maybe as double height for those that only want a single temperature number shown?

Looks like this replaces the entire app with a hello world or something like that.

@epifinygirl still problems with rain.   where you are getting it from - it's zero - but it rained here today,   from /better_forecast - notice the rain is 0

but if I use /observation/station/<station_id> - it's correct (it's in mm - but it's still correct.

which matches my web app:

at https://tempestwx.com/station/24329/grid

in that /better_forecast - I think that's how much rain is forecasted to fall - not how much has fallen.  rain is done here for the day

also - you have hard coded inches for rainfall - can't assume that.

I'll see if I can look at it

@jvivona the rain accum field should be from the station’s observation and not the forecast. Was it still coming up as 0 after the update where the decimals were missing? If so, I can research and see why it would be coming up as 0.
Good call out on the inches portion - the units should be there instead. Thanks for that catch.

it was still zero with the decimals from what I saw.   it's going to rain here again today - I'll keep an eye on it & check in again later.

you may have fixed this (but maybe didn't get pushed into the repo) - line 87 needs to be %g  instead of %d  to see the decimals.  But that also assumes the api is going to return 2 decimal places all the time in that element (which seems to be true).

this is what it looks like with %g

and with same test data using %d

No - it didn't rain 9.42 inches here yesterday :-)

You're right - I had thought I updated the %d but must have missed it. I submitted a PR for that change, along with a couple other items to update/fix 1396

looks good.   I just spent an hour messing with the oauth stuff on my end because I was just missing something simple.  now that I've got it - & I see your changes just pushed in.    Don't know why my device was reporting 0 rainfall yesterday - when the web app was clearly showing it.   maybe i fat fingered the device ID or something.      Thanks for the changes..


fixtures.json file is generated even without the command line argument

Using the latest version of Python 3.11 and pytest-json-fixtures 0.1.2, running tests generates a fixtures.json file even if you don't specify the --json-fixtures command line argument. The plugin code is triggered just by being there.
I don't know much about custom Pytest hooks, but I suspect this is because of the way the hook is registered on line 23 of pytest_json_fixtures.py.
@pytest.hookimpl(tryfirst=True, hookwrapper=True)

The hook code is always called. Maybe the original intent was to just bypass most of the pytest_collection_modifyitems function if the command line argument wasn't provided. That's my guess for why the if filename check exists on line 26. However, filename is always set. Even if the user doesn't specify one, it's set to the default string "fixtures.json" because of line 18.

Closed with https://github.com/marcosanchotene/pytest-json-fixtures/pull/5


Update readme.

An update of the intro video and some more info regarding features, available profiles, etc. won't hurt.

PR open https://github.com/haensl/js-performance/pull/61

Done in v1.17.2


Octoprint just opens a new instance instead of loading Authntication

Tried to generate  auth code but it just opens a new instance i have already verified my google account
Ive tried clearing cache and using a new browser

Clear the plugin's settings using the eraser icon in plugin manager.

Enable debug logging for the plugin in OctoPrint's logging section of settings and share octoprint.log here.


Run WMAgent validation for 1.4.7.patchX production release candidate

Impact of the new feature
WMAgent
Is your feature request related to a problem? Please describe.
By-monthly task
Describe the solution you'd like
We need to release a new WMAgent stable version in April, so this issue is to keep track of the full validation activity to be carried out in the first weeks of April, once we have a final 1.4.7 tag.
It also includes the creation of WMAgent release notes and the validation check-list twiki.
Describe alternatives you've considered
none
Additional context
none

This validation has been completed and we will start rolling this new version 1.4.7.patch2 to production.
Release notes can be found at (bulk of them in the patch1 release though): https://github.com/dmwm/WMCore/releases/tag/1.4.7.patch2
Validation twiki: https://twiki.cern.ch/twiki/bin/view/CMS/WMAgent147Validation
Closing this issue.


Fix: Update travis.yml to fix the release

What is the purpose of this pull request? (Check any that's applicable)

[ ] Feature
[ ] Bug fix
[ ] Dependency updates
[ ] Documentation updates
[X] Build related changes
[ ] Changes an existing functionality
[] Other, please explain:

Does this introduce a breaking change?

[ ] Yes
[X] No

What changes did you make? (Give an overview)
Updated the travis.yml file to trigger the release on main branch
Add any screenshots
N/A

:tada: This PR is included in version 2.6.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add texture support

Useful:

https://github.com/GRRLIB/GRRLIB/blob/master/examples/3D_sample2/source/main.c
app/src/raw_data_store.rs
app/src/renderer/indexed_model.rs
https://docs.rs/wavefront/0.2.3/wavefront/

Currently being worked on in lvdb/texture_support

@LucvandenBrand Tip: You can open a 'draft pull request' to indicate that work is ongoing, but already linking issue with branch, giving people the possibility to look at the work, and make it easier to look at CI output


[Wait for Istio 1.20.3] Istio 1.20.2 bump

Description
Update Kyma Istio module to use Istio in version 1.20.2 Update Istio version and used dependencies, adjust tests and documentation if needed. Upgrade needs to be with zero downtime for production settings.
ACs:

[x] review Istio RNs
[x] istio bumped on main and latest release branch (release-1.2)
[x] prepare kyma istio RNs based on Istio RNs
[x] istio installs and upgrades to 1.20.2 version
[ ] istio module upgrades with zero downtime - https://github.com/kyma-project/istio/issues/429
[ ] tests and documentation updated if needed
[ ] verify that sidecars are in sync with control-plane

Reasons
Keeping Istio up to date
DoD:
- [ ] Create a follow-up issue.
- [ ] Provide unit tests.
- [ ] Provide integration tests.

[x] Provide documentation.
[ ] Test on a production-like environment.
[ ] Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
[ ] Check the outcome of all related pipelines.
- [ ] Verify resource limits.
[x] As a PR reviewer, verify code coverage and evaluate if it is acceptable. --> Code coverage is lower, but this is caused by adding calls to Istio functions
- [ ] Create a release
[x] Add release notes

Attachments
https://istio.io/latest/news/releases/1.20.x/announcing-1.20.2/
https://istio.io/latest/news/releases/1.20.x/announcing-1.20/upgrade-notes/
PRs
- https://github.com/kyma-project/istio/pull/577 (main)
-  https://github.com/kyma-project/istio/pull/578 (release-1.2)

@howardjohn we actually tested 1.20.1 only with the commit I mention and it did break our k3d setup, however the fix resolves the issue, we also managed to validate it. thanks for fixing it so quickly. hope 1.20.3 is released soon.

Istio 1.20.3 is out - https://istio.io/latest/news/releases/1.20.x/announcing-1.20.3/


Hearts of iron 3 - flag and text not showing

Dear all, I would like to congratulate you on your incredible work.
Manually installing 32 dxvk 2.5.2, the game is very stable, even using the black ice mod. However, there are two problems: the flags are not rendered (all black) and the text of the diplomatic and menu section is blurry, as shown in the screenshot. I did several tests, both with steam - proton and with wine base, and using previous versions of dxvk. How could it be solved? Thank you

Software information
paradox interactive Hearts of Iron 3. 4.02 - complete collection. tested base game and modded with Black ice. Steam and GOG versions.
System information

GPU: intel cometlake-u GT2 8086:9b41 rev02
Driver: Mesa intel UHD Grpahic CML GT2. Kernel driver in use: i915
Wine version: 9. Proton 9, experimental
DXVK version: 2.5.2

Log files
please find attached game log.
game.log.txt

Check master, we already fixed a pretty bad bug that impacted older D3D9 and D3D8 games.

Check master, we already fixed a pretty bad bug that impacted older D3D9 and D3D8 games.

thank you very much for quick response! I'll try to compile the latest development version.

I'll try to compile the latest development version.

To be fair you don't have to compile it yourself, you can just grab the binaries generated by the GitHub Actions CI: https://github.com/doitsujin/dxvk/actions/runs/12435734651 (note that you need to be logged into GitHub to see the download link at the bottom of that page).

It seems work

Thanks for confirming.


Apply ZIO project template

Closes #9

applies project template
Update Scala / Scala.js versions to what zio/zio currently uses
Fix Scala 2.12 build

A few notes:

Scala.JS tests currently don’t work because files are read from resources
This changes the license
Currently, as per the template only John is listed in the contributors

@jdegoes conflicts resolved

Merged, thank you! 🔥


fix demo code of false()

There's a wrong example code on the page

I fixed this example when I recently updated my docs for v1.15 compatibility.


[release/v1.1] Bump EnvoyProxy to v1.32.2

Release Notes: https://github.com/envoyproxy/envoy/releases/tag/v1.31.2

/retest

/retest


Stable Diffusion not working - Expecting value: line 1 column 1 (char 0)

Expected Behavior
SD working on http://<IP_ADDRESS>:7860
Current Behavior
I see the web GUI, but everything I do, I see error
Expecting value: line 1 column 1 (char 0)
Steps to Reproduce
Just trying to make something (text-2-image, image-2-image, etc..)
Context
MacBook Pro M3Max - 48 GB Ram - Sonoma 14.1
Screenshots

Can you try to reinstall it?

Try pressing the  install button.

In my experience the Lollms webui doesn't download the stablediffusion model properly and I had to download it manually and put it in the right folder: Documents\lollms\shared\auto_sd\models\Stable-diffusion
The model you're looking for is here: v1-5-pruned-emaonly.safetensors https://huggingface.co/runwayml/stable-diffusion-v1-5/raw/main/v1-5-pruned-emaonly.safetensors


Change number to Percentage

Can i Change from number to Percentage?

However,data shown in tooltip is not in percentage,instead it is the data.How to solve this?

Pretty much in the same way @Obooman, this should work:
new Chart(ctx).Line(
    data,
    { tooltipTemplate: "<%= value + '%' %>" }
);

Or, with a label if set, taken from the docs:
new Chart(ctx).Line(
    data,
    { tooltipTemplate: "<%if (label){%><%=label%>: <%}%><%= value + '%' %>" }
);


How to set temprature and output token size in the chat mode?

Is there any examples to guide how to set temprature and output token size in the chat mode?

You may read this example:
examples/fill-in-middle/main.py

and "keep_alive" as well, thanks!

For example, I use the following for one of my projects:
from ollama import Options

        completion = ollama.chat(
            #keep_alive=0,
            model=config.ollamaDefaultModel,
            messages=[
                *ongoingMessages,
                {
                    "role": "user",
                    "content": prompt,
                },
            ],
            format="json",
            stream=True,
            options=Options(
                temperature=0.0,
                num_ctx=8192,
                num_predict=-1,
            ),
        )

Thanks Wong, I will try. Many thanks.


Docs: Programs faq

@Patrickming please review

(!) Found dead link /docs/programs/limitations in file SolanaDocumention/programs/faq.md
09:40:13.401 | (!) Found dead link /docs/programs/lang-rust in file SolanaDocumention/programs/faq.md
09:40:13.401 | (!) Found dead link /docs/programs/lang-rust in file SolanaDocumention/programs/faq.md
09:40:13.401 | (!) Found dead link /docs/programs/lang-rust in file SolanaDocumention/programs/faq.md
09:40:13.402 | (!) Found dead link /docs/programs/lang-c in file SolanaDocumention/programs/faq.md
09:40:13.402 | (!) Found dead link /docs/programs/lang-rust in file SolanaDocumention/programs/faq.md
09:40:13.402 | (!) Found dead link /docs/programs/lang-c in file SolanaDocumention/programs/faq.md
09:40:13.402 | (!) Found dead link /docs/programs/deploying in file SolanaDocumention/programs/faq.md
09:40:13.402 | (!) Found dead link /docs/programs/lang-rust in file SolanaDocumention/programs/faq.md
09:40:13.403 | (!) Found dead link /docs/programs/lang-c in file SolanaDocumention/programs/faq.md
09:40:13.403 | x Build failed in 7.92s
09:40:13.403

Sorry, I have rechecked and updated the link, execute doc build command OK
  vitepress v1.2.2

✓ building client + server bundles...
✓ rendering pages...
build complete in 10.20s.

OK @Fankouzu


Allow passing initial buffer, better errors, add missing grow_if_needed

Codecov Report

Merging #15 (452b89e) into main (0ebe164) will decrease coverage by 0.09%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
- Coverage   84.68%   84.58%   -0.10%
==========================================
  Files          10       10
  Lines        1358     1369      +11
==========================================
+ Hits         1150     1158       +8
- Misses        208      211       +3

Impacted Files
Coverage Δ

src/bufpool/agg.rs
81.36% <50.00%> (-0.30%)
:arrow_down:

src/proto/h1.rs
92.13% <100.00%> (+0.22%)
:arrow_up:

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


Growth KPIs Dashboard

Starting a repo to work on Issue #29  -- adding period growth metrics to core dashboard assets to streamline analysis and decision making. Adding @jackiep00 and @josephd8 for visibility.
https://github.com/SetProtocol/index-coop-analytics/issues/29

@josephd8 added the SQLs that power the line charts. I left the tables out for now because it is pretty redundant... all I do to get those is keep the raw numbers in the final query sort by date in descending order, and limit rows by 7

Awesome @ehrena ! So I think the last things to add would be:

BED Unit Supply
the last four tables for those product unit supply views

And then we can close out this issue and merge this PR. We will have to do some updating on some these once we get a re-vamp of all our exposure queries over the next week or two, but that will be a separate issue and task.

@josephd8 will make these additions ASAP

@josephd8 made the remaining changes -- added BED and the summary tables

Awesome! I am going to merge this PR and close the issue. We will likely build on this in the future! You should change the dashboard name to Index Coop Growth Metrics or something like that so it is recognizable! @ehrena


csvkit: 2.0.0 -> 2.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for csvkit is: Suite of command-line tools for converting to and working with CSV
meta.homepage for csvkit is: https://github.com/wireservice/csvkit
meta.changelog for csvkit is: https://github.com/wireservice/csvkit/blob/2.0.1/CHANGELOG.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.1 with grep in /nix/store/xq25d1papfx1xh9iqpp4yjbmrinlayxw-csvkit-2.0.1
found 2.0.1 in filename of file in /nix/store/xq25d1papfx1xh9iqpp4yjbmrinlayxw-csvkit-2.0.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

csvkit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xq25d1papfx1xh9iqpp4yjbmrinlayxw-csvkit-2.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A csvkit https://github.com/r-ryantm/nixpkgs/archive/7768267ae7e3a4ead7d3f28d291c32367951bd12.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7768267ae7e3a4ead7d3f28d291c32367951bd12#csvkit

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xq25d1papfx1xh9iqpp4yjbmrinlayxw-csvkit-2.0.1
ls -la /nix/store/xq25d1papfx1xh9iqpp4yjbmrinlayxw-csvkit-2.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

csvkit
csvkit.dist

Maintainer pings
cc @AndersonTorres for testing.

@NixOS/nixpkgs-merge-bot merge


--recursive flag not working

Hello,
It seems that the recursive flag from mocha is not working in this module.
My structure:
Project Folder
-- test (default mocha folder)
---- rootHooks.js
---- Folder 1
------ page1.js
------ page2.js
---- Folder 2
------ page1.js
------ page2.js
------ page3.js
For Mocha, I usually can run the following: "mocha --require babel-register --recursive", which tells mocha to recursively run in each folder, and defaults to the folder "test"
I have tried the flag with mocha-parallel-tests, as well as the following, with no luck:
mocha-parallel-tests --max-parallel 4 --require babel-register --recursive test/
mocha-parallel-tests --max-parallel 4 --require babel-register --recursive
mocha-parallel-tests --max-parallel 4 --require babel-register --recursive test//*.js
mocha-parallel-tests --max-parallel 4 --require babel-register test//.js
mocha-parallel-tests --max-parallel 4 --require babel-register --recursive **/.js
None of these combos will run my subfolder tests, but still run the root hooks in the test folder. It works for mocha, not for mocha-parallel-tests.
Any ideas? Am I doing something wrong/missing something?

It seems like this is an error. Thank you for posting it. Will take a look soon (2-3 days).

Seems strange because I can't reproduce your issue in my PR: https://github.com/yandex/mocha-parallel-tests/pull/95
Could you please check the PR or provide the code from your tests which is not running?

@jankcat ping

Sorry. I've been out of the office. I'll be back next week and can try again then.

@jankcat one more ping :)

I threw a repo up here with the issue, as I am still seeing it: here
You can see the commands I am running here.
And screenshots here.

Running the command to run all the tests in a folder does not work as it does in mocha, instead it complains that no tests exist.
Specifying a subfolder of tests works, but the root hooks (before all, after all) do not run, even when explicitly added to the command (see the single area and two area tests, as well as the sub area test in the example repo)

Sorry, now delay is from my side. I can see, will try to fix these.

Ah okay. I dont remember what my use case was (oops).
Thanks! The cats are not mine, but I do have 3 others that didnt make the pic.


Invalid Index errors

Is there a way to edit stack variables in order to resolve the 2 errors below?
Error: Invalid index
on network.tf line 108, in resource "oci_core_route_table_attachment" "cn_sftp_lb_subnet_rt_attachment"
108:   route_table_id = oci_core_route_table.cn_sftp_lb_subnet_rt[0].id
├────────────────
│ oci_core_route_table.cn_sftp_lb_subnet_rt is empty tuple
The given key does not identify an element in this collection value.
Error: Invalid index
on network.tf line 130, in resource "oci_core_route_table_attachment" "cn_sftp_servers_subnet_rt_attachment"
130:   route_table_id = oci_core_route_table.cn_sftp_servers_subnet_rt[0].id
├────────────────
│ oci_core_route_table.cn_sftp_servers_subnet_rt is empty tuple
The given key does not identify an element in this collection value.

Hello,
are you using OCI Resource Manager or are you running the module through Terraform ?
In the latter case, can you share your terraform.tfvars ?

Hi, thanks for responding. I'm using OCI Resource Manager. The "Deploy" button didn't work for me due to the url being gone so I downloaded the zip file of the latest release, uploaded it to a new stack in Resource Manager, edited my variables, ran a "Plan" and got the 2 errors.

The URL used by Deploy to Oracle Cloud was broken, the right URL is:
https://cloud.oracle.com/resourcemanager/stacks/create?region=home&zipUrl=https://github.com/oracle-quickstart/oci-cloud-native-sftp/releases/latest/download/oci-cloud-native-sftp-stack-latest.zip
The README.md has been updated accordingly, would you try again ?

Using the new link was helpful (thank you!), but the build still fails with the exact same 2 error messages as above.

Are you using existing subnets, right ?

@ratkosomni the issue was caused by wrong route table attachment when existing subnets are used. Since the subnets are already there, route tables are not created so their attachment should be skipped.
Now is it possible to run terraform plan successfully for both scenarios (non-existing and existing subnets), also using OCI Resource Manager.

Plan is now able to execute successfully, then attempting to run Apply using the successful Plan output fails.

Please share the error

Thank you for both fixes.

Thank you for both fixes.

Yes, please

Plan and Apply both ran successfully, thank you for your help! This was exactly what my org needed to quickly get an sftp server up and running on our cloud tenancy, can say enough how much I appreciate it.

Hi @moisesdasilvadeoliveira, which region are you using ?
Can you please open a new issue, specifying that the error is related to ADs


Website content crafting and publishing: (Components/Leaving IBM):  Target Jan 11, 2021

Objective
Provide Carbon for IBM.com adopter the best practices and guidance they need to adopt Carbon for IBM.com.
General publishing process
Please make sure you always start the content crafting process by viewing the 2020 website content publishing process box document first.
Publishing for Components section website page

Content crafting starts as soon as the design is finalized.
Components section includes UI components and Layout components.
The content can be at the MVP level. MVP means the content meets the basic needs of an adopter for learning. It does not mean the content crafting will or should stop at this stage. Future enhancement should be working on with a separate task issue.
MVP content publishing template and requirement can be found in the Publishing template and best practices/_UI and Layout Components folder.
Please use the visual and design spec files inside of the Carbon for IBM.com Box folder as a reference.
Content publishing to the live website can be code or markdowns. If you need guidance on how to start with markdowns, please see the step by step instruction in the Editing and publishing in Github Box document.
When the page is published, please also make sure the components table list on the Overview page is updated as part of the publishing task.

File naming and storage

Name the Sketch file with the following convention: Name of the category + components/pattern/guideline + version. ex: Components-Feature card block v1.0, Guidelines-Expressive theme v1.0, Help-Overview v1.0 and etc.
Please save all content publishing work files (box, markdowns link, or Sketch file) in the proper sub-folder under the ✍ Content + Design folder.

Publishing acceptance criteria

[ ] Content crafting is done.
[ ] Asset image creation is done.
[ ] Page design is done (as needed).
[ ] Publishing with markdowns is done.
[ ] QA'd by Jenny.
[ ] Web page preview is approved by Linda, Jeff, and Wonil.
[ ] PR merged by Jenny.
[ ] Web page is published and live on the website.

Design specs and exports for this are here. Pull request is in review here

Design specs and exports for this are here. Pull request is in review here

per slack with James, this issue can be closed.

per slack with James, this issue can be closed.

@photodow @RobertaJHahn The task issue needs to remain open since the Publishing acceptance criteria are not met completely (see detail below).

Wonil and I need to review the content via screenshot of the page design or via preview link
The PR needs to be merged after review
The content for the page needs to be live on the website.

@photodow @RobertaJHahn The task issue needs to remain open since the Publishing acceptance criteria are not met completely (see detail below).

Wonil and I need to review the content via screenshot of the page design or via preview link
The PR needs to be merged after review
The content for the page needs to be live on the website.

I have updated airtable and moved this issue to the current sprint 21-02

I have updated airtable and moved this issue to the current sprint 21-02


Error loading fact /var/lib/puppet/lib/facter/macaddress_primary.rb: cannot load such file -- cfpropertylist

This fact is confined, but the gem reference is causing noisy errors on Linux hosts that don't have the gem installed.
The require directive (as well any other refs) need to go into a begin rescue clause that catches LoadError.

I modified my local version and just created a pull request ;)

Fix is in develop. Ready for release 3.8.3.


Exclude dangling symlinks when creating a local repo.

Fix google/bazel#69

Thank you for your patch!
Can you add a test case in //src/test/shell/bazel:local_repository_test?
Can we continue the review on Gerrit so we can do a quality review?


Serialize RPC deadline as a Duration.

Duration was previously serialized as SystemTime. However, absolute times run into problems with clock skew: if the remote machine's clock is too far in the future, the RPC deadline will be exceeded before request processing can begin. Conversely, if the remote machine's clock is too far in the past, the RPC deadline will not be enforced.
By converting the absolute deadline to a relative duration, clock skew is no longer relevant, as the remote machine will convert the deadline into a time relative to its own clock. This mirrors how the gRPC HTTP2 protocol includes a Timeout in the request headers but the SDK uses timestamps. Keeping the absolute time in the core APIs maintains all the benefits of today, namely, natural deadline propagation between RPC hops when using the current context.
This serialization strategy means that, generally, the remote machine's deadline will be slightly in the future compared to the local machine. Depending on network transfer latencies, this could be microseconds to milliseconds, or worse in the worst case. Because the deadline is not intended for high-precision scenarios, I don't view this is as problematic.
Because this change only affects the serialization layer, local transports that bypass serialization are not affected.
Jaeger screenshot showing change in deadline between client and server:

Fixes #366

Using the serialization layer to hide the conversion is pretty neat. Thanks for fixing this!

Thanks for raising this issue and providing prompt feedback, @ditsing !


Add readonly mode option to workspaces

Add a readonly parameter option in workspaces definition.
When this option is activated, the user won't be able to edit or delete any study in the workspace.

The user now can't delete a study.


Fixup resource limit checks

Description
This PR fixes missing updates to resource limit tags during different VM & disk operations.

Scale VM - Both stopped and running
Restore VM with different template & offerings
Resize Disk
Change Disk offering

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15.  It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9353

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✖ debian ✔ suse15. SL-JID 9364

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9368

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.


Implemented the service-info endpoint

closes #37
Implemented the service-info endpoint.
I actually used the same file provided here by @tcezard.
I did one change in the lengths attribute's type that I changed it into string, which is how it is defined in our API, and we'll consider updating it into integer after we do the refactor in our API.
I would like to know whether we should use sorted_names_length_pairs, as provided in the service-info file, or sorted_name_length_pairs as we defined it in our java model.

I would like to know whether we should use sorted_names_length_pairs, as provided in the service-info file, or sorted_name_length_pairs as we defined it in our java model.

It should be sorted_name_length_pairs

@nsheff  I'll raise an issue for that to do the necessary refactoring


Review minimum required K8s version

What would you like to be added?
The minimum required K8s version necessary to run our Helm charts should be available in the Chart.yaml.
Why is this needed?
We currently publish 1.21.0-0 but we recently discussed that this is not tested:
https://github.com/redpanda-data/helm-charts/blob/cc959498a40307a6fc6a6862a5174a960a7c1e0c/charts/redpanda/Chart.yaml#L35
We should test K8s versions and publish the minimum required kubeVersion that we are confident will work.
JIRA Link: K8S-82

kubeVersion is intended to declare what version of the kubernetes API is required. There are ways to lint this without doing a full test suite.

Going to close this, as we tested against 1.25.x recently.


MINOR: add task ':streams:testAll'

Adds a new task to Streams to run all the tests for all sub-projects.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

One more thought, it might be useful to add this to the repo README if a user is only doing stream side changes and want to test it out on local @vvcephei.

Thanks @abbccdda ! There was only one flaky test, and the last change was only to the README, so I'll merge now.


Performance tanks in Mass Effect when looking at occluded part of the level

So, I like to benchmark the game in the comm room on the Normandy, since I found out (once the door closes) that I can get the highest framerates of all the game there.
I just walk against the FTL comm link at the bottom of it, and then stare at the empty wall.
In D3D9 I get around 420 fps, while dxvk gives me around 350, not that bad I thought.
I just figured out though, that if I just rotate the camera to "face the rest of the ship", while D3D9 only slows down to about 360fps, dxvk gets almost 3 times slower at 130.
Software information
Mass Effect 1, max in-game settings, no mods.
System information

GPU: Radeon R9 290
Driver: 20.11.2
Wine version: Windows 7 SP1
DXVK version: 1.7.3

Apitrace file(s)

Apitrace

Log files

d3d9.log

Are you CPU-bound or GPU-bound? That kind of info is extremely important when dealing with performance issues.
Also, be aware that DXVK is known not to perform well on first- and second-gen GCN cards due to some limitations around how they handle depth buffers.

I think it's actually both in the apitrace you can find.
I lowered the resolution to 640x480, and D3D9 wasn't actually affected at all (even though I could have swore gpu usage at 97% meant it was gpu-bound).
But then this had a big effect on DXVK. When I'm staring at the wall I gain those 70fps that I was missing earlier.
While I'm staring behind my shoulders, I'm still getting the same ~130 fps.

I can confirm that it's slower when looking at the wall that has geometry behind it and the hit is much larger than with Windows D3D9. Windows D3D9 pretty much runs the same and DXVK drops from 550 fps to 430 for me.
Fully CPU bound of course. I dont really know why though. There's nothing that obviously sticks out.

Can you try this?
d3d9.zip

This is enormously better. Performance hit is around 20% now, which is more or less the same ballpark of the one you get with native D3D9.

How about this one:
d3d9.zip
Does it yield similar results to yesterdays build?

Yes.

A8-7600, mesa 20.2.3, comm room scenario:
dxvk-master: 60fps (vsync - 88% gpu utilization) vs slightly above 48fps
pull request #1857 : 60fps (vsync - 88% gpu utilization) vs slightly below 48fps
The difference is perhaps 0,5fps or even less, but it does seem to perform worse. Not sure how random it is, rotating the camera seems to change that number a lot, but when looking straight at the door dxvk-master reports 31 render passes, #1857 32.
So no performance gain on radv.

A performance drop is expected because the game is simply doing a lot more when you look at that other wall.
It was just a special case for mirh where the cpu didnt submit work early enough so it would work for the gpu.

I did expect a performance drop, I was just thinking it's some generic performance improvement for that case, and the way you explain it, I guess it's related to way higher framerates he's having. Nevermind, don't mind me, I was just reporting 0,5fps drop in my case, which is acceptable.

d3d9.zip
How about this one? Still improved? That should hopefully not cause any performance regressions on other systems.

Yup. I also noticed a very marked 40% improvement in my "worst case spot" on the citadel.

d3d9.zip
How about this one? Still improved? That should hopefully not cause any performance regressions on other systems.

Thank you, its fixed FFXIII-2 Regression

Fixed.

Fixed.

Fixed.

Fixed.

Cool, now, how about tackling performance being "in general" slower?
On my desktop the difference is about 15-20% as I mentioned in the opening, but on my 950M I can get north of 50% faster framerate with native d3d9 (in fact, with a slightly different "not really much to render" camera angle from the same scenario above I can even near twice as much fps)

Cool, now, how about tackling performance being "in general" slower?
On my desktop the difference is about 15-20% as I mentioned in the opening, but on my 950M I can get north of 50% faster framerate with native d3d9 (in fact, with a slightly different "not really much to render" camera angle from the same scenario above I can even near twice as much fps)

There's nothing obviously wrong with DXVK that we could just optimize.
Is performance an issue anyway? As mentioned, on my system it runs at 500 fps with DXVK.
Sure it would be nice to reach the 600 fps that Nvidias D3D9 manages but no one's gonna notice the difference.

There's nothing obviously wrong with DXVK that we could just optimize.
Is performance an issue anyway? As mentioned, on my system it runs at 500 fps with DXVK.
Sure it would be nice to reach the 600 fps that Nvidias D3D9 manages but no one's gonna notice the difference.

And yes, it's kind of a big deal when it can make the difference between "playable" and "unplayable" (I have a dedicated gpu in my laptop thankfully, so here if any we are talking about "bearable" vs "great", but still)

I'm not talking about cpu limited situations here though (and in fact these last numbers were taken from W10, which would make even an nvidia suck there).
And yes, it's kind of a big deal when it can make the difference between "playable" and "unplayable" (I have a dedicated gpu in my laptop thankfully, so here if any we are talking about "bearable" vs "great", but still)

What kinds of numbers are you getting anyway where this is a problem and what settings and resolution?
Mass Effect is pretty much ALWAYS CPU limited on my system.

What kinds of numbers are you getting anyway where this is a problem and what settings and resolution?
Mass Effect is pretty much ALWAYS CPU limited on my system.

Increase the resolution then?
I'm using a 6500U+950M laptop now personally, so 1080p is already enough to run around the 60fps mark.
In the most gpu-limited scene I can find score is 52 fps vs 35.
 Which become 120 vs 60 when I stare to the ceiling.
That doesn't sound really trifles.

Increase the resolution then?
I'm using a 6500U+950M laptop now personally, so 1080p is already enough to run around the 60fps mark.
In the most gpu-limited scene I can find score is 52 fps vs 35.
 Which become 120 vs 60 when I stare to the ceiling.
That doesn't sound really trifles.