material

[WARN] TinyOBJ: material [ 'Minecraft_minecraft:dirt_12' ] not found in .mtl
IN MTL
newmtl Minecraft_minecraft:dirt_12
Ns 35.999996
Ka 1.000000 1.000000 1.000000
Kd 0.510000 0.360000 0.240000
Ks 0.370000 0.370000 0.370000
Ke 0.000000 0.000000 0.000000
Ni 1.450000
d 1.000000
illum 2

Same here, but this time it is broken due to spaces
[WARN] TinyOBJ: Both `d` and `Tr` parameters defined for "objMesh Zusammengef├╝hrtes Material". Use the value of `d` for dissolve (line 7 in .mtl.)
[WARN] TinyOBJ: material [ 'objMesh' ] not found in .mtl

This should get reported at https://github.com/tinyobjloader/tinyobjloader


Test broken link

This pull request demonstrates how FOLIO's continuous-integration/website-build reports a hugo failure due to a broken link on the pull request.
Compare with the GitHub Actions report on https://github.com/julianladisch/docs/pull/2 . I've made #46 to enable it in this repository.

@julianladisch : I don't understand what you are asking here.  At the moment, the docs site is built with Hugo using AWS CodeBuild and related tools.  There should be no GitHub Actions defined for this repository.  (Unless it is something that @sekjal is working on as part of his efforts to re-engineer the cumbersome documentation building process I had set up.)

I have wired up this repository to AWS Amplify as part of the re-engineering of the docs deployment process.  It may have resulted in Amplify adding some GitHub Actions to do the triggering of the Hugo builds

I'm not sure why this didn't occur to me before, but I went into the AWS CodeBuild logs to see why it failed:
[Container] 2021/12/02 12:32:11 Running command HUGO_ENV="production" hugo --verbose
INFO 2021/12/02 12:32:11 Using config file:
Start building sites …
INFO 2021/12/02 12:32:11 syncing static files to /codebuild/output/src684590677/src/github.com/folio-org/docs/public/
INFO 2021/12/02 12:32:12 postcss: use config file /codebuild/output/src684590677/src/github.com/folio-org/docs/themes/docsy/postcss.config.js
ERROR 2021/12/02 12:32:13 [en] REF_NOT_FOUND: Ref "singlesxxxxxxxxxxerverwithcontainers.md": "/codebuild/output/src684590677/src/github.com/folio-org/docs/content/en/docs/Getting started/Installation/_index.md:30:37": page not found
Total in 2313 ms
Error: Error building site: logged 1 error(s)

So the build failed because an internal reference to a page couldn't be found.  @julianladisch : Is there something you needed us to do in when this happens?  I'm not sure why you asked for a review from me and Marcia.


Compatibility with pod identities

