Cannot see my DFI I transferred over to my wallet and the DEX doesn't work

When checking my folder, my DFI doesn’t show in my wallet but when I go to the DEX, the amount I transferred over shows up as a swappable. Also, I have USDT and when I try to swap it and the DFI (when it shows my balance in the DEX) the currency pair in which Im trying to swap into remains at ‘0’. When I try to transfer out my USDT it the application won’t let me. Need help asap. Thanks.
App_log.zip

Hi @MAKEchelon, can you try to update the app with the latest version? v2.1.9. https://github.com/DeFiCh/app/releases/tag/v2.1.9.

Hi @MAKEchelon, can you try to update the app with the latest version? v2.1.9. https://github.com/DeFiCh/app/releases/tag/v2.1.9.

I did. Before with the earlier version, i only saw the DFI wallet there but now i see a few wallets but now I don’t see my DFI balance.

On Jan 14, 2021, at 6:13 PM, JJ Adonis<EMAIL_ADDRESS>wrote:

Hi @MAKEchelon, can you try to update the app with the latest version? v2.1.9. https://github.com/DeFiCh/app/releases/tag/v2.1.9.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I did. Before with the earlier version, i only saw the DFI wallet there but now i see a few wallets but now I don’t see my DFI balance.

On Jan 14, 2021, at 6:13 PM, JJ Adonis<EMAIL_ADDRESS>wrote:

Hi @MAKEchelon, can you try to update the app with the latest version? v2.1.9. https://github.com/DeFiCh/app/releases/tag/v2.1.9.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I tried to update it again, but same issue. Is there any update on options for me. Its time sensitive.

On Jan 14, 2021, at 6:13 PM, JJ Adonis<EMAIL_ADDRESS>wrote:
Hi @MAKEchelon https://github.com/MAKEchelon, can you try to update the app with the latest version? v2.1.9. https://github.com/DeFiCh/app/releases/tag/v2.1.9 https://github.com/DeFiCh/app/releases/tag/v2.1.9.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/DeFiCh/app/issues/301#issuecomment-760557919, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIFX6HYYDCHAQYGTYA37XJLSZ6CDJANCNFSM4WDIJVGA.

I tried to update it again, but same issue. Is there any update on options for me. Its time sensitive.

On Jan 14, 2021, at 6:13 PM, JJ Adonis<EMAIL_ADDRESS>wrote:
Hi @MAKEchelon https://github.com/MAKEchelon, can you try to update the app with the latest version? v2.1.9. https://github.com/DeFiCh/app/releases/tag/v2.1.9 https://github.com/DeFiCh/app/releases/tag/v2.1.9.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/DeFiCh/app/issues/301#issuecomment-760557919, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIFX6HYYDCHAQYGTYA37XJLSZ6CDJANCNFSM4WDIJVGA.

Similiar Issue with 2.1.10: https://transfer.sh/cwcqr/Kapture 2021-01-15 at 11.38.50.webm

Similiar Issue with 2.1.10: https://transfer.sh/cwcqr/Kapture 2021-01-15 at 11.38.50.webm

If the destination wallet contains some coins the DEX seems working as expected: https://transfer.sh/dPLUr/Kapture 2021-01-15 at 12.46.36.webm

If the destination wallet contains some coins the DEX seems working as expected: https://transfer.sh/dPLUr/Kapture 2021-01-15 at 12.46.36.webm

That’s awesome. Which version is that?

On Jan 15, 2021, at 5:48 AM, Raphael Lechner<EMAIL_ADDRESS>wrote:

If the destination wallet contains some coins the DEX seems working as expected: https://transfer.sh/dPLUr/Kapture 2021-01-15 at 12.46.36.webm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

That’s awesome. Which version is that?

On Jan 15, 2021, at 5:48 AM, Raphael Lechner<EMAIL_ADDRESS>wrote:

If the destination wallet contains some coins the DEX seems working as expected: https://transfer.sh/dPLUr/Kapture 2021-01-15 at 12.46.36.webm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi all,
I am having the same issue. I dont see any coins in my wallet but I can see them in the DEX view.
Sadly I am not able to swap as I am getting an error message every time saying something went wrong.
I tried updating the app via the appinternal update function but the app only crashed. (tried several times).
Updated now via the link sent by thedoublejay
Current DeFi App Version:
2.1.9
Previous DeFi App Version:
2.1.7
Operating System (OS):
windows 10
Uploading app logs.zip…

Hi all,
I am having the same issue. I dont see any coins in my wallet but I can see them in the DEX view.
Sadly I am not able to swap as I am getting an error message every time saying something went wrong.
I tried updating the app via the appinternal update function but the app only crashed. (tried several times).
Updated now via the link sent by thedoublejay
Current DeFi App Version:
2.1.9
Previous DeFi App Version:
2.1.7
Operating System (OS):
windows 10
Uploading app logs.zip…

Hi @MAKEchelon @Katakom88 @lraphael 	, regarding the issue DEX: something went wrong, I'll link you to https://github.com/DeFiCh/app/issues/280 which we can further discuss on the problem, please send your logs and / or screenshots there if it's new information. Let’s keep this thread related to what the original author opened. Thank you for your understanding.

Hi @MAKEchelon @Katakom88 @lraphael 	, regarding the issue DEX: something went wrong, I'll link you to https://github.com/DeFiCh/app/issues/280 which we can further discuss on the problem, please send your logs and / or screenshots there if it's new information. Let’s keep this thread related to what the original author opened. Thank you for your understanding.

Hi @MAKEchelon , update v2.1.10 is out https://defichain.com/downloads/. May I have a screenshot of your wallet screen with regards to "DFI doesn’t show in my wallet".
Can you check you balance via CLI using the following commands:
getbalance — utxo DFI
gettokenbalances — DFI
The sum of utxo DFI & DFI would be your total tokens.

Hi @MAKEchelon , update v2.1.10 is out https://defichain.com/downloads/. May I have a screenshot of your wallet screen with regards to "DFI doesn’t show in my wallet".
Can you check you balance via CLI using the following commands:
getbalance — utxo DFI
gettokenbalances — DFI
The sum of utxo DFI & DFI would be your total tokens.

Hi @Mabarkubus , tagging you here regarding the issue you're facing. Thank you.

Hi @Mabarkubus , tagging you here regarding the issue you're facing. Thank you.

@izzycsy thank you for linking me to issue #280.
However this is onlyone part of my issue. I still can not see my Defi balance in the wallet.
any chance the issues can befixed short therm? I am sure you areawareof the daily loss as long as we can not join the lequidity mining.
thanks and best wishes.

@izzycsy thank you for linking me to issue #280.
However this is onlyone part of my issue. I still can not see my Defi balance in the wallet.
any chance the issues can befixed short therm? I am sure you areawareof the daily loss as long as we can not join the lequidity mining.
thanks and best wishes.

Hi @Katakom88 , the team is investigating. I understand your concern, thank you for your patience.

Hi @Katakom88 , the team is investigating. I understand your concern, thank you for your patience.

Hi @MAKEchelon @monnyfx @adrian-schnell @Mabarkubus @Katakom88 	, update v2.1.11 is out https://defichain.com/downloads/.
Do give a thumbs up to this comment if your issue has been resolved, otherwise, you may reopen this issue with new information (include screenshots) and app logs. Thank you.

Hi @MAKEchelon @monnyfx @adrian-schnell @Mabarkubus @Katakom88 	, update v2.1.11 is out https://defichain.com/downloads/.
Do give a thumbs up to this comment if your issue has been resolved, otherwise, you may reopen this issue with new information (include screenshots) and app logs. Thank you.


Add Genius as a lyric source

Makes use of the Genius API and genius-api.com, a separate resource that
provides readable lyrics.
Fixes #1626.
This is my first contribution to beets so please let me know if anything is amiss.  I'd like to wrap some testing around this but I'm not particularly familiar with python testing frameworks, so that may take a little while longer.
Requires a new config option genius_API_key, and requests[security] to quell InsecureResponseWarnings.

This looks awesome! It will be great to have. A couple of outstanding notes:

We should mention the new backend (and its configuration) in the documentation for the plugin.
Should we apply for an official beets API key, as we do for some services, or just leave it up to the user?
It looks like Travis is reporting a few minor style issues.

I've added some documentation and fixed the style checks.  Registering the app to genius might be a good idea since we're only doing reads and they aren't user specific, I'll look into that this evening.  Is that something I should register or would it be more appropriate for the owner of the app or plugin?

Awesome!
Please do go for it. We're an open source hive-mind, so you're perfectly authorized to get the key. :smiley:

This looks great! Basically ready to merge. Two outstanding things:

Would you mind adding a brief note to the changelog about the addition?
Out of curiosity, why does this need requests[security]? Any chance there's a way around it, since beets users probably already have requests but not the security extra?

Heya,
For the first bullet point, how does the versioning work?  Should I add a note about this under 1.3.15?  I'm going to go ahead and push that out, let me know if it's incorrect.
Also, after a bit more research on the issue which prompted me to install requests[security], I'm pretty sure it's not actually necessary at all.  I'm currently running python 2.7.6 and according to this stackoverflow thread

Requests 2.6 introduced this warning for users of python prior to 2.7.9 with only stock SSL modules available.

So I think this was just an issue with my system being configured poorly.  I'll remove the dependency from the documentation.

Yes, under the latest version (1.3.15 at the moment) should do perfectly.
And awesome that the dependency situation can be simplified.
Thank you again! :sparkles:

All merged. Thanks once again.


[BUG] Mapping updates on leader with strict dynamic setting results in auto pause of replication

What is the bug?
For an actively replicating index, if the mapping is updated on the leader with dynamic set to strict, replication auto-pauses with following exception
curl -k -XGET -u $CREDS -s "$FOLLOWER/_plugins/_replication/follower-02-strict/_status?pretty"
{
  "status" : "PAUSED",
  "reason" : "AutoPaused: [[follower-02-strict][0] - org.opensearch.index.mapper.StrictDynamicMappingException - \"mapping set to strict, dynamic introduction of [place] within [_doc] is not allowed\"], ",
  "leader_alias" : "my-leader-1",
  "leader_index" : "leader-02-strict",
  "follower_index" : "follower-02-strict"
}

