scrollable marked logs

the marked items side pane has a max width of +- 20% of the total window size.
In our log files, the first 20 characters show the time, log level, thread name.   Navigating from the marked logs would only be useful if we can see the full log line.
So make the side pane scrollable, or allow it to take 50% of the available space

In <IP_ADDRESS>2 if there is no log property defined to be shown, than multiple lines can be shown for each log in Marked logs panel.


README feedback

This issue is for any feedback you have while reading the README.
Something confusing? Badly explained? Not discussed at all?
If you have any thoughts I would love to hear them.

I found all questions answered. Nothing to complain about.

I think it should be mentioned somewhere that completion times are not taken into account when comparing streams. An example: '-x-|' == '-x---|'.

@rjkip I might change that. My original rationale was that sometimes you want to make assertions against diagrams where the last event and completion occur in the same frame (character in diagram).
Like:
it("creates a stream that emits every period ms", (done) => {
  const Time = mockTimeSource();

  const stream = Time.periodic(40);

  const expected = Time.diagram(
    `----0---1---2|`
  );

  Time.assertEqual(
    stream.take(3),
    expected
  );

  Time.run(done);
});

The expected diagram states that completion occurs the frame after the last event, whereas in reality it occurs immediately. So there is lenience in asserting and a kludge in diagram generation to support this case.
The real fix for this issue is so support syntax for multiple items in a single frame, which I plan on investigating soon.
Even then I think it would be ugly to have to do:
it("creates a stream that emits every period ms", (done) => {
  const Time = mockTimeSource();

  const stream = Time.periodic(40);

  const expected = Time.diagram(
    `----0---1---(2|)`
  );

  Time.assertEqual(
    stream.take(3),
    expected
  );

  Time.run(done);
});

I'm also considering another kludge where I would check the time difference between completion events for actual and expected and fail if it's more than one frame different.

@rjkip I have released v0.6 which will fail a test if the actual and expected streams end at different times.
As part of this I have also added syntax to express simultaneous events, as per the above example.
However, to improve the readability of the above test, I have allowed for testing infinite streams:
it("creates a stream that emits every period ms", (done) => {
const Time = mockTimeSource();
const stream = Time.periodic(80);
const expected = Time.diagram(
----0---1---2---
);
Time.assertEqual(
stream,
expected
);
Time.run(done);
});

Even though `periodic` is infinite, now `Time.run()` will only run to the end of your longest diagram (if you've used a diagram). So we can now test infinite streams with using `.take`, which is nice, and they will no longer run forever if you forget to use `.take`.

@rjkip I have released v0.6 which will fail a test if the actual and expected streams end at different times.

That sounds good. Confirmed to work as well :)
It does make a test that tests for a value and a completion in the same frame a bit awkward, but I think that's acceptable. These things are hard. You can still change it in a future minor, though :)
Time.assertEqual(Time.periodic(20).take(1), Time.diagram(`-(0|)`));

[...] I have allowed for testing infinite streams without completion:

Great! I was wondering about options there :)
All in all, thanks for replying and creating and maintaining this library :ok_hand:

It does make a test that tests for a value and a completion in the same frame a bit awkward, but I think that's acceptable. These things are hard.

Agreed, but I figure for a testing tool it's important to prioritize accuracy and correctness. I would rather be explicit and slightly awkward than implicit and imprecise.
In any case, this will only really come up when you have a stream designed to emit in the last frame, like of and last. It's thankfully not the common case for Cycle.js apps.


Solve the problem that customers cannot update tags after creation.

Issue #, if available:
Description of changes:
Deletes previous tags function which didn't work, and adds a new tags function that customer can update tags.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Wrong change


How do I set different serialization rules for key and value?

Key and value want to use different serialization rules.
However, redisson only supports setting codec and cannot be set separately.

Codec can be set per Redisson object. Below is the example.
redisson.getMap("mapname", new MyCodec());


Add conflict filter to EntityList

This PR adds a conflict filter to EntityList, completing the Frontend portion of getodk/central#503. The hardest part was connecting the filter to a query parameter. That's something that we've done in SubmissionList and have wanted to do in AuditList (#525), so I added a generic composable for syncing a ref with one or more query parameters. I wanted to verify that the composable worked in the AuditList case as well, so this PR also closes #525.
What has been done to verify that this works as intended?
SubmissionList now uses the new composable, and related tests continue to pass. I've added new tests of entity components and of the composable. I also tried a couple of things locally.
Why is this the best possible solution? Were any other approaches considered?
The main question was how to connect the conflict filter to a query parameter. The filter logic in SubmissionList was a little complicated, and my hope was that a composable would simplify component code and reduce the barriers to future dynamic query parameters.
Relatedly, the data flow in SubmissionList felt a little suspect. SubmissionList defined a settable computed property for each filter. Here's an example of how things worked before:

Navigate to .../submissions?start=2023-10-15&end=2023-10-16&reviewState=rejected&reviewState=hasIssues.

The submissionDateRange computed property is an array of DateTime objects (call this array "date range 1").
The reviewStates computed property is an array of review states.

Select a different date range ("date range 2"). This will trigger a navigation, changing the start and end query parameters and the submissionDateRange computed property.
submissionDateRange has changed. However, it is not date range 2, but instead a different array with equivalent (but not equal) DateTime objects. That different date range is then passed back to the date range filter, which reacts to it.
Furthermore, even though it was the date range filter that changed, reviewStates is also changed. It is a different array with the same values as before. That different array is passed to the review state filter, which reacts to it.

This worked in terms of user-facing behavior, but data ends up changing in unexpected ways, so components react at unexpected times. The data flow is not very clear.
The new composable makes the data flow clearer, avoiding settable computed properties. SubmissionList now creates a ref for each filter. Each ref is synced with one or more query parameters. If a query parameter changes, then the value of the ref is set, to which filter components react. Conversely, if a selection is changed in a filter component, then the value of the ref is set, updating query parameters. Even though that triggers a navigation, the value of the ref is not set a second time. In the terms of the example above, once date range 2 is selected, submissionDateRange is actually set to date range 2, and it remains date range 2 after the navigation. Unrelated refs also do not change after the navigation (reviewStates in the example above). The ref is synced with one or more query parameters, and something happens only if the value of the ref is changed, or one of the query parameters is changed to a truly different value (not just a technically different array).
That approach makes things simpler, but there is a downside for the submitter filter. The previous submitterIds computed property used the submitters resource, such that once the response for submitters was received, submitterIds would recompute. That's no longer the case. With the composable, each ref is associated with a function that converts query parameters to a value, but that function is not wrapped in a reactive effect. Even if the function references reactive data, it does not rerun when that data changes. It only reruns with one of the query parameters changes. As a result, we now need to watch the submitters resource, setting the submitterIds ref once the response is received. I don't love the watcher, but I don't see a way to wrap the conversion function in a reactive effect without introducing cases where the value of the ref is changed to a technically different, but equivalent value. I think there's also conceptual clarity that comes with limiting the ways that the value of the ref can be changed automatically. At the end of the day, it's also only the submitter filter that's like this: other filters have static options.
The composable itself involves some complexity, but I think I've been able to keep that complexity encapsulated in the composable. I think component code and the data flow is simpler.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
The likeliest source of regression is the filters on the submissions page, but tests are passing.
Before submitting this PR, please make sure you have:

[x] run npm run test and npm run lint and confirmed all checks still pass OR confirm CircleCI build passes
[x] verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

I made a number of small changes after code review, but not anything that I think requires additional review.

One small but important change: the ref that the new composable returns is now shallow. A shallow ref is all that's needed, and I think a shallow ref is actually necessary to support the data flow laid out in the PR description. Otherwise, in cases where the value of the ref is an object, the value would be a reactive proxy of the value it was set to. I want the two values to be exactly the same.
An important edge case: if the value of the ref changes, but that doesn't change query parameters for some reason, then a navigation should not be triggered. That comes up for the submitterIds ref, since it is set initially and then once again once the response from …/submitters is received.
I added more tests, including unit tests of the useAudit() composable.
More comments and other small changes


bug: startScan is not resolved on iOS

Plugin(s)

[X] Barcode Scanning
[ ] Translation

Did you test the latest version?

[X] I use the latest version

Platform(s)

[ ] Android
[X] iOS
[ ] Web

Current behavior
The startScan() method returns a Promise that is never resolved.
Expected behavior
The Promise should resolve.
Reproduction
https://github.com/JanMisker/capacitor-mlkit-plugin-demo
Steps to reproduce
Run the demo app.
I added a console.log("before startScan()") and console.log("after startScan()").
On Android I see both messages logged, but on iOS only the before one.
Other information
No response
Capacitor doctor
💊   Capacitor Doctor  💊

Latest Dependencies:

  @capacitor/cli: 5.0.5
  @capacitor/core: 5.0.5
  @capacitor/android: 5.0.5
  @capacitor/ios: 5.0.5

Installed Dependencies:

  @capacitor/cli: 5.0.0
  @capacitor/core: 5.0.0
  @capacitor/android: 5.0.0
  @capacitor/ios: 5.0.0

