TPU model doesn't work with tensorflow.python.keras learning rate scheduler.

When I convert Keras model into TPU model using tensorflow.contrib.tpu.keras_to_tpu_model and try to fit it with learning rate scheduler callback, the training crashes with error ValueError: Optimizer must have a "lr" attribute.. I guess the problem is that the keras and tensorflow optimizers use different learning rate variable name, which makes the keras callback fail. The callback in tensorflow.python.keras should be therefore corrected to use the proper variable.
System information

Google Colab TPU runtime
TF 1.12.0rc1

Code fragment
    strategy = tensorflow.contrib.tpu.TPUDistributionStrategy(
        tensorflow.contrib.cluster_resolver.TPUClusterResolver(tpu = 'grpc://' + os.environ['COLAB_TPU_ADDR'])
    )
    model = tensorflow.contrib.tpu.keras_to_tpu_model(model, strategy=strategy)
    model.compile(
        loss=tensorflow.keras.losses.categorical_crossentropy,
        optimizer=tensorflow.train.GradientDescentOptimizer(learning_rate=lr_schedule(0)),
        metrics=['accuracy']
    )
    (...)
   callbacks = [tensorflow.python.keras.callbacks.LearningRateScheduler(lr_schedule_function)]

Describe the current behavior
Traceback (most recent call last)
<ipython-input-12-b6a9470abb3b> in <module>()
    441                         validation_data=(x_test, y_test),
    442                         epochs=epochs, verbose=1, workers=4,
--> 443                         callbacks=callbacks)
    444
    445 # Score trained model.

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training.py in fit_generator(self, generator, steps_per_epoch, epochs, verbose, callbacks, validation_data, validation_steps, class_weight, max_queue_size, workers, use_multiprocessing, shuffle, initial_epoch)
   2175         use_multiprocessing=use_multiprocessing,
   2176         shuffle=shuffle,
-> 2177         initial_epoch=initial_epoch)
   2178
   2179   def evaluate_generator(self,

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training_generator.py in fit_generator(model, generator, steps_per_epoch, epochs, verbose, callbacks, validation_data, validation_steps, class_weight, max_queue_size, workers, use_multiprocessing, shuffle, initial_epoch)
    141       for m in model.stateful_metric_functions:
    142         m.reset_states()
--> 143       callbacks.on_epoch_begin(epoch)
    144       steps_done = 0
    145       batch_index = 0

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/callbacks.py in on_epoch_begin(self, epoch, logs)
    198     logs = logs or {}
    199     for callback in self.callbacks:
--> 200       callback.on_epoch_begin(epoch, logs)
    201     self._delta_t_batch = 0.
    202     self._delta_ts_batch_begin = deque([], maxlen=self.queue_length)

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/callbacks.py in on_epoch_begin(self, epoch, logs)
    768   def on_epoch_begin(self, epoch, logs=None):
    769     if not hasattr(self.model.optimizer, 'lr'):
--> 770       raise ValueError('Optimizer must have a "lr" attribute.')
    771     try:  # new API
    772       lr = float(K.get_value(self.model.optimizer.lr))

ValueError: Optimizer must have a "lr" attribute.

@brge17 is correct that keras optimizer should work. Post your code here if you need further help.

I have tried doing this and it does not work. Specifically, I have tried the following:
from keras.optimizers import Adam
from tensorflow.keras.optimizers import Adam
from tensorflow.python.keras.optimizers import Adam
In the first case, the model will not compile. With the latter two, it compiles but during the fit, I get the message "ValueError: Operation 'tpu_140522079557168/VarIsInitializedOp' has been marked as not fetchable."

Facing the same issue!!
Found any solution to it yet?

Any Answer?

Any attempt to mix keras and tf.keras classes fail on TPU. You probably need to induce TF devs to fix their optimisers rather..


Addition of money should be green instead of yellow

Actually storno is green, topUp yellow and order red.
Lets make topUp and storno green? @theErikss0n @neilschark

i think topUp and storno should be a different colour, to better differentiate between them.

But why?
Both add something to your account.
We also have the type filters...


Fix decompression bug

The mod field was being calculated after the offset value it relied on
was modified. Moved the calculation of mod up to before offset was
modified.

Thanks for fixing the bugs I introduced.
I think adding those variables makes the code a little easier to understand. Reading though the source code I think the mod variable or the subfunction to calculate it subfunction could use some explaining (coming from a programmer with no background in compression) to ease understanding when reading through the sourcecode.
I tested by extracting a compressed sheets.vol. No issues noted.

Better comments would be nice. One problem though being, I don't really understand that method either. It was written using the disassembly from the game as a guide.
From a high level, I know that section of code calculates an offset into the repeat buffer, and I know it uses a variable length code to determine that offset. It's biased such that small offsets (backwards from the current output position) have shorter codes. That seems to make sense in that repeated data is often close to each other.
As for why particular constants were chosen, or why the offset is calculated as it is, I'm afraid I don't have answers there. I suspect it's related to Huffman codes, but using a fixed code table rather than adaptive codes for that section. Even that though, I'm uncertain of. I would need to review Huffman codes to see if the implementation actually matches.


Release gh-badges to npm

The library readme on npm looks incredibly outdated and the examples in there don't work:
var badge = require('gh-badges');
badge({ text: [ "build", "passed" ], colorscheme: "green" },
  function(svg) {
    // svg is a String… of your badge.
  });

throws an error because template is not set (which is mentioned in the README on master).

Yea, agreed, it would be a good idea to do a release. There are a few things that need doing:

[ ] Update the documentation in the readme (and document the API in doc/ if needed)
[ ] Make sure the public interface has tests
[ ] Make sure we're publishing the files we need
[ ] Publish a 2.0 RC

How far away are we from this? Maybe we could get incremental improvements instead of blocking on all these changes if it delays the release so long? I.e. if there is another breaking change, just cut 3.0, version numbers are cheap.

I'm curious about this too - 1.3.0 has a lot of security vulnerabilities and I'd like to upgrade.

Looking over the tasks, I don't mind having a look at this job. I assume when you say "make sure we're publishing the files we need", you mean ensuring this is right: https://github.com/badges/shields/blob/9b6ba776f004afff76ac0cc651e5b3c77a9c84e2/package.json#L101-L111
@paulmelnikow - if I can spend a bit of time to get the docs into shape, check the tests and test a package, do you have access to npm publish it?

I've submitted PR #2200 with some changes supporting this. It isn't an aspect of the project I've given any attention to before, but having done a bit of work on this, I think there are several other jobs we should do to improve the NPM package.
There is one issue I've raised in #2200 which I think we should consider before publishing a 2.0.0 release (should we force the user to make a choice of text measurer in order to generate a badge?). Additionally, these shouldn't be blockers to a 2.0.0 but we should think about them for future:

There is some internal code which we currently need to include in the NPM library due to tight internal coupling which isn't strictly necessary for NPM package users. e.g: the LRU cache module.
Because shields.io and gh-badges share the same package.json, our NPM package users are inheriting a load of unnecessary dependencies which are needed by shields.io but not the NPM package.
It is difficult to provide a good readme for NPM because npm pack collects the README.md from the root: https://docs.npmjs.com/files/package.json#files There isn't a neat way to specify "replace README.md with doc/gh-badges.md when we run npm pack".
Our package users also inherit a bunch on NPM scripts which aren't relevant to the library.

Those issues all stem from the fact we are trying to break a package out of a monolith. IMO we should aim to treat the subset of our codebase which makes up the gh-badges package as a package in its own right which shields.io depends on. It could either live in its own repo under the @badges org or use a "monorepo" arrangement with the package living in a separate corner of the repo with its own package.json. That would allow us to solve several of these issues. It would also create a situation where we're "eating our own dogfood", which would provide a much greater incentive to exercise better stewardship over the package.

+1 for putting the package into a separate repo.
We may be able to do this post-2.0 though. Lets get 2.0 released as soon as possible.

Think we've got the details nailed down in #2200 now, but if I merge it I don't have permission to npm publish the package. @espadrine  , @paulmelnikow  can either of you tag in to help get a 2.0.0-beta out?

I do not have access to the npm package. I'll email Thaddée. Can you confirm you're https://www.npmjs.com/~chris48s on npm?
Meanwhile let's not block. We could either publish to a scoped name like @shields/gh-badges and then roll things back into the main gh-badges when we get access, or pick a more meaningful name and plan to retire gh-badges. There's a way to mark old packages as not supported or provide a message encouraging users to switch. I haven't used it before, but I've seen those messages.
"github badges" is not really what this package does… so perhaps make-badge?

P.S. Thank you so much @chris48s for taking this on!

I had also thought about publishing a new package name if we need to. Did you already snag https://www.npmjs.com/org/shields or is that somebody else?

Nooope, that is somebody else…

Though there’s no need! Thaddee has added both of us to the gh-badges package. (I didn’t get a notification, and I’m not appearing on the public page, though it does show up in my list of packages.)

Sorry it has taken a while to get this sorted, but I've just published 2.0.0-beta1 to NPM:
https://www.npmjs.com/package/gh-badges/v/2.0.0-beta1
It would be useful to get a bit of feedback from those keen to get hold of a new release at this point. If there are no showstoppers, I'll cut a 2.0.0 stable.
Having done a bit of work on this, there are clearly some additional improvements we can make, but they can be done in minor releases without BC-breaks. Now that I have access to publish it to NPM, we should be able to work on incremental improvements more easily :)

