Choices not opening

I'm having trouble opening any choices when inserting the project file code into the app.c533aa25.js, and this issue occurs in versions 1.5.0 to 1.6.0. The only version that works without this problem is 1.4.3 below.

That's strange. If you don't mind, could you send me the project.json file from before it was inserted into app.c533aa25.js so I can check it?

https://pixeldrain.com/u/TMYVMSk7
here
Worm Ltouroumov and Lord of the ring

Upon checking, I found that it works without any issues. Please check these links.
https://hikawasisters.neocities.org/ICCPlusTest303/Viewer/Ltouroumov/
https://hikawasisters.neocities.org/ICCPlusTest303/Viewer/LordOfTheRing/

I see the problem, it only works when hosted on a local or a website, it doesn't work when you only open the index file and run the CYOA on your browser, making the CYOA fully offline.

Yes, the Viewer is essentially designed with hosting in mind. If you want it to work completely offline, I will consider including this feature in the next update.

No problem, and thank you for your time.
The version 1.4.3 still works, so it's not a big issue.

Oh, but I've already implemented that. It should work fine with version 1.6.3.


Noria adoption

Kudos to everyone working in the Noria sphere!
A couple questions:

Who is using Noria? Any large companies using it in production?
Is it ready and or suggested for production use cases?

https://readyset.io/ is the commercial adaptation of Noria, so that's the place to look :)


Help Request/Question: Keep sort when searching

Is there a way to keep the current sorting when filtering?
I have been digging through the documentation but have not found a way to keep the currently sorted column after a user searches.
Now I know I could apply a sort after OnDataLoaded if the getSorting() comes back with nothing. But this would end up with an additional call back to the server and would not be the exact column the user selected to sort.
Regards,

search method resets sorting, loadData doesn't. search method is the one used in the control field. To use loadData method instead, you can override _createSearchButton method of the control field, so that it calls loadData instead https://github.com/tabalinas/jsgrid/blob/master/src/fields/jsgrid.field.control.js#L170


Protections pop-up alignment

Pictures speak louder than words.
INSTEAD OF

EDGE-LIKE BEHAVIOR

Maybe somewhat a terrible mockup, but I created this Paint :P

You mean it should be before the search bar and not after it ?

You mean it should be before the search bar and not after it ?

Yes, kind of. I guess 'within' would be a better word.


doc/faq: provide the path to the client.crt for snap users too

@tomponline I found some other occurrences and also added a missing tilde in the faq.md. Sorry for the too early PR.


Unable to place blocks in Nether

Block placement is denied when placing blocks in the nether in 1.1beta

Resolved in commit f4440cf


codeql-cli-2.17.6 broken kotlin-java build in multi-module project

I have a multi-module kotlin project, where modules require different java versions (8, 11, ...)
I noticed that my codeql actions started failing and since I haven't made any changes to build configuration between last successful build and currently failed one, I've started looking at the version of the action.
While I can't spot anything in the logs, the last version that worked for me was  codeql-cli-2.17.3, and after setting that up explicitly the build works again. With the current  codeql-cli-2.17.6 , the build breaks with the following error:
[2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild] FAILURE: Build failed with an exception.
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild] * What went wrong:
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild] A problem occurred configuring project ':cli-bot'.
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild] > Could not resolve all files for configuration ':cli-bot:classpath'.
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild]    > Could not resolve org.graalvm.buildtools:native-gradle-plugin:0.10.1.
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild]      Required by:
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild]          project :cli-bot > org.graalvm.buildtools.native:org.graalvm.buildtools.native.gradle.plugin:0.10.1
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild]       > No matching variant of org.graalvm.buildtools:native-gradle-plugin:0.10.1 was found. The consumer was configured to find a library for use during runtime, compatible with Java 8, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '8.4' but:
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild]           - Variant 'apiElements' capability org.graalvm.buildtools:native-gradle-plugin:0.10.1 declares a library, packaged as a jar, and its dependencies declared externally:
  [2024-06-29 13:35:18] [build-stdout] [2024-06-29 13:35:18] [autobuild]               - Incompatible because this component declares a component for use during compile-time, compatible with Java 11 and the consumer needed a component for use during runtime, compatible with Java 8

This is a successful run after downgrading the codeql tooling to 2.17.3 and using<EMAIL_ADDRESS>version explicitly - https://github.com/serpro69/kotlin-faker/actions/runs/9724606568
If I use init@v3 and do not set tool version, which currently defaults to 2.17.6, the build fails to compile due to java version that is being picked up: https://github.com/serpro69/kotlin-faker/actions/runs/9724530099/job/26840837224
The problem is, with the current version, it's setting java8 by default, for some reason - https://github.com/serpro69/kotlin-faker/actions/runs/9724530099/job/26840837224#step:5:81 , and I do not see a way how to override that.
That wasn't the case previously, so gradle would just pick whichever version is needed, based on toolchains and gradle setup.
Is this intended behavior? Is there any way I can upgrade to latest version while preserving the previous behavior?

This is because we're now recognising the configuration in the root build.gradle.kts file to compile against Java 8. The best way to override this is to use a setup-java step to install the JDK version that your project requires.

Tricky. How about installing both, but then twiddling ~/.m2/toolchains.xml to only list Java 11? I think Gradle will still find Java 8 by exploring the platform default JDK directory.

OK, what I tried now is just to setup only one java version via setup-java, instead of multiple, and that worked for my case. Codeql recognized the installed java version and didn't default to java 8, at the same time, the gradle plugin which requires me to have java 11+ also didn't complain. Don't know why I didn't try this earlier... But thanks for your suggestions @smowton . Closing this.


Even or Odd

Title of programme
Write a Python programme to check a number even or odd.
Additional information
Input  : 3
Output : Odd Number

Input  : 2
Output : Even Number

Code of Conduct

[X] I have read and agree to the Codinasion project's Code of Conduct

I can work on this issue as well.


Deadlock issues

I have just implemented Christian Wade's "Automated Partition Mangement" solution in my company.
https://azure.microsoft.com...
But I got an error message when I run the process full of all tables.
I have this error message
Exception message: Failed to save modifications to the server. Error returned: 'The operation was canceled because a deadlock condition was detected with another transaction. This usually occurs when two transactions need to lock the same objects, but do so in a different order. Please retry your operation.
Anyone know how to fix this problem?

Hi, I'd start by making sure you are using the latest client libraries from here: https://docs.microsoft.com/en-us/analysis-services/client-libraries?view=asallproducts-allversions#amo-and-adomd
Deadlocks often occur when multiple operations such as refreshes and queries are occurring at the same time. The accompanying whitepaper with the Automated Partition Management has a section on it with the timeout settings you can use to control this

Hello @christianwade
Thank you for your help.
It's really strange because there is no query on this tabular model.
It's a new model that is being tested and that no one is using.
This model is deployed on Azure Analysis Service and I use the solution with Azure functions to process it.
As you advised me, I configured the table [TableConfiguration].
The values for the CommitTimeOut are 100,000 to avoid the lock.
And when I process the tables manually I don't get any errors.
Do you have any idea to help me resolve this error?

Hello
Another thing that I weird is that when I run the solution locally, on my personal workstation and not on Azure, I don't get any errors.
It drives me crazy. Three days that I have been working on this error.

Are you using the latest client libraries NuGet in the solution and rebuilt/redeployed?

@christianwade Any update on this ?
facing similar issue .
@LaguideHalid Did you issue resolved ?

Locking and blocking is something you may have to deal with if you have metadata, refresh and/or queries running concurrently. This is not specific to this tool. There are various settings and optimizations you can consider. Some are discussed briefly on page 26 of this document, and others.


Can't use previous row @-1 in formula body

Attempting to calculate the running sum of a list of transactions requires a reference to the sum in the previous row. Apparently, any of @-1 the formula body leads to a syntax error, both formulas in the examble fail, but various combinations without @-1 do not.
|    In |  Out | Saldo |
| -----:| ----:| -----:|
|  0.00 | 0.00 |       |
| 30.00 |      |       |
|  4.00 |      |       |
|       | 0.50 |       |
<!-- TBLFM: $>=(@-1) -->
<!-- TBLFM: $>=(@-1 + $-2 - $-1);%.2f -->

There is one requirement that I don't think is described in the docs: when doing a calculation with multiple operators, each sub calculation must be enclosed in parentheses.
Does this do what you want:
`

In
Out
Saldo

0.00
0.00
0.00

30.00

30.00

4.00

34.00

0.50
33.50

`

That definitely could be more clear in the documentation, and you are exactly right. All arithmetic operations must be in parenthesis. See the examples [in the docs|https://github.com/tgrosinger/md-advanced-tables/blob/main/docs/formulas.md#algebraic-operations]
Thanks for answering this @khorton.

Interesting point, but as described in the original question, any formula including the @-1 (previous row) reference fails.


Consistent macos failure on grpc_credentials_test

D0708 11:08:52.744596000<PHONE_NUMBER>13376 test_config.c:52] test slowdown: machine=1.000000 build=1.000000 total=1.000000
E0708 11:08:52.745542000<PHONE_NUMBER>13376 credentials.c:509] Call to http server ended with error 401 [{"access_token":"ya29.AHES6ZRN3-HlhAPya30GnW_bHSb_", "expires_in":3599,  "token_type":"Bearer"}].
E0708 11:08:52.745551000<PHONE_NUMBER>13376 credentials.c:521] Could not parse JSON from (null)
E0708 11:08:52.745557000<PHONE_NUMBER>13376 credentials.c:521] Could not parse JSON from access_token
E0708 11:08:52.745562000<PHONE_NUMBER>13376 credentials.c:540] Missing or invalid access_token in JSON.
E0708 11:08:52.745568000<PHONE_NUMBER>13376 credentials.c:521] Could not parse JSON from access_token
E0708 11:08:52.745573000<PHONE_NUMBER>13376 credentials.c:550] Missing or invalid expires_in in JSON.
E0708 11:08:52.745616000<PHONE_NUMBER>13376 sync_posix.c:46] assertion failed: pthread_mutex_destroy(mu) == 0
FAILED: bins/opt/grpc_credentials_test [ret=-6, pid=53843]

Note: the only line of the above log that is bad is the assertion failing on pthread_mutex_destroy.  A normal, correctly functioning, version of the test should print:
D0708 11:18:40.926029653   14760 test_config.c:52]           test slowdown: machine=1.000000 build=1.000000 total=1.000000
E0708 11:18:40.926381929   14760 credentials.c:509]          Call to http server ended with error 401 [{"access_token":"ya29.AHES6ZRN3-HlhAPya30GnW_bHSb_", "expires_in":3599,  "token_type":"Bearer"}].
E0708 11:18:40.926396108   14760 credentials.c:521]          Could not parse JSON from (null)
E0708 11:18:40.926405516   14760 credentials.c:521]          Could not parse JSON from access_token
E0708 11:18:40.926412408   14760 credentials.c:540]          Missing or invalid access_token in JSON.
E0708 11:18:40.926419960   14760 credentials.c:521]          Could not parse JSON from access_token
E0708 11:18:40.926426732   14760 credentials.c:550]          Missing or invalid expires_in in JSON.
E0708 11:18:40.926462586   14760 credentials.c:509]          Call to http server ended with error 403 [Not Authorized.].
E0708 11:18:40.926504324   14760 credentials.c:509]          Call to http server ended with error 403 [Not Authorized.].
E0708 11:18:40.939003149   14760 credentials.c:509]          Call to http server ended with error 403 [Not Authorized.].
E0708 11:18:40.945065106   14760 credentials.c:709]          Could not create signed jwt.
E0708 11:18:40.945088773   14760 credentials.c:509]          Call to http server ended with error 400 [].