[success] iOS looking great! 👌
[error] Missing <manifest package=""> attribute in app/src/main

Before submitting

[X] I understand that incomplete issues (e.g. without reproduction) are closed.

Thank you for creating this issue.
Seems like I forgot to call „completion()“ in line https://github.com/capawesome-team/capacitor-mlkit/blob/f9b38e9895d29d9793eacff742b2a93974c4725d/packages/barcode-scanning/ios/Plugin/BarcodeScanner.swift#L36
I will fix this as soon as I am home. You can also submit a PR.

Check, see PR #50


how to add lora

You can use the lora:..... inside your prompt. I'm getting the same result as webui.
r = api.txt2img(prompt='photo of a cute girl with black hair <lora:Moxin_10:0.6> shuimobysim',
                seed=102, eta=1.0)
r.image

The lora doesn't work when I'm using the same prompt as in webui

I found this [Bug]: Skipping unknown extra network: lora #9274

I found this [Bug]: Skipping unknown extra network: lora #9274

I used the solution in the 7984 and It works

If webui is run with --nowebui . extra networks is not initialized. This is a webui bug.
It should work when launched with --api (without --nowebui).


sync pillar votes after restart

Purpose

How does the solution address the problem

Changes made

prnet cleaned-up successfully


feat: remove support for new-webclient

BREAKING CHANGE: Support for the frontend called new-webclient has been removed.

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


set name input to be readonly when bundle is selected

When a user selects an image bundle for the trainer, the
name input is set to the name of the bundle. This input is supposed
to be read only at this point.
Fixes #64

Current coverage is 31.44%

Merging #82 into master will not affect coverage as of e56ba0a

@@            master     #82   diff @@
======================================
  Files            4       4
  Stmts          159     159
  Branches        33      33
  Methods          0       0
======================================
  Hit             50      50
  Partial          1       1
  Missed         108     108

Review entire Coverage Diff as of e56ba0a

Powered by Codecov. Updated on successful CI builds.

@kognate what if I train a classifier and then I want to train another one with my own images and name. Can I do that with your changes?
Looking at the code seems like it will keep the control as readonly

The control gets reloaded when the user goes back to train another classifier and then it's reset and can be modified.
Also,  I added a reset of the read-only status if the user clears the positive/negative images.


⚠ Bofrost.be has degraded performance

In 84900ca, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2400 ms

Resolved: Bofrost.be performance has improved in bd22fd5.


mpi tester shall die on the first failure.

Because after the first failuer the ranks is already in a inconsistent state. I am looking into this.

closed by adding the -x flag to pytest


Cross compiling windows with ubuntu fails on etc2comp build

Master branch
sudo apt-get install mingw-w64
scons p=windows
It stopped working ~5-10 days ago.
thirdparty/etc2comp/EtcImage.cpp: In member function 'Etc::Image::EncodingStatus Etc::Image::Encode(Etc::Image::Format, Etc::ErrorMetric, float, unsigned int, unsigned int)':
thirdparty/etc2comp/EtcImage.cpp:259:64: error: invalid use of incomplete type 'class std::future<void>'
   std::future<void> *handle = new std::future<void>[a_uiMaxJobs];
                                                                ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:268:12: error: invalid use of incomplete type 'class std::future<void>'
    handle[i] = async(std::launch::async, &Image::RunFirstPass, this, i, uiNumThreadsNeeded);
            ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:268:91: error: invalid use of incomplete type 'class std::future<void>'
 ndle[i] = async(std::launch::async, &Image::RunFirstPass, this, i, uiNumThreadsNeeded);
                                                                                ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:275:12: error: invalid use of incomplete type 'class std::future<void>'
    handle[i].get();
            ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:275:13: error: invalid use of incomplete type 'class std::future<void>'
    handle[i].get();
             ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:330:107: error: invalid use of incomplete type 'class std::future<unsigned int>'
 gned int> *handleToBlockEncoders = new std::future<unsigned int>[uiNumThreadsNeeded-1];
                                                                                ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<unsigned int>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:334:30: error: invalid use of incomplete type 'class std::future<unsigned int>'
       handleToBlockEncoders[i] = async(std::launch::async, &Image::IterateThroughWorstBlocks, this, blocksToIterateThisPass, i, uiNumThreadsNeeded);
                              ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<unsigned int>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:334:147: error: invalid use of incomplete type 'class std::future<unsigned int>'
 mage::IterateThroughWorstBlocks, this, blocksToIterateThisPass, i, uiNumThreadsNeeded);
                                                                                ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<unsigned int>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:340:50: error: invalid use of incomplete type 'class std::future<unsigned int>'
       uiIteratedBlocks += handleToBlockEncoders[i].get();
                                                  ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<unsigned int>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:340:51: error: invalid use of incomplete type 'class std::future<unsigned int>'
       uiIteratedBlocks += handleToBlockEncoders[i].get();
                                                   ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<unsigned int>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:343:15: warning: possible problem detected in invocation of delete [] operator: [-Wdelete-incomplete]
      delete[] handleToBlockEncoders;
               ^~~~~~~~~~~~~~~~~~~~~
thirdparty/etc2comp/EtcImage.cpp:330:33: warning: 'handleToBlockEncoders' has incomplete type
      std::future<unsigned int> *handleToBlockEncoders = new std::future<unsigned int>[uiNumThreadsNeeded-1];
                                 ^~~~~~~~~~~~~~~~~~~~~
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<unsigned int>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:343:15: note: neither the destructor nor the class-specific operator delete [] will be called, even if they are declared when the class is defined
      delete[] handleToBlockEncoders;
               ^~~~~~~~~~~~~~~~~~~~~
thirdparty/etc2comp/EtcImage.cpp:356:12: error: invalid use of incomplete type 'class std::future<void>'
    handle[i] = async(std::launch::async, &Image::SetEncodingBits, this, i, a_uiJobs);
            ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:356:84: error: invalid use of incomplete type 'class std::future<void>'
    handle[i] = async(std::launch::async, &Image::SetEncodingBits, this, i, a_uiJobs);
                                                                                ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:362:12: error: invalid use of incomplete type 'class std::future<void>'
    handle[i].get();
            ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:362:13: error: invalid use of incomplete type 'class std::future<void>'
    handle[i].get();
             ^
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:369:12: warning: possible problem detected in invocation of delete [] operator: [-Wdelete-incomplete]
   delete[] handle;
            ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:259:22: warning: 'handle' has incomplete type
   std::future<void> *handle = new std::future<void>[a_uiMaxJobs];
                      ^~~~~~
In file included from thirdparty/etc2comp/EtcImage.cpp:40:0:
/usr/lib/gcc/i686-w64-mingw32/6.2-win32/include/c++/future:115:11: note: declaration of 'class std::future<void>'
     class future;
           ^~~~~~
thirdparty/etc2comp/EtcImage.cpp:369:12: note: neither the destructor nor the class-specific operator delete [] will be called, even if they are declared when the class is defined
   delete[] handle;
            ^~~~~~

Edit
Kubuntu 17.04
gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406

Ubuntu and mingw versions?

Does it fail only when cross-compiling to win32, or also to win64?

Does it fail only when cross-compiling to win32, or also to win64?

Apparently both, as @Keetz had the same issue for win64: https://pastebin.com/vsdXEifT

Trying on Mageia, it builds fine both in 32-bit and 64-bit (I built with the changes of #9455, but I don't expect they would have an influence on this issue).
MinGW-w64 5.0.1 with GCC 6.1.0.

It also builds fine on Travis CI btw, with this system:
Ubuntu 14.04.3, MinGW-w64 3.1.0 with GCC 4.8.2.
So I'm not sure why it wouldn't work with versions in between like you have.

same issue on
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)

The fix is to change distro. So far it seems to fail only on Ubuntu :P

Are you guys using WSL (windows subsystem for linux) to compile Godot for Windows? I'm having the same issue here.
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Windows 10 version 1703 build 15063.483

Same issue here with Ubuntu 16.04 with i686-w64-mingw32-gcc (GCC) 5.3.1 20160211 :'-(

I found the trouble: by default mingw on ubuntu works in win32 mode (which doesn't support thread), if you compile with posix mode it works.
To use posix mode for mingw by default:
$ sudo update-alternatives --config x86_64-w64-mingw32-gcc
<choose x86_64-w64-mingw32-gcc-posix from the list>
$ sudo update-alternatives --config x86_64-w64-mingw32-g++
<choose x86_64-w64-mingw32-g++-posix from the list>

Hmm still not working.
I also get this message when I switch something.
update-alternatives: warning: skip creation of /usr/bin/x86_64-w64-mingw32-gcc-6 because associated file /usr/bin/x86_64-w64-mingw32-gcc-6-posix (of link group x86_64-w64-mingw32-gcc) doesn't exist

I was having the same problem on Ubuntu, but I managed to get it working by including bits=64 in the scons command

@sketchyfun  I had the same issue compiling it with either 32 or 64 bits. Changing to posix mode with the above method solved it for me.

@Xrayez I tried that, but I received the same error as @AlexHolly. Either way, hopefully a combination of this information will be of help to other people :)