How can one reproduce the bug?
1. Create test leader index with dynamic set to strict
curl -k -XPUT -u $CREDS -s "$LEADER/leader-02-strict?pretty" -H \
'Content-Type: application/json' \
-d'{"mappings":{"dynamic":"strict","properties":{"name":{"type":"text"}}}}'

2. Start replication
curl -sku "${CREDS}" -XPUT "${FOLLOWER}/_plugins/_replication/follower-02-strict/_start?pretty" \
-H 'Content-Type: application/json' \
-d '{"leader_alias":"my-leader-1", "leader_index": "leader-02-strict", "use_roles": { "leader_cluster_role": "all_access", "follower_cluster_role": "all_access" } }'

3. Update mapping on leader and ingest new doc using the updated mapping
curl -k -XPOST -u $CREDS -s "$LEADER/leader-02-strict/_mapping?pretty" \
-H 'Content-Type: application/json' \
-d'{"dynamic":"strict","properties":{"name":{"type":"text"},"place":{"type":"text"}}}' &&
curl -k -XPOST -u $CREDS -s "$LEADER/leader-02-strict/_doc/3" \
-H 'Content-Type: application/json' \
-d '{"name" : "dummy data1","place":"home"}'

4. Replication Status
curl -k -XGET -u $CREDS -s "$FOLLOWER/_plugins/_replication/follower-02-strict/_status?pretty"
{
  "status" : "PAUSED",
  "reason" : "AutoPaused: [[follower-02-strict][0] - org.opensearch.index.mapper.StrictDynamicMappingException - \"mapping set to strict, dynamic introduction of [place] within [_doc] is not allowed\"], ",
  "leader_alias" : "my-leader-1",
  "leader_index" : "leader-02-strict",
  "follower_index" : "follower-02-strict"
}

What is the expected behavior?
It looks like the mapping updates aren't propagated immediately and any data with additional field results in exception that halts replication.
Ideally the replication engine should handle mapping updates seamlessly even with dynamic set to strict.

We sync the mapping from leader shard if the applyTranslogOperation returns result type as MAPPING_UPDATE_REQUIRED: https://github.com/opensearch-project/cross-cluster-replication/blob/4f790d20eeefe78f00c0810501e73bc2b5dfc1ef/src/main/kotlin/org/opensearch/replication/action/replay/TransportReplayChangesAction.kt#L123
In this particular case, IndexShard simply rejects the request as dynamic mapping is set to strict. We need additional handling for StrictDynamicMappingException(or even the parent exception MapperParsingException). Incase we encounter this exception, we should sync the mapping again from leader and retry.


44 scaladoc in comments

What has been done in this PR?

Added https://github.com/ThoughtWorksInc/sbt-api-mappings plugin for a better link creation

Documentation added in all methods and vals.

Not sure why but build is failing and there's a conflict in the plugins file. Other than that LGTM!


Suggestion for site: Android Design Patterns

Disclaimer: I am the maintainer of this blog. :)
Feel free to add if you want (you don't have to either though :P).
http://www.androiddesignpatterns.com/

I am adding this site. The only reason because of which I was having second thoughts is that the site is not updated often.

I aim for quality, not quantity. :)

That's exactly what made me add it to the list. I myself have learned quite a lot from there before.


PhantomJS v2.x support (maintaining backwards-compatibility)

This PR should allow PhantomJS v2.x to pass most of the selftests.
There are still some failures that appear to be caused by regressions that should be fixed with PhantomJS v2.0.1.
This also fixes a few issues that I found while working around failing tests.
A few points still need to be addressed before this can be considered ready:

[ ] Travis needs to be setup for PhantomJS v2.0.0
[ ] SlimerJS appears to be stalling on the CoffeeScript tests (preexisting?)
[ ] Laucher needs to be fixed so SlimerJS actually gets tested on Travis

If anyone has any comments or concerns, please let me know.
/cc @n1k0 @mickaelandrieu

SlimerJS appears to be stalling on the CoffeeScript tests (preexisting?)

Which version are you using?

Laucher needs to be fixed so SlimerJS actually gets tested on Travis

Yeah, it's been bringing false positives for too long. While you're at it, could you handle this as well?
Thanks for your help.

Which version are you using?

$ slimerjs --version
Innophi SlimerJS 0.9.6, Copyright 2012-2015 Laurent Jouanneau & Innophi

I can check into why this is happening, but i may not get to it until this weekend.

Right now Travis is using the ENGINE_EXECUTABLE environment variable, which isn't being used by either the python or the dotNet launchers.
Some options that I'm considering are to:

Update both launchers to use this env variable in addition to the PHANTOMJS_EXECUTABLE and SLIMERJS_EXECUTABLE (I'm assuming that these variables should override the generic ENGINE_EXECUTABLE if they are present)
Update the Travis config to set the correct env variable

The second option may actually end up being more work in the long run, but I'll investigate both.

With either of those options, we will need to either update both launchers to use a CASPERJS_ENGINE env variable as an alternative to the --engine= argument or allow the makefile to take arguments so that the engine can be specified.
I'm leaning towards the first option because it would make the feature available outside of our testing.
It shouldn't be much more than changing line 86 of the python launcher to:
ENGINE = os.environ.get('CASPERJS_ENGINE', 'phantomjs');

I'm leaning towards the first option because it would make the feature available outside of our testing.

Makes sense, go for it.

I forgot that the ENGINE_FLAGS variable is appended to ENGINE_EXECUTABLE
ENGINE_FLAGS="--local-to-remote-url-access=yes --ignore-ssl-errors=yes"'
...
export ENGINE_EXECUTABLE="$ENGINE_EXECUTABLE $ENGINE_FLAGS"

I'll look into this and hopefully get a patch out tonight.

Also, this patch should replace #776

My last commit was just a hunch and it looks like I was right; the ENGINE_EXECUTABLE variable is out of scope of the script section in the Travis tests.
I'll try exporting the variables, so the lines would look like:
if [[ $ENGINE == 'phantomjs' ]]; then
  export ENGINE_EXECUTABLE="engine/bin/phantomjs";
elif [[ $ENGINE == 'slimerjs' ]]; then
  export ENGINE_EXECUTABLE="engine/slimerjs";

@n1k0 Would you like me to revert the changes that I made in b042eba?

Would you like me to revert the changes that I made in b042eba?

No that's useful, so we know the executable env configuration.

@n1k0 @mickaelandrieu
I've been looking into the failing tests and it appears as though the PhantomJS v1.8.2 tests are failing due to the page.onResourceError event not having been implemented until v1.9.0 (https://github.com/ariya/phantomjs/issues/10954). Support was also not added to SlimerJS until v0.9.0 (https://github.com/laurentj/slimerjs/issues/92).
With these versions being more than 2 years old, it may be time to remove support for them. Thoughts?
Test file: /home/travis/build/n1k0/casperjs/tests/suites/casper/resources.js
# Basic resources tests
PASS Basic resources tests (5 tests)
PASS only one resource found
PASS two resources found
PASS phantom image found via test RegExp
PASS phantom image found via test Function
PASS phantom image found via test String
# "resource.error" event
PASS "resource.error" event (3 tests)
Test server url not found: /tests/site/non-existant.html (file: /home/travis/build/n1k0/casperjs//tests/site/non-existant.html) warning
⚠  "resource.error" event: 3 tests planned, 0 tests executed

With these versions being more than 2 years old, it may be time to remove support for them. Thoughts?

Definitely.

:+1:

Great! Thanks for the fundamental work to prepare phantomjs2 support. :+1:


Fix readme markdown

Github changed it's markdown parser, breaking headings that do not separate the hash from the text.
Works
# Heading
Doesn't Work
#Heading

Thanks!


BatchTileMapRenderer beginRender() and endRender() when ownsRender is false

Regarding BatchTileMapRenderer, when the Batch is passed onto the constructor, thus the renderer not owning the batch, it should not call the batch.begin() and batch.end() on beginRender() and endRender() methods (should it?). I've created a subclass that overrides both methods to change this and its compatible with other batch drawing.
@Override
protected void beginRender() {
if (ownsBatch) {
super.beginRender();
}
}
@Override
protected void endRender() {
	if (ownsBatch) {
		super.endRender();
	}
}

The idea is that you would override the begin/end render methods if you
don't want to have the default behavior of beginning and ending the batch.
I can see where you are coming from and would be ok with changing this if
others agree.
On Mar 30, 2015 4:24 AM, "Nuno Flores"<EMAIL_ADDRESS>wrote:

Regarding BatchTileMapRenderer, when the Batch is passed onto the
constructor, thus the renderer not owning the batch, it should not call the
batch.begin() and batch.end() on beginRender() and endRender() methods
(should it?). I've created a subclass that overrides both methods to change
this and its compatible with other batch drawing.
@Override https://github.com/Override
protected void beginRender() {
if (ownsBatch) {
super.beginRender();
}
}
@Override
protected void endRender() {
if (ownsBatch) {
super.endRender();
}
}
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/issues/2991.

I have subclassed BatchTiledMapRenderer as well. In my case, I found unnecessary the call to batch.setProjectionMatrix (...) inside the setView (camera) method, causing a reflush of the batch, unnecessary if the batch has already set its projection matrix - as far as I understand. The default behavior is ok though, so I think it is just ok to subclass it.

I would agree.. To me it was an unexpected behavior because I assumed that the renderer required the batch to be begun before rendering, since it didn't own it. I was forced to subclass (in my case) OrthogonalTiledMapRenderer and add in the if (ownsBatch) { ... } statements by hand.
It seems redundant (to me) to be able to pass a batch if you have no real control over it...
It might be an a good idea to add such a subclass out of the box.


Add a Closer function to the notifier

Expected behavior
All errors make it to bugsnag, especially panics, even when Synchronous mode is off.
Observed behavior
I may be wrong, but looking at the code: there is no guarantees that in case of a recovered panic with Synchronous mode off an error makes it to bugsnag as the goroutine is not protected from exiting the application (if the panic is so fatal that the application has to exit).
Adding a closer function which can be registered as a deferred function could make sure that before exiting the application all pending errors are actually sent to Bugsnag.
Version
1.3.1

I'm familiar with that documentation, but I believe even then there is a case that the error gets lost.

I have the same problem. If I log a Fatal error, my program exits before Bugsnag can publish the error when Synchronous mode is off.
Would you be open to adding a Configuration value for a sync.WaitGroup? The reportPublisher can increment/decrement the WaitGroup when it starts a delivery, and I can wait to exit until the WaitGroup is done.
I can create a PR if you're interested but don't have the bandwidth.

Hi @countingtoten
Thanks for the offer, but I'm not sure we'd accept a PR at present. We'd like to more carefully consider other possible scenarios here and decide on the best way forward.
I'd suggest forking the repo in the short term with your proposed approach, and we'll report back on this issue when we've considered the best long term fix.


Article in medium for commenting (part 2 of learning graphs with ipycytoscape)

Dear @marimeireles & @ianhi,
I have ready a second article:
https://joseberlines.medium.com/part-2-learning-graphs-with-ipycytoscape-the-train-rail-net-grows-up-db2daa2f453d
it is yet unlisted.
If you have time the coming days can you please have a look and make any comment here before I made it available to everyone?
thanks

Hi @joseberlines, it's awesome that you're writing things like this. Overall I think that this could be very helpful to someone starting out learning how to visualize graphs! Content wise I don't think you've any mistakes, however one really nice improvement to the graphs could be to make the sizes of the edges correspond to the speed of that train connection.
I also have a few practical notes:

It would be nice to have a link to the first article at the beginning
Some of the lists don't seem be formatting such that they are properly indented. For example I'd expect this to have each point indented:

There are some grammar and spelling errors scattered throughout. For stuff like this I like using https://www.grammarly.com/ as it will help with phrasing in addition to the spelling of words.

Thanks. I will revisit grammar. My English is quite ok but i am not used to write articles.

Can you give me a hand here?

Hi @joseberlines, ... however one really nice improvement to the graphs could be to make the sizes of the edges correspond to the speed of that train connection.

I would love to do that but:
I see in the style file of the Gene graph the following:
"width": "mapData(score, 0, 0.006769776522008331, 20, 60)",
"height": "mapData(score, 0, 0.006769776522008331, 20, 60)",
So it looks like it is proportional to the score.
Why width and height if they are circles? I would expect a unique parameter like radius.
In the same file I see that there is another node with shape "rectangle" but that one without height and width.
Let me know how you pass the size and I would add it to the notebook and article.
thx

Hey @joseberlines check it out this part of the docs: https://js.cytoscape.org/#getting-started/specifying-basic-options
I think it might help, they have a json tweaking edges:
     selector: 'edge',
      style: {
        'width': 3,
        'line-color': '#ccc',
        'target-arrow-color': '#ccc',
        'target-arrow-shape': 'triangle',
        'curve-style': 'bezier'
      }


ARROW-12965: [Java] C Data Interface implementation

Adds experimental support for C Data Interface in Arrow Java.
Roundtrip example with dictionaries:
  void roundtrip(FieldVector vector, DictionaryProvider provider) {
    // Consumer allocates empty structures
    try (ArrowSchema consumerArrowSchema = ArrowSchema.allocateNew(allocator);
        ArrowArray consumerArrowArray = ArrowArray.allocateNew(allocator)) {

      // Producer creates structures from existing memory pointers
      try (ArrowSchema arrowSchema = ArrowSchema.wrap(consumerArrowSchema.memoryAddress());
          ArrowArray arrowArray = ArrowArray.wrap(consumerArrowArray.memoryAddress())) {
        // Producer exports vector into the FFI structures
        FFI.exportVector(allocator, vector, provider, arrowArray, arrowSchema);
      }

      // Consumer imports vector (and dictionaries)
      try (FFIDictionaryProvider dictionaries = new FFIDictionaryProvider();
          FieldVector imported = FFI.importVector(allocator, consumerArrowArray, consumerArrowSchema, dictionaries)) {
          // Do something
      }
    }
  }

Some notes and questions:

Only enabled when arrow-ffi profile is enabled (currently disabled by default). Should it be enabled by default? How best to allow enabling it (+integrate in CI)?
Requires building some JNI code (used just for private data and release callback). This is currently placed in the java/ffi module itself because this code does not require Arrow C++. Is that the right place for it?
The API is marked EXPERIMENTAL and is as close to the C++ API as possible
Conversion between StructVector and RecordBatch is not available in the Java implementation. We added it here by mimicking the VectorLoader/VectorUnloader approach. Is that the right approach? Where should this code reside?
As a design choice all allocations are done with a BufferAllocator. This is required for use cases that need a custom memory allocator (we are working on a Java-Rust demonstration using WebAssembly).
A ZeroVector is exported/imported as a NullVector (there is no C Data interface format for it).
Integration tests will be added in a future PR.
Currently only for 64bit systems. Is arrow targeting 32bit systems too?
ExtensionTypeVector support to be added to this PR soon (missed it)

I skimmed through it and it looks good, thanks a lot for this!
What we did in Rust was to use the c data interface that C++ exposes in Python to make calls from within the process, see here.
I think it would be beneficial to add integration tests against pyarrow. In Rust we found a couple of memory leaks and double frees during development by testing against pyarrow / c++.
I would also setup an environment to run those tests against e.g. valgrind, since in FFI is very easy to trigger UB.

I skimmed through it and it looks good, thanks a lot for this!
What we did in Rust was to use the c data interface that C++ exposes in Python to make calls from within the process, see here.
I think it would be beneficial to add integration tests against pyarrow. In Rust we found a couple of memory leaks and double frees during development by testing against pyarrow / c++.

Thanks Jorge. We have @tomersolomon1 working on integration tests against pyarrow as a follow-up to this PR. The approach that we are trying with integration tests is to use jpype (as suggested by @pitrou) and run the tests against the same datasets used in the IPC integration tests. It's too early to say if that makes sense. I think that eventually the same set of tests should be used for all languages.

I would also setup an environment to run those tests against e.g. valgrind, since in FFI is very easy to trigger UB.

I'm not familiar with using valgrind in Java but I will definitely check. FWIW the tests do fail in case of a memory leak for memory allocated with a buffer allocator (allocator#close() raises an exception if there are allocated bytes left).
Somewhat unrelated but I know that you ran tests with valgrind for arrow2, did you also ran it for arrow-rs? I thought that there is a memory leak in arrow-rs because no one ported your export API fixes yet. Just out of curiosity about my memory leak assumption.

The approach that we are trying with integration tests is to use jpype (as suggested by @pitrou) and run the tests against the same datasets used in the IPC integration tests. It's too early to say if that makes sense.

That sounds reasonable to me. You can start from hand-written data generation in PyArrow (or Java) if that's easier, though.

For the record, here's an example of testing against PyArrow in the Go PR:
https://github.com/apache/arrow/pull/11037/files#diff-7823a4f3ee456fdcc402770f66d886ce9946f4fd8ce465d32921fae9ee92dfe1

Is this PR waiting for review or are updates needed from the author?

@emkornfield We already addressed all of the review comments provided so far, but this PR was waiting for CI integration for unit testing and jar packaging. These were added in the last commit so a review of that part is required.

@github-actions crossbow submit java-jars

Sidenote: other implementations also exercise importing/exporting from/to C++ through Python, example: https://github.com/apache/arrow/blob/master/go/arrow/cdata/test/test_export_to_cgo.py

@kou can you please crossbow submit java-jars again?


counter: fix tests in release mode

This fixes should_panic tests in release mode, as they rely on
debug assertions.

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

Context: https://github.com/coreos/fedora-coreos-tracker/issues/190#issuecomment-498857691
/cc @rfairley

@lucab thanks! The RPM build now works locally, pushed the patch: https://pagure.io/rust-prometheus/c/71c34e5185c9c68879a6a47f693f9d450eb7df0f?branch=master

Thanks!  @overvenus PTAL

Thanks!


merge package template from Kronos-Tools/npm-package-template

package.json

chore(devDependencies): add<EMAIL_ADDRESS>from template
chore(devDependencies): add<EMAIL_ADDRESS>from template
chore(devDependencies): update<EMAIL_ADDRESS>from template
docs(package): remove keyword null

.npmignore

chore(npm)

Codecov Report

Merging #82 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #82   +/-   ##
======================================
  Coverage    92.3%   92.3%
======================================
  Files           1       1
  Lines          26      26
======================================
  Hits           24      24
  Misses          2       2

Continue to review full report at Codecov.

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

Changes Unknown when pulling 28cf8aa72b008a085a1e5caeeff1d5b131f03826 on template-sync-1 into ** on master**.


Update  to fit luos engine

Update Getting started code to fit the new Luos_engine repo.

PR is OK.


pass sidecar docker image to release pipeline

In #1218 we added a new docker image to the build and release, but we forgot to pass the meta_data through to the release pipeline. This resulted in the release pipeline failing - eg:
https://buildkite.com/buildkite/agent-release-edge/builds/294#8d50db3e-781c-4690-9378-f1ddf83988be

The failure this hopes to fix is in the release pipelines, so the only way to test it is to merge and see if it helps.
YOLO.

it worked :raised_hands:


Traffic Shaper Wizard Upstream SIP Server

Not being remembered and actioned.
Bug #4314
The corresponding *.inc files had the field name changed to upstream_sip_server but they had not been changed in the XML files.

Thx Phil merged.


FiraCode character render issue

Environment
Windows build number: Microsoft Windows [Version 10.0.19041.264]
Windows Terminal version (if applicable): Version: 1.0.1401.0

Any other software?

WSL2 + ZSH (oh my zsh) + Starship Prompt
Steps to reproduce

Set Windows Terminal fontFace to Fira Code.
Expected behavior

Render Square character as it is.
Actual behavior

Windows Terminal doesn't render square character as it is BTW I use same Fira Code font in vscode & it renders all characters correctly
Windows Terminal:

VS Code (correct character render):

Can you share the codepoint of that square glyph? I don’t have “lsd” here to test with.

sorry, i don't know the exact codepoint for this square glyph. is there any way to get codepoint from this? so I can provide that :)

It may help if you copy and paste it out of VSCode and terminal into a GitHub comment :)

The code points for the characters that you are looking for can be found in https://github.com/Peltoche/lsd/blob/master/src/icon.rs .  It seems that quite a lot of them are Private Use Area code points.
The error here is in the erroneous expectation that private use code points will be the same from font to font.  The local fix is to make lsd stop (ab)using them and have it use the standardized Unicode characters with --icon-theme unicode.
Sadly, a lot more work could be done on lsd's Unicode mode.  This is issue #10 for lsd and no-one has fleshed out the Unicode icon set beyond basic characters for file and folder.  Please go to the lsd people and suggest a few.

I can concur that this is more of a font issue. A little debugging told me that is a mixed usage of U+F115 and U+E27C, which are both considered illegal Unicode characters.
If I'm using Cascadia Code, the lsd result looks better:

However with Fira Code, this will happen:

It may help if you copy and paste it out of VSCode and terminal into a GitHub comment :)