Here is the backtrace at the failure point:

thread #1: tid = 0x110f0b, 0x00007fff874b5286 libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT

frame #0: 0x00007fff874b5286 libsystem_kernel.dylib__pthread_kill + 10 frame #1: 0x00007fff8ffbf42f libsystem_pthread.dylibpthread_kill + 90
frame #2: 0x00007fff895b9b53 libsystem_c.dylibabort + 129 frame #3: 0x000000010004a89b grpc_credentials_testgpr_mu_destroy(mu=0x0000000100600070) + 75 at sync_posix.c:46
frame #4: 0x000000010002ebd5 grpc_credentials_testgrpc_pollset_set_destroy(pollset_set=0x0000000100600070) + 21 at pollset_set_posix.c:53 frame #5: 0x000000010001f885 grpc_credentials_testgrpc_httpcli_context_destroy(context=0x0000000100600070) + 21 at httpcli.c:76
frame #6: 0x0000000100015f31 grpc_credentials_testoauth2_token_fetcher_destroy(creds=0x0000000100600000) + 65 at credentials.c:473 frame #7: 0x000000010001328c grpc_credentials_testgrpc_credentials_unref(creds=0x0000000100600000) + 76 at credentials.c:91
frame #8: 0x00000001000023a1 grpc_credentials_testtest_compute_engine_creds_success + 273 at credentials_test.c:519 frame #9: 0x0000000100000f07 grpc_credentials_testmain(argc=1, argv=0x00007fff5fbffb80) + 119 at credentials_test.c:868
frame #10: 0x00007fff8f6ee5c9 libdyld.dylib`start + 1

Likely fixed by #2252

Ok, good to know. I was starting to investigate further but will not do so until after #2252 gets merged.

Just confirming that this problem is fixed by #2252. I have put a comment to that effect in that PR.

Fixed by #2252. Confirmed.


[Documentation]: Update README for installation and usage

Contact details
No response
Tell us what you want to see in documentation
Missing documentation. Add basic documentation on how to install and use this software.

Created doc for installation using mkdocs


Update InferenceAPI docs (TGI update mostly)

Follow-up after https://github.com/huggingface/huggingface.js/pull/915 and https://github.com/huggingface/huggingface.js/pull/924.
Auto-generated update. Done by running:
cd scripts/api-inference
pnpm run generate
# and then commit changes

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


increment jackson version

Codecov Report

Merging #62 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #62      +/-   ##
============================================
- Coverage     54.96%   54.92%   -0.04%
+ Complexity      559      557       -2
============================================
  Files           106      106
  Lines          2540     2540
  Branches        139      139
============================================
- Hits           1396     1395       -1
  Misses         1063     1063
- Partials         81       82       +1

Impacted Files
Coverage Δ
Complexity Δ

...a/com/axibase/tsd/client/PlainStreamingSender.java
44.11% <0%> (-0.74%)
15% <0%> (-1%)

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 f7c9e7e...78ed350. Read the comment docs.


provide cassandra java driver 3.x plugin

Please answer these questions before submitting pull request

Why submit this pull request?
[ ] Bug fix
[x] New feature provided
[ ] Improve performance
_

New feature or improvement

http://cassandra.apache.org/

@dmsolr Any update?
@zhaoyuguang Please run this codes test case again. I want to see any good luck this time.

@wu-sheng, I think you want to ping @stone-wlg , right?
I had a look deeply, I think it is okay.

@dmsolr I was really pinging you, to make sure you don't have a further review to do. Why are you still awake at this moment?

@stone-wlg Do you update this PR to support async execution? Do you have the accurate execution time now?

haha, a glace before sleep. @wu-sheng , have a good dream.

@stone-wlg Do you update this PR to support async execution? Do we have the accurate execution time now?

yes, we have.

yes, we have.

But I could not find span#prepareForAsync. Is there unnecessary now?

yes, we have.

But I could not find span#prepareForAsync. Is there unnecessary now?

No, the key is the getUninterruptibly method. it likes lazy mode or cursor of database.

No, the key is the getUninterruptibly method. it likes lazy mode or cursor of database.

OK. That is another story. I am thinking about this too. But not related to this PR, could be done in a different way.

No, the key is the getUninterruptibly method. it likes lazy mode or cursor of database.

OK. That is another story. I am thinking about this too. But not related to this PR, could be done in a different way.

Currently, i intercept getUninterruptibly method by LOCAL METHOD in skywalking. So we can get accurate execution time whatever sync or async way.

Let's wait for test case and 6.4.0 shipped. We are only fixing bugs before 6.4.0 release.

Currently, i intercept getUninterruptibly method by LOCAL METHOD in skywalking. So we can get accurate execution time whatever sync or async way.

Make sense for now. I am thinking about a special tag for this kind of OP(cursor reading)

Let's wait for test case and 6.4.0 shipped. We are only fixing bugs before 6.4.0 release.

Let's wait for test case and 6.4.0 shipped. We are only fixing bugs before 6.4.0 release.

ok

Currently, i intercept getUninterruptibly method by LOCAL METHOD in skywalking. So we can get accurate execution time whatever sync or async way.

Make sense for now. I am thinking about a special tag for this kind of OP(cursor reading)

Got it.

@wu-sheng Currently, i am working monitor whatever log, metric and trace. i am thinking that is it necessary to add MQ(kafka) between skywalking agent and OAP? this is maybe another topic, i just want to know in a short word, thanks

Currently, i am working monitor whatever log, metric and trace. i am thinking that is it necessary to add MQ(kafka) between skywalking agent and OAP? this is maybe another topic, i just want to know in a short word, thanks

Most APM didn't do this, because it doesn't necessarily. If you want to discuss detail, feel free to open an issue, we could discuss there and move it to FAQ in case others want to know too.

Currently, i am working monitor whatever log, metric and trace. i am thinking that is it necessary to add MQ(kafka) between skywalking agent and OAP? this is maybe another topic, i just want to know in a short word, thanks

Most APM didn't do this, because it doesn't necessarily. If you want to discuss detail, feel free to open an issue, we could discuss there and move it to FAQ in case others want to know too.

ok, thanks

Testcase and Support-list describe different, is the testcase source code is not latest？

Testcase and Support-list describe different, is the testcase source code is not latest？

i had comment other versions, because it seems that could not test all scenarios in this env.
i commented out the other version, let's try whether is ok or not now. thanks

I had triggered the auto tests, let's wait for the result

assert failed.
IllegalDataFileException actualData.yaml

Does that have any illegal character?

assert failed.
IllegalDataFileException actualData.yaml

Does that have any illegal character?

No, if yes passed tests should be 0, but it is 1.

actually, i could passed all test cases on my pc.
[INFO] ---------------------------Here is the test report context -------------------------------------
Test Report - 2019-09-09 13:30

tests  : 4 passed. 0 failed
branch name : features/cassandra-java-driver-3.x-plugin
commit id : 7e6124170f6e5d58f12d03c9a752f77c92480d5d
cases branch: master
cases commit id: 565d60c983a2c527f17997bd5cf8aa6eda30c0be

Cases List

Case description
Status
Cases

Cassandra
4 passed. 0 failed
click me

Cassandra

Version
Passed
Failed

3.7.1
:heavy_check_mark:

3.7.2
:heavy_check_mark:

3.7.0
:heavy_check_mark:

3.6.0
:heavy_check_mark:

[INFO] -----------------------------------end the report-----------------------------------------------

Which happened before. It is so strange.

Can we download the actualData.xml? I am interesting in that.  @wu-sheng  @zhaoyuguang

Which happened before. It is so strange.

https://github.com/apache/skywalking/pull/3330#issuecomment-526506594
you can reference that we have talked about it before.

@dmsolr Could you run tests locally?

Yes, I run it now.

Yes. But I miss another problem which actualData.xml is empty. And I am trying find out.

Any update about empty expected file?

Sorry, @wu-sheng , Which is my mistake. That is why docker cannot launch because my ECS does not have enough memory to run four cases at once.

@stone-wlg I will keep only one test case, maybe our server has the same memory issue too.
@dmsolr Are you OK with this PR now?

it's ok!

/run ci

@kezhenxu94 @zhaoyuguang Please recheck.

/run ci

/run ci

server

OK, do i need to comment the other version in testcases project ?

I guess, otherwise, it will break as last time we tried(right?)

Just for reminder, it seems that there are pairs of async and sync methods in Cassandra, so please consider both of them when you intercept methods (consider whether they have async counterparts or not).
To name a few:

com.datastax.driver.core.Cluster#connect() vs com.datastax.driver.core.Cluster#connectAsync()
com.datastax.driver.core.SessionManager#execute vs com.datastax.driver.core.SessionManager#executeAsync

P.S. seems that the sync version simply calls the async version and wait for the result, so it should be able to just intercept the async version, maybe I'm wrong? Just a hint :)

exactly. sync version call async version and wait for results.
So you mean that only intercept async version is enough, right?
there are 2 questions, as below

if i intercept both sync and async as EXIT SPAN what is going on in skywalking?
if i only intercept async version, there is a little bit confuse on UI. when user call sync version, but tracing on UI will display async version, is there a standard way to solve it?
thanks.

if i intercept both sync and async as EXIT SPAN what is going on in skywalking?

Depend on what kind of codes you are written, basically, override happens. If sync calls async then, span set as sync name. Otherwise, async. Does async interceptor need #asyncFinish?

if i only intercept async version, there is a little bit confuse on UI. when user call sync version, but tracing on UI will display async version, is there a standard way to solve it?

If you only did this, you could just don't separate the sync and async in UI, then should be fine always. You could choose to do it separately or only async.

if i intercept both sync and async as EXIT SPAN what is going on in skywalking?

Depend on what kind of codes you are written, basically, override happens. If sync calls async then, span set as sync name. Otherwise, async. Does async interceptor need #asyncFinish?
Ok, override is what i want, and test result is LGTM.

async interceptor do not need #asyncFinish

if i only intercept async version, there is a little bit confuse on UI. when user call sync version, but tracing on UI will display async version, is there a standard way to solve it?

If you only did this, you could just don't separate the sync and async in UI, then should be fine always. You could choose to do it separately or only async.

@stone-wlg Your comment format is not clear. Could you reformat it?

@stone-wlg Your comment format is not clear. Could you reformat it?