Does it allow the use of iam oles and pod identities?
i created a role with pod identity association and included the service account name in the deployment
my config looks like
[profile opensearchrole]
role_arn = arn:aws:iam::227837763243:role/k8s-stage-com-sixt-tool-elastalert
source_profile = default
and i am mounting the configuration as a volume.
i get errored out:
Traceback (most recent call last):
File "/usr/local/bin/elastalert-create-index", line 8, in
sys.exit(main())
^^^^^^
File "/usr/local/lib/python3.11/site-packages/elastalert/create_index.py", line 215, in main
http_auth = auth(host=host,
^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/elastalert/auth.py", line 59, in call
refreshable_credential=session.get_credentials(),
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/boto3/session.py", line 203, in get_credentials
return self._session.get_credentials()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/botocore/session.py", line 509, in get_credentials
).load_credentials()
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/botocore/credentials.py", line 2035, in load_credentials
creds = provider.load()
^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/botocore/credentials.py", line 1898, in load
return self._retrieve_or_fail()
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/botocore/credentials.py", line 1907, in _retrieve_or_fail
creds = fetcher()
^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/botocore/credentials.py", line 1925, in fetch_creds
response = self._fetcher.retrieve_full_uri(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/botocore/utils.py", line 2861, in retrieve_full_uri
self._validate_allowed_url(full_url)
File "/usr/local/lib/python3.11/site-packages/botocore/utils.py", line 2868, in _validate_allowed_url
raise ValueError(
ValueError: Unsupported host '<IP_ADDRESS>'.  Can only retrieve metadata from these hosts: <IP_ADDRESS>, localhost, <IP_ADDRESS>

See #11 -- this should have been created as a discussion.


Include inSuccessfulContractCall for all events

Context - https://github.com/stellar/soroban-tools/pull/536#discussion_r1149568828

I don’t think this is necessary anymore. In https://github.com/stellar/go/blob/soroban-xdr-next/ingest/ledger_transaction.go#L185-L188, we “convert” normal events to DiagnosticEvents for the sake of go’s type system, by setting InSuccessfulContractCall = true on each one.


[Snyk] Security upgrade requests from 2.28.1 to 2.31.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements-test.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

591/1000  Why? Recently disclosed, Has a fix available, CVSS 6.1
Information Exposure SNYK-PYTHON-REQUESTS-5595532
requests:  2.28.1 -> 2.31.0
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Resolved with https://github.com/tackle-io/woodchipper/pull/72 (we stopped pinning the specific version)


Lightbox components do not get props from the Actions method?

Version
Tell us which versions you are using:

react-native-router-flux v4.0.0-beta.24
react-native v0.52

Expected behaviour
'gameId' should be passed to DemoGameLightbox component as a prop:
        Actions.DemoGameLightbox({
            gameId: 2,
        });

Actual behaviour
No props are passed to the LightBox component. Is this expected? Or a bug? How can we pass dynamic data to the lightbox?

Can you get your router code too?

@mn7676 Sure, I hope this helps. Thanks!
function reducerCreate(params) {
    const defaultReducer = Reducer(params);
    return (state, action) => {
        if ([ActionConst.POP_AND_REPLACE, ActionConst.BACK_ACTION].includes(action.type) && state.index === 0) {
            handleExitApp();
            return state;
        }
        return defaultReducer(state, action);
    };
}
...

<Router
                onExitApp={handleExitApp}
                createReducer={reducerCreate}
                sceneStyle={{
                    flex: 1,
                }}
            >
                <Lightbox key="lightbox">
                    <Scene key="root">
                        <Scene
                            key="Comp1"
                            component={Comp1}
                            hideNavBar
                            panHandlers={null}
                        />
                        <Scene
                            key="Comp2"
                            component={Comp2}
                            initial
                            hideNavBar
                            panHandlers={null}
                        />
                    </Scene>

                    <Scene
                        key="DemoGameLightbox"
                        component={DemoGameLightbox}
                    />
                </Lightbox>
            </Router>


Use serializable proxies when autowiring

When a non-serializable bean is injected into a Vaadin component, the bean should be injected as a serializable proxy to make it possible to use session replication. When the Vaadin component is deserialized, the proxy should look up the correct application context and bean to delegate to.
We have to verify that this is working both using automatic tests and in a real session replication environment. Will create a separate issue for that once we have it implemented.

Closing this issue in favor of #154

Are there some news related to this Issue ? Maybe the Time have solved the "deep problems" ?

I don't know whether the Vaadin dev team has done any work on this in the official add-on. The serialization problem would have to be addressed there and I'm not involved in that project.

Apparently, there is some progress being made: https://dev.vaadin.com/ticket/19462


Serving static assets

Hi,
I read your production setup documentation and stumbled upon this:
location /assets/ {
	proxy_pass http://localhost:3000/assets/;
}

"The same module is used for providing user with the static assets. Assets will be available under: https://prod.vuestorefront.io/assets."
I think you want to optimize communications, don't you? I am absolutely no web expert hence I did some research over the web. It seems to be possible to prevent the nodejs server from serving these static assets which optimizes communication because any access to these assets would not be a hit to the nodejs server anymore. Assuming your vue-storefront application runs on the nginx server (but the solution works also in the case where the nginx server and the nodejs server run on different computers), what you can do is adapt the nginx configuration like this for example:
location /assets {
  root path-to-vuestorefront/src/themes/default/assets;
}

In this case, you are sure that the nodejs application isn't serving the assets and that job has been taken over by the nginx server. If your two servers don't run on the same computer, then you need to share the assets folder of the nodejs computer with the nginx computer and let nginx serve the shared folder.

Yes, You can introduce this optimization  but since nginx/varnish can use the caching strategy for serving static assets the question is if it makes any sens? I mean - /assets is used in dev. mode - and therefore it's a straightforward way to use the same url structure in prod. You can add this note to the production docs, not a problem - please just create a PR


Stress test resources are deleted earlier than they should be

I had a test running in southeastasia for about 94h when the resources for the test were deleted. Since stress test apps are intended to test longer timelines (7 days or so) we need them to run for longer.
Talking with @ckairen  and @benbp  it looks like we're creating resource groups but assuming that a given test is only deployed once, which is no longer true now that we support deploying the same test to multiple namespaces. This means that the previous system (where a resource group was basically just the test name + the deployment ID) isn't guaranteed to be globally unique amongst all deployments in the Kubernetes cluster.
The simplest solution is just to use the same random naming that we use for resources and not worry about having a plain text association between the resources and the test. Developers that need to do some sort of collation can just look at the .env file for their test and figure out which resources they're looking at.
In the future it'd be nice to do some metadata tagging on the resource group so you can do some searches, but given the resources are temporary in nature it's probably not a huge deal to do that.

Linked a PR that should act as a short term workaround, but we should keep this open to think about the tagging, etc. that you mention.

(reopening: probably closed on accident since your previous comment indicates you want to keep it open)

The core issue was basically a bug that is fixed now. Some of the ideas around metadata are still valid, but not super high priority and just "nice to have." Closing unless those asks become higher priority.


Make sure Scrutinizer-CI gets updates

Expected Behavior
Scrutinizer should work.
Current Behavior
Scrutinizer does not work.
Possible Solution
Scrutinizer should sort it out.
Steps to Reproduce (for bugs)

Open README.md
Weep
???
Profit

Context
Personally, I'm devastated. Ever since that gorgeous green badge turned lifeless and grey, my world has become dull and sullen, and I no longer look forward to anything at all, hapless and hopeless.

Lol :laughing:

Unfortunately I had to delete and recreate the repo, so all the history is gone


connected, no node connectivity

script running directly no proxies, sending ping getting pong thru the network, but on the dashboard remains red "not connected".
any updates about it?

I check and try run with the official extension but it not show in the dasboard too, I think the dasboard have problem. Will upadate later if I found the exact problem

i saw some people using fake-useragent in they repo, i think you can try that way


Display is underneath of map ??

When user tries to pick a date, the display is hidden underneath of my map. It was working fine couple days ago. I dont know what cause this happened. I didnt change any codes.
How can I make the picker popup display above of the map? I used to show above of the map.
I use express node js
link(rel='stylesheet', href='https://unpkg.com/flatpickr/dist/flatpickr.min.css')
script(src='https://unpkg.com/flatpickr')

Looks like a z-index issue and should be resolved by https://github.com/chmln/flatpickr/commit/79075a739c5823ea90b4438a0c64ebcc1ae17d7f
Please feel free to re-open and provide a fiddle if the issue occurs again.
Thank you :+1:


Add fences to mutex methods

Without the fences the Mutex doesn't behave as expected.
Given this example:
static FOO: Mutex<RefCell<bool>> = Mutex::new(RefCell::new(false));

pub fn main() {
    let mut count = 0;
    loop {
        let cs = unsafe { CriticalSection::new() };
        if *FOO.borrow(cs).borrow() {
            break
        }
        count += 1;
    }
    let mut black_box = 0;
    unsafe { ptr::write_volatile(&mut black_box as *mut _, count); }
}

#[no_mangle]
pub extern "Rust" fn bar() {
    let cs = unsafe { CriticalSection::new() };
    *FOO.borrow(cs).borrow_mut() = true;
}

It's expected that the value of FOO will be evaluated at each loop pass, right now that doesn't happen, FOO is only evaluated once and if the value is false then the function branchs to an infinite loop:
.LBB1_2:
        b       .LBB1_2

godbolt link (Remove the comment to add the fence and see the difference)
I decided to go for a fence instead of a compiler_fence to cover the cases where the processors have a cache or are out of order. We could change SeqCst for a pair of Acquire and Release, but then I think we would have to put one of them in the Drop implementation of the CriticalSection, but we can't really rely that drop will run (mem::forget), so I went with SeqCst, maybe I'm missing some other way...
It seems that we would need to yank previous versions, unfortunately.

@thalesfragoso Note that fences at present do not work on msp430. And I am not certain how to fix this as I don't handle the LLVM side of things for msp430 :/.

@cr1901 a compiler fence could be implemented/used for MSP430, it's just a type 0 of LLVM AtomicFence that lowers to nothing for x86 and ARM.

How are core library mutexes doing it wrt to acquire/release?
Mutexguards should have a similar problem, ain’t they?

How are core library mutexes doing it wrt to acquire/release?
Mutexguards should have a similar problem, ain’t they?

I think that in the case of the std::sync::MutexGuard they can rely on drop because if the guard doesn't get dropped the mutex will remain locked forever. That might also make sense for us, and I was going to try that today, but I realized that CriticalSection is Copy and because of that we can't implement Drop for it.

As discussed in the matrix chat, it seems that fence (instead of compiler_fence) is only needed when dealing with a multi master bus, which it's out of scope for this crate, so I changed it to use just a compiler_fence.
I also provided a solution for the msp430 case, but the one I found will only compile on nightly, but that seems to be the case in the msp430 crate too, so it seems okay. CC @cr1901
CC @adamgreig

@thalesfragoso I don't have a problem making bare_metal nightly on msp430; we can fix that later. The msp430 crate is indeed nightly for now and will likely be so until asm! stabilizes.
I want a second opinion though: cc: @pftbest and @awygle.

Could we just document that CriticalSection::new requires the caller ensure a compiler fence is inserted and not otherwise change the body? That way cortex-m and msp430 will continue to work (since both take actions that result in fences being inserted when creating a CS), and no new code is added here.
That doesn't resolve the get_mut() issue which I am not yet convinced we actually need to change but I'm certainly open to being wrong there. I'm also not sure if riscv effectively inserts a fence when disabling interrupts, as I don't really understand how its register modification works.

I also agree with @adamgreig, the fences should be added only when CriticalSection is created, not on every borrow. For example,  you obtained a critical section and then do 3 borrows in a row:
    let cs = ...
    let a = *FOO.borrow(cs).borrow();
    let b = *BAR.borrow(cs).borrow();
    let c = *FOO.borrow(cs).borrow();

You don't need a fence inserted in between each borrow here, because nothing else can change the values of FOO and BAR while you are holding a critical section token. Adding fences here would be a pessimisation, because compiler will no longer be able to see that a and c is the same exact value and optimize out second access to FOO.

I also agree with @adamgreig, the fences should be added only when CriticalSection is created, not on every borrow. For example, you obtained a critical section and then do 3 borrows in a row:

That's already the case.

That's already the case.

I missed that, sorry.

To summarise discussion in today's meeting on Matrix: we require a fence at the end of the critical section as well, because otherwise the compiler could re-order a store to after the CS finishes, which could race with another thread. Since the CS might be safely forgotten, there's no way to ensure this inside the CS type. Instead, we should add a safety precondition to the CS documentation to say that users (the architecture crates such as cortex-m, cortex-a, msp430, riscv, etc) must ensure a compiler fence is inserted immediately after entering and before leaving the CS.
Currently this is mostly the case, for example cortex-m uses either an FFI call or inline asm with a memory clobber to enable and disable interrupts, which has the effect of ensuring a suitable fence. We should make these fences explicit (although it's a shame that compiler_fence has a potential panic in debug builds).
So, the update to bare_metal can probably just be a safety documentation on CriticalSection, but the architecture crates will all need updating to ensure suitable fences are used.
I don't think this resolves the Mutex::get_mut() concern yet though. I'm not sure how that should best be resolved. Since it requires &mut self, there shouldn't be any way in safe Rust to trigger this problem anyway...

For a little historical context: https://github.com/rust-embedded/cortex-m/commit/a396a68a43e684b4388cfdcaa0caacbe0dcc4b71

As it was discussed in the meeting, it seems that the best approach to this problem is to add one more condition to the CriticalSection::new method and rely on the arch crates to implement it correctly. Moreover, a closure approach seems to deal with this better.
I'm closing this in favor of this new solution, bare-metal should only need to update its documentation.


SSL Error - 'certificate verify failed'

I am using the home assistant integration and am now getting SLL errors. This started on 12-21-2019.
`2020-01-16 17:47:27 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform duke_energy
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/contrib/pyopenssl.py", line 485, in wrap_socket
cnx.do_handshake()
File "/usr/local/lib/python3.7/site-packages/OpenSSL/SSL.py", line 1934, in do_handshake
self._raise_ssl_error(self._ssl, result)
File "/usr/local/lib/python3.7/site-packages/OpenSSL/SSL.py", line 1671, in _raise_ssl_error
_raise_current_error()
File "/usr/local/lib/python3.7/site-packages/OpenSSL/_util.py", line 54, in exception_from_error_queue
raise exception_type(errors)
OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen
chunked=chunked,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 376, in _make_request
self._validate_conn(conn)
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 994, in validate_conn
conn.connect()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 394, in connect
ssl_context=context,
File "/usr/local/lib/python3.7/site-packages/urllib3/util/ssl.py", line 370, in ssl_wrap_socket
return context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/local/lib/python3.7/site-packages/urllib3/contrib/pyopenssl.py", line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
timeout=timeout
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 720, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 436, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.duke-energy.com', port=443): Max retries exceeded with url: /form/Login/GetAccountValidationMessage (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 158, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/duke_energy/sensor.py", line 28, in setup_platform
config[CONF_USERNAME], config[CONF_PASSWORD], update_interval=120
File "/usr/local/lib/python3.7/site-packages/pydukeenergy/api.py", line 48, in init
if not self._login():
File "/usr/local/lib/python3.7/site-packages/pydukeenergy/api.py", line 137, in _login
response = self.session.post(LOGIN_URL, data=data, headers=headers, timeout=10)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 581, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 514, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='www.duke-energy.com', port=443): Max retries exceeded with url: /form/Login/GetAccountValidationMessage (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])")))`

Just saw this I will try to figure it out over the next couple days. Looks like they changed some of the code on the site which is why it isn't working I will have to get an updated version out. I will let you know what I find.

Any update on this?

I have looked at it some. Their API changed a little, but using the new one I still get SSL errors. I think something changed in a recent version of Python. I will have to look in to it some more.

I’m actually digging into it as well. I’ve noticed that on my MacBook, I’m getting SSL very errors in Chrome but not Firefox or Safari. It looks like there is some kind of misconfiguration error.
Also I noticed they changed the login from from “Login” to “SignIn”
Will Blanton
<EMAIL_ADDRESS>
On Feb 10, 2020, at 21:01, William Scanlon<EMAIL_ADDRESS>wrote:

I have looked at it some. Their API changed a little, but using the new one I still get SSL errors. I think something changed in a recent version of Python. I will have to look in to it some more.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I think you’re right. I’m noticing some SSL errors and it looks like a few URL slugs have changed as well. I’ll see if I can get something working.
Will Blanton
<EMAIL_ADDRESS>
On Feb 10, 2020, at 21:01, William Scanlon<EMAIL_ADDRESS>wrote:

I have looked at it some. Their API changed a little, but using the new one I still get SSL errors. I think something changed in a recent version of Python. I will have to look in to it some more.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Great! Glad you're taking a look. Yeah I noticed the signin/login thing too.
I didn't test in a browser interesting you're seeing an issue there...

Just created a pull request. It's my first time forking a repo, so hopefully I did it right and you can see the changes. I've got most of functional, at least I think so. But I was still getting a few errors. But feel free to look it over and see what you think.
On another note, I noticed you were scraping using BS4 to get the meter info from the usage analysis page, but I have NO CLUE how that ever worked. They are currently using javascript to fill that drop down list, so without using Selenium, I don't even know of a way to get those values using python. For that reason, I just added a way for the users to manually input their own meter numbers. Not ideal, but it gets it working.
Also added a way for the user to ignore SSL verification if they wish. It's still on by default, but it can be bypassed by using the "verify_ssl=False" flag in the constructor.


Create new space modal empty

Most likely related to the initialization bug that was in the 0.7 that caused the plugin not to load at all. Let me know if it's still happening after the update

v0.7.1: Same bug present (installed + restarted)

Thanks I’ve confirmed the bug is happening on mobile and Compact mode

On Mar 21, 2023, at 6:49 AM, dxcore35 @.***> wrote:
https://user-images.githubusercontent.com/7279156/226584457-edcf89b9-df9d-40b9-8afd-7c9fcfc48fe0.jpg
—
Reply to this email directly, view it on GitHub https://github.com/Make-md/makemd-preview/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFHKNQ5ZJ35BGSMIFO7WM3W5GBR5ANCNFSM6AAAAAAWCID7U4.
You are receiving this because you are subscribed to this thread.

Fixed in 0.7.2

On Mar 21, 2023, at 1:09 PM, Peter C @.***> wrote:
Thanks I’ve confirmed the bug is happening on mobile and Compact mode

On Mar 21, 2023, at 6:49 AM, dxcore35 @.***> wrote:
https://user-images.githubusercontent.com/7279156/226584457-edcf89b9-df9d-40b9-8afd-7c9fcfc48fe0.jpg
—
Reply to this email directly, view it on GitHub https://github.com/Make-md/makemd-preview/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFHKNQ5ZJ35BGSMIFO7WM3W5GBR5ANCNFSM6AAAAAAWCID7U4.
You are receiving this because you are subscribed to this thread.


Notification bubble for tabs, buttons, etc.

did this ever get implemented?

http://ionicframework.com/docs/api/directive/ionTab/
the badge attribute for tabs


Remove stack driver exporter

/area API
/area monitoring
/kind cleanup
@MontyCarter gave the clear that the stack driver exporter can be removed

Sent an email to the various mailing lists
knative-users - https://groups.google.com/g/knative-users/c/YEH0Y8QAaJ0
Knative-dev - https://groups.google.com/g/knative-dev/c/OAq4EJ4LEAU

/assign @dprotaso

Ok so that means we now will have opencensus and prometheus direct support only right?

@skonto yes

There hasn't been any objections so I'm going 'unhold' the PR


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #31 (0a87577) into main (23f0529) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #31   +/-   ##
=======================================
  Coverage   98.22%   98.22%
=======================================
  Files          19       19
  Lines         338      338
  Branches       33       33
=======================================
  Hits          332      332
  Misses          6        6

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Please update transifex glossary for German

Please translate feature in the glossary as "Objekt", not "Eigenschaft", Same applies to:
zoom -> zoom not vergrößern
area -> Fläche not Gebiet
menu -> menu not ""

@manfredbrandl can anybody update the glossary?  I haven't used this before, but I do see some of the languages are using it.  Let me know if you need special permission on Transifex.

@bhousel I will change the glossary if I get the required permissions to do so. See https://docs.transifex.com/setup/glossary/adding-terms

@manfredbrandl I just made you a coordinator for German language team. Let me know if you're able to update the glossary.

@bhousel thanks for the extra powers, i have updated the glossary to get fewer warnings. i did not succeed removing the warnings for 'feature' but others like 'zoom' vanished.

@bhousel I might have lost access to the glossary as part of transferting iD to the OpenStreetMap Organisation on transifex.

@manfredbrandl I still see you as a coordinator, but it looks like with the recent move, the glossary terms might not have moved over.  Can you try to re-add them?

@bhousel there is still a glossary because i get glossary warnings, but i cannot access it any more.

@manfredbrandl As far as I can tell the glossary is there, just empty.  What happens when you click on "Add Term" ?

Sorry, because of my monitor vertically I did not see "Add term" before. If I add a Term I see:

Great!  Looks like it is working.  As far as I can tell this is what the glossary does - it just warns you if your translation deviates too much from the ones in the glossary.


syntax/css.vim needs update

I took the latest css.vim syntax file and put it into /usr/share/vim/vim81/syntax/ but some keywords remain uncolored. For example:

If i have multiple attributes split over multiple lines:

background: url("./images/index/004.jpg")
no-repeat
center
fixed;

here for example fixed is colored diferently (wrong) than no-repeat and center (right).

or for example with this keywords:

backdrop-filter: blur(5px);

where in the first line backdrop-filter should be colored consistently, while only filter is colored while backdrop is not.

or this:

transition: backdrop-filter 2s;

where backdrop- is colored diferently than filter.
QUESTION: Is there anything that can be added to the css.vim in order to add some keywords manually or could anyone of the developer team do it?

did you contact the maintainer?

I did today.

FTR: https://github.com/JulesWang/css.vim

closing as fixed as of e7b1ea0276cc83cd5c612f3189a174a60d57b5ed
Note, upstream css syntax script is: https://github.com/jsit/css.vim


Porch-controllers is reporting watch not being available for packageRevisionResources

Porch-controllers is reporting the following for packageRevisionResources:
E0327 13:48:14.426003       1 reflector.go:140] pkg/mod/k8s.io/client-go@v0.26.9/tools/cache/reflector.go:169: Failed to watch *v1alpha1.PackageRevisionResources: the server does not allow this method on the requested resource (get packagerevisionresources.porch.kpt.dev)
Probably this is because there is no implementation of watch for packageRevisionResources in porch-server (packagerevisionresources.go).
The error log is probably triggered by controller-runtime's caching k8s client that places a watch on each of the resources that were requested from it.
This could be a problem with other operators as well that would want to modify the packageRevisionResources CRs.

https://github.com/nephio-project/porch/pull/55

The code is merged and the issue is not reproducible after the merge. Closing the ticket.


Can intent filter work in custom tabs?

Use the same link, my intent filter can't work at custom tabs but works at chrome.
Do custom tabs support intent filter?
sincerely

please file bugs using the link at the bottom of readme
also please provide more details/code what you are trying to do and what does not work

Same here, not sure it's a bug or not.
For example, I declare an intent-filter below.
            <intent-filter>
                <action android:name="android.intent.action.VIEW" />

                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />
                <data
                    android:host="example.com"
                    android:scheme="https" />
            </intent-filter>

When click the scheme+host link in Chrome app, my app could receive the intent, a system intent chooser will show up for asking me next behavior, but not with custom tabs. Not sure it's a normal behavior or not.
In WebView, we could control the url handling behavior via WebChromeClient.

For example, I install both facebook app and chrome app on my phone.
When I click this link in facebook "https://www.facebook.com/juksymag/videos/10153239052963937/?__mref=message_bubble" via chrome, system intent chooser will show up and let me choose open the link by facebook or by chrome. But when I click the same facebook link via custom tabs, system intent chooser won't show up and just open the link by custom tabs.

Custom tab's current intent policy is:

If the user has previously selected a default external app to handle a type of url, then we respect the users' choice and send the url to the app. (By saying default I mean the user once selected an app as the default handler in an intent picker before, or In M+ the app is verified by the OS that it owns a url).
If the url has a custom scheme that chrome is not capable to handle (such as market://), chrome will always fire an intent.
Otherwise custom tab will not open the external app and will instead stay in the tab. Intent picker is never shown in a custom tab.

Therefore what I recommend you for now is to devise a custom scheme for you app and handle that url yourself. Then your app is guaranteed to be opened.


Expose view data (year, month)

I'm Submitting a ...

[ ] Bug report
[x] Feature request
[ ] Support request

Steps to Reproduce

We are developing a datetime range picker based on 'react-datetime', could you please expose the view data to outside so we can control '>', '<'? The view data here means the year and month value when user navigates through the datetime picker.

Looks like  @DaanDD code was merged 3 days ago, https://github.com/YouCanBookMe/react-datetime/pull/520, I will try it out. Thanks.

@ivyyangthl That PR has not been merged yet. Feel free to refer to my personal repo though. The code works for me.

Thanks @DaanDD. Actually, it's this PR: https://github.com/YouCanBookMe/react-datetime/pull/508. But I guess it's better to wait after fix on https://github.com/YouCanBookMe/react-datetime/pull/520 is merged? I will try your personal repo for now.


Crash on login - Cannot read properties of undefined (reading 'overworld')

On startup, I get the following error:
C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main>node main.js
Using chat settings: { model: 'gpt-4o-mini', api: 'openai' }
Using embedding settings: { api: 'openai' }
Logging in...
Mineflayer detected that you are using a deprecated event (physicTick)! Please use this event (physicsTick) instead.
C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\minecraft-protocol\src\transforms\framing.js:67
          } else { throw e }
                   ^

TypeError: Cannot read properties of undefined (reading 'overworld')
    at handleRespawnPacketData (C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\mineflayer\lib\plugins\game.js:46:63)
    at Client.<anonymous> (C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\mineflayer\lib\plugins\game.js:80:5)
    at Client.emit (node:events:531:35)
    at emitPacket (C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\minecraft-protocol\src\client.js:83:12)
    at FullPacketParser.<anonymous> (C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\minecraft-protocol\src\client.js:112:9)
    at FullPacketParser.emit (node:events:519:28)
    at addChunk (C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\protodef\node_modules\readable-stream\lib\_stream_readable.js:279:12)
    at readableAddChunk (C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\protodef\node_modules\readable-stream\lib\_stream_readable.js:262:11)
    at Readable.push (C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\protodef\node_modules\readable-stream\lib\_stream_readable.js:228:10)
    at Transform.push (C:\Users\Eesa\Downloads\mindcraft-main\mindcraft-main\node_modules\protodef\node_modules\readable-stream\lib\_stream_transform.js:132:32)

Node.js v20.17.0
Agent process exited with code 1 and signal null
Agent process exited too quickly. Killing entire process. Goodbye.

with settings.js
export default
{
    "minecraft_version": "1.20.4", // supports up to 1.20.4
    "host": "redacted", // or "localhost", "your.ip.address.here"
    "port": 25769,
    "auth": "offline", // or "microsoft"

    "profiles": [
        "./andy.json",
        // add more profiles here, check ./profiles/ for more
        // more than 1 profile will require you to /msg each bot indivually
    ],
    "load_memory": false, // load memory from previous session
    "init_message": "Say hello world and your name", // sends to all on spawn

    "allow_insecure_coding": true, // allows newAction command and model can write/run code on your computer. enable at own risk
    "code_timeout_mins": 10, // minutes code is allowed to run. -1 for no timeout

    "max_commands": -1, // max number of commands to use in a response. -1 for no limit
    "verbose_commands": true, // show full command syntax
    "narrate_behavior": true, // chat simple automatic actions ('Picking up item!')
}

It is worth mentioning that the server runs viabackwards, on 1.21.
The bot on login is also assigned the username +andy, rather than andy due to a mod that allows for both online and offline players.

Source code of the mod is available on request.

Using the same config as the bot on a real client - offline login, 1.20.4, and connecting to the server with ViaBackwards works without issue.

I have the same issue


Detect when a site is behind cloudflare

It seems like there is an easy way to detect when a site is behind cloudflare.
This can be done by checking:

That the cf-ray header is present
That the IP is in the range of the known cloudflare IPs: http://cloudflare.com/ips

It would be useful to annotate measurements of this sort to reduce false positives especially when they are via HTTPS. If we do reach cloudflare it means that it's most likely not blocked.
This is related to: https://github.com/TheTorProject/ooni-pipeline/issues/84

Hi
I think i can help you with this.
Do you need this as a standalone tool or it should be integrated with the tor browser?

If we do reach cloudflare it means that it's most likely not blocked

FTR, sometimes it's not the case:

ISPs interfere with the SSL encrypted traffic between Cloudflare’s Point-of-Presence in Cairo and the backend servers of sites (psiphon.ca, purevpn.com and ultrasawt.com) hosted outside of Egypt.
— The State of Internet Censorship in Egypt

For Cloudflare, there's also the Server: header:
$ curl -s -D - https://www.zendesk.com/ | grep -i -e "Server"
server: cloudflare

I wouldn't worry too much about the connection between the point of presence and the origin. That's only an issue if the origin is not encrypted. And if the interference exists, you should still be able to see that between the client and the reverse proxy.

That's only an issue if the origin is not encrypted

Do you mean TLS-to-Origin or some more sophisticated set up?
I ask as SNI of the webservice was sent from PoP to origin as-is in Full (strict) mode when I checked that back in April 2019 due to similar concerns.


Module not found: Error: Cannot resolve module 'react-foundation-apps/lib/modal'

How can I use modal?

:+1:

if you are using browserify/webpack please make sure .jsx extension is handled in the config files


Update database-commons, jdbc, mssqlserver, ... to 1.17.0

Updates

org.testcontainers:database-commons
org.testcontainers:jdbc
org.testcontainers:mssqlserver
org.testcontainers:mysql
org.testcontainers:oracle-xe
org.testcontainers:postgresql
org.testcontainers:testcontainers

from 1.16.3 to 1.17.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.testcontainers" } ]

labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #626.


Python 3.6 is out

Also, setup.py says Python 2.6 is supported so it should be tested too. Is there a special reason not to do so? (I'm not using Python 2.6.)


Automated cherry pick of #4685: Force create cni folders when starting Windows containerd

Cherry pick of #4685 on release-1.10.
#4685: Force create cni folders when starting Windows containerd
For details on the cherry pick process, see the cherry pick requests page.

/test-windows-containerd-e2e
/test-windows-containerd-conformance
/test-windows-containerd-networkpolicy

/test-windows-containerd-conformance
/test-windows-containerd-networkpolicy

/test-windows-containerd-networkpolicy


Buttons to get the app

More beautiful button for google play and a new one for fdroid ;)

Nice! thanks!


tests: Build failure

I'm unable to build with tests; the following output is printed when I try to build:
https://pastebin.com/raw/nrWTd6dL
As a workaround, I'm able to build if I configure like
./configure --disable-bench --disable-tests

https://github.com/BSHA3/bsha3/pull/18 fixes this for me

bench still gets stuck for me on MacOS:
3 warnings generated.
  CXX      bench/bench_bitcoin-ccoins_caching.o
  CXX      bench/bench_bitcoin-gcs_filter.o
  CXX      bench/bench_bitcoin-merkle_root.o
  CXX      bench/bench_bitcoin-mempool_eviction.o
  CXX      bench/bench_bitcoin-verify_script.o
  CXX      bench/bench_bitcoin-base58.o
  CXX      bench/bench_bitcoin-bech32.o
  CXX      bench/bench_bitcoin-lockedpool.o
  CXX      bench/bench_bitcoin-prevector.o
  CXX      bench/bench_bitcoin-coin_selection.o
  CXXLD    bench/bench_bitcoin
Undefined symbols for architecture x86_64:
  "_evhttp_uridecode", referenced from:
      urlDecode(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbitcoin_server.a(libbitcoin_server_a-httpserver.o)
  "_event_enable_debug_logging", referenced from:
      UpdateHTTPServerLogging(bool) in libbitcoin_server.a(libbitcoin_server_a-httpserver.o)
ld: symbol(s) not found for architecture x86_64

I seem to have latest libevent though...
➜  bsha3 git:(b0208b90f) ls /usr/local/lib/libevent-2.1.6.dylib
libevent-2.1.6.dylib@           libevent_extra.la*
libevent-2.2.1.dylib*           libevent_openssl-2.1.6.dylib@
libevent.a@                     libevent_openssl.a@
libevent.dylib@                 libevent_openssl.dylib@
libevent.la*                    libevent_pthreads-2.1.6.dylib@
libevent_core-2.1.6.dylib@      libevent_pthreads-2.2.1.dylib*
libevent_core-2.2.1.dylib*      libevent_pthreads.a@
libevent_core.a@                libevent_pthreads.dylib@
libevent_core.dylib@            libevent_pthreads.la*
libevent_core.la*               libleveldb.a
libevent_extra-2.1.6.dylib@     libleveldb.dylib*
libevent_extra-2.2.1.dylib*     libleveldb.dylib.1*
libevent_extra.a@               libleveldb.dylib.1.20*
libevent_extra.dylib@

brew install libevent:
Warning: libevent 2.1.8 is already installed and up-to-date
To reinstall 2.1.8, run `brew reinstall libevent`

I've tried uninstalling and reinstalling with homebrew, but no luck. Does it want me to downgrade?

Resolved; bench-tests are the remaining trouble


response_format with regex does not seem to work

Describe the bug
When passing a response_format of type regex to chat_completion, the output does not always respect the format.
Reproduction
This does not follow the regex:
from huggingface_hub import InferenceClient

client = InferenceClient("meta-llama/Meta-Llama-3.1-8B-Instruct")

output = client.chat_completion([{"role": "user", "content": "ok"}], response_format={"type": "regex", "value": ".+?\n\nCode:+?"})

print(output.choices[0].message.content)

But going through OpenAI Messages API does work:
url = "https://api-inference.huggingface.co/models/meta-llama/Meta-Llama-3.1-8B-Instruct/v1"

from openai import OpenAI

# init the client but point it to TGI
client = OpenAI(
    base_url=url,
    api_key="*"
)

chat_completion = client.chat.completions.create(
    model="tgi",
    messages=[
        {"role": "user", "content": "ok"}
    ],
    response_format={"type": "regex", "value": ".+?\n\nCode:+?"}
)
print(chat_completion.choices[0].message.content)

Logs
No response
System info
Copy-and-paste the text below in your GitHub issue.

- huggingface_hub version: 0.24.2
- Platform: macOS-14.1-arm64-arm-64bit
- Python version: 3.10.14
- Running in iPython ?: Yes
- iPython shell: ZMQInteractiveShell
- Running in notebook ?: Yes
- Running in Google Colab ?: No
- Token path ?: /Users/aymeric/.cache/huggingface/token
- Has saved token ?: True
- Who am I ?: m-ric
- Configured git credential helpers: osxkeychain, store
- FastAI: N/A
- Tensorflow: N/A
- Torch: 2.3.0
- Jinja2: 3.1.4
- Graphviz: N/A
- keras: N/A
- Pydot: N/A
- Pillow: 10.3.0
- hf_transfer: N/A
- gradio: 4.38.1
- tensorboard: N/A
- numpy: 1.26.4
- pydantic: 2.7.1
- aiohttp: 3.9.5
- ENDPOINT: https://huggingface.co
- HF_HUB_CACHE: /Users/aymeric/.cache/huggingface/hub
- HF_ASSETS_CACHE: /Users/aymeric/.cache/huggingface/assets
- HF_TOKEN_PATH: /Users/aymeric/.cache/huggingface/token
- HF_HUB_OFFLINE: False
- HF_HUB_DISABLE_TELEMETRY: False
- HF_HUB_DISABLE_PROGRESS_BARS: None
- HF_HUB_DISABLE_SYMLINKS_WARNING: False
- HF_HUB_DISABLE_EXPERIMENTAL_WARNING: False
- HF_HUB_DISABLE_IMPLICIT_TOKEN: False
- HF_HUB_ENABLE_HF_TRANSFER: False
- HF_HUB_ETAG_TIMEOUT: 10
- HF_HUB_DOWNLOAD_TIMEOUT: 10

cc @Wauplin this follows up on #2383.

Hi @aymeric-roucher, I've made some tests with the reproducible example you've shared. I do think this is a cache issue that has to be fixed either in Inference API or TGI directly. The only difference between OpenAI and InferenceClient clients in your example is that in the first case model="tgi" is passed while in the second model="meta-llama/Meta-Llama-3.1-8B-Instruct" is passed. When I use InferenceClient and also pass model="tgi" (with base_url pointing to Llama 3.1), then the regex works as expected.
I also tested the failing case with "ok 2" instead of "ok" and the answer was correctly using the regex.
Finally, I tested to disable the cache with InferenceClient(..., headers={"x-use-cache": "0"} and the answer was correctly using the regex, which implies the problem comes from an invalid cached answer.
I then tried to reproduce the error by sending a random string twice. First time without a regex (to warm-up the cache) and second time with the regex (to test if it would reuse the cache). I did not manage to reproduce the bug with this technique.
I don't know what is specific with the "ok" message and how it got an invalid answer cached. This is not an huggingace_hub.InferenceClient bug but it still needs to be investigated server-side cc @Narsil @OlivierDehaene

The cache key is computed by hashing the entire input (including parameters so including the regex).
This is unlikely to be a cache issue.
The invalid answer might have been cached, but it seems more a case of your regex formatting was ignored.
I think it's possible that some regex can be ignored in some circumstances (basically to avoid critical failure).
This however is not intended behavior.
If you're able to reproduce that'd help a lot.

@Narsil I've been able to reproduce it with cache disabled by repeating the exact same request until it fails:
from huggingface_hub import InferenceClient

client = InferenceClient("meta-llama/Meta-Llama-3.1-8B-Instruct", headers={"x-use-cache": "0"})

for i in range(50):
    output = client.chat_completion(
        [{"role": "user", "content": "ok"}],
        response_format={"type": "regex", "value": ".+?\n\nCode:+?"},
    )
    answer = output.choices[0].message.content

    if "Code:" in answer:
        print(f"Iteration {i}: OK")
    else:
        print(f"Iteration {i}: NOT OK\n{answer}")
        break

which outputs:
Iteration 0: OK
Iteration 1: OK
Iteration 2: OK
Iteration 3: OK
Iteration 4: OK
Iteration 5: OK
Iteration 6: NOT OK
It seems like you're ready to chat. Is there something specific you'd like to talk about or ask about? I can help with any questions or just have a conversation if you'd like. What's on your mind?  Would you like some suggestions? I could share some interesting topics if you are interested? like how the processor works, Some conspiracy theories or fun facts. let me know! :). There are some space news updates. Or there have been some epilepsy clues about satellites, other

Though it's not reproducing the error 100% of the time, it's still happening once every few requests.

Calling in @drbh on this. I know it can happen, I didn't expect 6 iteration would be enough to trigger.


test issue

This PR's title doesn't match our requirement.
Please make sure your title includes the corresponding Jira id.
@alabulei1, please update it.


Floating label plugin should hide placeholder

Reproduction
https://formkit.link/4018da7bad6990d43c4237fbe28f75bf
Describe the bug
The floating label plugin should hide the placeholder automatically to avoid a collision. 😄
Solutions given:
[data-floating-label="true"]  .formkit-input:not(:focus)::placeholder { color: transparent; }

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

Here's a playground with the recommended solution in action:
Hiding placeholders: https://formkit.link/bbbc68eec760560038cf2ecbe494c4a7
Hiding placeholders until focus: https://formkit.link/2b1814879047a5cda0d41f27e84ecec9
We'll likely end up adding the first one to the default styles that users import. Thanks for opening the issue!

@andrew-boyd the CSS solution doesn't work properly for example on the autocomplete or the date picker 🙂

This should be working now — including across Pro inputs — on the next tag.

@andrew-boyd you're awesome!! Thank you very much 🙏


Axum Integration

Hello there everybody!
I have successfully made a functional server and I want to serve request using Axum for a project I'm building. For Http1 and 2 The axum documentation states that this is the way to go for serving an axum router:
let hyper_service = hyper::service::service_fn(
                        move |request: axum::extract::Request<Incoming>| {
                            // We don't need to call `poll_ready` since `Router` is always ready.
                            let http_v = request.version();
                            println!("HTTP version: {http_v:?}");
                            router.clone().call(request)
                        },
                    );

hyper_util::server::conn::auto::Builder::new(TokioExecutor::new())
                        .serve_connection(h3_conn, hyper_service);

Are there any implementations for http3 here? I won't have a streaming request but I will have streaming responses. Are there any documentation on writing an http3 builder from scratch? Or are there any ways for me to create a Request from a Request and RequestStream to be used to cal the hyper_service (I think that this may solve all the problems i'm having)? Any help is welcomed :)

This is the code I've managed to put together:
use axum::handler::HandlerWithoutStateExt;
use axum::Router;
use bytes::{Bytes, BytesMut};
use http::{Request, Response, StatusCode, Version};
use rustls::pki_types::{CertificateDer, PrivateKeyDer};
use std::path::Path;
use std::{net::SocketAddr, path::PathBuf, sync::Arc};
use structopt::StructOpt;
use tokio::{fs::File, io::AsyncReadExt};
use tracing::{error, info, trace_span};

use h3::{error::ErrorLevel, quic::BidiStream, server::RequestStream};
use h3_quinn::quinn::{self, crypto::rustls::QuicServerConfig};
use hyper::body::Incoming;
use hyper_util::rt::TokioExecutor;
use tokio::net::UdpSocket;
use tower::buffer::Buffer;
use tower::{Service, ServiceExt};

static ALPN: &[u8] = b"h3";

pub async fn serve(router: axum::Router) -> Result<(), Box<dyn std::error::Error>> {
    tracing_subscriber::fmt()
        // .with_env_filter(tracing_subscriber::EnvFilter::from_default_env())
        .with_span_events(tracing_subscriber::fmt::format::FmtSpan::FULL)
        .with_writer(std::io::stderr)
        .with_max_level(tracing::Level::INFO)
        .init();

    let certificate_path = Path::new("certs/server.cert");
    let private_key = Path::new("certs/server.key");

    if !certificate_path.exists() || !private_key.exists() {
        let (ca_cert, ca_key) = crate::cert::new_ca();
        let (key, cert) = crate::cert::new_end_entity(&ca_cert, &ca_key);

        std::fs::create_dir_all("certs").unwrap();
        std::fs::write(certificate_path, cert.der()).unwrap();
        std::fs::write(private_key, key.serialize_der()).unwrap();

        std::fs::write("certs/ca.cert", ca_cert.der()).unwrap();
        std::fs::write("certs/ca.key", ca_key.serialize_der()).unwrap();
    }

    info!("Loading keys");
    // both cert and key must be DER-encoded
    let key = PrivateKeyDer::try_from(std::fs::read(private_key)?)?;
    let cert = CertificateDer::from(std::fs::read(certificate_path)?);
    //
    let mut tls_config = rustls::ServerConfig::builder()
        .with_no_client_auth()
        // .with_client_cert_verifier()
        .with_single_cert(vec![cert], key)?;

    tls_config.max_early_data_size = u32::MAX;
    tls_config.alpn_protocols = vec![ALPN.into()];

    let server_config =
        quinn::ServerConfig::with_crypto(Arc::new(QuicServerConfig::try_from(tls_config)?));

    // let udp_socket = UdpSocket::bind("[::1]:58097").await?;

    let endpoint = quinn::Endpoint::server(server_config, "[::1]:3000".parse()?)?;
    println!("serving on https://localhost:3000");

    // info!("listening on {}", opt.listen);

    // handle incoming connections and requests

    while let Some(new_conn) = endpoint.accept().await {
        trace_span!("New connection being attempted");

        let router = router.clone();

        tokio::spawn(async move {
            match new_conn.await {
                Ok(conn) => {
                    info!("new connection established");

                    let mut h3_conn = h3::server::Connection::new(h3_quinn::Connection::new(conn))
                        .await
                        .unwrap();

                    loop {
                        match h3_conn.accept().await {
                            Ok(Some((req, stream))) => {
                                info!("new request: {:#?}", req);
                                let router = router.clone();

                                tokio::spawn(async move {
                                    if let Err(e) =
                                        handle_request(req, stream, router.clone()).await
                                    {
                                        error!("handling request failed: {}", e);
                                    }
                                });
                            }

                            // indicating no more streams to be received
                            Ok(None) => {
                                break;
                            }

                            Err(err) => {
                                error!("error on accept {}", err);
                                match err.get_error_level() {
                                    ErrorLevel::ConnectionError => break,
                                    ErrorLevel::StreamError => continue,
                                }
                            }
                        }
                    }
                }
                Err(err) => {
                    error!("accepting connection failed: {:?}", err);
                }
            }
        });
    }

    println!("serving on https://localhost:3000");

    // shut down gracefully
    // wait for connections to be closed before exiting
    endpoint.wait_idle().await;

    Ok(())
}

async fn handle_request<T>(
    req: Request<()>,
    mut stream: RequestStream<T, Bytes>,
    tower_service: Router,
) -> Result<(), Box<dyn std::error::Error>>
where
    T: BidiStream<Bytes>,
{
    info!("new request: {:#?}", req);
    let mut body = vec![];

    while let Ok(Some(data)) = stream.recv_data().await {
        use bytes::Buf;
        let data = data.chunk();

        body.extend_from_slice(data);
    }

    stream
        .send_response(
            Response::builder()
                .status(500)
                .header("content-type", "text/plain")
                .version(Version::HTTP_3)
                .body(())
                .unwrap(),
        )
        .await
        .unwrap();

    let buf = "Hello world!".as_bytes().to_vec();

    stream.send_data(Bytes::from(buf)).await.unwrap();

    info!("Done");

    Ok(stream.finish().await?)
}

Our first step will be to integrate this repo into hyper, so that you can then make easy use in something like Axum. But it's not an aim for this repo directly.
The hyper::proto::h3 code will include this body integration.

I understand, but I wanted to do it now as I need a http3 server now. This worked, I just don't known if there are any apparent flaws that need to be fixed.
Could you perhaps point me somewhere that I will get help?


issue#1478 seems to persist in pyaedt 0.7: Changing plating thickness of Vias does not have effect on exported files to Maxwell (Vias are exported filled)

Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug
Hello,
it appears that issue #1478 is still persistent in 0.7. When trying to export from EDB to Maxwell the vias are filled regardless of the assigned plating thickness
Steps To Reproduce
import pyaedt
Version="2022.2"
ExportName="Export"
filename="Test.aedb"
PlatingThickness=0.1E-3
path=os.path.abspath(os.getcwd())
aedb_path =os.path.join(path,filename).replace('\','\\')
HideSiWave=True
edb = pyaedt.Edb(edbversion=Version, edbpath=aedb_path)
edb.save_edb() # Save the edb file
options_config = {
'LAUNCH_MAXWELL' : 0,
'NUM_PADS_FACET_COUNT': 8,
'NUM_ANTIPAD_FACET_COUNT': 8,
'DEFAULT_SOLDERBALL_FACET_COUNT' : 8,
'VIA_SEGMENTS' : 8,
'DEFAULT_BONDWIRE_FACET_COUNT' : 6,
'UNITE_NETS' : 0,
'EXCLUDE_TERMINALS_FROM_UNITE' : 1,
'SIMPLY_VIA_MODEL' : 0,
'IGNORE_DIELECTRICS' : 0,
'SEPARATE_DIELECTRICS' : 1,
'UNITE_LAYERS_WITH_SAME_MATERIALS' : 1,
'IGNORE_UNCONNECTED_PADS' : 0,
'CLIP_TRACES' : 0,
'CUT_DIELECTRICS' : 0,
'CREATE_SHEET_BODIES' : 0,
'GENERATE_TERMINALS' : 0,
'IGNORE_PLANES_WITH_AREA_LESS_THAN_THRESOLD' : 1,
'IGNORE_FLOAT_BODIES' : 0,
'MIN_PLANE_AREA' : 0.358979,
'MIN_EDGE_LENGTH_PADS' : '1um',
'MIN_EDGE_LENGTH_PLANES' : '1um',
'MIN_EDGE_LENGTH_TRACES' : '1um',
'MIN_DIELECTRIC_EDGE_LENGTH' : '10um',
'DIELECTRIC_EXPANSION_FACTOR' : 0.100000,
'IGNORE_HOLES' : 0,
'MIN_HOLE_AREA' : 0.358979,
'REMOVE-PLATING_TAILS' : 0,
'SUBTRACT_METAL_FROM_SUBSTRATE' : 0,
'DISCRETIZE_ARCS' : 0,
'CHOP_TRACE_ENDS' : 0,
'AIRBOX_THICKNESS_FACTOR' : 1.100000,
'AIRBOX_PAD_AMOUNT_PLUS_Z' : 0.500000,
'AIRBOX_PAD_AMOUNT_MINUS_Z' : 0.500000,
'PORT_PAD_AMOUNT' : 0.500000,
'CREATE_PORTS_FOR_PWR_GND_NETS' : 0,
'PORTS_FOR_PWR_GND_NETS' : 0,
'LAUNCH_HFSS' : 0,
'USE_CAUSAL_MATERIALS' : 1,
'AUTO_DC_THICKNESS' : 0,
'SOLVE_CAPACITANCE' : 0,
'SOLVE_DC_RESISTANCE' : 0,
'SOLVE_DC_INDUCTANCE_RESISTANCE' : 0,
'SOLVE_AC_INDUCTANCE_RESISTANCE' : 0,
'SOLVE_PROJECT' : 0,
'LAUNCH_Q3D' : 0,
'ASSIGN_SOLDER_BALLS_AS_SOURCES' : 0,
'Q3D_MERGE_SOURCES' : 0,
'Q3D_MERGE_SINKS' : 0,
'ACIS_VERSION' : 0
}
edb.write_export3d_option_config_file(path, options_config)
PadStackNames=[x for x in edb.core_padstack.padstacks] #API CALL: read all padstacks
for x in PadStackNames:
try:
edb.core_padstack.padstacks[x].hole_plating_ratio=0
edb.core_padstack.padstacks[x].hole_plating_thickness=PlatingThickness # API CALL: set plating thickness
except Exception as e:
    continue

edb.save_edb()
edb.export_maxwell(path_to_output=path,aedt_file_name=ExportName,hidden=HideSiWave)
edb.save_edb() #API CALL: Save file
edb.close_edb()
Which Operating System are you using?
Windows
Which Python version are you using?
3.7
Installed packages
C:\temp>python -m pip freeze
ansys-pythonnet==3.1.0rc3
cffi==1.16.0
clr-loader==0.2.6
defusedxml==0.7.1
fonttools==4.47.2
fpdf2==2.7.7
numpy==1.26.3
pandas==2.2.0
pillow==10.2.0
plumbum==1.8.2
psutil==5.9.8
pyaedt==0.7.10
pycparser==2.21
python-dateutil==2.8.2
pytz==2023.3.post1
pywin32==306
rpyc==5.3.1
six==1.16.0
tzdata==2023.4

@Jan-Hammer In the Closed Issue, @maxcapodi78 mentioned that it was a limitation in SIWave API, so PyAEDT can not solve it until SIwave does not expose the method.
I am not sure if it is fixed, but if it is, you will need to update to a new Ansys version.
Please @ring630 @svandenb-dev , this is an EDB related issue, could you help?
Thanks

@Samuelopez-ansys may be we can implement this in PyAEDT.

@Jan-Hammer it looks like there is no keyword in configure file to toggle 100% via fill checkbox. I am waiting answer from development.

@Jan-Hammer the keyword is TOTAL_VIA_FILL. The SIwave documetation will be updated. By setting it to 0, the via will have a hole  in maxwell.
options_config = {'TOTAL_VIA_FILL' : 0}


Missing function for 2 "share" buttons

Please see the attached screenshot
The email and whatsapp button work as intended if you click on the "Share" icon for an entry in the URL list, but not if you click on the "Statistics" icon and try to use these buttons at the "Sharing" tab.

That's not a YOURLS feature, this is probably a plugin


feat: add DoneOps to adopters page

Working on https://6398a6856cecae5d65863485--fluxcd.netlify.app/adopters/, so merging now! Thanks.

The build passes in Netlify now, but it doesn't seem to report this back to GitHub, or something. :man_shrugging:

hrrmmm the logo isn't updated on the support page. are netlify builds just really behind?


Module 4 exercises [Barbara Adomaa Kumi]

WS2_M4E1_Barbara Adomaa Kumi.docx

Well done, Barbara. You clearly grasped the material outlined in Module 4 and successfully applied it to these exercises. Thank you for your participation! Please be sure to fill out the post-Module survey before you begin the next Module.


Add default user to Makefile run and mount /srv externally

Hi, if you want strictly atomic commits you could also separate the addition of the .gitignore file into a separate commit (its a different change thematically, however I don't insist on that much, it's your call :) ).


user-panel-api-gateway not found

Here's the error:
1>#11 [build  3/10] COPY [src/3-ApiGateways/UserPanel/ApiGateway/ApiGateway.csproj, src/3-ApiGateways/UserPanel/ApiGateway/]
1>#11 sha256:159fb92e71e1b6c3cce8345df51a00e7c02323a4754e65d3c55d834adfbf41ee
1>#11 ERROR: "/src/3-ApiGateways/UserPanel/ApiGateway/ApiGateway.csproj" not found: not found
1>------
1> > [build  3/10] COPY [src/3-ApiGateways/UserPanel/ApiGateway/ApiGateway.csproj, src/3-ApiGateways/UserPanel/ApiGateway/]:
1>------
1>failed to compute cache key: "/src/3-ApiGateways/UserPanel/ApiGateway/ApiGateway.csproj" not found: not found
1>Service 'user-panel-api-gateway' failed to build : Build failed
1>C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Sdks\Microsoft.Docker.Sdk\build\Microsoft.VisualStudio.Docker.Compose.targets(523,5): error DT1001: Service 'user-panel-api-gateway' failed to build : Build failed

Hi @lurudong
Many Thanks for your report.
The problem was related to a case-sensitive folder name issue.
It was "ApiGateway" on my PC, but "ApiGateWay" on GitHub.
I would be happy to help you with any other question related to the project.
Have a good day.

Hi @hamed-shirbandi
我的电脑上是"ApiGateway"

Hi @hamed-shirbandi
Ok
Thank you!!!


Upgrading from JAXB 4.0.1 to 4.0.2 throws ClassNotFoundException

Caused by: java.lang.ClassNotFoundException: org.graalvm.nativeimage.hosted.Feature
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 30 more

Nothing jaxb code related in the stack trace.

mvn dependency:tree comparision can be good start and perhaps can lead to finding real cause eventually

Thanks for the suggestion @lukasj
I did what you proposed and found the artefact that causes the issue. It's jaxb-runtime, version 4.0.2.

Also note that I do not know what your app is, how/if it manages classloading, on which JDK and how exactly it is expected to run, during which operation does the exception appear, so whatever I say is just a blind guess - at least till steps to reproduce are provided. Anyway, one obvious workaround is to add graal-sdk to the classpath or modulepath, another is to lower versions of jaxb-runtime dependencies

After analyzing this myself this stems from JAXB upgrading a dependency. There was NOTHING in the application code that caused the issue. To make it work I had to exclude the angus-activation that was updated.
For folks hitting this issue I changed my dependency to be:
       <dependency>
            <groupId>org.glassfish.jaxb</groupId>
            <artifactId>jaxb-runtime</artifactId>
            <version>4.0.2</version>
            <scope>compile</scope>
            <exclusions>
                <exclusion>
                    <groupId>org.eclipse.angus</groupId>
                    <artifactId>angus-activation</artifactId>
                </exclusion>
            </exclusions>
       </dependency>

The question on how to reproduce the issue with standalone reproducer remains

@lukasj maybe this one is a problem?
https://github.com/eclipse-ee4j/angus-activation/blob/92299568693522c92709fdca9068358556603539/activation-registry/src/main/java/org/eclipse/angus/activation/nativeimage/AngusActivationFeature.java#L14
Seemingly this class is being picked up by a non-Graal JVM too, and then it obviously all comes down.

@arjantijms WHY is that class being picked up, by who and when? It is not - or should not be - reachable by any other VM just by itself

@lukasj After some investigation I managed to obtain some more details.
It concerns Piranha Web Profile, which can be found here: https://github.com/piranhacloud/piranha/tree/current/dist/webprofile
The issue occurs when annotation scanning takes place, which looks at all classes in the class loader. That's why it picks up that class.
So:
WHY - Annotation scanning looks at all classes
Who - Piranha Web Profile, probably some annotationscan module
When - When deploying an application
Reproducer:
Checkout https://github.com/manorrock/persian (https://github.com/manorrock/persian.git)
Revert the exclusion in the POM file
Build using mvn clean install
Run using  mvn piranha:run

missing parts of the stacktrace which clearly identify the WHO part of the problem - shouldn't this been part of the initial report?:
        at cloud.piranha.resource.impl.DefaultResourceManagerClassLoader.loadClass(DefaultResourceManagerClassLoader.java:127)
...
        at cloud.piranha.extension.annotationscan.AnnotationScanInitializer.loadClass(AnnotationScanInitializer.java:130)
        at cloud.piranha.extension.annotationscan.AnnotationScanInitializer.lambda$onStartup$2(AnnotationScanInitializer.java:113)
...
        at cloud.piranha.extension.annotationscan.AnnotationScanInitializer.onStartup(AnnotationScanInitializer.java:115)
        at cloud.piranha.core.impl.DefaultWebApplication.initializeInitializers(DefaultWebApplication.java:1002)
        at cloud.piranha.core.impl.DefaultWebApplication.initialize(DefaultWebApplication.java:931)
        at cloud.piranha.dist.webprofile.WebProfilePiranha.run(WebProfilePiranha.java:243)
        at java.base/java.lang.Thread.run(Thread.java:833)

to me this looks like a problem in how missing annotations are handled in Piranha Cloud.
Consider following case:

add provided dependency on jakarta.xml.ws:jakarta.xml.ws-api:4.0.0 to the persian webapp and add following service there:

@WebServiceProvider
public class Sample implements Provider<Source> {
    @Override
    public Source invoke(Source request) {
        return null;
    }
}

build and deploy the application

=> all one can see is following in the output and application seems to run fine:
INFO: WELD-000119: Not generating any bean definitions from com.manorrock.persian.rest.Sample because of underlying class loading error: Type Unable to load class: com.manorrock.persian.rest.Sample not found.  If this is unexpected, enable DEBUG logging to see the full error.

or following case:

add @WebServiceRef private Object svc; field to the RestApplicationBean class in the app
build and deploy the application

=> application seems to run fine (there's nothing in the log)

change the type of the field from Object to jakarta.xml.ws.Service
build and deploy the application

=> log shows following and application startup fails
WARNING: Initializer cloud.piranha.extension.weld.WeldInitializer failing onStartup
org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type RestApplicationBean with qualifiers @Default
  at injection point [UnbackedAnnotatedField] @Inject private com.manorrock.persian.rest.RestResource.application
  at com.manorrock.persian.rest.RestResource.application(RestResource.java:0)
WELD-001474: Class com.manorrock.persian.rest.RestApplicationBean is on the classpath, but was ignored because a class it references was not found: Unable to load class: jakarta.xml.ws.Service.

        at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
...

If piranha is able to handle missing @WebServiceRef/@WebServiceProvider annotations properly, why it is not able to handle other - eventually missing - ones?

@lukasj  Thank you for these details. This will help a LOT!


added warning and recovery guidance for bitlocker users

Resolves #392

Hmm, these steps should not be necessary. I have Bitlocker enabled on both my machines and didn't hit this issue. I think the right fix is to check for the right updates first before proceeding rather than disabling the hypervisor and re-enabling it later

What are the right updates? I'll happily retry but would appreciate a steer in the right direction.

I saw this mentioned on the forum and am trying to determine if and how it's related. Someone else said it fixed their problem, but I'm trying to figure out why. If that is the right fix, I'm hoping we can ask everyone to install this first, and use a bcdedit change as a temporary workaround until the right patch is installed.
Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3189866)
https://support.microsoft.com/en-us/kb/3189866

ok, I did find confirmation that the issue was fixed in KB3176934, which is included in all later update rollups too. The latest is KB3194496.
The easiest way to tell if you have this installed is to run winver, and look at the OS version number. 14393.222 is the latest as of today and it includes all fixes I mentioned.

I added an alternate PR that tells how to avoid the problem. I think it's easier to warn about the problem and ask to double check the OS version and update if needed instead of going straight to the BCDEDIT workaround.

Great.
I'm on 14393.51 so that may be the problem. Agreed that if being pro-active
on patch levels is preferable.
On 5 October 2016 at 15:05, Patrick Lang<EMAIL_ADDRESS>wrote:

I added an alternate PR that tells how to avoid the problem. I think it's
easier to warn about the problem and ask to double check the OS version and
update if needed instead of going straight to the BCDEDIT workaround.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/Virtualization-Documentation/pull/393#issuecomment-251813397,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGyvHOnbbT9JLSx3ncyFyYb8-JeeCBItks5qxB8igaJpZM4KJPYx
.

@PatrickLang @gavinbarron is this still relevant?  If not can I close the PR?

Thanks for bringing this up, but I merged in #406 instead. The new instructions in the Quick Start also check this automatically.


Support for Like a Dragon: Ishin!

Game name: Like a Dragon: Ishin!

Game package name: SEGAofAmericaInc.ProjectMacan_s751p9cej88mt
wgs.zip

This is now supported in the latest release https://github.com/Z1ni/XGP-save-extractor/releases


Add egg-pumpkin.json

Description
Add egg for Pterodactyl

Testing

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings: cargo clippy
[x] All unit tests pass: cargo test
[ ] I added new unit tests, so other people don't accidentally break my code by changing other parts of the codebase. How?

What have you done exactly to test it? I don't see anything specified in regards to that.
Even though docker is supposed to allow for one and the same environment to be replicate able across machines, I've found out that this may not always be the case.

What have you done exactly to test it? I don't see anything specified in regards to that.
Even though docker is supposed to allow for one and the same environment to be replicate able across machines, I've found out that this may not always be the case.

I ran it on Windows 11 WSL Debian bookworm.

Ran into the following issue after setting the CARGO_BUILD_JOBS environment value to a value and then emptying out the field.

error: could not parse ``. Number of parallel jobs should be `default` or a number.

You may need to setup better fallbacks with the following scripting syntax:
# takes CARGO_BUILD_JOBS env variable, if empty assigns "default".
CARGO_BUILD_JOBS=${CARGO_BUILD_JOBS:-default}

What have you done exactly to test it? I don't see anything specified in regards to that.
Even though docker is supposed to allow for one and the same environment to be replicate able across machines, I've found out that this may not always be the case.

I ran it on Windows 11 WSL Debian bookworm.

Windows (dies inside)

What have you done exactly to test it? I don't see anything specified in regards to that.
Even though docker is supposed to allow for one and the same environment to be replicate able across machines, I've found out that this may not always be the case.

I ran it on Windows 11 WSL Debian bookworm.

Windows (dies inside)

Need to play league of legends and I don't want to clutter my Debian server. I also have a dual boot with fedora, but I have not used it for a while.

What have you done exactly to test it? I don't see anything specified in regards to that.
Even though docker is supposed to allow for one and the same environment to be replicate able across machines, I've found out that this may not always be the case.

This is in docker's nature, because its repeatable and not reproducible, there is no way around this while using docker, i suggest we at least test it on macos, linux and windows before pushing this into master

We don't need to because Pterodactyl only supports Linux, see https://pterodactyl.io/wings/1.0/installing.html#supported-systems

I've tested this on my server and as long as the installation memory set in your Pterodactyl wing to a sufficient high number 4GB is probably best. It'll install just fine from there.


fix(requests, urllib3): Reverting last fix due to bug

Reverts epsagon/epsagon-python#286

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


Include easy module about mapping using usmap package

https://jtr13.github.io/cc19/different-ways-of-plotting-u-s-map-in-r.html
usmap is really nice. Something like this could be really great.
wa_dat <- countypop %>% filter(abbr == "WA")
plot_usmap(data = wa_dat,
           values = "pop_2022",
           include = c("WA")) +
  scale_fill_continuous() +
  theme(legend.position = "right")

Redundant with #147


Enable assertions in build.gradle

Codecov Report

Merging #93 (9994b5e) into master (0595cf0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #93   +/-   ##
=========================================
  Coverage     63.29%   63.29%
  Complexity      464      464
=========================================
  Files            94       94
  Lines          1738     1738
  Branches        183      183
=========================================
  Hits           1100     1100
  Misses          578      578
  Partials         60       60

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 0595cf0...9994b5e. Read the comment docs.


[feat] Named Parameter Groups in LearningRateMonitor

What does this PR do?
This PR allows the LearningRateMonitor callback to log the actual parameter group names, if they exist. It should fallback to prior behavior in the event that the parameter group names do not exist.
Fixes #7981
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Hello @AffineParameter! Thanks for opening this PR.

In the file pytorch_lightning/callbacks/lr_monitor.py:

Line 59:68: W291 trailing whitespace
Line 78:66: W291 trailing whitespace
Line 81:19: W291 trailing whitespace
Line 218:43: W291 trailing whitespace
Line 221:28: W291 trailing whitespace

In the file tests/callbacks/test_lr_monitor.py:

Line 312:5: E306 expected 1 blank line before a nested definition, found 0
Line 312:34: W291 trailing whitespace
Line 328:19: W291 trailing whitespace
Line 346:35: W291 trailing whitespace
Line 348:9: E123 closing bracket does not match indentation of opening bracket's line
Line 348:9: E125 continuation line with same indent as next logical line

Do see the Hitchhiker's guide to code style

Happy to update the CHANGELOG, provided I can get a milestone to target. This should tie a bow on things?
Thanks for the quick reviews!

@AffineParameter (love the name btw)  <3
This is a feature so it will go into 1.4. Could you add the changelog entry to the 1.4 section then in CHANGELOG.md?

PR Digression:
The contribution process (docs, workflow, reviews, etc.) have been really easy to work with! I am sure getting to this point hasn't been easy, but the effort and intentionality really shows. 🎩 's to all those responsible! :)