Use @touilleMan solution an switch to posix
Use @sketchyfun solution and run with scons p=windows bits=64

It works again, thanks.
Is there a bug in the scons or why is it not using bits=64 as default on a 64bit system?

@AlexHolly in my experience it is only p=windows that doesn't use 64 bits as default. Whenever i build to x11 it defaults to 64 bits.

The bits logic on Windows is pretty convoluted, both for MinGW and for MSVC, so no idea why it defaults to 32-bit. At least it seems to try to detect 64-bit so I guess it's a bug.

I believe the logic is only for MSVC, because it requires the proper compiler to be already set up. With MinGW you can have both compilers available and select the right one by changing the prefix.

so, issue or not?

Got a report on Discord of someone running into this issue on Lubuntu (version unknown) with MinGW-w64 4.0.4.
Looks like that version is buggy, so the fix would be: get a newer mingw.

does anyone know if it is possible to switch to posix in shell without manually entering the number?

If you try to build some CI you should try to use a proper docker-container where this is not needed.
This one works for me FROM debian:jessie
If not this should work.
RUN echo "1"| sudo update-alternatives --config x86_64-w64-mingw32-gcc
RUN echo "1"| sudo update-alternatives --config x86_64-w64-mingw32-g++

does anyone know if it is possible to switch to posix in shell without manually entering the number?

This should work:
sudo update-alternatives --set x86_64-w64-mingw32-gcc /usr/bin/x86_64-w64-mingw32-gcc-posix
sudo update-alternatives --set x86_64-w64-mingw32-g++ /usr/bin/x86_64-w64-mingw32-g++-posix


python: Collected python version in bad format

We run python -V and get a result like 'Python 3.7.0 (default, Sep 10 2019, 18:15:34) \n[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]\n' which is unexpected - we try to keep the format Python x.y.z. (this build is Python 3.7.0 on CentOS 7).
I suppose we could catch this case and strip away the other parts, so we remain with Python 3.7.0. Be very defensive to avoid incorrectly parsing versions.

This extended output is usually produced by something like
 python3 -V -V

or
python3 --version --version

or a combination of those, which would indicate that the version argument flag is being passed twice somehow.


cmake -DCMAKE_${X}_COMPILER problem fixed (IDFGH-2877)

bootloader external project: CMAKE_[C+CXX+ASM]_COMPILER parameters forwarding enabled;
esp32 toolchain: "isset" check before "set" enabled.

If we run cmake with the "-DCMAKE_ASM_COMPILER:STRING=/path/to/xtensa-esp32-elf-gcc -DCMAKE_CXX_COMPILER:STRING=/path/to/xtensa-esp32-elf-g++ -DCMAKE_C_COMPILER:STRING=/path/to/xtensa-esp32-elf-gcc" instead of changing PATH, then we'll get the following errors:

The ASM compiler identification is unknown
Found assembler: xtensa-esp32-elf-gcc
The C compiler identification is unknown
The CXX compiler identification is unknown
CMake Error at /home/nikita/work/esp/esp-idf/tools/cmake/project.cmake:99 (_project):
The CMAKE_ASM_COMPILER:
xtensa-esp32-elf-gcc
is not a full path and was not found in the PATH.
Tell CMake where to find the compiler by setting either the environment
variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
CMakeLists.txt:6 (project)
Warning: Did not find file Compiler/-ASM
CMake Error at /home/nikita/work/esp/esp-idf/tools/cmake/project.cmake:99 (_project):
The CMAKE_C_COMPILER:
... blah blah blah ...

It happens because:

tools/cmake/toolchain-esp32.cmake override user definitions;
bootloader external project executor doesn't forward theese options.

This commit fixes it.

Hi @p5-vbnekit ,
Thanks for bringing this up. I'm a little curious what the use cases are for specifying the toolchain on the command line like this.
Because of CMake's cross compiling behaviour, for future compatibility it may be preferable to support passing CMAKE_TOOLCHAIN_FILE= on the command line to load a custom toolchain file, rather than overriding parts of the toolchain file. Do you think this could work for your use case?
(Ping @igrr as he may have some thoughts about the best approach here, as well.)

Hi @p5-vbnekit ,
Thanks for bringing this up. I'm a little curious what the use cases are for specifying the toolchain on the command line like this.
Because of CMake's cross compiling behaviour, for future compatibility it may be preferable to support passing CMAKE_TOOLCHAIN_FILE= on the command line to load a custom toolchain file, rather than overriding parts of the toolchain file. Do you think this could work for your use case?
(Ping @igrr as he may have some thoughts about the best approach here, as well.)

Hi! Thanks for reply. Yes it is possible, but in my case it will require more actions for configuring build profile...
In my case i use QTCreator (or "dockered" jenkins for automatic builds) & standard esp32 toolchain but non-standard toolchain path. QTCreator overrides theese cmake variables. Overriding CMAKE_${X}_COMPILER is thinnest and compatible way to build automation (in my opinion).
Reasons:

not need to modify system environment
not need for additional files
it is legal cmake way too: https://gitlab.kitware.com/cmake/community/wikis/FAQ#how-do-i-use-a-different-compiler.

May be add both modes?

Hi @p5-vbnekit, it seems I am unable to reproduce the issue that prompted you to submit this patch:
If we run cmake with the "-DCMAKE_ASM_COMPILER:STRING=/path/to/xtensa-esp32-elf-gcc -DCMAKE_CXX_COMPILER:STRING=/path/to/xtensa-esp32-elf-g++ -DCMAKE_C_COMPILER:STRING=/path/to/xtensa-esp32-elf-gcc" instead of changing PATH, then we'll get the following errors:

What I did is made a copy of the toolchain somewhere in my system not in PATH, and executed idf.py and a bare CMake build with -DCMAKE_ASM_COMPILER:STRING=/path/to/xtensa-esp32-elf-gcc -DCMAKE_CXX_COMPILER:STRING=/path/to/xtensa-esp32-elf-g++ -DCMAKE_C_COMPILER:STRING=/path/to/xtensa-esp32-elf-gcc passed. The app and bootloader build used the override toolchain binaries.
Is there something missing from my attempt to reproduce the issue?

Deleted my previous reply since I was able to reproduce the issue you mention shortly thereafter.
About the patch, I'm not sure, since these would mean the patch would also be required for every other official toolchain-file ESP-IDF will deliver.
It doesn't seem to be standard practice for toolchain files as well: https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html.


Questions about real-time

Hello, is it possible to use the camera directly in the model to generate results in real time? Like yolo, you can input the camera data and get the result in real time.


QuickOpen: Allow any order for search terms

It could save a lot of time if the search terms in quickopen was not taken in order. I explain:
My project is like so:

If I search for index everything is fine, I get the expected 2 index.js files:

If I search for bar index, also I get the right index.js file:

But often during my development i'm searching first by file name, and then I remember that there is not only one file named like this in my project, so I want to specify the "module" afterwards like this:

I think it would be a great idea to show the same results for index bar as the ones for bar index but only if there is no better matches.
Some example to illustrate with the following tree:
project/
├── indexable/
│   ├── index.js
│   └── bar.js
└── bar/
     ├── index.js
     └── bar.js

Search terms: index bar
Results:
1st/ indexable/bar.js (because the order of terms matches the file path)
2nd/ bar/index.js  (as there is two matching terms, but in wrong order)
Search terms: indexbar
Results:
1st/ indexable/bar.js
bar/index.js is not a match cause it does not match any of the terms

Just see that it duplicates #30404
You can close it. I will up vote the other issue ;)


Ignore specific lines when comment/uncomment

Is it possible to ignore specific lines beside blank line when commence/uncomment?
Of course the specific line must startwith default delimiter, such as the following code, I use '//**'.
Actually, I want to comment the following code once and then uncomment them after build using shortcut key 14<leader>ci, but leave line 1 and 9 untouched.
 //**Ping Request********
 root_declare!(0x00u8,PingReq,count=25);
 #[derive(BinWrite,BinRead,Debug)]
 #[brw(magic=0x00u8)]
 pub struct PingReqLoad {
     pub reqid: u64,
 }

 //**Ping Response*********
 #[derive(BinWrite,BinRead,Debug)]
 #[brw(magic=0x01u8)]
 pub struct PingRspLoad {
     pub reqid: u64,
 }

Given the lines you want to ignore are already inline comments, no there isn't a way to do exactly what you want if you try to use inline comments to comment the lines again. I suggest using a block comment format to comment out the area with a single multi-line comment. Reversing that will then leave the inline comments intact.

Using block comment as followed and set option let g:NERDRemoveAltComs=0 in .vimrc, the block comment part can be ignore when commernt invert operation.
 /*Ping Request*/
 root_declare!(0x00u8,PingReq,count=25);
 #[derive(BinWrite,BinRead,Debug)]
 #[brw(magic=0x00u8)]
 pub struct PingReqLoad {
     pub reqid: u64,
 }

 /*Ping Response*/
 #[derive(BinWrite,BinRead,Debug)]
 #[brw(magic=0x01u8)]
 pub struct PingRspLoad {
     pub reqid: u64,
 }