OK

You need to update this PR and test cases.

You need to update this PR and test cases.

Ok, Done
currently only support 3.7.2 version

I think the plugins supporting more versions, right? Just in test case, we plan to merge one version.
@zhaoyuguang run tests again.
@kezhenxu94 recheck please.

versions

yes, i have test 4 version, all of them is passed on my pc.


chore(deps): update common-dev-assets digest to 9fe7626

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
0b25aa7 -> 9fe7626

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 3.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


OVS switches in shared namespaces

OVS's ovsdb gets linearly slower as you add more switches to it.
A workaround is to run multiple ovsdb instances. This is exactly what we do:

run multiple ovsdb instances
run them in namespaces
share the ovsdb namespaces among multiple OVS switches (OVSSwitchNS)
share a single bash process among multiple (OVSSwitchNS) objects

Running OVS in a namespace is somewhat complicated. For now we automatically attach
a NAT element so that they can connect to the root namespace as well as the LAN and beyond.
In the future we might want to revamp Mininet's --innamespace option to allow an explicit
control network, possibly with NAT.
Note that --nat can interfere with the control network NAT unless you specify --nat flush=0. In the future we may wish to make this the default.
Running multiple ovsdb instances, we can create 1024 (or more!) OVS switches relatively quickly, even on a laptop.
Note that sharing bash processes changes the semantics of certain methods since they now talk to a single bash rather than multiple shells. The advantage is that we don't create hundreds of extra processes that we don't need. This behavior can be switched off if desired.

What should I do if I want different ovs bridges to be in different namespaces?
What are the commands?


Stop on first failed test case; don't grade right after unlocking

Resolves #96 and #98. The command line options remain the same:
python3 ok -q question_name -u
python3 ok -q question_name

However, if the -u flag is specified, GradingProtocol does not get run. In addition, GradingProtocol stops at the very "first" failed test case.

LGTM. There's some merge conflicts that need to be resolved.


Fix the prevent default flag in child modules

What does this PR do?

This PR provides a fix for issue 1217.

Description of task to be completed?

The issue was that the child module configuration was not configured to override the prevent_destroy flag in the parent terragrunt.hcl file for the destroy commands to destroy resources .

It is important to not that the find_in_parent_folders() helper in the child module automatically searches up the directory tree to find the parent terragrunt.hcl file and inherit the remote_state configuration from it.

So for the terragrunt detroy command to actually destroy resources of the child module with prevent_destroy flag set to false, the prevent_destroy = true flag in the parent terragrunt.hcl file has to be overriden.

Thanks for the PR! Would you be up for adding a regression test that checks this behavior?
E.g., Create:
* `test/fixture-prevent-destroy/terragrunt.hcl` with `prevent_destroy = true`

* `test/fixture-prevent-destroy/child/terragrunt.hcl` with `prevent_destroy = true` and `include { path = find_in_parent_folders() }`

* `test/fixture-prevent-destroy/child/main.tf` with a `null_resource`

Then, in test/integration_test.go, you create a new test method that runs applyand thendestroyintest/fixture-prevent-destroy/child/` and makes sure it gets destroyed correctly.

Sure, let me add the test

Thanks for the PR! Would you be up for adding a regression test that checks this behavior?
E.g., Create:
* `test/fixture-prevent-destroy/terragrunt.hcl` with `prevent_destroy = true`

* `test/fixture-prevent-destroy/child/terragrunt.hcl` with `prevent_destroy = true` and `include { path = find_in_parent_folders() }`

* `test/fixture-prevent-destroy/child/main.tf` with a `null_resource`

Then, in test/integration_test.go, you create a new test method that runs applyand thendestroyintest/fixture-prevent-destroy/child/` and makes sure it gets destroyed correctly.

@brikis98, with reference to your repro of the bug,
I think * test/fixture-prevent-destroy/child/terragrunt.hcl should be created with prevent_destroy = false other than prevent_destroy = true like you had suggested.

@brikis98, with reference to the repro of the bug,
I think test/fixture-prevent-destroy/child/terragrunt.hcl should be created with prevent_destroy = false other than prevent_destroy = true like you had suggested.

Yes, sorry, copy/paste error in my comment! Just updated my comment to clear that up.

Looks like there was a compile error:
# github.com/gruntwork-io/terragrunt/config [github.com/gruntwork-io/terragrunt/config.test]
config/config_as_cty_test.go:61:3: cannot use true (type bool) as type *bool in field value
config/config_partial_test.go:32:34: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.False
config/config_partial_test.go:79:33: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.True
config/config_partial_test.go:95:34: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.False
config/config_partial_test.go:122:33: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.True
config/config_partial_test.go:142:34: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.False
config/config_test.go:571:21: cannot use cfg.PreventDestroy (type *bool) as type bool in argument to assert.False
?   	github.com/gruntwork-io/terragrunt	[no test files]
?   	github.com/gruntwork-io/terragrunt/aws_helper	[no test files]

Looks like there was a compile error:
# github.com/gruntwork-io/terragrunt/config [github.com/gruntwork-io/terragrunt/config.test]
config/config_as_cty_test.go:61:3: cannot use true (type bool) as type *bool in field value
config/config_partial_test.go:32:34: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.False
config/config_partial_test.go:79:33: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.True
config/config_partial_test.go:95:34: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.False
config/config_partial_test.go:122:33: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.True
config/config_partial_test.go:142:34: cannot use terragruntConfig.PreventDestroy (type *bool) as type bool in argument to assert.False
config/config_test.go:571:21: cannot use cfg.PreventDestroy (type *bool) as type bool in argument to assert.False
?   	github.com/gruntwork-io/terragrunt	[no test files]
?   	github.com/gruntwork-io/terragrunt/aws_helper	[no test files]

Let me check it out

Kicking off tests again!

Tests passed! Merging now, thanks!

https://github.com/gruntwork-io/terragrunt/releases/tag/v0.23.31


update git tag search

Look for the git tag before doing the fetch to increase the chances that we'll get the right thing.

This change is

 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.Jeff McAffer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@jeffmcaffer For some reason the CLA bot does not recognize your commit. Have you maybe used a author / committer email address that's not associated to your GitHub account?

too many different code bases. spaces, tabs, 2, 4, semi-colon, no, ...

I know. I'll try to add more automated checks for these nits.

The Appveyor branch status check does not seem to be happy though. Similarly on my other PR

Yeah, we had some issues with the AppVeyor service recently. I'll watch it for problems; we can override its feedback in any case.

I'll try to add more automated checks for these nits.

Turns out ktlint matches our style very well, it seems, so I've added it (in addition to keeping detekt).


FR: Add xcframeworks in zip file on tagged assets list for version

Feature proposal

Add in assets, xcframeworks in zip files

For example in tag v7.6.0 add FirebaseCore.xcframework.zip, FirebaseMessagging.xcframework.zip ...

Hi @jesusmateos1234, thanks for the request!
We do have the Firebase.zip download which contains all the XCFrameworks and their associated resources - does this not meet your needs? I don't suspect we'll ever put each XCFramework there individually because it'd be impossible to tell which frameworks you need without reading the README embedded in the zip file.

Thanks for your support @ryanwilson. We need to use some xcframeworks (not all) with manual - in house solution- integration. This not mean that Firebase.zip is a good solution for someone who has a bit knowledge or nothing to integrate xcframeworks in his project.
We only need a few of them, we don't required download 300mb of frameworks that we don't use. We need something like Appboy that specify zip files for their xcframeworks. It's a performance question
Including frameworks on project that we not use (or downloading it) will cause the IPA  much bigger or spend time that we don't need to spend. We know what frameworks we need to use in base of firebase service that we are using and we will use, and the Github Readme.
Other solution is provide a urls where we can download these xcframeworks individually if you don't like to put on assets tag version, how you have actually with Carthage (but in this case with xcframeworks not fat binaries)
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseABTestingBinary.json"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAdMobBinary.json"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json"
ETC

* https://dl.google.com/dl/firebase/ios/v7.0.6/FirebaseABTesting.xcframework.zip"
* https://dl.google.com/dl/firebase/ios/v7.0.6//FirebaseAdMobBinary.xcframework.zip"
* https://dl.google.com/dl/firebase/ios/v7.0.6//FirebaseAnalyticsBinary.xcframework.zip"
ETC

This is something critical for us, time to download this zip will cause more time to spend for release a new version.
Thanks for all, i'll hope that this request will be supported.

@jesusmateos1234 Thanks for the explanation.  The Carthage solution might be feasible for us once Carthage adds support for prebuilt binary xcframeworks - which looks to be making progress now at https://github.com/Carthage/Carthage/pull/3123

@paulb777 Thanks for your support. Nowadays we not use Carthage, so for this we're requesting this.

The idea is that if we migrate to xcframeworks for the Carthage distribution, you could use the Carthage URLs.

Since xcframeworks make binary distribution so much easier:
Wouldn't it make sense to distriubute as vendored_binary with cocoapdos too?
Firebase is a massive dependency slowing down the simplest iOS project build. We stopped integrating it via cocoapods. We simply added the xcframeworks to the project. However this makes updates a mess...

@savage7 Distributing as a vendored_binary makes supporting multiple Xcode versions more complicated, makes debugging harder, makes supporting a dynamic or static linking choice impossible, and is less stable in CocoaPods.
Despite that, there is a solution for the slowest part of the Firebase build - Firestore - at https://github.com/invertase/firestore-ios-sdk-frameworks
We also support building your own binaries with the tooling at https://github.com/firebase/firebase-ios-sdk/tree/master/ReleaseTooling

@paulb777 thank you for your support :blush:
I understand your concerns regarding "marking it harder" and reducing some options (static/dynamic linking...).
It would be really great if the released frameworks would be available separately on each release, like @jesusmateos1234 proposed. This would make it "easy" to create unofficial/official "binary" podspecs referencing these.

@savage7 Thanks for the request. We'll investigate options. Would you explain the issue in a bit more detail. I understand the slowness case, but from my understanding, that is almost exclusively a Firestore issue.  Where else do you see that with Firebase?

@paulb777
We don't use Firestone, only Messaging and Analytics. The Firebase builds are not slower than other builds, but are simply relatively big dependencies, since both have a large number of sub dependencies. So it's no general problem with Firebase, but with source code dependencies...
The problem arises mostly for our SwiftUI projects, we are forced to reduce our dependencies to an absolute minimum otherwise the SwiftUI Previews are getting unusable (timeouts since the preview gets slow or rebuilds take ages).
I've already split up the UI part and the business logic part of our apps into separate frameworks, so the UI only has a minimum set of dependencies.
We are also successfully using https://github.com/grab/cocoapods-binary-cache to prebuild the libs for our devs. But having binary pods from the start would ease the process of speeding up builds alot, since plugins like "cocoapods-binary-cache" have a tendency to break easily...

@jesusmateos1234 Thanks for the explanation. The Carthage solution might be feasible for us once Carthage adds support for prebuilt binary xcframeworks - which looks to be making progress now at Carthage/Carthage#3123