This is the last time I draw attention to my PR's by complementing the maintainers... 🤣
But seriously, I'll respond when I get the chance.

PR Digression:
The contribution process (docs, workflow, reviews, etc.) have been really easy to work with! I am sure getting to this point hasn't been easy, but the effort and intentionality really shows. 🎩 's to all those responsible! :)

Hey @AffineParameter, we definitely appreciated your mindset and contribution !
We hope to see more contributions from you and hope to keep the contribution process at the same high standard.
Best,
T.C


Add documentation on docker image use

... So people with little or zero docker experience could use it.
Also, I've checked that https://hub.docker.com/r/ethereumjs/ returns 404. Are you interested on having your docker hub account?
Anyways, I've built an image myself based on 21f2a7a, in my docker hub account

This is effectively a dupe of #62. Will eventually get to this. I'll talk to ethereumjs people about securing the name.

Can this or #62 be merged?

One can create Docker Hub organizations.  It feels like ethereumjs should be an organization, not a user.  If you all want, I can create an organization and add whomever to it and/or give ownership to whomever if that helps move things forward.

I merged another branch that had docker instructions a few minutes ago. Can one of you check to see if these instructions are correct, vs. the instructions in this PR? https://github.com/ethereumjs/testrpc#docker
I'm not a docker user so would love your help. If the instructions are incorrect and I should favor these instructions, let me know. Also, I'm very happy if someone would like to create and manage the ethereumjs docker org.