Really glad to have a beta shipped! Should we open a new issue for the follow-ons, like the monorepo / repo splitting?
By the way, we've removed all the vulnerable dependencies as of latest master, which is a big improvement compared to the beta1 release.

Yep - nobody seems to have raised any major issues so I think in the next few days we should:

Release 2.0.0 without any substantial changes from the beta
Close this issue
Track further work in new issues
Put out more 2.x releases as we restructure internals

closing this as v2.0.0 is now published.


Initial python project files

Bare bones files for packaging the new library.

@jguiditta I intended to include tox.ini and Pipfile* in a follow-on patch, but maybe you're right. Here's what I have so far.

Thanks for the additional level of detail. That's exactly what I needed.
On Mon, Jan 30, 2023 at 1:12 PM jguiditta @.***> wrote:

OK, thanks for adding those, that is a good start. However, on seeing what
you added, I realize I should have been more specific. The way we have been
structuring our projects makes the Pipfile and requirements.txt files
basically convenience wrappers to allow a developer to use pipenv to manage
their development environment, should they so choose, and the requirements
fores to be used for CI and distribution. So, for example, tox.ini should
not know anything about pipenv. Also, though this could certainly change (I
am aiming for consistency here, not trying to make a new decision), at this
point we are explicitly NOT keeping the .lock file in version control.
Since this is a library rather than an application, I suspect this will
stay the path forward. As an example, if you look at
flask-container-scaffold
https://github.com/release-depot/flask-container-scaffoldl, I would
like to see similar variations of the following files:

.github/workflows/test.yml
Pipfile
requirements.txt
setup.cfg
setup.py
test-requirements.txt
tox.ini

That, combined with the stub code you just added, should get us a good
baseline to verify we have:

the proper structure to the package, so it can be installed and
found as expected
a working CI pipeline
a consistent suite of tests that we run on each PR, consistent with
our other projects.

I promise this is not as much work as it may sound like, feel free to
reach out to me if you need any help with it.
—
Reply to this email directly, view it on GitHub
https://github.com/release-depot/bugjira/pull/1#issuecomment-1409189439,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABZ54MLOREGMNWJTA5RI53WVAHCBANCNFSM6AAAAAAUJGVPAM
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Steve Linabery
Senior Software Engineer - OpenStack
Red Hat
https://www.redhat.com
@.***    IM: eggs (irc)
https://red.ht/sig


CLOUDSTACK-10132: Extend support for management servers LB for agents

The new CA framework introduced basic support for comma-separated
list of management servers for agent, which makes an external LB
unnecessary.
This extends that feature to implement LB sorting algorithms that
sorts the management server list before they are sent to the agents.
This adds a central intelligence in the management server and adds
additional enhancements to Agent class to be algorithm aware and
have a background mechanism to check/fallback to preferred management
server (assumed as the first in the list). This is support for any
indirect agent such as the KVM, CPVM and SSVM agent, and would
provide support for management server host migration during upgrade
(when instead of in-place, new hosts are used to setup new mgmt server).
This FR introduces two new global settings:

indirect.agent.lb.algorithm: The algorithm for the indirect agent LB.
indirect.agent.lb.check.interval: The preferred host check interval
for the agent's background task that checks and switches to agent's
preferred host.

The indirect.agent.lb.algorithm supports following algorithm options:

static: use the list as provided.
roundrobin: evenly spreads hosts across management servers based on
host's id.
shuffle: (pseudo) randomly sorts the list (not recommended for production).

Any changes to the global settings - indirect.agent.lb.algorithm and
host does not require restarting of the mangement server(s) and the
agents. A message bus based system dynamically reacts to change in these
global settings and propagates them to all connected agents.
Comma-separated management server list is propagated to agents on
following cases:

Addition of a host (including ssvm, cpvm systevms).
Connection or reconnection by the agents to a management server.
After admin changes the 'host' and/or the
'indirect.agent.lb.algorithm' global settings.

On the agent side, the 'host' setting is saved in its properties file as:
host=<comma separated addresses>@<algorithm name>.
First the agent connects to the management server and sends its current
management server list, which is compared by the management server and
in case of failure a new/update list is sent for the agent to persist.
From the agent's perspective, the first address in the propagated list
will be considered the preferred host. A new background task can be
activated by configuring the indirect.agent.lb.check.interval which is
a cluster level global setting from CloudStack and admins can also
override this by configuring the 'host.lb.check.interval' in the
agent.properties file.
Every time agent gets a ms-host list and the algorithm, the host specific
background check interval is also sent and it dynamically reconfigures
the background task without need to restart agents.
Note: The 'static' and 'roundrobin' algorithms, strictly checks for the
order as expected by them, however, the 'shuffle' algorithm just checks
for content and not the order of the comma separate ms host addresses.
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1740

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-2292)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 34569 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2469-t2292-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
Smoke tests completed. 65 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_10_destroy_cpvm
Failure
95.86
test_ssvm.py

test_hostha_enable_ha_when_host_in_maintenance
Error
3.83
test_hostha_kvm.py

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-2293)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33477 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2469-t2293-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
Smoke tests completed. 65 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_02_vpc_privategw_static_routes
Failure
215.78
test_privategw_acl.py

test_04_rvpc_privategw_static_routes
Failure
336.79
test_privategw_acl.py

test_hostha_enable_ha_when_host_in_maintenance
Error
1.17
test_hostha_kvm.py

Trillian test result (tid-2300)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 30863 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2469-t2300-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
Smoke tests completed. 65 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_02_vpc_privategw_static_routes
Failure
191.87
test_privategw_acl.py

test_04_rvpc_privategw_static_routes
Failure
336.46
test_privategw_acl.py

test_hostha_enable_ha_when_host_in_maintenance
Error
1.94
test_hostha_kvm.py

Thanks, merging this based on test results and two LGTMs.


Cloze and remnote notes conflict with code blocks

First things first, this is an awesome plugin, thank you for making this!
I've just spent a little time testing and found the following issue. If I have a code block like the following two:
a == b && b == c

std::vector x{};

The plugin will detect the first as a Cloze task and the second as a remnote one, and has weird prompts when you open the flashcard review screen. I think anything inside code blocks should be ignored if possible (but being able to put code blocks after a multiline ? prompt is great)

Hello, I'm glad that you like the plugin!
I'll work on fixing this.
Thanks for the bug report.

Thanks!
One other issue I've just noticed: if I have a note like
How do you create a computed property in Python?
?
```
one line

another line
```

then it gets changed to
How do you create a computed property in Python?
?
```
one line
<!--SR:2021-05-20,4,270-->

another line
```

Perhaps the multiline notes should ignore blank lines if they're in the middle of a code block? This isn't a huge problem as I can add some spaces to the blank line to make the plugin skip that line

On version 1.5.2 I'm still seeing the issue @OliverBalfour mentioned in code blocks with blank lines. Adding spaces works, but it would definitely be preferable to have the entire code block be treated as a single block for review.
I tested with having a block reference ^likethis immediately after a code block. That worked great:

The block reference wasn't included in the card
The SR HTML comment was inserted after the block reference, so it won't break any block references I have to that code block.

@Masstronaut, I only did a partial fix for this issue so the blank lines bit is still pending. Changing the regex to accommodate this got a little too complicated so I decided to fix other things first.

I'll create a new issue for the blank lines bit & close this one.


Add Code Climate support to GA Pipeline

Description

This PR adds Code Climate support, removes Sonarqube, and updates the readme badges to reflect that.

SHOWCASE-1774
Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have checked that unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Further comments

PR Deployed at: https://comfort-dev.apps.silver.devops.gov.bc.ca/pr-163


Ability to clear the cache, after plugin config save