This is now merged  ✅ (Release pending)

Building with Carthage 0.38 with the --use-xcframeworks flag and adding all the xcframeworks that was build under frameworks in XC and setting to "do not embed"  XC fails to build with errors like
Undefined symbol: grpc::ByteBuffer::Dump(std::__1::vector<grpc::Slice, std::__1::allocator<grpc::Slice> >*) const
My cartfile looks like this:
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseABTestingBinary.json"    ~> 8.0
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json"    ~> 8.0
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAuthBinary.json"         ~> 8.0
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseCrashlyticsBinary.json"  ~> 8.0
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseFirestoreBinary.json"    ~> 8.0
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseMessagingBinary.json"    ~> 8.0
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json"  ~> 8.0
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseRemoteConfigBinary.json" ~> 8.0
I looks like I'm missing some GRPC stuff. The only thing Carthage spit out was gRPC-Core.xcframework which I did include.
What am I doing wrong here?

The Firestore folder should also include gRPC-C++.xcframework.  Did you include that (and everything else from the Firestore zip)?

Manually looking in the Firestore.zip reveals gRPC-C++.xcframework among other stuff, however with a Cartfile like this:
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseFirestoreBinary.json" == 8.0
After running the command  carthage update --use-xcframeworks
The Carthage/Build folder looks like this:
BoringSSL-GRPC.xcframework
FirebaseFirestore.xcframework
abseil.xcframework
gRPC-Core.xcframework
leveldb-library.xcframework

Seems to me like everything besides gRPC-C++.xcframework is there.
I'm really not sure what's going on here..

Thanks for the report. I reproduced and opened #8112 to track. Let's continue the discussion there.


Auto select first connected robot on NUsight Vision and Odometry tabs

This is a convenience feature that automatically selects the first connected robot when you visit the Vision and Odometry tabs, to save you having to select one before you can see something.

Yeah that's an existing issues to goes back to the standalone NUsight repo. I think we have a fix at 4Tel, I'll have a look.


Design Resource Page

Includes all Departments.
And under each department, there will be:-
Syllabus, Notes, Books, Previous Year Papers
(If you have a better idea, then do comment it)

I would like to work on this issue

I would like to work on this issue. please guide , do we have to make a HTML,CSS web page or just a design of what we are thinking to create ?

You have to make a complete working page which will obviously include HTML, CSS files.  All the necessary details you have to include on the page is already mentioned. Try to implement it in a better way.


Support Dark mode

This project is really amazing and it's helping me a bunch to get started with some ideas!
I was just wondering if the dark mode is not supported out of the box to support the pro version or you would be open once I manage to fix it to file a PR with such support?

Hi @thebergamo,
Thank you so much for your comment and thank you for your help. All support is welcomed.
Yes, unfortunately, the dark mode isn't supported out of the box yet but I'm planning to do it. Because the project is using Shadcn UI, it shouldn't be a big issue to implement it.
If you manage to implement a dark mode, I would love to review your PR and merge it if it's working perfectly.
Again thank you so much.

I kind of manage already to do it, but there is something that bugs me still.
The only way I manage to support it is using @media (prefers-color-scheme: dark) rather than the regular .dark from out of the box Shadcn UI. If that's fine for you I can do the PR for testing :)

Any reason it didn't work with the regular .dark from out of the box Shadcn UI? It would be great to keep the same logic as the Shadcn UI. What is the blocker to use the .dark feature from Shadcn UI?

I tried to understand, but didn't managed to grasp the why. In general in all my project it usually works fine, but for some reason in this one the .dark from the global.css it got striped and wasn't in the layout.css file

Here are some article explaining the issue:

https://github.com/shadcn-ui/ui/issues/313
https://github.com/shadcn-ui/ui/issues/278
https://github.com/shadcn-ui/ui/issues/515

You should be able to find the solution

Just implement and release a dark mode, you can find a live demo at: https://pro-demo.nextjs-boilerplate.com


Untar

There should be some support for untarring on the client.  Perhaps allow for saving it in local storage?

What's the status here?
I need only untar... ;)

I would also interested in this. Is the project still active?

I currently have no use for this project, so you can consider it dead. If you want to be a committer/author, let me know and I'll add you.
@jedie @dankelleher


Suggestion: Identity data commitments

Is your feature request related to a problem? Please describe.
In some use-cases, it would be necessary for users of a Semaphore to be able to associate data attributes with their identity in a group. For instance, a messaging solution may only wish for users to signal certain messages (e.g. to a particular group) if their identity has certain attributes (e.g. age >= 18).
Describe the solution you'd like
Semaphore identities being inserted should include a commitment to an arbitrary data payload. When a message is being signalled from the Semaphore, that data commitment should be salted by a random value and output publicly. An application can then rely upon this salted data commitment to generate an additional proof that the data commitment contains the attributes that are required for a signalling a given message, without disclosing which identity contains that data commitment, or needing to modify the base Semaphore circuit to include those proprietary rules.
A potential avenue to explore is whether this can be achieved without modifying the Semaphore circuit itself. For instance, if the identity data commitment could be specified as the identity trapdoor (making sure to include some random data within the commitment preimage for security), then the application-specific proof could simply reuse the CalculateNullifierHash component - essentially using the external nullifier as the commitment salt - to prove that the data attribute proof pertains to the same identity used in the signal proof, and then use data from the trapdoor commitment for attribute proofs.

@cedoor where can I find the commit to this?

Hey @AtHeartEngineer, this has not been implemented. Not in this repo at least.


Doc: clarification

https://github.com/threefoldtech/tfchain/blob/d718128ad98d585fa14b31c6111308bdd18074ba/substrate-node/pallets/pallet-tfgrid/spec.md?plain=1#L225
This should be corrected/rephrased as Graphql is not a database.

Yes, Much better.


Update to ungoogled-chromium 130.0.6723.58

This Pull Request updates the package to ungoogled-chromium 130.0.6723.58, and changes CI workflow to publish Apple Developer Notarized Build.
Notes:

[TODO] A submodule bump is made.
[TODO] A patch refresh is made.
Rust is updated according to Chromium requirement.
The GitHub Action workflow is changed so new binaries released will be signed by Apple Developer Account (Team Identifier B9A88FL5XJ).

Building...

Signed-off-by: Qian Qian "Cubik"<EMAIL_ADDRESS>

The application notarization script is being tested.
First Try (running): https://github.com/iXORTech/ungoogled-chromium-macos/actions/runs/11355758475

Could you explain the
codesign --sign "$MACOS_CERTIFICATE_NAME" --force --timestamp --identifier io.dekker.ungoogled-chromium --options restrict,library,runtime,kill --entitlements ./entitlements/app-entitlements.plist --requirements '=designated => identifier "io.dekker.ungoogled-chromium" and anchor apple generic and certificate 1[field.1.2.840.1136<IP_ADDRESS>.6] /* exists */ and certificate leaf[field.1.2.840.1136<IP_ADDRESS>.13] /* exists */' /Applications/Chromium.app

part of your script? I'm not very familiar with this part of the codesign process and is a bit confused by the parameters following --requirements.

Could you explain the
codesign --sign "$MACOS_CERTIFICATE_NAME" --force --timestamp --identifier io.dekker.ungoogled-chromium --options restrict,library,runtime,kill --entitlements ./entitlements/app-entitlements.plist --requirements '=designated => identifier "io.dekker.ungoogled-chromium" and anchor apple generic and certificate 1[field.1.2.840.1136<IP_ADDRESS>.6] /* exists */ and certificate leaf[field.1.2.840.1136<IP_ADDRESS>.13] /* exists */' /Applications/Chromium.app

part of your script? I'm not very familiar with this part of the codesign process and is a bit confused by the parameters following --requirements.

/cc @claudiodekker

So did it work in the end?

So did it work in the end?

I am testing locally now, it seems working.

By the way I need access to settings to this repository for setting up secrets for signing, could you give me permissions to do so? /cc @PF4Public @networkException

The past few action runs actually failed, despite action shows it's successful. The GitHub action env are not properly set, so the signing script actually failed. I am still trying to solve the issue.
/cc @claudiodekker
Do you have any idea what might be happening as my action running log shows
  env:
    MACOS_CERTIFICATE:
    MACOS_CERTIFICATE_PWD:
    MACOS_CERTIFICATE_NAME:
    MACOS_CI_KEYCHAIN_PWD:
    PROD_MACOS_NOTARIZATION_APPLE_ID:
    PROD_MACOS_NOTARIZATION_TEAM_ID:
    PROD_MACOS_NOTARIZATION_PWD:

showing it's all empty instead of having *** that suggests that secrets are redacted?

The past few action runs actually failed, despite action shows it's successful. The GitHub action env are not properly set, so the signing script actually failed. I am still trying to solve the issue.
/cc @claudiodekker
Do you have any idea what might be happening as my action running log shows
  env:
    MACOS_CERTIFICATE:
    MACOS_CERTIFICATE_PWD:
    MACOS_CERTIFICATE_NAME:
    MACOS_CI_KEYCHAIN_PWD:
    PROD_MACOS_NOTARIZATION_APPLE_ID:
    PROD_MACOS_NOTARIZATION_TEAM_ID:
    PROD_MACOS_NOTARIZATION_PWD:

showing it's all empty instead of having *** that suggests that secrets are redacted?

OK now it is working, confusing GitHub Action setup stuff 💀

The newest running action https://github.com/iXORTech/ungoogled-chromium-macos/actions/runs/11427055702/job/31800212783 seems to be working, however, the Notarization process by xcrun notarytool submit notarize.zip --keychain-profile notarytool-profile --wait command seems to be stuck in "In Progress" like I experience on local environment.
/cc @claudiodekker Could you maybe provide some help on this? Is this normal?

OK the notarization just take extremely long time for us (my terminated request from 2 days ago is not shown as accepted in history record)...

Yes, it is way faster once we have the app being accepted once (see https://github.com/iXORTech/ungoogled-chromium-macos/actions/runs/11427055702 rerun no.2, it only has arm64 build notarized though). I think this is almost ready to be merged and released.
Just before that, I will update the announcement, and I'll need settings permission to this repo to set up notarization secrets. @PF4Public @networkException can you give me the access to this repo's admin permission?

Sorry for the delay, you can change the secrets now. If you don't need admin for anything else I'd remove it in the interest of least privilege again after :)

@networkException It's all set now, I'll commit the new announcement soon and then this will be good to go!

I think it's good to go!

Is there anything blocking this PR?
I think, as .6723.69 tarball is still not yet released so the new version can't be built here yet, we should merge this one first? /cc @networkException @PF4Public

Are organisational things settled down?

Are organisational things settled down?

I think my admin privileges are yet to be removed, otherwise everything are set.

I think my admin privileges are yet to be removed

@networkException

Already did


The value of checkbox is not synchronized

When checked, not update the input value。

Please create a test case when submitting a bug, there is a JSfiddle to fork in the readme.


Error when compiling link-config from crates.io