Well, I've got some bad news. That's U+E60B, which is firmly in the private use area. Fira Code doesn't have a glyph for that codepoint, so what you're seeing is the NOGLYPH character. It looks like a box, sometimes a ?, sometimes a <?>, and certain layout engines will display it as a cute box with the characters E 6 0 B in it.
In all cases, it's the same issue: there's no glyph there. lsd seems to require a special font.
Resolving as external. :smile:

@DHowett @skyline75489 i changed windows terminal font to patched Cascadia code font from nerd fonts. now icons look better.

thanks in advance for the help <3 :)

Why my nerdfont icon is so small?


DOM hotspots addons

Add visible, interactive and cursor options to the DOM hotspots

 All committers have signed the CLA.

Problem solved, the roll property needed to be negated in STW and WTS conversion in Views.

LGTM with fix.


alcom: init at 1.8.1

This is the experimental GUI counterpart of vrc-get (called vrc-get-gui in the repo).
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[x] 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/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

CC @bddvlpr you might be interested in this ^^

nixfmt-check is failing because of deps.nix. This is currently by design and there is no consensus on formatting these: https://github.com/NixOS/nixpkgs/pull/325053

Interesting, thanks for the PR!
Seems to work as expected with a few minor visual bugs but those might very well be some Wayland moments.

Hi! author of ALCOM here!
I found that alcom is incorrectly registered with version names of vrc-get.
vrc-get is incremented independently with ALCOM releases.
Could you fix version name?
if possible, could you update them?
Actually latest ALCOM, v0.1.17, is far new than ALCOM at the time vrc-get 1.8.2 is released.


Fixing complex ArrayList deserialization

Description

Fixing complex ArrayList deserialization
Motivation and Context

Fixing complex ArrayList deserialization

How Has This Been Tested?

Included in the tests
Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[x] Unit Tests (work on Unit Tests, has no impact on code or features)
[ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@Ellerbach please review the changes in the Unit Test.

And thanks for the improvements in the tests :-)


Matrix-free or partial assembly in elasticity operator

Howdy!
I'm looking at MFEM for solving elasticity problems, and I've been getting errors saying that the elasticity integrator does not work with partial or no assembly.
I was wondering if there is a simple way to set this up on my end, or what would go into going around this integrator. (Could I use a combination of something like divergence and diffusion integrators to do the same thing? I don't know if these things can be combined.)
Thank you,
Justin

I am also interested in this.  Would love to hear from the community.
Thanks
Joe

You can also look into the Hooke mini app. It's a matrix-free version of solid mechanics with automatic differentiation and user defined materials using PA-like kernels.


feat(hubble): use fixed domain for hubble api

Goals:

api.jina.ai is unstable sometimes, remove this layer to get better quality. We need to maintain the old domain even we move to new domain anyway, so no worries about writing domain down directly.

Related to https://github.com/jina-ai/hubble/issues/434

black -S accepts single quote

@mapleeit I couldn't provide a suggestion that spans deleted lines, don't accept it directly xd

Done! Thanks for the advice.


set more restricted permissions for store

Summary
Using 0777 and 0666 permissions aren't best practice. Main problem is everybody can edit folders or files, what can create unexpected problems for us and it is security risk.
I recommend change it to 0750 for folder and 0640 for file.
0750 for folder can be maybe problematic for libvirt daemon.
Pls fix return of error in set function in the issue: https://github.com/ironcore-dev/libvirt-provider/blob/main/pkg/host/store.go#L238
Motivation
Better security.

If the same permissions are used in multiple places, wouldn't it make sense to centralize them in one location and then reference them elsewhere?


Footer JS-based responsiveness on pages without the sidebar is unnecessary

Current Situation

The footer layout needs to account for the sidebar width (if any) to make its layout responsive. This is achieved by using the JS-based responsiveness. However, this is not necessary on pages that do not have a sidebar, and lead to a layout shifts on the homepage.
Suggested Improvement

Audit the footer layout responsiveness, and only add it on the search layout with the sidebar.
Benefit

Improved performance and less layout shifting.
Additional context

@obulat instead of JS-based responsiveness on pages with a sidebar and regular media queries in pages without a sidebar, i think using container queries consistently in both scenarios would be the better approach.

I agree, @dhruvkb. This looks like a good guide on implementing container queries while also supporting older browsers: https://web.dev/blog/how-to-use-container-queries-now
We'll need to create a solution that works with Tailwind

Tailwind supports container queries with an official plugin. I hadn't considered that older browsers will need workarounds, thanks for the guide!


fix: instrumentation-aws-sdk typescript error

fix the following error:
`opentelemetry-instrumentation-aws-sdk/dist/src/types.d.ts:3:13 - error TS1192: Module '".../node_modules/aws-sdk/index"' has no default export.
3 import type AWS from 'aws-sdk';
~~~
Found 1 error.
`

Hi @taliasegev , Thank you for working on a fix. Actually, this instrumentation has moved to the official contrib repo with a new npm package name @opentelemetry/instrumentation-aws-sdk.
It was left in the repo for while but will be removed soon. I recommend to switch to this new package, and check if the issue is happening there as well.

thanks! the new repo solved the problem


Support other JVM language files (Scala, Kotlin, Clojure and JRuby).

The README.md should be updated to reflect these changes.


Investigate need to prevent double-submission of the case if someone uses the "back" button

we could just add a prevent_going_back(). If there's a check on the proxy server already, no need to add that complexity though.

There isn't a check on the proxy server (not sure the best way to handle that, maybe check for the session id in the docassemble JSON?). There a prevent_going_back() in (https://github.com/SuffolkLITLab/docassemble-EFSPIntegration/blob/9f80c6a4ecd6706fb1813e0d0d82e81f30fb2ab3/docassemble/EFSPIntegration/data/questions/efiling_integration.yml#L297), but commented out because it saves a lot of development time on the proxy server to just go back and resubmit if there's some bug I'm trying to track down. We can definitely get rid of that at some point.
We could also have a "resubmit" button if the submission failed for any reason? But that gets tricky because there could be something that goes wrong after the Tyler submission (i.e. our user transaction stuff going wrong), that would still allow a duplicate submission.

OK pre-submission let's just turn this back on then. i think it's fair to have the certification test require the tester to start over again from the beginning, even if it's not the final UX we want.

Turned back on with https://github.com/SuffolkLITLab/docassemble-EFSPIntegration/commit/b3b6106471648b48591bb6e0951ebceb83b7a72f


Not able to get the bot working in raspberry Pi

I am running the raspberry pi as headless and I am controlling it via SSH, I installed all the modules correctly. but when I tried to run it the following error showed, The error is saying that I should have a Display in order to send a message. But I have set up my Pi as a server for bots.
  File "bot.py", line 1, in <module>
    import pywhatkit as kit
  File "/usr/local/lib/python3.7/dist-packages/pywhatkit/__init__.py", line 6, in <module>
    from pywhatkit.main import print_sleep_time, check_window, sendwhatmsg, sendwhatmsg_to_group, info, playonyt, search, close_tab, sendwhatmsg_instantly
  File "/usr/local/lib/python3.7/dist-packages/pywhatkit/main.py", line 3, in <module>
    import pyautogui as pg
  File "/usr/local/lib/python3.7/dist-packages/pyautogui/__init__.py", line 241, in <module>
    import mouseinfo
  File "/usr/local/lib/python3.7/dist-packages/mouseinfo/__init__.py", line 223, in <module>
    _display = Display(os.environ['DISPLAY'])
  File "/usr/lib/python3.7/os.py", line 678, in __getitem__
    raise KeyError(key) from None
KeyError: 'DISPLAY'

PyWhatKit requires Chrome or any other browser with UI, i.e. you can't use it on servers as they use browsers in headless mode.

Oh okay, Thank you 👍🏼, you may close the issue.


g4f on OpenHands

Will it be integrated g4f?

Can you elaborate what that actually is?

https://github.com/xtekky/gpt4free


Initial MS Marco Document Ranking - add instructions how to reproduce Leaderboard submission

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

FYI @bratseth

The flow is sub-optimal but this is what I could manage today so need to revisit the readme in Q1 when we submit more runs.

Great!


Remove weak booleans.

They are totally useless, and I suppose we do not need this to demonstrate fcom anymore. @cangiuli

Sure, that's fine.


Feedback for: Tools for PWA Developers [en]

https://github.com/google/WebFundamentals/blob/master/src/content/en/ilt/pwa/tools-for-pwa-developers.md
in "Check notification permissions" section, underscores are being added and causing formatting issues.
Example:

Should look like:

GitBook reference
Source doc

Also occurring in the "Check IndexedDB" section

Fixed in source


Tests cases that throw exceptions don't print the counterexample

When SwiftCheck catches an error thrown by a test case, it prints the error, but it doesn't print the counterexample. This means I have no idea what input caused the problem.

Oh dear.  Give me just a minute to close out the other pull request and I'll have one where we can amend this together.

I found the code responsible, I'll toss you a PR.


Fix repository link, add epoch to fix version scheme.

Pushing this through as it's just adding an epoch and fixing a link (and Jenkins' output looks sane).

I don't get how that epoch line fixes it, where can I read more about epoch?
Also, why did you put in Kerbal%20Foundries%20Wheels%20and%20Repulsors%20ALPHA?
That's going to change (hopefully)?