@tcoulter The instructions in this PR are a bit more verbose/thorough, but both these and the current set are correct.  Offer still stands to create a Docker organization for ethereumjs and setting up automated builds so we can get some images uploaded.

I'm open to you setting that up. I'm sure others would be as well.
On Sat, Feb 18, 2017, 3:32 PM Micah Zoltu<EMAIL_ADDRESS>wrote:

@tcoulter https://github.com/tcoulter The instructions in this PR are a
bit more verbose/thorough, but both these and the current set are correct.
Offer still stands to create a Docker organization for ethereumjs and
setting up automated builds so we can get some images uploaded.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereumjs/testrpc/pull/67#issuecomment-280872789,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFp1TPowmwZ1NTzJKC0mlHgXa5Rcz9xks5rd1VCgaJpZM4IE83N
.

I was checking my open PRs. I guess there will be no further action to this one. We close it?


Add basic test pipeline

@Sastopher Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Oops!


Incorporate CSSOM into RenderTree

This is more long term since the CSSOM doesn't exist yet, but when it does, need to leverage it to compute some of the styles/manipulate the box layout

I'm currently busy with the implementation of the css3 parser.  We have the "general parser" which is the one @neuodev has written, but it needs to have more specific parsers on top. For instance, the selector parser which understands how selectors are made up. There are a few more parsers we need to setup depending on the different css modules we support (we should support pretty much all of them as a browser).
So, at this point we have a semi-working AST which can be used for the CSSOM interface, but we still need to implement more.