We should give the plugin developer the choice, to clear the cache, after plugin config saves.
The reasons could be like less variables in the plugin config etc.

You could archive the same by registering to Shopware_Controllers_Backend_Config_After_Save_Config_Element and \Shopware\Components\Api\Resource\Cache::delete('config') if I am not mistaken. For install() and update() it already works.
I'd rather clear the config cache after any plugin config saving automatically. But due to HTTP Cache and other caches, it will not have affect automatically anyways… so I am afraid, this seems a bit tricky and needs more consideration if we don't want to bloat the Bootstrap even more.

What would you think about a filter event at end of the function before assigning the values to the view, with the plugin as param. And the plugin developer could subscribe it and could add the invalidateCache array for the backend confirmation. That should reach it and i can remove the function from the bootstrap.
I could subscribe to Shopware_Controllers_Backend_Config_After_Save_Config_Element  and clear the config cache, but when i have a color picker in my plugin configuration, which is using the less compiler, its needs to generate the theme cache after a change. Thats the point, that i would handle with the default crud message after install/uninstall/update.
// sorry for my english :)

@dnoegel @bcremer
What would you think about a node "clear-cache" in New Plugin system to provide this actions. So we don't bloat the bootatrap and its would be a pro argumemt to switch to the new plugin system:)

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-15090.
Please use this issue to track the state of your pull request.

@shyim We decided to close this PR for now. We will reconsider to clear the config cache for any config change automatically.


When binary are in a vault, this extension causes obsidian to hang

I've noticed when I click into a folder (or at vault root) that contains a binary file (e.g. a pdf), obsidian will hang when this extension is installed. The duration of then hang depends on the size of the file. Is the extension attempting to render a binary file as text? Perhaps it should skip this for non .md files?

Yep. That's exactly what's happening. I hadn't gotten around to handling that but I think what I'll do is just display the title of those files and never consider the contents.
I'll get onto it asap.

Excellent! Once this is working for me, I think it will be really nice.

@OliverDudgeon This is now updated. Thanks for posting :)
Just update in your community plugins tab.
Changes documented here:
https://youtube.com/live/517ODVgPxz4


Move src/content/config.ts to content.config.ts

What kind of changes does this PR include?

New or updated content

Description

Move src/content/config.ts to a content.config.ts at the base of your project. See the Astro core PR to understand the change!
Remove callout that .js and .mjs are supported. This requires added tsconfig changes in order to work, and it feels premature to recommend this.

LGTM! ✅

Closing to match the Astro core PR status.


Add tutorials

Pull Request Test Coverage Report for Build 346

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

Totals

Change from base Build 336:
0.0%

Covered Lines:
2210

Relevant Lines:
2255

💛  - Coveralls


command send and hold/release

Hello Max,
first i want to say 1000 times thank you for your great work. It made my life a lot easyer!!!
Now to my question. Some planes need to hold the startet switch to run the eingine. How can i start a command an stop a command. maybe there is a new parameter needed like
Xconn.SendCommand(XPlaneConnector.Commands.StartersEngageStarter1, 1) 'Begin switch Starter
Xconn.SendCommand(XPlaneConnector.Commands.StartersEngageStarter1, 0) 'Release switch Starter
function SendCommand(Command, optional HoldReleaseKey Int)
Greetings
Heiko

Hello Max,
i´am writing at the moment on my app and i get an error. it seems that the "unregister"-function does not work. the first register is ok. the first unregister is ok. the second register is ok but on the second unregister it comes an error (exeption) that there are multible registrations. it seems, that the first unregister does not realy unregister. whats my mistake? hope you can read vb.net - code :-)
Dim DR_ElementINT As New XPlaneConnector.DataRefElement()
        DR_ElementINT.DataRef = "sim/cockpit/electrical/strobe_lights_on"
'OK
        Xconn.Subscribe(DR_ElementINT, 25, AddressOf DataRevChangedInt)
'OK
        Xconn.Unsubscribe("sim/cockpit/electrical/strobe_lights_on")
'OK
        Xconn.Subscribe(DR_ElementINT, 25, AddressOf DataRevChangedInt)
'CRASH
        Xconn.Unsubscribe("sim/cockpit/electrical/strobe_lights_on")
Greetings
Heiko
Von:   Max<EMAIL_ADDRESS>An:   MaxFerretti/XPlaneConnector<EMAIL_ADDRESS>Kopie:   pepelotte<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Gesendet:   26.01.2020 17:32
Betreff:   Re: [MaxFerretti/XPlaneConnector] command send and hold/release (#11)
I just added a new method StartCommand, I hope it helps :)
Refer to the Readme.md for an example.
Feel free to write again if you need help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hello,
I'm looking into this issue, I'll let you know as soon as possible.

Hi,
I confirm that there was a bug, when unsubscribing the previous DatRef wasn't removed from the list.
I updated the code to fix the bug and also allow multiple instance of the same DataRef.

Hello Max,
i got a new problem. i subscribe a string dataref to "sim/aircraft/view/acf_descrip".
Dim DR_ElementSTRING As New XPlaneConnector.StringDataRefElement
        DR_ElementSTRING.DataRef = "sim/aircraft/view/acf_descrip"
        DR_ElementSTRING.StringLenght = 255
        Xconn.Subscribe(DR_ElementSTRING, 25, AddressOf DataRevChangedString)