x_netkan_epoch forces an epoch string on the front of the version. With the beginning of a new epoch, new versions should now index properly.
I changed the repository link because https://kerbalstuff.com/mod/58/ generates a 404. KerbalStuff's servers will not give a page if you have a link ending with the mod's ID and a forward slash at the end of the URL. Alternatively I could have used https://kerbalstuff.com/mod/58 or even https://kerbalstuff.com/mod/58/ItDoesntMatterWhatTextAppearsHereAsLongAsItsNotTheModNumberFollowedByAForwardSlash

Inspiring stuff. Thanks.


Pixlet create & check commands no longer exist?

The publishing docs reference pixlet create and pixlet check but it doesn't look like either of those commands exist on the pixlet binary.

Never mind, I was on an old version, I updated the docs for the install.


Handle offline connection for Snowflake during diff DAT-18652

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

Is this only impacting snowflake? Based on the code change it seems like all dbms would bee impacted.

Good catch @abrackx .  I should have added this check in the SnowflakeJdbcExecutor override of the execute method.


🔨Fixes noteToFreq function

A short quick fix correcting the noteToQuick function.

closing as this is now fixed via #605 and again, apologies to both PR's for the delay and duplicated work! Hopefully good learnings along the way at least :)


lib/modules: assert that specialArgs has a valid lib

End-users have ran into issues before when attempting to re-use a lib from elsewhere in nixvim's configuration.
If a lib without the nixvim extension is used, the new assertion will explain that this isn't supported.
Nixvim requires a lib that includes some custom extensions, however the `lib` specialArg does not have a `nixvim` attr.
Remove `lib` from nixvim's specialArgs or ensure you apply nixvim's extensions to your lib.

In the future we can also provide better ways for end-users to overlay their own lib with nixvim's extensions, but this is not yet implemented. Draft #2328

@mergifyio queue


recipes-smt: Add recipe for Yices2 SMT solver

Yices 2 is an SMT solver that decides the satisfiability of formulas
containing uninterpreted function symbols with equality, real and
integer arithmetic, bitvectors, scalar types, and tuples. Yices 2
supports both linear and nonlinear arithmetic. For more details please
see:
https://yices.csl.sri.com/
Yices can be used in conjunction with yosys-smtbmc to formally verify a
design. For more details please see:
https://symbiyosys.readthedocs.io/en/latest/quickstart.html
Signed-off-by: Ovidiu Panait<EMAIL_ADDRESS>

You accidentally committed a .swp file in you most recent commit. So I manually merged this pull request and removed that from the commit. Thanks for the contribution!


chore: introduce calldata requestParser.test.ts

Motivation and Resolution
Cover calldata requestParser with tests
RPC version (if applicable)
...
Usage related changes

Change 1.
...

Development related changes

Change 1.
...

Checklist:

[ ] Performed a self-review of the code
[ ] Rebased to the last commit of the target branch (or merged it into my branch)
[ ] Linked the issues which this PR resolves
[ ] Documented the changes in code (API docs will be generated automatically)
[ ] Updated the tests
[ ] All tests are passing

Can you please add an @example on
export function parseCalldataField
🙏

done ✅


[BUG] Both onerror and onclose are triggered when socket connection fails to be initialized

Is there an existing issue for this?

[X] I have searched the existing issues

Description

This shouldn't be the case. Only the onerror should be triggered, meaning only the "Can't establish connection to the server!" should be displayed.
PNLS version
0.2.0
Python version
No response
Operating system
No response
Additional environment/system information
No response
Actual Behavior
Both messages, "Can't establish connection to the server!" and "Connection to the server has been terminated!" are displayed.
Expected Behavior
Only "Can't establish connection to the server!" message should be shown.
Steps To Reproduce
No response
Anything else?
No response

This should be an easy fix now after #37.


Bad advice for configuring StyleCop

Somehow there are projects with this line:
Exists('....\packages\StyleCop.MSBuild.<IP_ADDRESS>\build\StyleCop.MSBuild.Targets')
Not sure how it got there or if StyleCop is adding it or some instructions on the internet tell people to add it but it prevents projects from building.  This is highly abusive of that feature.  Some superfluous plugin should not be allowed to prevent a build.

The StyleCop.MSBuild.Targets file is included in the project file by installing the StyleCop.MSBuild NuGet package. It is the correct way to have a NuGet package customize the build process, as described in Microsoft's documentation. It is required in order to run StyleCop analysis as part of the build, and is neither bad advice nor abusive.
If you don't want StyleCop to run as part of the build, don't install the StyleCop.MSBuild package.

Is there some way to make it not cause errors on Release build?  This is
how your package is being used:
https://github.com/zabirauf/icsharp/wiki/Installation
[image: Inline image 1]
Maybe it isn't being updated with the new version number in the csproj
files?
I'm going to submit a PR that doesn't include it in the project.  NuGet is
not very smart with this stuff, I've found.
On Thu, Jun 8, 2017 at 6:51 PM, Chris Dahlberg<EMAIL_ADDRESS>wrote:

The StyleCop.MSBuild.Targets file is included in the project file by
installing the StyleCop.MSBuild NuGet package. It is the correct way to
have a NuGet package customize the build process, as described in Microsoft's
documentation
https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package#including-msbuild-props-and-targets-in-a-package.
It is required in order to run StyleCop analysis as part of the build, and
is neither bad advice nor abusive.
If you don't want StyleCop to run as part of the build, don't install the
StyleCop.MSBuild package.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/StyleCop/StyleCop/issues/130#issuecomment-307273420,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX5XbhJ5qiNqIAE-CprVvmALEeLXO-bsks5sCKUUgaJpZM4N0v7_
.

Of course it doesn't remove this line when I uninstall StyleCop.MsBuild it:
    <Error
Condition="!Exists('..\..\packages\StyleCop.MSBuild.<IP_ADDRESS>\build\StyleCop.MSBuild.Targets')"
Text="$([System.String]::Format('$(ErrorText)',
'..\..\packages\StyleCop.MSBuild.<IP_ADDRESS>\build\StyleCop.MSBuild.Targets'))"
/>

On Fri, Jun 9, 2017 at 10:45 AM, Brian Cullinan<EMAIL_ADDRESS>wrote:

Is there some way to make it not cause errors on Release build?  This is
how your package is being used:
https://github.com/zabirauf/icsharp/wiki/Installation
[image: Inline image 1]
Maybe it isn't being updated with the new version number in the csproj
files?
I'm going to submit a PR that doesn't include it in the project.  NuGet is
not very smart with this stuff, I've found.
On Thu, Jun 8, 2017 at 6:51 PM, Chris Dahlberg<EMAIL_ADDRESS>wrote:

The StyleCop.MSBuild.Targets file is included in the project file by
installing the StyleCop.MSBuild NuGet package. It is the correct way to
have a NuGet package customize the build process, as described in Microsoft's
documentation
https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package#including-msbuild-props-and-targets-in-a-package.
It is required in order to run StyleCop analysis as part of the build, and
is neither bad advice nor abusive.
If you don't want StyleCop to run as part of the build, don't install the
StyleCop.MSBuild package.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/StyleCop/StyleCop/issues/130#issuecomment-307273420,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX5XbhJ5qiNqIAE-CprVvmALEeLXO-bsks5sCKUUgaJpZM4N0v7_
.

I checked out the iCSharp repo, and saw the same error when trying to follow those instructions. There are multiple problems with how NuGet packages are being used in that repo, but I was able to quickly get .\iCSharp.sln building by first restoring packages for .\Engine\ScriptCs.sln.
On Windows you can do that by right-clicking on on the ScriptCs solution in Solution Explorer and choosing the option to restore NuGet packages, or on the command line you can run .nuget\NuGet.exe restore Engine\ScriptCs.sln from the root of the iCSharp repo.
On Linux/Mac it looks like you can restore packages and build by just running build_brew.sh in the root of the repo.

Lmftfy, there are many problems with nuget. Thanks for the try, I submitted
a PR. Why wouldn't reinstalling the .50 version update the version in the
csproj files?
On Jun 10, 2017 6:18 AM, "Chris Dahlberg"<EMAIL_ADDRESS>wrote:

I checked out the iCSharp repo, and saw the same error when trying to
follow those instructions. There are multiple problems with how NuGet
packages are being used in that repo, but I was able to quickly get
.\iCSharp.sln building by first restoring packages for
.\Engine\ScriptCs.sln.
On Windows you can do that by right-clicking on on the ScriptCs solution
in Solution Explorer and choosing the option to restore NuGet packages, or
on the command line you can run .nuget\NuGet.exe restore
Engine\ScriptCs.sln from the root of the iCSharp repo.
On Linux/Mac it looks like you can restore packages and build by just
running build_brew.sh in the root of the repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/StyleCop/StyleCop/issues/130#issuecomment-307564583,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX5Xbq-4GrC7jPZu-ng10oU45ZKN7Ksjks5sCpe1gaJpZM4N0v7_
.


[BUG] Lightning Flash integration doesn't work with current Flash version

tl;dr our Flash integration needs to be updated to support the latest Flash version
Our Lightning Flash integration was originally written for these versions of Flash/Pytorch Lightning:
pip install lightning-flash==0.4.0
pip install pytorch-lightning==1.3.6

With the above versions of those packages installed, I am still able to run the detection and embeddings examples from our integration docs. However, I am no longer able to load the pre-trained image checkpoint:
rm -rf ~/.cache/torch/hub/checkpoints

from flash.image import ImageClassifier

model = ImageClassifier.load_from_checkpoint(
    "https://flash-weights.s3.amazonaws.com/image_classification_model.pt"
)

AttributeError: Can't get attribute 'image_loader' on <module 'flash.image.data' from '/Users/Brian/dev/env/fifty3/lib/python3.6/site-packages/flash/image/data.py'>

If I upgrade to the latest version of Lightning Flash (0.6.0 as of this writing) then our examples no longer work.
Example code I tried running:
from flash.image import ImageClassifier, ObjectDetector

import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset("quickstart", max_samples=5)

model = ObjectDetector.load_from_checkpoint(
    "https://flash-weights.s3.amazonaws.com/object_detection_model.pt"
)
dataset.apply_model(model, label_field="flash_detector")

model = ImageClassifier.load_from_checkpoint(
    "https://flash-weights.s3.amazonaws.com/image_classification_model.pt"
)
dataset.apply_model(model, label_field="flash_classifier")