JSON CRDT server clock

[x] Prepare codecs to work well with server clock.
[x] Improve server clock tests.
[x] Fuzz testing for server clock?
[x] Missing APIs for working with patches.

[x] Batch
[x] Rebase
[x] Cloning

[x] Server clock scenario tests.

:tada: This issue has been resolved in version 7.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


minor parameter issue

hello -
using objects as  parameters does not appear to work for me.  i attempted to use the syntax found here:
https://github.com/agershun/alasql/wiki/Getting started
using this syntax:
 alasql.exec('INSERT INTO one (:a, :b);', {a:3,b:4});

http://jsfiddle.net/mtt9r7rx/7/

Crazy - we lost some syntax convenience somehow.
Its not working because its missing VALUES - but the example worked in earlier versions.
This feature is now part part of the regression tests and is implemented.
Until next release gets out you can use https://github.com/agershun/alasql/blob/develop/dist/alasql.fs.js

hello -
should i be able to use objects in an UPDATE as well?
alasql.exec('UPDATE one SET :a WHERE :b',  {a: 987654321, b: 4} ) ;

http://jsfiddle.net/mtt9r7rx/16/

The changes are now released as part of version 0.3.7


[SPARK-47722][SS] Wait until RocksDB background work finish before closing

What changes were proposed in this pull request?

When closing the rocksdb instance, we need to wait until all background work finish. If not, the following error could be observed:
24/03/29 06:47:11 INFO RocksDB StateStoreId(opId=0,partId=0,name=default): [NativeRocksDB-2] [/error_handler.cc:396] Background IO error IO error: No such file or directory: While open a file for appending: /ephemeral/tmp/spark-efd53c17-2b8a-4f80-aca0-b767dc06be3d/StateStoreId(opId=0,partId=0,name=default)-732271d8-03b3-4046-a911-5797804df25c/workingDir-3a85e625-e4fb-4a78-b668-941ca16cc7a2/000008.sst: No such file or directory
24/03/29 06:47:11 ERROR RocksDB StateStoreId(opId=0,partId=0,name=default): [NativeRocksDB-3] [/db_impl/db_impl_compaction_flush.cc:3021] Waiting after background flush error: IO error: No such file or directory: While open a file for appending: /ephemeral/tmp/spark-efd53c17-2b8a-4f80-aca0-b767dc06be3d/StateStoreId(opId=0,partId=0,name=default)-732271d8-03b3-4046-a911-5797804df25c/workingDir-3a85e625-e4fb-4a78-b668-941ca16cc7a2/000008.sst: No such file or directoryAccumulated background error counts: 1
<TRUNCATED LOG>
24/03/29 11:54:09 INFO ShutdownHookManager: Deleting directory /ephemeral/tmp/spark-b5dac908-59cc-4276-80f7-34dab79716b7/StateStoreId(opId=0,partId=0,name=default)-702d3c8f-245e-4119-a763-b8e963d07e7b
24/03/29 06:47:12 INFO ShutdownHookManager: Deleting directory /ephemeral/tmp/spark-efd53c17-2b8a-4f80-aca0-b767dc06be3d/StateStoreId(opId=0,partId=4,name=default)-0eb30b1b-b92f-4744-aff6-85f9efd2bcf2
24/03/29 06:47:12 INFO ShutdownHookManager: Deleting directory /ephemeral/tmp/streaming.metadata-d281c16c-89c7-49b3-b65a-6eb2de6ddb6f
pthread lock: Invalid argument

In the source code, after this error is thrown, there is a sleep for 1 second and then re lock the original mutex:
https://github.com/facebook/rocksdb/blob/e46ab9d4f0a0e63bfc668421e2994efa918d6570/db/db_impl/db_impl_compaction_flush.cc#L2613
From the logs of RocksDB and ShutdownHookManager , we can see that exactly 1 second after rocks db throws, the pthread lock: Invalid argument is thrown. So it is likely that this mutex throws.
Why are the changes needed?

Bug fix for a transient issue
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing test should be enough.
Was this patch authored or co-authored using generative AI tooling?

No

cc @anishshri-db

Merged to master.


How to set default value?

How do i set spinner default value (like placeholder or something)?

Hi @rafflypohan, sorry for the late response. Could you elaborate on this? Thanks!

You can set the default value with the method below:
android:hint="My SpinnerView"

thanks!


'Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections

I sometime get this error in the log file (the metrics collection fails, no metrics returned).
I use vmware_exporter-0.11.0.dist-info
and pyvmomi-<IP_ADDRESS>8.12-py3.7.egg-info
Expected behavior:
I wish the error log was more explicit (especially in debug mode).
Which vcenter was queried ? Which operation was running, which VMware object was queried.
Log:
Unhandled error in Deferred:

Traceback (most recent call last):
--- <exception caught here> ---
  File "d:\python\python37-32\lib\site-packages\vmware_exporter\vmware_exporter.py", line 725, in _vmware_get_host_perf_manager_metrics
    self.host_labels,
  File "d:\python\python37-32\lib\site-packages\vmware_exporter\defer.py", line 99, in parallelize
    results = yield defer.DeferredList(args, fireOnOneErrback=True)
twisted.internet.defer.FirstError: FirstError[#0, [Failure instance: Traceback: <class 'pyVmomi.VmomiSupport.vmodl.fault.SystemError'>: (vmodl.fault.SystemError) {
   dynamicType = <unset>,
   dynamicProperty = (vmodl.DynamicProperty) [],
   msg = 'A general system error occurred: Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.',
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [],
   reason = 'Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.'
}
d:\python\python37-32\lib\threading.py:917:_bootstrap_inner
d:\python\python37-32\lib\threading.py:865:run
d:\python\python37-32\lib\site-packages\twisted\_threads\_threadworker.py:46:work
d:\python\python37-32\lib\site-packages\twisted\_threads\_team.py:190:doWork
--- <exception caught here> ---
d:\python\python37-32\lib\site-packages\twisted\python\threadpool.py:250:inContext
d:\python\python37-32\lib\site-packages\twisted\python\threadpool.py:266:<lambda>
d:\python\python37-32\lib\site-packages\twisted\python\context.py:122:callWithContext
d:\python\python37-32\lib\site-packages\twisted\python\context.py:85:callWithContext
d:\python\python37-32\lib\site-packages\pyVmomi\VmomiSupport.py:706:<lambda>
d:\python\python37-32\lib\site-packages\pyVmomi\VmomiSupport.py:512:_InvokeMethod
d:\python\python37-32\lib\site-packages\pyVmomi\SoapAdapter.py:1374:InvokeMethod
]]

Can you check with "nc" or "telnet" if you are able to connect from your point of installation to the vmware api server you've configured?

There is a lot of close_wait on the adress:port of the exporter during this period .

Closing due to inactivity.


[Misdetection] Password protected Microsoft Excel 2007+ document (.xlsx) misdetected as MS Outlook Message (application)

What should the file have been detected as? What has the file been misdetected as?
A MS Excel 2007+ (.xlsx) spreadsheet that has been protected with a password is not accurately identified-- with low confidence it was dected as an MS Outlook Message.
Please link or attach the misdetected file below (Do NOT upload PII!)
password-protected-example.xlsx
Or:

Open LibreOffice spreadsheet application
Create a MS Excel 2007+ spreadsheet with .xlsx extension
Click File > Save as... > Save with password
Set password
Save

Additional context
Both the attached file and an existing private, password-protected, file were detected the same-- MS Outlook Message
$ magika -r -m high-confidence ~/Downloads/password-protected-example.xlsx
/home/bjester/Downloads/password-protected-example.xlsx: Unknown binary data (unknown) [Low-confidence model best-guess: MS Outlook Message (application), score=62]
$ mimetype ~/Downloads/password-protected-example.xlsx
/home/bjester/Downloads/password-protected-example.xlsx: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

Thanks for reporting (and sorry for the long delay). This indeed seems a tricky sample. We have a new model, and that says Word CDF, which is still not correct. Unfortunately magika currently doesn't support encrypted files of this kind. That being said, it's unclear why mimetype says application/vnd.openxmlformats-officedocument.spreadsheetml.sheet; file says CDFV2 Encrypted / application/encrypted. I quickly checked the header, and it does look like a CDF, rather than a OOXML. (So the extension should likely be .xls, not .xlsx)? CC @corkamig
Anyways, for now added to our set of problematic samples so that we can try to improve for the future (CLA: checked).
Thanks again!

Indeed, it's a CDF, but it's internally an 'Encrypted Package'. The binary content doesn't show that it's an Excel, Word or whatever.


Add Face detection using MTCNN project