Hello! I'm getting this when compiling link-config from crates.io:
   Compiling link-config v0.1.1
~/.cargo/registry/src/github.com-1ecc6299db9ec823/link-config-0.1.1/src/lib.rs:60:7: 60:8 error: macros that expand to items must either be surrounded with braces or followed by a semicolon
~/.cargo/registry/src/github.com-1ecc6299db9ec823/link-config-0.1.1/src/lib.rs:60     ) )

$ rustc --version
rustc 1.0.0-nightly (f1398d273 2015-01-31 20:21:02 +0000)

$ cargo -V
cargo 0.0.1-pre-nightly (2b9a3d6 2015-01-30 02:47:30 +0000)

This is when loading nanomsg so it may be due to something else upstream but figured since the error mentioned link-config I figured I'd start here.

Ah yes sorry, I'm not actually maintaining this library on crates.io (it's basically a deprecated library in favor of build scripts regardless).
I think I'm going to yank the previous versions there as well. Thanks for the report though!


WIP: Initial impl of RFC-277 - native exe throws on non-zero exit code

PR Summary
WORK IN PROGRESS: Implement a terminating error when a native executable returns a non-zero exit code similar to set -e on Linux.  Tests will come later.
PR Context
Implement RFC 277
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

There are internal APIs to get/set pref vars in ExecutionContext.cs, MshCommandRuntime.cs and PowerShell.cs (public api). Not sure if I need to define this preference variable in those files.

Assigning myself since I've been tasked with taking this work on, but since you've already started @rkeithhill maybe I can support you here instead

@rjmholt That would be great! I'd love to have your input on this.  I need to update this PR as I started it off of my memory of the RFC and now I see that (as @iSazonov  points out), I need to be checking the value of $ErrorActionPreference.  I also see in the PR that there are specifics regarding the generated ErrorRecord that I need to snap to.  I'll push an update to this PR tonight to cover those issues.  I'll try to add the implementation for NativeCommandException but may have some questions about where to put that source.

I implemented NativeCommandException. The result looks like this:

@rjmholt The current build checks seem to be stuck. Is there a way I restart them short of pushing a bogus commit?

Test failures are very weird...
/azp run

@rjmholt There is a test failure in output rendering tests which I don't believe this PR should impact:
2021-08-05T17:44:15.0467419Z     Context NormalView tests
2021-08-05T17:44:15.0498743Z +
2021-08-05T17:44:15.0512900Z
2021-08-05T17:44:15.0527114Z     Context DetailedView tests
2021-08-05T17:44:15.0555317Z +
2021-08-05T17:44:15.0570773Z
2021-08-05T17:44:15.0603255Z
2021-08-05T17:44:15.0611669Z   Describing OutputRendering tests
2021-08-05T17:44:15.0627692Z     [-] Error occurred in Describe block
2021-08-05T17:44:15.0649066Z       PSArgumentException: The key 'It:Skip' has already been added to the dictionary.
2021-08-05T17:44:15.0663568Z       MethodInvocationException: Exception calling "Add" with "2" argument(s): "The key 'It:Skip' has already been added to the dictionary."
2021-08-05T17:44:15.0704752Z       at <ScriptBlock>, D:\a\1\s\test\powershell\engine\Formatting\OutputRendering.Tests.ps1: line 6
2021-08-05T17:44:15.0717916Z       at Invoke-Blocks, D:\a\1\s\src\powershell-win-core\bin\Release\net6.0\win7-x64\publish\Modules\Pester\4.10.1\Functions\SetupTeardown.ps1: line 135
2021-08-05T17:44:15.0731656Z       at Invoke-TestGroupSetupBlocks, D:\a\1\s\src\powershell-win-core\bin\Release\net6.0\win7-x64\publish\Modules\Pester\4.10.1\Functions\SetupTeardown.ps1: line 121
2021-08-05T17:44:15.0746462Z       at DescribeImpl, D:\a\1\s\src\powershell-win-core\bin\Release\net6.0\win7-x64\publish\Modules\Pester\4.10.1\Functions\Describe.ps1: line 209