the first income value is "Fokker F50". If i switch the plane in xplane to a Piper, i get the following events. the event is released after each changed letter and not on the complete change. can you fix that?
and...can you please update then the dll in the NuGet to the latest version?
sim/aircraft/view/acf_descrip --> Pokker F50
sim/aircraft/view/acf_descrip --> Pikker F50
sim/aircraft/view/acf_descrip --> Pipker F50
sim/aircraft/view/acf_descrip --> Pipeer F50
sim/aircraft/view/acf_descrip --> Piperr F50
sim/aircraft/view/acf_descrip --> Piper  F50
sim/aircraft/view/acf_descrip --> Piper PF50
sim/aircraft/view/acf_descrip --> Piper PA50
sim/aircraft/view/acf_descrip --> Piper PA-0
sim/aircraft/view/acf_descrip --> Piper PA-3
sim/aircraft/view/acf_descrip --> Piper PA-34
sim/aircraft/view/acf_descrip --> Piper PA-34 S
sim/aircraft/view/acf_descrip --> Piper PA-34 Se
sim/aircraft/view/acf_descrip --> Piper PA-34 Sen
sim/aircraft/view/acf_descrip --> Piper PA-34 Sene
sim/aircraft/view/acf_descrip --> Piper PA-34 Senec
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G5
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G50
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 f
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 fo
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-p
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-pl
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-pla
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plan
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 1
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (W
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Wo
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Wor
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Work
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works i
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v1
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11,
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, b
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, bu
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but w
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but wi
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but wit
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but with
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but witho
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but withou
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v1
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-s
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-sp
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-spe
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-spec
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-speci
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specif
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specifi
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific f
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific fe
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific fea
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific feat
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific featu
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific featur
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific feature
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific features
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 10.5x (Works in v11, but without v11-specific features)
Von:   Max<EMAIL_ADDRESS>An:   MaxFerretti/XPlaneConnector<EMAIL_ADDRESS>Kopie:   pepelotte<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Gesendet:   17.02.2020 23:20
Betreff:   Re: [MaxFerretti/XPlaneConnector] command send and hold/release (#11)
Hi,
I confirm that there was a bug, when unsubscribing the previous DatRef wasn't removed from the list.
I updated the code to fix the bug and also allow multiple instance of the same DataRef.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hello,
I've seen what the problem is, fixing it is not as easy but I plan on
releasing an update to solve it soon.
In the meantime I've updated the nuget package, now the project target both
.Net 4.6 and .Net Core.
I'll write to you as soon as the problem is fixed.
Max
Il giorno dom 8 mar 2020 alle ore 19:40 pepelotte<EMAIL_ADDRESS>ha scritto:

Hello Max,
i got a new problem. i subscribe a string dataref to
"sim/aircraft/view/acf_descrip".
    Dim DR_ElementSTRING As New XPlaneConnector.StringDataRefElement
    DR_ElementSTRING.DataRef = "sim/aircraft/view/acf_descrip"
    DR_ElementSTRING.StringLenght = 255
    Xconn.Subscribe(DR_ElementSTRING, 25, AddressOf

DataRevChangedString)
the first income value is "Fokker F50". If i switch the plane in xplane to
a Piper, i get the following events. the event is released after each
changed letter and not on the complete change. can you fix that?
and...can you please update then the dll in the NuGet to the latest
version?
sim/aircraft/view/acf_descrip --> Pokker F50
sim/aircraft/view/acf_descrip --> Pikker F50
sim/aircraft/view/acf_descrip --> Pipker F50
sim/aircraft/view/acf_descrip --> Pipeer F50
sim/aircraft/view/acf_descrip --> Piperr F50
sim/aircraft/view/acf_descrip --> Piper  F50
sim/aircraft/view/acf_descrip --> Piper PF50
sim/aircraft/view/acf_descrip --> Piper PA50
sim/aircraft/view/acf_descrip --> Piper PA-0
sim/aircraft/view/acf_descrip --> Piper PA-3
sim/aircraft/view/acf_descrip --> Piper PA-34
sim/aircraft/view/acf_descrip --> Piper PA-34 S
sim/aircraft/view/acf_descrip --> Piper PA-34 Se
sim/aircraft/view/acf_descrip --> Piper PA-34 Sen
sim/aircraft/view/acf_descrip --> Piper PA-34 Sene
sim/aircraft/view/acf_descrip --> Piper PA-34 Senec
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G5
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G50
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 f
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 fo
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-p
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-pl
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-pla
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plan
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane 1
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (W
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Wo
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Wor
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Work
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works i
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v1
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11,
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, b
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, bu
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but w
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but wi
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but wit
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but with
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but witho
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but withou
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v1
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-s
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-sp
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-spe
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-spec
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-speci
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specif
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specifi
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific f
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific fe
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific fea
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific feat
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific featu
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific featur
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific feature
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific features
sim/aircraft/view/acf_descrip --> Piper PA-34 Seneca V w/G500 for X-plane
10.5x (Works in v11, but without v11-specific features)
Von: Max<EMAIL_ADDRESS>An: MaxFerretti/XPlaneConnector<EMAIL_ADDRESS>Kopie: pepelotte<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Gesendet: 17.02.2020 23:20
Betreff: Re: [MaxFerretti/XPlaneConnector] command send and hold/release
(#11)
Hi,
I confirm that there was a bug, when unsubscribing the previous DatRef
wasn't removed from the list.
I updated the code to fix the bug and also allow multiple instance of the
same DataRef.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/MaxFerretti/XPlaneConnector/issues/11?email_source=notifications&email_token=ACYWYQTREGCAXW2JJKAQWO3RGPRBFA5CNFSM4KLV6ST2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOE5VIY#issuecomment-596236963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYWYQTVVURVYQP5VTT4NTLRGPRBFANCNFSM4KLV6STQ
.


python310Packages.vivisect: switch to pythonRelaxDepsHook

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 232191 run on x86_64-linux 1

12 packages built:

flare-floss
flare-floss.dist
python310Packages.viv-utils
python310Packages.viv-utils.dist
python310Packages.vivisect
python310Packages.vivisect.dist
python311Packages.viv-utils
python311Packages.viv-utils.dist
python311Packages.vivisect
python311Packages.vivisect.dist
vivisect
vivisect.dist


Detecting failed permission and

Hello, great library! Thanks.
If the user refuses to grant permission, should this through an error to the error handler?
At least on Safari, instead it logs an unhandled rejection:

Or could it be another state variable like isTorchAvailable, "isCameraAvailable"?

Also on another related note I wanted to overlay some controls on the video, and I found making use of:
  const [ready, setReady] = useState(false);
  useEffect(() => {
    // Only show overlay with controls (torch, close) once actual video stream is displayed.
    const loadedListener = (e) => setReady(true);
    if (ref.current) ref.current.addEventListener('loadeddata', loadedListener);
    return () => current?.removeEventListener('loadeddata', loadedListener);
  }, [paused]);

Since there's already the ref to the video in case this is helpful to anyone.
Thanks again, one of the few react qrcode libraries that work out of the box these days.

Released in 2.0.0!

I will also consider your other note on listening to the loadeddata event. However, I'm not sure if this should be within the scope of this library.

Definitely.
One recommendation I think worth adding is an alternative loader such as
file input (which could be used if permissions fail).
Great work!
On Thu, Aug 17, 2023 at 10:08 AM Adam Alfredsson @.***>
wrote:

I will also consider your other note on listening to the loadeddata
event. However, I'm not sure if this should be within the scope of this
library.
—
Reply to this email directly, view it on GitHub
https://github.com/adamalfredsson/react-zxing/issues/15#issuecomment-1682355037,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZT4U3OKMJ65S5ZWRC5SVDXVYQVVANCNFSM6AAAAAAYYZMA6Y
.
You are receiving this because you authored the thread.Message ID:
@.***>


Text in Input-Boxes is sometimes not readable

The Text of sometimes not readable, especially in the FBI-Questionary in Question 19. If you enter more than one line of Text, some of the Text hides.

When the "No comment" field is to small, the text is not fully shown.


Unable to run in ubuntu 22.04

I am experiencing issues running the basic implementations from provided example files. I'm stuck at 1.0fps for some reason. I see the gpu usage spike sometimes but then it comes down to 0% and the simulator freezes for some reason. I tried reinstalling everything and following everything in the installation steps but still am not able to get it to work.

Some users experience the similar thing before: https://github.com/metadriverse/metadrive/issues/154 . There must be something wrong with the graphics card driver or OpenGL. Could you set debug_panda3d=True and debug=True in the config file when launching the simulation? The debug message may contain something helpful.

I reinstalled everything from X11 setup and nvidia drivers and now it works fine when i run it natively with native monitor. I tried using virtualgl with X11, with XPra and now running over TurboVNC but still it does not work. I'm able to run other graphics applications over vnc though. But for metadrive i'm stuck at 0.2fps or something like that. I could not find a better way to remote access it. Default RDP does not work as well.

I had a really hard time figuring this issue but this was related with .xconf file. When trying to run headless and then also run glx applications can be very complicated. Thus both x11 and turbovnc both with vgl worked well in my case. x11 was fine as i had a gigabit ethernet connected to the server. Here are the changes that I made to the .xconf file.
In Section "Monitor":
......
#Option         "DPMS"
Option         "dpms" "false"
In Section "Device"
......
Option "AllowEmptyInitialConfiguration" "true"
and finally added a new section "ServerFlags"
Section "ServerFlags"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
Option "dpms" "false"
EndSection
Here is my full xorg.conf file:
nvidia-xconfig: X configuration file generated by nvidia-xconfig
nvidia-xconfig:  version 535.154.05
Section "ServerLayout"
Identifier     "Layout0"
Screen      0  "Screen0"
InputDevice    "Keyboard0" "CoreKeyboard"
InputDevice    "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier     "Mouse0"
Driver         "mouse"
Option         "Protocol" "auto"
Option         "Device" "/dev/psaux"
Option         "Emulate3Buttons" "no"
Option         "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier     "Keyboard0"
Driver         "kbd"
EndSection
Section "Monitor"
Identifier     "Monitor0"
VendorName     "Unknown"
ModelName      "Unknown"
#Option         "DPMS"
Option         "dpms" "false"
EndSection
Section "Device"
Identifier     "Device0"
Driver         "nvidia"
VendorName     "NVIDIA Corporation"
Option "AllowEmptyInitialConfiguration" "true"
EndSection
Section "Screen"
Identifier     "Screen0"
Device         "Device0"
Monitor        "Monitor0"
DefaultDepth    24
SubSection     "Display"
Depth       24
EndSubSection
EndSection
Section "ServerFlags"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
Option "dpms" "false"
EndSection
Please find the reference here:
https://groups.google.com/g/virtualgl-users/c/d8k1ujwKJXo/m/79QYFBf8AAAJ


Level8

Migration to Level 8.0.0 while still  supporting Level 6.0.1 and 7.0.1 as discussed in #27

As discussed this is a work in progress ;-)

@mcollina I would like to know your opinion here. Does it make sense to support all those level versions or should we drop old ones and keep only latest maintained?

if a next version of Aedes would switch to iterators as well we could ditch streams all together

I'm not a fun of iterators as I think them make the code less readable. BTW Matteo has a deep knowladge of nodejs core so I think could tell us if them are more or less (or equal) to streams in performances. IMO streams are the best ones as the backpressue it's handled internally by nodejs

Funny enough I find that the iterator approach is more readable to me (personal pref ;-)) than the streams approach.
Last commit has removed all the internal streams handling so you can check for yourself which one you like better.
The streams handlers that got removed (callback-stream, though2 etc) are all third party dependencies and some have not been updated in 6 years or so. That does not need to be a bad thing, but feels a bit uncomfy to me ;-)
Happy to undo last commit if you all feel that we should stick streams.

Is you PR ready for review?

Yes, I'd like to think so :-)
It is functional complete and I tested it against Level 6.0.1, 7.0.1 and 8.0.0
Package.json now contains an engines field to warn against pre-14 installs
Removing through2 and concat-stream triggered a bug in aedes-persistance,although aedes-persistence-level does not use these modules they need to be installed to be able to test.
Error: Cannot find module 'concat-stream'
Require stack:
- /homedir/aedes-persistence-level/node_modules/aedes-persistence/abstract.js

We might want to move those in package.json of aedes-persistance from devDependencies to dependencies, once that is done they can be removed here ;-)
We could add, as usual ;-), some more ideas:

[ ] add typescript defs
[ ] add testing in CI for the various Level versions (if we need to still support those ;-))
[ ] generalize the db.get, db.put so we don't have to have to specify encoding and msgpack in every functional call
[ ] migrate internals from callback style to async/await to prepare for the future (Level can work with both styles)
[ ] create a separate "LevelPersistenceClassic" class with the streams and callbacks on top of a new "LevelPersistence" class that exposes generators and async/await style so any future version of Aedes can switch from the classic interface to the modern interface (but only if Matteo sees this as the way forward too ;-))

But then again you might want to see separate PR's for these, just let me know :-)

generalize the db.get, db.put so we don't have to have to specify encoding and msgpack in every functional call

I would do this for now, I like all your idea except the last one that would require a huge rewrite of also other persistences like mongodb and redis included aedes itself.
About the types I wish to move aedes to typescript one day but my free time in last months have been really low and also there I dunno if Matteo would agree with that or just prefers types definitions

I would do this for now, I like all your idea except the last one that would require a huge rewrite of also other persistences like mongodb and redis included aedes itself.

One could stick to the current API indefinitly, however it would not be to hard to create 2 shims:

classic2modern (as mentioned above) to facilitate current Aedes to continue to use the current API while persistences migrate to a more modern API
modern2classic to facilitate Aedes to use persistences that use the currrent API while Aedes has already migrated to a more modern API

However that would only make sense when there is benefit in moving from streams to iterators and from callbacks to async/await.

About the types I wish to move aedes to typescript one day but my free time in last months have been really low and also there I dunno if Matteo would agree with that or just prefers types definitions

Just adding the type definitions without going full typescript would help implementers of other persistences, however it might be more convenient to start that with aedes-persistence first as that is more or less the golden standard ;-) Once the TS interface definitions have been sorted it becomes much more easy to migrate persistences to typescript if desired since much of the typing has already been done by then ;-)
Anyways: I will try to tackle generalization of the db.get/put/del for now first ;-)

Ok, I generalized the encoding/decoding of db.get/put etc
I also tried to use standard private fields and private methods however Standard.js does not support those yet  so I had to revert to _ again :-(
The example in example.js is now also modernized ;-)
Cheers,
Hans

@seriousme For a cleaner code so, let's drop old Level versions support.
@mcollina What about the usage of generators in place of streams?

Removed support for Level < 8.0.0
Btw: the generators only replace streams internally, the interface to Aedes still supplies Node.js Readable streams ;-)

Thankks @seriousme


increase timeout to ~3000ms instead of 1000ms

1000 is probably cutting it too close for some fm data fetch scripts.

increased to 3000


Forge Armory TTP Folder Structure

Proposed Changes
Recommending the tree structure of Forge Armory be changed to reference the MITRE ATT&CK structure for TTPs. The changes I have made create three parent folders (Enterprise, Mobile, and ICS) that display the tactics. Within each folder will be a main folder that lists the techniques (Reconnaissance, Execution, etc.) and their respective technique IDs. Within each of the technique folders will be a message digest that provides an summary of what each technique means. Next, there will be three subfolders for linux, mac, and windows operating system commands in the event that code for one operating system needs to be different for another (e.g., windows commands vs linux commands). The procedures (YAML files) will be within a folder that contains the sub-technique ID and name. There will also be a link to the MITRE ATT&CK webpage for viewers to refer back to within the message digests.
Example of a folder structure with naming convention applied:

ForgeArmory/ttps/Enterprise/TA0007-Discovery/mac/T1087-Account_Discovery/T1087.001-Local_Account/list_local_users.yaml

I believe this will help platform users who are not well versed in the realm of TTPs better understand each one. Lastly, the new structure will help account for growth of newly developed TTPs and where they should be placed within ForgeArmory.
Related Issue(s)
Not applicable.
Testing
Not applicable.
Documentation
Several message digests have been created that contain a summary of each technique as it is stated on the MITRE ATT&CK website.
Screenshots/GIFs (optional)
Not applicable
Checklist

[x] Ran mage runprecommit locally and fixed any issues that arose.
[x] Curated your commit(s) so they are legible and easy to read and understand.
[x] 🚀

Thanks for the contribution!
We've run a lot of TTPs that do not have proper representation in that particular framework. Once you get into daisy-chaining, the translation becomes even more challenging.
In terms of the layout for TTPs, I wanted to try and have it to be as intuitive as possible to find and run a TTP, while minimizing avenues for duplication. For example, you can have a TTP that works for macOS, and linux. There are even cases where you may have a TTP that works on virtually all relevant operating systems. If we group by OS, then we end up with duplicate TTPs or have to do something like a symlink, which I don't love.
In an ideal world, I'd love to find a happy medium between the intuitive layout of nuclei-templates and the deduplication of module concerns that msf has achieved.


Turndown Error on application using Webpack.

Hi, I'm trying to make an Electron application using Webpack and Typescript, and I'm encountering an error trying to include Turndown in my project.
Even just including turndown (import * as Turndown from 'turndown';) prompts this error in the console:
App threw an error during load
ReferenceError: BigInt is not defined
    at createLongLongConversion (/home/aurailus/Documents/Projects/Aether/node_modules/turndown/node_modules/webidl-conversions/lib/index.js:162:51)
    at Object.<anonymous> (/home/aurailus/Documents/Projects/Aether/node_modules/turndown/node_modules/webidl-conversions/lib/index.js:224:24)
    at Object.<anonymous> (/home/aurailus/Documents/Projects/Aether/node_modules/turndown/node_modules/webidl-conversions/lib/index.js:431:3)
    at Module._compile (internal/modules/cjs/loader.js:711:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:559:12)
    at Function.Module._load (internal/modules/cjs/loader.js:551:3)
    at Module.require (internal/modules/cjs/loader.js:658:17)
    at require (internal/modules/cjs/helpers.js:20:18)

I am using node v12, BigInt is defined.

webidl-conversions is a dependency of jsdom. jsdom was replaced by domino and is not a production dependency since Turndown 7. So this error should no longer happen. Can you please verify it?

Unfortunately I'm no longer using Turndown in my application, so I'm not able to test. Apologies!


Provision to sort ISOs from UI, and Updated Templates/ISOs API response to return in the order of sortkey.

Description
This PR allows ISOs sorting from UI, and updates the Templates/ISOs API response to return in the order of sortkey.

Fixes: #5731

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] 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)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

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

Screenshots (if appropriate):

How Has This Been Tested?

Manually tested the Templates/ISOs sorting from the UI.

@blueorangutan package

@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1989

@blueorangutan test

@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-2718)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 31483 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5800-t2718-kvm-centos7.zip
Smoke tests completed. 91 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File


[Feature request] Add send amount in USD

As far as we have price in app would be very helpful to send USD amount(when exact etc amount is not the case).
Use cases:

Send a friend 10$ in BTC to hook him up
Send Sparrow dev 20$donation, calculating sats amount is just another obstacle and friction and it takes time. Will send once implemented.

Example from Trust Wallet:

Not sure if that's the path forward. Why would you want to measure you bitcoin in depreciating fiat? It's "convenient" bc it aligns with how we measure value today, I get that. But to overcome a broken system you have to change your mind-setting. In your mind send him bitcoin, not fiat. Send him how much he needs to fund a trade in HodlHodl or Bisq.

Not sure if that's the path forward. Why would you want to measure you bitcoin in depreciating fiat? It's "convenient" bc it aligns with how we measure value today, I get that. But to overcome a broken system you have to change your mind-setting. In your mind send him bitcoin, not fiat. Send him how much he needs to fund a trade in HodlHodl or Bisq.

Don't be maxi

+1

I really dont get it.
Any bitcoin wallet allows this action, and it's pretty obvious: you agree with the recipient the transaction amount in fiat, so how can you send the exact amount from sparrow?

I also agree. The amount is shown in fiat when you enter a BTC / sat amount. You should be able to enter the amount in the configured fiat currency as well.