Is your feature request related to a problem? Please describe.
In this project, I have implemented face detection using MTCNN, and I have conducted a comparative analysis with OpenCV to demonstrate the superior accuracy of MTCNN in real-world face detection scenarios.
Describe the solution you'd like
MTCNN (Multi-task Cascaded Convolutional Networks) is a popular face detection algorithm used in computer vision tasks. It is specifically designed for real-time face detection in images and videos. MTCNN consists of three stages.
No dataset required.
Describe alternatives you've considered
No response
Additional context
In this project, I have:

compared the superiority of the MTCNN algorithm over opencv in face detection task.
keypoints detection using MTCNN.
extract faces in the image.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I have already completed the project. You can check here .
So once it is assigned to me I shall come up with a PR.

@lakshmishreea122003 - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.


SQL Server date and datetime2 are reported as nvarchar

nanodbc::result results = nanodbc::execute(sql);
const short n_columns = results.columns();
for (int i = 0; i < n_columns; ++i)
{
	std:;cout << results.column_name(i);
	std:;cout << results.column_datatype(i);
	std:;cout << results.column_datatype_name(i); // returns wrong typename for date and datetime2
}

That was very quick. But now looks like something else might be broken?
I just replaced the two files, recompiled and somehow the UNICODE settings seem to be ignored.
Can yo check? Reverted to the old files.. all compiles clean,

There is one more commit related 674a10b94ef162b648d0b3dfe48dcc344a7e5e7c
You really need to be more specific:

what is actually wrong, what are the values you are getting and you consider incorrect
what DBMS version you use
what driver and version you use

You can compare what driver is used in appveyor.yml. The latest related builds are green on Windows
https://ci.appveyor.com/project/lexicalunit/nanodbc/build/1.0.492 as well as Linux
https://travis-ci.org/lexicalunit/nanodbc/builds/229538268

Regarding the Unicode, any chance you missed the changes in CMake options in #260 ?
Namely, CMake option and preprocessor define NANODBC_USE_UNICODE have been replaced with NANODBC_ENABLE_UNICODE.

I was still using NANODBC_USE_UNICODE.
I am not using CMake though. My environment is Visual Studio 2015 on Wndows 7.  SQL Server 2014.
Sometime I do compile with gcc on Windows. I did report an issue related to GCC #244
As for the current issue. It is not resolved in the files I just pulled,

You need to switch to NANODBC_ENABLE_UNICODE.
Regarding MinGW, sorry I can't help myself. I completely ignore any GCC flavours on Windows. I only use GCC on Linux. There may be others who can help.

@mloskot
This issue is still un-rersolved as I said 4 days ago. Just now I cloned the latest repo compiled and still datetime2 is reported as nvarchar. BTW I had already switched to  NANODBC_ENABLE_UNICODE. That was unrelated problem.

@bangusi Can you finally clarify if this issue occurs when building VS2015 or MinGW?
Above, you mention your environment is VS2015 and that you sometimes use GCC  on Windows too.
However, the issue description should be update to clearly indicate all such relevant details, including ODBC driver and its version you are using. Please, if you could update it.

My environment:
Windows 7 64 bit
VS2015 Update 3
SQL Server 12.0.5203.0
The code is what I posted 4 days ago
Compiled 64 bit with the following macros
NANODBC_ENABLE_UNICODE
NANODBC_DISABLE_ASYNC
I mentioned I had SQL Server 2014 the other day but turns out I have 2012. It is the Management Studio that is version 2014. Also MinGW is not my primary compiler just there for testing out stuff from time to time.
I hope that helps.

Thanks for the update.
I have used ODBC version 11 for SQL Server and I can confirm it works as expected (ie. 117c3b0983cfa006466975b8ad0f1c7e79b43fbc). Same for 13 and 13.1 versions of the driver.
AppVeyor builds use exactly this driver for all SQL Servers tested: {ODBC Driver 11 for SQL Server}

I mentioned I had SQL Server 2014 the other day but turns out I have 2012.

AFAIK, SQL Server 12.0.5203.0 is SQL Server 2014 isn't it?
I'd say, AppVeyor build cover exactly your environment, so I can't see what might be the reason you are getting datetime2 reported as nvarchar.

FYI, in 1bf9b36c2cea31da5b7381c241018f163b741381 I added two new build jobs to AppVeyor targetting SQL Server 2012, with NANODBC_ENABLE_UNICODE=ON and OFF.

May be something in my environment. I will try to build and run the test cases and report back.

@mloskot
I re-produced the problem on a  different environment ( different machine ):
Windows 7 Enterprise
SQL Server 13.0.1601.5 running on Windows Server 2012 R2
Compiler GCC 6.3
Driver: Not sure which one is loaded ; I have both 11 and 13 installed

Sorry, since I can't reproduce it, I can't help.
Assuming these tests cover your use case:

test_date
test_datetime2

and since they pass on AppVeyor as well as locally for myself, all works-for-me

@mloskot
Is it possible to setup the test harness with Visual Studio? I thought it was going to be easy as dropping the cpp files into the project and go but apparently not.
The problem does not affect me really since I don't use nanodbc for any work. If I did I could easily find a work around, I just want help make the library better.

get Catch header
create project
add nanodbc.cpp and mssql_test.cpp
configure include directories
build, if fails, fix configuration issues

Should be easy to work out
IMHO, its easier to run cmake, eg. In command line or in VSCode with CMake
Tools extension.
IMHO, CMake support built in VS2017 is far from easily usable
On 11 May 2017 23:42, "bangusi"<EMAIL_ADDRESS>wrote:

@mloskot https://github.com/mloskot
Is it possible to setup the test harness with Visual Studio? I thought it
was going to be easy as dropping the cpp files into the project and go but
apparently not.
The problem does not affect me really since I don't use nanodbc for any
work. If I did I could easily find a work around, I just want help make the
library better.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lexicalunit/nanodbc/issues/265#issuecomment-300925172,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE7ZTY-IziDRLU5J22Vfat1EQB6-vSDks5r44C4gaJpZM4NS5W2
.

Close but..
I have VS 2015 Express which it turns out ships without ATL. I never needed this before.
So went downloaded Windows7 driver SDK kit which includes ATL. I need atlbase.h.  Compile now but tons of link errors related to ATL.
Any idea why ATL is needed for these tests?

Any idea why ATL is needed for these tests?

See #230

@mloskot
Finally I got my test environment sorted out.
I have 7 failures including the following on dates:
-------------------------------------------------------------------------------
test_date
-------------------------------------------------------------------------------
\nanodbctestcases\mssql_test.cpp(399)
...............................................................................

\nanodbctestcases\test_case_fixture.h(829): FAILED:
  REQUIRE( result.column_datatype(0) == 91 )
with expansion:
  -9 == 91

-------------------------------------------------------------------------------
test_datetime2
-------------------------------------------------------------------------------
\nanodbctestcases\mssql_test.cpp(506)
...............................................................................

\nanodbctestcases\mssql_test.cpp(525): FAILED:
  REQUIRE( result.column_datatype(0) == 93 )
with expansion:
  -9 == 93

No idea what's going on there.
I've been running these tests against SQL Server for a year and never noticed such differences. But, it's ODBC so everything is possible.
What connection string do you use for the test (via command line or NANODBC_TEST_CONNSTR_MSSQL)?

I've just run the tests against Azure SQL Database (it is not SQL Server on VM, but SQL Server flavour based on SQL Server 2016 compatible with SQL Server 2014 and 2016) and I can not reproduce the problem. Everything works here as expected.

I've run second test against SQL Server 2012 on Azure running on Windows Server VM,
using connection string like:
"Driver={ODBC Driver 11 for SQL Server};Server=ml-sql2012.cloudapp.net;Database=curves;UID=XXX;PWD=XXX;MARS_Connection=Yes;"

I can not reproduce the problem here either..

I'm unable to reproduce the problem in seven distinct environments:

SQL Server 2008, 2012, 2014, 2016
Azure SQL Database
SQL Server 2012 on Azure
Locally, using SQL Server 2016 (LocalDB instance)

and using ODBC Driver for SQL Server versions 11, 13 and 13.1.
In production, I also use nanodbc with legacy Microsoft SQL Server ODBC Driver (SQLODBC), where I use DATE and DATETIME2 types too.
I'm not saying a bug is impossible anywhere, it might be related to some specific condition or configuration which I have no idea about.
I just can't reproduce the problem.
So, I'm personally giving up on investigating this issue.

@mloskot
This is my connect string
.\nanodbcTestcases -c "Driver={SQL Server}; Server=myserver;Database=pdwh;UID=myid;PWD=xxxxxxx" > testresults.txt
If I change to what you are using
.\nanodbcTestcases -c "Driver={ODBC Driver 11 for SQL Server}; Server=myserver;Database=pdwh;UID=myid;PWD=xxxxxxx" > testresults.txt
The all tests pass!

You are using the legacy driver {SQL Server} which has been deprecated by Microsoft and SQL Server 2012 is the last one this driver supports.
There is nothing wrong with nanodbc.
If you gave the connection string earlier it would save us a lot of time.
(BTW my production app handles the deprecated driver differences internally)