We currently have a style calculator which can calculate the CSS properties per document node. This is the first step of the rendering pipeline which outputs the render tree

This is pretty much implemented in the new style CSS system


#5884 Avro Maps can't be flattened in Kafka Indexing on master

Fix issue https://github.com/apache/incubator-druid/issues/5884 by @varaga  @jon-wei on master branch.
Successfully tested with Confluent 5.1.0 kafka and schema registry

It would also appear that you have opened a duplicate PR, #7254.

Thanks @chrishardis for taking over the bug and committing it to master.
Would you be able to add some tests to cover the bug if it's feasible.

I spend my morning trying to run a test case, but it's not so easy has using the io.confluent.kafka.serializers.KafkaAvroSerializer without a kafkaproducer is quite an hard job. I test it many times on real Confluent 5.1 Kafka Cluster with Schema Registry.

I spend my morning trying to run a test case, but it's not so easy has using the io.confluent.kafka.serializers.KafkaAvroSerializer without a kafkaproducer is quite an hard job. I test it many times on real Confluent 5.1 Kafka Cluster with Schema Registry.

I think this issue would exist for any type of Avro indexing; like if you could create an Avro formatted file with a column that is a map type with utf8 keys, you could test with the Hadoop indexing tests if that would be easier.
That said, this change seems small and harmless enough that I think it would probably be ok without tests, so I will go ahead and approve.