I really do hope that all you guys begging for being able to send "USD/fiat" amounts get rug pulled by a faulty exchange rate so that you accidentally "send" $5 but with an exchange rate of $1/BTC...goodbye to your 5 BTC you just transferred.

Do you also worry about entering 50,000 BTC instead of 50,000 sats? Or is this just an excuse because you have this maxi purist position? You were the one who started the insane issue to remove all fiat references from the app after all, right?

No, it's not an excuse, just a wish.
No, it's not a maxi position as those would argue more in the line of you & all the others (make it easy for newcomers, mass adoption, ngu,  I just want to send my fiat bro...)
Yes, it's a purist view.
Yes, I started the "insance" discussion to remove all fiat references (how do other people use wallets where no fiat is displayed....magicians?)
Yes, I think the more fiat in a wallet appears the dumber it's users are and/or will become.
Yes, you will see that as an insult but it's like with every thing: put enough abstractions on top and nobody will bother to still understand the fundamentals.
I'll give this space 2 more halvings and most "bitcoiners" won't even understand why their wallet sends 2 different btc amounts if they send the exact same USD amount at different times.

No, it's not an excuse, just a wish.
No, it's not a maxi position as those would argue more in the line of you & all the others (make it easy for newcomers, mass adoption, ngu,  I just want to send my fiat bro...)
Yes, it's a purist view.

Ok, great. Make it an option - you should be able to hide all fiat values if you don't want to see them

Yes, I started the "insane" discussion to remove all fiat references (how do other people use wallets where no fiat is displayed....magicians?)

I literally can't think of a single wallet like off of the top of my head.  It's the exception, not the rule.

Yes, I think the more fiat in a wallet appears the dumber it's users are and/or will become.
Yes, you will see that as an insult but it's like with every thing: put enough abstractions on top and nobody will bother to still understand the fundamentals.

Then why allow public servers? Why allow turning off tor? Why allow "efficiency" transactions? Maybe every sparrow user should run a full node, fulcrum server, and sparrow should only allow coinjoin transactions?

I'll give this space 2 more halvings and most "bitcoiners" won't even understand why their wallet sends 2 different btc amounts if they send the exact same USD amount at different times.

Sorry, but that's BS. We're the ones running our own nodes and electrum servers, and we're saying right now there's value still in thinking in terms of both BTC and fiat. People understand what an exchange rate is, no one is asking sparrow to protect them from their own stupidity. An advanced wallet should have advanced features but still be accessible to new users.

Tor can be DDoS'ed so you need an alternative way to connect (e.g. via VPS). "efficient" tx are normal bitcoin transactions why should they be a problem (if not for privacy)? Public servers are also bad for privacy but other than that, why not?

But that's my point - why allow these compromises (breaking privacy, etc) but be so hung up on showing fiat values?

Because they are inherent system limitations of bitcoin, networking etc. but FIAT isn't.

Sparrow is offering a compromise that violates the "best practices" for the sake of usability.

You have it completely backwards: it offers different ways to connect to the bitcoin network and offers from standard to privacy enhancing transactions everything. The focus is on enhancing.
As I said, these enhancements come all down to solutions to basic problems on the protocol or networking layer.
YOU on the other hand impose an outside unit of account (fiat) ONTO bitcoin which simply has no relevance in the world where the wallet operates. The wallet doesn't send fiat, the wallet doesn't receive fiat so it makes no sense to try and stuff a $5 "Send" button onto the wallet because it CAN'T SEND your imaginary exact $5.

You have it completely backwards: it offers different ways to connect to the bitcoin network and offers from standard to privacy enhancing transactions everything. The focus is on enhancing.
As I said, these enhancements come all down to solutions to basic problems on the protocol or networking layer.

OK, great. Right now there is a basic problem - no matter how much you want to deny it, exchange rates are a thing - Bitcoin is still expressed in BTC-USD, or BTC-EUR, etc. No one is forcing you to think in terms of the exchange rate if you don't want to. Go use Samourai if you don't want to see fiat values. you've been making this argument since 2021 - has anyone really stopped thinking in terms of the fiat value of BTC since then?

Right now there is a basic problem - no matter how much you want to deny it, exchange rates are a thing - Bitcoin is still expressed in BTC-USD, or BTC-EUR, etc.

I don't deny as you proclaim. As you very rightly stated there's a basic problem and that is people pricing Bitcoin and goods in fiat.
I would describe the conflict we have more in terms that people think differently about this problem and the consequences of how it should be handled. You all want to make life easy by removing the pain of having to deal with native Bitcoin by making it as much fiat as possible. I guess for "inclusiveness" you'd be willing to remove every bit that normies could find irritating on Bitcoin just so they're "onboard". I further guess that you think somewhere in the future (on a supposed bitcoin standard) this all magical reverses and people deal in sats.
I think this describes the slow death of Bitcoin as it will never happen. If you dance with the devil, the devil doesn't change, it changes you.

has anyone really stopped thinking in terms of the fiat value of BTC since then?

That's like regulators pointing at a market fully distorted from their regulations and screaming "look capitalist, your free market doesn't work, we need more regulations".
How on earth should people learn to price things in bitcoin if all you do is put more fiat on top so that they don't have to? You're really blaming me that no one adopts a btc denomination while crying that people need fiat in a wallet? Really?


skywaling 8.5 Storage issues

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion

Question
It was found that after skywaling was upgraded from 7.0 to 8.5, the data volume of es index sw_segment-xx increased by almost half under the same service volume and visit volume.
For advice, which parameter is related to the size of segment-index data in version 8.5?

Check changelog. I think we don't change segment entity for a long time.


Add IMAGE_OS_VERSION to image-builder buildspecs

Add IMAGE_OS_VERSION to image-builder buildspecs.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve

/cherry-pick release-0.19


feat: add skip option

Since PR #75 has been open for quite some time now, I wanted to implement my own skip option.
This PR uses the Seek trait as suggested.
resolves #16 and #87

@sharkdp Should I try to make it compile on Rust 1.31 or would you rather like to increase minimum required Rust version?

Thank you for your contribution. I bumped the min. required Rust version to 1.36 and "backported" it to this version (by matching on Input::* instead of Self::*).
I also removed the RefCell layer as it is not needed.

This will also fail if the input is not a file, but a pipe, for example (this is not "reading from STDIN"):
❯ hexyl <(echo test) --skip 2
Error: Illegal seek (os error 29)

Maybe we could catch that specific OS error and print a similar error message.
Another thing: when using --skip N, shouldn't the display offset be set to N? (unless the user explicitly specifies it).

I changed the error message to what you suggested. It will now also catch this specific OS error and display a proper error message.
You're right about the display offset, so it will now use skip as a default, if the user does not specifiy it.
It should still be possible to implement the --range N:M option. I think it would even make it easier, because you basically just have to parse it and set skip and length respectively.


haxePackages.hxcpp: 3.4.64 -> 4.1.15

Motivation for this change
hxcpp 3.4.64 failed compiling due to missing xlocale.h. This is resolved with the most current version
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review. If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108183 run on x86_64-linux 1

1 package built:

hxcpp (haxePackages.hxcpp)

This is a semi-automatic executed nixpkgs-review. If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.


Use GraphJSON to track organization's progress

Closing. @kamilkisiela feel free to reopen/prioritize if needed.


Increase pickaxe power

Is your feature request related to a problem? Please describe.
Most pickaxes are very underpowered
Describe the solution you'd like
Increase the mining speed of pickaxes
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Fixed in v1.5.1


Mendix Runtime Overview Diagram

Page link: mendix-runtime
Document link: _index.md
I think this diagram is a little bit too busy and could be perhaps split into two sections or simplified (and it could use a different colour scheme)

Hi Alastair,
Thanks for your suggestion. I will ask our design department to have a look at how this can be improved.


Which layers of the model are finetuned?

I understand when we set 'by_name=True', only those layers with same names will be loaded with weights and the rest finetuned. But can I know which section of layers exactly in yolo.py will be finetuned? And where are we initializing the weights of these layers? Thanks!
    if os.path.exists(saved_weights_name):
        print("\nLoading pretrained weights.\n")
        template_model.load_weights(saved_weights_name)
    else:
        template_model.load_weights("backend.h5", by_name=True)

Hello，have you figure out  this problem?

@yuyijie1995 , Nope. I haven't

