example not working

Hello, thank you for your effort and the package .. I tried to run your example but it's not  working  for me .

I tried to use your package to but there is  an issue with the transport and  producer callback it doesn’t  trigger  when produce

Have you ran the example?

Yes it's ran but it doesn't work when i try to join !!
That's what I get

I think server down. Tried yesterday. Use local server
чт, 29 июл. 2021 г., 17:51 salahkamal @.***>:

Yes it's ran but it doesn't work when i try to join !!
That's what I get
[image: Screenshot_20210729-164809]
https://user-images.githubusercontent.com/19710233/127513675-3454f3ff-f3b0-42df-a250-e22efb1a2e9e.jpg
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Blancduman/mediasoup-client-flutter/issues/18#issuecomment-889212020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVXEOYLP5TSDP5BFJZZ2FLT2FTF3ANCNFSM5BGSB56A
.

Hello, on produce i have a problem the event doesn’t trigger
`socket.emitWithAck('createTransport', {'transType': 'tx'},
ack: (data) async {
log('createTransport ' + data.toString());
// log('createTransport error ' + err.toString());
var sendTransport = device.createSendTransportFromMap(
data['params'],
producerCallback: _producerCallBack);
sendTransport.on('connectionstatechange', (state) {
switch (state) {
case 'connecting':
log('connecting');
break;
                  case 'connected':
                    //localVideo.srcObject = stream
                    log('connected');
                    break;

                  case 'failed':
                    sendTransport.close();
                    break;

                  default:
                    log('default');
                    break;
                }
              });
              sendTransport.on('connect', (data2) {
                log('sendTransport connect');
                DtlsParameters parameters = data2['dtlsParameters'];
                log('dtlsParameters ' +
                    // data['params']['dtlsParameters'].toString()
                    parameters.toMap().toString());
                socket.emitWithAck('connectTransport', {
                  'transType': 'tx', // tx or rx
                  'dtlsParameters': parameters.toMap(),
                }, ack: (data) {
                  log('connectTransport ' + data.toString());
                });
              });
              var stream = await navigator.mediaDevices
                  .getUserMedia({'video': true});
              var videoTrack = stream.getVideoTracks()[0];
              RtpCodecCapability codec = device.rtpCapabilities.codecs
                  .firstWhere(
                      (RtpCodecCapability c) =>
                          c.mimeType.toLowerCase() == 'video/vp9',
                      orElse: () =>
                          throw 'desired vp9 codec+configuration is not supported');

              try {
                sendTransport.on('produce', () {
                  log('-----------produce-----------');
                });
                sendTransport.produce(
                  track: videoTrack,
                  codecOptions: ProducerCodecOptions(
                    videoGoogleStartBitrate: 1000,
                  ),
                  encodings: [
                    RtpEncodingParameters(scalabilityMode: 'S3T3_KEY'),
                  ],
                  stream: stream,
                  codec: codec,
                );
              } catch (e) {
                await stream.dispose();
              } finally {
                await stream.dispose();
                // sendTransport.close();
              }
            });`

What event? Create transport?
вс, 1 авг. 2021 г., 17:40 salahkamal @.***>:

Hello, on produce i have a problem the event doesn’t trigger
`socket.emitWithAck('createTransport', {'transType': 'tx'},
ack: (data) async {
log('createTransport ' + data.toString());
// log('createTransport error ' + err.toString());
var sendTransport = device.createSendTransportFromMap(
data['params'],
producerCallback: _producerCallBack);
sendTransport.on('connectionstatechange', (state) {
switch (state) {
case 'connecting':
log('connecting');
break;
              case 'connected':

                //localVideo.srcObject = stream

                log('connected');

                break;

              case 'failed':

                sendTransport.close();

                break;

              default:

                log('default');

                break;

            }

          });

          sendTransport.on('connect', (data2) {

            log('sendTransport connect');

            DtlsParameters parameters = data2['dtlsParameters'];

            log('dtlsParameters ' +

                // data['params']['dtlsParameters'].toString()

                parameters.toMap().toString());

            socket.emitWithAck('connectTransport', {

              'transType': 'tx', // tx or rx

              'dtlsParameters': parameters.toMap(),

            }, ack: (data) {

              log('connectTransport ' + data.toString());

            });

          });

          var stream = await navigator.mediaDevices

              .getUserMedia({'video': true});

          var videoTrack = stream.getVideoTracks()[0];

          RtpCodecCapability codec = device.rtpCapabilities.codecs

              .firstWhere(

                  (RtpCodecCapability c) =>

                      c.mimeType.toLowerCase() == 'video/vp9',

                  orElse: () =>

                      throw 'desired vp9 codec+configuration is not supported');

          try {

            sendTransport.on('produce', () {

              log('-----------produce-----------');

            });

            sendTransport.produce(

              track: videoTrack,

              codecOptions: ProducerCodecOptions(

                videoGoogleStartBitrate: 1000,

              ),

              encodings: [

                RtpEncodingParameters(scalabilityMode: 'S3T3_KEY'),

              ],

              stream: stream,

              codec: codec,

            );

          } catch (e) {

            await stream.dispose();

          } finally {

            await stream.dispose();

            // sendTransport.close();

          }

        });`

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Blancduman/mediasoup-client-flutter/issues/18#issuecomment-890532237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVXEO24QQ7MJM5A5T3IOK3T2VMGFANCNFSM5BGSB56A
.

No, that event => Transport.on('produce', (data){});

also as its described Transport.produce() used to create a Producer by using producer callback to receive a new Producer.
but when I produce the callback doesn’t execute and I don’t know why ??!

@salahkamal
Maybe:

socket.emitWithAck('connectTransport', ... - you do not passing transport Id; and also you not using data2[callback] after that emit;
Same with sendTransport.on('produce', ... - use callback;

Let me know did this solves your problem

Thank you 🙏
It’s working now.

@salahkamal 👍

Hello again, Congratulations for the new releasing you made such a great work.
I have a question  can i disable WebRTC logs?

Hi. Thanks.
Right now - no.
Disable it for debug?
вт, 10 авг. 2021 г., 14:19 salahkamal @.***>:

Hello again, Congratulations for the new releasing you made such a great
work.
I have a question can i disable WebRTC logs?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Blancduman/mediasoup-client-flutter/issues/18#issuecomment-895945893,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVXEO7ZEFOAX5VIJNOAAFTT4EDMBANCNFSM5BGSB56A
.


Extension inserts null bytes at end of meson.build file after saving

Type: Bug
I have the following simple meson.build file for a test C project. With the meson VS Code extension enabled, anytime I modify this file and save it, a handful (around 9) of null bytes are inserted at the end, causing the language server to crash and meson itself to fail to lex the file. I'm pretty new to meson so if my build file is malformed in anyway (besides the null bytes I didn't ask for), that's on me :)
Edit: If it's worth mentioning, I do have format-on-save enabled globally in VS Code, and I used the extension bisect feature to narrow it down to the Meson extension.
Edit 2: I just confirmed that it's happening when I format the document manually from the command pallet as well. So probably something to do with the language server's formatting functionality?
project('crac', 'c', default_options: 'default_library=static')
incdir = include_directories('include')
deps = []
executable(
  'crac',
  'main.c',
  include_directories: incdir,
  dependencies: deps,
)

Extension version: 1.25.1
VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 9 5900X 12-Core Processor             (24 x 3700)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.92GB (21.31GB free)

Process Argv
--crash-reporter-id 54a44d29-4e67-454a-891a-d029558f2d94

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelc:31048052
dsvsc021:30996838
g316j359:31013175
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
impr_priority:31094925
refactorc:31093864
0c838689:31092287

I'm seeing the same issue here on Windows 10 Pro. Here's the steps to reproduce:

Open the project in the dir https://github.com/scott-wilson/openchecks/tree/8de1028178863dc4ba0ea7c24ecb259efcbf28ca/bindings/cpp
Open the root meson.build and format (I'm doing format on save)

This should cause the error to happen.

Thanks @JCWasmx86 for investigating. I only work on Linux, so can't test.

Saw the same issue, and have been for a month or so. Had to disable the meson extension because of it. Save without formatting also works, but that's a bit of a hassle. It happens every time I save any meson.build file, I end up with NUL chars inserted in my text.

Windows 11 Home
VSCode v. 1.90.1
Meson extension v. 1.25.1

Yes, outside of the trailing NULs at the end of the file, the formatted meson.build seems to be valid.
Also, the patched build has fixed the issue for me!

Also, if it helps at all, the NULs only appear when the file is actually formatted, as in, a modification is made first (inserting or removing a newline, for instance).


Add Wildfly as a MicroProfile runtime for Starter

Please add Wildfly to the list of "MicroProfile servers". Wildfly is "in progress" under the MicroProfile implementations page:
https://wiki.eclipse.org/MicroProfile/Implementation
Thank you,
Stefano

Hello @maeste,
I will take a look. Similarly as with #195 , the runtime pull request can be eventually merged as soon as the runtime passes TCK and is marked "Passed TCK" on Implementation wiki.
@cealsair Would you add Wildfly as "In Progress" to the wiki, please?

@Karm note Wildfly is "In Progress" on Microprofile 3.1 I see only 3.0 as latest in the wiki.

Shouldn't we add JBoss EAP in the table too?
On Mon, Oct 14, 2019 at 12:14 PM Stefano Maestri<EMAIL_ADDRESS>wrote:

@Karm https://github.com/Karm note Wildfly is "In Progress" on
Microprofile 3.1 I see only 3.0 as latest in the wiki.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eclipse/microprofile-starter/issues/233?email_source=notifications&email_token=AGB2SAWYV3OHQU67ECHZDETQOSLH3A5CNFSM4JAPPFQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBFM3EQ#issuecomment-541773202,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGB2SASPG2GFA2W73CRV35LQOSLH3ANCNFSM4JAPPFQQ
.

--
Cesar Saavedra
Senior Principal Technical Product Marketing Manager
<EMAIL_ADDRESS>(407) 492-9801


[bugfix] Solana: display spinner in staking workflows

📝 Description
Display spinner inside "continue" button in solana staking workflows (Delegate/Activate/Deactivate modals).

❓ Context

JIRA or GitHub link: https://ledgerhq.atlassian.net/browse/LIVE-10980

✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[x] npx changeset was attached.
[ ] Covered by automatic tests.
[x] Impact of the changes:

"Continue" button in Solana "Delegate/Activate/Deactivate" staking modals should now display correct loading Spinner

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

Looks good 👍 thanks
Just in case, isn't the same fix relevant for the following flows too:

DelegationReactivateFlowModal
DelegationWithdrawFlowModal

?

Hey @haammar-ledger
Sorry for delayed reply and thanks for review! You are correct.
I updated PR, here is the fix for DelegationReactivateFlowModal  and DelegationWithdrawFlowModal modals:  https://github.com/LedgerHQ/ledger-live/pull/6036/commits/a938cb68f18b112e2caa477500cf3b5594552e02


App language list

Discussed in https://github.com/johnSamilin/rosplata/discussions/35

Originally posted by johnSamilin March 27, 2023
Hi everyone!
Help us decide which languages should present in languages list! If you are able to help with translation please let us know.

@Sumit-Mundhe join the discussion!

I'm also thinking about arabic and Hebrew, because those languages are being used undeservedly rare

Yes, you can consider Arabic too.

Consider Hindi Also , India is a pretty large region where you could have a big userbase. I can help with the translations.

That would be just great! I this I'll even set higher priority to this task (adding internationalization)

As South Asian Countries are diversified by languages , I can help with Bengali which also has large user base .

Wonderful! @Gaurang-Ruikar I would appreciate your help!

Hey guys,
good news everyone!
I published a branch with translations (https://github.com/johnSamilin/rosplata/tree/feature/translations), and would be so grateful if you update corresponding files:
https://github.com/johnSamilin/rosplata/blob/feature/translations/translations/hi.json is for Hindi
https://github.com/johnSamilin/rosplata/blob/feature/translations/translations/bn.json is for Bengali
Each json file is a collection of messages. You just need to edit "value" prop for each message. There's also "defaultValue" prop, which holds the original (english) message just for reference.
Feel free to open PRs to the branch feature/translations!

I can help for Marathi language.

I can help for Marathi language.

Great! I pushed new language file, https://github.com/johnSamilin/rosplata/blob/feature/translations/translations/mr.json
please see https://github.com/johnSamilin/rosplata/wiki/Translations#how-translation-files-are-organized for details

Great news everyone!
I merged some new locales: Arabic, Bengal, Hindi, Hebrew, Korean, Chinese and Russian!
See details in telegram channel and in this article.
I'm closing this issue but there's link to discussion in the first message.
Thanks everyone


FastNLPProcessor annotatation is not stable

See also https://github.com/clulab/eidos/issues/861.  A different answer is computed from the same document.  This is now a unit test in https://github.com/clulab/processors/blob/kwalcock-envBug/corenlp/src/test/scala/org/clulab/processors/TestFastNLPProcessorEnv.scala.  Moving it from Eidos to Processors gets me a little closer to the cause and helps with debugging.

Can you please paste an example of differences here?

 Maybe it should be filed in the Stanford CoreNLP github?

That was almost my conclusion.  I'd like to make sure that we are not misusing SUTime by, for instance, not calling some reset method between documents.  I haven't yet found the line that makes the change that needs to be undone, though.  I'll check what remedies Stanford might offer.

Good point. Thanks!

The problem does seem to be with SUTime and I will file an issue there shortly.  This here is for practice.
The rules for dealing with time are encoded in src/edu/stanford/nlp/time/rules/english.sutime.txt.  The rules
  ENV.defaults["stage"] = 4
  ...
  {  pattern: ( [ { tag:/VBD/ } | /have/ ] []{0,2} [ $hasTemporal ] ),
     action: VTag( $0[-1].temporal.value, "resolveTo", RESOLVE_TO_PAST )
  }
  {  pattern: ( [ $hasTemporal ] []{0,2} [ { tag:/VBD/ } | /have/ ] ),
     action: VTag( $0[0].temporal.value, "resolveTo", RESOLVE_TO_PAST )
  }
  {  pattern: ( (/would/ | /could/ | /should/ | /will/ | /going/ /to/ | /'/ /ll/ | /'ll/ )
                []{0,2} [ $hasTemporal ]
              ),
     action: VTag( $0[-1].temporal.value, "resolveTo", RESOLVE_TO_FUTURE )
  }
  {  pattern: ( [ $hasTemporal ] []{0,2}
                (/would/ | /could/ | /should/ | /will/ | /going/ /to/ | /'/ /ll/ | /'ll/ ) ),
     action: VTag( $0[0].temporal.value, "resolveTo", RESOLVE_TO_FUTURE )
  }

arrange for a value tag (VTag) to be added to the environment.  The tag's key is "resolveTo" and the value will depend on the matching pattern.  This ends up happening in ValueFunctions.java where I can observe the change take place.  The problem is that the environment influences other operations, the whole point of it, but that it cannot easily be reset.  The first document is annotated without a resolveTo tag and SUTime acts in one way.  The second document is annotated with a side effect of the resolveTo tag being added.  The first document gets read again, but the side effect influences behavior and a different result gets produced.  I see no support anywhere for restoring the environment to its initial condition between documents short of doing something like throwing everything away and starting with a new object, which would be very expensive on a per document basis.
Opinions to the contrary are very welcome.

Nice catch!
I think you're correct.

Other related code is GenericTimeExpressionPatterns.java.determineRelFlags:
  public int determineRelFlags(CoreMap annotation, TimeExpression te)
  {
    int flags = 0;
    boolean flagsSet = false;
    if (te.value.getTags() != null) {
      Value v = te.value.getTags().getTag("resolveTo");
      if (v != null && v.get() instanceof Number) {
        flags = ((Number) v.get()).intValue();
        flagsSet = true;
      }
    }
    if (!flagsSet) {
      if (te.getTemporal() instanceof SUTime.PartialTime) {
        flags = SUTime.RESOLVE_TO_CLOSEST;
      }
    }
    return flags;
  }
}

and SUTime.PartialTime.resolve().  I'll reference them as well.

Submitted as https://github.com/stanfordnlp/CoreNLP/issues/1061...

We just recently read 40,000 documents twice and the same phenomenon was observed.  The reading changes.

It's the exact same as before, which shouldn't be surprising.  The week wanders around, and we have lots and lots of examples.  It wasn't somehow a temporary problem.  The repeatability consequence is troubling.  Aside from results reported in papers, Eidos with a given version is supposed to report the same results downstream for the same document.


[PR] increase QGIS version from 3.10.1. to 3.10.2

Checklist

[x ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

This PR increased the QGIS version from 3.10.1. to 3.10.2

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Add some testable (godoc) examples to 0-Disk packages

A golang feature we haven't made use of yet, is testable examples. It allows us to write examples which will be available in the godoc documentation for the relevant package, while the go test tool ensures those examples are actually valid.
More information: https://blog.golang.org/examples
Packages where we should add such examples:

[x] github.com/zero-os/0-Disk

how to create a new hash, how to create a hash from bytes, how would you use the Hash methods afterwards;
how to create and use a hasher;
how to create and use a keyed hasher;

[x] ~github.com/zero-os/0-Disk/log~

~how to create a logger and how to use it;~
~how to use and configure the global logger;~
~how to broadcast errors;~

[x] github.com/zero-os/0-Disk/nbd/ardb/storage

how to create a storage for a given vdisk;
how to use a (block)storage;

Replaced by individual issues #544  and #545.


Turnstile cover prevents link from loading

Page loads and redirects to https://my domain.com/validate-captcha/user-id and shows a blank page. But without the turnstile it loads page correctly. Please what’s the fix Thanks

[18:19:22] [err] failed to add clicked link event to database: record not found (Also shows this in the terminal when link is clicked )


Enhancement Add more error msgs for wrong data types in orc and parquet reader.

Proposed changes
Enhancement Add more error msgs for wrong data types in orc and parquet reader.

run buildall


The suggestion is so weird

@ramya-rao-a
Issue Type: Bug
Set
"emmet.includeLanguages": {
        "javascript": "javascriptreact"
 }

If there is !, there is a wrong item in the suggestions.

VS Code version: Code 1.22.1 (950b8b0d37a9b7061b6f0d291837ccc4015f5ecd, 2018-04-06T02:26:57.615Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz (4 x 2304)

Memory (System)
7.89GB (2.14GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

vscode-eslint
dba
1.4.8

EditorConfig
Edi
0.12.1

tslint
eg2
1.0.28

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

svn-scm
joh
1.29.0

debugger-for-chrome
msj
4.3.0

vscode-icons
rob
7.22.0

Good catch, thanks for reporting. Will push a fix soon

What's this?

You can get the fix in tomorrow's Insiders build


[java-sdk] Create Dapr's HTTP Client

NEW SCOPE:
Manually create http client for Dapr's APIs.
OLD SCOPE:

Auto-generate http client from Dapr's OpenAPI definition (https://swagger.io/specification/)
If needed, create OpenAPI definition in Dapr/dapr to seed auto-generation for any language.

Linking to https://github.com/dapr/dapr/issues/16
For now, we can handcraft the http calls as we have few http calls. Autogenerated ones will need to be wrapped.

It seems that we don't have the OpenAPI specs ready to complete this task.

I have changed the scope of this task to not use the auto-generated version since we don't have service API specs for that yet. It can be simply be manually created right now.

Can you assign me please?


📚  update T1K docs

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Part of https://github.com/d3b-center/bixu-tracker/issues/2332
Type of change
Please delete options that are not relevant.

[x] documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Just docs

Test Configuration:

Environment:
Test files:

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings
[ ] I have committed any related changes to the PR

@dmiller15 found a couple more requests for added info here: https://github.com/d3b-center/bixu-tracker/issues/2332#issuecomment-2032994819


Docs

Added documentation for user and developers. It inherits the documentation structure of odin.

@ajgosl Is the link not available on the right side in the about section? I'll just add it to the read me anyway but I'm sure I added to the about section.

Yes sorry I had missed it there.  It might be nice to just add it to the README in the first paragraph somewhere as well.


Makefile

This change adds a Makefile and bindings to more easily build static/dynamic libraries for use in C-based languages. The implementation is intended to be as generic as possible, to make for easier adoption and diffing.
This comes from discussion in the main tree-sitter repo https://github.com/tree-sitter/tree-sitter/issues/1488.

Hey @mattmassicotte! Building locally I get:
cc  -shared -Wl,-lc++-soname,libtree-sitter-elixir.so.0 src/parser.o src/scanner.o  -o libtree-sitter-elixir.so.0.0
/usr/bin/ld: cannot find -lc++-soname
/usr/bin/ld: cannot find libtree-sitter-elixir.so.0: No such file or directory
collect2: error: ld returned 1 exit status
make: *** [Makefile:81: libtree-sitter-elixir.so.0.0] Error 1

I assume that's because I'm missing clang, but in a fresh ubuntu20 docker image I did apt install build-essential clang libc++-dev libc++abi-dev and sill could build. Did you successfully built on linux?

It does build correctly with clang now, thanks! FTR here's how I tested it:
docker run -it --rm ubuntu:20.04

then
apt update
apt install git build-essential clang libc++-dev libc++abi-dev
git clone https://github.com/mattmassicotte/tree-sitter-elixir.git
cd tree-sitter-elixir
make

Also, we are not gitignoring the generated .so files, because they have the version suffix. Let's add libtree-sitter-elixir.so*?

Thanks @mattmassicotte!


allow optional use of a filter based on its existence

Resolves #842
Summary:

Undefined filters nested in if/elif/else statements will cause an error only if executed during runtime
Filters can be used in tests like variables

Files changed:

nodes.py
compiler.py
runtime.py

Are we covering cases like {{ 'foo'|nosuchfilter if false else 'bar' }} and {{ 'foo' if true else 'bar'|nosuchfilter }} - neither should raise (since the filter is not actually used, but based on the code it looks like it may raise..

Are we covering cases like {{ 'foo'|nosuchfilter if false else 'bar' }} and {{ 'foo' if true else 'bar'|nosuchfilter }} - neither should raise (since the filter is not actually used, but based on the code it looks like it may raise..

Right, I forgot to account for those but probably should (and will) too.

I have the feeling any block-level check is likely to have problematic edge cases - can't we just let it fail when actually accessing the filter?

I have the feeling any block-level check is likely to have problematic edge cases - can't we just let it fail when actually accessing the filter?

Hmm that's true. The error won't be as helpful though: TypeError: 'NoneType' object is not callable

Good point, that error is awful and filters that are sometimes but not always undefined are very much an edge case for which we probably shouldn't sacrifice error verboseness with other, more common, cases

Could we compile filters to something like this at the beginning of the template?
try:
    filter_tmp_0 = self.filters['filter_name']
except KeyError:
    @internalcode
    def filter_tmp_0(*unused):
        raise TemplateRuntimeError("no filter named 'filter_name'")

Then the code where the  filter is actually used just uses filter_tmp_0 which will either call the filter or raise an exception - without adding extra runtime overhead every time the filter is actually invoked.

Ooh that's a good idea! I moved it to pull_dependencies in the new commit. Let me know if I misunderstood. Will address conditional expressions next.

I'm working on a separate PR to create an if 'name' is filter test.


How to dowland it pls help

How I can dowland this mod ?

oh man i am not good with computer plz to halp

Yes me too

h

what h ?

he

Ok ?
but can someone help me

PLease can someone help me

You will have to build it yourself, or if you want I can send you the mod when I am home because I have it built already

cameradetach-1.0.0.zip
This is the built jar file if you don't know how to build it.


Dogo trying to censor sentences that has no badwords

Describe the bug
Sometimes Dogo censors random messages that has no badwords
To Reproduce
Steps to reproduce the behavior:

I don't know :c

Expected behavior
Nothing should happens.
Screenshots
https://i.imgur.com/K1Cvu5E.png

Additional context
That guild had no badwords

closed in c9582d9e5ccad2d290c9a8bb7b58096a468958c6


Login text not visible

The content of the Login card is not properly visible

Assigned!
Make sure to attach before & after screenshots in your PR and include the issue number.
Also, please star the repo before working on it.
i am the project mentor you can reach out to me for any help!
Happy open-source contributing! 🎉


how to create a foreground service for real-time tracking

It seems a background service for tracing in real time shall not be working if SDK version >26(Android8.0), here comes up a article and codes of Android Studio on creating a foreground service claim that it work, I'm not faimilar with native android codes, and no idea on how to create a foreground service in NativeScript, could somebody help to release a demo? @elena-p
Ref1: https://hackernoon.com/android-location-tracking-with-a-service-80940218f561
Ref2: https://bitbucket.org/tiitha/backgroundserviceexample/branches/

Thanks to @jnorkus's issue, a foreground service example in NativeScript could be found here and downloaded for reference.
https://github.com/NativeScript/NativeScript/issues/6994
https://github.com/NativeScript/NativeScript/files/2940493/ns-test-android.zip

Hi, currently I'm getting a
 ERROR Error: java.lang.Exception: Failed resolving method startForegroundService on class android.content.ContextWrapper

When trying to run it on a emulator. Do you know how to solve it?


feat: upgrade deps and add react compiler rules

Developer Checklist (Definition of Done)
Issue

[x] All acceptance criteria from the issue are met
[x] Tested in latest Chrome/Firefox

UI/UX/Vis

[ ] Requires UI/UX/Vis review

[ ] Reviewer(s) are notified (tag assignees)
[ ] Review has occurred (link to notes)
[ ] Feedback is included in this PR
[ ] Reviewer(s) approve of concept and design

Code

[ ] Branch is up-to-date with the branch to be merged with, i.e., develop
[ ] Code is cleaned up and formatted
[ ] Unit tests are written (frontend/backend if applicable)
[ ] Integration tests are written (if applicable)

PR

[ ] Descriptive title for this pull request is provided (will be used for release notes later)
[ ] Reviewer and assignees are defined
[ ] Add type label (e.g., bug, feature) to this pull request
[ ] Add release label (e.g., release: minor) to this PR following semver
[ ] The PR is connected to the corresponding issue (via Closes #...)
[ ] Summary of changes is written

Summary of changes

Bumps versions
Adds https://www.npmjs.com/package/eslint-plugin-react-compiler
Includes https://github.com/datavisyn/visyn_scripts/pull/77

Screenshots
Additional notes for the reviewer(s)

Thanks for creating this pull request 🤗

Closed in favor of https://github.com/datavisyn/visyn_scripts/pull/77


add prettier

would you accept a PR to include prettier in this project?

Prettier is in this project since the first commit 😄
https://github.com/19majkel94/type-graphql/blob/06189043959cb99ae67ca94f3ed4bb1fbf4def4a/package.json#L19
There's no git hook because prettier has some issue with formatting decorators:
https://github.com/prettier/prettier/issues/2613
But I constantly format the code with prettier using VSCode on development, so it's not a big deal when I'm the only contributor 😉

oh I assumed it's not here because there is no .prettierrc file, maybe it would be good to add it?

It is also available from the first commit 😆
https://github.com/19majkel94/type-graphql/blob/06189043959cb99ae67ca94f3ed4bb1fbf4def4a/.prettierrc

sorry, my bad, can't believe I missed it


Gutter prop, opposed to manually passing padding/ margins

Hello,
I'm really loving your grid so thanks for building it. I was wondering what your thoughts were on a 'gutter' parameter to figure out padding and negative margins for you?
I've been doing it with a scss grid I made a while ago and have never had any problems with it. By default gutters are added to the inside spaces only with an option to add the same gutter size around the border of the grid.

This is how I imagine it
import styled from 'styled-components'
import {
  space,
  color,
  width,
  fontSize,
  flexWrap,
  flexDirection,
  alignItems,
  justifyContent,
  flex,
  order,
  alignSelf,
  themeGet
} from 'styled-system'

export const Box = styled('div')({
  boxSizing: 'border-box'
},
  space,
  color,
  width,
  fontSize,
  flex,
  order,
  alignSelf,
  props => props.css,
  props => {
    if (props.gutter) {
      return {
        padding: `${parseInt(props.theme.space[props.gutter], 10) / 2}px`
      }
    }
  }
)

Box.displayName = 'Box'

Box.propTypes = {
  ...space.propTypes,
  ...color.propTypes,
  ...width.propTypes,
  ...fontSize.propTypes,
}

const FlexWrapper = styled(Box)({
  display: 'flex'
},
  flexWrap,
  flexDirection,
  alignItems,
  justifyContent,
  props => {
    if (props.gutter) {
      return {
        margin: `${(parseInt(props.theme.space[props.gutter], 10) / 2) * -1}px;`,
        padding: 0
      }
    }
  }
)

FlexWrapper.displayName = 'Flex'

FlexWrapper.propTypes = {
  ...flexWrap.propTypes,
  ...flexDirection.propTypes,
  ...alignItems.propTypes,
  ...justifyContent.propTypes
}

export const Flex = class extends React.Component {
  renderChildren = () => {
    const { children } = this.props
    return React.Children
      .map(children, (child) => React.cloneElement(child, {
      gutter: this.props.gutter
    }))
  }

  render() {
    return <FlexWrapper {...this.props}>
      {this.renderChildren()}
    </FlexWrapper>
  }
}

<Flex flexWrap='wrap' gutter={1}>
  <Box width={1/2}>
    <Area />
  </Box>
  <Box width={1/2}>
    <Area />
  </Box>
</Flex>

@pea there's a horizontal scroll bar that appears when the columns go edge to edge with the border, is there a way to fix that other than using overflow-x: hidden?

I'd recommend making a wrapper around the Flex component that handles this sort of thing by applying props to its direct children. This library is meant to be lower-level and only directly affect styles of the components themselves


Add Spanish and Swedish translations

Thank you, Ismael!

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/416/
Hooray Jenkins reported success with all tests good!

Thanks indeed, yay more translations!
And aiiee we are officially overflowing the poor language drop-down (#2134). I have to actually make the window larger now to see the new Swedish :-)
I tweaked the meta-language fields again (just had "English" translated again) and updated the weblate branch as we..


Add tests

Two major considerations for implementing tests: framework choice and test data implementation
for frameworks, two major players are the rails built-in framework minitest or the ruby testing tool rspec
for test data, two major considerations are using fixtures vs factories (see Factory_bot or fabrication gems)

Added in #125


all 5 detections should be perfect

Fixed the multi stage issue per team feedback.  5 rules modified.  Passes validation.

I think this is related to the multi-stage scenario for a single detection.  I changed it from multiple comma separated values in a single "stage=" to multiple comma separate "stage=" assignments.  I will change it and retest.

Started a new branch from scratch.  I think this is a build problem; not a content problem.


Missing PO Entry when using String Concatenation (+) or Referencing Text defined in const/Field/Property/Variable

Repro Cases
String Concatenation +
S["Hey there " +
   "how do you like this?" +
   "I know it's not recommended"];

String Reference (Field/Property...)
const string MyMessage = "This is my message";

....

S[MyMessage];

Actual Behavior
extractpo runs successfully, but the generated *.po file does not contain any entries for these calls.
Expected (Desired) Behavior
Either one of the following would be fine for me:

not support these and communicating it when hitting such a case:

crash the app with error message indicating the problem
exit the app with an error code, and write to

support these so that Hey there how do you like this? I know it's not recommended / This is my message turns up in the PO file, respectively.

note that the case of referencing an item would require either

a) using the S[...] line as context
b) or the one of the field/property, but then would require duplicate detection, because the same field/property might be referenced twice!

Note: for the string +-concatenation I would prefer if it would be supported. The reason is, that this is the only supported way how to break a long single-line string into multiple source code lines. All other approaches introduce new lines.
Also note, that the +-concatenation is compiler optimized so that the compilation actually contains a single string -> in the compiled assembly there is no difference between "a" + "b" and "ab"! Something I've learned today :D

I have reproduced this with the current version on develop - the behavior is the same as the latest release 1.0.1 = the issue still exists.

I will try to reproduce it

@BrunoJuchli sorry for the delay on this, could you please write a unit test for each and push a PR for fixing those?

@hishamco
Thanks for getting back to me.
Unfortunately I don't have enough time at the moment to look into this further.
We're still in the decision phase for how we're dealing with translations - if we do actually decide to use this tool I'll probably come back to it.
I'm fine with you closing the issue, if you want to.

We're still in the decision phase for how we're dealing with translations - if we do actually decide to use this tool I'll probably come back to it.

Please let me know if you need any support on the tool, it's my pleasure that the tool is already used by OC and hopefully other projects

It would be really nice if you could release a new version, though. Since this would fix a few of the issues we experience with the tool, it would go a long way to convince the team.

Ya I will do ASAP

I've figured out the code to extract the string from a string literal concatenation expression like:
["foo" + "bar" + "licious"]

here's the code:
public static bool IsStringLiteralExpression(
        ExpressionSyntax expression,
        [NotNullWhen(true)] out string? stringLiteralExpression)
    {
        if(GetLiteralExpressionValue(expression) is { } s)
        {
            stringLiteralExpression = s;
            return true;
        }

        string concatenatedRights = string.Empty;
        while(expression is BinaryExpressionSyntax binaryExpressionSyntax)
        {
            if (GetLiteralExpressionValue(binaryExpressionSyntax.Right) is not { } right)
            {
                break;
            }

            concatenatedRights = right + concatenatedRights;

            if (GetLiteralExpressionValue(binaryExpressionSyntax.Left) is { } left)
            {
                stringLiteralExpression = left + concatenatedRights;
                return true;
            }

            expression = binaryExpressionSyntax.Left;
        }

        stringLiteralExpression = null;
        return false;
    }

    static string? GetLiteralExpressionValue(
        ExpressionSyntax expression)
    {
        if(expression is LiteralExpressionSyntax literal &&
           literal.IsKind(SyntaxKind.StringLiteralExpression))
        {
            return literal.Token.ValueText;
        }

        return null;
    }

I've tested this with 2, 5 and 6 concatenations.
I'm not planning on creating a PR since we're not going to use POExtractor after all.
I'm writing our own tool, extracting to JSON (and using type detection instead detecting by variable name, and so far it works good, it's just a bit slower).

I'm writing our own tool, extracting to JSON (and using type detection instead detecting by variable name, and so far it works good, it's just a bit slower).

As I said before you can skip the limitation of the variable names, check #92

I'm writing our own tool, extracting to JSON (and using type detection instead detecting by variable name, and so far it works good, it's just a bit slower).

As I said before you can skip the limitation of the variable names, check #92

yes, thanks, but as I said before, I don't like it - because it actually doesn't eliminate the limitation, it just broadens the list of possible values.
And again, if you ever write an analyzer for this, you can only analyze it if you check the types, not just the name, and you just end up with an unnecessarily complicated solution:
checking names and types - where checking the types would suffice.
Also, my solution respects the <T> parameter, another considerable advantage - in my opinion. And again something you can only achieve by dealing with types.
Of course there's two downsides to my solution as well:

only works when the solution can be compiled
takes longer

In my environment I anticipate these downsides as having minimal impact.

Feel free to close the issues I've reported.


How preproccess the image when use the pretrained model?

Could you please tell me how to preproccess the image when use the pretrained SE-ResNet50 model? I use the preproccessing as showed below, but get wrong classify output.
Compose([
Resize((244,244)),
ToTensor(),
Normalize([.485, .456, .406], [.229, .224, .225]),
])

I think just following the evaluation phase is fine.


adds core-infra-lb-service combined example

Description

For scenarios when you want to deploy a service into an empty account. This example provides a single terraform module to deploy a network, cluster, ALB, and service.
Motivation and Context

This is another example.  See above.
How Has This Been Tested?

[x] I have tested and validated these changes using one or more of the provided examples/* projects
[x] I have executed pre-commit run -a on my pull request

hello @jritsema This is Joooyoung. Firstly, thank you for your contribution to the ECS Blueprints.
Upon reviewing the code, I've noticed that the template you have provided combines both the core infra and frontend. This appears to yield the same outcome as provisioning our existing core infra and frontend templates separately.
We are hesitant to merge this into the main branch as we strive to ensure each template captures different scenarios without overlapping with others.
If there's something I might have misunderstood, please let me know. Thanks


@Html.CheckBoxFor MVC not showing well in card view

I am trying to put the checkboxfor in the card view for the boolean values in my model but it is not showing up in the view. I tried overriding -webkit-appearance to None and also a few other things but it just doesnt seem to work.
Here is my code
`    public class License
{
[Key]
public Guid LicenseId { get; set; }
    [Required]
    public string LicenseKey { get; set; }

    [DataType(DataType.DateTime)]
    public DateTime? FirstInstalledOn { get; set; }

    [DataType(DataType.DateTime)]
    public DateTime? LastInstalledOn { get; set; }

    public bool IsDEMO { get; set; }

    [ForeignKey("Product")]
    public Guid ProductId { get; set; }
    public virtual Product Product { get; set; }

}`
I have attached my view page

Rendered View is like this:-

I tried all this but it still doesn't shows the check box for strongly typed views. Although a normal input tag shows up well.
I am new to front-end development so please pardon me for my noobie skills

Hi there, I've same the same problem with you, but I'm using Web Forms, maybe this article can help : https://github.com/Dogfalo/materialize/issues/2463

Thanks Bro. But I fixed that way before. I don't really remember how but I do remember that it was fixed not by fiddling with id but something different than that. Anyway, thanks for your response. :)


TeachingTips in page can cause memory leaks

Describe the bug
When create a TeachingTips in ResourceDictionary and navigate to another page, the old page will not be released by GC.
Steps to reproduce the bug

Steps to reproduce the behavior:

Create PageA include TeachingTips Sample: https://docs.microsoft.com/zh-cn/windows/uwp/design/controls-and-patterns/dialogs-and-flyouts/teaching-tip#create-a-teaching-tip.
Then navigate to PageB, and back to PageA, repeat this action.
Open the diagnostic tool window and take a memory snapshot. We will see multiple PageA when we search "PageA" in this snapshot. Every PageA were holding in memory by TeachingTips.

Expected behavior
In the diagnostic tool, we should not see multiple PageA.
Version Info
NuGet package version:
Microsoft.UI.Xaml 2.4.2

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

May 2020 Update (19041)
Yes

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

The memory gets released properly if you don’t put the TeachingTips in the ResourceDictionary like this:
<Button x:Name="SaveButton" Content="Save" />
<muxc:TeachingTip x:Name="AutoSaveTip"
            Target="{x:Bind SaveButton}"
            Title="Save automatically"
            Subtitle="When you save your file to OneDrive, we save your changes as you go - so you never have to.">
</muxc:TeachingTip>

@cnbluefire does the repro require that the teaching tip be open when you navigate away? Or only that it have ever been opened (and then closed)? Or does the open/close status not matter at all?

@cnbluefire does the repro require that the teaching tip be open when you navigate away? Or only that it have ever been opened (and then closed)? Or does the open/close status not matter at all?

Sometimes it leaks when the tip has been opened, you should navigate to another page and go back multiple times.


e2e: Secrets validation and deletion using UI

Fixes

https://issues.redhat.com/browse/HAC-4885
Description

Add Secrets validation and deletion from UI by navigating to secrets Page in Advance flow.
remove the secrets validation through API in advance flow.
Type of change

[ ] Feature
[ ] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[x] Other (please describe): Test

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[x] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

[test]

[test]

/lgtm
/approve

/retest


Use feature macro to check for support of filesystem

Rather than defaulting to std::experimental::filesystem in files.h a feature
macro can be used to determine what stdfs uses.

There are some bugs in the MS implementation of std::experimental::filesystem that were fixed in std::filesystem but remain in std::experimental::filesystem so ideally std::filesystem should be preferred on Windows.
https://developercommunity.visualstudio.com/content/problem/357916/stdfilesystemcanonical-weird-output.html
https://developercommunity.visualstudio.com/content/problem/393925/stdfilesystemu8path-converts-to-ucs-2-instead-of-u.html
This should also use std::filesystem on *nix implementations if available.

My pleasure! Thanks for making the effort to get us up to date with std::filesystem with this PR @donny-dont


tr_image: do not use R_FindImageLoader with cube maps, test multifile cubemaps first (or preview may be loaded as cubemap instead)

Deep rewrite of image loading code.

do not walk .shader files in tr_image.cpp
do not use R_FindImageLoader with cube maps
only use home read for KTX with IF_HOMEPATH
load home KTX with IF_HOMEPATH before doing any lookup
do not do any other home loading
test multifile cubemaps before singlefile ones (or preview may be loaded as cubemap instead)
fix a crash when singlefile cubemap is freed because it was loaded but not created
look for cubemap file with explicit extension
add many debug logs and factorize them

Fixes #1393:

https://github.com/DaemonEngine/Daemon/issues/1393

I finally reworded the thing in a better way, including the non-cubemap code.

I added some TODO comments saying the removal of homepath reading have to be investigated later.

I noticed some functions were copying with Q_strncpyz strings received as argument before using them. I guess it's some security check in case some user-provided data is intentionally wrong. I don't know if such copy is needed but I renamed the symbols to make them more obvious.

LGTM


track positions of parsed blocks, for code folding

see: https://github.com/bsilverthorn/maccarone-vscode/pull/25


Add count-based stabilization

The count based algorithm can be enabled by using the --window-size flag. I didn't reuse the -p flag because it still would require another flag to interpret the meaning of -p flag.

This is still not fixed.. We must keep #include "inference_profiler.h" as the first include.
I think you commented on the previous commit. It is fixed in the latest commit.

Can you fix the message in inference_profiler.cc L735-L736 so that it can read correct for count_windows mode? Otherwise the change looks good to me.

@tanmayv25 The latency size can never be zero for the other mode because we won't exit the while loop until enough requests are captured. I have a check when parsing the CLIs which ensures that --measurement-request-count is greater than zero.


Remove unneeded beforeAll calls from SDK test (first-timers-only)

first-timers-only
This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.
Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.
Find more first-timers-only issues from DAV Foundation here.
Thank you for your help :heart:
What is this project?
DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.
As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.
dav-js
This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.
How you can help
In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.
Here is a good opportunity to simplify one of our tests:
In src/SDK.test.ts there is an empty function: beforeAll(() => { /**/ });
This is code that does nothing and can be deleted.

After making your changes, make sure the tests still pass by running npm run jest
Contributing to dav-js

[ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
[ ] Comment in this issue that you would like to do it.
[ ] Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
[ ] Code Code Code
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
[ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help
We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

Hi, Can I look into this?

Go ahead @sark01
Thank you 👍

Hi, I made the changes as mentioned in the task, but when I try to execute "npm run jest", I get errors.
I have attached the npm debug log for reference.
Please help.
npm-debug.log

Hi, I made the changes as mentioned in the task, but when I try to execute "npm run jest", I get errors.
I have attached the npm debug log for reference.
Please help.
npm-debug.log

@sark01 Did you execute npm run jest before making your changes as well? This will help you understand whether the tests failed because of the code you entered or is it unrelated?
I would clone the basic code again, run npm install and then npm run jest.

@TalAter, I did not execute the npm run jest before making the changes previously.

Today, I made a fresh clone of the code.

Did npm install

Then did npm run jest (prior to making any changes to the code).

After that, I made the changes as suggested in this post, then again executed npm run jest.

I found the same error messages/ test case failure's as before.

To conclude, I feel the failure of the tests are not related to whatever code I wrote/removed.

Did you get errors after running it for the first time before making your changes?

Yes, Some of the tests were failing.

Hi @TalAter,
Today I again did a clean clone of the repository again and did npm install, and then did npm run jest, the tests were passing.
So I made the necessary changes and will send in a PR as soon as I'm done with it.
Thanks.

Thank you @sark01 👍
Looks great.
I'm glad the initial problems resolved themselves. I believe it had to do with some issues one of our developers just fixed.
Thanks again 😎

Thanks, are there any newcomer issues/ low difficulty issues I can work on?

Sure. I just created #55. You want to give that a try?

Sure thing.


Using sc4s alternate destination config to forward syslog to a thirdparty SIEM do not retain the source IP after being being received by a SIEM

Was the issue replicated by support?
Yes. Case #3475996
What is the sc4s version ?
3.16.0
Which operating system (including its version) are you using for hosting SC4S?
Rhel 8
Which runtime (Docker, Podman, Docker Swarm, BYOE, MicroK8s) are you using for SC4S?
podman
Is there a pcap available? If so, would you prefer to attach it to this issue or send it to Splunk support?
Yes, will send seperately once the issue is assigned
Is the issue related to the environment of the customer or Software related issue?
Software related
Is it related to Data loss, please explain ?
Protocol? Hardware specs?
Last chance index/Fallback index?
Is the issue related to local customization?
Do we have all the default indexes created?
Describe the bug
A clear and concise description of what the bug is.
All our syslog devices are ingesting syslog to Splunk Cloud via sc4s app using HEC. No issues. All good. Also, using alternate destinations config (https://splunk.github.io/splunk-connect-for-syslog/main/destinations/#example-5-cisco-asa-send-to-a-third-party-siem), we want to forward to the third-party SIEM (QRADAR) appliance. I followed the documentation and logs are showing in qradar, but with the following issue:

The source IP is being overwritten with the sc4s server instead of the actual source IP after being received by a SIEM from sc4s.  - client IP ----> sc4s (syslog-ng) ---> SIEM (source is coming up as sc4s server instead of client IP).
looks like the syslog protocol is unable to maintain the original sender's address when forwarding syslog messages. This is because the sender's address is taken from the received TCP packet.

env_file:
SC4S_DEST_SYSLOG_QRADARSIEM_HOST=x.x.x.x
SC4S_DEST_SYSLOG_QRADARSIEM_PORT=514
SC4S_DEST_SYSLOG_QRADARSIEM_MODE=SELECT
set to #yes for ietf frames
SC4S_DEST_SYSLOG_QRADARSIEM_IETF=yes
To Reproduce
Steps to reproduce the behavior:

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

Hi @rjha-splunk any update on this? Thanks

No, it didn't work @rjha-splunk
SIEM is looking into the header info and calculating the source ip as <IP_ADDRESS> (which is the sc4s server instead of the actual host sending the packet).
As per your config, host is being changed to IP in the sample message content shown below (see <IP_ADDRESS>), but we don't want that
Sample Packet Header:
18:21:57.494911 IP (tos 0x0, ttl 64, id 61068, offset 0, flags [DF], proto TCP (6), length 159)
<IP_ADDRESS>.41025 > <IP_ADDRESS>.514: Flags [P.], cksum 0xe9fc (incorrect -> 0x470d), seq<PHONE_NUMBER>:2382849122, ack<PHONE_NUMBER>, win 58, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 107
Sample Message:
1.2024-06-24T22:21:57.494+00:<IP_ADDRESS>.98.-.6736.-.-....0].info:.start.of.service.(unbound.1.6.6)..

We need to look for a solution and possible enhancement, we will keep you posted

I investigated and checked, right now i have following for the case:

we cant make it possible for TCP, UDP we can try to implement that using spoof-source and python parsers but it will be only possible after syslog-ng 4.8.0 release

Closing this issue as per above comment, SC4S today cant spoof tcp packets intial origin source.

2. Right now using parsers Sourceip information can be added to the header.
application sc4s-lp-cisco_asa_d_syslog_test[sc4s-lp-dest-select-d_syslog_test] {
    filter {
        'cisco' eq "${fields.sc4s_vendor}" and 'asa' eq "${fields.sc4s_product}";
    };

    parser {
        syslog-parser(template("SourceIP=${SOURCEIP} ${MSG}\n"));
    };
};

was this tested? above config doesn't update the header source ip.

Yes it is tested with ASA sample, it will  just add sourceip to the message , i will share the screenshot tomorrow

Oh, adding sourceip to the message not to the header. This doesn't resolve our issue.
Can you please let us know if there are any timelines to get my issue resolved? Thanks

documentation also needs to be updated appropriately as this is not working as expected - https://splunk.github.io/splunk-connect-for-syslog/main/destinations/#example-5-cisco-asa-send-to-a-third-party-siem

Thanks @rjha-splunk

Just to confirm, splunk edge processor can be used to ingest UF/hec/sc4s based logs to splunkcloud or splunk enterprise indexes or AWS S3, but cannot ingest to any alternate destination (for e.g SIEM). Its NOT supported
https://docs.splunk.com/Documentation/SplunkCloud/9.2.2403/EdgeProcessor/ManageDestination


Added 404 page

Fixes #141
Added 404 page with well designed UI.
Please review and merge it.

Hi @skpandey885, this page will show up when :-

the page has been deleted from the website.
The page was moved to another URL and the redirection was done incorrectly.
User entered an incorrect URL address.

In this “.htaccess” file you will need to add this line:
ErrorDocument 404 /pages/404.html


The tenant registers agent to the verifier first before handling initial quote provided by the agent.

Is your an issue a feature request? If so, please raise it as an enhancement
Environment

OS / version: Ubuntu 20.04
Processor architecture:
TPM Manufacturer:
Keylime version: d632e2a

Description
The tenant registers agent to the verifier first and then it handles initial quote provided by the agent.
Expected behavior vs. actual behavior
The tenant registers agent to the verifier first and then it handles initial quote provided by the agent. This may lead to an issue that the verifier keeps asking quotes from the agent before proper attestation quote validation by the tenant. This may happen by e.g. a malicious agent, another malicious process or http request (sent to the agent by the tenant) which doesn’t timeout
Steps to reproduce problem

See the order in tenant.py#L1176

Relevant logs
Attach any relevant log files that can help to debug your issue.

I've tried switching the order of do_cv() and do_qoute() and nothing immediately broke.
On first glance I couldn't find that do_qoute() has a dependency on do_cv() other than removing the agent from the verifier if it failed.  Is there another reason why we don't just switch the order?
There would be a change in behavior.  The failed agent never gets added to the verifier and is there in a stopped state. If that is desired the order should not be changed and only the EK validation could be moved before the do_cv().

I've tried switching the order of do_cv() and do_qoute() and nothing immediately broke.

I've tried too and it should work fine.

While I am certainly willing to support such change, we would need a new enhancement proposal for this.

@igurel Hello, do you plan to propose the enhancement? I think this change makes sense (together with #679), and would like to offer help, if needed.


feat: Integrate cert-manager to manage secrets

Use cert-manager to manager secrets, so we can dynamically update certificates, such as SSL certificates.

Please assign me @tao12345666333


Update lib.rs

A PR to expose the num_traits as public, it is also the fix for https://github.com/vbarrielle/sprs/issues/205.

Thanks!


C interface to "crypto"

Could a C interface be provide (like is done for Hyperledger Ursa)?
That would make it possible to use the crypto library from other languages.

Sorry for the late reply but we don't have any plans for that.

Sure.


The latest bespoke have errors wtih bespoke-fx demo

Uncaught TypeError: Cannot set property 'keys' of undefined bespoke-keys.js:9
2014-08-24 16:08:45.340
Uncaught TypeError: Cannot set property 'loop' of undefined bespoke-loop.js:11
2014-08-24 16:08:45.342
Uncaught TypeError: Cannot set property 'fx' of undefined bespoke-fx.js:769
2014-08-24 16:08:45.343
Uncaught TypeError: undefined is not a function

Looks like this only uses globals to hook into bespoke, e.g.,
(function(bespoke, BespokeFx) {
  bespoke.plugins.fx = function(deck, options) {
     ...
  };

}(bespoke, BespokeFx));

But bespoke now officially uses modules, e.g., from the README:

Plugins are simply functions that are called when presentations are created. They are passed a deck instance which allows you to interact with the deck's state, bind events and modify its elements.
To be consistent with the suite of official Bespoke.js plugins, it is highly recommended that you implement your plugin as a function that takes configuration and returns a plugin function.
// Creating the plugin
var myPlugin = function() {
  return function() {
    deck.on('activate', function(e) {
      console.log('Activated slide ' + (e.index + 1) + ' of ' + deck.slides.length);
    });
  }
};

The plugin can now be provided in the plugins array when using the from(selector[, plugins]) method.
// Using the plugin
bespoke.from('#presentation', [
  myPlugin()
]);


What is the meaning of missing-text?

Question
When exporting docx documents as text, I always seem to get some missing-text in the output. I was not able to find this string in the project repository, python-docx, or documentation.
Snippet:
doc_converter = DocumentConverter(allowed_formats=[InputFormat.DOCX])
conv_res = doc_converter.convert(input_doc_path)
print(conv_res.document.export_to_text())

Output:
<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

<missing-text>

Documents:

Complete failure, all text is "missing-text": doc.docx
Partial failure, only some of the text is "missing-text": doc2.docx

Both documents are public.
What causes missing-text? What should be my mental model for it when processing documents?
Thanks!

@Belval here is a draft PR to fix the issue of missing text: https://github.com/DS4SD/docling/pull/528
Issue appeared when embedding text element into nested tables, moreover it's in a different xml tag that expected, I suspect those documents were exported from other applications than MSWord.
Regarding doc2 example - this PR seems to be fixing it completely
Regarding doc - text is there, however the entire document is a complex nest of nested tables, that creates other artifacts in the final output, however now text is preserved. For this file we recommend it to convert it to PDF and then run through Docling for better quality results.

Here's the missing-textdummy. https://github.com/DS4SD/docling-core/blob/f464be5521a92a21cb312b2d7f68489487b63b10/docling_core/types/doc/document.py#L2140


[AutoDiff] NFC: Clean up dead code.

emitBuiltinDifferentiableFunction() and emitBuiltinLinearFunction() are unused.

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


Physical Path removing \

I'm using the latest version 1.4.3, and it appears to be trimming the slashes on the physical path when creating a web site
I'm trying to point to a network share, but it deploys without the \
eg
\fabrikam\site
on IIS
fabrikam\site

https://github.com/Microsoft/vsts-rm-extensions/pull/194 Fix checked in will be released along with other issues. Closing the issue


remove [DEPRECATED] Field 'allocate_public_ip'

Running terraform apply hit the issue below.

1 error(s) occurred:

* alicloud_instance.instances: 1 error(s) occurred:

* alicloud_instance.instances: Error creating Aliyun ecs instance: &common.Error{ErrorResponse:common.ErrorResponse{Response:common.Response{RequestId:"9DEEC05A-7458-469C-BBAE-F37BA9BCD82C"}, HostId:"ecs-cn-hangzhou.aliyuncs.com", Code:"Zone.NotOnSale", Message:"The specified zone is not available for purchase."}, StatusCode:403}```

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

Hi @zzxwill thanks for your contribution. The issue has been fixed. Please be check.


Spread scheduling but counting only running containers.

I'd like to request a scheduling strategy (unless its possible to do so with current spread scheduling) that counts only running containers rather than all containers on the node.
The issue is that a node may have a bunch of containers that have exited/dead/stuck in created, but few running containers and thus will not receive any more containers. Even though the node is not running as many containers, it will still get a load distributed based on the total rather than the total running number.
(Of course another solution for me is just to clean up not running containers but I thought perhaps this may be useful for others as well)

@ikreymer We are going with another solution ... is just to clean up not running containers. The reason is to be consistent on swarm resource management. Swarm considers mapped network ports, container memory reservation, etc as used resource until the container is deleted. Otherwise restarting the containers would result in conflict/failure. Under the same principal swarm counts stopped containers in container scheduling. #1520 is to update document on this.

@dongluochen There is a scenario that cannot delete exisiting container before running a new one. I want to upgrade the image tag of the container from 1.0 to 2.0 and still keep the volumes, so that i have to run a new container with --volume-from in the same host. The problem is, as swarm take the stopped containers into account, that host is filtered out when the old container has a port mapped to the host because the new container wants the same port. How can i solve this?

@jimmycmh Data volume container is independent of service and can be attached to multiple containers. Separating data volume from service would resolve your problem. If this is not the issue you have, can you elaborate your use case?

@dongluochen thanks for replying. Actually we are providing docker service to our users and we are using docker-compose to update containers when users changing their compose file. The behavior of docker-compose is to start a new container with --voumes-from to the old container, and if there is an binded port to the host, restarting will fail.
And in spite of docker-compose, it's unconvenient  to get volumes of a container if there's no host directory.

@jimmycmh If you want volumes to be persist at upgrade, you may define data volume containers without port mapping. In the following example, I can remove web and replace it with another image. docker-compose up --no-recreate will not change your data volumes. If it doesn't work for you,  example yml file may be helpful.
data:
    image: busybox
    volumes:
        - "/home/dchen/temp/www:/srv/www"
web:
    image: nginx
    ports:
        - "443:443"
        - "80:80"
    volumes_from:
        - "data"
web3:
    image: nginx
    ports:
        - "843:443"
        - "8088:80"
    volumes_from:
        - "data"


fix: Return all vessels from search, not just arbitrary 100

Hello @KitBurgess! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file vortexasdk/client.py:

Line 44:80: E501 line too long (80 > 79 characters)
Line 52:9: E731 do not assign a lambda expression, use a def
Line 52:80: E501 line too long (87 > 79 characters)

This closes #29


Allow laravel 7.x

Allow laravel 7.x

This change is

any updates here?

@santiripper
The composer.json should be updated like
"~5.3||^6.0||^7.0"

It should support 5.x, 6.x and 7.x

Updated, thanks @ankurk91

ping @benwilkins

@benwilkins
Please tag a new patch version. Thanks!


Which package manager?

The repo appears to currently be using npm. Is this the long term plan? Thoughts on yarn? What about https://pnpm.io/?

For now npm is great as we don't have any complex workspace/monorepo requirements. From a performance perspective npm v7+ has no issues keeping up with yarn or pnpm once a lockfile is present (in my experience). It also becomes a bother having to setup installation for pnpm in CI, or warn contributors that they have to use pnpm (not a big deal but slight hurdle).
As soon as we require a monorepo setup we'll definitely switch straight over to pnpm. What do you like using and why?

I concur on all points. npm is more than sufficient for now.
I don't have a strong preference. I usually just use whatever a repo ships with because it's one less thing to worry about, but as far as I can tell, pnpm is the most compelling long term solution.
Feel free to close this issue, unless we want to keep it open for additional discussion?


better parsing of PDDL domain

improve parsing of PDDL domain. I.e. extract predicates, rules and actions (action preconditions). Is required for #16 and #19.

As #16 is solved and I am not convinced that this is really necessary for #19, I will close this issue.


feature: recode cloudcommon policy default/resource codes

这个 PR 实现什么功能/修复什么问题:
改进：把预定义policy放到各个服务自己管理，目前只把onecloud的处理了，其他服务等合并和再处理

是否需要 backport 到之前的 release 分支:
NONE

/area util
/cc @yousong @zexi

Codecov Report

Merging #5614 into master will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #5614   +/-   ##
=======================================
  Coverage    6.76%    6.77%
=======================================
  Files         620      620
  Lines      104938   104944    +6
=======================================
+ Hits         7102     7110    +8
+ Misses      97264    97259    -5
- Partials      572      575    +3

Flag
Coverage Δ

#aFlag
6.77% <0.00%> (+<0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/policy/defaults.go
0.00% <ø> (ø)

pkg/cloudcommon/policy/resources.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/lockman/fifo.go
80.00% <0.00%> (-10.00%)
:arrow_down:

pkg/cloudcommon/cronman/cronman.go
50.43% <0.00%> (+4.38%)
:arrow_up:

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 d239f99...995428a. Read the comment docs.

/lgtm

/lgtm


Use list item available since API 1

Fix for #47
simple_list_item_activated_1 is only available since 11, use simple_list_item_1 instead.

Hi @ranterle, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


[TRI-950] io.runTask return type of the callback has TypeScript error when it includes an unknown type

To recreate this issue:
await io.runTask("foo", { name: "Foo" }, async () => {
  return {
    foo: "bar",
  } as unknown;
});

That is because the return type of the callback is typed as required to extend SerializedJson:
https://github.com/triggerdotdev/trigger.dev/blob/fa942fc9f5aa1c2255efdb6304600be7f89cf20b/packages/trigger-sdk/src/io.ts#L434
We do this so the types of the return of runTask will match what is actually returned, since we run the results of the runTask callback through a JSON stringify/parsing as task output is stored in the database as JSON. Because of Resumability, this is a requirement, unless another solution can be identified.
I'm also now realizing that this SerializedJson might be incorrectly typed as well, as it can include Date and Symbol:
https://github.com/triggerdotdev/trigger.dev/blob/fa942fc9f5aa1c2255efdb6304600be7f89cf20b/packages/core/src/schemas/json.ts#L12
So this could cause issues when resuming a run and using the cached task output, where Date's would be symbols and the types would be wrong. It would be great to test this and possible change the required type to DeserializedJson.
TRI-950

/bounty $75

/attempt #280

/attempt #280

Hello,@ericallam Can you explain a bit more

I was able to reproduce the issue but it is not clear what needs to be done so far. It would be nice to get some details
/attempt #280

how about we having a wrapper something like this
async function runTaskWrapper<TResult>(
  key: string | any[],
  options: RunTaskOptions,
  callback: (task: IOTask, io: IO) => Promise<TResult>
): Promise<SerializableJson> {
  const result = await io.runTask(key, options, async (task, io) => {
    const userResult = await callback(task, io);
    // Ensure that userResult is of SerializableJson type
    return userResult as SerializableJson;
  });

  return result;
}

@yashug even thought this would work, it's not safety right? We would be getting a type safety at transpile/development, but on runtime the data type could be different and bring unexpected behaviors

@ericallam, can you take a look at #342?
I decided to take a shot, and if you test with your example
await io.runTask("foo", { name: "Foo" }, async () => {
  return {
    foo: "bar",
  } as unknown;
});

It's working now

So this could cause issues when resuming a run and using the cached task output, where Date's would be symbols and the types would be wrong. It would be great to test this and possible change the required type to DeserializedJson.

Do you see a way of handling this without a breaking change?

Can we close this one guys? @ericallam @matt-aitken

Can we close it, guys? @matt-aitken @ericallam

Yep @ologbonowiwi, I'll close now


Add instructions how to setup the plugin while it is not published yet

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

Thanks for the contribution, @PaulWoitaschek. The plugin is actually published to Maven Central, not the Gradle Plugin Portal. That is not part of plugins management by default so needs to be added there. I've added that to the readme.


$ref in additionalProperties in external yaml ignored

Initially opened against swagger codegen as #4135. They send me here.
It seems that swagger-parser cannot handle a $ref below additionalProperties in a external yaml file.

The verbose output of swagger-codegen shows it:
{
  "swagger" : "2.0",
  "info" : {
    "version" : "1.0.0",
    "title" : "Test API"
  },
  "host" : "swagger.io",
  "basePath" : "/show-bug",
  "schemes" : [ "http" ],
  "consumes" : [ "application/json" ],
  "produces" : [ "application/json" ],
  "paths" : {
    "/tests" : {
      "get" : {
        "operationId" : "listTests",
        "parameters" : [ ],
        "responses" : {
          "200" : {
            "description" : "Returns results.",
            "schema" : {
              "$ref" : "#/definitions/result"
            }
          }
        }
      }
    }
  },
  "definitions" : {
    "result" : {
      "type" : "object",
      "properties" : {
        "name" : {
          "type" : "string"
        },
        "_links" : {
          "$ref" : "#/definitions/link-object"
        }
      }
    },
    "link-object" : {
      "type" : "object",
      "additionalProperties" : {
        "$ref" : "#/definitions/rel-data"
      }
    }
  }
}

This is not implemented

@fehguy When you say it's not implemented, is it that this is currently not implemented in YAML? IT looks like there are tests to cover this in JSON processing.
I ask because there's a related issue reported to swagger-codegen (swagger-api/swagger-codegen#5753).

hmm.  As of december last year it wasn't implemented, and it shouldn't matter if it's JSON or YAML for how the parser works.  Where are the tests that you've seen?

@fehguy it looked like tests hitting this file should have covered it. Specifically testLoadRelativeFileTree_Json and testLoadRelativeFileTree_Yaml look like they'd cover JSON and YAML of this scenario, although I can't seem to find the yaml file referenced in that last test. Maybe the test is parsing JSON and passing? I didn't dig much deeper than that.

thanks @jimschubert I'll get into this one shortly

We just ran up against this. Any news or updates? I also left a more detailed question on the linked codegen ticket - don't think that impacts here, but it may.

Ugh, sorry, this got lost. We'll try to have a look at it soon.

Hi, Please check in branch 2.0, we merged a PR solving the issue. @slarti-b @jimschubert @rakus


A bit of cleanup to Managers

Overview

Updated the Mixed Reality Manager's Enable<Feature> to be Is<Feature>Enabed

Double checked to also make sure these bools check if the profile is not null.

Updated Handedness flags because Both and Any were the same flag value of 3.  Any now properly includes Other.
Sorted the order of the configuration profiles in the creation context menu.
Removed unnecessary ping object in input system initialization.
Fixed an issue with the Input Action property drawer.
Updated Boundary Manager to properly initialize values in it's initialization method instead of the constructor.

TODO

[x] Fix an issue with assembly reloading not disabling managers properly.

Found a few more issues I want to address.


Upgrade to clap 4

Issue https://github.com/roc-lang/roc/issues/5388
Summary of changes

Use Arg.num_args

Supersedes multiple_values and takes_value

Use Arg.value_parser

Replace Arg.possible_values
Remove use of Arg.allow_invalid_utf8, either parsing directly to PathBuf or OsString
Move custom parsing logic from usage to arg definition (e.g., usize)

Use ArgMatches.get_one and ArgMatches.get_many in place of ArgMatches.value_of* and ArgMatches.values_of*
Use new flag/option idioms

Arg.action(ArgAction::SetTrue) for flags
Replace ArgMatches.is_present with ArgMatches.get_flag for flags
Replace ArgMatches.is_present with ArgMatches.contains_id to check option presence

Remove use of App.trailing_var_arg

This was moved to Arg and now conflicts with last. See relevant unit test.

Yeah, should be fine. We already talked about making this change anyway.
May require changing use in a test, but should be fine to do that as well.
On Sun, May 14, 2023, 4:31 PM David Smith @.***> wrote:

@.**** commented on this pull request.
In crates/cli/src/lib.rs
https://github.com/roc-lang/roc/pull/5405#discussion_r1193226294:

     .required(false);

 let flag_prebuilt = Arg::new(FLAG_PREBUILT)
     .long(FLAG_PREBUILT)
     .help("Assume the platform has been prebuilt and skip rebuilding the platform\n(This is enabled by default when using `roc build` with a --target other than `--target <current machine>`.)")

   .possible_values(["true", "false"])

   .value_parser(["true", "false"])

Is it ok that it's not backward compatible? If so, happy to make the
change.
—
Reply to this email directly, view it on GitHub
https://github.com/roc-lang/roc/pull/5405#discussion_r1193226294, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7S22FZ2LTPOLALGQNKHWDXGFTM5ANCNFSM6AAAAAAYATAUVE
.
You are receiving this because you commented.Message ID:
@.***>

Looks great! Thanks for dealing with this update.

I think you may need to search for prebuilt-platform= in the repo and update a few uses in tests/comments.

I'll look at the clippy failure

Thanks for the help, @Anton-4!


IE11 "Possible Unhandled Promise Rejection" error

Hi,
'react-sortable-hoc' version greater than 1.0.0 is not working on IE11 and throwing "Possible Unhandled Promise Rejection" console message.
Is this component no longer supporting IE11 on newer versions?
Thanks for any help.

+1 I have the same issue, I guess problem here: https://github.com/clauderic/react-sortable-hoc/blob/master/src/utils.js#L228. But can't be 100% sure.
see sceenshot


Java 9 related errors on startup

Ubuntu 16.04
$ java -version
openjdk version "9-internal"
OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src)
OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, mixed mode)

$ java -jar shinyproxy-0.7.5.jar
2016-11-20 00:26:35.400  INFO 20339 --- [           main] e.o.components.UsageStatsCollector       : Disabled. Usage statistics will not be posted.
2016-11-20 00:26:35.726  WARN 20339 --- [           main] ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'springSecurityFilterChain' defined in class path resource [org/springframework/security/config/annotation/web/configuration/WebSecurityConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.servlet.Filter]: Factory method 'springSecurityFilterChain' threw exception; nested exception is java.lang.IllegalAccessError: class org.springframework.ldap.core.support.AbstractContextSource (in unnamed module @0x4b13c23c) cannot access class com.sun.jndi.ldap.LdapCtxFactory (in module java.naming) because module java.naming does not export com.sun.jndi.ldap to unnamed module @0x4b13c23c
2016-11-20 00:26:35.755 ERROR 20339 --- [           main] o.s.boot.SpringApplication               : Application startup failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'springSecurityFilterChain' defined in class path resource [org/springframework/security/config/annotation/web/configuration/WebSecurityConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.servlet.Filter]: Factory method 'springSecurityFilterChain' threw exception; nested exception is java.lang.IllegalAccessError: class org.springframework.ldap.core.support.AbstractContextSource (in unnamed module @0x4b13c23c) cannot access class com.sun.jndi.ldap.LdapCtxFactory (in module java.naming) because module java.naming does not export com.sun.jndi.ldap to unnamed module @0x4b13c23c
... MORE

We typically deploy with a Zulu Java 8 (http://zulu.org/download/) also on Ubuntu 16.04. Probably this is a Java 9 compatibility issue - we'll investigate, thanks!

Just adding another case to this issue. I'm on the same OS and Java version as @1beb and get the same error. Let me know if I can add any info to help diagnose it. Thanks!

@mdec @1beb: temporary workaround: launch ShinyProxy using
java -XaddExports:java.naming/com.sun.jndi.ldap=ALL-UNNAMED -jar shinyproxy-0.7.5.jar

@mdec @1beb: there is not much we can do at the moment, except for that workaround.
The problem originates in a class of spring-ldap-core:
private static final Class<com.sun.jndi.ldap.LdapCtxFactory> DEFAULT_CONTEXT_FACTORY
            = com.sun.jndi.ldap.LdapCtxFactory.class;

This reference to the class com.sun.jndi.ldap.LdapCtxFactory does not work in current builds of OpenJDK 9. Bumping spring-ldap-core to its latest version (2.2.0.RELEASE) shows the same problem.

Thanks, Tobias. This solves the problem of launching ShinyProxy, but now I can't get anything to happen when I try to access it on port 8080. All requests time out. I'm on AWS and have no firewall restrictions in place for now. Anything else I should check? Let me know if I should start a separate issue for this.

Thanks @mdec, can you share your shinyproxy.log file?

Sure, file attached (had to change the file extension for Github to allow it).
shinyproxy.txt
Happy to send more info if this doesn't help you diagnose it.

The missing class appears to have been added to the OpenJDK in the meantime.
Just tested ShinyProxy on Zulu <IP_ADDRESS> (a certified OpenJDK build) and the error did not appear anymore.


HBASE-28316 Add BootstrapNodeService handlers (#5637)

Signed-off-by: Bryan Beaudreault<EMAIL_ADDRESS>(cherry picked from commit c001ed3ba3c25a0d1a684c393092756b7ad9ee25)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  0s
branch-2 passed

+1 :green_heart:
compile
3m  6s
branch-2 passed

+1 :green_heart:
checkstyle
0m 49s
branch-2 passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m  7s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 43s
the patch passed

+1 :green_heart:
compile
3m  7s
the patch passed

+1 :green_heart:
javac
3m  7s
the patch passed

+1 :green_heart:
checkstyle
0m 45s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 29s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
spotless
0m 54s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 58s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 18s
The patch does not generate ASF License warnings.

32m 55s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5639

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 07738be9d4b2 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 6721863af1

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
78 (vs. ulimit of 30000)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 59s
branch-2 passed

+1 :green_heart:
compile
1m  4s
branch-2 passed

+1 :green_heart:
shadedjars
5m 32s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 41s
the patch passed

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

+1 :green_heart:
shadedjars
5m 34s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
8m  8s
hbase-client in the patch passed.

+1 :green_heart:
unit
213m 12s
hbase-server in the patch passed.

246m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5639

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a0688f8c34a3 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 6721863af1

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/testReport/

Max. process+thread count
4408 (vs. ulimit of 30000)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m  8s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 22s
branch-2 passed

+1 :green_heart:
compile
1m  1s
branch-2 passed

+1 :green_heart:
shadedjars
4m 37s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 16s
the patch passed

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

+1 :green_heart:
shadedjars
4m 37s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
7m 27s
hbase-client in the patch passed.

-1 :x:
unit
221m 45s
hbase-server in the patch failed.

252m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5639

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7feb98941029 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 6721863af1

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/testReport/

Max. process+thread count
4288 (vs. ulimit of 30000)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5639/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

The failed UT is not related.
Let me merge.