Polymer Compat is broken since 1.0.1

Since I look at the item inside the packet byte buffer, now it doesn't recognise where the item is from.

Apparently this issue fixed itself?
Idk what Patbox or I did but polymer items display the correct mod.


Make sample redux example work with latest dependencies versions

Version
Tell us which versions you are using:

react-native-router-flux v4.0.6
react v16.8.6
react-native v0.59.4

Expected behaviour
I expect the sample project to work with latest versions of react-native
Actual behaviour
I got this error and was requested to upgrade gradle version.
After upgrading gradle, I'm able to build the project, but I get on my phone:
Unable to load script. Make sure you're either running a metro server...
Of course, I have the server running with no error: Running Metro Bundler on port 8081.
If I try to reload, I get a new error:
Could not connect to development server
I already tried to go to Dev settings -> Debug server host & port for device and set the 192.168.<local ip of my laptop>:8081
Steps to reproduce
For non-obvious bugs, please fork this component, modify Example project to reproduce your issue and include link here.

git clone https://github.com/Sharcoux/redux.git
cd redux
yarn install
react-native run-android

Reproducible Demo
Cf above

Not knowing if react-native-router-flux is directly responsible, I posted a question on stack overflow: https://stackoverflow.com/questions/55742983/impossible-to-make-react-native-router-flux-sample-project-work-with-latest-vers?noredirect=1#comment98169591_55742983