It's balking on this last line here:
Describe 'OutputRendering tests' {
    BeforeAll {
        $PSDefaultParameterValues.Add('It:Skip', (-not $EnabledExperimentalFeatures.Contains('PSAnsiRendering')))

Anything wrong with that? It's a bit different than how you skipped the tests for this PR when the exp feature is not enabled.

@rjmholt Woohoo!  All checks pass!

@rkeithhill - Thank you for all the hard work. I just spoke with @rjmholt and he thinking he might open a separate pr to add a couple of tests.

Sounds good to me.  I wouldn't be able to do anything until later this evening and even then I don't have a ton of time before I'm out of vacation next week.

@rkeithhill see https://github.com/rkeithhill/PowerShell/pull/21

Merged.

Markdown tests failed. Le sigh.

This is a downside of relying on websites during the build.

/azp run

Opened https://github.com/rkeithhill/PowerShell/pull/22

Closing in favour of https://github.com/PowerShell/PowerShell/pull/15897 because I needed to rebase the branch and can't edit this one (@rkeithhill you can turn that on in future if you'd like)


code for 100% coverage of QuestionSetObjectFactory

see issue #160
code coverage result:

@eyurko addressed your comments in most recent commit


refactor/NR-20915: vmware-esxi

Summary
A concise description of the changes being introduced. If you are submitting a PR for a
new quickstart please review the pre merge checklist section to validate this PR is ready for review.

Pre merge checklist

[ ] Did you check you NRQL syntax? - Does it work?
[ ] Did you check your dashboard image quality? -  Do they look good?
[ ] Did you check that your alerts actually work?
[x] Did you include an InstallPlan and Documentation reference?
[ ] Did you check your descriptive content for voice, tone, spelling and grammar errors?
[ ] Did you attach images of your dashboards to the PR so we can see them working?

 The PR looks great! One small thing - we prefer directory names remain consistent throughout the repository.
Example: quickstarts/vmware/vmware-esxi/
If you wouldn't mind updating to reflect:
install/third-party/VMware ESXi/ -> install/third-party/vmware-esxi/
Thanks!

Hi @josephgregoryii
updated directory name, please once review it.


Machine Learning features implementation.

Machine learning features implementation progress tracker.

[ ] ML Features Development
[ ] ML Features Unit Tests Development
[ ] ML Features Unit Tests Execution
[ ] ML Features Documentation

MachineLearningData class implemented. Concurrency feature is handled by a separate issue (#24). Unit Test cases development should start (issue #25).
Usage example:
import pandas as pd

df = pd.read_csv('sample_data.csv', parse_dates=True, index_col=0)

ml_data = MachineLearningData(
    input_data=df,
    ti_features=[{'ti': 'AccumulationDistributionLine', 'kwargs': {}},
                 {'ti': 'AverageTrueRange', 'kwargs': {}},
                 {'ti': 'BollingerBands', 'kwargs': {'std_number': 3, 'period': 50}}],
    price_diff_periods=1,
    verbose=True)

data = ml_data.createMLData()

ml_data.saveMLData('ml_data.csv')

MachineLearningData class implemented. Concurrency feature is handled by a separate issue (#24). Unit Test cases development should start (issue #25).
Usage example:
import pandas as pd

df = pd.read_csv('sample_data.csv', parse_dates=True, index_col=0)

ml_data = MachineLearningData(
    input_data=df,
    ti_features=[{'ti': 'AccumulationDistributionLine', 'kwargs': {}},
                 {'ti': 'AverageTrueRange', 'kwargs': {}},
                 {'ti': 'BollingerBands', 'kwargs': {'std_number': 3, 'period': 50}}],
    price_diff_periods=1,
    verbose=True)

data = ml_data.createMLData()

ml_data.saveMLData('ml_data.csv')

Concurrency implemented.
Without concurrency, all technical indicators as features: Execution time for all indicators: 203.193 seconds
With concurrency, all technical indicators as features: Execution time for all indicators: 30.831 seconds

Concurrency implemented.
Without concurrency, all technical indicators as features: Execution time for all indicators: 203.193 seconds
With concurrency, all technical indicators as features: Execution time for all indicators: 30.831 seconds

Recurrent Neural Network implementation, handled in issue #30.

Recurrent Neural Network implementation, handled in issue #30.

Long Short Term Memory Neural Network implementation, handled in issue #31.

Long Short Term Memory Neural Network implementation, handled in issue #31.

Machine Learning API development is done, in the RNN implementation branch. RNN implementation is used as POC.

Machine Learning API development is done, in the RNN implementation branch. RNN implementation is used as POC.


Document CLI commands for finding and rerunning failed tasks

PR: https://github.com/influxdata/influxdb/pull/20307

[ ] Add influx task retry-failed command

Relevant URLs

https://docs.influxdata.com/influxdb/cloud/reference/cli/influx/task/
https://docs.influxdata.com/influxdb/cloud/process-data/manage-tasks/

Confirming from the OSS side that this merged to master, and we plan to include it in the 2.0.5 release


Use input dtype for constants in jax.nn.gelu

This ensures that gelu(bf16).dtype == bf16

Thanks, @trevorcai ! Is it possible to add a test for this new behavior (so that we don't accidentally revert it)?

Done.


support multi keys yankpad-map

Hi
would it possible to add support for multi key yankpad-map keys?
so something like this:
* img: image size  X                                                 :key:ix:
* img: image size  Y                                                  :key:iy:

this (for me at least) could improve on usability
best
Z

This already works for me. Have you tried it?

yes that works, i did try it before unsuccessfully but probably mucked it somehow :)
thx, closing
Z


I really like seeing my bot rebranded

Very epic, My bot has been renamed to Rei and made into a Github bot anyone can setup

May I know what your bot exactly is? I got the bot source from a friend, made some improvement and put it on GitHub, this is the second time I've seen someone talk about it. Maybe we could talk about it on Discord as I'm really confused about what's going on.

add me on discord @ethan29183


Incorrect storage download link host in local

Describe the bug
Local edge functions run on docker inside a container called supabase_deno_relay which auto-sets the SUPABASE_URL. However, it uses the internal URL of the container network. This causes issues with the JS clients that run inside edge functions with storage since it creates the download and signed URLs using the internal http://supabase_kong_hyperion-app:8000 instead of the usual exposed localhost:54321api endpoint.
To Reproduce
Steps to reproduce the behavior:

Run edge functions with serve cli command
Generate a download link using the JS client inside an edge function
Try to access the download link (will be in this format: http://supabase_kong_app:8000/storage/v1/object/public/public/users/ce5b2b2f-cfdc-4f56-a886-488dba35a184/file.txt) instead of using localhost:54321

Expected behavior
The download link generated is accessible locally using localhost:54321
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Version of CLI 1.75.2
Version of supabase-js 2.26.0

Yup this is a known limitation https://github.com/supabase/cli/issues/1079#issuecomment-1546058111. with a temporary workaround. I will leave this issue open for tracking.

Hey @sweatybridge , gotcha. How about if in the storage client, the download link functions check if the URL contains the internal edge function SUPABASE_URL (the kong url) used by the edge function and if it is, rewrite it to the localhost:54321 endpoint?

Perhaps a simpler alternative is to instantiate a separate StorageClient in your edge function with url set to localhost:54321. For example,
import { StorageClient } from '@supabase/storage-js'

const STORAGE_URL = 'http://localhost:54321/storage/v1'
const SERVICE_KEY = '<service_role_key>'

const storageClient = new StorageClient(STORAGE_URL, {
  apikey: SERVICE_KEY,
  Authorization: `Bearer ${SERVICE_KEY}`,
})

You can use this new client for creating signed urls and the original supabase-js client for other operations that target kong.

Hey @sweatybridge update: the suggested approach doesnt work, the URL has to be change after the fact, if not the edge function client cannot find the API endpoint:
Handler error: StorageUnknownError: error sending request for url (http://localhost:54321/object/sign/public): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
    at https://esm.sh/v127/@supabase/storage-js@2.5.1/esnext/storage-js.mjs:2:1638
    at Generator.next (<anonymous>)
    at u (https://esm.sh/v127/@supabase/storage-js@2.5.1/esnext/storage-js.mjs:2:1254)

I think my original approach will work and will remove the need for devs to handle this edge case any time we use the storage client in local.

I see, thanks for investigating. Let me transfer this ticket to storage-js to see if anyone can pick it up sooner.


Completed pull request (ready for merge)

In this initial set of commits, I have created some generic "workhorse" functions in window.R, and then used these generic functions to implement the ozone calculations requested in issue #2 in a set of 4 functions (o3_daily_max, o3_rolling_8hr_avg, o3_ann_4th_highest, o3_three_yr_avg).
Next steps will be to implement the other 3 functions mentioned in issue #11, #12, #13, using these generic functions.

Thanks @nograpes! I'll have a look and get back to you. But feel free to keep working while I do.

This is looking really good @nograpes! I think you addressed all of my original comments. I've started poking around a bit again but won't do a full review until you let me know you're ready

Great, I still have more than a few tests to add, but I'm getting there. It'll be ready for review by midnight tonight.

It is now ready for a full review.

All the changes have been made, but unfortunately travis seems to be failing when building against the dev version of R. It can't seem to find all the dependencies like rgdal and sp. I'm working through the problem now.

Getting gdal and friends working in Travis can be a nightmare, but I have some experience with it. I'll have a look too

Also, if it's building fine on r-release you can just remove the R-devel line in .travis.yml and I can fix it later

Okay, I'll remove the dev version now, but I'll continue to debug the issue

@nograpes once you have fixed that one bug and added some tests for the exclusion functionality, I think we will be good to merge.

Okay, so that last round of checking and new tests revealed a bug and few annoying inconsistencies. Everything is all sorted out now, and I am declaring this ready to merge.

Nice catches - adding tests is great for that! Happens to me all the time :) LGTM!


Replace debug (pll|mmcm) with debug clocks

Only one of these will be active, and output anything, so let's just run both, under the hood.

LGTM!


Get variable and constraint names

Many MOI tests require getting variable and constraint indices by name.
The two solutions are:

keep a dictionary of names for each like HiGHS.jl does. Might be simpler to build and test? But we create yet another pair of dicts, this wrapper has a lot of them between SCIP.Optimizer and SCIPData
fetch the names from SCIP directly, see following function:

/** parses the given string for a variable name and stores the variable in the corresponding pointer if such a variable
 *  exits and returns the position where the parsing stopped
 *
 *  @return \ref SCIP_OKAY is returned if everything worked. Otherwise a suitable error code is passed. See \ref
 *          SCIP_Retcode "SCIP_RETCODE" for a complete list of error codes.
 *
 *  @pre This method can be called if @p scip is in one of the following stages:
 *       - \ref SCIP_STAGE_PROBLEM
 *       - \ref SCIP_STAGE_TRANSFORMING
 *       - \ref SCIP_STAGE_INITPRESOLVE
 *       - \ref SCIP_STAGE_PRESOLVING
 *       - \ref SCIP_STAGE_EXITPRESOLVE
 *       - \ref SCIP_STAGE_PRESOLVED
 *       - \ref SCIP_STAGE_SOLVING
 */
SCIP_EXPORT
SCIP_RETCODE SCIPparseVarName(
   SCIP*                 scip,               /**< SCIP data structure */
   const char*           str,                /**< string to parse */
   SCIP_VAR**            var,                /**< pointer to store the problem variable, or NULL if it does not exit */
   char**                endptr              /**< pointer to store the final string position if successful */
   );

Opinions? @odow @rschwarz @etadewal

after trying things for a bit, calling SCIP methods directly seems a bit brittle for now (I'm never sure in which state SCIP is), we'll go for yet anoth dict

edit from @fserra : SCIPfindVar could do the job we want here

tackled in #205

I believe this was implemented at some point, letting SCIP store the names. But it lead to errors, so it was removed again. Unfortunately, I can't remember the details. So, bon courage!

Keeping a dictionary isn't too hard. Check the var_to_name stuff here:
https://github.com/jump-dev/MathOptInterface.jl/blob/master/src/Utilities/model.jl

This was done with #205

it does not yet follow the MOI convention that getting a variable name when several have the same should throw though


[Question] Is there any plan to add message queue component support ???

1. What version of Go and system type/arch are you using?

First of all, thank the team for open-sourcing such a good framework of GF, which provides great help for my daily work !!!
GF integrates a large number of very effective and useful components, but it seems that there is no support development plan for the message queue component. The message queue has become particularly important in daily work, and I hope it can support !!!
2. What version of GoFrame are you using?

3. Can this issue be re-produced with the latest release?
4. What did you do?

5. What did you expect to see?
6. What did you see instead?

Why not use message queue service such as RabbitMQ directly?
You can use rabbitmq client for Go and embaded to GoFrame by yourself.


⚠ Nano has degraded performance

In 85cf9e3, Nano (https://nano.shuttleapp.rs/up) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: Nano performance has improved in 8790d94 after 27 minutes.


"The editor has crashed", no way to know what's really happening.

I've build atom on archlinux, but everytime I run it, I eventually get The editor has crashed.
The fact that editor crashes is nothing special, in fact not an issue, but I am literally unable to provide any further information! This message is the only thing that appears. I DO know that this is unhelpful, and that's exactly the problem.
What I've done:
-> Tried checking /tmp/Atom Crashes, but it was... empty
-> Tried running with the -f option, only find out that it's impossible to get crash dump id:
$ atom -f
[1928:0305/185349:ERROR:browser_main_loop.cc(203)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[1928:0305/185350:INFO:audio_manager_pulse.cc(257)] Failed to connect to the context.   See https://www.chromestatus.com/features/6750456638341120 for more details.", source:  (0)
Failed to get crash dump id.
Report Id:

-> I've read the debugging info, only to find out that I am not as lucky not to have this issue in --safe mode, and I can't check my settings since the editor crashes
->~/.atom/nohup.out shows nothing more (and this super secret file location wasn't included in the debugging document....)
I don't know any other secret tricks to get more info.

What version of freetype2 do you have installed? There's a known issue with electron and freetype 2.6.3-1, so you have to pin it at 2.6.2-1. There's a fix but atom is painfully slow to pull it.

I have 2.6.3-1, but I'm currently using the binary package and it works. (I didn't reinstall anything)
So either the package author has pulled the fix, or it's a different bug, but unfortunately I can't test because I no longer have the build directory and I'm unable to build it again due to lack of time.

That version of freetype2 has an issue with electron that will be fixed when PR #10983 is merged. That was most likely your issue.

+1 for version 1.7.0-beta2 under Arch Linux.

+1 for version 1.7.4 under Arch Linux.
guess its related to the actual issue headline.
atom -df
[2127:0530/132223:ERROR:browser_main_loop.cc(203)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[2127:0530/132223:INFO:audio_manager_pulse.cc(257)] Failed to connect to the context.  Error: Connection refused
App load time: 547ms
Failed to get crash dump id.
Report Id:

 atom --version
Atom    : 1.7.4
Electron: 0.36.12
Chrome  : 47.0.2526.110
Node    : 5.1.1

honestly, i dont need sound in atom.

Try building from git checkout b9dbb81. That's the version of 1.9.0-dev that I currently have running on my Manjaro box.

This thread has diverged from the original post and thread title. I suggest opening an new thread regarding the linux freetype issue, because while that is a problem, it has no bearing on the fact there is little to no useful information provided with "the editor has crashed" alert. I've ran into this alert on Windows when adding a specific project folder to an empty Atom window (other project folders do not cause crashes) and I was hoping this thread (given the title) might help provide where to look for info or how to get it. While the last post in this thread is from May 2016, the lack of information on this type of crash is still an issue in the most recently release beta 1.15.0-beta3 x64 on Windows.
Anyhow, I'd like to see this topic remain true to it's origin: more information should be provided when Atom crashes with the "The editor has crashed" dialog.

In this case, the crash was caused by an upstream issue in Electron. The crash dump provided enough information for diagnosis. The issue was diagnosed in another thread and I recognized the same environment here.
I don't think the intention of this thread was ever to discuss how Atom handles crashes in general. If you feel the way Atom handles crashes in general isn't enough, you should create an issue and/or visit the Slack channels to discuss it.

I was affected by this problem back in the day, and it got fixed via the natural process of updates percolating through the ecosystem. This issue can be closed.


debug/pe: TestInternalLinkerDWARF fail in windows

What version of Go are you using (go version)?

$ go version
go version devel go1.22-d6ef98b8 Thu Nov 16 05:53:55 2023 +0000 windows/amd64

Does this issue reproduce with the latest release?
yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=auto
set GOARCH=amd64
set GOBIN=
set GOCACHE=D:\tmp\go-build
set GOENV=C:\Users\26454\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=D:\file\gofile\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=D:\file\gofile
set GOPRIVATE=
set GOPROXY=https://goproxy.cn,direct
set GOROOT=C:\Users\26454\.go\current
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=local
set GOTOOLDIR=C:\Users\26454\.go\current\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=devel go1.22-d6ef98b8 Thu Nov 16 05:53:55 2023 +0000
set GCCGO=gccgo
set GOAMD64=v3
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\26454\AppData\Local\Temp\go-build186784699=/tmp/go-build -gno-record-gcc-switches

What did you do?
go test debug/pe
What did you expect to see?
test pass.
What did you see instead?
--- FAIL: TestInternalLinkerDWARF (0.99s)
    file_test.go:389: building test executable for linktype 2 failed: exit status 1 # command-line-arguments
        panic: runtime error: index out of range [10] with length 10

        goroutine 1 [running]:
        cmd/link/internal/loader.(*Relocs).At(...)
                C:/Users/26454/.go/current/src/cmd/link/internal/loader/loader.go:1885
        cmd/link/internal/loadpe.findHandlerInXDataAMD64(0xc00009a000, 0x1812c, 0x44)
                C:/Users/26454/.go/current/src/cmd/link/internal/loadpe/seh.go:108 +0x2b2
        cmd/link/internal/loadpe.processSEHAMD64(0xc00009a000, 0x1812d)
                C:/Users/26454/.go/current/src/cmd/link/internal/loadpe/seh.go:54 +0x1a5
        cmd/link/internal/loadpe.processSEH(0xc00009a000?, 0xc000018144?, 0x29a2e40?, 0xc0?)
                C:/Users/26454/.go/current/src/cmd/link/internal/loadpe/seh.go:33 +0x79
        cmd/link/internal/loadpe.Load(0xc00009a000, 0x77ed20, 0x71, 0xc0023eae50, {0x581b85, 0x4}, 0x5fe8d0?, {0xc0023eeaf0, 0x64})
                C:/Users/26454/.go/current/src/cmd/link/internal/loadpe/ldpe.go:605 +0x18cd
        cmd/link/internal/ld.ldobj.func3(0xc00014e000, 0xc0023eae50?, {0x581b85?, 0x0?}, 0xc0023eeaf0?, {0xc0023eeaf0?, 0xc0023eeaf0?})
                C:/Users/26454/.go/current/src/cmd/link/internal/ld/lib.go:2223 +0x6b
        cmd/link/internal/ld.hostObject(0xc00014e000, {0x581b85, 0x4}, {0xc0023eeaf0, 0x64})
                C:/Users/26454/.go/current/src/cmd/link/internal/ld/lib.go:2397 +0x378
        cmd/link/internal/ld.loadWindowsHostArchives(0xc00014e000)
                C:/Users/26454/.go/current/src/cmd/link/internal/ld/lib.go:695 +0x10d
        cmd/link/internal/ld.(*Link).loadlib(0xc00014e000)
                C:/Users/26454/.go/current/src/cmd/link/internal/ld/lib.go:641 +0x7c5
        cmd/link/internal/ld.Main(_, {0x20, 0x20, 0x1, 0x7, 0x10, 0x0, {0xc0000086b9, 0x1, 0x1}, ...})
                C:/Users/26454/.go/current/src/cmd/link/internal/ld/main.go:347 +0x122b
        main.main()
                C:/Users/26454/.go/current/src/cmd/link/main.go:72 +0xdfb
FAIL
FAIL    debug/pe        9.143s
FAIL

(CC @golang/windows)

Bug introduced in CL 534555. This logic is wrong: https://github.com/golang/go/blob/d6ef98b8fa4851f025779ef4ade084d63290de2a/src/cmd/link/internal/loadpe/seh.go#L93-L98
sort.Search will return idx == xrels.Count() if no symbol is found, but the code is checking if idx == 0 instead. While working on this I couldn't trigger this code path, and the Go builders don't complain neither, I supose that it depends on the GCC toolchain.
Would be good to understand how is that no relocation was found, maybe a malformed .pdata section? Either way, let's first fix the bug, I can investigate it once I have more availability. @dagood could you help here submitting the fix? Thanks.

Submitted the simple fix at https://go-review.googlesource.com/c/go/+/543076.
@qiulaidongfeng, what C compiler and version are you using?
It sounds like this would be useful information to be able to reproduce the issue and perhaps figure out a test case. (I also haven't seen this before.)

The test still failed
--- FAIL: TestInternalLinkerDWARF (3.05s)
file_test.go:389: building test executable for linktype 2 failed: exit status 1 # command-line-arguments
crt2(.xdata): unhandled relocation for __C_specific_handler (type 46 (SDYNIMPORT) rtype 88 (R_PEIMAGEOFF))
crt2(.xdata): unhandled relocation for __C_specific_handler (type 46 (SDYNIMPORT) rtype 88 (R_PEIMAGEOFF))
FAIL
FAIL    debug/pe        28.196s
gcc --version
gcc (MinGW-W64 x86_64-msvcrt-posix-seh, built by Brecht Sanders) 12.1.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Get from here: https://winlibs.com/

Hmm, this error means that the __C_specific_handler function is only reachable via a SEH handler, so the Go linker will not add it to the final binary unless it is found by loadpe.findHandlerInXDataAMD64, in which case the handler is made reachable if the function being guarded is also reachable (this happens here).
We should understand why loadpe.findHandlerInXDataAMD64 can't find the handler when calling sort.Search, as it should be there. @dagood can you try to reproduce the issue and fix it? Else we can just revert CL 534555 and pospone this improvement till go1.23.

Confirmed with winlibs-x86_64-posix-seh-gcc-12.1.0-llvm-14.0.6-mingw-w64msvcrt-10.0.0-r3:
=== RUN   TestInternalLinkerDWARF
    file_test.go:389: building test executable for linktype 2 failed: exit status 1 # command-line-arguments
        crt2(.xdata): unhandled relocation for __C_specific_handler (type 46 (SDYNIMPORT) rtype 88 (R_PEIMAGEOFF))
        crt2(.xdata): unhandled relocation for __C_specific_handler (type 46 (SDYNIMPORT) rtype 88 (R_PEIMAGEOFF))
--- FAIL: TestInternalLinkerDWARF (1.88s)

I tested a few other versions using MSVCRT (12.2.0, 12.3.0, 13.2.0) and got the same result.
Using UCRT on the same 12.1.0 version runs successfully.
winlibs-x86_64-posix-seh-gcc-12.1.0-llvm-14.0.6-mingw-w64ucrt-10.0.0-r3
(Side note: these builds are listed on https://www.mingw-w64.org/downloads/, so they aren't really obscure. This is something to consider when setting up more CI to validate more C compilers and/or a list of what we're testing.)
My understanding is that UCRT is newer, and MSVCRT is useful to target older versions of Windows, so swapping might not be possible in some situations.
(I'm planning to look into this further. Advice is of course quite welcome!)

An update on what I've found so far. It looks like the first different thing about the MSVCRT vs. UCRT build is that when building with the MSVCRT MinGW, Go includes crt2.o because this condition is met:
https://github.com/golang/go/blob/e58c9baa9f7b708bcd6a3abf5a8426b0531ed002/src/cmd/link/internal/ld/lib.go#L690-L697
This is where the failing search happens.
MinGW, providing crt2.o, is unfortunately not able to parse its xdata all that well. .\bin\objdump.exe -x .\x86_64-w64-mingw32\lib\crt2.o shows this:
...
Dump of .xdata
<PHONE_NUMBER>000000 (rva: 00000000):<PHONE_NUMBER>000000 -<PHONE_NUMBER>000017
warning: xdata section corrupt
<PHONE_NUMBER>000008 (rva: 00000008):<PHONE_NUMBER>000017 -<PHONE_NUMBER>00009a
warning: xdata section corrupt
<PHONE_NUMBER>000014 (rva: 00000014):<PHONE_NUMBER>00009a -<PHONE_NUMBER>0000f6
warning: xdata section corrupt
<PHONE_NUMBER>000020 (rva: 00000020):<PHONE_NUMBER>0000f6 -<PHONE_NUMBER>000125
        Version: 1, Flags: UNW_FLAG_EHANDLER
        Nbr codes: 3, Prologue size: 0x08, Frame offset: 0x0, Frame reg: rbp
          pc+0x08: alloc small area: rsp = rsp - 0x30
          pc+0x04: FPReg: rbp = rsp + 0x0 (info = 0x0)
          pc+0x01: push rbp
        Handler:<PHONE_NUMBER>000000.
        User data:
          000: 01 00 00 00 05 01 00 00 1b 01 00 00 00 00 00 00
          010: 1b 01 00 00
<PHONE_NUMBER>000044 (rva: 00000044):<PHONE_NUMBER>000125 -<PHONE_NUMBER>000154
        Version: 1, Flags: UNW_FLAG_EHANDLER
        Nbr codes: 3, Prologue size: 0x08, Frame offset: 0x0, Frame reg: rbp
          pc+0x08: alloc small area: rsp = rsp - 0x30
          pc+0x04: FPReg: rbp = rsp + 0x0 (info = 0x0)
          pc+0x01: push rbp
        Handler:<PHONE_NUMBER>000000.
        User data:
          000: 01 00 00 00 34 01 00 00 4a 01 00 00 00 00 00 00
          010: 4a 01 00 00
<PHONE_NUMBER>000068 (rva: 00000068):<PHONE_NUMBER>000154 -<PHONE_NUMBER>00047f
warning: xdata section corrupt
<PHONE_NUMBER>000074 (rva: 00000074):<PHONE_NUMBER>00047f -<PHONE_NUMBER>000583
warning: xdata section corrupt
<PHONE_NUMBER>000080 (rva: 00000080):<PHONE_NUMBER>000583 -<PHONE_NUMBER>00068a
warning: xdata section corrupt
<PHONE_NUMBER>00008c (rva: 0000008c):<PHONE_NUMBER>00068a -<PHONE_NUMBER>0006b9
warning: xdata section corrupt

...

So, one part of the puzzle: is this .o file not conforming to what this Go code expects? (Still looking deeper.)

Another part is that some of the Go logic doesn't seem to match the docs and .NET CoreCLR:
https://github.com/golang/go/blob/2e77b51df5b9f7753f500c6cbba8f0dab5bf2250/src/cmd/link/internal/loadpe/seh.go#L84-L88
In https://learn.microsoft.com/en-us/cpp/build/exception-handling-x64?view=msvc-170, the number of codes is byte 3 of UNWIND_INFO, taking into account the bit field:

Size
Value

UBYTE: 3
Version

UBYTE: 5
Flags

UBYTE
Size of prolog

UBYTE
Count of unwind codes

...
...

Changing it to data[2] makes the value match what's in the xdata dump.
.NET CoreCLR matches that at https://github.com/dotnet/runtime/blob/02812350ddacde36e7f05f0aabd7c43b3095bc65/src/coreclr/inc/win64unwind.h#L99-L106.
I'm not able to track down a source for the if codes%2 != 0 {  check. The xdata dump claims that there are 3 codes, but according to this logic there are actually 4 codes. I hoped looking at raw xdata dump data would clear it up, but it's not yet clear to me what this situation would look like.
Both of these affect the targetOff so I would expect some effect on the search. However, so far I haven't seen any change in the end results after making these changes. (Still looking deeper.)

I also noticed this:
https://github.com/golang/go/blob/2e77b51df5b9f7753f500c6cbba8f0dab5bf2250/src/cmd/link/internal/loadpe/seh.go#L17-L19
https://learn.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlvirtualunwind says these should be 1, 2, 4, because they're flags. (To be clear, the bitshift is fine, it's how this code deals with the bit field.)
4 isn't being used in these entries and the CHAININFO execution path doesn't get hit in my repro, so I don't think it's related to this issue.

Changing it to data[2] makes the value match what's in the xdata dump.

Good catch. I suppose the code works even with this bug because the relocation search doesn't look for an exact offset match. It will certainly find the wrong relocation sometimes.

I'm not able to track down a source for the if codes%2 != 0 {  check. The xdata dump claims that there are 3 codes, but according to this logic there are actually 4 codes

There are 3 logical codes, but 4 codes in disk, as that array should contain an even number of entries. See this part of the docs:

For alignment purposes, this array always has an even number of entries, and the final entry is potentially unused. In that case, the array is one longer than indicated by the count of unwind codes field.

So, one part of the puzzle: is this .o file not conforming to what this Go code expects? (Still looking deeper.)

We should make our code resilient to corrupted xdata entries, as seems to be this case. What if we mark the xrel in https://github.com/golang/go/blob/539b4d8d5bb91f74f580a1bc6e8e28b9de38aedd/src/cmd/link/internal/loadpe/seh.go#L55 as Weak in case the handler is nil so the linker doesn't complain?

@dagood I looks like I got confused counting bytes. You will have to also fix targetOff and unwStaticDataSize (this last one doesn't make much sense). The right one is targetOff := add + 4 + 2*int64(codes). This might solve the whole issue.

Thanks! Yep, it seems to work now with any MinGW version I throw at it.
I think unwStaticDataSize still makes sense as 4, for targetOff := add + unwStaticDataSize + 2*int64(codes) and the earlier bounds check. In fact, I think that 2 could also use name, like unwCodeSize.
I'll put up a CL shortly.


Add ibc3 feature

From what i know, ibc3 is the norm in cosmos, including this feature seems to be the logic thing to do in ics721.
Small fixes to unit-tests, ibc_channel_open change of expected result, and upgrade optimizer version to 0.12.9
Closes #36

pretty much every chain is now running ibc v3 and v4 coming with the new wasmd upgrade so I guess this is fine.

i've moved this commit into my latest changes: https://github.com/public-awesome/ics721/commit/1b086c6934ffe8667e89db3632501d48d795b2f4


Is this project Dead?

Hey folks,
Its seem a long time since updates on this project.. is this a dead project?
Thanks

I don't know if this project is dead (though it looks to be). However, I know another one that is actively developed: https://github.com/nartc/mapper

Hi, I still love the project. However, I think it is technically dead indeed 😀. The alternative mentioned above is a good suggestion. Originally, this repo also was based on a port, although it has been completely rewritten since.

Thanks @patrykdawid and @loedeman !
As the owner confirms it, Ill close this comment.
Keep on rocking!


Res.status returns 404 when using promises in routes

Hello,
The response object returns a 404 whenever I use promises with the routes. When I remove the promise, the response is resolved normally. The examples on the site are done with async/await, so I think that is likely the issue. Is there any example using regular promises?

Hey,
Thanks for your question. If you didn't mind providing a code snippet that would be a huge help.
Here is an arbitrary example of using Rill with vanilla promises.
require('isomorphic-fetch')

app.get('/home', (ctx) => {
  return fetch('http://google.ca')
    .then(response => response.text())
    .then(html => {
      ctx.res.body = html
    })
})

@DylanPiercey I have something like that too. At what point is the status set? When the ctx.res.body is set?

If the body is non empty the status will default to 200. You can also manually set ctx.res.status = 200.

@DylanPiercey So the promise needs to be returned for it to properly resolve.

@imolorhe that is correct, otherwise Rill has no idea when the promise finishes.

@DylanPiercey Okay so what exactly determines the value of ctx.res.status? Is it setting the value of ctx.res.body? Or there is another condition that is applied? I am asking this because it seems I am getting 404 even without a promise involved.

ctx.res.status will only automatically set if there is a ctx.res.body, if there is a ctx.res.body it will default to 200. Otherwise it is 404 unless explicitly set by the user.

@DylanPiercey Thanks! I know it's probably too much to ask, but what is the promise-based equivalent of this snippet:
app.use(async (ctx, next)=> {
  try {
    await next()
  } catch (error) {
    // Catch errors later on in the stack.
    log.error('server error', err)
  }
})

@imolorhe no problem -
app.use((ctx, next) => {
  return next().catch((err) => {
    log.error('server error', err)
  })
})

@imolorhe i'm going to close this for now. Hit me up on gitter if you have any other questions regarding this or promises 😄.

@DylanPiercey Okay


Exhaustiveness check does not work for tagged union when there is the only tag

TypeScript Version:  3.9.2

Search Terms:

typescript exhaustiveness check for single tag
typescript exhaustiveness check for single option
typescript switch case on tagged union with single item
typescript type guards for tagged union of single item

Expected behavior:
No compile errors: we cannot get the default branch, so type of x in there should be narrowed down to never, and the function test is correct.
Actual behavior:
Compile error at line 20 (return absurd(x);):

Argument of type 'Disjoint' is not assignable to parameter of type 'never'.

However, if we uncomment the code that adds the second item to Disjoint, it will be working properly.
Code

enum Labels {RED, YELLOW}

type Disjoint
    = { label: Labels.RED; value: number }
    // | { label: Labels.YELLOW; value: string}
;

const absurd = (u: never): never => { throw new Error() };

function test(x: Disjoint): number {
    switch (x.label) {
        case Labels.RED:
            return x.value;

        // case Labels.YELLOW:
        //     return +x.value;

        default:
            return absurd(x);
    }
}

This may seem a weird corner-case, but I have stumbled this behaviour multiple times. You can have a tagged union of single tag when you plan to extend it later. When you want to ensure that later when you add new tags to it, you will get compile errors in every non-exhaustive switch statement that must be exhaustive.
Output
"use strict";
var Labels;
(function (Labels) {
    Labels[Labels["RED"] = 0] = "RED";
    Labels[Labels["YELLOW"] = 1] = "YELLOW";
})(Labels || (Labels = {}));
const absurd = (u) => { throw new Error(); };
function test(x) {
    switch (x.label) {
        case Labels.RED:
            return x.value;
        // case Labels.YELLOW:
        //     return +x.value;
        default:
            return absurd(x);
    }
}

Compiler Options
{
  "compilerOptions": {
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "strictBindCallApply": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "useDefineForClassFields": false,
    "alwaysStrict": true,
    "allowUnreachableCode": false,
    "allowUnusedLabels": false,
    "downlevelIteration": false,
    "noEmitHelpers": false,
    "noLib": false,
    "noStrictGenericChecks": false,
    "noUnusedLocals": false,
    "noUnusedParameters": false,
    "esModuleInterop": true,
    "preserveConstEnums": false,
    "removeComments": false,
    "skipLibCheck": false,
    "checkJs": false,
    "allowJs": false,
    "declaration": true,
    "experimentalDecorators": false,
    "emitDecoratorMetadata": false,
    "target": "ES2017",
    "module": "ESNext"
  }
}

Playground Link: Provided

@RyanCavanaugh Doesn't discriminated-union narrowing only apply when the property being checked is a unit type, though?  In your example arg.x is string, so .x wouldn't be a discriminator there anyway.  And if .x were a unit type, then it seems fair to assume such a check wouldn't exist unless you wanted the narrowing.


Is there any way to set table's defaultrowheight in word?

I'm using NPOI 2.5.6
But i don't find any way to set default row height of table in word.
If it's support?

https://stackoverflow.com/questions/36545834/how-to-decrease-default-height-of-a-table-row-in-word-using-apache-poi-in-java
You can set the row height by setting XWPFTableRow.Height


AirMapCoordinate.h file not found

Hi,
I got an error "AirMapCoordinate.h file not found" while build the code with XCODE 13.1.
Here is my system:

XCODE -> 13.1
REACT-NATIVE -> 0.64.2
REACT-NATIVE-MAPS -> 0.30.1

Here is my PodFile
`
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '11.0'
use_frameworks! :linkage => :static
pre_install do |installer|
Pod::Installer::Xcode::TargetValidator.send(:define_method, :verify_no_static_framework_transitive_dependencies) {}
installer.pod_targets.each do |pod|
if pod.name.eql?('RNPermissions') || pod.name.start_with?('Permission-')
def pod.build_type;
# Uncomment the line corresponding to your CocoaPods version
Pod::BuildType.static_library # >= 1.9
# Pod::Target::BuildType.static_library # < 1.9
end
end
end
end
def appodeal
pod 'APDAdColonyAdapter'
pod 'APDAmazonAdsAdapter'
pod 'APDAppLovinAdapter'
pod 'APDBidMachineAdapter'
pod 'APDFacebookAudienceAdapter'
pod 'APDGoogleAdMobAdapter'
pod 'APDIronSourceAdapter'
pod 'APDMyTargetAdapter'
pod 'APDOguryAdapter'
pod 'APDSmaatoAdapter'
pod 'APDStartAppAdapter'
pod 'APDUnityAdapter'
pod 'APDVungleAdapter'
pod 'APDYandexAdapter'
end
target 'testapplication' do
permissions_path = "../node_modules/react-native-permissions/ios"
pod 'Permission-AppTrackingTransparency', :path => "#{permissions_path}/AppTrackingTransparency"
pod 'Permission-Calendars', :path => "#{permissions_path}/Calendars"
pod 'Permission-Camera', :path => "#{permissions_path}/Camera"
pod 'Permission-Contacts', :path => "#{permissions_path}/Contacts"
pod 'Permission-FaceID', :path => "#{permissions_path}/FaceID"
pod 'Permission-LocationAccuracy', :path => "#{permissions_path}/LocationAccuracy"
pod 'Permission-LocationAlways', :path => "#{permissions_path}/LocationAlways"
pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
pod 'Permission-MediaLibrary', :path => "#{permissions_path}/MediaLibrary"
pod 'Permission-Notifications', :path => "#{permissions_path}/Notifications"
pod 'Permission-PhotoLibrary', :path => "#{permissions_path}/PhotoLibrary"
pod 'Permission-PhotoLibraryAddOnly', :path => "#{permissions_path}/PhotoLibraryAddOnly"
pod 'Permission-Reminders', :path => "#{permissions_path}/Reminders"
rn_maps_path = '../node_modules/react-native-maps'
pod 'react-native-google-maps', :path => rn_maps_path
config = use_native_modules!
use_react_native!(
:path => config[:reactNativePath],
# to enable hermes on iOS, change false to true and then install pods
:hermes_enabled => false
)
pod 'react-native-maps', :path => '../node_modules/react-native-maps'
target 'testapplicationTests' do
inherit! :complete
# Pods for testing
end
appodeal
post_install do |installer|
react_native_post_install(installer)
end
end
`
Here is my AppDelegate.m

Here is my Header Search Path

I already look at another issue reports about it, I already tried everything but still not works.

Please help

I am also facing the same issue suddenly. This has been working earlier.
Project Config:
XCODE -> 13.1
REACT-NATIVE -> 0.65.1
REACT-NATIVE-MAPS -> 0.28.0

same here was working fine until a week ago

It got automatically fixed. Try clearing cache and pod repo update might help.

Same issue!

Closing for now. If you keep experiencing this issue, please feel free to open a new issue following the bug issue template.

I'm experiencing this issue! It's after upgrade to Expo SDK 46

https://github.com/react-native-maps/react-native-maps/issues/3597#issuecomment-1168582636

same its issue

Fixed here: https://github.com/react-native-maps/react-native-maps/issues/3597