Would love to see a fix for this.
I've tried updating the imports but there seem to be some other issues. With a little bit of direction I'd be happy to make a PR :)

I also quite interested in a new working version of integrationof the "semantic segmentation" example / use case. In the meanwhile up to the time the fix is available maybe adding a comment that newer flash version are not supported yet, would be nice. Thank you!


[spdm_requester_lib] fixed potential buffer overflow

In function spdm_negotiate_connection_version there is a potential buffer overflow (line 115) where the indexing variable (res_index) is incremented before the array access.
This bug was found by ESBMC as a part of our work of applying formal verification to libspdm.

CI fails. Please add your signed-off.


Re-origanize launch file for probabilisitic_occupancy_grid_map packages

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
Try to reorganize launch file for occuapncy grid map generation.
Purpose
Problem Statements

There are duplicated launch files in tier4_perception_launch and probabilisitic_occupancy_grid_map packages.

This is confusing for users which file to edit

poor readability because of launch.py style

It's better to rewrite launch file in xml file
or create organizer launch to access each launch.py files

Possible approaches

Create origanizer launch.xml in tier4_perception_launch instead of current launch.py

From the launch.xml file, call launch.py in probabilistic_occupancy_grid_map packages.
Switchable between potincloud/laserscan based methods

Definition of done
Reproduce the same behavior

@YoshiRi
@Zeysthingz is willing to help with this task. @Zeysthingz Could you describe your approach (or create a draft PR) and align with @YoshiRi about this task?

@mitsudome-r  @Zeysthingz
OK. Where should we discuss? I'll just describe my load map here.

I did not examine the issue in detail yet but I think we can discuss on discord if it's fine.

My goal
As described in https://github.com/autowarefoundation/autoware.universe/issues/2906, I think we need to create occupancy grid map in each sensor frame to correctly reflect the FOV of the sensor.
So, my goal image is like following figures:

Current
Final goal

Sub Goals
To achieve the goal, I

<1> Fix grid map generation

a. need to generate same grid map for fusion but different scan frame
b. manage each sensor FOV correctly
c. launch refactoring

<2> Add fusion node

a. asyncronous grid map fusion with [[Binary Bayes/ Linear Opinion Pool/ Dempster-Shafer]]

Related PRs

1.a: Separate grid map origin and scan origin :

https://github.com/autowarefoundation/autoware.universe/pull/2939

1.b: Filter the obstacle pointcloud by raw pointcloud to correctly reflect FOV:

https://github.com/autowarefoundation/autoware.universe/pull/3054

1.c: Refactor launch.xml

https://github.com/autowarefoundation/autoware.universe/pull/3058

2.a: under going...

I did not examine the issue in detail yet but I think we can discuss on discord if it's fine.

@Zeysthingz Fine, but I am not familiar with discord (just used chat space), could you guide me?

Yes sure I can ,we usually use discord for company stuffs. zeys#0531 is me you can add me.

My goal
As described in #2906, I think we need to create occupancy grid map in each sensor frame to correctly reflect the FOV of the sensor.
So, my goal image is like following figures:
Current 	Final goal

Sub Goals
To achieve the goal, I think there should be some sub goals to be achieved.
* <1> Fix grid map generation

  * a. need to generate same grid map for fusion but different scan frame
  * b. manage each sensor FOV correctly
  * c. launch refactoring

* <2> Add fusion node

  * a. asyncronous grid map fusion with [[Binary Bayes/ Linear Opinion Pool/ Dempster-Shafer]]

Related PRs
* 1.a: Separate grid map origin and scan origin :

  * [feat(probablistic_occupancy_grid_map): add alternative to gridmap origin frame #2939](https://github.com/autowarefoundation/autoware.universe/pull/2939)

* 1.b: Filter the obstacle pointcloud by raw pointcloud to correctly reflect FOV:

  * [feat(probabilistic_occupancy_grid_map): add pointcloud filter in gridmap generation #3054](https://github.com/autowarefoundation/autoware.universe/pull/3054)

* 1.c: Refactor launch.xml

Looks like all PRs are merged. Can this issue be closed or is there other work outstanding?

I think this issue is good to be closed.


Migrate testing to ava?

//cc @gokulkrishh What say?

@hemanth Sounds good to me

@gokulkrishh with ava
   1 passed
   3 exceptions

  ✖ test/temp/test/js/app.js exited with a non-zero exit code: 1

  ✖ test/temp/test/server.js exited with a non-zero exit code: 1

  ✖ test/temp/test/sw.js exited with a non-zero exit code: 1

Is that a minor exception or a major one + error response is not so clear to find where the test case is breaking. Other wise looks grt @hemanth . I will try to contribute more 👍

Just take a pull and try.

👍 Checked. Test cases passed 💥

But still in travis 1 test case is getting failed
Ref: https://travis-ci.org/hemanth/generator-pwa/jobs/130334828
I will work on this

Cannot find module 'underscore.string' but why...hmm


Speedup CI

Add a big crate to measure the performance of CI.
Add the following major packages to measure how long it takes to compile, clippy, etc.
boa_engine = "0.16.0"
headless_chrome = "1.0.1"
html5ever = "0.26.0"
serde = "1.0.152"
tokio = "1.24.1"

Strategy 1.
This strategy is based on the following article https://zenn.dev/shotaro_tsuji/scraps/1eae69f2e0d7e6
targets are kept and Rust's incremental builds and caches are used to speed up builds after the second.
The cache validation is based on the mtime of the source code, so checkout with fetch-depth: 0 and restore mtime with chetan/git-restore-mtime-action.
Possible disadvantages: The targets may become too large. It takes time to restore the cache.
1st
succeeded Jan 10, 2023 in 7m 56s
Checkout ... 1s
Install Rust toolchain ... 14s
clippy ... 2m18s
Coverage ... 4m29s
Post Run actions/cache@v3 ... 43s

Codecov Report
Base: 33.33% // Head: 33.33% // No change to project coverage :thumbsup:

Coverage data is based on head (f4d5bd1) compared to base (53717b8).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage   33.33%   33.33%
=======================================
  Files           1        1
  Lines           3        3
=======================================
  Hits            1        1
  Misses          2        2

Flag
Coverage Δ

unittests
33.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Activation fails when using env prefix

Thanks for creating this handy plugin!
After setting a Conda environment prefix as per the docs here and running hatch env create, I am seeing an error that looks like
EnvironmentLocationNotFound: Not a conda environment: /path/to/cwd/project_default_3.8

Digging into the implementation, it looks like this is because conda activate isn't using the prefix: https://github.com/OldGrumpyViking/hatch-conda/blob/5cdeccc47be52a482c185ff6731a09f05f559592/hatch_conda/plugin.py#L246

Yes this should probably be wrapped in a prefix check:
if self.config_prefix is not None:
    cmdl = f"{self.config_command} activate {self.config_prefix}"
else:
    cmdl = f"{self.config_command} activate {self.conda_env_name}"

You are welcome to make the PR.


moment-business-days not supporting nuxt3. Kindly assist us.

I configured like below. It works in "npm run dev" but error "npm run build".
defineNuxtConfig({
vite: {
optimizeDeps:{
esbuildOptions:{
plugins:[
esbuildCommonjs(['moment-business-days'])
]
}
},
build: {
modulePreload: { polyfill: true,  }
}
}
})

I'm sorry, I have no experience with Nuxt so I wouldn't know where to start to assist you. I hope you can find a solution and share it here.

No solution still

I think you need to use updateLocale method.

The latest 1.3.0 is not published. When will publish this ?

Kindly release new version boss

Hi sir, did you release this GitHub version in the npm?. It would be very helpful.


CLOUD-714 - Fix monitoring test for PMM dev-latest image

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1197/commits/51164ee7a6cae6e247cbfb230b277dac0befb3b7
image: perconalab/percona-xtradb-cluster-operator:PR-1197-51164ee7

Test name
Status

big-data
passed

storage
passed

upgrade-haproxy
passed

scaling
passed

scheduled-backup
failed

recreate
passed

haproxy
failed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

init-deploy
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

demand-backup
passed

limits
failed

smart-update
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

pitr
failed

upgrade-consistency
failed

monitoring-2-0
failed

demand-backup-encrypted-with-tls
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 35 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1197/commits/51164ee7a6cae6e247cbfb230b277dac0befb3b7
image: perconalab/percona-xtradb-cluster-operator:PR-1197-51164ee7

Test name
Status

upgrade-haproxy
passed

cross-site
passed

scheduled-backup
failed

big-data
passed

haproxy
failed

scaling
passed

storage
passed

recreate
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

init-deploy
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

demand-backup
passed

smart-update
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

pitr
failed

limits
failed

upgrade-consistency
failed

demand-backup-encrypted-with-tls
passed

monitoring-2-0
failed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1197/commits/018487466f063773d8ea236f3848e828d99b09b8
image: perconalab/percona-xtradb-cluster-operator:PR-1197-01848746

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1197/commits/018487466f063773d8ea236f3848e828d99b09b8
image: perconalab/percona-xtradb-cluster-operator:PR-1197-01848746

Test name
Status

haproxy
passed

recreate
passed

upgrade-haproxy
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

storage
passed

big-data
passed

pitr
failed

self-healing
passed

cross-site
passed

scaling
passed

scheduled-backup
passed

self-healing-chaos
passed

scaling-proxysql
passed

self-healing-advanced
passed

security-context
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

init-deploy
passed

limits
passed

monitoring-2-0
failed

demand-backup-encrypted-with-tls
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1197/commits/018487466f063773d8ea236f3848e828d99b09b8
image: perconalab/percona-xtradb-cluster-operator:PR-1197-01848746

Test name
Status

upgrade-haproxy
passed

big-data
passed

recreate
passed

scheduled-backup
passed

scaling
passed

storage
passed

haproxy
passed

restore-to-encrypted-cluster
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

cross-site
passed

demand-backup
passed

self-healing-chaos
passed

security-context
passed

limits
passed

pitr
passed

self-healing-advanced
passed

monitoring-2-0
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

demand-backup-encrypted-with-tls
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1197/commits/018487466f063773d8ea236f3848e828d99b09b8
image: perconalab/percona-xtradb-cluster-operator:PR-1197-01848746


Update to Verilator 4.102

Require Verilator 4.102 (over 4.040) to fix a bug we encounter in OTBN
tracing code.
Besides the typical set of bug fixes and improvements we don't expect
any visible change to existing testbenches.
Note that this version of Verilator now requires a C++11-capable
compiler on the host; this is not a new requirement for OpenTitan users,
as we had such a host compiler requirement for a while now and building,
e.g. spiflash, requires even newer C++ features.
Fixes #4170

Intent to change system requirements sent to the mailing lists, please comment in this PR if there are reasons why we should not move forward with this change.
Otherwise I'm aiming to merge it by Wednesday Nov 18.

Small potential change in plans: Verilator 4.104 would solve one additional issue, let's go with that instead if it doesn't cause too much inconvenience for people. (Better get it done now instead of doing another bump in a month.)


Update New-SPAuthenticationProvider.md

Cleaned up examples.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/New-SPAuthenticationProvider.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


Feature/add multiselect filter

Added feature #405
This new feature is to add a multiple selection option to vue-good table. Seen in the image below:

The changes made in this PR are:

Added library for multiselect options called: vue-select
Using new component added an option to the filter options to set the multiselect dropdown.

This option does a fuzy search on any of the selected options.
This feature will work with the specified types as well
This also works when reseting the table

Updated docs to include documentation for new filter options
Updated dev app to use new feature

This is sweeet! @cassmbautista my only concern is adding another library for something that is not core to the table and might not be used by everyone.
I'm trying to trim down the existing ones to reduce the size (lodash etc). Is it possible to add this as a plugin for vue-good-table? that way you can maintain it and people can optionally add it if they want to use it?

@xaksis Yea I was concerned about that too since I noticed you have very little dependencies. However, I have no idea how to add it as a plugin for vue-good-table. Any ideas? Do you have any examples of plugins to components?

Good point. I was actually thinking of making a column-manager plugin for VGT myself to figure out how that'd work. Mind if I hold off on this for a bit? Then we can use that as a template if it works.

Yea, you can hold off on this for a while. I am also interested in the functionality of the column-manager plugin.

@xaksis
I was wanting a column manager option as well. My design for it would have been a button or icon that opens a pop-out menu with all columns listed in a scrollable area. Each column name would have a grabber icon on the left to drag it up/down to reorder them and a checkmark to the right of the column name to show/hide that column.
My original mockup:

The default sort allows the user to pick which column to sort by by default.

haha @TheJaredWilcurt that's pretty much exactly what I have implemented in the project that I was planning to refactor. Glad to see it validated!

Guys (@cassmbautista, @xaksis) while you are discussing the column plugin, it can be a good idea to give an autocomplete function in the filter (let say you want to filter by a particular user, and there are 1000s of the user and autocomplete server fetching is a good option) for those using remote mode

@bhargavjoshi
This PR uses vue-select which has that capability. I'm not sure if this PR supports that, but it could be an additional follow up PR to add that functionality if it doesn't.

https://vue-select.org/guide/ajax.html

@cassmbautista, @xaksis
I was thinking about giving users the ability to use their own filter component.
Right now we have these options.
filterOptions: {
  enabled: true,
  filterValue: '',
  placeholder: "Show All",
  filterDropdownItems: ['']
}

We can add a property for a component like this
filterOptions: {
  enabled: true,
  filterValue: '',
  component: '<MyCustomComponent :attr1="attr1" @change="functionToSetFilterValue" />'
}

We have to think about how we can pass data to the component and also get data from the component.
My use case Is I want to give two text inputs with labels to put min amount and max amount. (basically a range filter).
Let's discuss more on this.

Nice work! Would love to see this get integrated!

@xaksis Have you been able to make an example plugin for vue-good-table, so that I can convert this PR to a plugin?

Would love to see this get integrated too! :)

@cassmbautista really sorry but I have been very busy with another project. When I get a breather I'll get on it! I will keep you updated.

It's looking good. Can't wait to see it integrated or as a plugin :)