I started a bounty: https://stackoverflow.com/questions/55742983/impossible-to-make-react-native-router-flux-sample-project-work-with-latest-vers


[BUG] Dynamic Partition Insertion truncates entire delta table before write

Bug
Dynamic Partition Insertion truncates delta table before write; bug exists on databricks 10.4 LTS
Describe the problem
Contrary to documentation here: https://docs.databricks.com/spark/latest/spark-sql/language-manual/sql-ref-syntax-dml-insert-into.html

If you specify OVERWRITE the following applies:

Without a partition_spec the table is truncated before inserting the first row.
Otherwise all partitions matching the partition_spec are truncated before inserting the first row.

essentially; the below dynamic partition spec truncates entire table first (which is not desired)
insert overwrite into $target_table
partition (x, y, z)
select
derp
,x
,y
,z
from $source_table

you have to
insert overwrite into $target_table
partition (x = _x, y = _y, z = _z)
select
derp
from $source_table

Steps to reproduce
see above
Observed results
see above
Expected results
insert overwrite into $target_table
partition (x, y, z)
select
derp
,x
,y
,z
from $source_table

should truncate only matching partitions dynamically from the select
Further details
Looks related to:
https://github.com/delta-io/delta/pull/371
https://github.com/delta-io/delta/pull/1214
But they were closed without merging?
Environment information
Running on Databricks 10.4 LTS https://docs.databricks.com/release-notes/runtime/10.4.html