I am inspecting the backend.h5 file, found 249 variables of yolo inside the h5 file. only 10 variables are missed, they are ['conv_81', 'input_3', 'input_2', 'conv_93', 'input_4', 'conv_105', 'input_5', 'yolo_layer_1', 'yolo_layer_2', 'yolo_layer_3']. besides the input layer(for input) and yolo layer(for caculating loss). only conv_81, _93, _105 are missed, they are the last conv layers which have the specific num_classes outputs, maybe only finetune these layers


merge takes only 1 argument

when trying to use merge with more than 1 arguments it throws a ReqlDriverError
it should accept multiple arguments to merge.
From the docs:
Command syntax
singleSelection.merge([object | function, object | function, ...]) → object
object.merge([object | function, object | function, ...]) → object
sequence.merge([object | function, object | function, ...]) → stream
array.merge([object | function, object | function, ...]) → array
Description
Merge two or more objects together to construct a new object with properties from all. When there is a conflict between field names, preference is given to fields in the rightmost object in the argument list. merge also accepts a subquery function that returns an object, which will be used similarly to a map function.

Fixed in 2.1.12.


Simplify the way we explain how to test cookies in controller

The previous documentation was old and was not clear enough to help
developers to understand properly how to test cookies inside a
controller test. Since then it is much easier to test cookies if you
stick to cookies and don't use response.cookies.
You can use response.cookies when you don't change cookies inside your
test.
def show
  cookies["user_name"] = nil
  head 200
end

RSpec.describe SignOutsController, type: :request do
  describe 'GET /signout' do
    it "clear cookie value" do
      get "/sign_out"

      expect(response.cookies["user_name"]).to eq(nil)
    end
  end
end

Use cookies to set and expect when you set cookies inside your test
def show
  cookies.delete("user_name")
  head 200
end

RSpec.describe SignOutsController, type: :request do
  describe 'GET /signout' do
    it "clear cookie value" do
      cookies["user_name"] = "Sam"

      get "/sign_out"

      expect(cookies["user_name"]).to eq("")
    end
  end
end

This is the preferred way.
Related:

https://github.com/rspec/rspec-rails/issues/1993

Can we stick rubocop version...? It is failing way too often.

LGTM, merge on green!


Lightbridges don't trigger detectors with lightbridge setting

ISSUE 500 WOOOO!

Turns out it was just an issue with the mappack, after some quick tests there is no problem with it


Hyperion crashes on Pi2 (process dead...)

Im using a Raspberry Pi 2 with raspbian (2015-02-16-raspbian-wheezy) for external video sources.
I can use the stk1160 video grabber and the one with a fushicai chipsets but I get randomly crashes.
Im using the v4l2grabber with a frame decimation of 2 and a size decimation of 8.
The load is about 9%.
I also using linear smoothing and blackborder detection.
Everything is working perfect but the LEDs sometimes stop.
When I enter "sudo service hyperion status" I get "process dead but pidfile exists".
I can start hyperion again with "sudo /etc/init.d/hyperion start" but it will crash most of the time in a few minutes.
Sometimes a reboot seems to help.
First I thougt it was a driver issue of the STK1160 but it happened several times to a fushicai grabber as well.
I also formated the sd card and started with a clean raspbian (2 times) but the problem still exists.
Im using an active USB-Hub.
Sometimes the Pi 2 does not start properly and I get a bootloop.
I think these 2 problems have different reasons but I wanted to say it.
I hope anyone can help me!

I have the same issue with the pi B (512M)
Perhaps we should look into the rpi firmware, I think the problem is there since I upgrade it...

@p1n9
@Phil1988

Sometimes the Pi 2 does not start properly and I get a bootloop.
You should sort this out first. Maybe problems with your usb hub or half dead sd card
You should power your Pi and LEDs with the same power source to prevent problems.

Closed due to lack of information


Add possibility to display line numbers in Markdown files

Gitea version (or commit ref):
1.11.4 built with GNU Make 4.1, go1.13.9 : bindata, sqlite, sqlite_unlock_notify
Git version:
Operating system: Linux 5.6.7-arch1-1
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
The line numbers are displayed for text files, but since Markdown is processed on the web interface, line numbers are not displayed.
Is it possible to display line numbers in Markdown files from the web interface?
In my case, I write project documentation in Markdown and I would like to be able to refer/quote some Markdown content with the line numbers inside issues.
Thanks :)

This feature has also been asked on Github:
https://github.com/isaacs/github/issues/297


editing config.json

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I wish to attach a network to a container after it has already been created, i.e.
The functionality of "docker network connect"
Since there is no similar API in podman, I tried to do this by editing the container's config.json manually. But the config does not stay when the container is started. How to overcome this?
Steps to reproduce the issue:

Create and start a container:
podman run -it --name "container" --network=mgmtnet img_v1 /bin/bash

stop container:
podman stop container

Edit config.json at:
/var/lib/containers/storage/overlay-containers/60dfc044f28b0b60f0490f351f44b3647531c245d1348084944feaea783a6ad5/userdata/config.json

I add an extra netns path in the namespaces section in config.json.
"namespaces": [
            {
                "type": "pid"
            },
            {
                "type": "network",
>>              "path": "/var/run/netns/cni-8231c733-6932-ed54-4dee-92477014da6e",
>>[+]           "path": "/var/run/netns/test_net"
            },
            {
                "type": "ipc"
            },
            {
                "type": "uts"
            },
            {
                "type": "mount"
            }
        ],

Start the container:
podman start container

Describe the results you received:
I expected a new interface inside the container corresponding to the namespace I supplied in config.json.
The changes in config.json should persist.
Describe the results you expected:
New interface not found in container. On container start (step-4), config.json reverts back to original and my changes are wiped out.
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:            1.4.2-stable2
RemoteAPI Version:  1
Go Version:         go1.12.8
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.12.8
  podman version: 1.4.2-stable2
host:
  BuildahVersion: 1.9.0
  Conmon:
    package: podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.1-dev, commit: unknown'
  Distribution:
    distribution: '"rhel"'
    version: "8.1"
  MemFree:<PHONE_NUMBER>96
  MemTotal:<PHONE_NUMBER>20
  OCIRuntime:
    package: runc-1.0.0-60.rc8.module+el8.1.0+4081+b29780af.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.1-dev'
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 16
  hostname: bng-ix-svr1.englab.juniper.net
  kernel: 4.18.0-147.el8.x86_64
  os: linux
  rootless: false
  uptime: 2h 27m 43.71s (Approximately 0.08 days)
registries:
  blocked: null
  insecure: null
  search:
  - registry.redhat.io
  - registry.access.redhat.com
  - quay.io
  - docker.io
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 4
  GraphDriverName: overlay
  GraphOptions: null
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 2
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
#rpm -q podman
podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="8.1 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.1"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.1 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8.1:GA"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.1
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.1"

This is not supported via manual editing. We regenerate the configuration for each run of the container and immediately pass it into the OCI runtime as part of the container creation process.
Podman theoretically supports "pre-create" stage OCI hooks that receive the OCI spec before the container is created and have the option to process it, but I don't believe this has been tested in a number of releases (the original intended user did not require it in the end).

Also, adding extra network namespace paths is not supported. The spec allows at most one.
You need to edit the container's existing network namespace.

Also, may I ask what you're trying to do with network connect?

Hi Matthew
Q "Also, may I ask what you're trying to do with network connect?"
I wish to create macvtap interface connectivity between host and container.
Macvtaps require a physical interface on host for creation, but this info is not known at the time of first container start, so I must somehow allow the user to configure them at a later stage.
Right now, the network namespace (mentioned in  in conf.json) gets automatically created based on the .conflist specs in /etc/cni/net.d/ folder, right? The interfaces created inside the container depend on the network names provided in 'podman run --network cli' for which these specs exist.
Ex:
podman run -it --log-level=debug --name "container" --network=jmgmtnet,cbnet img_v1 /bin/bash