Merging this is means a 15% increase in the payload size (since it will now include the vue-select dependency). If this can be set up as an optional dependency or to be tree-shakable that would be ideal. However I'm also fine with that being a follow up issue.


Bring time input behavior in line with time_select when inputs are empty

Before this change, it wasn't possible to create an input of type 'time'
that didn't default to the current date. This made it impossible to
differentiate between a form submission wherein the user hadn't picked a
date, and one in which they'd picked midnight UTC.

Makes sense for me. @justinfrench?

Does this change default behaviour from "if there's no time on the model, make it 'now'" to "if there's no time on the model, show nothing"? I'm not necessarily against that change, but we should be conscious of it.

The way I would put the current behavior is "if no time is entered in a formtastic time input, save 2000-01-01 00:00 UTC to the database". This change results in that scenario leaving the field nil, which is desirable if you ever want a time field to be optional.

"save … to the database" is too implementation specific, so let's stick to what the user sees on the form — if there's no time present on the attribute, what did the user see, what will the see going forward?

You're asking about an edit form, right? Going forward, the user sees blank values for the time dropdowns when the field is nil, same as they would for a new object

I think we should not set "default values".
Let think about optional date time field.
If user want to keep this field blank, they should change the value because the form render the current time by default.
I guess if developer want to set the current time as default, he should do something like that on controller:
@account = Account.new
@account.create_at = Time.current

That's the default behavior of rails, I guess.

@sobrinho, totally agree, but anything that changes the default behaviour of Formtastic should be at least well documented in the release notes, so I'm trying to figure out what the user-facing change is.

Sounds like we're basically on the same page, then.
The release notes could read something like "Changed time input so that blank values aren't persisted as midnight"
Would it also make sense to point out that this change makes the formtastic behavior consistent with ActionView's time_select with include_blank? Eg.
time_select foo, bar, :include_blank => true


Error beeps and echoing of the last command in ZOC

How to reproduce:

git clone https://github.com/reciprocity/ggrc-core
librarian-chef install; vagrant up; vagrant ssh  # precise64 box
ssh into the machine using ZOC
sudo apt-get install zsh
passwd  # set it to something
chsh -s $(which zsh) vagrant
curl -L http://install.ohmyz.sh | sh
re-login

Now, type some commands and notice how they're echoes before execute. Additionally, the terminal beeps in about half the cases. I've been using ZOC for 5+ years and never had this problem.

Can you check again after upgrading oh-my-zsh? It might be a bug in how oh-my-zsh sets the encoding to utf-8...

Yep, still beeps and odd characters:

Try again after restarting the terminal. If it still fails, please post the output of locale and infocmp.

 I've been using it for years; it's great.

Maybe it's the autotitle functionality, try running DISABLE_AUTO_TITLE=true

That works! No more beeps or odd characters.