Delta Lake version: 1.1.0 (i had a read of the newer version release logs and  did not see any reference to dynamic partitions)
Spark version: 3.2.1

spark_config
spark.databricks.delta.merge.enableLowShuffle true
spark.databricks.delta.properties.defaults.autoOptimize.optimizeWrite true
spark.databricks.delta.properties.defaults.autoOptimize.autoCompact true
spark.databricks.acl.dfAclsEnabled false
spark.hadoop.fs.s3a.requester-pays.enabled true
spark.sql.shuffle.partitions 128

Scala version: 2.12

Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?

[ ] Yes. I can contribute a fix for this bug independently.
[X] Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
[ ] No. I cannot contribute a bug fix at this time.

Hey @crankswagon, we're planning on releasing this with Delta Lake 2.0.0, and it's currently included in the Delta Lake 2.0.0 Preview.


System Center 2022 is already GA

System Center 2022 is already GA.
https://cloudblogs.microsoft.com/windowsserver/2022/04/01/system-center-2022-is-now-generally-available/

@tksh164 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#assign:robinharwood


XmlLayout + JsonLayout - ExcludeProperties using StringComparer.OrdinalIgnoreCase

Nice. Maybe good idea to add unit tests?

Yes more unit-tests should be made, especially since the unit-tests from the Database-Target might move into its own repository.
After trying to use ValueTypeLayoutInfo more places, then I think it should be implemented differently. I don't like that one is required to inherit from the ValueTypeLayoutInfo.

Because Microsoft broke Visual Studio in ver. 16.10. So rolling back to 16.9 until AppVeyor has updated their latest image with bugfix.
Sent from my Sony Xperia
---- Julian Verdurmen wrote ----
@304NotModified commented on this pull request.

In appveyor.ymlhttps://github.com/NLog/NLog/pull/4470#discussion_r655777374:

@@ -1,6 +1,6 @@
version: 4.7.0-{build}
image:

Visual Studio 2019

Previous Visual Studio 2019

Why do we need this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/NLog/NLog/pull/4470#pullrequestreview-688947577, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXZ7HH77BSJAVE6H7JPD5TTT7FKZANCNFSM467OSN6A.


Move Crystalline to LSProtocol

LSProtocol is a repo with auto-generated types for the language server protocol, which I have added Crystal support to here (and an external shard here). Being auto-generated, it makes adding new functionality really easy, and is the basis of development for larimar.
Moving crystalline to this would involve moving the server component of elbywan/lsp into crystalline itself, but would allow for more control of the server as a whole, alongside not needing to figure out the LSP API itself (on a protocol level).
If you would be interested in this, I'd be happy to port crystalline over and create a PR. Feedback is also welcome.

Hey, thanks for reaching out but I am not interested.
See: https://github.com/elbywan/crystalline?tab=readme-ov-file#project-status

See: https://github.com/elbywan/crystalline?tab=readme-ov-file#project-status

I just read the readme. It's sad that someone treated you that way. I've been using Crystalline for a few months. For me, if there were no LSP server, I probably wouldn't have gotten interested in the Crystal language. Sometimes autocompletion doesn't work - I haven't figured out when exactly. But even so, it's very useful. Despite everything, I believe there are more users who appreciate your work (like me), even if they might not be vocal about it.

I'm not so sure about the trash-talk thing, but man I really wished the Crystal team valued this project more. There's a trend of modern languages treating LSP as a first-class citizen, but Crystal isn't one of them. IMO it's got the biggest leverage for fixing the language's popularity, above Windows support.
Crystalline already is a fantastic project. It's the de-facto standard tooling for the language and like most people, I use it exclusively when developing in Crystal. Once you've set it up, it works outstandingly well, given the heavy constraints the language must pose you. Yet somehow nobody in the ecosystem actually cares for it. It's so weird.
Thanks for your work elbywan!

I'm not so sure about the trash-talk thing, but man I really wished the Crystal team valued this project more. There's a trend of modern languages treating LSP as a first-class citizen, but Crystal isn't one of them. IMO it's got the biggest leverage for fixing the language's popularity, above Windows support.
Crystalline already is a fantastic project. It's the de-facto standard tooling for the language and like most people, I use it exclusively when developing in Crystal. Once you've set it up, it works outstandingly well, given the heavy constraints the language must pose you. Yet somehow nobody in the ecosystem actually cares for it. It's so weird.
Thanks for your work elbywan!

Totally agree with you!
I don't know why the Crystal core team was so hasty, I had mentioned it multiple times on the forum before, they spend too much resources on (unpopular) Windows, while they don't care about the actual users' experience.
Some responsible language, LSP is even part of language itself, but, i consider Crystal core team never really considered supporting it.


Please add Hebrew Local (iw) to the list

Please could you add Hebrew (iw) to the locales list? You have "he" but iw is also used.

Yes please, you are correct in theory, but indeed there are some applications out there that specifically cite iw when displaying Hebrew and hence my original request

Ok, I'm going to close this in favour to #46 then


QueryDirectory with filter incorrectly reports "NO SUCH FILE" in winfspy

The reason that the file in the filter is not found is because winfspy reports it as L"\0" and the FSD compares it to L"". Windows does not use NULL-terminated strings internally, so the FSD finds that these 2 strings are not the same.
In fact, removing the +2 from this line does fix the problem:
https://github.com/Scille/winfspy/blob/6cd4d27e922b9a986e67962001f7796dfbc7276c/src/winfspy/operations.py#L610
Thanks @billziss-gh for reporting this issue and providing the relevant information!

Fixed in #13