@mloskot
I never knew that connect string triggered the use of the legacy driver. At one time in the near past I was using SQL Server Native Client 11.0 Then I think I read Microsoft was recommending use of plain ODBC driver so I wrongly assumed simply using SQL Server the latest installed driver will be used.

Driver={SQL Server} is the request to use the legacy "SQL Server Driver (SQLODBC)", it does not trigger anything implicitly.
Microsoft ODBC Driver for SQL Server is the current and recommended driver:

Driver=ODBC Driver 13 for SQL Server}
Driver=ODBC Driver 11 for SQL Server}

The legacy and often deprecated options are:

SQL Server Native Client (SNAC)

SQL Server Native Client (ODBC): Driver={SQL Server Native Client 11.0}
SQL Server Native Client (OLE DB): Provider={SQLNCLI11}

OLE DB Provider for SQL Server (SQLOLEDB): Provider={SQLOLEDB}
SQL Server Driver (SQLODBC): Driver={SQL Server}

Finally, the forest of differences and incompatibilities between drivers for the same DBMS (eg. SQL Server) plus differences between drivers for other DBMS (eg. SQLite vs SQL Server) is big enough to make one loose hair.
nanodbc is a thin layer on top of ODBC API.
nanodbc does not aim to act as abstraction unifying all such differences and incompatibilities between drivers.
nanodbc tests try to handle obvious or most annoying differences,  but that is just to enable testing against possibly wide spectrum of DBMS.


OpenAIRE 4 required fields

These changes add new fields to DSpace to allow the compliance with literature guidelines OpenAIRE 4.0. This includes datacite fields, schema.org fields, additional DC identifiers and the OpenAIRE schema (oaire) created for that particular guidelines.
Also, it is already organized on the different entities needed for the compliance of the guidelines.
To include those new registry files, you can change your dspace.cfg and include the following lines:
registry.metadata.load = openaire4-types.xml
registry.metadata.load = datacite-types.xml

or can manually load those new schemas into the database by executing in the CLI:
[/dspace]/bin/dspace registry-loader -metadata [/dspace]/config/registries/openaire4-types.xml
[/dspace]/bin/dspace registry-loader -metadata [/dspace]/config/registries/datacite-types.xml

please mind that [/dspace] should be replaced with the path to your DSpace installation.

The build failure is related with this test: MetadatafieldRestRepositoryIT.findAll
It's expecting to find dc.title and dc.date.issued within the first 100 fetched records. Since this PR adds more fields, those specific fields aren't found and the test fails. I will adjust the test.

Thanks for the PR @paulo-graca
I can't comment on which fields are relevant for OpenAIRE (which you all know much more about), but the only issue I see here is creating a large amount of Dublin Core fields, which may be confusing to the user (as discussed in the last meeting).
If those can be moved to e.g. an OpenAIRE schema, I think this is good to go

Thanks @benbosman @dimitrispie @mwoodiupui @tdonohue  and others for taking the time to look and for your contributions.
After our meeting I had the change to spoke with @josekarvalho and we agree to remove the added identifiers from publications. And the reasons are:

Resource Identifier (https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/v4.0.0/field_resourceidentifier.html) in the repository context it will be the Handle or the generated DOI that is present in dc.identifier.uri. No need to have a specific field.
RelatedIdentifiers (https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/v4.0.0/field_relatedidentifier.html) are identifiers of other resources that somehow are related with this one. Example: ISBN. This work isPartOf this ISBN. This identifier should be stored in a kind of a relation and DSpace already have specific fields for that like: dc.relation.ispartof. For now we will not propose any changes to the DC or Publication or OAIRE schema, but we still need to address the need to store the type of the field and the value. At the moment we can infer some types like: DOI, HANDLE, URL, ...
AlternateIdentifiers (https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/v4.0.0/field_alternativeidentifier.html) are external identifiers that refer to the same resource. We did an exercise to try to identify the use cases when this might happen and we identified two in the repository context:

When the content is migrated and perhaps harvested from other source and is assigned with a different ID
Both repository and a journal emit a DOI for the same resource

on those cases, DSpace already uses dc.identifier so, at the moment, we don't have the need to have new fields. Future PR might address further discussion.


Missing Entity Function upgrade information