Ok, try running print -Pn "\e]2;a:q\a" and `print -Pn "\e]1;a:q\a" to see which one beeps.

I can reproduce with ZOC 7.05.0 on OS X. Looks like it supports the "\e]2;$name\a" window title sequence but not the print -Pn "\e]1;$name\a" icon title; that one causes a beep and normal text to be echoed to the screen.
Looks like we could add a workaround to this by detecting ZOC using the ZOCINSTANCE environment variable it sets. Use that to turn off the icon setting attempt.
➜  ~  set | grep -i -a zoc
ZOCINSTANCE=1

Hello!
A user made us aware of the problem (and these posts) and we were just looking into it.
apjanke is right, we currently (as of 7.05.0 and earlier) ignore the 1; sequence and redirect it to the screen.  This will be fixed in the next ZOC release (7.05.1 or 7.06.0) with about the next 4 weeks.
Btw, in Options>Program Settings>Tabs, there is an option that will allow/prevent the change of tab title.  It currently needs to be enabled to allow the 2; sequence to change the tab title as well.
Thanks
Markus Goemmel
(Co-Developer of ZOC)

Excellent. Thanks for being responsive.
While it would probably be nice to have independent tab control, I think it's probably more important for compatibility that ZOC detect and swallow all "OSC" sequences, not just the ones it implements functionality for. Basically, an xterm will treat any sequence of the form \e]Ps;Pt\a as a control sequence meant for the terminal, and not to be displayed on the screen. (Where \e is ESC, Ps is any number, Pt is any string of printable characters, and \a is BEL.)
For example, in iTerm2, OS X xterm, and Terminal.app, you can do this with any number, and you won't get visible junk on the screen.
➜  ~  printf "\e]0;whatever\a"
➜  ~  printf "\e]1;whatever\a"
➜  ~  printf "\e]2;whatever\a"
➜  ~  printf "\e]9;whatever\a"
➜  ~  printf "\e]12345;whatever\a"
➜  ~  printf "\e]999999999;whatever\a"

(That \a is a literal ASCII BEL character, which is why the terminal beeps when this stuff gets echoed to the screen.)
I sent your colleague Markus Schmidt a detailed email about this.
OMZ folks, if there's a fix for this coming out soon, and the DISABLE_AUTO_TITLE=false workaround works, let's not put in any special cases for ZOC in the OMZ code.

Do we have any updates to this? Was ZOC updated to handle this?

Marc,
I'm not sure what the status of this is, but I remember some changes
about "zsh".
Our version 7.05.0 has a version entry which I think was related to it:
xterm icon title request now changes tab title (requires option from
program settings > tabs)
If you still have specific problems after this version, feel free to
email me directly.
Regards
Markus Schmidt
Telnet, SSH, Modem ... our product ZOC will do it all (and more).
EmTec, Innovative Software
http://www.emtec.com/
<EMAIL_ADDRESS>Phone: +49<PHONE_NUMBER>
Mobile: +49<PHONE_NUMBER>
Fax: + 49<PHONE_NUMBER>
On 16.01.2016 11:26, Marc Cornellà wrote:

Do we have any updates to this? Was ZOC updated to handle this?
—
Reply to this email directly or view it on GitHub
https://github.com/robbyrussell/oh-my-zsh/issues/3331#issuecomment-172181232.

Ok thanks Markus, I'm closing this then. If a problem like this happens again we'll add a special case for ZOC. Cheers!


Aci integ

This PR brings in the changes for ACI integration.
Summary of changes:

Added a hook into AppCreate for posting app-profiles based on composition
Added support for per-EPG vlan allocation
Added contivctl support for enabling/disabling the above
godep update to bring in changes to objmodel (note this resulted in a bunch of unused components being deleted from Godep/_workspace, and those show up in the diff)

Testing:

Verified sanity after rebase
Verified aci and non-aci functionality using the contivctl to configure.

@jojimt: will the removal of various javascript files make the front page rendering that is otherwise available?

I ran it by Sukhesh yesterday and he gave the go ahead. @shaleman can you please comment?

perhaps he is working on regenerating them in objmodel... will let him comment

These particular files are not needed for Web UI rendering(They are only required for building web UI javascript bundle).
They were accidentally checked in because i had manually copied objmodel into godep directory at some point. Its good they are getting cleaned up now.

Are you able to see the diffs? Looks like my real diffs are drowned out by the Godeps.

I have created a diff file without the extraneous stuff. It's available at contiv141:/home/ladmin/pull_173.diff

Can someone help merge this?


[AutoPR network/resource-manager] Fix the typo for actionsRequired in PrivateLinkServiceConnectionState.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7672

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/6189


Option for excluding individual from its group when the individual is compared with the group

There are situations when one wants to calculate f-statistics between an individual and its own population, e.g.:
F4(PopulationA, TestPopulation; Individual1FromPopulationA, Outgroup)
In such situations it might be useful (or might make more sense) to use PopulationA but with Individual1 excluded.
I'm not sure whether this should be a default behavior but would certainly be a useful option.
Specifying an ad hoc "PopulationA-minus-Individual1FromPopulationA" for each individual is of course an option but when one is estimating a lot of f-statistics and, particularly, when there is many individuals that one would like such estimates for, it ends up being fairly cumbersome.
If this would be a fairly easy option to introduce, it would be awesome to have it.

Right. Thanks for adding this issue. I agree about the usefulness, but so far lack imagination for how the exact API could look so that users won't be surprised. Will think about it.

Don't you think that it actually could be a default behavior that whenever an individual is compared to its own population it gets excluded from the population? Then it wouldn't be confusing by there being more options to set up.
I mean every time you have fstats estimation, xerxes would first check whether the entities which are individuals are a part of any other entity that are populations or packages and if they are, turn this population/package into (population - individual) or (package - individual).
That should also work in cases when there are more than one individual in the fstats.


[WIP] FEATURE-RELEASE: Set mimetype and encoding on renditions (using generated rendition file)

Description

Adds content type (aka mime type) recognition for a rendition.

Adds encoding recognition for a rendition.

Both encoding and content type are metadata. Metadata are now filled out during the rendition_success call, and sent in the event. This should cover shellscript and javascript workers.

Add a unit-tests script to the package.json, which displays log statements in the console (useful for debugging) and generates a code coverage version in HTML (helps to find locations where code coverage can be improved).

Technical details:
To add mimetype and encoding recognition, I ended up calling the file command from the underlying operating system. This relies on libmagic.
Libmagic has bindings for nodejs, but adding any of those libraries would make action packaging fail:

for mmmagic: this library tries to recompile its native dependency during installation (npm-i). There are ways to compile for different target than we install on, so before packaging we could recompile for a Linux target... This library will work on Mac and Linux, but make our packaging fail with a path resolution error. Actually, webpack can't/won't support the packaging of native libraries/binaries (*.node, *.o for instance). Since we would not be able to package, and I didn't want every single worker to have to either know where libmagic/a magic file is found on a system or use a custom Docker image we would maintain, I switched to another solution.
for magic: this library uses the native implementation of libmagic, written in C and transpiled to web assembly. I had similar issues for packaging as for the above library with this, and also I could not get it to run on my machine properly (web assembly kept complaining it can't initialize).
other libraries relying on libmagic are either old or unmaintained.
file-type library is full javascript, but is unfortunately incomplete and cannot recognize everything (allthough for the time being it would cover our needs).

So I ended up using execa to call the file command from the underlying operating system. I chose execa because it is an improved child_process (e.g. cleans up if parent process dies), that makes it easy to read results from the command. Also, it is promisified and runs cross-platform (if Windows had a file installed...).
To finish, I also did some sha1 handling changes and moved metata generation into the rendition class.
Fixes # NUI-607
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes (and some more to increase coverage a bit).
[x] All new and existing tests passed.

Based on prototype from https://github.com/adobe/asset-compute-sdk/pull/12.

@alexkli
Also the rendition.exists() usage in worker.js (at least 2). is not part of mimetype feature (it's more a refactoring), and could/should be another PR. It was not clear to me I had to productize all NUI-600 prototype.

@alexkli
Regarding content detection feature:
I was pondering, when coding it, why we need a mechanism to set mimetype/encoding type from a worker, and settled with myself to only code automated detection for now (for me it dud fit the bill to have a mimetype-setting mechanism, as it is done in the sdk at rendition-success event sending time. Also, I could share implementation for shell and js workers).
I can see why we may one day need it for less common types. But currently I would have a tendency to rely on mime identification rather than setting:

if sdk does the identification in one place, a developer doesn't need to remember to do it (which would be the case for setting a mime type manually, right? I mean it would have to be done in the worker, not the sdk)
using detection based on our container should always yield the same mime type (there are different mimetype fitting the same file type, eg image/tif and image/tiff for tif files. There are even more synonyms for psd or ms office files).

I will add the mechanism for setting a mimetype from a worker as this is what you wish for. But I will be keeping automated detection as fallback, or even only doing automated detection in the sdk, be it only for the reasons I listed above.

@tmathern

Also the rendition.exists() usage in worker.js (at least 2). (tmn edit: changed - but I could find only one. The other one may be part of the inline() feature)

There are 2:

https://github.com/adobe/asset-compute-sdk/pull/12/files#diff-644d8ede25bb88427ccf4229d03bba1bR179
https://github.com/adobe/asset-compute-sdk/pull/12/files#diff-644d8ede25bb88427ccf4229d03bba1bR239

I added a mechanism so workers can set the mimetype and encoding of the rendition they're creating. I set mimetype and encoding together (1 function call), as they are related. Also, I set them together because I updated them together when using the file command too.
Usage:

for shellscript workers: the worker should write mimetype+encoding in a file in the /out directory of the worker (mimeinfo-${renditionId}.txt). The exact path is made available in an ENV variable, mimefile.The content should be formatted like the file command would (aka mimetype; encoding). The file has the rendition id in its name to ensure it is unique and can be recognized as a given rendition's mime information. The file is created by the sdk the following way during the run preparation (prepare.js):

function prepareMimeInfoFile(directory, renditionId) {
    const mimeDir = path.resolve(directory, "mimeinfo");
    fs.mkdirSync(mimeDir, {recursive: true});
    return path.resolve(mimeDir, `mimeinfo-${renditionId}.txt`);
}

for javascript workers: javascript workers can call the method setMimeInformation(mime, encoding) on the rendition object.

Caching:

setMimeInformation is used to update the mime+encoding information for the rendition. If setMimeInformation gets a mimetype and encoding entered as parameters, those have precedence. If not, setMimeInformation tries to read the mime-info file. If this file is not found, it falls back on the file command (if available). If the file command is not here (which is the case currently in our images), it tries to find the mimetype using the file-type library (https://www.npmjs.com/package/file-type).
I have been debating with myself whether or not to cache mime and encoding information (to avoid the possible costly file fallback). In the end, I decided not to cache yet. This will allow information to be re-read at each .encoding() or .mimeType() call, which means that a mimetype can be updated (may be useful to update a mimetype as more information becomes available). Wdyt?

Known issues:

some mimetype can have synonyms. For instance, mimetypes image/tif and image/tiff are synonyms. Since we cannot really control what the final mimetype name will be, we should not do tests based on that. The fix would be to normalize names (using a map, for instance). Do we need this? I don't think so for now (but maybe later).

Requests for feedback:

Wdyt about the usage to set mimetypes?
For me, mimetype and encoding are deeply linked, hence handled together. But would you prefer them to be split: one method for setting encoding, one for mimetype?
Content-type is generated based on the content of mimetype and encoding properties. Are there objections to that?

Left to do:

If usage is OK, I'll add more unit tests.

Note that 27.1.0 was an erroneous release. It was unpublished.


Tracing package should not change on major version bumps

Wanted to drop this in so it's tracked for 4.0 - the class Tracer is a singleton; you register observers to get traces, and every tracer reports to the list of observers. Every time we change the package name we add a new singleton.
This means that an internal app which wants full trace coverage (through e.g. libraries like tritium-tracing) must register remoting1, remoting2 and remoting3 observers. In practice, they only register a single observer, so would miss out on events. E.g. tritium-tracing is remoting1, so is functionally useless now.
I would propose simply not changing the package name in future (or else a final move to remoting-api (it's API!) and linking the remoting3 class pointing to that) - this is a static singleton and must remain so.

Or just move the tracing java lib into a separate project.

prefer moving it to a separate repo


bug: Hero section is hiding behind fixed navbar. not able to see text properly

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

OS [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

fixed in latest commit


Versions of iptables 1.6.1 or older do not have --version as a valid save flag

AKA "@sridhargaddam Was Right" :D
https://github.com/istio/istio/pull/49703#discussion_r1519612928
Basically - ubuntu bionic ships iptables-legacy 1.6.1 - which is from 2017, and that particular version DOES have iptables-save, but that version does not understand the --version flag. The version in jammy and newer (and all reasonably current versions) do support this flag.
We didn't detect this before because the old logic did not do version detection in all cases, so the fact that bionic didn't actually have a version flag slipped thru unnnoticed.
Basic fix is to distinguish between "binary exists" and "binary supports --version flag", and if it exists but does not support that, assume it's a very-old legacy binary and use it anyway.

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
afd0922c5cdede8ea7f6ccc255ff0bdf34e22c08
link
true
/test release-notes

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

/test release-notes

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
afd0922c5cdede8ea7f6ccc255ff0bdf34e22c08
link
true
/test release-notes

gencheck_istio
afd0922c5cdede8ea7f6ccc255ff0bdf34e22c08
link
true
/test gencheck

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

...unclear why gencheck would fail vis a vis master? Oh well.