will create two interfaces inside the container (corresponding to what is specified in the conflist files for jmgmtnet and cbnet):
root@d0ff7fb58a5c:/# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::6451:21ff:fea3:4264  prefixlen 64  scopeid 0x20<link>
        ether 66:51:21:a3:42:64  txqueuelen 0  (Ethernet)
        RX packets 10  bytes 618 (618.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7  bytes 558 (558.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        ether ea:34:8d:da:a7:d5  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

on the host, i can see the network namespace (only one, as you pointed out. I was mistaken that there would be more):
# ip netns exec cni-fbf321e2-5ff9-7e13-1b05-c204dd8fcc6f ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether 66:51:21:a3:42:64 brd ff:ff:ff:ff:ff:ff link-netnsid 0
3: eth1@if5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN mode DEFAULT group default
    link/ether ea:34:8d:da:a7:d5 brd ff:ff:ff:ff:ff:ff link-netnsid 0

But I have noticed that, on every container restart, the namespace name is dynamically generated and is different from the earlier name.
Ex: On container stop and restart, the new namespace is now named:
/var/run/netns/cni-15a94433-5108-0246-1026-3e3267316bca
In this case, how do I supply a new interface to an already created container?

I cannot manually create an interface on host and move it to the namespace, as the namespace will change on reboots.
I cannot supply a new network name (based on conflist spec) to a running container ( as is done via network connect functionality) as there is no such support in podman start/network cli.
You mention that manual editing is not supported via config.json as it gets regenerated everytime. There must be somewhere this raw config is getting stored, from where you regenerate the config.json?
You mention OCI hooks, is it possible to supply a conflist-spec/network to the container through them?

PS: Thanks for taking the time and helping me out with this!

Hi
Any updates?

The path to the namespace is in podman inspect as SandboxKey - that should provide the path to it in a deterministic manner. From there, you can modify the namespace itself to add interfaces. If you want to do this before the container starts, podman init should create the namespace but not start the container.

@Swatigupta1997 @mheon Can we close this issue?

Reopen if I was mistaken.


User impersonation with service accounts

I am attempting to use a Google Service Account to retrieve mail for users in the organisation.  With the Google Auth Library I can use a method like setServiceAccountUser when requesting a token to allow the Service Account to act as another user.  I have been unable to find similar functionality in yup-oauth2.   Does similar functionality already exist?
An illustration of the functionality can be found at:
https://github.com/googleapis/google-auth-library-java/blob/f9a9b8ace0199e6b75ed42c7bacfa3be30c34111/oauth2_http/javatests/com/google/auth/oauth2/ServiceAccountCredentialsTest.java

[https://developers.google.com/identity/protocols/oauth2/service-account#delegatingauthority](Elsewhere in the Google documentation) it suggests the method createDelegated instead.  yup-oauth2 appears to use the phrase "delegate" for another purpose.

Delegate domain-wide authority
If you have delegated domain-wide access to the service account and you want to impersonate a user account, specify the email address of the user account with the createDelegated method of the GoogleCredential object. For example:

GoogleCredential credential = GoogleCredential.fromStream(new FileInputStream("MyProject-1234.json"))
    .createScoped(Collections.singleton(SQLAdminScopes.SQLSERVICE_ADMIN))
    .createDelegated("user@example.com");

It appears I should be able to do
let service_authenticator = ServiceAccountAuthenticator::builder(service_account_key.clone())
<EMAIL_ADDRESS>    .build()?;

however this always results in a "Lookup failed" response when authenticating with the imap crate.
Domain-wide delegation is enabled for the organisation in the Google Admin console.

The subject being set is the subject in the JWT. After some cursory research, I've unfortunately not been able to find the right documentation about impersonation (in my memory, Google's documentation used to be a lot better??). If you have a reference, I'd love to take a closer look.
Thank you for being patient with me :grimacing:

I created a test application that uses the Google API instead of the OAuth2 API and received a message indicating the service account was not configured correctly.  The difficult here seems to be in error messages not being helpful.  It is unclear how far deep down the stack the core problem with the error message starts.
It does appear the OAuth2 subject is what needs to be set to the address of the impersonated account.
Google's documentation did used to be better. It seems like the current documentation is nothing but circular references and Capitalised Names of Things that have no definition.
I will let you know if I have more information to contribute in the future.  For now I'm on another task.  Thanks for attempting to help.

Thank you for the investigation, I hope we manage to solve this issue at some point!

@dermesser @sheldonjms did you manage to solve it?
yup-oauth2 has the ability to use Domain-wide delegation?

Problem in google-apis-rs crate. Solved here - https://github.com/Byron/google-apis-rs/discussions/487


[FEATURE] add home page

Description
👇🏽This is the design for the home page, since we have none.
The white part should be a video of how to use the website, example will be the gif in the Readme
Screenshots

It's great having you contribute to this project by creating an issue Make sure you are assigned to this before you work on it and you read the Contributing.md file, Thank you! Welcome to the community :nerd_face:

Hi Dunsin, can I be assigned to this?

You can do it now, but I will merge it when Hacktoberfest starts🙌🏽

Hey @ctoffanin can I help you with this contribution ?

If @Dun-sin is ok with it, it can be assigned to you. I don't mind.

sure @Vishrut19

Hey @Dun-sin  I was trying to work on this task that is assigned to me but I am a bit confused as what has to be done in this issue ? Can you please elaborate a bit about it to me

When you open the website, it shows nothing but the side menu
Use the design above to add text and a quick video recording of the website

okay got it @Dun-sin I will do it and yes Just wanted to ask you that is there a video recording available with you for reference.

Nope, you can make yours or use the gif in the Readme file

Can I also help in this contribution? @Vishrut19 , @Dun-sin, @ctoffanin

Can I also help in this contribution? @Vishrut19 , @Dun-sin, @ctoffanin

depends on if @Vishrut19 needs help

@Vishrut19 please let me know if you need help :)

Yes you can help me @dhrumishah

Not much but yes I have contributed. Can you let me know how can I help? @Vishrut19

Can we plan a time and connect on discord for the same (if you are from india)? @dhrumishah

Yeah sure :)
Here's my ID: Dhrumi | 0xdee#0946

Hey @Dun-sin I am done with the text thing. Can you please see if it is okay ?

@Vishrut19 looks good

okay so tomorrow can you merge my PR ?

Okay so tomorrow can you merge my PR ? @Dun-sin

If you are done

I will be working on 'inserting gif' to the website @Dun-sin

I will be working on 'inserting gif' to the website @Dun-sin

Well you can add it to he's fork version and he can create a pull request, should have both your names on it. Not sure tho.
Otherwise he has to do everything

okay @Dun-sin lets connect on discord @dhrumishah  so that we can decide how we need to move forward with the project

okay @Dun-sin lets connect on discord @dhrumishah  so that we can decide how we need to move forward with the project

There's the community discord server in the readme

Yes @Dun-sin I am connected in that discord server

Hey @Dun-sin I am done with adding gif to the page. I am attaching the picture please have a look at it and let me know if it is okay then we can move forward.

Nice, maybe a border would be nice to differentiate the video from the original background

Hey @Dun-sin please have a look at it I have tried doing something.

Hey @Dun-sin please have a look at it I have tried doing something.

Good, but the space in between doesn't look good, I think it's too much

Now @Dun-sin ! Sorry for disturbing you again and again since it is my first time thats why.

Now @Dun-sin ! Sorry for disturbing you again and again since it is my first time thats why.

No worries, it's okay now

Thanks a lot @Dun-sin then is it mergable now ? If that is the correct word 😂

Well you have to create a pull request

okay but tomorrow right ? @Dun-sin

okay but tomorrow right ? @Dun-sin  or today only?

Your choice, it's my merge that matters

okay so you will merge tomorrow ? @Dun-sin

It means tomorrow @Dun-sin ?

Description
👇🏽This is the design for the home page, since we have none.
The white part should be a video of how to use the website, example will be the gif in the Readme
Screenshots

hi, i wanted to ask apart from the description of landing page you mentioned, if one can work on generating a different , interactive landing page?

Description
👇🏽This is the design for the home page, since we have none.
The white part should be a video of how to use the website, example will be the gif in the Readme
Screenshots

hi, i wanted to ask apart from the description of landing page you mentioned, if one can work on generating a different , interactive landing page?

You can create it as a separate issue

:tada: This issue has been resolved in version 2.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix existence and type of a generated key

Execute generatedKeys.add(key) only if a key is provided.
Additionally on postgreSQL unexpected generated keys of type String are returned

Merci Philippe.
Accepted, because it does fix the bug with PostgreSQL.
It seems that when asked for generated keys, PostgresSQL returns a result set with every columns everytime, not just the generated ones. When the first column of the result set is a String, it causes the bug.
However a proper solution would be to only ask the database for generated keys when there are indeed generated keys instead of doing it every time and to mention what column if any holds the generated key. I'll look into it.


Holograms sticks to holocamera

The hologram in the scene is being moved to the origin (the cameras position) on startup.
Using SpatialMapping, WorldAnchorManager, TapToPlace and InputManager in the scene.

Make sure you don't have a script that's changing the position of your object.

I have no scripts that changes the position of the object attached to the hologram. Only the TapToPlace and the Interpolator scripts were added to my object, outside the script i created.

@DrunkReaperMatt did you ever figure out what the problem was?
btw we've updated the Hololens camera to the MixedRealityCameraParent, give it a try.