Page doesn't contain anything about entity functions and how to handle state migration of entity functions, it is only about orchestration functions.
I can guess that changing the serialized state of entity function will throw EntitySchedulerException "Failed to deserialize entity state" (https://github.com/Azure/azure-functions-durable-extension/blob/790e086b271205975ef3b01620e2aec3f826aab3/src/WebJobs.Extensions.DurableTask/ContextImplementations/DurableEntityContext.cs#L181).
Page should describe how to handle changes in structure e.g. I have IDictionary<string, DateTime> _innerState (serialized as JSON) and I need to change it into IDictionary<string, InnerState>.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b735d777-d93c-8e8f-ee3f-2a10857c49a2
Version Independent ID: e65714b1-bbae-c0e2-1484-0e7d38a89758
Content: Versioning in Durable Functions - Azure
Content Source: articles/azure-functions/durable/durable-functions-versioning.md
Service: azure-functions
GitHub Login: @cgillum
Microsoft Alias: azfuncdf

@jahav Thank you for your feedback! We have assigned this issue to the author to review further and take the right course of action.

FYI @anthonychu

I can take a crack at this #reassign-to:anthonychu

We currently talk about making changes to entity classes in the .NET Durable Entities article. Both class-based entities and getting the state via GetState<T>() work the same way.
We're looking at updating the versioning page to include other languages. Deserializing into strongly typed objects is .NET specific, we'll have to see what's the best home for it once we make the changes. Closing for now. Thanks.
#please-close


Support multiple values for a given parameter

Pyramid has excellent support for URIs like /foo?x=bar&x=baz in the form of a Multidict. We want to support this option within pyramid_swagger so a URL like:
/foo?x=bar&x=baz
can successfully validate against a schema like:
{
   paramType: "query",
   type: "string",
   paramType: "query",
}

This requires query argument validation supporting both the primitive value and a MultiDict of the primitive, as long as all values satisfy the primitive type.

Lost to the sands of time ⏳ Also changed significantly after Swagger 1.2


Text alignment on a per-message basis

This could be implemented as a TbyOption, e.g. TbyOption.SetAlignment, with left, center and right as options.
An alignment constant can be given to the scribble_create() script, which handles the correct drawing.
https://github.com/glitchroy/textboxy/blob/9ab8e43be61a47224db60c88d053c1097f9b11e7/scripts/tby_st_tb_init/tby_st_tb_init.gml#L21
The default would be fa_left, but this could very easily be a config option, e.g. tby_default_alignment.

Implemented in scribble v3.1.1 (a4bfc483da338c6a8951e679652f27a1a8cfa432).


feat: add predictions

⚠ Note: This system is still in progress, but I need a review before the official test ⚠
New command /predictions
This command allows users to add predictions for the Serie A TIM football league. The system is interactive and includes checking for the validity of the prediction and live scores for the leaderboard.

Tu tu tu tu, Max Verstappen


Roll Flutter Engine from 8aa2e6516af1 to 11020a2ee6d7 (2 revisions)

https://github.com/flutter/engine/compare/8aa2e6516af1...11020a2ee6d7
2023-07-07<EMAIL_ADDRESS>Roll Skia from 11a2eefe4c61 to 57dc2a31bf26 (1 revision) (flutter/engine#43456)
2023-07-07<EMAIL_ADDRESS>Manual roll Dart SDK from 2d98d9e27dae to 0b07debd5862 (21 revisions) (flutter/engine#43457)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Darwin base chip cluster

Problem
This PR is the first part of some PRs to update the Objc API.
The ZAP templates changes are separated to the ZAP generation in terms of commits in order make it easier for the reviewer to not have to search for what has really been changed.
Summary of Changes

Add a CHIPCluster base class for Objc Clusters
Update the method calls to return (void) in instead of (BOOL) and pass an error in the completionHandler if something fails

@vivien-apple conflicts here :(


Sv 13 driving mode switching

SV-13 is about driving mode switching. Key 'A' represents front wheel steering, Key 'B' represents crab steering , Keys 'D' represent four wheel steering. When certain keys are pressed, certain block on GUI should becomes red.
I add a publisher to the GUI so that when key pressing is detected, the variable 'a' should increase by 1 and send through topic 'ros_driving_mode_switching'. The value of a should be visualized on the screen

@TomyangSydney Master has been updated, please re-merge and resolve conflicts.


font-size .vgt-input .vgt-select

When clicking on the search bar safari zooms in on the page when using mobile. Same thing when clicking on the select dropdowns. The fix is to set the font-size 16px instead on 14px on .vgt-input .vgt-select, but i can only change this in the node_modules/vue-good-table/dist/vue-good-table.css.
However this gets reseted every time i update  vue-good-table.
I tried using custom css and sett the .vgt-input .vgt-select to font-size 16 but no luck.
Anyone has any tips?
thank you
Specs
What version are you using?
2.21.1
What browser?
Safari IOS
Expected Behavior
What did you expect to happen?
not to zoom in
Actual Behavior
zooms in
Steps to Reproduce the Problem
font-size 14px

ok, so i found a fix for this. my problem was that i tried to do this in styles
<style scoped>.vgt-input {font-size: 16px;</style>
but the fix is to do this form a custom css file that you import to your projects main.js file
import<EMAIL_ADDRESS>in the main.css file add
#Phonenumbers .vgt-input {     font-size: 16; } #Phonenumbers .vgt-select {     font-size: 16px; }
then you simply add this to your
<vue-good-table id="Phonenumbers"</vue-good-table>

@mrkazu you can also use the deep selector to change any css within the component:
https://vue-loader.vuejs.org/guide/scoped-css.html#deep-selectors
closing.


Avoid received event nil pointer

Related commit: https://github.com/nbd-wtf/go-nostr/commit/92c0143762f349d1ab9316f8eb622b54dddd486a

When will this happen?

I have experienced that myself too, but I think it is a bug somewhere else. No nil pointers should be sent through the Events channel. We should fix it there at the source. I tried, but I don't remember what happened.


Nodegroup label selector pulls in all security groups defined on a UXP node.

What happened?
When deploying a 2nd EKS cluster claim on the same UXP instance, the 2nd nodegroup cannot be provisioned because it tries to pull in all the subnetIDs on a cluster using a label selector. Since the subnets are defined in another composition, matchControllerRef does not work. The label selector should be unique to the composition.
 subnetIdRefs:
    - name: cluster-a-nbvd5-wl7qq
    - name: cluster-b-vgfzq-9np6m
    - name: cluster-b-vgfzq-cm726
    - name: cluster-a-nbvd5-9ndmw

apply failed: error creating EKS Node Group (cluster-b-vgfzq-7bsgj:cluster-b-vgfzq-v755f): InvalidParameterException: Subnets specified must belong in the same VPC
{
  RespMetadata: {
    StatusCode: 400,
    RequestID: "13cab71f-84d8-4c50-8947-065c3a4727ce"
  },
  ClusterName: "cluster-b-vgfzq-7bsgj",
  Message_: "Subnets specified must belong in the same VPC",
  NodegroupName: "cluster-b-vgfzq-v755f"
}:

Epic #
How can we reproduce it?
Deploy 2 cluster claims. kubectl describe nodegroup.eks
What environment did it happen in?

platform-ref-aws:v0.5.0
upbound/crossplane:v1.10.1-up.1
xpkg.upbound.io/upbound/provider-aws:v0.20.0

I believe the issue is that the patch is trying to select subnetSelector when it needs to be patching the subnetIdSelector field.  Will run a test.


fix: The Smartlimit description is always cut off

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/50959
PROPOSAL: https://github.com/Expensify/App/issues/50959#issuecomment-2417981500
Tests

Precondition: WS has set up expensify cards and approver.
Steps:

Open Expensify Card page
Press Issue new card
Proceed up to "Choose a limit type"
Verify that: The smart limit option is displayed in 2 lines

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Precondition: WS has set up expensify cards and approver.
Steps:

Open Expensify Card page
Press Issue new card
Proceed up to "Choose a limit type"
Verify that: The smart limit option is displayed in 2 lines

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/62e05c36-ffde-4659-80ef-dab261275478

Android: mWeb Chrome
https://github.com/user-attachments/assets/f29e43c3-188a-4691-a1dc-67a1f74b259c

iOS: Native
https://github.com/user-attachments/assets/b798f111-3768-4379-907c-c7ddd8124d7d

iOS: mWeb Safari
https://github.com/user-attachments/assets/b479d574-6b51-4504-bce9-a043906971ed

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/57fb40b7-7d39-427a-a9a6-fa256d540655

MacOS: Desktop
https://github.com/user-attachments/assets/6036b94d-3c03-4d5e-b71b-ed4e6770d305

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Option to save figure when plotting

As suggested by Данила Пилин.
When calling the functions or methods that have show_plot as argument, there should also be an option to save the plot to a file.

Created branch feature/save_fig to add the args, as well as docstrings, to all methods and fuctions that have show_plot functionality


Let user upload multi material vrm to merge

Users should be able to optimize vrm's by dragging and dropping a VRM with mutliple materials. Character studio should merge it, create an atlas and download it

#57 will do this now


Bazel file detection defeated by MacVim's filetype.vim

After installing this plugin and opening a *.bzl file in MacVim, I get:
:verbose set ft?

filetype=conf
Last set from /Applications/MacVim.app/Contents/Resources/vim/runtime/filetype.vim

I'm currently working around this via:
au BufRead,BufNewFile *.bzl,BUILD,WORKSPACE set ft=bzl
````

(Note: I'm using `set ft=` instead of `setf` in order to defeat MacVim's filetype.vim)

Yeah, reasonable to change it ti set ft= instead of setf. No point merging that change into vim since the builtin version has control over precedence.
BTW, I remember that aggressive conf rule in older versions of vim but I don't see it anymore in recent versions.


Create new section in Contacts step for Reviewer Information, rename to Contacts and Reviewer Information

See https://github.com/NASA-IMPACT/nasa-apt/issues/753#issuecomment-1600820097 and previous comments for context
Current Behavior
Currently, all reviews are conducted in APT through a dedicated review process. However, some historical ATBDs (PDF uploads) will have their content reviewed before entering in APT, or reviewed by people who don't have APT accounts.
Desired Behavior
Basic reviewer metadata is captured for all ATBDs (APT or PDF workflow).
Acceptance Criteria

[ ] In the Contacts step, add a similar field below where users can add reviewer information.
[ ] First, add a checkbox/yes-no select with the prompt Has this ATBD been reviewed already?

[ ] If yes, reveal the reviewer info collection form (https://github.com/NASA-IMPACT/nasa-apt/issues/753)
[ ] If no, do nothing (this will be reviewed in the platform)

[ ] Rename step to Contacts and Reviewer Information
[ ] This new section (reviewer info) should only be visible in the edit mode, not view or pdf exports

@bwbaker1, do you see any usability issues when users fill in reviewer information before writing their ATBD? Do users know who will review their ATBD? I thought that the review step was somewhat anonymized.

@wrynearson I don't see any issues with adding the reviewers first. Users can always come back and edit this section later if needed.
I think the initial conceptualization was that the review process would be anonymous, but this isn't really the case. Each science team has specific people that will review the ATBD. There is still anonymity in that the users do not know the specific person leaving reviews (i.e., they see reviewer1, reviewer2, etc. on the comments).

@bwbaker1 this is ready for your review

@wrynearson Looks good to me. I think it is ready for prod.

@wrynearson i think this is ready for prod. Just see my comments related permissions .


Consider using get instead of show

Show suggests some visualization IMO

Sure, if you think it is better. I think it is important that we are consequent in what we using. Im happy with: index, get, create, update, delete


ebiten: add more mouse cursor shapes

Operating System

[X] Windows
[X] macOS
[X] Linux
[ ] FreeBSD
[ ] OpenBSD
[ ] Android
[ ] iOS
[ ] Nintendo Switch
[ ] Xbox
[X] Web Browsers

What feature would you like to be added?
It would be good to have more cursor shapes similar to what GLFW/SDL have.
In particular, something close to:

GLFW_RESIZE_ALL_CURSOR (arrows pointing in 4 directions)
GLFW_NOT_ALLOWED_CURSOR ("crossed out circle" cursor)

If the platform doesn't support a particular cursor shape, I think it will be OK to not change cursor at all.
Why is this needed?
No response

I would also make a great use of this feature, currently I'm drawing ebiten.Image on the cursor position (as probably everyone) and this has some frustrating limitations

https://github.com/glfw/glfw/issues/427 These were added to GLFW 3.4, not 3.3 unfortunately, but I can add some hacks for Ebitengine.

GLFW_RESIZE_ALL_CURSOR

Probably this is move in CSS https://developer.mozilla.org/en-US/docs/Web/CSS/cursor

GLFW_NOT_ALLOWED_CURSOR

not-allowed in CSS.

Ha, in my environment (macOS 13), _moveCursor was not available. Apparently I would have to use WebKit's resource: https://stackoverflow.com/a/21786835/5435443
See also: https://docs.rs/winit/latest/x86_64-apple-darwin/src/winit/platform_impl/macos/util/cursor.rs.html

Hmm, this requires a hack to GLFW and we would need to port GLFW to Go.

Interesting. I thought that you planned to do this anyway, right?

Yes.


Please add expandall in sidebar

Searched dupes, didn't find this.
I use the side bar for searching but search results do not return until you expand the folder where the file is found. There is currently a Collapse All button. A lot of times, the opposite of Collapse All is Expand All and you can just hit the same button over and over to get them to expand/collapse. Can that please be added to better enable searches?

Thanks

Some related discussion in #66811, where I also learned that Alt+click on an expanded twistie will recursively collapse it, so next time you expand it with an unmodified click its subfolders will be in the closed state. Conversely, Alt+click on a collapsed twistie will recursively expand it but only for folders that have previously been manually expanded. AFAIK that constraint is to avoid the scenario where a single user action (Alt+click) on a root folder of a huge tree causes VSCode to go wild.

Perhaps the ability can be disabled/reenabled in Settings? I don't mind VSCode going wild if I can get my search results to work without all the manual expansion I'm doing now.

I agre, there is an issue for this here: https://github.com/microsoft/vscode/issues/70357


Game broken

When attempting to access this at https://githubschool.github.io/github-games-jhill0914/, I am getting a 404. This could be caused by a couple things:

GitHub pages needs to be enabled on master. You can fix this in the repository settings.
the index.html file is incorrectly named inde.html. We will fix this together in class.

Can you please fix the first bullet @jhill0914?

@rwnfoo I don't have the Settings tab, do I not have the proper access rights to this repository?

@rwnfoo Oops, I didn't see the collaboration invite email.  Got it now.

Hey @jhill0914 - This is actually Project 3, some folks in class requested to have advanced repos generated. If you feel comfortable following the training manual to complete this at your own time, feel free to do so.


[2044] add created at and changed at timestamp for providers to api v1

Context
v1 api providers endpoint
created at and changed at timestamp for providers
Changes proposed in this pull request
Added created at and changed at timestamp for providers to api v1
Amended docs to reflect changes
Guidance to review
/api/v1/2019/providers
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Add "created_at" & "changed_at" timestamps for providers to API V1


Error when running make setup

Did the following:
$ go run ./cmd/todox/
public/public.go:7:12: pattern *.css: no matching files found
$ make setup
ℹ  Downloading Tailwind CSS binary. Please wait...
✅ TailwindCSS binary downloaded.
mv: cannot move 'tailwindcss-macos-arm64' to 'bin/tailwindcss': No such file or directory
make: *** [Makefile:9: setup] Error 1

Hey @soypat, Good catch. I will make sure the dir is created in the Makefile. Thank you.


504 Gateway Time-out on packages.microsoft.com

Describe the issue
504 errors on PMC
When did the issue occur?
Sun Jun 9, all day.
If applicable, what package did you attempt to install, and from which repo?
https://packages.microsoft.com/rhel/9/prod/msodbcsql18-<IP_ADDRESS>-1.x86_64.rpm
https://packages.microsoft.com/rhel/9/prod/mssql-tools18-<IP_ADDRESS>-1.x86_64.rpm
Steps to Reproduce
wget "https://packages.microsoft.com/rhel/9/prod/msodbcsql18-<IP_ADDRESS>-1.x86_64.rpm"
--2024-06-09 17:29:17--  https://packages.microsoft.com/rhel/9/prod/msodbcsql18-<IP_ADDRESS>-1.x86_64.rpm
Resolving packages.microsoft.com (packages.microsoft.com)... <IP_ADDRESS>
Connecting to packages.microsoft.com (packages.microsoft.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 504 Gateway Time-out
Retrying.

NOTE: Intermittent - it sometimes succeeds, especially when run from GitHub actions, but it fails frequently too. From my laptop, it always fails.
Actual Result
504 Gateway Time-out
Expected Result
200 OK and file downloaded

@timd73 there is currently an outage affecting packages.microsoft.com. Our central infrastructure is unable to pull container images that are used for central services. We're working urgently to resolve the issue,

packages.microsoft.com service should now be restored. Let us know if you continue to see issues.

@mbearup  right now it looks solved - I'll let you know if it recurs.
Thanks!


GitHub app uninstall event

:warning: The Git Automator app has been uninstalled on this repo.
Please click here to reinstall.

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

@v-caxian @TinaLiuGirl
The Git Automator for PR app has been uninstalled to this repo, which will cause the Git Automator service to be unavailable. Please install it in time, thank you!

The Git Automator app has been installed to this repo.


updated menu lyche

the norwegian menu is updated. Missing english translation

This looks good, added wrapping to the flex-box to prevent overflow.


Invalid issuer in discovery document expected: https://sub.domain.tld current: http://sub.domain.tld

Hello,
I'm scratching my head for few days now because of this error :
invalid issuer in discovery document – "expected: https://sub.domain.tld" – "current: http://sub.domain.tld"

Front is running on http://localhost:4200
.NET Core identity backend running on remote server reverse proxied through nginx/1.10.3 with proper CORS support.

The worst part is on my local dev machine all requests sent by Angular's app on https://sub.domain.tld/.well-known/openid-configuration are successful with a HTTP 200 code.
I don't understand what I'm doing wrong.
Any help would really be appreciated !
Cheers,

Did you spot the https (on "expected") vs http (on "current")?

Yes that was precisely the issue. I resolved my problem ! Fyi, I'm using IdentityServer4 as my Identity Provider, the issue was to add the option 'options.PublicOrigin = “https://sub.domain.tld“;' to change the default routes in /.well-known/openid-configuration which are 'http' and not 'https' because the .NET app is reverse-proxied.

Did you spot the https (on "expected") vs http (on "current")?

I am facing the same error as below.
invalid issuer in discovery document expected: https://mbisdev.com:443/auth/realms/nec current: https://mbisdev.com/auth/realms/nec
i checked that port number is added to the issuer url but the error says current url is without port.


nc_def_var_chunking_ints() returns NC_NOERR for HDF4 files - why?

Is there a reason why nc_def_var_chunking_ints() returns NC_NOERR for HDF4 files?
Seems like it should return NC_EPERM, since you can't define chunking on read-only files, and all HDF4 files are read-only...
This is demonstrated on my current branch in tst_interops2.c.

I believe this was just a mistake in the original code that had no consequences, so was never noticed.
I have taken it out as I moved the HDF4 layer to its own dispatch layer. I will put that work up in a bit and close this issue then.


Adding myself to Contributors

https://github.com/apache/camel/pull/2903 My small changes so far. Hoping to get more involved.

Thanks


fix issue #304

add the following pointcut when specify 'useServerPrepStmts' option :
com.mysql.jdbc.ServerPreparedStatement#serverExecute (for mysql5)
com.mysql.cj.jdbc.ServerPreparedStatement#serverExecute (for mysql8)
test passed for mysql-connector-java-5.1.6 and mysql-connector-java-8.0.13
and jackson-core version need bump to 2.12.7(https://github.com/chaosblade-io/chaosblade/issues/891), not included in this pr
fix:https://github.com/chaosblade-io/chaosblade-exec-jvm/issues/304

Thank you for your contribution.


Nano ledger with metamask: Transaction signature is not valid

Our Blockchain network is the fork of Go-Ethereum with Istanbul consensus algorithm. We are using metamask by providing node RPC address and chain ID and it is working fine but we attach nano ledger S/X with Metamask to make transactions, it gives following error:
error: Object { code: -32603, message: "Error: Ledger: The transaction signature is not valid", stack: "Error: Error: Ledger: The transaction signature is not valid" }
Please help us to understand why it is working with other ethereum wallets including Trezor but not with Ledger.  How can we fix it?

same problem. Trying to execution a transaction with Ledger Nano by proving an node RPC address. Got the error "The transaction signature is not valid".

I'm encountering the same issue with a Ledger Nano S on firmware 1.6.0. What additional logs does the Ledger team need to troubleshoot this?

I notice that it gives the same error when connecting to Ganache. Essentially, anything that is an RPC connection will fail.

this is a huge issue! i have matic on the matic side chain and i cant touch it because of this. is there a fix? im on the nano x btw

Still not fixed! It breaks the Energy Web Token... Please fix!!!

Still not fixed! It breaks the Energy Web Token... Please fix!!!

Hi, same problem :/ could you solve this error?
Thanks

Hi also have the same problem, still not fixed.

Still not fixed! It breaks the Energy Web Token... Please fix!!!

I had the same problem with MetaMask. I got around this by using MyCrypto which was suggested in the Energy Web documentation. When you visit the MyCrypto website, select the EWC network in the drop down in the top right corner. When adding your Ledger wallet, there will be an "addresses" drop down menu with Default (EWC) selected. Change that to either Ledger (ETH) or Default (ETH). Your EWT should show up in the first address. After doing this I was finally able to send my EWT.

Still not fixed! It breaks the Energy Web Token... Please fix!!!

I had the same problem with MetaMask. I got around this by using MyCrypto which was suggested in the Energy Web documentation. When you visit the MyCrypto website, select the EWC network in the drop down in the top right corner. When adding your Ledger wallet, there will be an "addresses" drop down menu with Default (EWC) selected. Change that to either Ledger (ETH) or Default (ETH). Your EWT should show up in the first address. After doing this I was finally able to send my EWT.

i still cant send my ewt anywhere i keep getting the transaction signature is not valid

How can this still be open???
Fix it please...

It seems that connecting your ledger nano with metamask in a side chain is a nightmare. They haven't fixed this issue and many of us and others will want to use the side chains to avoid high fees, but Ledger doesn't care about us. I cannot believe that this thread started more than 1 year ago and they haven't solved it yet...

I am able to use Metamask and Ledger on Polygon.

same problem trying to do transactions on fantom side chain

I still can't send MATIC tokens from Ledger Nano S to Metamask on the Matic network. 🐲